IPv6 Multicast Address Scopes
draft-droms-6man-multicast-scopes-00
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
The information below is for an old version of the document.
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Expired".
|
|
|---|---|---|---|
| Author | Ralph Droms | ||
| Last updated | 2013-05-22 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-droms-6man-multicast-scopes-00
Internet Engineering Task Force R. Droms
Internet-Draft Cisco
Updates: RFC 4291 (if approved) May 22, 2013
Intended status: Standards Track
Expires: November 23, 2013
IPv6 Multicast Address Scopes
draft-droms-6man-multicast-scopes-00.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 November 23, 2013.
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
Droms Expires November 23, 2013 [Page 1]
Internet-Draft IPv6 Multicast Address Scopes May 2013
RFC 4291 [RFC4291] defines values and semantics for the scope field
in IPv6 multicast addresses. The following table updates those
definitions:
0 reserved
1 Interface-Local scope
2 Link-Local scope
3 Network-Specific scope, greater than Link-Local scope, defined
automatically from the network topology
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
2. Definition of Network-Specific scopes
The definition of any Network-Specific 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 Network-Specific scope will
be listed in the IANA "IPv6 Multicast Address Scopes" registry.
Droms Expires November 23, 2013 [Page 2]
Internet-Draft IPv6 Multicast Address Scopes May 2013
3. 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
Network-Specific scoping rules that use scope 3.
4. Security Considerations
This document has no security considerations beyond those in RFC 4291
[RFC4291].
5. Normative References
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006.
Author's Address
Ralph Droms
Cisco
1414 Massachusetts Avenue
Boxborough, MA 01719
US
Phone: +1 978 936 1674
Email: rdroms@cisco.com
Droms Expires November 23, 2013 [Page 3]