IPv6 Multicast Address Scopes
draft-ietf-6man-multicast-scopes-05

The information below is for an old version of the document
Document Type Active Internet-Draft (6man WG)
Last updated 2014-06-03 (latest revision 2014-05-16)
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html 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 IESG Evaluation
Consensus Boilerplate Unknown
Telechat date
Needs a YES. Needs 8 more YES or NO OBJECTION positions to pass.
Responsible AD Brian Haberman
Send notices to 6man-chairs@tools.ietf.org, draft-ietf-6man-multicast-scopes@tools.ietf.org
IANA IANA review state IANA - Not OK
IANA action state None
Internet Engineering Task Force                                 R. Droms
Internet-Draft                                                     Cisco
Updates: 4007, 4291 (if approved)                           May 16, 2014
Intended status: Standards Track
Expires: November 17, 2014

                     IPv6 Multicast Address Scopes
                draft-ietf-6man-multicast-scopes-05.txt

Abstract

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

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 17, 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.

Droms                   Expires November 17, 2014               [Page 1]
Internet-Draft        IPv6 Multicast Address Scopes             May 2014

   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
   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.

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

   The following table updates the definitions in RFC 4291:

Droms                   Expires November 17, 2014               [Page 2]
Internet-Draft        IPv6 Multicast Address Scopes             May 2014

      +------+--------------------------+
      | scop | NAME                     |
      +------+--------------------------+
      |  0   | reserved                 |
      |  1   | Interface                |
      |  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:

Droms                   Expires November 17, 2014               [Page 3]
Internet-Draft        IPv6 Multicast Address Scopes             May 2014

   OLD:

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