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

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

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.

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.