IPv6 Multicast Address Scopes
RFC 7346

Document Type RFC - Proposed Standard (August 2014; Errata)
Updates RFC 4291, RFC 4007
Author Ralph Droms 
Last updated 2020-07-25
Stream IETF
Formats plain text html pdf htmlized bibtex
Stream WG state Submitted to IESG for Publication
Document shepherd Ole Trøan
Shepherd write-up Show (last changed 2014-05-05)
IESG IESG state RFC 7346 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Brian Haberman
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state RFC-Ed-Ack
Internet Engineering Task Force (IETF)                          R. Droms
Request for Comments: 7346                                         Cisco
Updates: 4007, 4291                                          August 2014
Category: Standards Track
ISSN: 2070-1721

                     IPv6 Multicast Address Scopes


   This document updates the definitions of IPv6 multicast scopes and
   therefore updates RFCs 4007 and 4291.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at

Droms                        Standards Track                    [Page 1]
RFC 7346              IPv6 Multicast Address Scopes          August 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
   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.

   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" as "a 4-bit multicast scope value
   used to limit the scope of the multicast group" and defines "scop 3"
   as "reserved".  The multicast protocol specification in [MPL] desires
   to use multicast scop 3 to transport multicast traffic scoped to a
   network of nodes connected in a mesh.  This scop value is used to
   accommodate a multicast scope that is greater than Link-Local but is
   also automatically determined by the network architecture.

Droms                        Standards Track                    [Page 2]
RFC 7346              IPv6 Multicast Address Scopes          August 2014

2.  Definition of IPv6 Multicast Address Scopes (Updates RFC 4291)

   The following table updates the definitions in [RFC4291]:

      | scop | NAME                     | REFERENCE               |
      |  0   | Reserved                 | [RFC4291], RFC 7346     |
      |  1   | Interface-Local scope    | [RFC4291], RFC 7346     |
      |  2   | Link-Local scope         | [RFC4291], RFC 7346     |
      |  3   | Realm-Local scope        | [RFC4291], RFC 7346     |
      |  4   | Admin-Local scope        | [RFC4291], RFC 7346     |
      |  5   | Site-Local scope         | [RFC4291], RFC 7346     |
      |  6   | Unassigned               |                         |
      |  7   | Unassigned               |                         |
      |  8   | Organization-Local scope | [RFC4291], RFC 7346     |
      |  9   | Unassigned               |                         |
      |  A   | Unassigned               |                         |
      |  B   | Unassigned               |                         |
      |  C   | Unassigned               |                         |
      |  D   | Unassigned               |                         |
      |  E   | Global scope             | [RFC4291], RFC 7346     |
      |  F   | Reserved                 | [RFC4291], RFC 7346     |

   The following change is applied to Section 2.7 of [RFC4291].


      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
Show full document text