[ppml] [address-policy-wg] Re: Can the RIRs bypass the IETF and do their own thing?

[JORDI PALET MARTINEZ]

I've not started the discussion of ULA-central on this list.

It has been started in other RIRs because they had accepted my policy
proposals on that.

Discussing about the ID and the policy proposals are different issues, and
can be handled in parallel, unless you show me anything in the PDP that says
"no".

Regards,
Jordi




> De: <michael.dillon at bt.com>
> Responder a: <ppml-bounces at arin.net>
> Fecha: Wed, 16 May 2007 11:36:39 +0100
> Para: <ppml at arin.net>
> Conversación: [ppml] [address-policy-wg] Re: Can the RIRs bypass the IETF and
> do their own thing?
> Asunto: Re: [ppml] [address-policy-wg] Re: Can the RIRs bypass the IETF and do
> their own thing?
> 
>> If you know about the IETF process, you will also know that the proper
>> venue
>> for ULA-central ID discussion is ipv6 at ietf.org.
> 
> Then why are you dragging it into the RIR policy groups? Fred Baker has
> offered the v6ops working group, which again, is an IETF venue, not an
> RIR policy list.
> 
>> This doesn't precludes on discussion in parallel the related policy
>> (proposal), in those RIR service regions where it has been submitted
> (not
>> yet here at ARIN, but I will do soon).
> 
> As you have pointed out, there is no draft under discussion so any talk
> in the RIRs is beyond premature.
> 
> I would hope that the Advisory Council rejects your proposal on that
> basis. There is absolutely no urgency to act upon Central ULA addressing
> until after it reaches RFC status. We should wait.
> 
> --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.