draft-ietf-mpls-remote-lsp-ping-00.txt		draft-ietf-mpls-remote-lsp-ping-01.txt
	Network Working Group George Swallow		Network Working Group George Swallow
	Internet Draft Cisco Systems, Inc.		Internet Draft Cisco Systems, Inc.
	Category: Standards Track		Category: Standards Track
	Expiration Date: October 2007
	Vanson Lim		Vanson Lim
	Cisco Systems, Inc.		Cisco Systems, Inc.
			November 2007
	Proxy LSP Ping		Proxy LSP Ping
	draft-ietf-mpls-remote-lsp-ping-00.txt		draft-ietf-mpls-remote-lsp-ping-01.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		By submitting this Internet-Draft, each author represents that any
	applicable patent or other IPR claims of which he or she is aware		applicable patent or other IPR claims of which he or she is aware
	have been or will be disclosed, and any of which he or she becomes		have been or will be disclosed, and any of which he or she becomes
	aware will be disclosed, in accordance with Section 6 of BCP 79.		aware will be disclosed, in accordance with Section 6 of BCP 79.
	Internet-Drafts are working documents of the Internet Engineering		Internet-Drafts are working documents of the Internet Engineering
	Task Force (IETF), its areas, and its working groups. Note that		Task Force (IETF), its areas, and its working groups. Note that
	skipping to change at page 2, line 21		skipping to change at page 2, line 21
	3.1 Procedures for the initiator .............................. 5		3.1 Procedures for the initiator .............................. 5
	3.2 Procedures for the proxy LSR .............................. 6		3.2 Procedures for the proxy LSR .............................. 6
	3.2.1 Sending an MPLS proxy ping reply .......................... 7		3.2.1 Sending an MPLS proxy ping reply .......................... 7
	3.2.2 Sending the MPLS echo requests ............................ 7		3.2.2 Sending the MPLS echo requests ............................ 7
	4 Proxy Ping Request / Reply Messages ....................... 8		4 Proxy Ping Request / Reply Messages ....................... 8
	4.1 Proxy Ping Request / Reply Message formats ................ 9		4.1 Proxy Ping Request / Reply Message formats ................ 9
	4.2 Proxy Ping Request Message contents ....................... 10		4.2 Proxy Ping Request Message contents ....................... 10
	4.3 Proxy Ping Reply Message Contents ......................... 10		4.3 Proxy Ping Reply Message Contents ......................... 10
	5 Object formats ............................................ 11		5 Object formats ............................................ 11
	5.1 Proxy Echo Parameters Object .............................. 11		5.1 Proxy Echo Parameters Object .............................. 11
	5.2 Previous Hop Object ....................................... 13		5.2 Reply-to Address Object ................................... 12
			5.3 Previous Hop Address Object ............................... 13
	6 Security Considerations ................................... 13		6 Security Considerations ................................... 13
	7 IANA Considerations ....................................... 13		7 IANA Considerations ....................................... 13
	7.1 Message and Object Type Assignments ....................... 13		7.1 Message and Object Type Assignments ....................... 14
	7.2 Return Code Assignments ................................... 14		7.2 Return Code Assignments ................................... 14
	8 Acknowledgments ........................................... 14		8 Acknowledgments ........................................... 14
	9 References ................................................ 14		9 References ................................................ 14
	9.1 Normative References ...................................... 14		9.1 Normative References ...................................... 14
	9.2 Informative References .................................... 14		9.2 Informative References .................................... 15
	10 Authors' Addresses ........................................ 15		10 Authors' Addresses ........................................ 15
	1. Introduction		1. Introduction
	It is anticipated that very large Point-to-Multipoint (P2MP) Label		It is anticipated that very large Point-to-Multipoint (P2MP) Label
	Switched Paths (LSPs) will exist. Further it is anticipated that		Switched Paths (LSPs) will exist. Further it is anticipated that
	many of the applications for P2MP tunnels will require OAM that is		many of the applications for P2MP tunnels will require OAM that is
	both rigorous and scalable.		both rigorous and scalable.
	Suppose one wishes to trace a P2MP LSP to localize a fault which is		Suppose one wishes to trace a P2MP LSP to localize a fault which is
	skipping to change at page 4, line 45		skipping to change at page 4, line 45
	The proxy LSR validates that it has a label mapping for the specified		The proxy LSR validates that it has a label mapping for the specified
	FEC and that it is authorized to send the specified MPLS echo request		FEC and that it is authorized to send the specified MPLS echo request
	on behalf of the initiator. Depending on the Reply Mode carried in		on behalf of the initiator. Depending on the Reply Mode carried in
	the header of the proxy ping request message and the above results an		the header of the proxy ping request message and the above results an
	MPLS remote echo reply message might be sent back to the initiator.		MPLS remote echo reply message might be sent back to the initiator.
	This message may also communicate the address of the previous hop.		This message may also communicate the address of the previous hop.
	If the proxy LSR has a label mapping for the FEC and and all autho-		If the proxy LSR has a label mapping for the FEC and and all autho-
	rization check have passed, the proxy LSR formats an MPLS echo		rization check have passed, the proxy LSR formats an MPLS echo
	request. If the source address of the IP packet is not the initia-		request. If the source address of the IP packet is not the initia-
	tor, it includes a ReplyTo object containing the initiator's address.		tor, it includes a Reply-to Address object containing the initiator's
	It then sends it inband of the LSP.		address. It then sends it inband of the LSP.
	The receivers process the MPLS echo request as normal, sending their		The receivers process the MPLS echo request as normal, sending their
	MPLS echo replies back to the initiator.		MPLS echo replies back to the initiator.
	3. Remote Echo / Reply Pprocedures		3. Remote Echo / Reply Pprocedures
	3.1. Procedures for the initiator		3.1. Procedures for the initiator
	The initiator creates an MPLS proxy ping request message.		The initiator creates an MPLS proxy ping request message.
	skipping to change at page 6, line 40		skipping to change at page 6, line 40
	The proxy LSR then determines if it is authorized to send the speci-		The proxy LSR then determines if it is authorized to send the speci-
	fied MPLS echo request on behalf of the initiator. An LSR MUST be		fied MPLS echo request on behalf of the initiator. An LSR MUST be
	capable of filtering addresses to validate initiators. Other filters		capable of filtering addresses to validate initiators. Other filters
	on FECs or MPLS echo request contents MAY be applied. If a filter		on FECs or MPLS echo request contents MAY be applied. If a filter
	has been invoked (i.e. configured) and an address does not pass the		has been invoked (i.e. configured) and an address does not pass the
	filter, then an MPLS echo request message MUST NOT be sent, and the		filter, then an MPLS echo request message MUST NOT be sent, and the
	event SHOULD be logged. An MPLS proxy ping reply message may be sent		event SHOULD be logged. An MPLS proxy ping reply message may be sent
	with a Return Code of <tba>, "Remote Ping not authorized".		with a Return Code of <tba>, "Remote Ping not authorized".
	If the "Request for Previous Hop" flag is set, a PHOP Address Object		If the "Request for Previous Hop" flag is set, a Previous Hop Address
	is formatted for inclusion in the MPLS proxy ping reply. If the pre-		Object is formatted for inclusion in the MPLS proxy ping reply. If
	vious HOP is unknown or ambiguous the Address Type is set to "No		the previous HOP is unknown or ambiguous the Address Type is set to
	Address Supplied".		"No Address Supplied".
	If there is a list of Next Hop addresses in the Proxy Echo Parameters		If there is a list of Next Hop addresses in the Proxy Echo Parameters
	object, each address is examined to determine if it is a next hop for		object, each address is examined to determine if it is a next hop for
	this FEC. If any are not, those addresses are deleted from the list.		this FEC. If any are not, those addresses are deleted from the list.
	The updated Proxy Echo Parameters object is included in the MPLS		The updated Proxy Echo Parameters object is included in the MPLS
	proxy ping reply.		proxy ping reply.
	If the "Request for Downstream Mapping" flag is set the LSR formats a		If the "Request for Downstream Mapping" flag is set the LSR formats a
	Downstream Mapping object for each interface that the MPLS echo		Downstream Mapping object for each interface that the MPLS echo
	request will be sent out.		request will be sent out.
	skipping to change at page 7, line 45		skipping to change at page 7, line 45
	Flags and Reply Mode are copied from the Proxy Echo Parameters		Flags and Reply Mode are copied from the Proxy Echo Parameters
	object. The Return Code and Return Subcode are set to zero.		object. The Return Code and Return Subcode are set to zero.
	The Sender's Handle and Sequence Number are copied from the remote		The Sender's Handle and Sequence Number are copied from the remote
	echo request message.		echo request message.
	The TimeStamp Sent is set to the time-of-day (in seconds and		The TimeStamp Sent is set to the time-of-day (in seconds and
	microseconds) that the echo request is sent. The TimeStamp Received		microseconds) that the echo request is sent. The TimeStamp Received
	is set to zero.		is set to zero.
	A ReplyTo object (see [SelfTest]) containing the initiator's address		A Reply-to Address object containing the initiator's address is
	is included.		included.
	The following objects are copied from the MPLS proxy ping request		The following objects are copied from the MPLS proxy ping request
	message. Note that of these, only the Target FEC Stack is REQUIRED		message. Note that of these, only the Target FEC Stack is REQUIRED
	to appear in the MPLS proxy ping request message.		to appear in the MPLS proxy ping request message.
	Target FEC Stack		Target FEC Stack
	Pad		Pad
	Vendor Enterprise Number		Vendor Enterprise Number
	Reply TOS Byte		Reply TOS Byte
	P2MP Egress Identifier [McstPing]		P2MP Egress Identifier [McstPing]
	skipping to change at page 10, line 32		skipping to change at page 10, line 32
	objects:		objects:
	Type Object		Type Object
	---- -----------		---- -----------
	1 Target FEC Stack		1 Target FEC Stack
	2 Downstream Mapping		2 Downstream Mapping
	3 Pad		3 Pad
	5 Vendor Enterprise Number		5 Vendor Enterprise Number
	10 Reply TOS Byte		10 Reply TOS Byte
	tba Proxy Echo Parameters		tba Proxy Echo Parameters
	tba PHOP Address
	tba P2MP Egress Identifier [McstPing]		tba P2MP Egress Identifier [McstPing]
	tba Echo Jitter TLV [McstPing]		tba Echo Jitter TLV [McstPing]
	Vendor Private TLVs		Vendor Private TLVs
	4.3. Proxy Ping Reply Message Contents		4.3. Proxy Ping Reply Message Contents
	The MPLS proxy ping reply message MAY contain the following objects:		The MPLS proxy ping reply message MAY contain the following objects:
	Type Object		Type Object
	---- -----------		---- -----------
	1 Target FEC Stack		1 Target FEC Stack
	2 Downstream Mapping		2 Downstream Mapping
	5 Vendor Enterprise Number		5 Vendor Enterprise Number
	9 Errored TLVs		9 Errored TLVs
	tba Proxy Echo Parameters		tba Proxy Echo Parameters
	tba PHOP Address		tba Previous Hop Address
	Vendor Private objects		Vendor Private objects
	5. Object formats		5. Object formats
	5.1. Proxy Echo Parameters Object		5.1. Proxy Echo Parameters Object
	0 1 2 3		0 1 2 3
	0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1		0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Address Type | Flags | Reply mode | TTL |		| Address Type | Flags | Reply mode | TTL |
	skipping to change at page 12, line 4		skipping to change at page 11, line 37
	Address Type		Address Type
	The type of address found in the in the Destination IP Address		The type of address found in the in the Destination IP Address
	and Next Hop IP Addresses fields. The type codes appear in the		and Next Hop IP Addresses fields. The type codes appear in the
	table below:		table below:
	Address Family Type		Address Family Type
	IPv4 Numbered 1		IPv4 Numbered 1
	IPv6 Numbered 3		IPv6 Numbered 3
	Flags		Flags
	Request for Previous Hop 0x01		Request for Previous Hop 0x01
	When set this requests that the proxy LSR supply the PHOP		When set this requests that the proxy LSR supply the previous hop
	address in the MPLS proxy ping reply message		address in the MPLS proxy ping reply message
	Request for Downstream Mapping 0x02		Request for Downstream Mapping 0x02
	When set this requests that the proxy LSR supply a		When set this requests that the proxy LSR supply a
	Downstream Mapping object in the MPLS proxy ping reply		Downstream Mapping object in the MPLS proxy ping reply
	message		message
	Reply mode		Reply mode
	The reply mode to be sent in the MPLS Echo Request message; the		The reply mode to be sent in the MPLS Echo Request message; the
	values are as specified in [RFC4379]		values are as specified in [RFC4379]
	TTL		TTL
	The TTL to be used in the label corresponding to the FEC in the		The TTL to be used in the label corresponding to the FEC in the
	MPLS Echo Request packet		MPLS Echo Request packet
	skipping to change at page 13, line 5		skipping to change at page 12, line 33
	If the Address Type is IPv4, an address from the range 127/8;		If the Address Type is IPv4, an address from the range 127/8;
	If the Address Type is IPv6, an address from the range		If the Address Type is IPv6, an address from the range
	0:0:0:0:0:FFFF:127/104		0:0:0:0:0:FFFF:127/104
	Next Hop IP Addresses		Next Hop IP Addresses
	A list of next hop address that the echo request message is to		A list of next hop address that the echo request message is to
	be sent towards		be sent towards
	5.2. Previous Hop Object		5.2. Reply-to Address Object
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| Address Type | MUST be Zero |		| Address Type | MUST be Zero |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	| |		| |
	: Previous Hop IP Address :		: Reply-to Address :
			| |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			Address Type
			A type code as specified in the table below:
			Type Type of Address
			1 IPv4
			3 IPv6
			5.3. Previous Hop Address Object
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| Address Type | MUST be Zero |
			+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
			| |
			: Previous Hop Address :
	| |		| |
	+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+		+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
	Address Type		Address Type
	A type code as specified in the table below:		A type code as specified in the table below:
	Type Type of Address		Type Type of Address
	0 No Address Supplied		0 No Address Supplied
	skipping to change at page 13, line 44		skipping to change at page 14, line 16
	This document makes the following codepoint assigments (pending IANA		This document makes the following codepoint assigments (pending IANA
	action):		action):
	Registry Codepoint Purpose		Registry Codepoint Purpose
	LSP Ping Message Type tba MPLS proxy ping request message		LSP Ping Message Type tba MPLS proxy ping request message
	tba MPLS proxy ping reply		tba MPLS proxy ping reply
	LSP Ping Object Type tba Proxy Echo Parameters		LSP Ping Object Type tba Proxy Echo Parameters
	tba PHOP Address		tba Reply-to Address
			tba Previous Hop Address
	7.2. Return Code Assignments		7.2. Return Code Assignments
	Value Meaning		Value Meaning
	tba Remote Ping not authorized		tba Remote Ping not authorized
	tba Failed Next Hops
	8. Acknowledgments		8. Acknowledgments
	9. References		9. References
	9.1. Normative References		9.1. Normative References
	[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol		[RFC4379] Kompella, K. and G. Swallow, "Detecting Multi-Protocol
	Label Switched (MPLS) Data Plane Failures", RFC 4379,		Label Switched (MPLS) Data Plane Failures", RFC 4379,
	February 2006.		February 2006.
	[SelfTest] Swallow, G. et al., "LSR Self Test",
	draft-ietf-mpls-lsr-self-test-06.txt, October 2005.
	[KeyWords] Bradner, S., "Key words for use in RFCs to Indicate		[KeyWords] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	[McstPing] Farrel, A. et al, "Detecting Data Plane Failures in		[McstPing] Farrel, A. et al, "Detecting Data Plane Failures in
	Point-to-Multipoint MPLS Traffic Engineering -		Point-to-Multipoint MPLS Traffic Engineering -
	Extensions to LSP Ping",		Extensions to LSP Ping",
	draft-ietf-mpls-p2mp-lsp-ping-02.txt, September 2006.		draft-ietf-mpls-p2mp-lsp-ping-02.txt, September 2006.
	9.2. Informative References		9.2. Informative References
	skipping to change at page 17, line 4		skipping to change at line 659
	rights, licenses and restrictions contained in BCP 78, and except as		rights, licenses and restrictions contained in BCP 78, and except as
	set forth therein, the authors retain all their rights.		set forth therein, the authors retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Notes:
	Indication leaf, bud etc. Look at [McstPing] need to discuss with
	Adrian. New Downstream mapping thingy
	Inclusion of multiple Downstream Mapping
	Multiple FECs in FEC Stack
	partial rules for FEC processing
	Node must recognize top FEC;
	Must recognize FEC subsequent FECs if the previous operation was
	POP
	PHOP/Downstream only request???
	Specification of TOS byte for MPLS proxy ping reply???
	Container for other objects?
	Multiple DS maps; grouping by nexthop.
	proxy echo parameters - change MBZ to Global Flags with none defined?
	version number should be added to message description.
	TTL values for additional labels
	IANA Registry name is hopelessly confusing!
	"Label Switched Paths (LSPs) Parameters - Message Types"
	Flags MAY be set to request use of either the ingress' source address
	or the initiators source address.
	If the "Ingress Source Address" flag is set and the proxy LSR is con-
	figured to allow to use the ingress address, the proxy LSR determines
	the ingress LSR. If the address is found, it is used as the source
	address of the MPLS echo request. Otherwise the Return Code is set
	to <tba>, "Unable to use ingress source address". If the Reply Mode
	of the message header is not 0, an MPLS proxy ping reply message
	SHOULD be sent as described below.
	If either the "Initiator Source Address" or "Initiator Source
	Address" flags is set, the source address is set as specified. Oth-
	erwise
	If the "Initiator Source Address" flag is set and the proxy LSR is
	configured to allow to use the iniator's address it is used as the
	source address of the MPLS echo request. Otherwise the Return Code
	is set to <tba>, "Unable to use intiator source address". If the
	Reply Mode of the message header is not 0, an MPLS proxy ping reply
	message SHOULD be sent as described below.
	Ingress Source Address 0x04
	When set this requests that the address of the ingress of
	the LSP be used as the source address of the MPLS echo
	request packet
	Initiator Source Address 0x08
	When set this requests that the address of the initiator be
	used as the source address of the MPLS echo request packet
	tba Unable to use ingress source address
	tba Unable to use initiator source address
End of changes. 20 change blocks.
	24 lines changed or deleted		40 lines changed or added
This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/