[ppml] [address-policy-wg] Those pesky ULAs again

[JORDI PALET MARTINEZ]

That's broken. As it has been stated in previous messages some days ago, RIR
communities can do whatever they want, especially if IETF fails. I'm doing
IETF work, but it is clear that some times, for whatever reasons is too
slow, or even fails. This community has the right to bypass that if
required.

And one more demonstration that this is broken: All the RIRs did 4-byte-ASN
policies when no RFCs where available. As you can see the RIR system is
still working.

So yes, I will much prefer to have an RFC, and this is the way we are going,
but nothing precludes to go in parallel, as it has been done in the
4-byte-ASN, and probably some other times I guess.

And, in the worst case, if the IETF fails again on this (I'm sure will not
be the case this time), we could always go for a global policy to instruct
IANA to delegate that resource to the RIRs.

Regards,
Jordi




> De: <michael.dillon at bt.com>
> Responder a: <ppml-bounces at arin.net>
> Fecha: Tue, 29 May 2007 22:13:47 +0100
> Para: <ppml at arin.net>, <address-policy-wg at ripe.net>
> Conversación: [ppml] [address-policy-wg] Those pesky ULAs again
> Asunto: Re: [ppml] [address-policy-wg] Those pesky ULAs again
> 
>> The policies for ULA-C are likely to be different from
>> the policies for PI.
> 
> ULA-C doesn't exist. There is not even a current Internet draft to
> define what the acronym stands for. If any RIRs create a policy on that
> basis, then it will be the beginning of the end of the RIR system.
> 
> The RIRs are supposed to be stewards, prudently managing a shared
> resource. 
> 
> --Michael Dillon
> 
> _______________________________________________
> This message sent to you through the ARIN Public Policy Mailing List
> (PPML at arin.net).
> Manage your mailing list subscription at:
> http://lists.arin.net/mailman/listinfo/ppml




**********************************************
The IPv6 Portal: http://www.ipv6tf.org

Bye 6Bone. Hi, IPv6 !
http://www.ipv6day.org

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.