RFC 2375

IPv6 Multicast Address Assignments

πŸ“… published July 1998, from ietf

RFC 2375: IPv6 Multicast Address Assignments πŸŽ€

Title block facts, bestie: this is RFC 2375, from the Network Working Group, dated July 1998. The authors are R. Hinden (Ipsilon Networks) and S. Deering (Cisco). It's Category: Informational, so it's giving "here's some info" rather than "here's a rule you must follow." The title block doesn't list anything it obsoletes or updates. πŸ’…

Status of this Memo

This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. 🧚

Copyright (C) The Internet Society (1998). All Rights Reserved. πŸ“œ

1.0 Introduction ✨

Okay so this document sets up the initial assignment of IPv6 multicast addresses. It's built on the "IP Version 6 Addressing Architecture" [ADDARCH] and on the current IPv4 multicast address assignments listed at ftp://venera.isi.edu/in-notes/iana/assignments/multicast-addresses. The IPv4 assignments that matter for IPv6 got adapted into IPv6 assignments, and the ones that weren't relevant didn't get converted. The authors are literally asking for comments on this conversion, so if you have thoughts, speak up! πŸ¦‹

Also, every other IPv6 multicast address is reserved. Hands off, bestie. πŸ™ˆ

Sections 2 and 3 are where the reserved and preassigned IPv6 multicast addresses get specified, and [ADDRARCH] is where the rules for assigning brand-new ones live. πŸ’–

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119]. Those are the official BCP 14 words, so they carry exact meaning here. πŸ”₯

2. Fixed Scope Multicast Addresses πŸ’–

These permanently assigned multicast addresses are valid over a specified scope value. Think of the scope value as the address's guest list. πŸŽ€

2.1 Node-Local Scope πŸ¦‹

FF01:0:0:0:0:0:0:1     All Nodes Address                  [ADDARCH]
FF01:0:0:0:0:0:0:2     All Routers Address                [ADDARCH]
FF02:0:0:0:0:0:0:1     All Nodes Address                  [ADDARCH]
FF02:0:0:0:0:0:0:2     All Routers Address                [ADDARCH]
FF02:0:0:0:0:0:0:3     Unassigned                             [JBP]
FF02:0:0:0:0:0:0:4     DVMRP Routers                  [RFC1075,JBP]
FF02:0:0:0:0:0:0:5     OSPFIGP                        [RFC2328,Moy]
FF02:0:0:0:0:0:0:6     OSPFIGP Designated Routers     [RFC2328,Moy]
FF02:0:0:0:0:0:0:7     ST Routers                    [RFC1190,KS14]
FF02:0:0:0:0:0:0:8     ST Hosts                      [RFC1190,KS14]
FF02:0:0:0:0:0:0:9     RIP Routers                        [RFC2080]
FF02:0:0:0:0:0:0:A     EIGRP Routers                    [Farinacci]
FF02:0:0:0:0:0:0:B     Mobile-Agents                 [Bill Simpson]

FF02:0:0:0:0:0:0:D     All PIM Routers                  [Farinacci]
FF02:0:0:0:0:0:0:E     RSVP-ENCAPSULATION                  [Braden]

FF02:0:0:0:0:0:1:1     Link Name                       [Harrington]
FF02:0:0:0:0:0:1:2     All-dhcp-agents              [Bound,Perkins]

FF02:0:0:0:0:1:FFXX:XXXX     Solicited-Node Address       [ADDARCH]

2.3 Site-Local Scope 🏑

FF05:0:0:0:0:0:0:2       All Routers Address              [ADDARCH]

FF05:0:0:0:0:0:1:3       All-dhcp-servers           [Bound,Perkins]
FF05:0:0:0:0:0:1:4       All-dhcp-relays            [Bound,Perkins]
FF05:0:0:0:0:0:1:1000    Service Location                 [RFC2165]
 -FF05:0:0:0:0:0:1:13FF

3.0 All Scope Multicast Addresses 🌈

These permanently assigned multicast addresses are valid over all scope ranges, no cap. You can spot them by the "X" in the scope field, which stands for any legal scope value. ✨

Also, as [ADDARCH] defines, IPv6 multicast addresses that only differ in scope are actually different groups. So nodes must join each group individually. That's a big deal, bestie, so don't skip it! πŸ‘‘

The IPv6 multicast addresses with variable scope are as follows: πŸ’œ

FF0X:0:0:0:0:0:0:0     Reserved Multicast Address         [ADDARCH]

FF0X:0:0:0:0:0:0:100   VMTP Managers Group           [RFC1045,DRC3]
FF0X:0:0:0:0:0:0:101   Network Time Protocol (NTP)   [RFC1119,DLM1]
FF0X:0:0:0:0:0:0:102   SGI-Dogfight                           [AXC]
FF0X:0:0:0:0:0:0:103   Rwhod                                  [SXD]
FF0X:0:0:0:0:0:0:104   VNP                                   [DRC3]
FF0X:0:0:0:0:0:0:105   Artificial Horizons - Aviator          [BXF]
FF0X:0:0:0:0:0:0:106   NSS - Name Service Server             [BXS2]
FF0X:0:0:0:0:0:0:107   AUDIONEWS - Audio News Multicast      [MXF2]
FF0X:0:0:0:0:0:0:108   SUN NIS+ Information Service          [CXM3]
FF0X:0:0:0:0:0:0:109   MTP Multicast Transport Protocol       [SXA]
FF0X:0:0:0:0:0:0:10A   IETF-1-LOW-AUDIO                       [SC3]
FF0X:0:0:0:0:0:0:10B   IETF-1-AUDIO                           [SC3]
FF0X:0:0:0:0:0:0:10C   IETF-1-VIDEO                           [SC3]
FF0X:0:0:0:0:0:0:10D   IETF-2-LOW-AUDIO                       [SC3]
FF0X:0:0:0:0:0:0:10E   IETF-2-AUDIO                           [SC3]
FF0X:0:0:0:0:0:0:10F   IETF-2-VIDEO                           [SC3]

