mulcast assignments

Thu May 3 20:38:14 UTC 2012

On Thu, May 3, 2012 at 1:19 PM, Owen DeLong <owen at delong.com> wrote:
> Simpler solution... Just set the P flag and use your unicast prefix as part 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 recommended
> to be ≤32 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 at 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 at 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 at yahoo.com> wrote:
>>>>    How do I get a registered multicast block?
>>>>
>>>
>>>
>