draft-ietf-mboned-mtrace-v2-13.txt		draft-ietf-mboned-mtrace-v2-14.txt
	MBONED Working Group H. Asaeda		MBONED Working Group H. Asaeda
	Internet-Draft NICT		Internet-Draft NICT
	Intended status: Standards Track K. Meyer		Intended status: Standards Track K. Meyer
	Expires: December 7, 2016 Cisco		Expires: February 1, 2017 Cisco
	W. Lee, Ed.		W. Lee, Ed.
	June 5, 2016		July 31, 2016
	Mtrace Version 2: Traceroute Facility for IP Multicast		Mtrace Version 2: Traceroute Facility for IP Multicast
	draft-ietf-mboned-mtrace-v2-13		draft-ietf-mboned-mtrace-v2-14
	Abstract		Abstract
	This document describes the IP multicast traceroute facility, named		This document describes the IP multicast traceroute facility, named
	Mtrace version 2 (Mtrace2). Unlike unicast traceroute, Mtrace2		Mtrace version 2 (Mtrace2). Unlike unicast traceroute, Mtrace2
	requires special implementations on the part of routers. This		requires special implementations on the part of routers. This
	specification describes the required functionality in multicast		specification describes the required functionality in multicast
	routers, as well as how an Mtrace2 client invokes a query and		routers, as well as how an Mtrace2 client invokes a query and
	receives a reply.		receives a reply.
	skipping to change at page 1, line 37 ¶		skipping to change at page 1, line 37 ¶
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF). Note that other groups may also distribute		Task Force (IETF). Note that other groups may also distribute
	working documents as Internet-Drafts. The list of current Internet-		working documents as Internet-Drafts. The list of current Internet-
	Drafts is at http://datatracker.ietf.org/drafts/current/.		Drafts is at http://datatracker.ietf.org/drafts/current/.
	Internet-Drafts are draft documents valid for a maximum of six months		Internet-Drafts are draft documents valid for a maximum of six months
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		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 Notice
	Copyright (c) 2016 IETF Trust and the persons identified as the		Copyright (c) 2016 IETF Trust and the persons identified as the
	document authors. All rights reserved.		document authors. All rights reserved.
	This document is subject to BCP 78 and the IETF Trust's Legal		This document is subject to BCP 78 and the IETF Trust's Legal
	Provisions Relating to IETF Documents		Provisions Relating to IETF Documents
	(http://trustee.ietf.org/license-info) in effect on the date of		(http://trustee.ietf.org/license-info) in effect on the date of
	publication of this document. Please review these documents		publication of this document. Please review these documents
	skipping to change at page 6, line 47 ¶		skipping to change at page 6, line 47 ¶
	routing protocol. For instance, the address of ALL-PIM-		routing protocol. For instance, the address of ALL-PIM-
	ROUTERS.MCAST.NET [5] is '224.0.0.13' for IPv4 and 'ff02::d' for		ROUTERS.MCAST.NET [5] is '224.0.0.13' for IPv4 and 'ff02::d' for
	IPv6.		IPv6.
	3. Packet Formats		3. Packet Formats
	This section describes the details of the packet formats for Mtrace2		This section describes the details of the packet formats for Mtrace2
	messages.		messages.
	All Mtrace2 messages are encoded in TLV format (see Section 3.1). If		All Mtrace2 messages are encoded in TLV format (see Section 3.1). If
	an implementation receives an unknown TLV, it SHOULD ignored and		an implementation receives an unknown TLV, it SHOULD ignore and
	silently discarded the unknown TLV. If the length of a TLV exceeds		silently discard the unknown TLV. If the length of a TLV exceeds the
	the length specified in the TLV, the TLV SHOULD be accepted; however,		length specified in the TLV, the TLV SHOULD be accepted; however, any
	any additional data after the specified TLV length SHOULD be ignored.		additional data after the specified TLV length SHOULD be ignored.
	All Mtrace2 messages are UDP packets. For IPv4, Mtrace2 Query and		All Mtrace2 messages are UDP packets. For IPv4, Mtrace2 Query and
	Request messages MUST NOT be fragmented. For IPv6, the packet size		Request messages MUST NOT be fragmented. For IPv6, the packet size
	for the Mtrace2 messages MUST NOT exceed 1280 bytes, which is the		for the Mtrace2 messages MUST NOT exceed 1280 bytes, which is the
	smallest MTU for an IPv6 interface [2]. The source port is uniquely		smallest MTU for an IPv6 interface [2]. The source port is uniquely
	selected by the local host operating system. The destination port is		selected by the local host operating system. The destination port is
	the IANA reserved Mtrace2 port number (see Section 8). All Mtrace2		the IANA reserved Mtrace2 port number (see Section 8). All Mtrace2
	messages MUST have a valid UDP checksum.		messages MUST have a valid UDP checksum.
	Additionally, Mtrace2 supports both IPv4 and IPv6, but not mixed.		Additionally, Mtrace2 supports both IPv4 and IPv6, but not mixed.
	skipping to change at page 19, line 42 ¶		skipping to change at page 19, line 42 ¶
	4.1.1. Query Packet Verification		4.1.1. Query Packet Verification
	Upon receiving an Mtrace2 Query message, a router MUST examine		Upon receiving an Mtrace2 Query message, a router MUST examine
	whether the Multicast Address and the Source Address are a valid		whether the Multicast Address and the Source Address are a valid
	combination as specified in Section 3.2.1, and whether the Mtrace2		combination as specified in Section 3.2.1, and whether the Mtrace2
	Client Address is a valid IP unicast address. If either one is		Client Address is a valid IP unicast address. If either one is
	invalid, the Query MUST be silently ignored.		invalid, the Query MUST be silently ignored.
	Mtrace2 supports a non-local client to the LHR/RP. A router SHOULD,		Mtrace2 supports a non-local client to the LHR/RP. A router SHOULD,
	however, support a mechanism to filter out queries from clients		however, support a mechanism to filter out queries from clients
	beyond a specified administrative boundary. Such a boundary could,		beyond a specified administrative boundary. The potential approaches
	for example, be specified via a list of allowed/disallowed client		are described in Section 8.
	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.
	In the case where a local LHR client is required, the router must		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		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		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		has a multicast-capable interface on the same subnet as the Mtrace2
	Client Address and is the router that would forward traffic from the		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		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		multicast group address specified in the query is 0 and if the IP
	header destination address is a valid RP address on this router.		header destination address is a valid RP address on this router.
End of changes. 6 change blocks.
	13 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/