--- 1/draft-ietf-mboned-lightweight-igmpv3-mldv2-03.txt	2008-09-06 12:12:18.000000000 +0200
+++ 2/draft-ietf-mboned-lightweight-igmpv3-mldv2-04.txt	2008-09-06 12:12:18.000000000 +0200
@@ -1,20 +1,20 @@
 
 MBONED Working Group                                              H. Liu
 Internet-Draft                                                    W. Cao
-Expires: December 7, 2008                  Huawei Technologies Co., Ltd.
-                                                               H. Asaeda
+Intended status: BCP                       Huawei Technologies Co., Ltd.
+Expires: March 10, 2009                                        H. Asaeda
                                                          Keio University
-                                                            June 5, 2008
+                                                       September 6, 2008
 
                  Lightweight IGMPv3 and MLDv2 Protocols
-             draft-ietf-mboned-lightweight-igmpv3-mldv2-03
+             draft-ietf-mboned-lightweight-igmpv3-mldv2-04
 
 Status of this Memo
 
    By submitting this Internet-Draft, each author represents that any
    applicable patent or other IPR claims of which he or she is aware
    have been or will be disclosed, and any of which he or she becomes
    aware will be disclosed, in accordance with Section 6 of BCP 79.
 
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF), its areas, and its working groups.  Note that
@@ -25,21 +25,21 @@
    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."
 
    The list of current Internet-Drafts can be accessed at
    http://www.ietf.org/ietf/1id-abstracts.txt.
 
    The list of Internet-Draft Shadow Directories can be accessed at
    http://www.ietf.org/shadow.html.
 
-   This Internet-Draft will expire on December 7, 2008.
+   This Internet-Draft will expire on March 10, 2009.
 
 Abstract
 
    This document describes lightweight IGMPv3 and MLDv2 protocols (LW-
    IGMPv3 and LW-MLDv2), which simplify the standard (full) versions of
    IGMPv3 and MLDv2.  The interoperability with the full versions and
    the previous versions of IGMP and MLD is also taken into account.
 
 Conventions used in this document
 
@@ -560,23 +560,21 @@
    use.
 
 6.1.1.  Behavior of Group Members
 
    A LW-IGMPv3 host's compatibility mode is determined from the Host
    Compatibility Mode variable which can be in one of three states:
    IGMPv1, IGMPv2, or IGMPv3.  When a lightweight host behaves on its
    interface as LW-IGMPv3, its Host Compatibility Mode of that interface
    is set to IGMPv3, and the host sends a subset of IGMPv3 report
    messages, which can be recognized by a multicast router running the
-   full or the lightweight IGMPv3 protocol on the same LAN.  The
-   lightweight host's processing rule in presence of older version
-   Queriers should be the same as that of full IGMPv3.
+   full or the lightweight IGMPv3 protocol on the same LAN.
 
 6.1.2.  Behavior of Multicast Routers
 
    A LW-IGMPv3 or LW-MLDv2 router does not process directly IS_EX(x) and
    TO_EX(x) records that are used by the full version.  When a LW-
    IGMPv3/LW-MLDv2 router receives these report messages from the full
    version host, it MUST translate them internally to IS_EX({}) and
    TO_EX({}) respectively and behaves accordingly.
 
 6.2.  Interoperation with IGMPv1/IGMPv2
@@ -628,20 +626,22 @@
 
    When Group Compatibility mode is IGMPv1, a LW-IGMPv3 router
    internally translates the following IGMPv1 and IGMPv2 messages for
    that group to their IGMPv3 equivalents:
 
                 IGMPv1 Message         LW-IGMPv3 Equivalent
                 --------------         --------------------
 
                   v1 Report                  TO_EX({})
 
+                  v2 Report                  TO_EX({})
+
 6.3.  Interoperation with MLDv1
 
    The MLDv2 hosts and routers MUST interoperate with the hosts and
    routers running MLDv1.  The method is the same as described in
    Section 6.2.  The difference is that when a MLDv2 router has a MLDv1
    listener on its network, it translates the following MLDv1 messages
    to their MLDv2 equivalents:
 
                  MLDv1 Message         LW-MLDv2 Equivalent
                  -------------         -------------------