Hi Benson, Not speaking to the utility of that particular proposal, but I would think that the policy (ARIN Draft Policy 2011-5) might also need to be reposted as an IETF RFC to modify the IANA address registry. (in much the same way rfc3849 came from the APNIC allocation)
If that were the case then the IANA address registry would reflect it. Otherwise, I am not aware of any provision for an individual RIR to set a particular prefix's status without some global policy work being done. Cheers Terry On 24/06/11 10:27 AM, "Benson Schliesser" <[email protected]> wrote: > > > On 6/23/11 6:54 PM, "Terry Manderson" <[email protected]> wrote: > >> The obvious example (and please - I don't care to buy into the brouhaha of >> 6to4 going historic) is "192.88.99.0/24 reserved for 6to4 Relay Anycast" >> >> The designated status is reserved, but it is routable. > > Thanks for the clarification, Terry. Your explanation makes sense. > > Out of curiosity: In the event that an RIR sets aside a block to be Non > Routable (such as ARIN Draft Policy 2011-5) would the PRI designation be > ALLOCATED Non Routable, or something else? > > Cheers, > -Benson > _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
