draft-ietf-6man-multicast-addr-arch-update-06.txt   draft-ietf-6man-multicast-addr-arch-update-07.txt 
6man Working Group M. Boucadair 6man Working Group M. Boucadair
Internet-Draft France Telecom Internet-Draft France Telecom
Updates: 3306,3956,4291 (if approved) S. Venaas Updates: 3306,3956,4291 (if approved) S. Venaas
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: January 5, 2015 July 04, 2014 Expires: January 8, 2015 July 07, 2014
Updates to the IPv6 Multicast Addressing Architecture Updates to the IPv6 Multicast Addressing Architecture
draft-ietf-6man-multicast-addr-arch-update-06 draft-ietf-6man-multicast-addr-arch-update-07
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 re-defining the reserved bits as generic flag bits. The document
provides also some clarifications related to the use of these flag provides also some clarifications related to the use of these flag
bits. bits.
This document updates RFC 3956, RFC 3306 and RFC 4291. This document updates RFC 3956, RFC 3306 and RFC 4291.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on January 5, 2015. This Internet-Draft will expire on January 8, 2015.
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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. 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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Addressing Architecture Update . . . . . . . . . . . . . . . 3 2. Addressing Architecture Update . . . . . . . . . . . . . . . 3
3. Flag Bits: A Recommendation . . . . . . . . . . . . . . . . . 3 3. Flag Bits: A Recommendation . . . . . . . . . . . . . . . . . 3
4. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. RFC Updates . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1. RFC 3306 . . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. RFC 3306 . . . . . . . . . . . . . . . . . . . . . . . . 4
4.1.1. Update #1 . . . . . . . . . . . . . . . . . . . . . . 4 4.1.1. Update #1 . . . . . . . . . . . . . . . . . . . . . . 4
4.1.2. Update #2 . . . . . . . . . . . . . . . . . . . . . . 5 4.1.2. Update #2 . . . . . . . . . . . . . . . . . . . . . . 5
4.2. RFC 3956 . . . . . . . . . . . . . . . . . . . . . . . . 6 4.2. RFC 3956 . . . . . . . . . . . . . . . . . . . . . . . . 6
4.2.1. Update #1 . . . . . . . . . . . . . . . . . . . . . . 6 4.2.1. Update #1 . . . . . . . . . . . . . . . . . . . . . . 6
4.2.2. Update #2 . . . . . . . . . . . . . . . . . . . . . . 6 4.2.2. Update #2 . . . . . . . . . . . . . . . . . . . . . . 7
4.2.3. Update #3 . . . . . . . . . . . . . . . . . . . . . . 8 4.2.3. Update #3 . . . . . . . . . . . . . . . . . . . . . . 8
4.2.4. Update #4 . . . . . . . . . . . . . . . . . . . . . . 8 4.2.4. Update #4 . . . . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 8 6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
8.1. Normative References . . . . . . . . . . . . . . . . . . 9 8.1. Normative References . . . . . . . . . . . . . . . . . . 9
8.2. Informative References . . . . . . . . . . . . . . . . . 9 8.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 9 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 re-defining reserved bits as generic flag bits (Section 2). The
document provides also some clarifications related to the use of document provides also 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 recommendation on the flag updates are logical consequences of the recommendation on the flag
 End of changes. 8 change blocks. 
9 lines changed or deleted 21 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/