--- 1/draft-ietf-mboned-mtrace-v2-13.txt 2016-07-31 20:16:54.565188385 -0700 +++ 2/draft-ietf-mboned-mtrace-v2-14.txt 2016-07-31 20:16:54.637190257 -0700 @@ -1,20 +1,20 @@ MBONED Working Group H. Asaeda Internet-Draft NICT Intended status: Standards Track K. Meyer -Expires: December 7, 2016 Cisco +Expires: February 1, 2017 Cisco W. Lee, Ed. - June 5, 2016 + July 31, 2016 Mtrace Version 2: Traceroute Facility for IP Multicast - draft-ietf-mboned-mtrace-v2-13 + draft-ietf-mboned-mtrace-v2-14 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 December 7, 2016. + This Internet-Draft will expire on February 1, 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 @@ -273,24 +273,24 @@ routing protocol. For instance, the address of ALL-PIM- ROUTERS.MCAST.NET [5] is '224.0.0.13' for IPv4 and 'ff02::d' for IPv6. 3. Packet Formats This section describes the details of the packet formats for Mtrace2 messages. All Mtrace2 messages are encoded in TLV format (see Section 3.1). If - an implementation receives an unknown TLV, it SHOULD ignored and - silently discarded the unknown TLV. If the length of a TLV exceeds - the length specified in the TLV, the TLV SHOULD be accepted; however, - any additional data after the specified TLV length SHOULD be ignored. + an implementation receives an unknown TLV, it SHOULD ignore and + silently discard the unknown TLV. If the length of a TLV exceeds the + length specified in the TLV, the TLV SHOULD be accepted; however, any + additional data after the specified TLV length SHOULD be ignored. All Mtrace2 messages are UDP packets. For IPv4, Mtrace2 Query and Request messages MUST NOT be fragmented. For IPv6, the packet size for the Mtrace2 messages MUST NOT exceed 1280 bytes, which is the smallest MTU for an IPv6 interface [2]. The source port is uniquely selected by the local host operating system. The destination port is the IANA reserved Mtrace2 port number (see Section 8). All Mtrace2 messages MUST have a valid UDP checksum. Additionally, Mtrace2 supports both IPv4 and IPv6, but not mixed. @@ -866,25 +866,22 @@ 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. Such a boundary could, - for example, be specified via a list of allowed/disallowed client - addresses or subnets. If a query is received from beyond the - specified administrative boundary, the Query MUST NOT be processed. - The router MAY, however, perform rate limited logging of such events. + beyond a specified administrative boundary. The potential approaches + are described in Section 8. 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.