--- 1/draft-ietf-6man-multicast-addr-arch-update-03.txt	2014-03-12 01:14:36.600395128 -0700
+++ 2/draft-ietf-6man-multicast-addr-arch-update-04.txt	2014-03-12 01:14:36.620395627 -0700
@@ -1,19 +1,19 @@
 
 6man Working Group                                          M. Boucadair
 Internet-Draft                                            France Telecom
 Updates: 3306,3956,4291 (if approved)                          S. Venaas
 Intended status: Standards Track                                   Cisco
-Expires: August 17, 2014                               February 13, 2014
+Expires: September 13, 2014                               March 12, 2014
 
          Updates to the IPv6 Multicast Addressing Architecture
-             draft-ietf-6man-multicast-addr-arch-update-03
+             draft-ietf-6man-multicast-addr-arch-update-04
 
 Abstract
 
    This document updates the IPv6 multicast addressing architecture by
    defining the 17-20 reserved bits as generic flag bits.  The document
    provides also some clarifications related to the use of these flag
    bits.
 
    This document updates RFC 3956, RFC 3306 and RFC 4291.
 
@@ -31,21 +31,21 @@
    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 August 17, 2014.
+   This Internet-Draft will expire on September 13, 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
@@ -299,28 +299,28 @@
 
       |   8    |  4 |  4 |  4 |  4 | 8  |       64       |    32    |
       +--------+----+----+----+----+----+----------------+----------+
       |11111111|ff1 |scop|ff2 |RIID|plen| network prefix | group ID |
       +--------+----+----+----+----+----+----------------+----------+
                                       +-+-+-+-+
       ff1 is a set of four flags:     |X|R|P|T|
                                       +-+-+-+-+
       X may be set to 0 or 1.
 
-   R = 1 indicates a multicast address that embeds the address of the RP.
-   P MUST be set to 1, and consequently T MUST be set to 1, according
-   to [RFC3306], as this is a special case of
-   unicast-prefix based addresses. This implies that for instance prefixes
-   ff70::/12 and fff0::/12 are embedded RP prefixes.
-   The behavior is unspecified if P or T is not set to 1. When the
-   R-bit is set, the last 4 bits of the previously reserved field are
-   interpreted as embedding the RP interface ID, as specified in this memo.
+   R = 1 indicates a multicast address that embeds the address of the
+   RP.  P MUST be set to 1, and consequently T MUST be set to 1,
+   according to [RFC3306], as this is a special case of unicast-prefix
+   based addresses.  This implies that for instance prefixes ff70::/12
+   and fff0::/12 are embedded RP prefixes.  The behavior is unspecified
+   if P or T is not set to 1.  When the R-bit is set, the last 4 bits of
+   the field that were reserved in [RFC3306] are interpreted as
+   embedding the RP interface ID, as specified in this memo.
 
    This document changes Section 4 of [RFC3956] as follows:
 
    OLD:
 
       It MUST be a multicast address with "flgs" set to 0111, that is,
       to be of the prefix FF70::/12,
 
    NEW: