Unicast-Prefix-based IPv6 Multicast Addresses
RFC 3306

Document Type RFC - Proposed Standard (September 2002; No errata)
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html
Stream WG state (None)
Consensus Unknown
Document shepherd No shepherd assigned
IESG IESG state RFC 3306 (Proposed Standard)
Telechat date
Responsible AD Allison Mankin
IESG note After a lot of effort by IANA/Thomas, this was
published as RFC 3306 2002-09-04 [note from Allison]
Responsible: Finished
Send notices to <bob.hinden@nokia.com>, <mrw@windriver.com>
Network Working Group                                        B. Haberman
Request for Comments: 3306                                    Consultant
Category: Standards Track                                      D. Thaler
                                                               Microsoft
                                                             August 2002

             Unicast-Prefix-based IPv6 Multicast Addresses

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This specification defines an extension to the multicast addressing
   architecture of the IP Version 6 protocol.  The extension presented
   in this document allows for unicast-prefix-based allocation of
   multicast addresses.  By delegating multicast addresses at the same
   time as unicast prefixes, network operators will be able to identify
   their multicast addresses without needing to run an inter-domain
   allocation protocol.

Table of Contents

   1. Introduction....................................................2
   2. Motivation......................................................2
   3. Terminology.....................................................2
   4. Multicast Address Format........................................2
   5. Address Lifetime................................................4
   6. Source-Specific Multicast Addresses.............................4
   7. Examples........................................................4
   8. Security Considerations.........................................5
   9. References......................................................5
   Author's Address...................................................6
   Full Copyright Statement...........................................7

Haberman & Thaler           Standards Track                     [Page 1]
RFC 3306          Unicast-Prefix-based IPv6 Multicast        August 2002

1. Introduction

   This document specifies an extension to the multicast portion of the
   IPv6 addressing architecture [ADDRARCH].  The current architecture
   does not contain any built-in support for dynamic address allocation.
   This proposal introduces encoded information in the multicast address
   to allow for dynamic allocation of IPv6 multicast addresses and IPv6
   source-specific multicast addresses.

2. Motivation

   The current IPv4 multicast address allocation architecture [RFC 2908]
   is based on a multi-layered, multi-protocol system.  The goal of this
   proposal is to reduce the number of protocols that need to be
   deployed in order to get dynamic multicast address allocation.

   The use of unicast prefix-based multicast address allocation will, at
   a minimum, remove the need to run the Multicast Address Allocation
   Protocol (AAP) [AAP WORK] and the Multicast Address-Set Claim (MASC)
   Protocol [RFC 2909].

3. Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC 2119].

4. Multicast Address Format

   Section 2.7 of [ADDRARCH] defines the following operational format of
   IPv6 multicast addresses:

      |    8   |  4 |  4 |                     112                     |
      +--------+----+----+---------------------------------------------+
      |11111111|flgs|scop|                  group ID                   |
      +--------+----+----+---------------------------------------------+

Haberman & Thaler           Standards Track                     [Page 2]
RFC 3306          Unicast-Prefix-based IPv6 Multicast        August 2002

   This document introduces a new format that incorporates unicast
   prefix information in the multicast address.  The following
   illustrates the new format:

      |   8    |  4 |  4 |   8    |    8   |       64       |    32    |
      +--------+----+----+--------+--------+----------------+----------+
      |11111111|flgs|scop|reserved|  plen  | network prefix | group ID |
      +--------+----+----+--------+--------+----------------+----------+

                                   +-+-+-+-+
   flgs is a set of 4 flags:       |0|0|P|T|
Show full document text