Benson,
I agree with Terry.
When the proposal was sent to the IETF the environment was different.
We still have v4 addresses in IANA's pool and I think that the feeling was "we
do not want to give that precious space for a shared pool because there is one
already". Now things are different, there are no more addresses in the central
pool, v4 address are more scarce, ISPs claim that need space for transition
technologies to v6, and the ARIN community is willing to give some space for
that purpose (this last one is the important one IMHO).
I cannot speak for others, but in my view a new I+D similar to the last
one (I think it was sent to OPSWAG WG) with some amendments would have more
opportunities to be adopted.
Regards,
.as
On 28 Jun 2011, at 21:32, Terry Manderson wrote:
> 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
_______________________________________________
GROW mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/grow
