[ppml] Proposed Policy: eGLOP Multicast Address Assignments - not accepted by AC as formal policy proposal
tme at multicasttech.com
Fri Mar 2 14:06:43 EST 2007
On Mar 2, 2007, at 1:29 PM, Andrew Dul wrote:
>> -------Original Message-------
>> From: Marshall Eubanks <tme at multicasttech.com>
>> Subject: Re: [ppml] Proposed Policy: eGLOP Multicast Address
>> Assignments - not accepted by AC as formal policy proposal
>> Sent: 02 Mar '07 10:19
>> On Mar 2, 2007, at 12:46 PM, Member Services wrote:
>>> On 1 March 2007 the ARIN Advisory Council (AC) concluded its
>>> review of
>>> the proposed policy 'eGLOP Multicast Address Assignments' and did
>>> accept it as a formal policy proposal.
>>> Citing RFC 2050, the AC concluded that ARIN was not empowered to
>>> administer multicast address space.
>> I must admit that I do not understand this reasoning, and intend to
>> petition / appeal this.
>> RFC 2050 / BCP 12 merely says WRT multicast that
>> This document does not describe private Internet address space and
>> multicast address space.
> I would also tend to agree.
> To me, RFC 3180 specifically asks the RIRs to administer this space.
> However, I also realize administration of multicast space is
> something new for the RIRs and we need to consider this before
> jumping in. This policy proposal, as written, is probably not
> complete enough as written and needs further work (specific
> allocation criteria, etc).
I will be working with Filliz Yilmaz of RIPE to help get this into
appropriate shape for them. I would be glad to hear suggestions on or
off list as to how to do that.
> The other issue that don't know if it has been considered with is
> the issue of ensuring uniqueness between RIRs . Do we expect IANA
> to chop up the eGLOP space and give a chunk to each RIR?
That is a good question - as written, it does. However, it would also
be suitable to have only one RIR take this on, or even to set up a
new entity just for this purpose.
More information about the ARIN-PPML