--- 1/draft-ietf-mboned-mtrace-v2-14.txt	2016-08-13 08:15:55.415596865 -0700
+++ 2/draft-ietf-mboned-mtrace-v2-15.txt	2016-08-13 08:15:55.487598682 -0700
@@ -1,20 +1,20 @@
 
 MBONED Working Group                                           H. Asaeda
 Internet-Draft                                                      NICT
 Intended status: Standards Track                                K. Meyer
-Expires: February 1, 2017                                          Cisco
+Expires: February 14, 2017                                         Cisco
                                                              W. Lee, Ed.
-                                                           July 31, 2016
+                                                         August 13, 2016
 
          Mtrace Version 2: Traceroute Facility for IP Multicast
-                     draft-ietf-mboned-mtrace-v2-14
+                     draft-ietf-mboned-mtrace-v2-15
 
 Abstract
 
    This document describes the IP multicast traceroute facility, named
    Mtrace version 2 (Mtrace2).  Unlike unicast traceroute, Mtrace2
    requires special implementations on the part of routers.  This
    specification describes the required functionality in multicast
    routers, as well as how an Mtrace2 client invokes a query and
    receives a reply.
 
@@ -26,21 +26,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 February 1, 2017.
+   This Internet-Draft will expire on February 14, 2017.
 
 Copyright Notice
 
    Copyright (c) 2016 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
@@ -867,21 +867,21 @@
 
    Upon receiving an Mtrace2 Query message, a router MUST examine
    whether the Multicast Address and the Source Address are a valid
    combination as specified in Section 3.2.1, and whether the Mtrace2
    Client Address is a valid IP unicast address.  If either one is
    invalid, the Query MUST be silently ignored.
 
    Mtrace2 supports a non-local client to the LHR/RP.  A router SHOULD,
    however, support a mechanism to filter out queries from clients
    beyond a specified administrative boundary.  The potential approaches
-   are described in Section 8.
+   are described in Section 9.2.
 
    In the case where a local LHR client is required, the router must
    then examine the Query to see if it is the proper LHR/RP for the
    destination address in the packet.  It is the proper local LHR if it
    has a multicast-capable interface on the same subnet as the Mtrace2
    Client Address and is the router that would forward traffic from the
    given (S,G) or (*,G) onto that subnet.  It is the proper RP if the
    multicast group address specified in the query is 0 and if the IP
    header destination address is a valid RP address on this router.