--- 1/draft-ietf-mboned-mtrace-v2-19.txt	2017-10-14 22:13:13.793582453 -0700
+++ 2/draft-ietf-mboned-mtrace-v2-20.txt	2017-10-14 22:13:13.877584451 -0700
@@ -1,20 +1,20 @@
 
 MBONED Working Group                                           H. Asaeda
 Internet-Draft                                                      NICT
 Intended status: Standards Track                                K. Meyer
-Expires: April 10, 2018                                            Cisco
+Expires: April 17, 2018                                            Cisco
                                                              W. Lee, Ed.
-                                                         October 7, 2017
+                                                        October 14, 2017
 
          Mtrace Version 2: Traceroute Facility for IP Multicast
-                     draft-ietf-mboned-mtrace-v2-19
+                     draft-ietf-mboned-mtrace-v2-20
 
 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 https://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 April 10, 2018.
+   This Internet-Draft will expire on April 17, 2018.
 
 Copyright Notice
 
    Copyright (c) 2017 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
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -1560,21 +1560,21 @@
    Dave Thaler, Achmad Husni Thamrin, Stig Venaas, and Cao Wei.
 
 11.  References
 
 11.1.  Normative References
 
    [1]        Bradner, S., "Key words for use in RFCs to indicate
               requirement levels", RFC 2119, March 1997.
 
    [2]        Deering, S. and R. Hinden, "Internet Protocol, Version 6
-              (IPv6) Specification", RFC 2460, December 1998.
+              (IPv6) Specification", RFC 8200, July 2017.
 
    [3]        Hinden, R. and S. Deering, "IP Version 6 Addressing
               Architecture", RFC 4291, February 2006.
 
    [4]        Cotton, M., Leiba, B., and T. Narten, "Guidelines for
               Writing an IANA Considerations Section in RFCs", RFC 8126,
               June 2017.
 
    [5]        Fenner, B., Handley, M., Holbrook, H., Kouvelas, I.,
               Parekh, R., Zhang, Z., and L. Zheng, "Protocol Independent