Funet > Network services and support > IP multicast > Multicast address allocation in Funet, NORDUnet and TERENA
 
Tehdyt toimenpiteet

Multicast address allocation in Funet, NORDUnet and TERENA

It has been agreed on principles how the global IPv4 multicast address space is divided among users. In order to guarantee successful operation, please, configure your systems according to these instructions.

The IPv4 multicast address space (224.0.0.0-239.255.255.255) has been divided to multiple diffent parts with different allocation and routing policies that may depend on where you are located. The best source for current information is your network service provider's multicast routing expert who should coordinate routing with TERENA and RIPE.

Here's a quick overview of various address ranges as seen from the Funet network which has multicast connectivity via NORDUnet to at least GEANT and Internet 2 networks. This page is by no means complete. New allocation methods and address ranges are being agreed in various forums. For GEANT backbone users the Dante MBONE-pages should provide more information.

The SSM and GLOP ranges might suit applications needing a semi-permanent address or other special needs as detailed in the relevant RFCs. As always, please check your local routing and filtering setups as well as the relevant allocation authorities before using of most other addresses than the traditional SAP dynamic assingments.

Addresses

Description

References

224.0.0.0 - 224.0.0.255

statically assigned link-local scope

RFC2365, IANA

224.0.1.0 - 224.0.255.255

statically assigned addresses

IANA

224.2.0.0-224.2.127.253

Multimedia Conference Calls

RFC2365, IANA

224.2.128.0-224.2.255.255

SAP Dynamic Assignments (sdr allocates from here by default)

RFC2365, IANA

232.0.0.0 - 232.255.255.255

Source specific multicast (SSM)

RFC3569, IANA

233.0.0.0 - 233.251.255.255

AS based GLOP addressing

RFC2770, IANA

233.6.205.0-233.6.205.255 Funet (AS1741) GLOP block, propagated globally
Funet

239.0.0.0 - 239.255.255.255

Scoped address range

RFC2365, IANA

239.192.0.0 - 239.195.255.255

organization-local scope (In Europe suballocated, see below)

RFC2365, IANA

239.192.0.0 - 239.192.255.255

NORDUnet scope

personal communication

239.193.0.0 - 239.193.255.255

Funet scope

Funet

239.194.0.0 - 239.194.255.255

European academic network scope

Dante, RFC2365

239.252.0.0 - 239.255.255.255

site-local scope

RFC2365, IANA

Scoped addresses are a very efficient way to limit the reach of a multicast group but not implemented everywhere yet. No information about the group should flow beoynd the scope boundary so it should lessen the load on routers, allow address space reuse and improve security and stability provided the scoping is well implemented in all border routers.

This page has originally been compiled from the mentioned references in the context of Terena TF-Stream task force by  Harri Salminen and has had occasional updates afterwards.