[arin-ppml] Transfer Proposals

[David Farmer]

I've been reading up on the NRPM, and I have a few comments to add.

On 30 Sep 2008 Leo Bicknell wrote:

> In a message written on Tue, Sep 30, 2008 at 01:15:33AM -0500, mack wrote:
> > Wow, I did a closer read and you are correct.
> > There is nothing in either the policy manual or
> > the RSA that requires the return of unused resources
> > if they are justified and later not needed.
> 
> http://www.faqs.org/rfcs/rfc2050.html
> 
> Section 3.1:
> 
> ] IP addresses are valid as long as the criteria continues to be met.
> ] The IANA reserves the right to invalidate any IP assignments once it
> ] is determined the the requirement for the address space no longer
> ] exists.  In the event of address invalidation, reasonable efforts
> ] will be made by the appropriate registry to inform the organization
> ] that the addresses have been returned to the free pool of IPv4
> ] address space.

Actually NRPM 4.1.2, 4.1.3, and 4.1.4 paraphrases much of this text, as it 
probably should.  However, 2007-14 proposes to delete these sections, and 
I'm not sure it replaces every thing it deletes, I'll make those comments in 
regard to 2007-14, but if this issue is important to you maybe you should 
look closely at 2007-14.

] 4.1.2. Validity
] 
] IP address allocations are valid as long as the utilization and other relevant
] criteria continue to be met, and the yearly fee is submitted.
] 
] 4.1.3. Invalidation
] 
] ARIN may invalidate any IP allocation if it determines that the requirement 
] for the address space no longer exists.
] 
] 4.1.4. Recall
] 
] In the event of address space recall, ARIN will make every reasonable
]  effort to inform the organization that the addresses are being returned to
]  the free pool of IPv4 address space.

So these with 4.1.7's reference to RFC 2050 cover the issue, however given 
that we are moving into a world with no IANA Free Pool more explicit 
language could probably be helpful.  The language here in the NRPM and 
RFC 2050 leave a lot to interpretation.

> http://www.arin.net/policy/nrpm.html#four17
> 
> ] 4.1.7. RFC 2050
> ] 
> ] ARIN takes guidance from allocation and assignment policies and
> ] procedures set forth in RFC 2050. These guidelines were developed to
> ] meet the needs of the larger Internet community in conserving scarce
> ] IPv4 address space and allowing continued use of existing Internet
> ] routing technologies.
> 
> http://www.arin.net/registration/agreements/rsa.pdf
> 
> ] 7. POLICIES 
> ] 
> ] Pursuant to ARIN's Internet Resource Policy Evaluation Process
> ] ("IRPEP"), ARIN maintains the Policies and may amend the Policies,
> ] implement new policies (which once implemented, will be considered
> ] Policies), or make certain Policies obsolete. Applicant acknowledges
> ] and agrees it has read, understands, and agrees to be bound by and
> ] comply with the Policies, as amended.  ARIN may, at any time in its
> ] sole and absolute discretion, amend the Policies or create new
> ] Policies and such amendments or new Policies shall be binding upon
> ] Applicant immediately after they are posted on the Website.
> 
> RSA->Policies->2050->Unused IP allocations can be invalidated.
> 
> -- 
>        Leo Bicknell - bicknell at ufp.org - CCIE 3440
>         PGP keys at http://www.ufp.org/~bicknell/
 



=======================================================
David Farmer				     Email:	farmer at umn.edu
Office of Information Technology
Networking & Telecomunication Services
University of Minnesota			     Phone:	612-626-0815
2218 University Ave SE			     Cell:		612-812-9952
Minneapolis, MN 55414-3029		     FAX:	612-626-1818
=======================================================