draft-ietf-mpls-3209-patherr-03.txt		draft-ietf-mpls-3209-patherr-04.txt
	Networking Working Group JP. Vasseur, Ed.		Networking Working Group JP. Vasseur, Ed.
	Internet-Draft George. Swallow		Internet-Draft George. Swallow
	Intended status: BCP Cisco Systems, Inc		Intended status: BCP Cisco Systems, Inc
	Expires: February 19, 2009 Ina. Minei		Expires: August 6, 2009 Ina. Minei
	Juniper Networks		Juniper Networks
	August 18, 2008		February 2, 2009
	Node behavior upon originating and receiving Resource ReserVation		Node behavior upon originating and receiving Resource ReserVation
	Protocol (RSVP) Path Error message		Protocol (RSVP) Path Error message
	draft-ietf-mpls-3209-patherr-03.txt		draft-ietf-mpls-3209-patherr-04.txt
	Status of this Memo		Status of this Memo
	By submitting this Internet-Draft, each author represents that any		This Internet-Draft is submitted to IETF in full conformance with the
	applicable patent or other IPR claims of which he or she is aware		provisions of BCP 78 and BCP 79.
	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.
	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
	other groups may also distribute working documents as Internet-		other groups may also distribute working documents as Internet-
	Drafts.		Drafts.
	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."
	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.
	This Internet-Draft will expire on February 19, 2009.		This Internet-Draft will expire on August 6, 2009.
			Copyright Notice
			Copyright (c) 2009 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
			carefully, as they describe your rights and restrictions with respect
			to this document.
	Abstract		Abstract
	The aim of this document is to describe a common practice with regard		The aim of this document is to describe a common practice with regard
	to the behavior of a node sending a Resource ReserVation Protocol		to the behavior of a node sending a Resource ReserVation Protocol
	(RSVP) Traffic Engineering (TE) Path Error message and to the		(RSVP) Traffic Engineering (TE) Path Error message and to the
	behavior of a node receiving an RSVP Path Error message for a		behavior of a node receiving an RSVP Path Error message for a
	preempted Multi-Protocol Label Switching (MPLS) Traffic Engineering		preempted Multi-Protocol Label Switching (MPLS) Traffic Engineering
	Label Switched Path (TE LSP). This document does not define any new		Label Switched Path (TE LSP). This document does not define any new
	protocol extensions.		protocol extensions.
	skipping to change at page 2, line 24		skipping to change at page 3, line 4
	2. Protocol behavior . . . . . . . . . . . . . . . . . . . . . . . 3		2. Protocol behavior . . . . . . . . . . . . . . . . . . . . . . . 3
	2.1. Behavior at Detecting Nodes . . . . . . . . . . . . . . . . 4		2.1. Behavior at Detecting Nodes . . . . . . . . . . . . . . . . 4
	2.2. Behavior at Receiving Nodes . . . . . . . . . . . . . . . . 5		2.2. Behavior at Receiving Nodes . . . . . . . . . . . . . . . . 5
	2.3. Data Plane Behavior . . . . . . . . . . . . . . . . . . . . 5		2.3. Data Plane Behavior . . . . . . . . . . . . . . . . . . . . 5
	3. RSVP PathErr Messages For a Preempted TE LSP . . . . . . . . . 5		3. RSVP PathErr Messages For a Preempted TE LSP . . . . . . . . . 5
	4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5		4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
	5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6		5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
	6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6		6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 6
	7. Normative References . . . . . . . . . . . . . . . . . . . . . 6		7. Normative References . . . . . . . . . . . . . . . . . . . . . 6
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 6
	Intellectual Property and Copyright Statements . . . . . . . . . . 8
	1. Introduction		1. Introduction
	The aim of this document is to describe a common practice with regard		The aim of this document is to describe a common practice with regard
	to the behavior of a node sending a Resource ReserVation Protocol		to the behavior of a node sending a Resource ReserVation Protocol
	(RSVP) Traffic Engineering (TE) Path Error message and to the		(RSVP) Traffic Engineering (TE) Path Error message and to the
	behavior of a node receiving an RSVP Path Error message for a		behavior of a node receiving an RSVP Path Error message for a
	preempted Multi-Protocol Label Switching (MPLS) Traffic Engineering		preempted Multi-Protocol Label Switching (MPLS) Traffic Engineering
	Label Switched Path (TE LSP).		Label Switched Path (TE LSP).
	skipping to change at page 8, line 4		skipping to change at line 273
	USA		USA
	Email: swallow@cisco.com		Email: swallow@cisco.com
	Ina Minei		Ina Minei
	Juniper Networks		Juniper Networks
	1194 North Mathilda Ave.		1194 North Mathilda Ave.
	Sunnyvale, 94089		Sunnyvale, 94089
	Email: ina@juniper.net		Email: ina@juniper.net
	Full Copyright Statement
	Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.
	This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Intellectual Property
	The IETF takes no position regarding the validity or scope of any
	Intellectual Property Rights or other rights that might be claimed to
	pertain to the implementation or use of the technology described in
	this document or the extent to which any license under such rights
	might or might not be available; nor does it represent that it has
	made any independent effort to identify any such rights. Information
	on the procedures with respect to rights in RFC documents can be
	found in BCP 78 and BCP 79.
	Copies of IPR disclosures made to the IETF Secretariat and any
	assurances of licenses to be made available, or the result of an
	attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.
End of changes. 7 change blocks.
	9 lines changed or deleted		18 lines changed or added
This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/