FF0X:0:0:0:0:0:0:110   MUSIC-SERVICE             [Guido van Rossum]
FF0X:0:0:0:0:0:0:111   SEANET-TELEMETRY             [Andrew Maffei]
FF0X:0:0:0:0:0:0:112   SEANET-IMAGE                 [Andrew Maffei]
FF0X:0:0:0:0:0:0:113   MLOADD                              [Braden]
FF0X:0:0:0:0:0:0:114   any private experiment                 [JBP]
FF0X:0:0:0:0:0:0:115   DVMRP on MOSPF                         [Moy]
FF0X:0:0:0:0:0:0:116   SVRLOC                            [Veizades]
FF0X:0:0:0:0:0:0:117   XINGTV                      <hgxing@aol.com>
FF0X:0:0:0:0:0:0:118   microsoft-ds         <arnoldm@microsoft.com>
FF0X:0:0:0:0:0:0:119   nbc-pro           <bloomer@birch.crd.ge.com>
FF0X:0:0:0:0:0:0:11A   nbc-pfn           <bloomer@birch.crd.ge.com>
FF0X:0:0:0:0:0:0:11B   lmsc-calren-1                         [Uang]
FF0X:0:0:0:0:0:0:11C   lmsc-calren-2                         [Uang]
FF0X:0:0:0:0:0:0:11D   lmsc-calren-3                         [Uang]
FF0X:0:0:0:0:0:0:11E   lmsc-calren-4                         [Uang]
FF0X:0:0:0:0:0:0:11F   ampr-info                          [Janssen]

FF0X:0:0:0:0:0:0:120   mtrace                              [Casner]
FF0X:0:0:0:0:0:0:121   RSVP-encap-1                        [Braden]
FF0X:0:0:0:0:0:0:122   RSVP-encap-2                        [Braden]
FF0X:0:0:0:0:0:0:123   SVRLOC-DA                         [Veizades]
FF0X:0:0:0:0:0:0:124   rln-server                            [Kean]
FF0X:0:0:0:0:0:0:125   proshare-mc                          [Lewis]
FF0X:0:0:0:0:0:0:126   dantz                               [Yackle]
FF0X:0:0:0:0:0:0:127   cisco-rp-announce                [Farinacci]
FF0X:0:0:0:0:0:0:128   cisco-rp-discovery               [Farinacci]
FF0X:0:0:0:0:0:0:129   gatekeeper                            [Toga]
FF0X:0:0:0:0:0:0:12A   iberiagames                        [Marocho]
FF0X:0:0:0:0:0:0:201  "rwho" Group (BSD) (unofficial)         [JBP]
FF0X:0:0:0:0:0:0:202   SUN RPC PMAPPROC_CALLIT               [BXE1]

FF0X:0:0:0:0:0:2:0000
 -FF0X:0:0:0:0:0:2:7FFD  Multimedia Conference Calls          [SC3]
FF0X:0:0:0:0:0:2:7FFE    SAPv1 Announcements                  [SC3]
FF0X:0:0:0:0:0:2:7FFF    SAPv0 Announcements (deprecated)     [SC3]
FF0X:0:0:0:0:0:2:8000
 -FF0X:0:0:0:0:0:2:FFFF  SAP Dynamic Assignments              [SC3]

Part 2 is where the References, the People list, the Security Considerations, and the Authors' Addresses live. Stay tuned, bestie πŸ§šπŸ’œ

Copyright (C) The Internet Society (1998). All Rights Reserved. πŸŽ€

Okay bestie, this is the legal bit, so pay attention 🧐 Anyone can copy this document and share it with other people, and they can translate it too. They can also write derivative works that comment on or explain it, or help people implement it, and publish and distribute those in whole or in part with no restrictions at all ✨ The one catch is that the above copyright notice and this paragraph have to stay on every copy and every derivative work 🫢

The document itself is a different story πŸ™… You can't modify it in any way, like removing the copyright notice or the references to the Internet Society or other Internet organizations. There are two exceptions: you can do it when you're developing Internet standards, but then the copyright procedures in the Internet Standards process must be followed, or when you need to translate it into a language other than English 🌈

The permissions I just listed are perpetual, which means the Internet Society or its successors or assigns will never revoke them πŸ’œ Forever and ever 😭

Now the serious part πŸ’€ This document and the information in it are provided "AS IS", and the Internet Society and the Internet Engineering Task Force are not making any promises here. They disclaim all warranties, express or implied, including any warranty that using the information won't infringe any rights, and any implied warranties of merchantability or fitness for a particular purpose πŸ₯Ί

THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
πŸ“¦ where this page comes from