--- 1/draft-ietf-mboned-mtrace-v2-25.txt 2018-08-01 00:13:08.174880805 -0700 +++ 2/draft-ietf-mboned-mtrace-v2-26.txt 2018-08-01 00:13:08.254882732 -0700 @@ -1,20 +1,20 @@ MBONED Working Group H. Asaeda Internet-Draft NICT Intended status: Standards Track K. Meyer -Expires: January 26, 2019 +Expires: February 1, 2019 W. Lee, Ed. - July 25, 2018 + July 31, 2018 Mtrace Version 2: Traceroute Facility for IP Multicast - draft-ietf-mboned-mtrace-v2-25 + draft-ietf-mboned-mtrace-v2-26 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 January 26, 2019. + This Internet-Draft will expire on February 1, 2019. Copyright Notice Copyright (c) 2018 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 @@ -371,20 +371,21 @@ The format is based on the Type value. The length of the value field is Length field minus 3. All reserved fields in the Value field MUST be transmitted as zeros and ignored on receipt. 3.2. Defined TLVs The following TLV Types are defined: Code Type ==== ================================ + 0x00 Reserved 0x01 Mtrace2 Query 0x02 Mtrace2 Request 0x03 Mtrace2 Reply 0x04 Mtrace2 Standard Response Block 0x05 Mtrace2 Augmented Response Block 0x06 Mtrace2 Extended Query Block Each Mtrace2 message MUST begin with either a Query, Request or Reply TLV. The first TLV determines the type of each Mtrace2 message. Following a Query TLV, there can be a sequence of optional Extended @@ -936,24 +937,24 @@ blocks filled in, and uses TLV type of 0x01. 4.1.1. Query Packet Verification 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 9.2. + Mtrace2 supports a non-local client to the LHR/RP. A router MUST, + however, support a mechanism to drop Queries from clients beyond a + specified administrative boundary. The potential approaches 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.