draft-ietf-mpls-3209-patherr-02.txt | draft-ietf-mpls-3209-patherr-03.txt | |||
---|---|---|---|---|
Networking Working Group JP. Vasseur, Ed. | Networking Working Group JP. Vasseur, Ed. | |||
Internet-Draft George. Swallow | Internet-Draft George. Swallow | |||
Intended status: Best Current Cisco Systems, Inc | Intended status: BCP Cisco Systems, Inc | |||
Practice Ina. Minei | Expires: February 19, 2009 Ina. Minei | |||
Expires: August 21, 2008 Juniper Networks | Juniper Networks | |||
February 18, 2008 | August 18, 2008 | |||
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-02.txt | draft-ietf-mpls-3209-patherr-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 | Task Force (IETF), its areas, and its working groups. Note that | |||
skipping to change at page 1, line 36 | skipping to change at page 1, line 36 | |||
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 August 21, 2008. | This Internet-Draft will expire on February 19, 2009. | |||
Copyright Notice | ||||
Copyright (C) The IETF Trust (2008). | ||||
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 8, line 44 | skipping to change at line 303 | |||
attempt made to obtain a general license or permission for the use of | attempt made to obtain a general license or permission for the use of | |||
such proprietary rights by implementers or users of this | such proprietary rights by implementers or users of this | |||
specification can be obtained from the IETF on-line IPR repository at | specification can be obtained from the IETF on-line IPR repository at | |||
http://www.ietf.org/ipr. | http://www.ietf.org/ipr. | |||
The IETF invites any interested party to bring to its attention any | The IETF invites any interested party to bring to its attention any | |||
copyrights, patents or patent applications, or other proprietary | copyrights, patents or patent applications, or other proprietary | |||
rights that may cover technology that may be required to implement | rights that may cover technology that may be required to implement | |||
this standard. Please address the information to the IETF at | this standard. Please address the information to the IETF at | |||
ietf-ipr@ietf.org. | ietf-ipr@ietf.org. | |||
Acknowledgment | ||||
Funding for the RFC Editor function is provided by the IETF | ||||
Administrative Support Activity (IASA). | ||||
End of changes. 4 change blocks. | ||||
10 lines changed or deleted | 6 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/ |