--- 1/draft-ietf-6man-multicast-scopes-02.txt 2014-02-13 16:14:32.968747790 -0800 +++ 2/draft-ietf-6man-multicast-scopes-03.txt 2014-02-13 16:14:32.984748176 -0800 @@ -1,44 +1,44 @@ Internet Engineering Task Force R. Droms Internet-Draft Cisco -Updates: RFC 4007, RFC 4291 (if approved) November 11, 2013 +Updates: RFC 4007, RFC 4291 (if approved) February 14, 2014 Intended status: Standards Track -Expires: May 15, 2014 +Expires: August 18, 2014 IPv6 Multicast Address Scopes - draft-ietf-6man-multicast-scopes-02.txt + draft-ietf-6man-multicast-scopes-03.txt Abstract This document updates the definitions of IPv6 multicast scopes. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at http://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any 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 May 15, 2014. + This Internet-Draft will expire on August 18, 2014. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + 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 @@ -49,51 +50,40 @@ used to limit the scope of the multicast group." scop 3 is defined as "reserved" in RFC 4291. The multicast protocol specification in draft-ietf-roll-trickle-mcast [I-D.ietf-roll-trickle-mcast] desires to use multicast scop 3 for transport of multicast traffic scoped to a network of nodes connected in a mesh. The use of this scop value is to accommodate a multicast scope that is greater than Link-Local but is also automatically determined by the network architecture. The following table updates the definitions in RFC 4291: - 0 reserved - - 1 Interface-Local scope - - 2 Link-Local scope - - 3 Realm-Local scope - - 4 Admin-Local scope - - 5 Site-Local scope - - 6 (unassigned) - - 7 (unassigned) - - 8 Organization-Local scope - - 9 (unassigned) - - A (unassigned) - - B (unassigned) - - C (unassigned) - - D (unassigned) - - E Global scope - - F reserved + +------+--------------------------+ + | scop | NAME | + +------+--------------------------+ + | 0 | reserved | + | 1 | Interface | + | 2 | Link-Local scope | + | 3 | Realm-Local scope | + | 4 | Admin-Local scope | + | 5 | Site-Local scope | + | 6 | (unassigned) | + | 7 | (unassigned) | + | 8 | Organization-Local scope | + | 9 | (unassigned) | + | A | (unassigned) | + | B | (unassigned) | + | C | (unassigned) | + | D | (unassigned) | + | E | Global scope | + | F | reserved | + +------+--------------------------+ The following change is applied to section 2.7 of RFC 4291: 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. @@ -138,64 +128,65 @@ 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]. + addressing architecture [RFC4291] and updated by this document. 4. Definition of Realm-Local Scope for IEEE 802.15.4 When used in an IP-over-IEEE802.15.4 network, "scop 3" is defined to include all interfaces sharing a PAN ID. 5. IANA Considerations IANA is asked to establish a sub-registry titled "IPv6 Multicast Address Scopes" in the existing "Internet Protocol version 6 (IPv6) - Multicast Address Allocations" registry. The "IPv6 Multicast Address - Scopes" is to be populated with the scope values given in section 1, - with a note associated with scope 3 listing all RFCs that define + Multicast Address Allocations" registry. The new registry is to be + populated with the scope values given in section 1. New definitions + for scop values will be made with "IETF Review" policy. The registry + will have a note associated with scope 3 listing all RFCs that define Realm-Local scoping rules that use scope 3. 6. Acknowledgments Robert Cragie, Kerry Lynn, Jinmei Tatuya, Dave Thaler and Stig Venaas all contributed text and/or review to ensure that the updates to RFC 4007 and RFC 4291 are correct 7. Security Considerations - This document has no security considerations beyond those in RFC 4291 - [RFC4291]. + This document has no security considerations beyond those in RFC 4007 + [RFC4007] and RFC 4291 [RFC4291]. 8. References 8.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. 8.2. Informative References [I-D.ietf-roll-trickle-mcast] Hui, J. and R. Kelsey, "Multicast Protocol for Low power and Lossy Networks (MPL)", draft-ietf-roll-trickle- - mcast-05 (work in progress), August 2013. + mcast-06 (work in progress), January 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 for Low-Rate Wireless Personal Area Networks (WPANs)", October 2006.