draft-ietf-teas-rsvp-ingress-protection-02.txt   draft-ietf-teas-rsvp-ingress-protection-03.txt 
Internet Engineering Task Force H. Chen, Ed. Internet Engineering Task Force H. Chen, Ed.
Internet-Draft Huawei Technologies Internet-Draft Huawei Technologies
Intended status: Standards Track R. Torvi, Ed. Intended status: Standards Track R. Torvi, Ed.
Expires: September 10, 2015 Juniper Networks Expires: December 22, 2015 Juniper Networks
March 9, 2015 June 20, 2015
Extensions to RSVP-TE for LSP Ingress Local Protection Extensions to RSVP-TE for LSP Ingress Local Protection
draft-ietf-teas-rsvp-ingress-protection-02.txt draft-ietf-teas-rsvp-ingress-protection-03.txt
Abstract Abstract
This document describes extensions to Resource Reservation Protocol - This document describes extensions to Resource Reservation Protocol -
Traffic Engineering (RSVP-TE) for locally protecting the ingress node Traffic Engineering (RSVP-TE) for locally protecting the ingress node
of a Traffic Engineered (TE) Label Switched Path (LSP), which is a of a Traffic Engineered (TE) Label Switched Path (LSP), which is a
Point-to-Point (P2P) LSP or a Point-to-Multipoint (P2MP) LSP. Point-to-Point (P2P) LSP or a Point-to-Multipoint (P2MP) LSP.
Status of this Memo Status of this Memo
skipping to change at page 1, line 34 skipping to change at page 1, line 34
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
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."
This Internet-Draft will expire on September 10, 2015. This Internet-Draft will expire on December 22, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 23 skipping to change at page 2, line 23
3.2. Backup and Source Detect Failure . . . . . . . . . . . . . 5 3.2. Backup and Source Detect Failure . . . . . . . . . . . . . 5
4. Backup Forwarding State . . . . . . . . . . . . . . . . . . . 5 4. Backup Forwarding State . . . . . . . . . . . . . . . . . . . 5
4.1. Forwarding State for Backup LSP . . . . . . . . . . . . . 5 4.1. Forwarding State for Backup LSP . . . . . . . . . . . . . 5
5. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 6 5. Protocol Extensions . . . . . . . . . . . . . . . . . . . . . 6
5.1. INGRESS_PROTECTION Object . . . . . . . . . . . . . . . . 6 5.1. INGRESS_PROTECTION Object . . . . . . . . . . . . . . . . 6
5.1.1. Subobject: Backup Ingress IPv4 Address . . . . . . . . 7 5.1.1. Subobject: Backup Ingress IPv4 Address . . . . . . . . 7
5.1.2. Subobject: Backup Ingress IPv6 Address . . . . . . . . 8 5.1.2. Subobject: Backup Ingress IPv6 Address . . . . . . . . 8
5.1.3. Subobject: Ingress IPv4 Address . . . . . . . . . . . 8 5.1.3. Subobject: Ingress IPv4 Address . . . . . . . . . . . 8
5.1.4. Subobject: Ingress IPv6 Address . . . . . . . . . . . 8 5.1.4. Subobject: Ingress IPv6 Address . . . . . . . . . . . 8
5.1.5. Subobject: Traffic Descriptor . . . . . . . . . . . . 9 5.1.5. Subobject: Traffic Descriptor . . . . . . . . . . . . 9
5.1.6. Subobject: Label-Routes . . . . . . . . . . . . . . . 9 5.1.6. Subobject: Label-Routes . . . . . . . . . . . . . . . 10
6. Behavior of Ingress Protection . . . . . . . . . . . . . . . . 10 6. Behavior of Ingress Protection . . . . . . . . . . . . . . . . 10
6.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 10 6.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 10
6.1.1. Relay-Message Method . . . . . . . . . . . . . . . . . 10 6.1.1. Relay-Message Method . . . . . . . . . . . . . . . . . 10
6.1.2. Proxy-Ingress Method . . . . . . . . . . . . . . . . . 11 6.1.2. Proxy-Ingress Method . . . . . . . . . . . . . . . . . 11
6.1.3. Comparing Two Methods . . . . . . . . . . . . . . . . 11 6.1.3. Comparing Two Methods . . . . . . . . . . . . . . . . 12
6.2. Ingress Behavior . . . . . . . . . . . . . . . . . . . . . 12 6.2. Ingress Behavior . . . . . . . . . . . . . . . . . . . . . 12
6.2.1. Relay-Message Method . . . . . . . . . . . . . . . . . 12 6.2.1. Relay-Message Method . . . . . . . . . . . . . . . . . 13
6.2.2. Proxy-Ingress Method . . . . . . . . . . . . . . . . . 13 6.2.2. Proxy-Ingress Method . . . . . . . . . . . . . . . . . 13
6.3. Backup Ingress Behavior . . . . . . . . . . . . . . . . . 14 6.3. Backup Ingress Behavior . . . . . . . . . . . . . . . . . 14
6.3.1. Backup Ingress Behavior in Off-path Case . . . . . . . 14 6.3.1. Backup Ingress Behavior in Off-path Case . . . . . . . 15
6.3.2. Backup Ingress Behavior in On-path Case . . . . . . . 17 6.3.2. Backup Ingress Behavior in On-path Case . . . . . . . 17
6.3.3. Failure Detection and Refresh PATH Messages . . . . . 17 6.3.3. Failure Detection and Refresh PATH Messages . . . . . 18
6.4. Revertive Behavior . . . . . . . . . . . . . . . . . . . . 18 6.4. Revertive Behavior . . . . . . . . . . . . . . . . . . . . 18
6.4.1. Revert to Primary Ingress . . . . . . . . . . . . . . 18 6.4.1. Revert to Primary Ingress . . . . . . . . . . . . . . 18
6.4.2. Global Repair by Backup Ingress . . . . . . . . . . . 19 6.4.2. Global Repair by Backup Ingress . . . . . . . . . . . 19
7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
8.1. A New Class Number . . . . . . . . . . . . . . . . . . . . 19 8.1. A New Class Number . . . . . . . . . . . . . . . . . . . . 19
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 20
10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 21 10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 21
11. Normative References . . . . . . . . . . . . . . . . . . . . . 21 11. Normative References . . . . . . . . . . . . . . . . . . . . . 21
A. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22 A. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 22
1. Co-authors 1. Co-authors
Ning So, Autumn Liu, Alia Atlas, Yimin Shen, Tarek Saad, Fengman Xu, Ning So, Autumn Liu, Alia Atlas, Yimin Shen, Tarek Saad, Fengman Xu,
Mehmet Toy, Lei Liu Mehmet Toy, Lei Liu
2. Introduction 2. Introduction
For MPLS LSPs it is important to have a fast-reroute method for For a MPLS LSP it is important to have a fast-reroute method for
protecting its ingress node as well as transit nodes. This is not protecting its ingress node and transit nodes. Protecting an ingress
covered either in the fast-reroute method defined in [RFC4090] or in is not covered either in the fast-reroute method defined in [RFC4090]
the P2MP fast-reroute extensions to fast-reroute in [RFC4875]. or in the P2MP fast-reroute extensions to fast-reroute in [RFC4875].
An alternate approach to local protection (fast-reroute) is to use An alternate approach to local protection (fast-reroute) is to use
global protection and set up a second backup LSP (whether P2MP or global protection and set up a secondary backup LSP (whether P2MP or
P2P) from a backup ingress to the egresses. The main disadvantage of P2P) from a backup ingress to the egresses. The main disadvantage of
this is that the backup LSP may reserve additional network bandwidth. this is that the backup LSP may reserve additional network bandwidth.
This specification defines a simple extension to RSVP-TE for local This specification defines a simple extension to RSVP-TE for local
protection of the ingress node of a P2MP or P2P LSP. protection of the ingress node of a P2MP or P2P LSP.
2.1. An Example of Ingress Local Protection 2.1. An Example of Ingress Local Protection
Figure 1 shows an example of using a backup P2MP LSP to locally Figure 1 shows an example of using a backup P2MP LSP to locally
protect the ingress of a primary P2MP LSP, which is from ingress R1 protect the ingress of a primary P2MP LSP, which is from ingress R1
skipping to change at page 4, line 6 skipping to change at page 4, line 6
[Ra]----[Rb] [L3] [Ra]----[Rb] [L3]
Figure 1: Backup P2MP LSP for Locally Protecting Ingress Figure 1: Backup P2MP LSP for Locally Protecting Ingress
In normal operations, source S sends the traffic to primary ingress In normal operations, source S sends the traffic to primary ingress
R1. R1 imports the traffic into the primary LSP. R1. R1 imports the traffic into the primary LSP.
When source S detects the failure of R1, it switches the traffic to When source S detects the failure of R1, it switches the traffic to
backup ingress Ra, which imports the traffic from S into the backup backup ingress Ra, which imports the traffic from S into the backup
LSP to R1's next hops R2 and R4, where the traffic is merged into the LSP to R1's next hops R2 and R4, where the traffic is merged into the
primary LSP, and then sent to egresses L1, L2 and L3. primary LSP, and then sent to egresses L1, L2 and L3. Source S
detects the failure of R1 and switches the traffic within 10s of ms.
Source S should be able to detect the failure of R1 and switch the
traffic within 10s of ms.
Note that the backup ingress must be one logical hop away from the Note that the backup ingress is one logical hop away from the
ingress. A logical hop is a direct link or a tunnel such as a GRE ingress. A logical hop is a direct link or a tunnel such as a GRE
tunnel, over which RSVP-TE messages may be exchanged. tunnel, over which RSVP-TE messages may be exchanged.
2.2. Ingress Local Protection with FRR 2.2. Ingress Local Protection with FRR
Through using the ingress local protection and the FRR, we can Through using the ingress local protection and the FRR, we can
locally protect the ingress, all the links and the transit nodes of locally protect the ingress, all the links and the transit nodes of
an LSP. The traffic switchover time is within 10s of ms whenever the an LSP. The traffic switchover time is within 10s of ms whenever the
ingress, any of the links and the transit nodes of the LSP fails. ingress, any of the links and the transit nodes of the LSP fails.
skipping to change at page 4, line 47 skipping to change at page 4, line 45
ingress of an LSP. The backup ingress is ready to import the traffic ingress of an LSP. The backup ingress is ready to import the traffic
from the source into the backup LSP after the backup LSP is up. from the source into the backup LSP after the backup LSP is up.
In normal operations, the source sends the traffic to the primary In normal operations, the source sends the traffic to the primary
ingress. When the source detects the failure of the primary ingress, ingress. When the source detects the failure of the primary ingress,
it switches the traffic to the backup ingress, which delivers the it switches the traffic to the backup ingress, which delivers the
traffic to the next hops of the primary ingress through the backup traffic to the next hops of the primary ingress through the backup
LSP, where the traffic is merged into the primary LSP. LSP, where the traffic is merged into the primary LSP.
For a P2P LSP, after the primary ingress fails, the backup ingress For a P2P LSP, after the primary ingress fails, the backup ingress
must use a method to reliably detect the failure of the primary MUST use a method to reliably detect the failure of the primary
ingress before the PATH message for the LSP expires at the next hop ingress before the PATH message for the LSP expires at the next hop
of the primary ingress. After reliably detecting the failure, the of the primary ingress. After reliably detecting the failure, the
backup ingress sends/refreshes the PATH message to the next hop backup ingress sends/refreshes the PATH message to the next hop
through the backup LSP as needed. through the backup LSP as needed.
After the primary ingress fails, it will not be reachable after After the primary ingress fails, it will not be reachable after
routing convergence. Thus checking whether the primary ingress routing convergence. Thus checking whether the primary ingress
(address) is reachable is a possible method. (address) is reachable is a possible method.
3.2. Backup and Source Detect Failure 3.2. Backup and Source Detect Failure
skipping to change at page 7, line 47 skipping to change at page 7, line 45
an ingress and transit node. an ingress and transit node.
The INGRESS_PROTECTION object may contain some sub objects below. The INGRESS_PROTECTION object may contain some sub objects below.
5.1.1. Subobject: Backup Ingress IPv4 Address 5.1.1. Subobject: Backup Ingress IPv4 Address
When the primary ingress of a protected LSP sends a PATH message with When the primary ingress of a protected LSP sends a PATH message with
an INGRESS_PROTECTION object to the backup ingress, the object may an INGRESS_PROTECTION object to the backup ingress, the object may
have a Backup Ingress IPv4 Address sub object containing an IPv4 have a Backup Ingress IPv4 Address sub object containing an IPv4
address belonging to the backup ingress. The Type of the sub object address belonging to the backup ingress. The Type of the sub object
is TBD-1, and the body of the sub object is given below: is TBD1 (the exact number to be assigned by IANA), and the body of
the sub object is given below:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address (4 bytes) | | Backup ingress IPv4 address (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv4 address: A 32-bit unicast, host address. Backup ingress IPv4 address: An IPv4 host address of backup ingress
5.1.2. Subobject: Backup Ingress IPv6 Address 5.1.2. Subobject: Backup Ingress IPv6 Address
When the primary ingress of a protected LSP sends a PATH message with When the primary ingress of a protected LSP sends a PATH message with
an INGRESS_PROTECTION object to the backup ingress, the object may an INGRESS_PROTECTION object to the backup ingress, the object may
have a Backup Ingress IPv6 Address sub object containing an IPv6 have a Backup Ingress IPv6 Address sub object containing an IPv6
address belonging to the backup ingress. The Type of the sub object address belonging to the backup ingress. The Type of the sub object
is TBD-2, the body of the sub object is given below: is TBD2, the body of the sub object is given below:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 address (16 bytes) | | Backup ingress IPv6 address (16 bytes) |
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 address: A 128-bit unicast, host address. Backup ingress IPv6 address: An IPv6 host address of backup ingress
5.1.3. Subobject: Ingress IPv4 Address 5.1.3. Subobject: Ingress IPv4 Address
The INGRESS_PROTECTION object may have an Ingress IPv4 Address sub The INGRESS_PROTECTION object may have an Ingress IPv4 Address sub
object containing an IPv4 address belonging to the primary ingress. object containing an IPv4 address belonging to the primary ingress.
The Type of the sub object is TBD-3. The sub object has the The Type of the sub object is TBD3. The sub object has the following
following body: body:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address (4 bytes) | | Ingress IPv4 address (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv4 address: A 32-bit unicast, host address. Ingress IPv4 address: An IPv4 host address of ingress
5.1.4. Subobject: Ingress IPv6 Address 5.1.4. Subobject: Ingress IPv6 Address
The INGRESS_PROTECTION object may have an Ingress IPv6 Address sub The INGRESS_PROTECTION object may have an Ingress IPv6 Address sub
object containing an IPv6 address belonging to the primary ingress. object containing an IPv6 address belonging to the primary ingress.
The Type of the sub object is TBD-4. The sub object has the The Type of the sub object is TBD4. The sub object has the following
following body: body:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 address (16 bytes) | | Ingress IPv6 address (16 bytes) |
~ ~ ~ ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
IPv6 address: A 128-bit unicast, host address. Ingress IPv6 address: An IPv6 host address of ingress
5.1.5. Subobject: Traffic Descriptor 5.1.5. Subobject: Traffic Descriptor
The INGRESS_PROTECTION object may have a Traffic Descriptor sub The INGRESS_PROTECTION object may have a Traffic Descriptor sub
object describing the traffic to be mapped to the backup LSP on the object describing the traffic to be mapped to the backup LSP on the
backup ingress for locally protecting the primary ingress. The Type backup ingress for locally protecting the primary ingress. The Type
of the sub object is TBD-5/TBD-6/TBD-7 for Interface/IPv4/IPv6 Prefix of the sub object is TBD5, TBD6, TBD7 or TBD8 for Interface, IPv4
respectively. The sub object has the following body: Prefix, IPv6 Prefix or Application Identifier respectively. The sub
object has the following body:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Traffic Element 1 | | Traffic Element 1 |
~ ~ ~ ~
| Traffic Element n | | Traffic Element n |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Traffic Descriptor sub object may contain multiple Traffic The Traffic Descriptor sub object may contain multiple Traffic
Elements of same type as follows: Elements of same type as follows:
o Interface Traffic (Type TBD-5): Each of the Traffic Elements is a o Interface Traffic (Type TBD5): Each of the Traffic Elements is a
32 bit index of an interface, from which the traffic is imported 32 bit index of an interface, from which the traffic is imported
into the backup LSP. into the backup LSP.
o IPv4/IPv6 Prefix Traffic (Type TBD-6/TBD-7): Each of the Traffic o IPv4 Prefix Traffic (Type TBD6): Each of the Traffic Elements is
Elements is an IPv4/IPv6 prefix, containing an 8-bit prefix length an IPv4 prefix, containing an 8-bit prefix length followed by an
followed by an IPv4/IPv6 address prefix, whose length, in bits, IPv4 address prefix, whose length, in bits, is specified by the
was specified by the prefix length, padded to a byte boundary. prefix length, padded to a byte boundary.
o IPv6 Prefix Traffic (Type TBD7): Each of the Traffic Elements is
an IPv6 prefix, containing an 8-bit prefix length followed by an
IPv6 address prefix, whose length, in bits, is specified by the
prefix length, padded to a byte boundary.
o Application Traffic (Type TBD8): Each of the Traffic Elements is a
32 bit identifier of an application, from which the traffic is
imported into the backup LSP.
5.1.6. Subobject: Label-Routes 5.1.6. Subobject: Label-Routes
The INGRESS_PROTECTION object in a PATH message from the primary The INGRESS_PROTECTION object in a PATH message from the primary
ingress to the backup ingress will have a Label-Routes sub object ingress to the backup ingress will have a Label-Routes sub object
containing the labels and routes that the next hops of the ingress containing the labels and routes that the next hops of the ingress
use. The Type of the sub object is TBD-8. The sub object has the use. The Type of the sub object is TBD9. The sub object has the
following body: following body:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
~ Subobjects ~ ~ Subobjects ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The Subobjects in the Label-Routes are copied from those in the The Subobjects in the Label-Routes are copied from those in the
RECORD_ROUTE objects in the RESV messages that the primary ingress RECORD_ROUTE objects in the RESV messages that the primary ingress
receives from its next hops for the primary LSP. They MUST contain receives from its next hops for the primary LSP. They MUST contain
the first hops of the LSP, each of which is paired with its label. the first hops of the LSP, each of which is paired with its label.
6. Behavior of Ingress Protection 6. Behavior of Ingress Protection
6.1. Overview 6.1. Overview
There are four parts of ingress protection: 1) setting up the There are four parts of ingress protection: 1) setting up the
necessary backup LSP forwarding state; 2) identifying the failure and necessary backup LSP forwarding state; 2) identifying the failure and
providing the fast repair (as discussed in Sections 3 and 4); 3) providing the fast repair (as discussed in Sections 3 and 4); 3)
maintaining the RSVP-TE control plane state until a global repair can maintaining the RSVP-TE control plane state until a global repair is
be done; and 4) performing the global repair(see Section 6.4). done; and 4) performing the global repair(see Section 6.4).
There are two different proposed signaling approaches to obtain There are two different proposed signaling approaches to obtain
ingress protection. They both use the same new INGRESS_PROTECTION ingress protection. They both use the same new INGRESS_PROTECTION
object. The object is sent in both PATH and RESV messages. object. The object is sent in both PATH and RESV messages.
6.1.1. Relay-Message Method 6.1.1. Relay-Message Method
The primary ingress relays the information for ingress protection of The primary ingress relays the information for ingress protection of
an LSP to the backup ingress via PATH messages. Once the LSP is an LSP to the backup ingress via PATH messages. Once the LSP is
created, the ingress of the LSP sends the backup ingress a PATH created, the ingress of the LSP sends the backup ingress a PATH
skipping to change at page 12, line 4 skipping to change at page 12, line 9
is not any next-hop node after the ingress for all associated sub- is not any next-hop node after the ingress for all associated sub-
LSPs. LSPs.
The key advantage of this approach is that it minimizes the special The key advantage of this approach is that it minimizes the special
handling code requires. Because the backup ingress is on the handling code requires. Because the backup ingress is on the
signaling path, it can receive various notifications. It easily has signaling path, it can receive various notifications. It easily has
access to all the PATH messages needed for modification to be sent to access to all the PATH messages needed for modification to be sent to
refresh control-plane state after a failure. refresh control-plane state after a failure.
6.1.3. Comparing Two Methods 6.1.3. Comparing Two Methods
+-------+-----------+-------+--------------+---------------+---------+ +-------+-----------+-------+--------------+---------------+---------+
|\_ Item|Primary LSP|Config |PATH Msg from |RESV Msg from |Reuse | |\_ Item|Primary LSP|Config |PATH Msg from |RESV Msg from |Reuse |
| \_ |Depends on |Proxy- |Backup Ingress|Primary Ingress|Some | | \_ |Depends on |Proxy- |Backup Ingress|Primary Ingress|Some |
| \|Backup |Ingress|to Primary |to Backup |Existing | | \|Backup |Ingress|to Primary |to Backup |Existing |
|Method |Ingress |ID |Ingress |Ingress |Functions| |Method |Ingress |ID |Ingress |Ingress |Functions|
+-------+-----------+-------+--------------+---------------+---------+ +-------+-----------+-------+--------------+---------------+---------+
|Relay- | No | No | No | No | Yes- | |Relay- | No | No | No | No | Yes- |
|Message| | | | | | |Message| | | | | |
+-------+-----------+-------+--------------+---------------+---------+ +-------+-----------+-------+--------------+---------------+---------+
|Proxy- | Yes | Yes | Yes | Yes | Yes | |Proxy- | Yes | Yes- | Yes | Yes | Yes |
|Ingress| | | | | | |Ingress| | | | | |
+-------+-----------+-------+--------------+---------------+---------+ +-------+-----------+-------+--------------+---------------+---------+
6.2. Ingress Behavior 6.2. Ingress Behavior
The primary ingress must be configured with a couple of pieces of The primary ingress MUST be configured with a couple of pieces of
information for ingress protection. information for ingress protection.
o Backup Ingress Address: The primary ingress must know an IP o Backup Ingress Address: The primary ingress MUST know an IP
address for it to be included in the INGRESS_PROTECTION object. address for it to be included in the INGRESS_PROTECTION object.
o Proxy-Ingress-Id (only needed for Proxy-Ingress Method): The o Proxy-Ingress-Id (only needed for Proxy-Ingress Method): The
Proxy-Ingress-Id is only used in the Record Route Object for Proxy-Ingress-Id is only used in the Record Route Object for
recording the proxy-ingress. If no proxy-ingress-id is specified, recording the proxy-ingress. If no proxy-ingress-id is specified,
then a local interface address that will not otherwise be included then a local interface address that will not otherwise be included
in the Record Route Object can be used. A similar technique is in the Record Route Object can be used. A similar technique is
used in [RFC4090 Sec 6.1.1]. used in [RFC4090 Sec 6.1.1].
o Application Traffic Identifier: The primary ingress and backup o Application Traffic Identifier: The primary ingress and backup
ingress must both know what application traffic should be directed ingress MUST both know what application traffic should be directed
into the LSP. If a list of prefixes in the Traffic Descriptor into the LSP. If a list of prefixes in the Traffic Descriptor
sub-object will not suffice, then a commonly understood sub-object will not suffice, then a commonly understood
Application Traffic Identifier can be sent between the primary Application Traffic Identifier can be sent between the primary
ingress and backup ingress. The exact meaning of the identifier ingress and backup ingress. The exact meaning of the identifier
should be configured similarly at both the primary ingress and should be configured similarly at both the primary ingress and
backup ingress. The Application Traffic Identifier is understood backup ingress. The Application Traffic Identifier is understood
within the unique context of the primary ingress and backup within the unique context of the primary ingress and backup
ingress. ingress.
With this additional information, the primary ingress can create and With this additional information, the primary ingress can create and
signal the necessary RSVP extensions to support ingress protection. signal the necessary RSVP extensions to support ingress protection.
6.2.1. Relay-Message Method 6.2.1. Relay-Message Method
To protect the ingress of an LSP, the ingress does the following To protect the ingress of an LSP, the ingress MUST do the following
after the LSP is up. after the LSP is up.
1. Select a PATH message. 1. Select a PATH message.
2. If the backup ingress is off-path, then send it a PATH message 2. If the backup ingress is off-path, then send it a PATH message
with the content from the selected PATH message and an with the content from the selected PATH message and an
INGRESS_PROTECTION object; else (the backup ingress is a next INGRESS_PROTECTION object; else (the backup ingress is a next
hop, i.e., on-path case) add an INGRESS_PROTECTION object into hop, i.e., on-path case) add an INGRESS_PROTECTION object into
the existing PATH message to the backup ingress (i.e., the next the existing PATH message to the backup ingress (i.e., the next
hop). The object contains the Traffic-Descriptor sub-object, the hop). The object contains the Traffic-Descriptor sub-object, the
Backup Ingress Address sub-object and the Label-Routes sub- Backup Ingress Address sub-object and the Label-Routes sub-
object. The flags is set to indicate whether a Backup P2MP LSP object. The options is set to indicate whether a Backup P2MP LSP
is desired. A second LSP-ID is allocated (if it is not allocated is desired. A secondary LSP-ID is allocated (if it is not
yet) and used in the object. The Label-Routes sub-object allocated yet) and used in the object. The Label-Routes sub-
contains the next-hops of the ingress and their labels. object contains the next-hops of the ingress and their labels.
3. For each of the other PATH messages, send the backup ingress a 3. For each of the other PATH messages, send the backup ingress a
PATH message with the content copied from the message and an PATH message with the content copied from the message and an
empty INGRESS_PROTECTION object, which is an object without any empty INGRESS_PROTECTION object, which is an object without any
Traffic-Descriptor sub-object. Traffic-Descriptor sub-object.
6.2.2. Proxy-Ingress Method 6.2.2. Proxy-Ingress Method
The primary ingress is responsible for starting the RSVP signaling The primary ingress is responsible for starting the RSVP signaling
for the proxy-ingress node. To do this, the following is done for for the proxy-ingress node. To do this, the following MUST be done
the RSVP PATH message. for the RSVP PATH message.
1. Compute the EROs for the LSP as normal for the ingress. 1. Compute the EROs for the LSP as normal for the ingress.
2. If the selected backup ingress node is not the first node on the 2. If the selected backup ingress node is not the first node on the
path (for all sub-LSPs), then insert at the beginning of the ERO path (for all sub-LSPs), then insert at the beginning of the ERO
first the backup ingress node and then the ingress node. first the backup ingress node and then the ingress node.
3. In the PATH RRO, instead of recording the ingress node's address, 3. In the PATH RRO, instead of recording the ingress node's address,
replace it with the Proxy-Ingress-Id. replace it with the Proxy-Ingress-Id.
4. Leave the HOP object populated as usual with information for the 4. Leave the HOP object populated as usual with information for the
ingress-node. ingress-node.
5. Add the INGRESS_PROTECTION object to the PATH message. Allocate 5. Add the INGRESS_PROTECTION object to the PATH message. Allocate
a second LSP-ID to be used in the INGRESS-PROTECTION object. a secondary LSP-ID to be used in the INGRESS-PROTECTION object.
Include the Backup Ingress Address (IPv4 or IPv6) sub-object and Include the Backup Ingress Address (IPv4 or IPv6) sub-object and
the Traffic-Descriptor sub-object. Set or clear the flag the Traffic-Descriptor sub-object. Set or clear the options
indicating that a Backup P2MP LSP is desired. indicating that a Backup P2MP LSP is desired.
6. Optionally, add the FAST-REROUTE object [RFC4090] to the Path 6. Optionally, add the FAST-REROUTE object [RFC4090] to the Path
message. Indicate whether one-to-one backup is desired. message. Indicate whether one-to-one backup is desired.
Indicate whether facility backup is desired. Indicate whether facility backup is desired.
7. The RSVP PATH message is sent to the backup node as normal. 7. The RSVP PATH message is sent to the backup node as normal.
If the ingress detects that it can't communicate with the backup If the ingress detects that it can't communicate with the backup
ingress, then the ingress should instead send the PATH message to the ingress, then the ingress SHOULD instead send the PATH message to the
next-hop indicated in the ERO computed in step 1. Once the ingress next-hop indicated in the ERO computed in step 1. Once the ingress
detects that it can communicate with the backup ingress, the ingress detects that it can communicate with the backup ingress, the ingress
SHOULD follow the steps 1-7 to obtain ingress failure protection. SHOULD follow the steps 1-7 to obtain ingress failure protection.
When the ingress node receives an RSVP PATH message with an INGRESS- When the ingress node receives an RSVP PATH message with an INGRESS-
PROTECTION object and the object specifies that node as the ingress PROTECTION object and the object specifies that node as the ingress
node and the PHOP as the backup ingress node, the ingress node SHOULD node and the PHOP as the backup ingress node, the ingress node SHOULD
remove the INGRESS_PROTECTION object from the PATH message before remove the INGRESS_PROTECTION object from the PATH message before
sending it out. Additionally, the ingress node must store that it sending it out. Additionally, the ingress node MUST store that it
will install ingress forwarding state for the LSP rather than will install ingress forwarding state for the LSP rather than
midpoint forwarding. midpoint forwarding.
When an RSVP RESV message is received by the ingress, it uses the When an RSVP RESV message is received by the ingress, it uses the
NHOP to determine whether the message is received from the backup NHOP to determine whether the message is received from the backup
ingress or from a different node. The stored associated PATH message ingress or from a different node. The stored associated PATH message
contains an INGRESS_PROTECTION object that identifies the backup contains an INGRESS_PROTECTION object that identifies the backup
ingress node. If the RESV message is not from the backup node, then ingress node. If the RESV message is not from the backup node, then
ingress forwarding state should be set up, and the INGRESS_PROTECTION ingress forwarding state SHOULD be set up, and the INGRESS_PROTECTION
object MUST be added to the RESV before it is sent to the NHOP, which object MUST be added to the RESV before it is sent to the NHOP, which
should be the backup node. If the RESV message is from the backup SHOULD be the backup node. If the RESV message is from the backup
node, then the LSP should be considered available for use. node, then the LSP SHOULD be considered available for use.
If the backup ingress node is on the forwarding path, then a RESV is If the backup ingress node is on the forwarding path, then a RESV is
received with an INGRESS_PROTECTION object and an NHOP that matches received with an INGRESS_PROTECTION object and an NHOP that matches
the backup ingress. In this case, the ingress node's address will the backup ingress. In this case, the ingress node's address will
not appear after the backup ingress in the RRO. The ingress node not appear after the backup ingress in the RRO. The ingress node
should set up ingress forwarding state, just as is done if the LSP SHOULD set up ingress forwarding state, just as is done if the LSP
weren't ingress-node protected. weren't ingress-node protected.
6.3. Backup Ingress Behavior 6.3. Backup Ingress Behavior
An LER determines that the ingress local protection is requested for An LER determines that the ingress local protection is requested for
an LSP if the INGRESS_PROTECTION object is included in the PATH an LSP if the INGRESS_PROTECTION object is included in the PATH
message it receives for the LSP. The LER can further determine that message it receives for the LSP. The LER can further determine that
it is the backup ingress if one of its addresses is in the Backup it is the backup ingress if one of its addresses is in the Backup
Ingress Address sub-object of the INGRESS_PROTECTION object. The LER Ingress Address sub-object of the INGRESS_PROTECTION object. The LER
as the backup ingress will assume full responsibility of the ingress as the backup ingress will assume full responsibility of the ingress
after the primary ingress fails. In addition, the LER determines after the primary ingress fails. In addition, the LER determines
that it is off-path if it is not a next hop of the primary ingress. that it is off-path if it is not any node of the LSP.
6.3.1. Backup Ingress Behavior in Off-path Case 6.3.1. Backup Ingress Behavior in Off-path Case
The backup ingress considers itself as a PLR and the primary ingress The backup ingress considers itself as a PLR and the primary ingress
as its next hop and provides a local protection for the primary as its next hop and provides a local protection for the primary
ingress. It behaves very similarly to a PLR providing fast-reroute ingress. It behaves very similarly to a PLR providing fast-reroute
where the primary ingress is considered as the failure-point to where the primary ingress is considered as the failure-point to
protect. Where not otherwise specified, the behavior given in protect. Where not otherwise specified, the behavior given in
[RFC4090] for a PLR should apply. [RFC4090] for a PLR applies.
The backup ingress SHOULD follow the control-options specified in the The backup ingress MUST follow the control-options specified in the
INGRESS_PROTECTION object and the flags and specifications in the INGRESS_PROTECTION object and the flags and specifications in the
FAST-REROUTE object. This applies to providing a P2MP backup if the FAST-REROUTE object. This applies to providing a P2MP backup if the
"P2MP backup" is set, a one-to-one backup if "one-to-one desired" is "P2MP backup" is set, a one-to-one backup if "one-to-one desired" is
set, facility backup if the "facility backup desired" is set, and set, facility backup if the "facility backup desired" is set, and
backup paths that support the desired bandwidth, and administrative- backup paths that support the desired bandwidth, and administrative-
colors that are requested. colors that are requested.
If multiple non empty INGRESS_PROTECTION objects have been received If multiple non empty INGRESS_PROTECTION objects have been received
via multiple PATH messages for the same LSP, then the most recent one via multiple PATH messages for the same LSP, then the most recent one
MUST be the one used. MUST be the one used.
The backup ingress creates the appropriate forwarding state for the The backup ingress creates the appropriate forwarding state for the
backup LSP tunnel(s) to the merge point(s). backup LSP tunnel(s) to the merge point(s).
When the backup ingress sends a RESV message to the primary ingress, When the backup ingress sends a RESV message to the primary ingress,
it should add an INGRESS_PROTECTION object into the message. It it MUST add an INGRESS_PROTECTION object into the message. It MUST
SHOULD set or clear the flags in the object to report "Ingress local set or clear the flags in the object to report "Ingress local
protection available", "Ingress local protection in use", and protection available", "Ingress local protection in use", and
"bandwidth protection". "bandwidth protection".
If the backup ingress doesn't have a backup LSP tunnel to all the If the backup ingress doesn't have a backup LSP tunnel to each of the
merge points, it SHOULD clear "Ingress local protection available". merge points, it SHOULD clear "Ingress local protection available".
[Editor Note: It is possible to indicate the number or which are [Editor Note: It is possible to indicate the number or which are
unprotected via a sub-object if desired.] unprotected via a sub-object if desired.]
When the primary ingress fails, the backup ingress redirects the When the primary ingress fails, the backup ingress redirects the
traffic from a source into the backup P2P LSPs or the backup P2MP LSP traffic from a source into the backup P2P LSPs or the backup P2MP LSP
transmitting the traffic to the next hops of the primary ingress, transmitting the traffic to the next hops of the primary ingress,
where the traffic is merged into the protected LSP. where the traffic is merged into the protected LSP.
In this case, the backup ingress keeps the PATH message with the In this case, the backup ingress MUST keep the PATH message with the
INGRESS_PROTECTION object received from the primary ingress and the INGRESS_PROTECTION object received from the primary ingress and the
RESV message with the INGRESS_PROTECTION object to be sent to the RESV message with the INGRESS_PROTECTION object to be sent to the
primary ingress. The backup ingress sets the "local protection in primary ingress. The backup ingress MUST set the "local protection
use" flag in the RESV message, indicating that the backup ingress is in use" flag in the RESV message, indicating that the backup ingress
actively redirecting the traffic into the backup P2P LSPs or the is actively redirecting the traffic into the backup P2P LSPs or the
backup P2MP LSP for locally protecting the primary ingress failure. backup P2MP LSP for locally protecting the primary ingress failure.
Note that the RESV message with this piece of information will not be Note that the RESV message with this piece of information will not be
sent to the primary ingress because the primary ingress has failed. sent to the primary ingress because the primary ingress has failed.
If the backup ingress has not received any PATH message from the If the backup ingress has not received any PATH message from the
primary ingress for an extended period of time (e.g., a cleanup primary ingress for an extended period of time (e.g., a cleanup
timeout interval) and a confirmed primary ingress failure did not timeout interval) and a confirmed primary ingress failure did not
occur, then the standard RSVP soft-state removal SHOULD occur. The occur, then the standard RSVP soft-state removal SHOULD occur. The
backup ingress SHALL remove the state for the PATH message from the backup ingress SHALL remove the state for the PATH message from the
primary ingress, and tear down the one-to-one backup LSPs for primary ingress, and tear down the one-to-one backup LSPs for
protecting the primary ingress if one-to-one backup is used or unbind protecting the primary ingress if one-to-one backup is used or unbind
the facility backup LSPs if facility backup is used. the facility backup LSPs if facility backup is used.
When the backup ingress receives a PATH message from the primary When the backup ingress receives a PATH message from the primary
ingress for locally protecting the primary ingress of a protected ingress for locally protecting the primary ingress of a protected
LSP, it checks to see if any critical information has been changed. LSP, it MUST check to see if any critical information has been
If the next hops of the primary ingress are changed, the backup changed. If the next hops of the primary ingress are changed, the
ingress SHALL update its backup LSP(s) accordingly. backup ingress SHALL update its backup LSP(s) accordingly.
6.3.1.1. Relay-Message Method 6.3.1.1. Relay-Message Method
When the backup ingress receives a PATH message with an non empty When the backup ingress receives a PATH message with an non empty
INGRESS_PROTECTION object, it examines the object to learn what INGRESS_PROTECTION object, it examines the object to learn what
traffic associated with the LSP. It determines the next-hops to be traffic associated with the LSP. It determines the next-hops to be
merged to by examining the Label-Routes sub-object in the object. merged to by examining the Label-Routes sub-object in the object.
The backup ingress stores the PATH message received from the primary The backup ingress MUST store the PATH message received from the
ingress, but does NOT forward it. primary ingress, but NOT forward it.
The backup ingress responds with a RESV to the PATH message received The backup ingress responds with a RESV to the PATH message received
from the primary ingress. If the INGRESS_PROTECTION object is not from the primary ingress. If the INGRESS_PROTECTION object is not
"empty", the backup ingress SHALL send the RESV message with the "empty", the backup ingress SHALL send the RESV message with the
state indicating protection is available after the backup LSP(s) are state indicating protection is available after the backup LSP(s) are
successfully established. successfully established.
6.3.1.2. Proxy-Ingress Method 6.3.1.2. Proxy-Ingress Method
The backup ingress determines the next-hops to be merged to by The backup ingress determines the next-hops to be merged to by
collecting the set of the pair of (IPv4/IPv6 sub-object, Label sub- collecting the set of the pair of (IPv4/IPv6 sub-object, Label sub-
object) from the Record Route Object of each RESV that are closest to object) from the Record Route Object of each RESV that are closest to
the top and not the Ingress router; this should be the second to the the top and not the Ingress router; this should be the second to the
top pair. If a Label-Routes sub-object is included in the top pair. If a Label-Routes sub-object is included in the
INGRESS_PROTECTION object, the included IPv4/IPv6 sub-objects are INGRESS_PROTECTION object, the included IPv4/IPv6 sub-objects are
used to filter the set down to the specific next-hops where used to filter the set down to the specific next-hops where
protection is desired. A RESV message must have been received before protection is desired. A RESV message MUST have been received before
the Backup Ingress can create or select the appropriate backup LSP. the Backup Ingress can create or select the appropriate backup LSP.
When the backup ingress receives a PATH message with the When the backup ingress receives a PATH message with the
INGRESS_PROTECTION object, the backup ingress examines the object to INGRESS_PROTECTION object, the backup ingress examines the object to
learn what traffic associated with the LSP. The backup ingress learn what traffic associated with the LSP. The backup ingress
forwards the PATH message to the ingress node with the normal RSVP forwards the PATH message to the ingress node with the normal RSVP
changes. changes.
When the backup ingress receives a RESV message with the When the backup ingress receives a RESV message with the
INGRESS_PROTECTION object, the backup ingress records an IMPLICIT- INGRESS_PROTECTION object, the backup ingress records an IMPLICIT-
NULL label in the RRO. Then the backup ingress forwards the RESV NULL label in the RRO. Then the backup ingress forwards the RESV
message to the ingress node, which is acting for the proxy ingress. message to the ingress node, which is acting for the proxy ingress.
6.3.2. Backup Ingress Behavior in On-path Case 6.3.2. Backup Ingress Behavior in On-path Case
An LER as the backup ingress determines that it is on-path if one of An LER as the backup ingress determines that it is on-path if one of
its addresses is a next hop of the primary ingress (and the primary its addresses is a next hop of the primary ingress (and for Proxy-
ingress is not its next hop via checking the PATH message with the Ingress Method the primary ingress is not its next hop via checking
INGRESS_PROTECTION object received from the primary ingress for the PATH message with the INGRESS_PROTECTION object received from the
Proxy-Ingress Method). The LER on-path sends the corresponding PATH primary ingress). The LER on-path MUST send the corresponding PATH
messages without any INGRESS_PROTECTION object to its next hops. It messages without any INGRESS_PROTECTION object to its next hops. It
creates a number of backup P2P LSPs or a backup P2MP LSP from itself creates a number of backup P2P LSPs or a backup P2MP LSP from itself
to the other next hops (i.e., the next hops other than the backup to the other next hops (i.e., the next hops other than the backup
ingress) of the primary ingress. The other next hops are from the ingress) of the primary ingress. The other next hops are from the
Label-Routes sub object. Label-Routes sub object.
It also creates a forwarding entry, which sends/multicasts the It also creates a forwarding entry, which sends/multicasts the
traffic from the source to the next hops of the backup ingress along traffic from the source to the next hops of the backup ingress along
the protected LSP when the primary ingress fails. The traffic is the protected LSP when the primary ingress fails. The traffic is
described by the Traffic-Descriptor. described by the Traffic-Descriptor.
After the forwarding entry is created, all the backup P2P LSPs or the After the forwarding entry is created, all the backup P2P LSPs or the
backup P2MP LSP is up and associated with the protected LSP, the backup P2MP LSP is up and associated with the protected LSP, the
backup ingress sends the primary ingress the RESV message with the backup ingress MUST send the primary ingress the RESV message with
INGRESS_PROTECTION object containing the state of the local the INGRESS_PROTECTION object containing the state of the local
protection such as "local protection available" flag set to one, protection such as "local protection available" flag set to one,
which indicates that the primary ingress is locally protected. which indicates that the primary ingress is locally protected.
When the primary ingress fails, the backup ingress sends/multicasts When the primary ingress fails, the backup ingress sends/multicasts
the traffic from the source to its next hops along the protected LSP the traffic from the source to its next hops along the protected LSP
and imports the traffic into each of the backup P2P LSPs or the and imports the traffic into each of the backup P2P LSPs or the
backup P2MP LSP transmitting the traffic to the other next hops of backup P2MP LSP transmitting the traffic to the other next hops of
the primary ingress, where the traffic is merged into protected LSP. the primary ingress, where the traffic is merged into protected LSP.
During the local repair, the backup ingress continues to send the During the local repair, the backup ingress MUST continue to send the
PATH messages to its next hops as before, keeps the PATH message with PATH messages to its next hops as before, keep the PATH message with
the INGRESS_PROTECTION object received from the primary ingress and the INGRESS_PROTECTION object received from the primary ingress and
the RESV message with the INGRESS_PROTECTION object to be sent to the the RESV message with the INGRESS_PROTECTION object to be sent to the
primary ingress. It sets the "local protection in use" flag in the primary ingress. It MUST set the "local protection in use" flag in
RESV message. the RESV message.
6.3.3. Failure Detection and Refresh PATH Messages 6.3.3. Failure Detection and Refresh PATH Messages
As described in [RFC4090], it is necessary to refresh the PATH As described in [RFC4090], it is necessary to refresh the PATH
messages via the backup LSP(s). The Backup Ingress MUST wait to messages via the backup LSP(s). The Backup Ingress MUST wait to
refresh the PATH messages until it can accurately detect that the refresh the PATH messages until it can accurately detect that the
ingress node has failed. An example of such an accurate detection ingress node has failed. An example of such an accurate detection
would be that the IGP has no bi-directional links to the ingress node would be that the IGP has no bi-directional links to the ingress node
and the last change was long enough in the past that changes should and the last change was long enough in the past that changes should
have been received (i.e., an IGP network convergence time or have been received (i.e., an IGP network convergence time or
approximately 2-3 seconds) or a BFD session to the primary ingress' approximately 2-3 seconds) or a BFD session to the primary ingress'
loopback address has failed and stayed failed after the network has loopback address has failed and stayed failed after the network has
reconverged. reconverged.
As described in [RFC4090 Section 6.4.3], the backup ingress, acting As described in [RFC4090 Section 6.4.3], the backup ingress, acting
as PLR, SHOULD modify and send any saved PATH messages associated as PLR, MUST modify and send any saved PATH messages associated with
with the primary LSP to the corresponding next hops through backup the primary LSP to the corresponding next hops through backup LSP(s).
LSP(s). Any PATH message sent will not contain any Any PATH message sent will not contain any INGRESS_PROTECTION object.
INGRESS_PROTECTION object. The RSVP_HOP object in the message The RSVP_HOP object in the message contains an IP source address
contains an IP source address belonging to the backup ingress. The belonging to the backup ingress. The sender template object has the
sender template object has the backup ingress address as its tunnel backup ingress address as its tunnel sender address.
sender address.
6.4. Revertive Behavior 6.4. Revertive Behavior
Upon a failure event in the (primary) ingress of a protected LSP, the Upon a failure event in the (primary) ingress of a protected LSP, the
protected LSP is locally repaired by the backup ingress. There are a protected LSP is locally repaired by the backup ingress. There are a
couple of basic strategies for restoring the LSP to a full working couple of basic strategies for restoring the LSP to a full working
path. path.
- Revert to Primary Ingress: When the primary ingress is restored, - Revert to Primary Ingress: When the primary ingress is restored,
it re-signals each of the LSPs that start from the primary it re-signals each of the LSPs that start from the primary
skipping to change at page 18, line 41 skipping to change at page 18, line 46
switched back to the primary ingress from the backup ingress. switched back to the primary ingress from the backup ingress.
- Global Repair by Backup Ingress: After determining that the - Global Repair by Backup Ingress: After determining that the
primary ingress of an LSP has failed, the backup ingress computes primary ingress of an LSP has failed, the backup ingress computes
a new optimal path, signals a new LSP along the new path, and a new optimal path, signals a new LSP along the new path, and
switches the traffic to the new LSP. switches the traffic to the new LSP.
6.4.1. Revert to Primary Ingress 6.4.1. Revert to Primary Ingress
If "Revert to Primary Ingress" is desired for a protected LSP, the If "Revert to Primary Ingress" is desired for a protected LSP, the
(primary) ingress of the LSP re-signals the LSP that starts from the (primary) ingress of the LSP SHOULD re-signal the LSP that starts
primary ingress after the primary ingress restores. After the LSP is from the primary ingress after the primary ingress restores. After
re-signaled successfully, the traffic can be switched back to the the LSP is re-signaled successfully, the traffic SHOULD be switched
primary ingress from the backup ingress on the source node and back to the primary ingress from the backup ingress on the source
redirected into the LSP starting from the primary ingress. node and redirected into the LSP starting from the primary ingress.
The primary ingress can specify the "Revert to Ingress" control- The primary ingress can specify the "Revert to Ingress" control-
option in the INGRESS_PROTECTION object in the PATH messages to the option in the INGRESS_PROTECTION object in the PATH messages to the
backup ingress. After receiving the "Revert to Ingress" control- backup ingress. After receiving the "Revert to Ingress" control-
option, the backup ingress stops sending/refreshing PATH messages for option, the backup ingress MUST stop sending/refreshing PATH messages
the protected LSP. for the protected LSP.
6.4.2. Global Repair by Backup Ingress 6.4.2. Global Repair by Backup Ingress
When the backup ingress has determined that the primary ingress of When the backup ingress has determined that the primary ingress of
the protected LSP has failed (e.g., via the IGP), it can compute a the protected LSP has failed (e.g., via the IGP), it can compute a
new path and signal a new LSP along the new path so that it no longer new path and signal a new LSP along the new path so that it no longer
relies upon local repair. To do this, the backup ingress uses the relies upon local repair. To do this, the backup ingress MUST use
same tunnel sender address in the Sender Template Object and uses the the same tunnel sender address in the Sender Template Object and the
previously allocated second LSP-ID in the INGRESS_PROTECTION object previously allocated secondary LSP-ID in the INGRESS_PROTECTION
of the PATH message as the LSP-ID of the new LSP. This allows the object of the PATH message as the LSP-ID of the new LSP. This allows
new LSP to share resources with the old LSP. In addition, if the the new LSP to share resources with the old LSP. In addition, if the
Ingress recovers, the Backup Ingress SHOULD send it RESVs with the Ingress recovers, the Backup Ingress SHOULD send it RESVs with the
INGRESS_PROTECTION object where the "Revert to Ingress" is specified. INGRESS_PROTECTION object where the "Revert to Ingress" is specified.
The Secondary LSP ID should be the unused LSP ID - while the LSP ID The Secondary LSP ID MUST be the unused LSP ID - while the LSP ID
signaled in the RESV will be that currently active. The Ingress can signaled in the RESV will be that currently active. The Ingress can
learn from the RESVs what to signal. Even if the Ingress does not learn from the RESVs what to signal. Even if the Ingress does not
take over, the RESVs notify it that the particular LSP IDs are in take over, the RESVs notify it that the particular LSP IDs are in
use. The Backup Ingress can reoptimize the new LSP as necessary use. The Backup Ingress can reoptimize the new LSP as necessary
until the Ingress recovers. Alternately, the Backup Ingress can until the Ingress recovers. Alternately, the Backup Ingress can
create a new LSP with no bandwidth reservation that duplicates the create a new LSP with no bandwidth reservation that duplicates the
path(s) of the protected LSP, move traffic to the new LSP, delete the path(s) of the protected LSP, move traffic to the new LSP, delete the
protected LSP, and then resignal the new LSP with bandwidth. protected LSP, and then resignal the new LSP with bandwidth.
7. Security Considerations 7. Security Considerations
skipping to change at page 19, line 43 skipping to change at page 19, line 47
8. IANA Considerations 8. IANA Considerations
IANA is requested to administer the assignment of new values defined IANA is requested to administer the assignment of new values defined
in this document and summarized in this section. in this document and summarized in this section.
8.1. A New Class Number 8.1. A New Class Number
IANA maintains a registry called "Class Names, Class Numbers, and IANA maintains a registry called "Class Names, Class Numbers, and
Class Types" under "Resource Reservation Protocol-Traffic Engineering Class Types" under "Resource Reservation Protocol-Traffic Engineering
(RSVP-TE) Parameters". IANA is requested to assign a new Class (RSVP-TE) Parameters". IANA is requested to assign a new Class
Number for new object EGRESS_BACKUP as follows: Number for new object INGRESS_PROTECTION as follows:
+====================+===============+============================+ +====================+===============+============================+
| Class Names | Class Numbers | Class Types | | Class Names | Class Numbers | Class Types |
+====================+===============+============================+ +====================+===============+============================+
| INGRESS_PROTECTION | TBD1 (>192) | 1: INGRESS_PROTECTION_IPv4 | | INGRESS_PROTECTION | TBD (>192) | 1: INGRESS_PROTECTION_IPv4 |
| | +----------------------------+ | | +----------------------------+
| | | 2: INGRESS_PROTECTION_IPv6 | | | | 2: INGRESS_PROTECTION_IPv6 |
+--------------------+---------------+----------------------------+ +--------------------+---------------+----------------------------+
IANA is requested to assign Types for new TLVs in the new objects as IANA is requested to assign Types for new TLVs in the new objects as
follows: follows:
Type Name Allowed in Type Name Allowed in
1 BACKUP_INGRESS_IPv4_ADDRESS INGRESS_PROTECTION_IPv4 1 BACKUP_INGRESS_IPv4_ADDRESS INGRESS_PROTECTION_IPv4
2 BACKUP_INGRESS_IPv6_ADDRESS INGRESS_PROTECTION_IPv6 2 BACKUP_INGRESS_IPv6_ADDRESS INGRESS_PROTECTION_IPv6
3 INGRESS_IPv4_ADDRESS INGRESS_PROTECTION_IPv4 3 INGRESS_IPv4_ADDRESS INGRESS_PROTECTION_IPv4
4 INGRESS_IPv6_ADDRESS INGRESS_PROTECTION_IPv6 4 INGRESS_IPv6_ADDRESS INGRESS_PROTECTION_IPv6
5 TRAFFIC_DESCRIPTOR_INTERFACE INGRESS_PROTECTION 5 TRAFFIC_DESCRIPTOR_INTERFACE INGRESS_PROTECTION
6 TRAFFIC_DESCRIPTOR_IPv4_PREFIX INGRESS_PROTECTION_IPv4 6 TRAFFIC_DESCRIPTOR_IPv4_PREFIX INGRESS_PROTECTION_IPv4
7 TRAFFIC_DESCRIPTOR_IPv6_PREFIX INGRESS_PROTECTION_IPv6 7 TRAFFIC_DESCRIPTOR_IPv6_PREFIX INGRESS_PROTECTION_IPv6
8 LabeL_Routes INGRESS_PROTECTION 8 TRAFFIC_DESCRIPTOR_APPLICATION INGRESS_PROTECTION
9 LabeL_Routes INGRESS_PROTECTION
9. Contributors 9. Contributors
Renwei Li Renwei Li
Huawei Technologies Huawei Technologies
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 Santa Clara, CA 95050
USA USA
Email: renwei.li@huawei.com Email: renwei.li@huawei.com
skipping to change at page 21, line 22 skipping to change at page 21, line 24
Juniper Networks Juniper Networks
10 Technology Park Drive 10 Technology Park Drive
Westford, MA 01886 Westford, MA 01886
USA USA
Email: mjork@juniper.net Email: mjork@juniper.net
10. Acknowledgement 10. Acknowledgement
The authors would like to thank Nobo Akiya, Rahul Aggarwal, Eric The authors would like to thank Nobo Akiya, Rahul Aggarwal, Eric
Osborne, Ross Callon, Loa Andersson, Daniel King, Michael Yue, Osborne, Ross Callon, Loa Andersson, Daniel King, Michael Yue,
Olufemi Komolafe, Rob Rennison, Neil Harrison, Kannan Sampath, and Olufemi Komolafe, Rob Rennison, Neil Harrison, Kannan Sampath,
Ronhazli Adam for their valuable comments and suggestions on this Gregory Mirsky, and Ronhazli Adam for their valuable comments and
draft. suggestions on this draft.
11. Normative References 11. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] 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.
[RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, "Multiprotocol
Label Switching Architecture", RFC 3031, January 2001. Label Switching Architecture", RFC 3031, January 2001.
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V., [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
 End of changes. 68 change blocks. 
124 lines changed or deleted 134 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/