How do I get a registered multicast block?
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
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
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?
Owen
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
Does it make sense to be planning new deployments for anythign else? 
(Hint - if your reaction is "but we're not v6-capable", who's fault is that?)
The original question was not from me. 
But even for IPv6 I would avoid embedded addressing and just use SSM.
With SSM there's no need for embedded addressing and again you get all
the security and network simplicity.
FF3x::/96
Greg
SSM is indeed a lot simpler and better than GLOP in every conceivable way -
except vendor support. It needs igmpv3 on all intermediate devices and SSM
support on the client device. All major desktop operating systems now have
SSM support (OS/X since 10.7/Lion), but there is still lots of older
hardware which either doesn't support igmpv3 or else only supports it in a
very primitive fashion. This can lead to Unexpected Behaviour in naive
roll-outs.
Nick
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.SSM is indeed a lot simpler and better than GLOP in every conceivable way -
except vendor support. It needs igmpv3 on all intermediate devices and SSM
support on the client device. All major desktop operating systems now have
SSM support (OS/X since 10.7/Lion), but there is still lots of older
hardware which either doesn't support igmpv3 or else only supports it in a
very primitive fashion. This can lead to Unexpected Behaviour in naive
roll-outs.
I haven't seen a piece of network gear without SSM support in a very
long time. The weak link is the applications. It was the OS stacks but
that's finally caught up - it only took it 10 years...
The weakest link is simply multicast deployment - if it's not
everywhere it has little use. That's what AMT is promising to fix. And
with AMT comes the opportunity to bring SSM to non-SSM-capable apps if
it is implemented correctly.
Greg
And I've seen plenty of gear without SSM support:
Some of the larger offenders:
Juniper Clusters.
Cisco ASA
Some Linksys managed switches (no IGMP snooping support for it).
I really wouldn't think it'd be that hard to implement SSM if the equipment
had functional ASM support, but that's a story for another day I guess.
Most development for mcast largely occurred between the last 90s and early
2000s it seems. Since ~2005 once the hopes of inter-domain multicast
fizzled and IPTV failed to launch in any meaningfully way, multicast
development has largely been neglected by the major equipment vendors and
cast away as some funky thing used by certain enterprise and educational
market segments.
At least, IMHO...
Hi,
All modern routers support mapping from IGMPv2 to PIM SSM, all static, some others thru DNS, etc
Regards,
Jeff
If you truly need a globally unique multicast block, and GLOP/RFC6034/SSM won't work, you can submit an application to IANA here:
Hi,
All modern routers support mapping from IGMPv2 to PIM SSM, all static, some others thru DNS, etc
I am not sure what you mean here. To support SSM, you need IGMPv3. Most
routers do support IGMPv3, but there is still a fair amount of legacy
gear at various
edges which doesn't.
Regards
Marshall
Marshall,
That's exactly what the feature does, when it receives a IGMPv1/2 join it adds a preconfigured S and sends S,G (INCLUDE)upstream.
Google for IGMP mapping
Regards,
Jeff