draft-ietf-mboned-mtrace-v2-25.txt		draft-ietf-mboned-mtrace-v2-26.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: January 26, 2019		Expires: February 1, 2019
	W. Lee, Ed.		W. Lee, Ed.
	July 25, 2018		July 31, 2018
	Mtrace Version 2: Traceroute Facility for IP Multicast		Mtrace Version 2: Traceroute Facility for IP Multicast
	draft-ietf-mboned-mtrace-v2-25		draft-ietf-mboned-mtrace-v2-26
	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 https://datatracker.ietf.org/drafts/current/.		Drafts is at https://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 January 26, 2019.		This Internet-Draft will expire on February 1, 2019.
	Copyright Notice		Copyright Notice
	Copyright (c) 2018 IETF Trust and the persons identified as the		Copyright (c) 2018 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
	(https://trustee.ietf.org/license-info) in effect on the date of		(https://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 9, line 7 ¶		skipping to change at page 9, line 7 ¶
	The format is based on the Type value. The length of the value		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 is Length field minus 3. All reserved fields in the Value
	field MUST be transmitted as zeros and ignored on receipt.		field MUST be transmitted as zeros and ignored on receipt.
	3.2. Defined TLVs		3.2. Defined TLVs
	The following TLV Types are defined:		The following TLV Types are defined:
	Code Type		Code Type
	==== ================================		==== ================================
			0x00 Reserved
	0x01 Mtrace2 Query		0x01 Mtrace2 Query
	0x02 Mtrace2 Request		0x02 Mtrace2 Request
	0x03 Mtrace2 Reply		0x03 Mtrace2 Reply
	0x04 Mtrace2 Standard Response Block		0x04 Mtrace2 Standard Response Block
	0x05 Mtrace2 Augmented Response Block		0x05 Mtrace2 Augmented Response Block
	0x06 Mtrace2 Extended Query Block		0x06 Mtrace2 Extended Query Block
	Each Mtrace2 message MUST begin with either a Query, Request or Reply		Each Mtrace2 message MUST begin with either a Query, Request or Reply
	TLV. The first TLV determines the type of each Mtrace2 message.		TLV. The first TLV determines the type of each Mtrace2 message.
	Following a Query TLV, there can be a sequence of optional Extended		Following a Query TLV, there can be a sequence of optional Extended
	skipping to change at page 10, line 22 ¶		skipping to change at page 10, line 22 ¶
	| |		| |
	+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+		+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+
	| |		| |
	| Source Address |		| Source Address |
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	| Mtrace2 Client Address |		| Mtrace2 Client Address |
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Query ID | Client Port # |		| Query ID | Client Port # |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Figure 2		Figure 2
	Length: 16 bits		Length: 16 bits
	The length field MUST be either 20 (i.e., 8 plus 3 * 4 (IPv4		The length field MUST be either 20 (i.e., 8 plus 3 * 4 (IPv4
	addresses)) or 56 (i.e., 8 + 3 * 16 (IPv6 addresses)); if the		addresses)) or 56 (i.e., 8 + 3 * 16 (IPv6 addresses)); if the
	length is 20, then IPv4 addresses MUST be assumed and if the		length is 20, then IPv4 addresses MUST be assumed and if the
	length is 56, then IPv6 addresses MUST be assumed.		length is 56, then IPv6 addresses MUST be assumed.
	skipping to change at page 21, line 40 ¶		skipping to change at page 21, line 40 ¶
	blocks filled in, and uses TLV type of 0x01.		blocks filled in, and uses TLV type of 0x01.
	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 MUST,
	however, support a mechanism to filter out queries from clients		however, support a mechanism to drop Queries from clients beyond a
	beyond a specified administrative boundary. The potential approaches		specified administrative boundary. The potential approaches are
	are described in Section 9.2.		described in Section 9.2.
	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. 7 change blocks.
	9 lines changed or deleted		10 lines changed or added
This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/