draft-ietf-6man-multicast-scopes-03.txt   draft-ietf-6man-multicast-scopes-04.txt 
Internet Engineering Task Force R. Droms Internet Engineering Task Force R. Droms
Internet-Draft Cisco Internet-Draft Cisco
Updates: RFC 4007, RFC 4291 (if approved) February 14, 2014 Updates: 4007, 4291 (if approved) March 27, 2014
Intended status: Standards Track Intended status: Standards Track
Expires: August 18, 2014 Expires: September 28, 2014
IPv6 Multicast Address Scopes IPv6 Multicast Address Scopes
draft-ietf-6man-multicast-scopes-03.txt draft-ietf-6man-multicast-scopes-04.txt
Abstract Abstract
This document updates the definitions of IPv6 multicast scopes. This document updates the definitions of IPv6 multicast scopes. This
document updates RFC 4007 and RFC 4291
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 18, 2014. This Internet-Draft will expire on September 28, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
1. Definition of IPv6 Multicast Address Scopes (Updates RFC 4291) 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 4-bit multicast scope value RFC 4291 [RFC4291] defines "scop is a 4-bit multicast scope value
used to limit the scope of the multicast group." scop 3 is defined as used to limit the scope of the multicast group." scop 3 is defined as
"reserved" in RFC 4291. The multicast protocol specification in "reserved" in RFC 4291. The multicast protocol specification in
draft-ietf-roll-trickle-mcast [I-D.ietf-roll-trickle-mcast] desires draft-ietf-roll-trickle-mcast [I-D.ietf-roll-trickle-mcast] desires
to use multicast scop 3 for transport of multicast traffic scoped to 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 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 is to accommodate a multicast scope that is greater than Link-Local
but is also automatically determined by the network architecture. 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: The following table updates the definitions in RFC 4291:
+------+--------------------------+ +------+--------------------------+
| scop | NAME | | scop | NAME |
+------+--------------------------+ +------+--------------------------+
| 0 | reserved | | 0 | reserved |
| 1 | Interface | | 1 | Interface |
| 2 | Link-Local scope | | 2 | Link-Local scope |
| 3 | Realm-Local scope | | 3 | Realm-Local scope |
| 4 | Admin-Local scope | | 4 | Admin-Local scope |
skipping to change at page 3, line 30 skipping to change at page 4, line 30
of configuring their boundaries will be defined when the of configuring their boundaries will be defined when the
semantics of the scope is defined. semantics of the scope is defined.
According to RFC 4007 [RFC4007], the zone of a Realm-Local According to RFC 4007 [RFC4007], the zone of a Realm-Local
scope must fall within zones of larger scope. Because the scope must fall within zones of larger scope. Because the
zone of a Realm-Local scope is configured automatically, zone of a Realm-Local scope is configured automatically,
while the zones of larger scopes are configured manually, while the zones of larger scopes are configured manually,
care must be taken in the definition of those larger scopes care must be taken in the definition of those larger scopes
to ensure that inclusion contraint is met. to ensure that inclusion contraint is met.
2. Definition of Realm-Local scopes 3. Definition of Realm-Local scopes
The definition of any Realm-Local scope for a particular network The definition of any Realm-Local scope for a particular network
technology should be published in an RFC. For example, such a scope technology should be published in an RFC. For example, such a scope
definition would be appropriate for publication in an "IPv6-over-foo" definition would be appropriate for publication in an "IPv6-over-foo"
RFC. RFC.
Any RFCs that include the definition of a Realm-Local scope will be Any RFCs that include the definition of a Realm-Local scope will be
listed in the IANA "IPv6 Multicast Address Scopes" registry. listed in the IANA "IPv6 Multicast Address Scopes" registry.
Section 4 gives the definition of scop 3 for IEEE 802.15.4 Section 5 gives the definition of scop 3 for IEEE 802.15.4
[IEEE802.15.4] networks. [IEEE802.15.4] networks.
3. Definition of automatic and administratively configured scopes 4. Definition of automatic and administratively configured scopes
(updates RFC 4007) (updates RFC 4007)
Section 5 of RFC 4007 [RFC4007] and section 2.7 of RFC 4291 disagree 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 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 that disagreement, change the last bullet in the list in section 5 of
RFC 4007 as follows: RFC 4007 as follows:
OLD: OLD:
o The boundaries of zones of a scope other than interface-local, o The boundaries of zones of a scope other than interface-local,
link-local, and global must be defined and configured by network link-local, and global must be defined and configured by network
administrators. administrators.
NEW: NEW:
o The boundaries of zones of a scope are defined by the IPv6 o The boundaries of zones of a scope are defined by the IPv6
addressing architecture [RFC4291] and updated by this document. addressing architecture [RFC4291] and updated by this document.
4. Definition of Realm-Local Scope for IEEE 802.15.4 5. 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 When used in an IP-over-IEEE802.15.4 network, "scop 3" is defined to
include all interfaces sharing a PAN ID. include all interfaces sharing a PAN ID.
5. IANA Considerations 6. IANA Considerations
IANA is asked to establish a sub-registry titled "IPv6 Multicast IANA is asked to establish a sub-registry titled "IPv6 Multicast
Address Scopes" in the existing "Internet Protocol version 6 (IPv6) Address Scopes" in the existing "Internet Protocol version 6 (IPv6)
Multicast Address Allocations" registry. The new registry is to be Multicast Address Allocations" registry. The new registry is to be
populated with the scope values given in section 1. New definitions populated with the scope values given in section 1. New definitions
for scop values will be made with "IETF Review" policy. The registry 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 will have a note associated with scope 3 listing all RFCs that define
Realm-Local scoping rules that use scope 3. Realm-Local scoping rules that use scope 3.
6. Acknowledgments 7. Acknowledgments
Robert Cragie, Kerry Lynn, Jinmei Tatuya, Dave Thaler and Stig Venaas Robert Cragie, Kerry Lynn, Jinmei Tatuya, Dave Thaler and Stig Venaas
all contributed text and/or review to ensure that the updates to RFC all contributed text and/or review to ensure that the updates to RFC
4007 and RFC 4291 are correct 4007 and RFC 4291 are correct
7. Security Considerations 8. Security Considerations
This document has no security considerations beyond those in RFC 4007 This document has no security considerations beyond those in RFC 4007
[RFC4007] and RFC 4291 [RFC4291]. [RFC4007] and RFC 4291 [RFC4291].
8. References 9. References
8.1. Normative References 9.1. Normative References
[RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and [RFC4007] Deering, S., Haberman, B., Jinmei, T., Nordmark, E., and
B. Zill, "IPv6 Scoped Address Architecture", RFC 4007, B. Zill, "IPv6 Scoped Address Architecture", RFC 4007,
March 2005. March 2005.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
8.2. Informative References 9.2. Informative References
[I-D.ietf-roll-trickle-mcast] [I-D.ietf-roll-trickle-mcast]
Hui, J. and R. Kelsey, "Multicast Protocol for Low power Hui, J. and R. Kelsey, "Multicast Protocol for Low power
and Lossy Networks (MPL)", draft-ietf-roll-trickle- and Lossy Networks (MPL)", draft-ietf-roll-trickle-
mcast-06 (work in progress), January 2014. mcast-07 (work in progress), February 2014.
[IEEE802.15.4] [IEEE802.15.4]
IEEE Std 802.15.4-2006, "IEEE Standard for Information IEEE Std 802.15.4-2006, "IEEE Standard for Information
technology - Telecommunications and information exchange technology - Telecommunications and information exchange
between systems - Local and metropolitan area networks - between systems - Local and metropolitan area networks -
Specific requirements; Part 15.4: Wireless Medium Access Specific requirements; Part 15.4: Wireless Medium Access
Control (MAC) and Physical Layer (PHY) Specifications for Control (MAC) and Physical Layer (PHY) Specifications for
Low-Rate Wireless Personal Area Networks (WPANs)", October Low-Rate Wireless Personal Area Networks (WPANs)", October
2006. 2006.
Author's Address Author's Address
Ralph Droms Ralph Droms
Cisco Cisco
1414 Massachusetts Avenue 1414 Massachusetts Avenue
Boxborough, MA 01719 Boxborough, MA 01719
US US
Phone: +1 978 936 1674 Phone: +1 978 936 1674
Email: rdroms@cisco.com Email: rdroms.ietf@gmail.com
 End of changes. 19 change blocks. 
17 lines changed or deleted 32 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/