idnits 2.17.1 draft-ietf-ipngwg-multicast-assgn-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-03-28) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. == There are 3 instances of lines with non-RFC3849-compliant IPv6 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'JBP' is mentioned on line 273, but not defined == Missing Reference: 'JXM1' is mentioned on line 275, but not defined == Missing Reference: 'KS14' is mentioned on line 281, but not defined == Missing Reference: 'GSM11' is mentioned on line 265, but not defined == Missing Reference: 'Farinacci' is mentioned on line 263, but not defined == Missing Reference: 'Braden' is mentioned on line 235, but not defined == Missing Reference: 'Harrington' is mentioned on line 76, but not defined == Missing Reference: 'DRC3' is mentioned on line 259, but not defined == Missing Reference: 'DLM1' is mentioned on line 257, but not defined == Missing Reference: 'AXC' is mentioned on line 233, but not defined == Missing Reference: 'SXD' is mentioned on line 307, but not defined == Missing Reference: 'BXF' is mentioned on line 245, but not defined == Missing Reference: 'BXS2' is mentioned on line 249, but not defined == Missing Reference: 'MXF2' is mentioned on line 295, but not defined == Missing Reference: 'CXM3' is mentioned on line 253, but not defined == Missing Reference: 'SXA' is mentioned on line 305, but not defined == Missing Reference: 'SC3' is mentioned on line 299, but not defined == Missing Reference: 'Veizades' is mentioned on line 315, but not defined == Missing Reference: 'Uang' is mentioned on line 313, but not defined == Missing Reference: 'Janssen' is mentioned on line 271, but not defined == Missing Reference: 'Casner' is mentioned on line 251, but not defined == Missing Reference: 'Kean' is mentioned on line 279, but not defined == Missing Reference: 'Lewis' is mentioned on line 285, but not defined == Missing Reference: 'Yackle' is mentioned on line 317, but not defined == Missing Reference: 'Toga' is mentioned on line 311, but not defined == Missing Reference: 'Marocho' is mentioned on line 140, but not defined == Missing Reference: 'BXE1' is mentioned on line 243, but not defined == Missing Reference: 'Bressler' is mentioned on line 239, but not defined == Missing Reference: 'DXS3' is mentioned on line 261, but not defined == Missing Reference: 'IANA' is mentioned on line 269, but not defined == Missing Reference: 'Lee' is mentioned on line 283, but not defined == Missing Reference: 'Malamud' is mentioned on line 287, but not defined == Missing Reference: 'Marohco' is mentioned on line 291, but not defined == Missing Reference: 'Simpson' is mentioned on line 301, but not defined == Unused Reference: 'RFC1887' is defined on line 185, but no explicit reference was found in the text == Unused Reference: 'AUTORFC' is defined on line 191, but no explicit reference was found in the text == Unused Reference: 'RFC1112' is defined on line 202, but no explicit reference was found in the text ** Downref: Normative reference to an Informational RFC: RFC 1887 ** Obsolete normative reference: RFC 1884 (Obsoleted by RFC 2373) -- Possible downref: Non-RFC (?) normative reference: ref. 'AUTORFC' ** Downref: Normative reference to an Experimental RFC: RFC 1045 ** Downref: Normative reference to an Experimental RFC: RFC 1075 ** Obsolete normative reference: RFC 1119 (Obsoleted by RFC 1305) ** Obsolete normative reference: RFC 1190 (Obsoleted by RFC 1819) ** Obsolete normative reference: RFC 1583 (Obsoleted by RFC 2178) ** Obsolete normative reference: RFC 1723 (Obsoleted by RFC 2453) Summary: 17 errors (**), 0 flaws (~~), 39 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT R. Hinden, Ipsilon Networks 2 October 11, 1996 S. Deering, Xerox PARC 3 Expire in six months 5 IPv6 Multicast Address Assignments 7 9 Status of this Memo 11 This document is an Internet Draft. Internet Drafts are working 12 documents of the Internet Engineering Task Force (IETF), its Areas, 13 and its Working Groups. Note that other groups may also distribute 14 working documents as Internet Drafts. 16 Internet Drafts are draft documents valid for a maximum of six 17 months. Internet Drafts may be updated, replaced, or obsoleted by 18 other documents at any time. It is not appropriate to use Internet 19 Drafts as reference material or to cite them other than as a 20 ``working draft'' or ``work in progress.'' 22 Please check the 1id-abstracts.txt listing contained in the internet- 23 drafts Shadow Directories on nic.ddn.mil, nnsc.nsf.net, 24 nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au to learn the 25 current status of any Internet Draft. 27 1.0 Introduction 29 This document defines the initial assignment of IPv6 multicast 30 addresses. It is based on the "RFC-1884 IP Version 6 Addressing 31 Architecture" [RFC1884] and current IPv4 multicast address assignment 32 found in . It adapts the IPv4 assignments that are relevant to IPv6 34 assignments. IPv4 assignments that were not relevant were not 35 converted into IPv6 assignments. Comments are solicited on this 36 conversion. 38 All other IPv6 multicast addresses are reserved. 40 Sections 2 and 3 specify reserved and preassigned IPv6 multicast 41 addresses. Section 4 defines guidelines for assigning new IPv6 42 multicast addresses. 44 INTERNET-DRAFT IPv6 Multicast Address Assignments 11 Oct 96 46 2. Fixed Scope Multicast Addresses 48 These permanently assigned multicast addresses are valid over a 49 specified scope value. 51 2.1 Node Scope 53 FF01:0:0:0:0:0:0:1 All Nodes Address [RFC1884] 54 FF01:0:0:0:0:0:0:2 All Routers Address [RFC1884] 56 2.2 Link Scope 58 FF02:0:0:0:0:0:0:1 All Nodes Address [RFC1884] 59 FF02:0:0:0:0:0:0:2 All Routers Address [RFC1884] 60 FF02:0:0:0:0:0:0:3 Unassigned [JBP] 61 FF02:0:0:0:0:0:0:4 DVMRP Routers [RFC1075,JBP] 62 FF02:0:0:0:0:0:0:5 OSPFIGP [RFC1583,JXM1] 63 FF02:0:0:0:0:0:0:6 OSPFIGP Designated Routers [RFC1583,JXM1] 64 FF02:0:0:0:0:0:0:7 ST Routers [RFC1190,KS14] 65 FF02:0:0:0:0:0:0:8 ST Hosts [RFC1190,KS14] 66 FF02:0:0:0:0:0:0:9 RIP Routers [RFC1723,GSM11] 67 FF02:0:0:0:0:0:0:A IGRP Routers [Farinacci] 68 FF02:0:0:0:0:0:0:B Mobile-Agents [Bill Simpson] 69 FF02:0:0:0:0:0:0:C DHCP Server / Relay Agent [RFC1884] 70 FF02:0:0:0:0:0:0:D All PIM Routers [Farinacci] 71 FF02:0:0:0:0:0:0:E RSVP-ENCAPSULATION [Braden] 73 FF02:0:0:0:0:0:1:1 Link Name [Harrington] 74 FF02:0:0:0:0:0:1:2 All-dhcp-agents [Harrington] 75 FF02:0:0:0:0:0:1:3 All-dhcp-servers [Harrington] 76 FF02:0:0:0:0:0:1:4 All-dhcp-relays [Harrington] 78 FF02:0:0:0:0:1:XXXX:XXXX Solicited-Node Address [RFC1884] 80 3.0 All Scope Multicast Addresses 82 These permanently assigned multicast addresses are valid over all 83 scope ranges. This is shown by an "X" in the scope field of the 84 address that means any legal scope value. 86 Note that, as defined in RFC1884, IPv6 multicast addresses which are 87 only different in scope represent different groups. Nodes must join 88 each group individually. 90 The IPv6 multicast addresses with variable scope are as follows: 92 FF0X:0:0:0:0:0:0:0 Reserved Multicast Address [RFC1884] 94 INTERNET-DRAFT IPv6 Multicast Address Assignments 11 Oct 96 96 FF0X:0:0:0:0:0:0:100 VMTP Managers Group [RFC1045,DRC3] 97 FF0X:0:0:0:0:0:0:101 Network Time Protocol (NTP) [RFC1119,DLM1] 98 FF0X:0:0:0:0:0:0:102 SGI-Dogfight [AXC] 99 FF0X:0:0:0:0:0:0:103 Rwhod [SXD] 100 FF0X:0:0:0:0:0:0:104 VNP [DRC3] 101 FF0X:0:0:0:0:0:0:105 Artificial Horizons - Aviator [BXF] 102 FF0X:0:0:0:0:0:0:106 NSS - Name Service Server [BXS2] 103 FF0X:0:0:0:0:0:0:107 AUDIONEWS - Audio News Multicast [MXF2] 104 FF0X:0:0:0:0:0:0:108 SUN NIS+ Information Service [CXM3] 105 FF0X:0:0:0:0:0:0:109 MTP Multicast Transport Protocol [SXA] 106 FF0X:0:0:0:0:0:0:10A IETF-1-LOW-AUDIO [SC3] 107 FF0X:0:0:0:0:0:0:10B IETF-1-AUDIO [SC3] 108 FF0X:0:0:0:0:0:0:10C IETF-1-VIDEO [SC3] 109 FF0X:0:0:0:0:0:0:10D IETF-2-LOW-AUDIO [SC3] 110 FF0X:0:0:0:0:0:0:10E IETF-2-AUDIO [SC3] 111 FF0X:0:0:0:0:0:0:10F IETF-2-VIDEO [SC3] 113 FF0X:0:0:0:0:0:0:110 MUSIC-SERVICE [Guido van Rossum] 114 FF0X:0:0:0:0:0:0:111 SEANET-TELEMETRY [Andrew Maffei] 115 FF0X:0:0:0:0:0:0:112 SEANET-IMAGE [Andrew Maffei] 116 FF0X:0:0:0:0:0:0:113 MLOADD [Braden] 117 FF0X:0:0:0:0:0:0:114 any private experiment [JBP] 118 FF0X:0:0:0:0:0:0:115 DVMRP on MOSPF [John Moy] 119 FF0X:0:0:0:0:0:0:116 SVRLOC [Veizades] 120 FF0X:0:0:0:0:0:0:117 XINGTV 121 FF0X:0:0:0:0:0:0:118 microsoft-ds 122 FF0X:0:0:0:0:0:0:119 nbc-pro 123 FF0X:0:0:0:0:0:0:11A nbc-pfn 124 FF0X:0:0:0:0:0:0:11B lmsc-calren-1 [Uang] 125 FF0X:0:0:0:0:0:0:11C lmsc-calren-2 [Uang] 126 FF0X:0:0:0:0:0:0:11D lmsc-calren-3 [Uang] 127 FF0X:0:0:0:0:0:0:11E lmsc-calren-4 [Uang] 128 FF0X:0:0:0:0:0:0:11F ampr-info [Janssen] 130 FF0X:0:0:0:0:0:0:120 mtrace [Casner] 131 FF0X:0:0:0:0:0:0:121 RSVP-encap-1 [Braden] 132 FF0X:0:0:0:0:0:0:122 RSVP-encap-2 [Braden] 133 FF0X:0:0:0:0:0:0:123 SVRLOC-DA [Veizades] 134 FF0X:0:0:0:0:0:0:124 rln-server [Kean] 135 FF0X:0:0:0:0:0:0:125 proshare-mc [Lewis] 136 FF0X:0:0:0:0:0:0:126 dantz [Yackle] 137 FF0X:0:0:0:0:0:0:127 cisco-rp-announce [Farinacci] 138 FF0X:0:0:0:0:0:0:128 cisco-rp-discovery [Farinacci] 139 FF0X:0:0:0:0:0:0:129 gatekeeper [Toga] 140 FF0X:0:0:0:0:0:0:12A iberiagames [Marocho] 142 FF0X:0:0:0:0:0:0:201 "rwho" Group (BSD) (unofficial) [JBP] 143 FF0X:0:0:0:0:0:0:202 SUN RPC PMAPPROC_CALLIT [BXE1] 145 INTERNET-DRAFT IPv6 Multicast Address Assignments 11 Oct 96 147 FF0X:0:0:0:0:0:2:0000 148 -FF0X:0:0:0:0:0:2:7FFD Multimedia Conference Calls [SC3] 149 FF0X:0:0:0:0:0:2:7FFE SAPv1 Announcements [SC3] 150 FF0X:0:0:0:0:0:2:7FFF SAPv0 Announcements (deprecated) [SC3] 151 FF0X:0:0:0:0:0:2:8000 152 -FF0X:0:0:0:0:0:2:FFFF SAP Dynamic Assignments [SC3] 154 4.0 Assignment of New IPv6 Multicast Addresses 156 Multicast address as defined in [RFC1884] have the following format: 158 | 8 | 4 | 4 | 112 bits | 159 +------ -+----+----+---------------------------------------------+ 160 |11111111|flgs|scop| group ID | 161 +--------+----+----+---------------------------------------------+ 163 The current approach [RFC1972] to map IPv6 multicast addresses into 164 IEEE 802 MAC addresses takes the low order 32 bits of the IPv6 165 multicast address and uses it to create a MAC address. Groups ID's 166 less than or equal to 32 bits will generate unique MAC addresses. 167 Due to this new IPv6 multicast addresses should be assigned so that 168 the group identifier is always in the low order 32 bits as shown in 169 the following: 171 | 8 | 4 | 4 | 80 bits | 32 bits | 172 +------ -+----+----+---------------------------+-----------------+ 173 |11111111|flgs|scop| reserved must be zero | group ID | 174 +--------+----+----+---------------------------+-----------------+ 176 While this limits the number of permanent IPv6 multicast groups to 177 2^32 this is unlikely to be a limitation in the future. If it 178 becomes necessary to exceed this limit in the future multicast will 179 still work but the processing will be sightly slower. 181 INTERNET-DRAFT IPv6 Multicast Address Assignments 11 Oct 96 183 5.0 References 185 [RFC1887] Rekhter, Y., Li, T., "An Architecture for IPv6 Unicast 186 Address Allocation", RFC-1887, December 1995. 188 [RFC1884] Hinden, R., "IP Version 6 Addressing Architecture", 189 RFC-1884, December 1995. 191 [AUTORFC] Thompson, S., "IPv6 Stateless Address Autoconfiguration", 192 Internet Draft. 194 [RFC1045] Cheriton, D., "VMTP: Versatile Message Transaction Protocol 195 Specification", RFC 1045, Stanford University, February 196 1988. 198 [RFC1075] Waitzman, D., C. Partridge, and S. Deering "Distance Vector 199 Multicast Routing Protocol", RFC-1075, BBN STC, Stanford 200 University, November 1988. 202 [RFC1112] Deering, S., "Host Extensions for IP Multicasting", STD 5, 203 RFC 1112, Stanford University, August 1989. 205 [RFC1119] Mills, D., "Network Time Protocol (Version 1), 206 Specification and Implementation", STD 12, RFC 1119, 207 University of Delaware, July 1988. 209 [RFC1190] Topolcic, C., Editor, "Experimental Internet Stream 210 Protocol, Version 2 (ST-II)", RFC 1190, CIP Working Group, 211 October 1990. 213 [RFC1583] Moy, J., "The OSPF Specification", RFC 1583, Proteon, March 214 1994. 216 [RFC1723] Malkin, G., "RIP Version 2: Carying Additional 217 Information", RFC 1723, Xylogics, November 1994. 219 [RFC1884] Hinden, R., and S. Deering, "IP Version 6 Addressing 220 Architecture", RFC 1884, Ipsilon Networks, Xerox PARC, 221 December 1995. 223 [RFC1972] Crawford, M., "A Method for the Transmission of IPv6 224 Packets over Ethernet Networks", RFC 11972, Fermilab, 225 August 1996. 227 INTERNET-DRAFT IPv6 Multicast Address Assignments 11 Oct 96 229 6. People 231 233 [AXC] Andrew Cherenson 235 [Braden] Bob Braden, , April 1996. 237 [Bob Brenner] 239 [Bressler] David J. Bressler, , April 1996. 241 243 [BXE1] Brendan Eic 245 [BXF] Bruce Factor 247 [Farinacci] Dino Farinacci, , February 1996. 249 [BXS2] Bill Schilit 251 [Casner] Steve Casner, , January 1995. 253 [CXM3] Chuck McManis 255 [Tim Clark] 257 [DLM1] David Mills 259 [DRC3] Dave Cheriton 261 [DXS3] Daniel Steinber 263 [Farinacci] Dino Farinacci, , March 1996. 265 [GSM11] Gary S. Malkin 267 269 [IANA] IANA 271 [Janssen] Rob Janssen, , January 1995. 273 [JBP] Jon Postel 275 [JXM1] Jim Miner 277 INTERNET-DRAFT IPv6 Multicast Address Assignments 11 Oct 96 279 [Kean] Brian Kean, , August 1995. 281 [KS14] 283 [Lee] Choon Lee, , April 1996. 285 [Lewis] Mark Lewis, , October 1995. 287 [Malamud] Carl Malamud, , January 1996. 289 [Andrew Maffei] 291 [Marohco] Jose Luis Marocho, <73374.313@compuserve.com>, July 1996. 293 [John Moy] John Moy 295 [MXF2] Martin Forssen 297 [Guido van Rossum] 299 [SC3] Steve Casner 301 [Simpson] Bill Simpson November 1994. 303 [Joel Snyder] 305 [SXA] Susie Armstrong 307 [SXD] Steve Deering 309 [tynan] Dermot Tynan, , August 1995. 311 [Toga] Jim Toga, , May 1996. 313 [Uang] Yea Uang November 1994. 315 [Veizades] John Veizades, , May 1995. 317 [Yackle] Dotty Yackle, , February 1996. 319 INTERNET-DRAFT IPv6 Multicast Address Assignments 11 Oct 96 321 7.0 Security Considerations 323 Security issues are not discussed in this memo. 325 8.0 Authors' Addresses 327 Robert M. Hinden 328 Ipsilon Networks, Inc. 329 232 Java Way 330 Sunnyvale, CA 94089 331 USA 333 phone: +1 415 990 2000 334 email: hinden@ipsilon.com 336 Stephen E. Deering 337 Xerox Palo Alto Research Center 338 3333 Coyote Hill Road 339 Palo Alto, CA 94304 340 USA 342 phone: +1 415 812 4839 343 email: deering@parc.xerox.com