Updates to Dynamic IPv6 Multicast Address Group IDs

For IPv6 multicast addresses, defines the lower 32 bits of the IPv6 address, which are mapped directly to the link-layer, as the group ID, and then assigns ranges of group ID values based on how they are allocated. Section describes dynamic assignment of group ID values and lists two different approaches (server allocation and host allocation). However, both approaches are assigned the same range of group ID values, which means they cannot coexist without risking an address collision. Also concerning is that the range for dynamic assignment overlaps with the range used for solicited-node multicast addresses (see ). Only one server allocation protocol has been defined so far (see ), but advocates developing a decentralized, zero-configuration host allocation protocol. This document updates the dynamic IPv6 multicast group ID ranges to better align with current practices for protocol number assignment and to support development of additional dynamic allocation protocols.

Requirements Language The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here.

Existing group ID allocations specified in and are summarized in the following table: Existing Allocations

`0x80000000`-`0xFEFFFFFF`		Server allocation (MADCAP)	Host allocation
`0xFF000000`-`0xFFFFFFFF`	Solicited-node

This document updates the allocations in and moves them into a new registry in the IPv6 Multicast Address Space Registry registry group. The registry shall be populated with the following entries: Updated Allocations

Range	Description	Reference
`0x80000000`-`0x8FFFFFFF`	MADCAP
`0x90000000`-`0xFEFFFFFF`	Unassigned
`0xFF000000`-`0xFFFFFFFF`	Solicited-node multicast addresses

This reduces the range previously available for MADCAP, while still providing a sizable allocation. In addition, this documents the range used for solicited-node multicast addresses and reserves the remaining entries for future protocol development.

This document does not expand on any security considerations beyond what is discussed in .

IANA should create a new registry named "Dynamic Multicast Group IDs" in the "IPv6 Multicast Address Space Registry" registry group. This registry shall initially contain the entries listed in . The "Standards Action" registration policy is required to update the registry. IANA should also update the references to "FF3X:0:0:0:0:0:8000:0-FF3X:0:0:0:0:0:FFFF:FFFF" in the "Unicast-based (Including SSM) Multicast Group IDs" registry in the "IPv6 Multicast Address Space Registry" registry group. The registration procedure should indicate that this range uses dynamic assignment according to the protocols listed in the new "Dynamic Multicast Group IDs" registry and include a reference to this document. The description in the registry entry should indicate that this range uses dynamic assignment according to the protocols listed in the new "Dynamic Multicast Group IDs" registry and the reference should be changed to this document.

Special thanks to the National Marine Electronics Association for their contributions in developing marine industry standards and their support for this research. Thanks also to the members of the PIM working group for their early brainstorming sessions and review of this draft. Finally, thanks to Dave Thaler for discussing MADCAP deployment in Microsoft products and the impact of changing the range of group IDs used by MADCAP.