draft-ietf-6man-multicast-addr-arch-update-08.txt   rfc7371.txt 
6man Working Group M. Boucadair Internet Engineering Task Force (IETF) M. Boucadair
Internet-Draft France Telecom Request for Comments: 7371 France Telecom
Updates: 3306,3956,4291 (if approved) S. Venaas Updates: 3306, 3956, 4291 S. Venaas
Intended status: Standards Track Cisco Category: Standards Track Cisco
Expires: February 12, 2015 August 11, 2014 ISSN: 2070-1721 September 2014
Updates to the IPv6 Multicast Addressing Architecture Updates to the IPv6 Multicast Addressing Architecture
draft-ietf-6man-multicast-addr-arch-update-08
Abstract Abstract
This document updates the IPv6 multicast addressing architecture by This document updates the IPv6 multicast addressing architecture by
re-defining the reserved bits as generic flag bits. The document redefining the reserved bits as generic flag bits. The document also
provides also some clarifications related to the use of these flag provides some clarifications related to the use of these flag bits.
bits.
This document updates RFC 3956, RFC 3306 and RFC 4291.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", This document updates RFCs 3956, 3306, and 4291.
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This is an Internet Standards Track document.
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 This document is a product of the Internet Engineering Task Force
and may be updated, replaced, or obsoleted by other documents at any (IETF). It represents the consensus of the IETF community. It has
time. It is inappropriate to use Internet-Drafts as reference received public review and has been approved for publication by the
material or to cite them other than as "work in progress." Internet Engineering Steering Group (IESG). Further information on
Internet Standards is available in Section 2 of RFC 5741.
This Internet-Draft will expire on February 12, 2015. Information about the current status of this document, any errata,
and how to provide feedback on it may be obtained at
http://www.rfc-editor.org/info/rfc7371.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 29 skipping to change at page 2, line 34
modifications of such material outside the IETF Standards Process. modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other it for publication as an RFC or to translate it into languages other
than English. than English.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction ....................................................3
2. Addressing Architecture Update . . . . . . . . . . . . . . . 3 1.1. Requirements Language ......................................3
3. Flag Bits: New Processing Rules . . . . . . . . . . . . . . . 3 2. Addressing Architecture Update ..................................3
4. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Flag Bits: New Processing Rules .................................4
4.1. RFC 3306 . . . . . . . . . . . . . . . . . . . . . . . . 4 4. RFC Updates .....................................................4
4.1.1. Update #1 . . . . . . . . . . . . . . . . . . . . . . 4 4.1. Updates to RFC 3306 ........................................4
4.1.2. Update #2 . . . . . . . . . . . . . . . . . . . . . . 5 4.1.1. Update #1 ...........................................4
4.2. RFC 3956 . . . . . . . . . . . . . . . . . . . . . . . . 6 4.1.2. Update #2 ...........................................6
4.2.1. Update #1 . . . . . . . . . . . . . . . . . . . . . . 6 4.2. Updates to RFC 3956 ........................................6
4.2.2. Update #2 . . . . . . . . . . . . . . . . . . . . . . 7 4.2.1. Update #1 ...........................................6
4.2.3. Update #3 . . . . . . . . . . . . . . . . . . . . . . 8 4.2.2. Update #2 ...........................................7
4.2.4. Update #4 . . . . . . . . . . . . . . . . . . . . . . 8 4.2.3. Update #3 ...........................................8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 4.2.4. Update #4 ...........................................9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9 5. Security Considerations .........................................9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 6. Acknowledgements ................................................9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 7. References ......................................................9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9 7.1. Normative References .......................................9
8.2. Informative References . . . . . . . . . . . . . . . . . 9 7.2. Informative References ....................................10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
This document updates the IPv6 addressing architecture [RFC4291] by This document updates the IPv6 addressing architecture [RFC4291] by
re-defining reserved bits as generic flag bits (Section 2). The redefining reserved bits as generic flag bits (Section 2). The
document provides also some clarifications related to the use of document also provides some clarifications related to the use of
these flag bits (Section 3). these flag bits (Section 3).
This document updates [RFC3956], [RFC3306], and [RFC4291]. These This document updates [RFC3956], [RFC3306], and [RFC4291]. These
updates are logical consequences of the new processing rules in updates are logical consequences of the new processing rules in
Section 3. Section 3.
Textual representation of IPv6 addresses included in the RFC updates Textual representation of IPv6 addresses included in the RFC updates
follows the recommendation in [RFC5952]. follows the recommendation in [RFC5952].
1.1. Requirements Language
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 [RFC2119].
2. Addressing Architecture Update 2. Addressing Architecture Update
Bits 17-20 of a multicast address, where bit 1 is the most Bits 17-20 of a multicast address, where bit 1 is the most
significant bit, are defined in [RFC3956] and [RFC3306] as reserved significant bit, are defined in [RFC3956] and [RFC3306] as reserved
bits. This document defines these bits as generic flag bits so that bits. This document defines these bits as generic flag bits so that
they apply to any multicast address. These bits are referred to as they apply to any multicast address. These bits are referred to as
ff2 (flag field 2) while the flgs bits in [RFC4291][RFC3956] are "ff2" (flag field 2), while the "flgs" bits in [RFC4291] [RFC3956]
renamed to ff1 (flag field 1). are renamed to "ff1" (flag field 1).
Within this document, flag bits denote both ff1 and ff2. Within this document, flag bits denote both ff1 and ff2.
Defining the bits 17-20 as flags for all IPv6 multicast addresses Defining the bits 17-20 as flags for all IPv6 multicast addresses
allows addresses to be treated in a more uniform and generic way, and allows addresses to be treated in a more uniform and generic way, and
allows for these bits to be defined in the future for different allows for these bits to be defined in the future for different
purposes, irrespective of the specific type of multicast address. purposes, irrespective of the specific type of multicast address.
For the record, this design choice was initially triggered by the For the record, this design choice was initially triggered by the
specification in [I-D.ietf-mboned-64-multicast-address-format] which specification in [ADDR-FORMAT], which proposed associating a meaning
proposed for associating a meaning with one of the reserved bits. with one of the reserved bits. Moreover, [ADDR-FORMAT] also
Moreover, [I-D.ietf-mboned-64-multicast-address-format] considered considered the use of the last remaining flag in ff1, but that
also the use of the last remaining flag in ff1 but that approach was approach was abandoned because it is not clear at this stage whether
abandoned because it is not clear at this stage whether there is there are other usage scenarios of the flag.
other usage scenarios of the flag.
Section 4 specifies the updated structure of the addressing Section 4 specifies the updated structure of the addressing
architecture. architecture.
Further specification documents may define a meaning for these flag Further specification documents may define a meaning for these
bits. flag bits.
3. Flag Bits: New Processing Rules 3. Flag Bits: New Processing Rules
Some implementations and specification documents do not treat the Some implementations and specification documents do not treat the
flag bits as separate bits but tend to use their combined value as a flag bits as separate bits but tend to use their combined value as a
4-bit integer. This practice is a hurdle for assigning a meaning to 4-bit integer. This practice is a hurdle for assigning a meaning to
the remaining flag bits. Below are listed some examples for the remaining flag bits. Below are listed some examples for
illustration purposes: illustration purposes:
o the reading of [RFC3306] may lead to conclude that ff3x::/32 is o The reading of [RFC3306] may lead one to conclude that ff3x::/32
the only allowed Source Specific Multicast (SSM) IPv6 prefix is the only allowed Source-Specific Multicast (SSM) IPv6 prefix
block. block.
o [RFC3956] states only ff70::/12 applies to Embedded-RP. o [RFC3956] states that only ff70::/12 applies to Embedded-RP.
Particularly, implementations should not treat the fff0::/12 range Particularly, implementations should not treat the fff0::/12 range
as Embedded-RP. as Embedded-RP.
To avoid such confusion and to unambiguously associate a meaning with To avoid such confusion and to unambiguously associate a meaning with
the remaining flags, the following requirement is made: the remaining flags, the following requirement is made:
Implementations MUST treat flag bits as separate bits. Implementations MUST treat flag bits as separate bits.
4. RFC Updates 4. RFC Updates
4.1. RFC 3306 4.1. Updates to RFC 3306
4.1.1. Update #1 4.1.1. Update #1
This document changes Section 4 of [RFC3306] as follows: This document changes Section 4 of [RFC3306] as follows:
OLD: OLD:
| 8 | 4 | 4 | 8 | 8 | 64 | 32 | | 8 | 4 | 4 | 8 | 8 | 64 | 32 |
+--------+----+----+--------+--------+----------------+----------+ +--------+----+----+--------+--------+----------------+----------+
|11111111|flgs|scop|reserved| plen | network prefix | group ID | |11111111|flgs|scop|reserved| plen | network prefix | group ID |
+--------+----+----+--------+--------+----------------+----------+ +--------+----+----+--------+--------+----------------+----------+
+-+-+-+-+ +-+-+-+-+
flgs is a set of 4 flags: |0|0|P|T| flgs is a set of 4 flags: |0|0|P|T|
+-+-+-+-+ +-+-+-+-+
o P = 0 indicates a multicast address that is not assigned o P = 0 indicates a multicast address that is not assigned
based on the network prefix. This indicates a multicast based on the network prefix. This indicates a multicast
address as defined in [ADDRARCH]. address as defined in [ADDRARCH].
o P = 1 indicates a multicast address that is assigned based o P = 1 indicates a multicast address that is assigned based
skipping to change at page 5, line 10 skipping to change at page 5, line 15
o If P = 1, T MUST be set to 1, otherwise the setting of the T 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]. bit is defined in Section 2.7 of [ADDRARCH].
The reserved field MUST be zero. The reserved field MUST be zero.
Note: [ADDRARCH] is a reference listed in [RFC3306]. [ADDRARCH] Note: [ADDRARCH] is a reference listed in [RFC3306]. [ADDRARCH]
has been since obsoleted by [RFC4291]. has been since obsoleted by [RFC4291].
NEW: NEW:
| 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 | | 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 |
+--------+----+----+----+----+--------+----------------+----------+ +--------+----+----+----+----+--------+----------------+----------+
|11111111|ff1 |scop|ff2 |rsvd| plen | network prefix | group ID | |11111111|ff1 |scop|ff2 |rsvd| plen | network prefix | group ID |
+--------+----+----+----+----+--------+----------------+----------+ +--------+----+----+----+----+--------+----------------+----------+
+-+-+-+-+ +-+-+-+-+
ff1 (flag field 1) is a set of 4 flags: |X|Y|P|T| ff1 (flag field 1) is a set of 4 flags: |X|Y|P|T|
+-+-+-+-+ +-+-+-+-+
X and Y may each be set to 0 or 1. Note, X is for future assignment X and Y may each be set to 0 or 1. Note that X is for future
while a meaning is associated with Y in RFC3956. assignment, while a meaning is associated with Y in RFC 3956.
o P = 0 indicates a multicast address that is not assigned o P = 0 indicates a multicast address that is not assigned
based on the network prefix. This indicates a multicast based on the network prefix. This indicates a multicast
address as defined in [RFC4291]. address as defined in [RFC4291].
o P = 1 indicates a multicast address that is assigned based o P = 1 indicates a multicast address that is assigned based
on the network prefix. on the network prefix.
o If P = 1, T MUST be set to 1, otherwise the setting of the T o If P = 1, T MUST be set to 1; otherwise, the setting of the
bit is defined in Section 2.7 of [RFC4291]. T bit is defined in Section 2.7 of [RFC4291].
+-+-+-+-+ +-+-+-+-+
ff2 (flag field 2) is a set of 4 flags: |r|r|r|r| ff2 (flag field 2) is a set of 4 flags: |r|r|r|r|
+-+-+-+-+ +-+-+-+-+
where "rrrr" are for future assignment as additional flag bits. where "rrrr" are for future assignment as additional flag bits.
r bits MUST each be sent as zero and MUST be ignored on receipt. r bits MUST each be sent as zero and MUST be ignored on receipt.
Flag bits denote both ff1 and ff2. Flag bits denote both ff1 and ff2.
skipping to change at page 6, line 8 skipping to change at page 6, line 20
These settings create an SSM range of FF3x::/32 (where 'x' is any These settings create an SSM range of FF3x::/32 (where 'x' is any
valid scope value). The source address field in the IPv6 header valid scope value). The source address field in the IPv6 header
identifies the owner of the multicast address. identifies the owner of the multicast address.
NEW: NEW:
If the flag bits in ff1 are set to 0011, these settings create an If the flag bits in ff1 are set to 0011, these settings create an
SSM range of ff3x::/32 (where 'x' is any valid scope value). The SSM range of ff3x::/32 (where 'x' is any valid scope value). The
source address field in the IPv6 header identifies the owner of source address field in the IPv6 header identifies the owner of
the multicast address. ff3x::/32 is not the only allowed SSM the multicast address. ff3x::/32 is not the only allowed SSM
prefix range. For example if the most significant flag bit in ff1 prefix range. For example, if the most significant flag bit in
is set, then we would get the SSM range ffbx::/32. ff1 is set, then we would get the SSM range ffbx::/32.
4.2. RFC 3956 4.2. Updates to RFC 3956
4.2.1. Update #1 4.2.1. Update #1
This document changes Section 2 of [RFC3956] as follows: This document changes Section 2 of [RFC3956] as follows:
OLD: OLD:
As described in [RFC3306], the multicast address format is as As described in [RFC3306], the multicast address format is
follows: as follows:
| 8 | 4 | 4 | 8 | 8 | 64 | 32 | | 8 | 4 | 4 | 8 | 8 | 64 | 32 |
+--------+----+----+--------+----+----------------+----------+ +--------+----+----+--------+----+----------------+----------+
|11111111|flgs|scop|reserved|plen| network prefix | group ID | |11111111|flgs|scop|reserved|plen| network prefix | group ID |
+--------+----+----+--------+----+----------------+----------+ +--------+----+----+--------+----+----------------+----------+
Where flgs are "0011". (The first two bits are as yet undefined, Where flgs are "0011". (The first two bits are as yet undefined,
sent as zero and ignored on receipt.) sent as zero and ignored on receipt.)
NEW: NEW:
The multicast address format is as follows: The multicast address format is as follows:
| 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 | | 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 |
+--------+----+----+----+----+----+----------------+----------+ +--------+----+----+----+----+----+----------------+----------+
|11111111|ff1 |scop|ff2 |rsvd|plen| network prefix | group ID | |11111111|ff1 |scop|ff2 |rsvd|plen| network prefix | group ID |
+--------+----+----+----+----+----+----------------+----------+ +--------+----+----+----+----+----+----------------+----------+
+-+-+-+-+ +-+-+-+-+
ff1 (flag field 1) is a set of four flags: |X|R|P|T| ff1 (flag field 1) is a set of four flags: |X|R|P|T|
+-+-+-+-+ +-+-+-+-+
where X is for future assignment as additional flag bit. X may be
set to 0 or 1.
+-+-+-+-+ where X is for future assignment as an additional flag bit.
ff2 (flag field 2) is a set of 4 flags: |r|r|r|r| X may be set to 0 or 1.
+-+-+-+-+
where "rrrr" are for future assignment as additional flag bits.
r bits MUST each be sent as zero and MUST be ignored on receipt.
Flag bits denote both ff1 and ff2. +-+-+-+-+
ff2 (flag field 2) is a set of 4 flags: |r|r|r|r|
+-+-+-+-+
where "rrrr" are for future assignment as additional flag bits.
r bits MUST each be sent as zero and MUST be ignored
on receipt.
Flag bits denote both ff1 and ff2.
4.2.2. Update #2 4.2.2. Update #2
This document changes Section 3 of [RFC3956] as follows: This document changes Section 3 of [RFC3956] as follows:
OLD: OLD:
| 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 | | 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 |
+--------+----+----+----+----+----+----------------+----------+ +--------+----+----+----+----+----+----------------+----------+
|11111111|flgs|scop|rsvd|RIID|plen| network prefix | group ID | |11111111|flgs|scop|rsvd|RIID|plen| network prefix | group ID |
skipping to change at page 8, line 5 skipping to change at page 8, line 15
The behavior is unspecified if P or T is not set to 1, as then the The behavior is unspecified if P or T is not set to 1, as then the
prefix would not be FF70::/12. Likewise, the encoding and the prefix would not be FF70::/12. Likewise, the encoding and the
protocol mode used when the two high-order bits in "flgs" are set to protocol mode used when the two high-order bits in "flgs" are set to
11 ("FFF0::/12") is intentionally unspecified until such time that 11 ("FFF0::/12") is intentionally unspecified until such time that
the highest-order bit is defined. Without further IETF the highest-order bit is defined. Without further IETF
specification, implementations SHOULD NOT treat the FFF0::/12 range specification, implementations SHOULD NOT treat the FFF0::/12 range
as Embedded-RP. as Embedded-RP.
NEW: NEW:
| 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 | | 8 | 4 | 4 | 4 | 4 | 8 | 64 | 32 |
+--------+----+----+----+----+----+----------------+----------+ +--------+----+----+----+----+----+----------------+----------+
|11111111|ff1 |scop|ff2 |RIID|plen| network prefix | group ID | |11111111|ff1 |scop|ff2 |RIID|plen| network prefix | group ID |
+--------+----+----+----+----+----+----------------+----------+ +--------+----+----+----+----+----+----------------+----------+
+-+-+-+-+ +-+-+-+-+
ff1 is a set of four flags: |X|R|P|T| ff1 is a set of four flags: |X|R|P|T|
+-+-+-+-+ +-+-+-+-+
where X is for future assignment as additional flag bit. X may be where X is for future assignment as an additional flag bit.
set to 0 or 1. X may be set to 0 or 1.
R = 1 indicates a multicast address that embeds the address of the R = 1 indicates a multicast address that embeds the address of the
RP. Then P MUST be set to 1, and consequently T MUST be set to 1, RP. Then, P MUST be set to 1, and consequently T MUST be set
according to [RFC3306], as this is a special case of unicast-prefix to 1, according to [RFC3306], as this is a special case of
based addresses. This implies that, for instance, prefixes ff70::/12 unicast-prefix-based addresses. This implies that, for instance,
and fff0::/12 are embedded RP prefixes. When the R-bit is set, the prefixes ff70::/12 and fff0::/12 are embedded RP prefixes. When
last 4 bits of the field that were reserved in [RFC3306] are the R-bit is set, the last 4 bits of the field that were reserved
interpreted as embedding the RP interface ID, as specified in this in [RFC3306] are interpreted as embedding the RP interface ID, as
memo. specified in this memo.
4.2.3. Update #3 4.2.3. Update #3
This document changes Section 4 of [RFC3956] as follows: This document changes Section 4 of [RFC3956] as follows:
OLD: OLD:
It MUST be a multicast address with "flgs" set to 0111, that is, o It MUST be a multicast address with "flgs" set to 0111, that is, to
to be of the prefix FF70::/12, be of the prefix FF70::/12,
NEW: NEW:
It MUST be a multicast address with R-bit set to 1. o It MUST be a multicast address with the R-bit set to 1.
It MUST have P-bit and T-bit both set to 1 when using the o It MUST have the P-bit and T-bit both set to 1 when using the
embedding in this document as it is a prefix-based address. embedding in this document as it is a prefix-based address.
4.2.4. Update #4 4.2.4. Update #4
This document changes Section 7.1 of [RFC3956] as follows: This document changes Section 7.1 of [RFC3956] as follows:
OLD: OLD:
To avoid loops and inconsistencies, for addresses in the range To avoid loops and inconsistencies, for addresses in the range
FF70::/12, the Embedded-RP mapping MUST be considered the longest FF70::/12, the Embedded-RP mapping MUST be considered the longest
possible match and higher priority than any other mechanism. possible match and higher priority than any other mechanism.
NEW: NEW:
To avoid loops and inconsistencies, for addresses with R-bit set To avoid loops and inconsistencies, for addresses with the R-bit
to 1, the Embedded-RP mapping MUST be considered the longest set to 1, the Embedded-RP mapping MUST be considered the longest
possible match and higher priority than any other mechanism. possible match and higher priority than any other mechanism.
5. IANA Considerations 5. Security Considerations
This document does not require any action from IANA.
6. Security Considerations
The same security considerations as those discussed in [RFC3956], The same security considerations as those discussed in [RFC3956],
[RFC3306] and [RFC4291] are to be taken into account. [RFC3306], and [RFC4291] are to be taken into account.
7. Acknowledgements 6. Acknowledgements
Special thanks to Brian Haberman for the discussions prior to the Special thanks to Brian Haberman for the discussions prior to the
publication of this document. publication of this document.
Many thanks to Jouni Korhonen, Tatuya Jinmei, Charlie Kaufman, and Many thanks to Jouni Korhonen, Tatuya Jinmei, Charlie Kaufman, and
Ben Campbell for their review. Ben Campbell for their review.
8. References 7. References
8.1. Normative References 7.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6 [RFC3306] Haberman, B. and D. Thaler, "Unicast-Prefix-based IPv6
Multicast Addresses", RFC 3306, August 2002. Multicast Addresses", RFC 3306, August 2002.
[RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous [RFC3956] Savola, P. and B. Haberman, "Embedding the Rendezvous
Point (RP) Address in an IPv6 Multicast Address", RFC Point (RP) Address in an IPv6 Multicast Address",
3956, November 2004. RFC 3956, November 2004.
[RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing [RFC4291] Hinden, R. and S. Deering, "IP Version 6 Addressing
Architecture", RFC 4291, February 2006. Architecture", RFC 4291, February 2006.
[RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6 [RFC5952] Kawamura, S. and M. Kawashima, "A Recommendation for IPv6
Address Text Representation", RFC 5952, August 2010. Address Text Representation", RFC 5952, August 2010.
8.2. Informative References 7.2. Informative References
[I-D.ietf-mboned-64-multicast-address-format] [ADDR-FORMAT]
Boucadair, M., Qin, J., Lee, Y., Venaas, S., Li, X., and Boucadair, M., Qin, J., Lee, Y., Venaas, S., Li, X., and
M. Xu, "IPv6 Multicast Address With Embedded IPv4 M. Xu, "IPv6 Multicast Address With Embedded IPv4
Multicast Address", draft-ietf-mboned-64-multicast- Multicast Address", Work in Progress, April 2013.
address-format-05 (work in progress), April 2013.
Authors' Addresses Authors' Addresses
Mohamed Boucadair Mohamed Boucadair
France Telecom France Telecom
Rennes 35000 Rennes 35000
France France
Email: mohamed.boucadair@orange.com EMail: mohamed.boucadair@orange.com
Stig Venaas Stig Venaas
Cisco Cisco
USA USA
Email: stig@cisco.com EMail: stig@cisco.com
 End of changes. 45 change blocks. 
136 lines changed or deleted 127 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/