Creation of Reverse Delegation Objects

On Thu, 25 Apr 2002, Tanja Heimes wrote:

> Date: Thu, 25 Apr 2002 17:34:34 +0200
> From: Tanja Heimes <theimes at de.cw.net>
> To: Rimas Janusauskas <Rimas.Janusauskas at sc.vu.lt>
> Cc: Dominic Spratley <dominic at ripe.net>, lir-wg at ripe.net
> Subject: Re: Creation of Reverse Delegation Objects
>
> Rimas,
>
> you mean - than end-users could use this zz.unspecified reg-id in order
> to perform reverse delegation
> records by themselves?
>
>
> Tanja
>


Exactly!

Dominic could correct me if I'm wrong:
message with reverse address delegation reguest is checked for regID;
if found, it's ckecked, do address space is allocated to the registry;
if yes - further actions on reguest are taken.

So, if introduce zz.unspecified RegID for PI address assignments,
the described scheme should work.

One more thing: section 5.3.4 of ripe-185 might be revised, if my proposal
seems acceptable. Current statement:

	5.3.4.Side Effects for PA/PI Assignments
	End users have a right to reverse mapping services. An end user holding
	non-PA address space from a zone that has been reverse delegated to one
	service provider is permitted to keep the address space, and obtain
	connectivity services from another provider. Because the address space
	falls in the reverse delegation zone of the initial Local IR, that IR is
	required to continue to provide reverse mapping services for the address
	space assigned to the end user. Moreover, the Local IR has to provide this
	service under the same conditions it applies to its other end users (e.g.
	extremely high fees for this service are unacceptable - unless they are
	applied to all end users.)

IMHO,  this is shortest way to eliminate contradiction.


Best regards,

Rimas