--- 1/draft-ietf-mboned-mtrace-v2-10.txt 2014-10-27 02:14:51.566485316 -0700 +++ 2/draft-ietf-mboned-mtrace-v2-11.txt 2014-10-27 02:14:51.634487016 -0700 @@ -1,19 +1,19 @@ MBONED Working Group H. Asaeda Internet-Draft NICT Intended status: Standards Track W. Lee, Ed. -Expires: January 10, 2014 Juniper Networks, Inc. - July 09, 2013 +Expires: April 29, 2015 + October 26, 2014 Mtrace Version 2: Traceroute Facility for IP Multicast - draft-ietf-mboned-mtrace-v2-10 + draft-ietf-mboned-mtrace-v2-11 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. @@ -25,25 +25,25 @@ 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 January 10, 2014. + This Internet-Draft will expire on April 29, 2015. Copyright Notice - Copyright (c) 2013 IETF Trust and the persons identified as the + 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 carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as @@ -53,48 +53,48 @@ 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 5 3. Packet Formats . . . . . . . . . . . . . . . . . . . . . . . 6 3.1. Mtrace2 TLV format . . . . . . . . . . . . . . . . . . . 7 3.2. Defined TLVs . . . . . . . . . . . . . . . . . . . . . . 7 3.2.1. Mtrace2 Query . . . . . . . . . . . . . . . . . . . . 8 3.2.2. Mtrace2 Request . . . . . . . . . . . . . . . . . . . 10 3.2.3. Mtrace2 Reply . . . . . . . . . . . . . . . . . . . . 10 - 3.2.4. IPv4 Mtrace2 Standard Response Block . . . . . . . . 10 + 3.2.4. IPv4 Mtrace2 Standard Response Block . . . . . . . . 11 3.2.5. IPv6 Mtrace2 Standard Response Block . . . . . . . . 14 3.2.6. Mtrace2 Augmented Response Block . . . . . . . . . . 17 3.2.7. Mtrace2 Extended Query Block . . . . . . . . . . . . 18 4. Router Behavior . . . . . . . . . . . . . . . . . . . . . . . 19 4.1. Receiving Mtrace2 Query . . . . . . . . . . . . . . . . . 19 4.1.1. Query Packet Verification . . . . . . . . . . . . . . 19 4.1.2. Query Normal Processing . . . . . . . . . . . . . . . 20 4.2. Receiving Mtrace2 Request . . . . . . . . . . . . . . . . 20 4.2.1. Request Packet Verification . . . . . . . . . . . . . 20 4.2.2. Request Normal Processing . . . . . . . . . . . . . . 20 4.3. Forwarding Mtrace2 Request . . . . . . . . . . . . . . . 22 4.3.1. Destination Address . . . . . . . . . . . . . . . . . 22 - 4.3.2. Source Address . . . . . . . . . . . . . . . . . . . 22 + 4.3.2. Source Address . . . . . . . . . . . . . . . . . . . 23 4.3.3. Appending Standard Response Block . . . . . . . . . . 23 4.4. Sending Mtrace2 Reply . . . . . . . . . . . . . . . . . . 23 4.4.1. Destination Address . . . . . . . . . . . . . . . . . 23 4.4.2. Source Address . . . . . . . . . . . . . . . . . . . 23 - 4.4.3. Appending Standard Response Block . . . . . . . . . . 23 + 4.4.3. Appending Standard Response Block . . . . . . . . . . 24 4.5. Proxying Mtrace2 Query . . . . . . . . . . . . . . . . . 24 4.6. Hiding Information . . . . . . . . . . . . . . . . . . . 24 5. Client Behavior . . . . . . . . . . . . . . . . . . . . . . . 25 5.1. Sending Mtrace2 Query . . . . . . . . . . . . . . . . . . 25 5.1.1. Destination Address . . . . . . . . . . . . . . . . . 25 5.1.2. Source Address . . . . . . . . . . . . . . . . . . . 25 5.2. Determining the Path . . . . . . . . . . . . . . . . . . 25 5.3. Collecting Statistics . . . . . . . . . . . . . . . . . . 25 - 5.4. Last Hop Router (LHR) . . . . . . . . . . . . . . . . . . 25 + 5.4. Last Hop Router (LHR) . . . . . . . . . . . . . . . . . . 26 5.5. First Hop Router (FHR) . . . . . . . . . . . . . . . . . 26 5.6. Broken Intermediate Router . . . . . . . . . . . . . . . 26 5.7. Non-Supported Router . . . . . . . . . . . . . . . . . . 26 5.8. Mtrace2 Termination . . . . . . . . . . . . . . . . . . . 27 5.8.1. Arriving at Source . . . . . . . . . . . . . . . . . 27 5.8.2. Fatal Error . . . . . . . . . . . . . . . . . . . . . 27 5.8.3. No Upstream Router . . . . . . . . . . . . . . . . . 27 5.8.4. Reply Timeout . . . . . . . . . . . . . . . . . . . . 27 5.9. Continuing after an Error . . . . . . . . . . . . . . . . 27 6. Protocol-Specific Considerations . . . . . . . . . . . . . . 28 @@ -704,25 +705,25 @@ Remote Address: 128 bits This field specifies the address of the upstream router, which, in most cases, is a link-local unicast address for the upstream router. Although a link-local address does not have enough information to identify a node, it is possible to detect the upstream router with the assistance of Incoming Interface ID and the current router address (i.e., Local Address). - Note that this may be a multicast group (e.g., - ALL-[protocol]-ROUTERS.MCAST.NET) if the upstream router is not - known because of the workings of a multicast routing protocol. - However, it should be the unspecified address (::) if the incoming - interface address is unknown. + Note that this may be a multicast group (e.g., ALL-[protocol]- + ROUTERS.MCAST.NET) if the upstream router is not known because of + the workings of a multicast routing protocol. However, it should + be the unspecified address (::) if the incoming interface address + is unknown. Input packet count on incoming interface: 64 bits Same definition as in IPv4. Output packet count on outgoing interface: 64 bits Same definition as in IPv4. Total number of packets for this source-group pair: 64 bits Same definition as in IPv4, except if the S bit is set (see below), the count is for the source network, as specified by the @@ -1453,23 +1455,23 @@ mrouted 3.3 by Ajit Thyagarajan. Van's original slides credit Steve Casner, Steve Deering, Dino Farinacci and Deb Agrawal. The original multicast traceroute client, mtrace (version 1), has been implemented by Ajit Thyagarajan, Steve Casner and Bill Fenner. The idea of the "S" bit to allow statistics for a source subnet is due to Tom Pusateri. For the Mtrace version 2 specification, the authors would like to give special thanks to Tatsuya Jinmei, Bill Fenner, and Steve Casner. Also, extensive comments were received from David L. Black, Ronald - Bonica, Yiqun Cai, Liu Hui, Bharat Joshi, Robert W. Kebler, Heidi Ou, - Pekka Savola, Shinsuke Suzuki, Dave Thaler, Achmad Husni Thamrin, and - Cao Wei. + Bonica, Yiqun Cai, Liu Hui, Bharat Joshi, Robert W. Kebler, Heidi + Ou, Pekka Savola, Shinsuke Suzuki, Dave Thaler, Achmad Husni Thamrin, + 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. @@ -1483,22 +1485,22 @@ [5] Fenner, B., Handley, M., Holbrook, H., and I. Kouvelas, "Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)", RFC 4601, August 2006. [6] Handley, M., Kouvelas, I., Speakman, T., and L. Vicisano, "Bidirectional Protocol Independent Multicast (BIDIR- PIM)", RFC 5015, October 2007. [7] Fenner, B., He, H., Haberman, B., and H. Sandick, "Internet Group Management Protocol (IGMP) / Multicast - Listener Discovery (MLD)-Based Multicast Forwarding ("IGMP - /MLD Proxying")", RFC 4605, August 2006. + Listener Discovery (MLD)-Based Multicast Forwarding + ("IGMP/MLD Proxying")", RFC 4605, August 2006. 11.2. Informative References [8] Cain, B., Deering, S., Kouvelas, I., Fenner, B., and A. Thyagarajan, "Internet Group Management Protocol, Version 3", RFC 3376, October 2002. [9] Draves, R. and D. Thaler, "Default Router Preferences and More-Specific Routes", RFC 4191, November 2005. @@ -1520,16 +1522,10 @@ Hitoshi Asaeda National Institute of Information and Communications Technology 4-2-1 Nukui-Kitamachi Koganei, Tokyo 184-8795 Japan Email: asaeda@nict.go.jp WeeSan Lee (editor) - Juniper Networks, Inc. - 1194 North Mathilda Avenue - Sunnyvale, CA 94089-1206 - US - - Email: weesan@juniper.net