[152618] in North American Network Operators' Group
Re: mulcast assignments
daemon@ATHENA.MIT.EDU (Greg Shepherd)
Thu May 3 16:39:04 2012
In-Reply-To: <1824091A-68F2-4DD0-8615-A7394B9C9641@delong.com>
Date: Thu, 3 May 2012 13:38:14 -0700
From: Greg Shepherd <gjshep@gmail.com>
To: Owen DeLong <owen@delong.com>
Cc: NANOG list <nanog@nanog.org>
Reply-To: gjshep@gmail.com
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, May 3, 2012 at 1:19 PM, Owen DeLong <owen@delong.com> wrote:
> Simpler solution... Just set the P flag and use your unicast prefix as pa=
rt of the group ID.
>
> For example, if your unicast prefix is 2001:db8:f00d::/48, you could use:
>
> ff4e:2001:db8:f00d::<group number>
>
> Where <group number> is any number of your choosing up to 64 bits, but re=
commended
> to be =E2=89=A432 bits.
>
> Make sense?
Sure, for v6. :)
Greg
> Owen
>
> On May 3, 2012, at 1:00 PM, Greg Shepherd wrote:
>
>> Sure, but GLOP predated SSM, and was really only an interim fix for
>> the presumed need of mcast address assignments. GLOP only gives you a
>> /24 for each ASN where SSM gives you a /8 for every unique unicast
>> address you have along with vastly superior security and network
>> simplicity.
>>
>> Greg
>>
>> On Thu, May 3, 2012 at 12:53 PM, Quentin Carpent
>> <quentin.carpent@vtx-telecom.ch> wrote:
>>> You can also use the glop IP addressing:
>>> http://tools.ietf.org/html/rfc3180
>>>
>>> Quentin
>>>
>>> -----Original Message-----
>>> From: Greg Shepherd [mailto:gjshep@gmail.com]
>>> Sent: Thu 5/3/2012 9:35 PM
>>> To: Philip Lavine
>>> Cc: NANOG list
>>> Subject: Re: mulcast assignments
>>>
>>> Why do you think you need an assigned mcast block? All inter domain
>>> mcast uses source trees only, so just use SSM and you don't need
>>> address assignments.
>>>
>>> Greg
>>>
>>> On Thu, May 3, 2012 at 12:24 PM, Philip Lavine <source_route@yahoo.com>=
wrote:
>>>> =C2=A0 =C2=A0How do I get a registered multicast block?
>>>>
>>>
>>>
>
