--- 1/draft-ietf-6man-multicast-scopes-05.txt 2014-06-03 15:14:26.663534598 -0700 +++ 2/draft-ietf-6man-multicast-scopes-06.txt 2014-06-03 15:14:26.679534974 -0700 @@ -1,19 +1,19 @@ Internet Engineering Task Force R. Droms Internet-Draft Cisco -Updates: 4007, 4291 (if approved) May 16, 2014 +Updates: 4007, 4291 (if approved) June 3, 2014 Intended status: Standards Track -Expires: November 17, 2014 +Expires: December 5, 2014 IPv6 Multicast Address Scopes - draft-ietf-6man-multicast-scopes-05.txt + draft-ietf-6man-multicast-scopes-06.txt Abstract This document updates the definitions of IPv6 multicast scopes. This document updates RFC 4007 and RFC 4291 Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. @@ -21,21 +21,21 @@ 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 November 17, 2014. + This Internet-Draft will expire on December 5, 2014. 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 @@ -65,40 +65,40 @@ 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. 2. Definition of IPv6 Multicast Address Scopes (Updates RFC 4291) The following table updates the definitions in RFC 4291: - +------+--------------------------+ - | 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 | - +------+--------------------------+ + +------+--------------------------+--------------------+ + | scop | NAME | REFERENCE | + +------+--------------------------+--------------------+ + | 0 | Reserved | [ RFC-to-be ] | + | 1 | Interface | [ RFC-to-be ] | + | 2 | Link-Local scope | [ RFC-to-be ] | + | 3 | Realm-Local scope | [ RFC-to-be ] | + | 4 | Admin-Local scope | [ RFC-to-be ] | + | 5 | Site-Local scope | [ RFC-to-be ] | + | 6 | Unassigned | | + | 7 | Unassigned | | + | 8 | Organization-Local scope | [ RFC-to-be ] | + | 9 | Unassigned | | + | A | Unassigned | | + | B | Unassigned | | + | C | Unassigned | | + | D | Unassigned | | + | E | Global scope | [ RFC-to-be ] | + | F | Reserved | [ RFC-to-be ] | + +------+--------------------------+--------------------+ 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. @@ -121,21 +121,22 @@ to ensure that inclusion contraint is met. 3. Definition of Realm-Local scopes 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 - listed in the IANA "IPv6 Multicast Address Scopes" registry. + added to the IANA 'IPv6 Multicast Address Scopes' registry under the + Realm-Local scope entry. Section 5 gives the definition of scop 3 for IEEE 802.15.4 [IEEE802.15.4] networks. 4. Definition of automatic and administratively configured scopes (updates RFC 4007) Section 5 of RFC 4007 [RFC4007] and section 2.7 of RFC 4291 disagree about the way in which multicast scope 3 is configured. To resolve that disagreement, change the last bullet in the list in section 5 of @@ -156,23 +157,30 @@ When used in an IP-over-IEEE802.15.4 network, "scop 3" is defined to include all interfaces sharing a PAN ID. 6. 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 new registry is to be populated with the scope values given in Section 2. 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. + for scop values will be made with "IETF Review" policy. IANA will + add a note to the top of this 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' RFC. + + Any RFCs that include the definition of a Realm-Local scope will + be listed in this registry." 7. 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 8. Security Considerations This document has no security considerations beyond those in RFC 4007