[ppml] Proposed Policy: eGLOP Multicast Address Assignments -not accepted by AC as formal policy proposal

Andrew Dul andrew.dul at quark.net
Sat Mar 3 14:18:12 EST 2007

At 05:59 PM 3/2/2007 -0500, Leo Bicknell wrote:

>It would seem to me that 3180 could be interpreted as "Additional
>guidelines" and thus I don't see a 2050 problem.
>I think the bigger problem here is, what is ARIN to do?  Reading
>3180 (http://www.faqs.org/rfcs/rfc3180.html) there's no registry
>function.  You take a prefix, you add your AS number.  Boom, done.
>There's nothing for ARIN to allocate, track, report on or otherwise
>Since the purpose of a policy proposal is to change the NRPM, and
>this references no sections of the NRPM, what specifcally do you
>want ARIN to do?  Perhaps if you rephrased in the form "Insert into
>section x.y.z of the NRPM the following text:" it would be more

My understading was this policy was trying to create a registry to
administer 233.x.y.z  where x & y is composed of the private ASN range of
64512 - 65534. Someone correct me if I'm wrong...

More information about the ARIN-PPML mailing list