< draft-ietf-ccamp-rsvp-node-id-based-hello-02.txt		draft-ietf-ccamp-rsvp-node-id-based-hello-03.txt >
	Network Working Group Zafar Ali		Network Working Group Zafar Ali
	Internet Draft Reshad Rahman		Internet Draft Reshad Rahman
	Category: Proposed Standard Danny Prairie		Category: Proposed Standard Danny Prairie
	Expires: March 2005 Cisco Systems		Expires: September 2006 Cisco Systems
	D. Papadimitriou		D. Papadimitriou
	Alcatel		Alcatel
	September 2005		March 2006
	Node ID based RSVP Hello: A Clarification Statement		Node ID based RSVP Hello: A Clarification Statement
	draft-ietf-ccamp-rsvp-node-id-based-hello-02.txt		draft-ietf-ccamp-rsvp-node-id-based-hello-03.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 other		Task Force (IETF), its areas, and its working groups. Note that other
	skipping to change at page 1, line 39 ¶		skipping to change at page 1, line 39 ¶
	material or to cite them other than as "work in progress."		material or to cite them other than as "work in progress."
	The list of current Internet-Drafts can be accessed at		The list of current Internet-Drafts can be accessed at
	http://www.ietf.org/ietf/1id-abstracts.txt.		http://www.ietf.org/ietf/1id-abstracts.txt.
	The list of Internet-Draft Shadow Directories can be accessed at		The list of Internet-Draft Shadow Directories can be accessed at
	http://www.ietf.org/shadow.html.		http://www.ietf.org/shadow.html.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005). All Rights Reserved.		Copyright (C) The Internet Society (2006). All Rights Reserved.
	Abstract		Abstract
	Use of Node-ID based RSVP Hello messages is implied in a number of		Use of Node-ID based RSVP Hello messages is implied in a number of
	cases, e.g., when data and control plan are separated, when TE links		cases, e.g., when data and control plan are separated, and when TE links
	are unnumbered. Furthermore, when link level failure detection is		are unnumbered. Nonetheless, this implied behavior is unclear
	performed by some means other than exchanging RSVP Hello messages,
	use of Node-ID based Hello session is optimal for detecting signaling
	adjacency failure for Resource reSerVation Protocol-Traffic
	Engineering (RSVP-TE). Nonetheless, this implied behavior is unclear
	and this document formalizes use of Node-ID based RSVP Hello session		and this document formalizes use of Node-ID based RSVP Hello session
	as a best current practice (BCP) in some scenarios. The procedure		in some scenarios. The procedure described in this document applies
	described in this document applies to both Multi-Protocol Label		to both Multi-Protocol Label Switching (MPLS) and Generalized MPLS
	Switching (MPLS) and Generalized MPLS (GMPLS) capable nodes.		(GMPLS) capable nodes.
			When link level failure detection is performed by some means other
			than exchanging RSVP Hello messages, use of Node-ID based Hello
			session is optimal for detecting signaling adjacency failure for
			Resource reSerVation Protocol-Traffic Engineering (RSVP-TE). The use
			of Node-ID based Hello session is optimal in the sense that as long as
			there is IP reachability to the nieghbor (node-id), the signalling
			adjacency will remain up.
	Conventions used in this document		Conventions used in this document
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this		"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
	document are to be interpreted as described in RFC 2119 [RFC2119].		document are to be interpreted as described in RFC 2119 [RFC2119].
	1. Terminology		1. Terminology
	Node-ID: TE Router ID as advertised in the Router Address TLV for		Node-ID: TE Router ID as advertised in the Router Address TLV for
	skipping to change at page 7, line 41 ¶		skipping to change at page 7, line 41 ¶
	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 AND THE INTERNET		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
	ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,		ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
	INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE		INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
	INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		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.
	Copyright Statement		Copyright Statement
	Copyright (C) The Internet Society (2005). This document is subject		Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and		to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.		except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is currently provided by the
	Internet Society.		Internet Society.
End of changes. 7 change blocks.
	14 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/