网页
综合
更新时间 2002-09-03 00:00:00
RFC 3306: Unicast-Prefix-based IPv6 Multicast Addresses | RFC Editor
自动蜘蛛
www.iana.org
正文约 6000 字
Skip to content Primary navigationThe RFC SeriesFor AuthorsAbout UsHomeRFC 3306 View as: Plain Text, Compact HTML Info RFC 3306: Unicast-Prefix-based IPv6 Multicast AddressesIPv6multicastSeptember 2002. B. Haberman, D. ThalerProposed StandardSubscribe10 subscribed Add to Set Read aloud This RFC was updated, see RFC 3956, RFC 4489, RFC 7371.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| +-+-+-+-+ o P = 0 indicates a multicast address that is not assigned based on the network prefix. This indicates a multicast address as defined in [ADDRARCH]. o P = 1 indicates a multicast address that is assigned based on the network prefix. o If P = 1, T MUST be set to 1, otherwise the setting of the T bit is defined in Section 2.7 of [ADDRARCH]. The reserved field MUST be zero. plen indicates the actual number of bits in the network prefix field that identify the subnet when P = 1. network prefix identifies the network prefix of the unicast subnet owning the multicast address. If P = 1, this field contains the unicast network prefix assigned to the domain owning, or allocating, the multicast address. All non-significant bits of the network prefix field SHOULD be zero. It should be noted that the Interface Identifier requirements in Section 2.5.1 of [ADDRARCH] effectively restrict the length of the unicast prefix to 64 bits, hence the network prefix portion of the multicast address will be at most 64 bits. Group ID is set based on the guidelines outlined in [IPV6 GID]. The scope of the unicast-prefix based multicast address MUST NOT exceed the scope of the unicast prefix embedded in the multicast address. Haberman & Thaler Standards Track [Page 3] RFC 3306 Unicast-Prefix-based IPv6 Multicast August 2002 5. Address Lifetime The lifetime of a unicast prefix-based multicast address SHOULD NOT exceed the Valid Lifetime field in the Prefix Information option, corresponding to the unicast prefix being used, contained in the Neighbor Discovery Router Advertisement message [RFC 2461]. The lifetime of the multicast address is needed to support the Abstract API for Multicast Address Allocation [RFC 2771]. It should be noted that the unicast prefix's Valid Lifetime i
本页为82搜索生成的网页快照,内容来自站内索引;演示数据的原文链接仅作示例。