[ppml] Proposal for the creation of a working group.

[Leo Bicknell]

In a message written on Wed, Oct 10, 2007 at 09:39:22AM -0500, Stephen Sprunk wrote:
> What is stopping someone from putting "Upon adoption by all other RIRs" in 
> the "Timetable for implementation" slot of the policy template?  We could 
> pass a proposal but it wouldn't go into the NRPM or be implemented by staff 
> until that occurred.  Given how nearly all proposals give a timetable of 
> "immediately", such a trick seems like the only purpose for having that 
> field...

Truthfully, I'm not entirely clear.  If you look at
http://www.nro.net/documents/nro4.html the problem seems to be in
step 4:

] 4. This common text will be ratified by each RIR, by methods of its own
]    choosing.

I'm not sure if it's ARIN's interpretation, or the NRO's interpretation
of ARIN's policies, but "ratified" seems to mean a passed policy
proposal added to the NRPM.  That's not to say it has to be
implemented, e.g. ARIN actively doing what it is the policy states,
but it needs to be in the ARIN NRPM somewhere.

This gives rise to some fairly absurd (at least to me) situations.
Consider this global policy:
http://www.nro.net/policy/iana-rir-ipv6-allocation-proposal.html

So the RIR's have to each put in their own policy process information
on how IANA is going to hand them blocks as if it were so, so the
NRO can approve it and then IANA can do it.  It's just backwards.
How IANA hands out space to RIR's should not appear in any RIR's
policy manuals, that's not something an RIR can implement.  RIR's should
have input, and the method of making that policy should be bottom up; I
don't want to change any of that.  I do feel strongly there should be a
way for RIR's to send off delegates or statements or something though to
the central policy making group and have this end up as a central,
global policy in a much more straight forward method though.

-- 
       Leo Bicknell - bicknell at ufp.org - CCIE 3440
        PGP keys at http://www.ufp.org/~bicknell/
Read TMBG List - tmbg-list-request at tmbg.org, www.tmbg.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20071010/2f05ff9a/attachment.sig>