Creation of Reverse Delegation Objects

Hi Tanja,

There are several reasons why we do not accept requests directly
from end-users. Most are based on the fact that the Internet
Registry system is hierarchical. This means that we are funded by
LIRs to provide services to them, not to end-users.

LIRs have more expertise in dealing with the RIPE Database than
End Users. This is the main reason for requiring requests to come
from them.

Yours sincerely,


Dominic Spratley,

R.S. Assistant Manager,
RIPE NCC



At 09:45 AM 4/24/2002 +0200, Tanja Heimes wrote:
>Hi All,
>
>this ist the response of the RIPE Robot to one of our customers after he
>tried to create a reverse delegation object in the RIPE DB:
>
>"The RIPE NCC no longer accepts requests for creation and ammendments
>of reverse delegations which do not include the registry ID of an
>existing Local Internet Registry.
>
>If you are not a representative of an LIR, you should contact the
>LIR who assigned you the address space, or your upstream provider..."
>
>The customers owns his Provider Independent IP address space and is not
>able to create this object as he needs to state a
>reg-id in the request. Now this customers (and others in the past) claim
>that they have to apply to there upstream provider in
>order that this ISP creates the object. The customer certainly has is
>own maintainer.
>
>My question now:
>
>Should  Provider Indepent IP space not be 100% Provider Indepent in
>concern to its administration in the RIPE DB?
>In my opinion the RIPE Robot should distinguish between PA and PI space
>and not request an reg-id for customers that own PI
>space and like to create a reverse delegation record.
>
>Best regards,
>
>Tanja Heimes
>
>
>--
>Tanja Heimes / IP Engineer              E-Mail Tanja.Heimes at de.cw.com
>
>Cable & Wireless Deutschland GmbH       TEL. + 49 89 92699-0
>Landsberger Strasse 155                 Fax. + 49 89 92699-810
>D-80687 Munich, Germany                 web: http://www.cw.com/de