Internet Engineering Task Force (IETF) R. DromsInternet-DraftRequest for Comments: 7346 Cisco Updates: 4007, 4291(if approved) June 12,August 2014Intended status:Category: Standards TrackExpires: December 14, 2014ISSN: 2070-1721 IPv6 Multicast Address Scopesdraft-ietf-6man-multicast-scopes-07.txtAbstract This document updates the definitions of IPv6 multicastscopes. This documentscopes and therefore updatesRFCRFCs 4007 andRFC 42914291. Status of This Memo ThisInternet-Draftissubmitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documentsan Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF).Note that other groups may also distribute working documents as Internet-Drafts. The listIt represents the consensus ofcurrent Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents validthe IETF community. It has received public review and has been approved fora maximumpublication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 ofsix monthsRFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may beupdated, replaced, or obsoleted by other documentsobtained atany time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on December 14, 2014.http://www.rfc-editor.org/info/rfc7346. Copyright Notice Copyright (c) 2014 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://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. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. 1. Introduction RFC 4291 [RFC4291] defines"scop is a"scop" as "a 4-bit multicast scope value used to limit the scope of the multicastgroup." scop 3 is definedgroup" and defines "scop 3" as"reserved" in RFC 4291."reserved". The multicast protocol specification indraft-ietf-roll-trickle-mcast [I-D.ietf-roll-trickle-mcast][MPL] desires to use multicast scop 3forto transportofmulticast traffic scoped to a network of nodes connected in a mesh.The use of thisThis scop value is used to accommodate a multicast scope that is greater than Link-Local but is also automatically determined by the network architecture. 2. Definition of IPv6 Multicast Address Scopes (Updates RFC 4291) The following table updates the definitions inRFC 4291:[RFC4291]: +------+--------------------------+-------------------------+ | scop | NAME | REFERENCE | +------+--------------------------+-------------------------+ | 0 | Reserved |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | | 1 | Interface-Local scope |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | | 2 | Link-Local scope |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | | 3 | Realm-Local scope |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | | 4 | Admin-Local scope |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | | 5 | Site-Local scope |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | | 6 | Unassigned | | | 7 | Unassigned | | | 8 | Organization-Local scope |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | | 9 | Unassigned | | | A | Unassigned | | | B | Unassigned | | | C | Unassigned | | | D | Unassigned | | | E | Global scope |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | | F | Reserved |[RFC4291],[ RFC-to-be ][RFC4291], RFC 7346 | +------+--------------------------+-------------------------+ The following change is applied tosectionSection 2.7 ofRFC 4291:[RFC4291]. OLD: Admin-Local scope is the smallest scope that must be administratively configured, i.e., not automatically derived from physical connectivity or other, non-multicast-related configuration. NEW: Interface-Local, Link-Local, and Realm-Local scope boundaries are automatically derived from physical connectivity orother, non-multicast related configuration.other non- multicast-related configurations. Global scope has no boundary. The boundaries of all other non-reserved scopes of Admin-Local or larger are administratively configured. For reserved scopes, the way of configuring their boundaries will be defined when the semantics of the scopeisare defined. According to RFC 4007 [RFC4007], the zone of a Realm-Local scope must fall within zones of larger scope. Because the zone of a Realm-Local scope is configuredautomatically,automatically while the zones of larger scopes are configured manually, care must be taken in the definition of those larger scopes to ensure that the inclusion constraint is met. Realm-Local scopes created by different network technologies are considered to be independent and will have different zone indices (seeRFC 4007, section 6).Section 6 of [RFC4007]). A router with interfaces on links using different network technologies does not forward traffic between the Realm-Local multicast scopes defined by those technologies. 3. Definition of Realm-LocalscopesScopes The definition of any Realm-Local scope for a particular network technology should be published in an RFC. For example, such a scope definition would be appropriate for publication in an "IPv6-over-foo" RFC. Any RFCs that include the definition of a Realm-Local scope will be added to the IANA'IPv6"IPv6 Multicast AddressScopes'Scopes" registry under the Realm-Local scope entry, and those specifications must include such a request in their IANA Considerations. Section 5 of this document gives the definition of scop 3 for IEEE 802.15.4 [IEEE802.15.4] networks. 4. Definition ofautomaticAutomatic andadministratively configured scopes (updatesAdministratively Configured Scopes (Updates RFC 4007) Section 5 of RFC 4007 [RFC4007] andsectionSection 2.7 of RFC 4291 [RFC4291] disagreeabouton the way in which multicastscopescop 3 is configured. To resolve that disagreement,changethe last bullet in the list insectionSection 5 ofRFC 4007[RFC4007] is upated as follows: OLD: o The boundaries of zones of a scope other than interface-local, link-local, and global must be defined and configured by network administrators. NEW: o The boundaries of zones of a scope are defined by the IPv6 addressing architecture [RFC4291] and updated by[RFC-to-be].RFC 7346. 5. Definition of Realm-Local Scope for IEEE 802.15.4 When used in an IP-over-IEEE802.15.4 network,"scop 3"scop 3 is defined to include all interfaces sharing aPAN ID.Personal Area Network Identifier (PAN ID). 6. IANA Considerations IANAis requested to establishhas established a sub-registry titled "IPv6 Multicast Address Scopes" in the existing"Internet Protocol version 6 (IPv6)"IPv6 Multicast AddressAllocations" registry.Space Registry". The new registryis to behas been populated with thescopescop values given in Section 2. New definitions for scop values will be madewithfollowing the "IETF Review"policy.policy [RFC5226]. For each future RFC that defines a Realm-Local scope for new network technologies (scop 3), IANAis requested towill add a reference to theRealm-Local scope entry (scop 3)defining document in the "IPv6 Multicast Address Scopes"registry for each future RFC that defines a Realm-Local scope for new network technologies.registry. Such RFCs are expected to make an explicit request to IANA for inclusion in the registry. IANAis requested to includehas included a notetoon the top of the "IPv6 Multicast Address Scopes" registry: The definition of any Realm-Local scope for a particular network technology should be published in an RFC. For example, such a scope definition would be appropriate for publication in an'IPv6-over-foo''IPv6- over-foo' RFC. Any RFCs that define a Realm-Local scope will be listed in this registry as an additional reference in the Realm-Local scope entry. Such RFCs are expected to make an explicit request to IANA for inclusion in this registry. 7. Acknowledgments Robert Cragie, Kerry Lynn, Jinmei Tatuya, DaveThalerThaler, and Stig Venaas all contributed text and/or review to ensure that the updates to RFC 4007 and RFC 4291 are correct. 8. Security Considerations This document has no security considerations beyond those in RFC 4007 [RFC4007] and RFC 4291 [RFC4291]. 9. References 9.1. Normative References [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, March 2005. [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing Architecture", RFC 4291, February 2006. 9.2. Informative References[I-D.ietf-roll-trickle-mcast][IEEE802.15.4] IEEE Computer Society, "IEEE Std. 802.15.4-2006", October 2006. [MPL] Hui, J. and R. Kelsey, "Multicast Protocol for Low power and Lossy Networks (MPL)",draft-ietf-roll-trickle- mcast-09 (workWork inprogress),Progress, April 2014.[IEEE802.15.4] IEEE Std 802.15.4-2006, "IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements; Part 15.4: Wireless Medium Access Control (MAC) and Physical Layer (PHY) Specifications[RFC5226] Narten, T. and H. Alvestrand, "Guidelines forLow-Rate Wireless Personal Area Networks (WPANs)", October 2006.Writing an IANA Considerations Section in RFCs", BCP 26, RFC 5226, May 2008. Author's Address Ralph Droms Cisco 1414 Massachusetts Avenue Boxborough, MA 01719 USA Phone: +1 978 936 1674Email:EMail: rdroms.ietf@gmail.com