[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]
Versions: (draft-berger-ccamp-gmpls-segment-recovery)
00 01 02 03 RFC 4873
Internet Draft Lou Berger (LabN)
Updates: 3473, [E2E-RECOVERY] Igor Bryskin (Movaz Networks)
Category: Standards Track Dimitri Papadimitriou (Alcatel)
Expiration Date: April 2007 Adrian Farrel (Old Dog Consulting)
October 2006
GMPLS Based Segment Recovery
draft-ietf-ccamp-gmpls-segment-recovery-03.txt
Status of this Memo
By submitting this Internet-Draft, each author represents that any
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
aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet-
Drafts.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html
Abstract
This document describes protocol specific procedures for GMPLS
(Generalized Multi-Protocol Label Switching) RSVP-TE (Resource
ReserVation Protocol - Traffic Engineering) signaling extensions to
support label switched path (LSP) segment protection and restoration.
These extensions are intended to complement and be consistent with
the Extensions for End-to-End GMPLS-based Recovery. Implications and
interactions with Fast Reroute are also addressed. This document
also updates the handling of Notify_Request objects.
Berger, et al. [Page 1]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
Contents
1 Introduction .............................................. 3
2 Segment Recovery .......................................... 4
2.1 Segment Protection ........................................ 6
2.2 Segment Re-routing and Restoration ........................ 6
3 Association Object ........................................ 6
3.1 Format .................................................... 7
3.2 Procedures ................................................ 7
3.2.1 Recovery Type Processing .................................. 7
3.2.2 Resource Sharing Association Type Processing .............. 7
4 Explicit Control of LSP Segment Recovery .................. 8
4.1 Secondary Explicit Route Object Format .................... 8
4.1.1 Protection Subobject ...................................... 8
4.2 Explicit Control Procedures ............................... 9
4.2.1 Branch Failure Handling ................................... 11
4.2.2 Resv Message Processing ................................... 12
4.2.3 Admin Status Change ....................................... 12
4.2.4 Recovery LSP Tear Down .................................... 12
4.3 Tear Down From Non-Ingress Nodes .......................... 13
4.3.1 Modified Notify Request Object Processing ................. 13
4.3.2 Modified Notify and Error Message Processing .............. 14
5 Secondary Record Route Objects ............................ 15
5.1 Format .................................................... 15
5.2 Path Processing ........................................... 15
5.3 Resv Processing ........................................... 15
6 Dynamic Control of LSP Segment Recovery ................... 16
6.1 Modified Protection Object Format ......................... 16
6.2 Dynamic Control Procedures ................................ 17
7 Updated RSVP Message Formats .............................. 18
8 Security Considerations ................................... 20
9 IANA Considerations ....................................... 21
9.1 New Association Type Assignment ........................... 21
9.2 Definition of Protection Object Reserved Bits ............. 21
9.3 Secondary Explicit Route Object ........................... 21
9.4 Secondary Record Route Object ............................. 22
9.5 New Error Code ............................................ 22
9.6 Use of Not Yet Assigned Protection Object C-type .......... 22
10 References ................................................ 23
10.1 Normative References ...................................... 23
10.2 Informative References .................................... 23
11 Authors' Addresses ........................................ 24
12 Full Copyright Statement .................................. 24
13 Intellectual Property ..................................... 25
Berger, et al. [Page 2]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
In addition, the reader is assumed to be familiar with the
terminology used in [RFC3209], [RFC3471], [RFC3473] as well as
[RFC4427], [RFC4426], [E2E-RECOVERY] and [RFC4090].
1. Introduction
[RFC4427] covers multiple types of protection, including end-to-end
and segment based approaches. [E2E-RECOVERY], RSVP-TE Extensions in
support of End-to-End GMPLS-based Recovery, defines a set of
extensions to support multiple types of recovery. The supported
types include 1+1 unidirectional/ 1+1 bi-directional protection, LSP
protection with extra-traffic (including 1:N protection with extra-
traffic), pre-planned LSP re-routing without extra-traffic (including
shared mesh), and full LSP re-routing. In all cases, the recovery is
provided on an end-to-end basis, i.e., the ingress and egress nodes
of both the protected and the protecting LSP are the same.
[RFC4090] provides a form of segment recovery for packet MPLS-TE
networks. Two methods of Fast Reroute are defined in [RFC4090]. The
one-to-one backup method creates detour LSPs for each protected LSP
at each potential point of local repair. The facility backup method
creates a bypass tunnel to protect a potential failure point which is
shared by multiple LSPs and uses label stacking. Neither approach
supports the full set of recovery types supported by [E2E-RECOVERY].
Additionally, the facility backup method is not applicable to most
non-PSC (packet) switching technologies.
The extensions defined in this document allow for support of the full
set of recovery types supported by [E2E-RECOVERY], but on a segment,
or portion of the LSP, basis. The extensions allow (a) the signaling
of desired LSP segment protection type, (b) upstream nodes to
optionally identify where segment protection starts and stops, (c)
the optional identification of hops used on protection segments, and
(d) the reporting of paths used to protect an LSP. The extensions
also widen the topological scope over which protection can be
supported. They allow recovery segments that protect against an
arbitrary number of nodes and links. They enable overlapping
protection and nested protection. These extensions are intended to
be compatible with, and in some cases used with Fast Reroute.
Berger, et al. [Page 3]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
2. Segment Recovery
Segment recovery is used to provide protection and restoration over a
portion of an end-to-end LSP. Such segment protection and
restoration is useful to protect against a span failure, a node
failure, or failure over a particular portion of a network used by an
LSP.
Consider the following topology:
A---B---C---D---E---F
\ /
G---I
In this topology, end-to-end protection and recovery is not possible
for an LSP going between node A and node F, but it is possible to
protect/recover a portion of the LSP. Specifically, if the LSP uses
a working path of [A,B,C,D,E,F] then a protection or restoration LSP
can be established along the path [C,G,I,E]. This LSP protects
against failures on spans {C,D} and {D,E} as well as a failure of
node D. This form of protection/restoration is referred to as
Segment Protection and Segment Restoration, or Segment Recovery
collectively. The LSP providing the protection or restoration is
referred to as a segment protection LSP or a segment restoration LSP.
The term segment recovery LSP is used to cover either a segment
protection LSP or a segment restoration LSP. The term branch node is
used to refer to a node that initiates a recovery LSP, e.g., node C
in the figure shown above. This is equivalent to the point of local
repair (PLR) used in [RFC4090]. As with [RFC4090], the term merge
node is used to refer to a node that terminates a recovery LSP, e.g.,
node E in the figure shown above.
Segment protection or restoration is signaled using a working LSP and
one or more segment recovery LSPs. Each segment recovery LSP is
signaled as an independent LSP. Specifically, the Sender_Template
object uses the IP address of the node originating the recovery path,
e.g., node C in the topology shown above, and the Session object
contains the IP address of the node terminating the recovery path,
e.g., node E shown above. There is no specific requirement on LSP ID
value, Tunnel ID and Extended Tunnel ID. Values for these fields are
selected normally, including consideration for make-before-break.
Intermediate nodes follow standard signaling procedures when
processing segment recovery LSPs. A segment recovery LSP may be
protected itself using segment or end-to-end protection/restoration.
Note, in PSC environments it may be desirable to construct the
Sender_Template and Session objects per [RFC4090].
When [RFC4090] isn't being used, the association between segment
recovery LSPs with other LSPs is indicated using the Association
Berger, et al. [Page 4]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
object defined in [E2E-RECOVERY]. The Association object is used to
associate recovery LSPs with the LSP they are protecting. Working
and protecting LSPs, as well as primary and secondary LSPs, are
identified using LSP Status as described in [E2E-RECOVERY]. The O-
bit in the segment flags portion of the Protection object is used to
identify when a recovery LSP is carrying the normal (active) traffic.
An upstream node can permit downstream nodes to dynamically identify
branch and merge points by setting the desired LSP segment protection
bits in the Protection object. These bits are defined below.
Optionally, an upstream node, usually the ingress node, can identify
the endpoints of a segment recovery LSP. This is accomplished using
a new object. This object uses the same format as an ERO and is
referred to as a Secondary Explicit Route object or SERO, see section
4.1. SEROs also support a new subobject to indicate the type of
protection or restoration to be provided. At a minimum an SERO will
indicate a recovery LSP's initiator, protection/restoration type and
terminator. Standard ERO semantics, see [RFC3209], can optionally be
used within and SERO to explicitly control the recovery LSP. A
Secondary Record Route object or SRRO is defined for recording the
path of a segment recovery LSP, see section 5.
SEROs are carried between the node creating the SERO, typically the
ingress, and the node initiating a recovery LSP. The node initiating
a recovery LSP uses the SERO to create the ERO for the recovery LSP.
At this (branch) node, all local objects are removed, and the new
protection subobject is used to create the Protection object for the
recovery LSP. It is also possible to control the handling of a
failure to establish a recovery LSP.
SRROs are carried in Path messages between the node terminating a
recovery LSP, the merge node, and the egress. SRROs are used in Resv
messages between a branch node and the ingress. The merge node of a
recovery LSP creates an SRRO by copying the RRO from the Path message
of the associated recovery LSP into a new SRRO object. Any SRROs
present in the recovery LSP's Path message are also copied. The
branch node of a recovery LSP creates an SRRO by copying the RRO from
the Resv message of associated recovery LSP into a new SRRO object.
Any SRROs present in the recovery LSP's Resv message are also copied.
Notify request processing is also impacted by LSP segment recovery.
Per [RFC3473], only one Notify Request object is meaningful and
should be propagated. Additional Notify Request objects are used to
identify recovery LSP branch nodes.
Berger, et al. [Page 5]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
2.1. Segment Protection
Three approaches for end-to-end protection are defined in [E2E-
RECOVERY]: 1+1 Unidirectional Protection, see Section 5; 1+1 Bi-
directional Protection, see Section 6: and 1:1 Protection With Extra
Traffic, see Section 7. The segment protection forms of these
protection approaches all operate much like their end-to-end
counterparts. Each behaves just like its end-to-end counterpart,
with the exception that the protection LSP protects only a portion of
the working LSP. The type of protection to be used on a segment
protection LSP is indicated, to the protection LSP's ingress, using
the protection SERO subobject defined in Section 4.1.
The switch-over processing for segment 1+1 Bi-directional protection
and 1:1 Protection With Extra Traffic follows the same procedures as
end-to-end protection forms, see Section 6.2 and Section 7.2 for
details.
2.2. Segment Re-routing and Restoration
Three re-routing and restoration approaches are defined [E2E-
RECOVERY]: Re-routing without Extra-Traffic, see Section 8; Shared-
Mesh Restoration, see Section 9; (Full) LSP Re-routing, see Section
11. As with protection, these approaches are supported on a segment
basis. The segment forms of re-routing and restoration operate
exactly like their end-to-end counterparts, with the exception that
the restoration LSP recovers only a portion of the working LSP. The
type of re-routing or restoration to be used on a segment restoration
LSP is indicated, to the restoration LSP's ingress, using the new
protection SERO subobject.
3. Association Object
The Association object is used association of segment protection LSPs
when [RFC4090] isn't being used. The Association object is defined
in [E2E-RECOVERY]. In this document we define a new Association Type
field value to support make before break, formats and procedures
defined in [E2E-RECOVERY] are not otherwise modified.
Berger, et al. [Page 6]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
3.1. Format
Association Type: 16 bits
Value Type
----- ----
2 Resource Sharing (R)
See [E2E-RECOVERY] for the definition of other fields and other
values.
3.2. Procedures
The Association object is used to associate different LSPs with each
other. In the protection and restoration context, the object is used
to associate a recovery LSP with the LSP it is protecting. The
Association object is also used to support resource sharing during
make-before-break. This object MUST NOT be used when association is
made according to the methods defined in [RFC4090].
3.2.1. Recovery Type Processing
Recovery type processing procedures are the same as those defined in
[E2E-RECOVERY], but processing and identification occurs with respect
to segment recovery LSPs. Note that this means that multiple
Association objects of type recovery may be present on an LSP.
3.2.2. Resource Sharing Association Type Processing
The Association object with an Association Type with the value
Resource Sharing is used to enable resource sharing during make-
before-break. Resource sharing during make-before-break is defined
in [RFC3209]. The defined support only works with LSPs that share
the same LSP egress. With the introduction of segment recovery LSPs,
it is now possible for an LSP end-point to change during make-before-
break.
A node includes an Association object with a Resource Sharing
Association Type in outgoing an Path message when it wishes to
indicate resource sharing across an associated set of LSPs. The
Association Source is set to the originating node's router address.
The Association ID MUST be set to a value that uniquely identifies
the association of LSPs. This MAY be set to the working LSP's LSP
ID. Once included, an Association object with a Resource Sharing
Association Type SHOULD NOT be removed from the Path messages
Berger, et al. [Page 7]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
associated with an LSP.
Any node processing a Path message for which it does not have
matching state, and which contains a Association object with a
Resource Sharing type, examines existing LSPs for matching
Association Type, Association Source and Association ID values. If
any match is found, then [RFC3209] style resource sharing SHOULD be
provided between the new and old LSPs. See [RFC3209] for additional
details.
4. Explicit Control of LSP Segment Recovery
Secondary Explicit Route objects, or SEROs, are defined in this
document. They may be used to indicate the branch and merge nodes of
recovery LSPs. They may also provide additional information that is
to be carried in a recovery LSP's ERO. When upstream control of
branch and merge nodes is not desired, SEROs are not used.
4.1. Secondary Explicit Route Object Format
The format of a SECONDARY_EXPLICIT_ROUTE object is the same as an
EXPLICIT_ROUTE object. This includes the definition of subobjects
defined for EXPLICIT_ROUTE object. The class of the
SECONDARY_EXPLICIT_ROUTE object is TBA by IANA (of form 11bbbbbb).
4.1.1. Protection Subobject
A new subobject, called the protection subobject, is defined for use
in the SECONDARY_EXPLICIT_ROUTE object. As mentioned above, the new
protection subobject is used to create the Protection object for the
recovery LSP. Specific procedures related to the protection
subobject are provided in Section 4.2. The protection subobject is
not valid for use with the Explicit and Record Route objects and MUST
NOT be included in those objects.
Berger, et al. [Page 8]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
The format of the Protection Subobject is defined as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L| Type | Length | Reserved | C-Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| PROTECTION Object Contents |
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
L-bit
This is defined in [RFC3209] and MUST be set to zero for
protection subobjects.
Type
37 Protection
Length
As defined in [RFC3209], Section 4.3.3.
Reserved
This field is reserved. It MUST be set to zero on transmission
and MUST be ignored on receipt.
C-Type
The C-Type of the included Protection object.
PROTECTION Object Contents
The contents of the Protection object, with the format matching
the indicated C-Type, excluding the object header.
4.2. Explicit Control Procedures
SEROs are carried in Path messages and indicate at which node a
recovery LSP is to be initiated relative to the LSP carrying the
SERO. More than one SERO MAY be present in a Path message.
To indicate the branch and merge nodes of a recovery LSPs, an SERO is
created and added to the Path message of the LSP being recovered.
The decision to create and insert an SERO is a local matter and
Berger, et al. [Page 9]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
outside the scope of this document.
An SERO SHOULD contain at least three subobjects. The first
subobject MUST indicate the node that is to originate the recovery
LSP, i.e. the segment branch node. The address used SHOULD also be
listed in the ERO or another SERO. This ensures that the branch node
is along the LSP path. The second subobject SHOULD be a protection
subobject and should indicate the protection or restoration to be
provided by the recovery LSP. When the protection subobject is
present, the LSP Segment Recovery Flags in the Protection subobject
MUST be ignored. The final subobject in the SERO MUST be the merge
node of the recovery LSP, and MAY have the L-bit set. Standard ERO
subobjects MAY be inserted between the protection subobject and the
final subobject. These subobjects MAY be loose or strict.
A node receiving a Path message containing one or more SEROs SHOULD
examine each SERO to see if it indicates a local branch point. This
determination is made by examining the first object of each SERO and
seeing if the address indicated in the subobject can be associated
with the local node. If any of indicated addresses are associated
with the local node, then the local node is a branch node. If the
local node is not a branch node, all received SEROs MUST be
transmitted, without modification, in the corresponding outgoing Path
message.
At a branch node, the SERO together with the Path message of LSP
being recovered provides the information to create the recovery LSP.
The Path message for the recovery LSP is created at the branch node
by cloning the objects carried in the incoming Path message of the
LSP being protected. Certain objects are replaced or modified in the
recovery LSP's outgoing Path message. The Sender_template MUST be
updated to use an address on the local node, and the LSP ID MUST be
updated to ensure uniqueness. The Session object MUST be updated to
use the address indicated in the final subobject of the SERO as the
tunnel endpoint, the tunnel ID MAY be updated, and the extended
tunnel ID MUST be set to the local node. The Protection object is
replaced with the contents of the matching SERO protection subobject,
when present. In all cases, the R-bit of a new Protection object is
reset (0). Any RROs and EROs present in the incoming Path message
MUST NOT be included in the recovery LSP. A new ERO MUST be
included, with the contents of the SERO that indicated a local
branch. As with all EROs, no local information (local address and
any protection subobjects) is carried in the ERO carried in the
recovery LSP's outgoing Path message. The SERO that indicated a
local branch MUST be omitted from the recovery LSP's outgoing Path
message. Note, by default all other received SEROs are passed in the
recovery LSP's outgoing Path message. SEROs MAY be omitted, from the
recovery LSP's outgoing Path message as well as the outgoing Path
Berger, et al. [Page 10]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
message for the LSP being protected when the SERO does not relate to
the outgoing path message.
The resulting Path message is used to create the recovery LSP. From
this point on, Standard Path message processing is used in processing
the resulting Path message.
4.2.1. Branch Failure Handling
During setup, it is possible that a processing node will be unable to
support a requested branch. Additionally, during setup and during
normal operation, PathErr messages may be received at a branch node.
The processing of these events depend on a number of factors.
When a failure or received PathErr message is associated with the LSP
being protected, the event is first processed per standard processing
rules. This includes generation of a standard PathErr message. When
LSP state is removed due to a local failure or the a PathErr message
with the Path_State_Removed flag set (1), the node MUST send a
PathTear message downstream on all other branches.
When a failure or received PathErr message is associated with a
recovery LSP, processing is based on the R-bit in addition to the
Path_State_Removed flag. In all cases, a received PathErr message is
first processed per standard processing rules and the the failure or
received PathErr message SHOULD trigger the generation of a PathErr
message upstream for the LSP being protected. The outgoing PathErr
message SHOULD indicate an error of "Routing Problem/LSP Segment
Protection Failed". The outgoing PathErr message MUST include any
SEROs carried in a received PathErr message. If no SERO is present
in a received PathErr message or when the failure is local, then an
SERO that matches the errored LSP or failed branch MUST be added to
the outgoing PathErr message.
When a PathErr message with the Path_State_Removed flag cleared (0)
is received, the outgoing (upstream) PathErr message SHOULD be sent
with the Path_State_Removed flag cleared (0).
When a PathErr message for a recover LSP with the Path_State_Removed
flag set (1) is received, the processing node MUST examine the R-bit
(as defined below) of the LSP being protected. The R-bit is carried
in the protection object that triggered the initiation of the
recovery LSP. When the R-bit is not set (0), the outgoing (upstream)
PathErr message SHOULD be sent with the Path_State_Removed flag
cleared (0). When the R-bit is set (1), the outgoing (upstream)
PathErr message MUST be sent with the Path_State_Removed flag set
(1).
Berger, et al. [Page 11]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
In all cases where an outgoing (upstream) PathErr message is sent
with the Path_State_Removed flag set (1), all path state for the LSP
being protected MUST be removed and the node MUST send a PathTear
message downstream on all active branches.
4.2.2. Resv Message Processing
Branch nodes will process Resv messages for both recovery LSPs and
LSPs being protected. Resv messages are propagated upstream of branch
nodes only after a Resv message is received for the protected LSP.
Resv messages on recovery LSPs will typically not trigger
transmission of upstream Resv messages (for the LSP being protected).
Exceptions to this include when RROs/SRROs are being collected and
during certain Admin Status object processing. See below for more
information on related processing.
4.2.3. Admin Status Change
In general, objects in a recovery LSP are created based on the
corresponding objects in the LSP being protected. The Admin Status
object is created the same way, but it also requires some special
coordination at branch nodes. Specifically, in addition to normal
processing, a branch node that receives an Admin Status object in a
Path message also MUST relay the Admin Status object in a Path on
every recovery LSP. All Path messages MAY be concurrently sent
downstream.
Downstream nodes process the change in the Admin Status object per
[RFC3473], including generation of Resv messages. When the most
recently received upstream Admin Status object had the R bit set,
branch nodes wait for a Resv message with a matching Admin Status
object to be received on all branches before relaying a corresponding
Resv message upstream.
4.2.4. Recovery LSP Tear Down
Recovery LSP removal is follows standard the standard procedures
defined in [RFC3209] and [RFC3473]. This includes without and with
setting the administrative status.
4.2.4.1. Tear Down Without Admin Status Change
The node initiating the tear down originates a PathTear message.
Each node that receives a PathTear message process the PathTear
Berger, et al. [Page 12]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
message per standard processing, see [RFC3209] and [RFC2205], and
MUST also relay a PathTear on every recovery LSP. All PathTear
messages (received from upstream and locally originated) may be
concurrently sent downstream.
4.2.4.2. Tear Down With Admin Status Change
Per [RFC3473], the ingress node originates a Path message with the D
and R bits set in the Admin Status object. The admin status change
procedure defined above, see Section 4.2.3, MUST then be followed.
Once the ingress receives all expected Resv messages, it MUST follow
the tear down procedure described in Section 4.2.4.1.
4.3. Tear Down From Non-Ingress Nodes
As with any LSP, any node along a recovery LSP may initiate removal
of the recovery LSP. To do this, the node initiating the tear down
sends a PathErr message with the appropriate Error Code and the
Path_State_Removed flag cleared (0) toward the LSP ingress. As
described above, the recovery LSP ingress will propagate the error to
the LSP ingress which can then signal the removal of the recovery
LSP.
It is also possible for the node initiating the tear down to remove a
Recovery LSP in a non-graceful manner. In this case, the initiator
sends a PathTear message downstream and a PathErr message with a
"Confirmation" indication (error code and value set to zero) and the
Path_State_Removed flag set (1) toward the LSP ingress node. This
manner of non-ingress node tear down is NOT RECOMMENDED as it can
result in the removal of the LSP being protected in some case.
4.3.1. Modified Notify Request Object Processing
When a node is branching a recovery LSP, it SHOULD include a single
Notify Request object in the Path message of the recovery LSP. The
notify node address MUST be set to the router address of the branch
node.
A branch node SHOULD also add a Notify Request object to the LSP
being protected. The notify node address is set to the address used
in the sender template of the recovery LSP. A locally added Notify
Request object MUST be listed first in the outgoing message, any
received Notify Request objects MUST then be listed in the message in
the order that they were received. Note that this can result in a
stack of (or ordered list) of objects.
Berger, et al. [Page 13]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
Normal notification procedures are then followed for the LSP being
protected. That is, the notifying node MUST issue a Notify message to
the recipient indicated by the notify address of the first listed
Notify Request object. Under local policy control, a node issuing a
Notify message MAY also send a Notify message to the Notify Node
Address indicated in the last, or any other, Notify Request object
carried in the Path message.
Recovery LSP merge nodes remove the object added by the recovery
branch node from outgoing Path messages for the LSP being protected.
This is done by removing the Notify Request object that matches the
source address of the recovery LSP. This will normally be the first
of the listed Notify Request objects. Note, to cover certain
backwards compatibility scenarios the Notify Request object SHOULD
NOT be removed if it is the sole Notify Request object.
A similar set of rules are applied to the processing of Resv message
objects to enable merge nodes adding a Notify Request to the Resv
message for the protected LSP, arranging the objects as an ordered
list or stack.
Note this requires the following change to [RFC3473], Section 4.2.1:
o old text:
If a message contains multiple Notify_Request objects, only the
first object is meaningful. Subsequent Notify_Request objects
MAY be ignored and SHOULD NOT be propagated.
o new text:
If a message contains multiple Notify_Request objects, only the
first object used is in notification. Subsequent Notify_Request
objects MUST be propagated in the order received.
4.3.2. Modified Notify and Error Message Processing
Branch nodes MUST support the following modification to Notify
message processing. When a branch node receives notification of an
LSP failure and it is unable to recover from that failure, it MUST
notify the node indicated in the first Notify_Request object received
in the Path message associated with the LSP.
Berger, et al. [Page 14]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
5. Secondary Record Route Objects
Secondary Record Route objects, or SRROs, are used to record the path
used by recovery LSPs.
5.1. Format
The format of a SECONDARY_RECORD_ROUTE object is the same as a
RECORD_ROUTE object, Class number 21. This includes the definition
of subobjects defined for RECORD_ROUTE object. The class of the
SECONDARY_RECORD_ROUTE object is TBA by IANA (of form 11bbbbbb).
The protection subobject defined above can also be used in
SECONDARY_RECORD_ROUTE objects.
5.2. Path Processing
SRROs may be carried in Path messages and indicate the presence of
upstream recovery LSPs. More than one SRRO MAY be add and present in
a Path message.
Any received SRRO, MUST be transmitted by transit nodes, without
modification, in the corresponding outgoing Path message.
SRROs are inserted in Path messages by recovery LSP merge nodes. The
SRRO is created by copying the contents of an RRO received the
recovery LSP into a new SRRO object. This SRRO is added to the
outgoing Path message of the recovered LSP. Note multiple SRROs may
be present. The collection of SRROs is controlled via the segment-
recording-desired flag in the SESSION_ATTRIBUTE object. This flag MAY
be set even when SEROs are not used.
5.3. Resv Processing
SRROs may be carried in Resv messages and indicate the presence of
downstream recovery LSPs. More than one SRRO MAY be add and present
in a Resv message.
Any received SRRO, MUST be transmitted by transit nodes, without
modification, in the corresponding outgoing Resv message. When Resv
messages are merged, the resulting merged Resv SHOULD contain all
SRROs received in downstream Resv messages.
SRROs are inserted in Resv messages by branch nodes of recovery LSPs.
The SRRO SHOULD be created with the first two objects being the local
Berger, et al. [Page 15]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
node address followed by a protection subobject with the contents of
the recovery LSP's Protection object. The remainder of the SRRO
SHOULD be created by copying the contents of the RRO received the
recovery LSP. This SRRO SHOULD be added to the outgoing Resv message
of the recovered LSP. Again, multiple SRROs may be present.
If the newly added SRRO causes the message to be too big to fit in a
Resv message, SRRO subobjects SHOULD be removed from any present
SRROs. When removing subobjects, the first two subobjects and the
last subobject in an SRRO MUST NOT be removed. Note that the sub-
object that followed a removed sub-object MUST be updated with the L-
bit set (1). If after removing all but the first and last subobjects
in all SRROs the resulting message is still too large to fit, then
whole SRROs SHOULD be removed until the message does fit.
6. Dynamic Control of LSP Segment Recovery
Dynamic identification of branch and merge nodes is supported via the
LSP Segment Recovery Flags carried in the Protection object. The LSP
Segment Recovery Flags are carried within one of Reserved fields
defined in the Protection object defined in [E2E-RECOVERY]. LSP
Segment Recovery Flags are used to indicate when LSP segment recovery
is desired. When these bits are set branch and merge nodes are
dynamically identified.
Note, the procedures defined in this section parallel the explicit
control procedures defined above in Section 4.2. The primary
difference is in creation of a recovery LSP's ERO.
6.1. Modified Protection Object Format
LSP Segment Recovery Flags are carried in the Protection object of
the same C-Type defined in [E2E-RECOVERY]. The format of the flags
are:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | Class-Num(37) | C-Type (TBA) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|P|N|O| Reserved | LSP Flags | Reserved | Link Flags|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|I|R| Reserved | Seg.Flags | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
In-Place (I): 1 bit
Berger, et al. [Page 16]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
When set (1) indicates that the desired segment recovery type
indicated in the LSP Segment Recovery Flag is already in place
for the associated LSP.
Required (R): 1 bit
When set (1) indicates that failure to establish the indicated
protection should result in a failure of the LSP being
protected.
Segment Recovery Flags (Seg.Flags): 6 bits
This field is used to indicate when an upstream node desires
LSP Segment recovery to be dynamically initiated where
possible. The values used in this field are identical to the
values defined for LSP Flags, see [E2E-RECOVERY].
See [E2E-RECOVERY] for the definition of other fields.
6.2. Dynamic Control Procedures
LSP Segment Recovery Flags are set to indicate that LSP segment
recovery is desired for the LSP being signaled. The type of recovery
desired is indicated by the flags. The decision to set the LSP
Segment Recovery Flags is a local matter and outside the scope of
this document. A value of zero (0) means that no dynamic
identification of segment recovery branch nodes are needed for the
associated LSP. When the In-Place bit is set, it means that the
desired type of recovery is already in place for that particular LSP.
A transit node receiving a Path message containing a Protection
object with a non-zero LSP Segment Recovery Flags value and the In-
Place bit clear (0) SHOULD consider if it can support the indicated
recovery type and if it can identify an appropriate merge node for a
recovery LSP. Dynamic identification MUST NOT be done when the
processing node is identified as a branch node in an SERO. If a node
is unable to provide the indicated recovery type or identify a merge
node, the Path message MUST be processed normally and the LSP Segment
Recovery Flags MUST NOT be modified.
When a node dynamically identifies itself as a branch node and
identifies the merge node for the type of recovery indicated in the
LSP Segment Recovery Flags, it attempts to setup a recovery LSP. The
dynamically identified information, together with the Path message of
LSP being recovered provides the information to create the recovery
LSP.
Berger, et al. [Page 17]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
The Path message for the recovery LSP is created at the branch node
by cloning the objects carried in the incoming Path message of the
LSP being protected. Certain objects are replaced or modified in the
recovery LSP's outgoing Path message. The Sender_template MUST be
updated to use an address on the local node, and the LSP ID MUST be
updated to ensure uniqueness. The Session object MUST be updated to
use the address of the dynamically identified merge node as the
tunnel endpoint, the tunnel ID MAY be updated, and the extended
tunnel ID MUST be set to the local node. The Protection object is
updated with the In-Place bit set (1). Any RROs and EROs present in
the incoming Path message MUST NOT be included in the recovery LSP. A
new ERO MAY be created based on any path information dynamically
computed by the local node.
The resulting Path message is used to create the recovery LSP. While
the recovery LSP exists and unless overridden by local policy, the
Protection object in the original Path message MUST also be updated
with the In-Place bit set (1). From this point on, Standard Path
message processing is used in processing the resulting and original
Path messages.
The merge node of a dynamically controlled recovery LSP SHOULD reset
(0) the In-Place bit in the Protection object of the outgoing Path
message associated with the terminated recovery LSP.
Unlike with explicit control, if the creation of a dynamically
identified recovery LSP fails for any reason, the recovery LSP is
removed and no error message or indication is sent upstream. With
this exception, all the other procedures for explicitly controlled
recovery LSPs apply to dynamically controlled recovery LSPs. These
other procedures are defined above in defined in Sections 4.2.1
through 4.2.4.
7. Updated RSVP Message Formats
This section presents the RSVP message related formats as modified by
this document. Where they differ, formats for unidirectional LSPs
are presented separately from bidirectional LSPs.
Berger, et al. [Page 18]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
The format of a Path message is as follows:
<Path Message> ::= <Common Header> [ <INTEGRITY> ]
[ [<MESSAGE_ID_ACK> | <MESSAGE_ID_NACK>] ... ]
[ <MESSAGE_ID> ]
<SESSION> <RSVP_HOP>
<TIME_VALUES>
[ <EXPLICIT_ROUTE> ]
<LABEL_REQUEST>
[ <PROTECTION> ]
[ <LABEL_SET> ... ]
[ <SESSION_ATTRIBUTE> ]
[ <NOTIFY_REQUEST> ... ]
[ <ADMIN_STATUS> ]
[ <ASSOCIATION> ... ]
[ <SECONDARY_EXPLICIT_ROUTE> ... ]
[ <POLICY_DATA> ... ]
<sender descriptor>
The format of the sender description for unidirectional LSPs is:
<sender descriptor> ::= <SENDER_TEMPLATE> <SENDER_TSPEC>
[ <ADSPEC> ]
[ <RECORD_ROUTE> ]
[ <SUGGESTED_LABEL> ]
[ <RECOVERY_LABEL> ]
[ <SECONDARY_RECORD_ROUTE> ... ]
The format of the sender description for bidirectional LSPs is:
<sender descriptor> ::= <SENDER_TEMPLATE> <SENDER_TSPEC>
[ <ADSPEC> ]
[ <RECORD_ROUTE> ]
[ <SUGGESTED_LABEL> ]
[ <RECOVERY_LABEL> ]
<UPSTREAM_LABEL>
[ <SECONDARY_RECORD_ROUTE> ... ]
The format of a PathErr message is as follows:
<PathErr Message> ::= <Common Header> [ <INTEGRITY> ]
[ [<MESSAGE_ID_ACK> | <MESSAGE_ID_NACK>] ... ]
[ <MESSAGE_ID> ]
<SESSION> <ERROR_SPEC>
[ <ACCEPTABLE_LABEL_SET> ... ]
[ <SECONDARY_EXPLICIT_ROUTE> ... ]
[ <POLICY_DATA> ... ]
<sender descriptor>
Berger, et al. [Page 19]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
The format of a Resv message is as follows:
<Resv Message> ::= <Common Header> [ <INTEGRITY> ]
[ [<MESSAGE_ID_ACK> | <MESSAGE_ID_NACK>] ... ]
[ <MESSAGE_ID> ]
<SESSION> <RSVP_HOP>
<TIME_VALUES>
[ <RESV_CONFIRM> ] [ <SCOPE> ]
[ <NOTIFY_REQUEST> ... ]
[ <ADMIN_STATUS> ]
[ <POLICY_DATA> ... ]
<STYLE> <flow descriptor list>
<flow descriptor list> ::= <FF flow descriptor list>
| <SE flow descriptor>
<FF flow descriptor list> ::= <FLOWSPEC> <FILTER_SPEC>
<LABEL> [ <RECORD_ROUTE> ]
[ <SECONDARY_RECORD_ROUTE> ... ]
| <FF flow descriptor list>
<FF flow descriptor>
<FF flow descriptor> ::= [ <FLOWSPEC> ] <FILTER_SPEC> <LABEL>
[ <RECORD_ROUTE> ]
[ <SECONDARY_RECORD_ROUTE> ... ]
<SE flow descriptor> ::= <FLOWSPEC> <SE filter spec list>
<SE filter spec list> ::= <SE filter spec>
| <SE filter spec list> <SE filter spec>
<SE filter spec> ::= <FILTER_SPEC> <LABEL> [ <RECORD_ROUTE> ]
[ <SECONDARY_RECORD_ROUTE> ... ]
8. Security Considerations
This document introduces new message objects for use in GMPLS
signaling [RFC3473]. It does not introduce any new signaling
messages, nor change the relationship between LSRs that are adjacent
in the control plane.
The procedures defined in this document result in an increase in the
amount of topology information carried in signaling messages since
the presence of SEROs and SRROs necessarily means that there is more
information about LSP paths carried than in simple EROs and RROs.
Thus, in the event of the interception of a signaling message,
Berger, et al. [Page 20]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
slightly more could be deduced about the state of the network than
was previously the case, but this is judged to be a very minor
security risk as this information is already available via routing.
Otherwise, this document introduces no additional security
considerations. See [RFC3473] for relevant security considerations.
9. IANA Considerations
IANA is requested to administer assignment of new values for
namespaces defined in this document and reviewed in this section.
9.1. New Association Type Assignment
Upon approval of this document, the IANA will make the following
assignment to the "Association Types" Registry, see [E2E-RECOVERY],
in the "ASSOCIATION (object)" section of the "RSVP PARAMETERS"
registry located at http://www.iana.org/assignments/rsvp-parameters
Value Type
----- ----
2 Resource Sharing (R) [RFC-ccamp-gmpls-segment-recovery]
9.2. Definition of Protection Object Reserved Bits
This document defines bits carried in the Reserved field of the
Protection Object defined in [E2E-RECOVERY]. As no IANA registry for
these bits is requested in [E2E-RECOVERY], no IANA action is required
related to this definition.
9.3. Secondary Explicit Route Object
Upon approval of this document, the IANA will make the following
assignments in the "Class Names, Class Numbers, and Class Types"
section of the "RSVP PARAMETERS" registry located at
http://www.iana.org/assignments/rsvp-parameters
A new class named SECONDARY_EXPLICIT_ROUTE will be created in the
11bbbbbb range (198 suggested) with the following definition:
Class Types or C-types:
Same values as EXPLICIT_ROUTE object (C-Num 20)
For Class 1, C-Type 1, the following additional Sub-object type is
Berger, et al. [Page 21]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
defined:
37 Protection [RFC-ccamp-gmpls-segment-recovery]
9.4. Secondary Record Route Object
Upon approval of this document, the IANA will make the following
assignments in the "Class Names, Class Numbers, and Class Types"
section of the "RSVP PARAMETERS" registry located at
http://www.iana.org/assignments/rsvp-parameters
A new class named SECONDARY_RECORD_ROUTE will be created in the
11bbbbbb range (198 suggested) with the following definition:
Class Types or C-types:
Same values as RECORD_ROUTE object (C-Num 21)
For Class 1, C-Type 1, the following additional Sub-object type is
defined:
37 Protection [RFC-ccamp-gmpls-segment-recovery]
9.5. New Error Code
Upon approval of this document, the IANA will make the following
assignments in the "Routing Problem" subsection of "Error Codes and
Values" section of the "RSVP PARAMETERS" registry located at
http://www.iana.org/assignments/rsvp-parameters
xx = LSP Segment Protection Failed [RFC-ccamp-gmpls-segment-recovery]
9.6. Use of Not Yet Assigned Protection Object C-type
This document modifies the Protection Object, class number 37, C-Type
defined in [E2E-RECOVERY]. Per Section 14.1 of [E2E-RECOVERY], this
C-Type is still "TBA", but has a suggested value of 2. Section 6.1
of this document, should be updated to match the assignment made by
IANA for Section 14.1 of [E2E-RECOVERY].
Berger, et al. [Page 22]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
10. References
10.1. Normative References
[RFC2205] Braden, R. Ed. et al, "Resource ReserVation Protocol
-- Version 1 Functional Specification", RFC 2205,
September 1997.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels," RFC 2119.
[RFC3209] Awduche, et al, "RSVP-TE: Extensions to RSVP for
LSP Tunnels", RFC 3209, December 2001.
[RFC3471] Berger, L., Editor, "Generalized Multi-Protocol
Label Switching (GMPLS) Signaling Functional
Description", RFC 3471, January 2003.
[RFC3473] Berger, L., Editor, "Generalized Multi-Protocol Label
Switching (GMPLS) Signaling - Resource ReserVation
Protocol-Traffic Engineering (RSVP-TE) Extensions",
RFC 3473, January 2003.
[E2E-RECOVERY] Lang, J.P., Rekhter, Y., Papadimitriou, D., Editors,
"RSVP-TE Extensions in support of End-to-End
GMPLS-based Recovery", Work in Progress,
draft-lang-ccamp-gmpls-recovery-e2e-signaling-03.txt,
April 2005.
10.2. Informative References
[RFC4090] Pan, et al, "Fast Reroute Extensions to RSVP-TE for LSP
Tunnels", RFC 4090, May 2005.
[RFC4426] J.P.Lang and B.Rajagopalan (Editors), "Generalized MPLS
Recovery Functional Specification," RFC 4426, March 2006.
[RFC4427] E.Mannie and D.Papadimitriou (Editors), "Recovery
(Protection and Restoration) Terminology for GMPLS,"
Internet Draft, RFC 4427, March 2006.
Berger, et al. [Page 23]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
11. Authors' Addresses
Lou Berger
LabN Consulting, L.L.C.
Phone: +1 301-468-9228
Email: lberger@labn.net
Igor Bryskin
Movaz Networks, Inc.
7926 Jones Branch Drive
Suite 615
McLean VA, 22102
Email: ibryskin@movaz.com
Adrian Farrel
Old Dog Consulting
Phone: +44 (0) 1978 860944
Email: adrian@olddog.co.uk
Dimitri Papadimitriou (Alcatel)
Francis Wellesplein 1
B-2018 Antwerpen, Belgium
Phone: +32 3 240-8491
Email: dimitri.papadimitriou@alcatel.be
12. Full Copyright Statement
Copyright (C) The Internet Society (2006). 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 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.
Berger, et al. [Page 24]
Internet Draft draft-ietf-ccamp-gmpls-segment-recovery-03.txt October 2006
13. 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.
Berger, et al. [Page 25]
Generated on: Fri Oct 6 11:36:26 EDT 2006
Html markup produced by rfcmarkup 1.111, available from
https://tools.ietf.org/tools/rfcmarkup/