--- 1/draft-ietf-mboned-v4v6-mcast-ps-03.txt	2013-09-06 07:14:24.184934817 -0700
+++ 2/draft-ietf-mboned-v4v6-mcast-ps-04.txt	2013-09-06 07:14:24.224935836 -0700
@@ -1,50 +1,50 @@
 
 MBONED Working Group                                        C. Jacquenet
 Internet-Draft                                              M. Boucadair
 Intended status: Informational                     France Telecom Orange
-Expires: December 07, 2013                                        Y. Lee
+Expires: March 10, 2014                                           Y. Lee
                                                                  Comcast
                                                                   J. Qin
                                                            Cisco Systems
                                                                  T. Tsou
                                                Huawei Technologies (USA)
                                                                   Q. Sun
                                                            China Telecom
-                                                           June 05, 2013
+                                                      September 06, 2013
 
           IPv4-IPv6 Multicast: Problem Statement and Use Cases
-                   draft-ietf-mboned-v4v6-mcast-ps-03
+                   draft-ietf-mboned-v4v6-mcast-ps-04
 
 Abstract
 
-   This document discusses issues and requirements raised by IPv4-IPv6
-   multicast interconnection and co-existence scenarios.  It also
-   discusses various multicast use cases which may occur during IPv6
-   transitioning.
+   This document discusses issues and requirements raised by intra-
+   domain IPv4-IPv6 multicast interconnection and co-existence
+   scenarios.  It also discusses various multicast use cases which may
+   occur during IPv6 transitioning.
 
 Status of This Memo
 
    This Internet-Draft is submitted in full conformance with the
    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
    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 December 07, 2013.
+   This Internet-Draft will expire on March 10, 2014.
 
 Copyright Notice
 
    Copyright (c) 2013 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
@@ -100,23 +100,23 @@
    example, the observed evolution of ADSL broadband access
    infrastructures from a service-specific, multi-PVC (Permanent Virtual
    Circuit) scheme towards a "service-agnostic", single PVC scheme,
    assumes the allocation of a globally unique IPv4 address on the WAN
    (Wide Area Network) interface of the CPE (Customer Premises
    Equipment), or to a mobile terminal), whatever the number and the
    nature of the services the customer has subscribed to.
 
    Likewise, the global IPv4 address depletion encourages the
    development of IPv6 receivers while contents may very well remain
-   IPv4-formatted.  There is therefore a need to make sure such IPv6
-   receivers can access IPv4-formatted contents during the transition
-   period.
+   IPv4-formatted, i.e., sourced by an IPv4 application.  There is
+   therefore a need to make sure such IPv6 receivers can access
+   IPv4-formatted contents during the transition period.
 
    During the transition period, the usage of the remaining global IPv4
    address blocks will have to be rationalized for the sake of IPv4
    service continuity.  The current state-of-the-art suggests the
    introduction of NAT (Network Address Translation) capabilities
    (generally denoted as CGN, for Carrier-Grade NAT) in providers'
    networks, so that a global IPv4 address will be shared between
    several customers.
 
    As a consequence, CPE or mobile UE (User Equipment) devices will no