IPv6 Multicast Address Scopes
draft-ietf-6man-multicast-scopes-02
| The information below is for an old version of the document |
| Document |
Type |
|
Active Internet-Draft (6man WG)
|
|
Last updated |
|
2013-11-12
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
pdf
htmlized (tools)
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
WG Document
|
|
Document shepherd |
|
None
|
| IESG |
IESG state |
|
I-D Exists
|
|
Consensus Boilerplate |
|
Unknown
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Internet Engineering Task Force R. Droms
Internet-Draft Cisco
Updates: RFC 4007, RFC 4291 (if approved) November 11, 2013
Intended status: Standards Track
Expires: May 15, 2014
IPv6 Multicast Address Scopes
draft-ietf-6man-multicast-scopes-02.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.
Copyright Notice
Copyright (c) 2013 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.
1. Definition of IPv6 Multicast Address Scopes (Updates RFC 4291)
Droms Expires May 15, 2014 [Page 1]
Internet-Draft IPv6 Multicast Address Scopes November 2013
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
"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
The following change is applied to section 2.7 of RFC 4291:
OLD:
Droms Expires May 15, 2014 [Page 2]
Internet-Draft IPv6 Multicast Address Scopes November 2013
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 or other, non-multicast related configuration.
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 scope is 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 configured automatically,
while the zones of larger scopes are configured manually,
care must be taken in the definition of those larger scopes
to ensure that inclusion contraint is met.
2. 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.
Section 4 gives the definition of scop 3 for IEEE 802.15.4
[IEEE802.15.4] networks.
3. Definition of automatic and administratively configured scopes
(updates RFC 4007)
Show full document text