draft-ietf-mpls-summary-frr-rsvpte-06.txt   draft-ietf-mpls-summary-frr-rsvpte-07.txt 
MPLS Working Group M. Taillon MPLS Working Group M. Taillon
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track T. Saad, Ed. Updates: RFC4090 (if approved) T. Saad, Ed.
Expires: May 21, 2020 Juniper Networks Intended status: Standards Track Juniper Networks
R. Gandhi Expires: June 13, 2020 R. Gandhi
Cisco Systems, Inc. Cisco Systems, Inc.
A. Deshmukh A. Deshmukh
Juniper Networks Juniper Networks
M. Jork M. Jork
128 Technology 128 Technology
V. Beeram V. Beeram
Juniper Networks Juniper Networks
November 18, 2019 December 11, 2019
RSVP-TE Summary Fast Reroute Extensions for LSP Tunnels RSVP-TE Summary Fast Reroute Extensions for LSP Tunnels
draft-ietf-mpls-summary-frr-rsvpte-06 draft-ietf-mpls-summary-frr-rsvpte-07
Abstract Abstract
This document defines Resource Reservation Protocol (RSVP) Traffic- This document updates the Resource Reservation Protocol (RSVP)
Engineering (TE) signaling extensions that reduce the amount of RSVP Traffic-Engineering (TE) procedures that are defined in RFC 4090 for
signaling required for Fast Reroute (FRR) procedures and subsequently facility backup protection. The updates include extensions that
improve the scalability of the RSVP-TE signaling when undergoing FRR reduce the amount of signaling and processing that occurs during Fast
convergence after a link or node failure. Such extensions allow the Reroute (FRR), and subsequently, improves scalability when undergoing
RSVP message exchange between the Point of Local Repair (PLR) and the FRR convergence after a link or node failure. These extensions allow
Merge Point (MP) to be independent of the number of protected Label the RSVP message exchange between the Point of Local Repair (PLR) and
Switched Paths (LSPs) traversing between them when facility bypass the Merge Point (MP) to be independent of the number of protected
FRR protection is used. The signaling extensions are fully backwards Label Switched Paths (LSPs) traversing between them when facility
compatible with nodes that do not support them. bypass FRR protection is used. The signaling extensions are fully
backwards compatible with nodes that do not support them.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://datatracker.ietf.org/drafts/current/. Drafts is at https://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 May 21, 2020. This Internet-Draft will expire on June 13, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 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
(https://trustee.ietf.org/license-info) in effect on the date of (https://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 39 skipping to change at page 2, line 39
3.1.2. IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID . . . 7 3.1.2. IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID . . . 7
3.2. B-SFRR-Active Extended ASSOCIATION Object . . . . . . . . 10 3.2. B-SFRR-Active Extended ASSOCIATION Object . . . . . . . . 10
3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID . . . . . 11 3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID . . . . . 11
3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID . . . . . 12 3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID . . . . . 12
3.3. Signaling Procedures Prior to Failure . . . . . . . . . . 13 3.3. Signaling Procedures Prior to Failure . . . . . . . . . . 13
3.3.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 14 3.3.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 14
3.3.2. MP Signaling Procedure . . . . . . . . . . . . . . . 14 3.3.2. MP Signaling Procedure . . . . . . . . . . . . . . . 14
3.4. Signaling Procedures Post Failure . . . . . . . . . . . . 15 3.4. Signaling Procedures Post Failure . . . . . . . . . . . . 15
3.4.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 15 3.4.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 15
3.4.2. MP Signaling Procedure . . . . . . . . . . . . . . . 16 3.4.2. MP Signaling Procedure . . . . . . . . . . . . . . . 16
3.5. Refreshing Summary FRR Active LSPs . . . . . . . . . . . 16 3.5. Refreshing Summary FRR Active LSPs . . . . . . . . . . . 17
4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 17 4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 17
5. Security Considerations . . . . . . . . . . . . . . . . . . . 17 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
9.1. Normative References . . . . . . . . . . . . . . . . . . 18 9.1. Normative References . . . . . . . . . . . . . . . . . . 18
9.2. Informative References . . . . . . . . . . . . . . . . . 19 9.2. Informative References . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
The Fast Reroute (FRR) procedures defined in [RFC4090] describe the The Fast Reroute (FRR) procedures defined in [RFC4090] describe the
mechanisms for the Point of Local Repair (PLR) to reroute traffic and mechanisms for the Point of Local Repair (PLR) to reroute traffic and
signaling of a protected RSVP-TE LSP onto the bypass tunnel in the signaling of a protected RSVP-TE LSP onto the bypass tunnel in the
event of a TE link or node failure. Such signaling procedures are event of a TE link or node failure. Such signaling procedures are
skipping to change at page 3, line 28 skipping to change at page 3, line 28
For example, in a large scale RSVP-TE LSPs deployment, a single LSR For example, in a large scale RSVP-TE LSPs deployment, a single LSR
acting as a PLR node may host tens of thousands of protected RSVP-TE acting as a PLR node may host tens of thousands of protected RSVP-TE
LSPs egressing the same link, and also act as a MP node for similar LSPs egressing the same link, and also act as a MP node for similar
number of LSPs that ingress on the same link. In the event of the number of LSPs that ingress on the same link. In the event of the
failure of the link or neighbor node, the RSVP-TE control plane of failure of the link or neighbor node, the RSVP-TE control plane of
the node when acting as PLR becomes busy rerouting protected LSPs the node when acting as PLR becomes busy rerouting protected LSPs
signaling over the bypass tunnel(s) in one direction, and when acting signaling over the bypass tunnel(s) in one direction, and when acting
as an MP node becomes busy merging RSVP states from signaling as an MP node becomes busy merging RSVP states from signaling
received over bypass tunnels for LSP(s) in the reverse direction. received over bypass tunnels for LSP(s) in the reverse direction.
Subsequently, the head-end LER(s) that are notified of the local Subsequently, the head-end LER(s) that are notified of the local
repair at downstream LSR will attempt to (re)converge affected RSVP- repair at downstream LSR will attempt to (re)converge the affected
TE LSPs onto newly computed paths - possibly traversing the same RSVP-TE LSPs onto newly computed paths - possibly traversing the same
previously affected LSR(s). As a result, the RSVP-TE control plane previously affected LSR(s). As a result, the RSVP-TE control plane
at the PLR and MP becomes overwhelmed by the amount of FRR RSVP-TE at the PLR and MP becomes overwhelmed by the amount of FRR RSVP-TE
processing overhead following the link or node failure, and the processing overhead following the link or node failure, and due to
competing other control plane protocol(s) (e.g. the IGP) that undergo other control plane protocol(s) (e.g. the IGP) that undergo
their convergence at the same time. convergence on the same node at the same time too.
The extensions defined in this document enable a MP node to become The extensions defined in this document update the procedures defined
aware of the PLR node's bypass tunnel assignment group and allow FRR in [RFC4090] for facility backup protection to enable a MP node to
procedures between PLR node and MP node to be signaled and processed become aware of the PLR node's bypass tunnel assignment group and
on groups of LSPs. allow the FRR procedures between PLR node and MP node to be signaled
and processed on groups of protected LSPs.
As defined in [RFC2961], Summary Refresh procedures use MESSAGE_ID to As defined in [RFC2961], Summary Refresh procedures use MESSAGE_ID to
refresh the RSVP Path and Resv states to help with the scale. The refresh the RSVP Path and Resv states to help with the scale. The
MESSAGE_ID information for the rerouted PATH and RESV states are extensions defined in this document allow the MESSAGE_ID information
exchanged between PLR and MP nodes between PLR and MP nodes a priori for the rerouted Path and Resv states to be exchanged between PLR and
to the fault such that Summary Refresh procedures defined in MP nodes a priori to the fault such that Summary Refresh procedures
[RFC2961] can continue to be used to refresh the rerouted state(s) can continue to be used to refresh the rerouted state(s) after FRR
after FRR has occurred. has occurred.
2. Conventions Used in This Document 2. Conventions Used in This Document
2.1. Terminology 2.1. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
skipping to change at page 5, line 35 skipping to change at page 5, line 35
The MP maintains the PLR group assignments learned via signaling, and The MP maintains the PLR group assignments learned via signaling, and
acknowledges the group assignments via signaling. Once the PLR acknowledges the group assignments via signaling. Once the PLR
receives the acknowledgment, FRR signaling can proceed as group receives the acknowledgment, FRR signaling can proceed as group
based. based.
The PLR node that supports Summary FRR procedures adds the Extended The PLR node that supports Summary FRR procedures adds the Extended
ASSOCIATION object with Type B-SFRR-Ready and respective Extended ASSOCIATION object with Type B-SFRR-Ready and respective Extended
Association ID in the RSVP Path message of the protected LSP to Association ID in the RSVP Path message of the protected LSP to
inform the MP of the PLR's assigned bypass tunnel, Summary FRR inform the MP of the PLR's assigned bypass tunnel, Summary FRR
Bypass_Group_Identifier, and the MESSAGE_ID that the PLR will use to Bypass_Group_Identifier, and the MESSAGE_ID that the PLR will use to
refresh the protected LSP PATH state after FRR occurs. refresh the protected LSP Path state after FRR occurs.
The MP node that supports Summary FRR procedures adds the B-SFRR- The MP node that supports Summary FRR procedures adds the B-SFRR-
Ready Extended ASSOCIATION object and respective Extended Association Ready Extended ASSOCIATION object and respective Extended Association
ID in the RSVP Resv message of the protected LSP to acknowledge the ID in the RSVP Resv message of the protected LSP to acknowledge the
PLR's bypass tunnel assignment, and provide the MESSAGE_ID object PLR's bypass tunnel assignment, and provide the MESSAGE_ID object
that the MP node will use to refresh the protected LSP RESV state that the MP node will use to refresh the protected LSP Resv state
after FRR occurs. after FRR occurs.
This document also defines a new Association Type for the Extended This document also defines a new Association Type for the Extended
ASSOCIATION object and new Extended Association ID to describe the B- ASSOCIATION object and new Extended Association ID to describe the B-
SFRR-Active association. The B-SFRR-Active Extended ASSOCIATION SFRR-Active association. The B-SFRR-Active Extended ASSOCIATION
object and Extended Association ID are sent by PLR after activating object and Extended Association ID are sent by PLR after activating
FRR procedures on the PLR. The B-SFRR-Active Extended ASSOCIATION FRR procedures on the PLR. The B-SFRR-Active Extended ASSOCIATION
object and Extended Association ID are sent within the RSVP Path object and Extended Association ID are sent within the RSVP Path
message of the bypass LSP to inform the MP node that one or more message of the bypass tunnel to inform the MP node that one or more
groups of protected LSPs protected by the bypass tunnel are now being groups of protected LSPs protected by the bypass tunnel are now being
rerouted over the bypass tunnel. rerouted over the bypass tunnel.
3.1. B-SFRR-Ready Extended ASSOCIATION Object 3.1. B-SFRR-Ready Extended ASSOCIATION Object
The Extended ASSOCIATION object is populated using the rules defined The Extended ASSOCIATION object is populated using the rules defined
below to associate a protected LSP with the bypass LSP that is below to associate a protected LSP with the bypass tunnel that is
protecting it when Summary FRR procedures are enabled. protecting it when Summary FRR procedures are enabled.
The Association Type, Association ID, and Association Source MUST be The Association Type, Association ID, and Association Source MUST be
set as defined in [RFC4872] for the ASSOCIATION Object. More set as defined in [RFC4872] for the ASSOCIATION Object. More
specifically: specifically:
Association Source: Association Source:
The Association Source is set to an address of the PLR node. The Association Source is set to an address of the PLR node.
skipping to change at page 9, line 31 skipping to change at page 9, line 31
Bypass_Group_Identifier: 32 bits Bypass_Group_Identifier: 32 bits
The bypass tunnel group identifier. The bypass tunnel group identifier.
MESSAGE_ID MESSAGE_ID
A MESSAGE_ID object as defined by [RFC2961]. A MESSAGE_ID object as defined by [RFC2961].
The PLR assigns a bypass tunnel and Bypass_Group_Identifier for each The PLR assigns a bypass tunnel and Bypass_Group_Identifier for each
protected LSP. The same Bypass_Group_Identifier is used for the set protected LSP. The same Bypass_Group_Identifier is used for the set
of protected LSPs that share the same bypass tunnel and traverse the of protected LSPs that share the same bypass tunnel, traverse the
same egress link and are not already rerouted. The PLR also same egress link, and are not already rerouted. The PLR also
generates a MESSAGE_ID object (flags SHOULD be clear, Epoch and generates a MESSAGE_ID object (flags SHOULD be clear, Epoch and
Message_Identifier MUST be set according to [RFC2961]). Message_Identifier MUST be set according to [RFC2961]).
The PLR MUST generate a new Message_Identifier each time the contents The PLR MUST generate a new Message_Identifier each time the contents
of the B-SFRR-Ready Extended ASSOCIATION ID changes (e.g. when PLR of the B-SFRR-Ready Extended ASSOCIATION ID changes (e.g. when PLR
node changes the bypass tunnel assignment). node changes the bypass tunnel assignment).
The PLR node notifies the MP node of the bypass tunnel assignment via The PLR node notifies the MP node of the bypass tunnel assignment via
adding a B-SFRR-Ready Extended ASSOCIATION object and Association ID adding a B-SFRR-Ready Extended ASSOCIATION object and Extended
in the RSVP Path message for the protected LSP using procedures Association ID in the RSVP Path message for the protected LSP using
described in Section 3.4. procedures described in Section 3.4.
The MP node acknowledges the PLR node assignment by signaling the B- The MP node acknowledges the assignment to the PLR node by signaling
SFRR-Ready Extended ASSOCIATION object and Association ID within the the B-SFRR-Ready Extended ASSOCIATION object and Extended Association
RSVP Resv message of the protected LSP. With exception of the ID within the RSVP Resv message of the protected LSP. With exception
MESSAGE_ID objects, all other fields of the received in the B-SFRR- of the MESSAGE_ID objects, all other fields of the received in the B-
Ready Extended ASSOCIATION ID in the RSVP Path message are copied SFRR-Ready Extended ASSOCIATION ID in the RSVP Path message are
into the B-SFRR-Ready Extended ASSOCIATION ID to be added in the Resv copied into the B-SFRR-Ready Extended ASSOCIATION ID to be added in
message. The MESSAGE_ID object is set according to [RFC2961] with the Resv message. The MESSAGE_ID object is set according to
the Flags being clear. A new Message_Identifier MUST be used to
acknowledge an updated PLR assignment. [RFC2961] with the Flags being clear. A new Message_Identifier MUST
be used to acknowledge an updated PLR assignment.
The PLR considers the protected LSP as Summary FRR capable only if The PLR considers the protected LSP as Summary FRR capable only if
all the fields in the B-SFRR-Ready Extended ASSOCIATION ID that are all the fields in the B-SFRR-Ready Extended ASSOCIATION ID that are
sent in the RSVP Path message and the ones received in the RSVP Resv sent in the RSVP Path message and the ones received in the RSVP Resv
message (with exception of the MESSAGE_ID) match. If it does not message (with exception of the MESSAGE_ID) match. If it does not
match, or if B-SFRR-Ready Extended ASSOCIATION object is absent in a match, or if B-SFRR-Ready Extended ASSOCIATION object is absent in a
subsequent refresh, the PLR node MUST consider the protected LSP as subsequent refresh, the PLR node MUST consider the protected LSP as
not Summary FRR capable. not Summary FRR capable.
3.2. B-SFRR-Active Extended ASSOCIATION Object 3.2. B-SFRR-Active Extended ASSOCIATION Object
The Extended ASSOCIATION object for B-SFRR-Active association type is The Extended ASSOCIATION object for B-SFRR-Active association type is
populated by a PLR node to indicate to the MP node (bypass tunnel populated by a PLR node to indicate to the MP node (bypass tunnel
destination) that one or more groups of protected LSPs that are being destination) that one or more groups of Summary FRR protected LSPs
protected by the specified bypass tunnel are being rerouted over the that are being protected by the bypass tunnel are being rerouted over
bypass tunnel. the bypass tunnel.
The B-SFRR-Active Extended ASSOCIATION object is carried in the RSVP The B-SFRR-Active Extended ASSOCIATION object is carried in the RSVP
Path message of a bypass LSP and signaled downstream towards the MP Path message of the bypass tunnel and signaled downstream towards the
(bypass LSP destination). MP (bypass tunnel destination).
The Association Type, Association ID, and Association Source MUST be The Association Type, Association ID, and Association Source MUST be
set as defined in [RFC4872] for the ASSOCIATION Object. More set as defined in [RFC4872] for the ASSOCIATION Object. More
specifically: specifically:
Association Source: Association Source:
The Association Source is set to an address of the PLR node. The Association Source is set to an address of the PLR node.
Association Type: Association Type:
skipping to change at page 13, line 42 skipping to change at page 13, line 42
The IPv6 address that the PLR sets to identify backup path(s) as The IPv6 address that the PLR sets to identify backup path(s) as
described in Section 6.1.1 of [RFC4090]. This address is described in Section 6.1.1 of [RFC4090]. This address is
applicable to all groups identified by Bypass_Group_Identifier(s) applicable to all groups identified by Bypass_Group_Identifier(s)
carried in the B-SFRR-Active Extended ASSOCIATION ID. carried in the B-SFRR-Active Extended ASSOCIATION ID.
3.3. Signaling Procedures Prior to Failure 3.3. Signaling Procedures Prior to Failure
Before Summary FRR procedures can be used, a handshake MUST be Before Summary FRR procedures can be used, a handshake MUST be
completed between the PLR and MP. This handshake is performed using completed between the PLR and MP. This handshake is performed using
Extended ASSOCIATION object that carries the B-SFRR-Ready Extended the Extended ASSOCIATION object that carries the B-SFRR-Ready
Association ID in both the RSVP Path and Resv messages of the Extended Association ID in both the RSVP Path and Resv messages of
protected LSP. the protected LSP.
When using procedures defined in this document, the PLR MUST ensure When using procedures defined in this document, the PLR MUST ensure
bypass tunnel assignment can satisfy the protected LSP MTU bypass tunnel assignment can satisfy the protected LSP MTU
requirements post FRR. This avoids any packets from being dropped requirements post FRR. This avoids any packets from being dropped
due to exceeding the MTU size of the bypass tunnel after traffic is due to exceeding the MTU size of the bypass tunnel after traffic is
rerouted on the bypass tunnel post failure. rerouted on the bypass tunnel post failure.
3.3.1. PLR Signaling Procedure 3.3.1. PLR Signaling Procedure
The B-SFRR-Ready Extended ASSOCIATION object is added by each PLR in The B-SFRR-Ready Extended ASSOCIATION object is added by each PLR in
the RSVP Path message of the protected LSP to record the bypass the RSVP Path message of the protected LSP to record the bypass
tunnel assignment. This object is updated every time the PLR updates tunnel assignment. This object is updated every time the PLR updates
the bypass tunnel assignment and that triggers an RSVP Path change the bypass tunnel assignment and that triggers an RSVP Path change
message. message.
Upon receiving an RSVP Resv message with B-SFRR-Ready Extended Upon receiving an RSVP Resv message with B-SFRR-Ready Extended
ASSOCIATION object, the PLR node checks if the expected sub-objects ASSOCIATION object, the PLR node checks if the expected sub-objects
from the B-SFRR-Ready ASSOCIATION ID are present. If present, the from the B-SFRR-Ready Extended ASSOCIATION ID are present. If
PLR determines if the MP has acknowledged the current PLR assignment. present, the PLR determines if the MP has acknowledged the current
PLR assignment.
To be a valid acknowledgement, the received B-SFRR-Ready ASSOCIATION To be a valid acknowledgement, the received B-SFRR-Ready Extended
ID contents within the RSVP Resv message of the protected LSP MUST ASSOCIATION ID contents within the RSVP Resv message of the protected
match the latest B-SFRR-Ready Extended ASSOCIATION object and LSP MUST match the latest B-SFRR-Ready Extended ASSOCIATION object
Association ID contents that the PLR node had sent within the RSVP and Association ID contents that the PLR node had sent within the
Path message (with exception of the MESSAGE_ID). RSVP Path message (with exception of the MESSAGE_ID).
Note, when forwarding an RSVP Resv message upstream, the PLR node Note, when forwarding an RSVP Resv message upstream, the PLR node
SHOULD remove any/all B-SFRR-Ready Extended ASSOCIATION objects whose SHOULD remove any/all B-SFRR-Ready Extended ASSOCIATION objects whose
Association Source matches the PLR node address. Association Source matches the PLR node address.
3.3.2. MP Signaling Procedure 3.3.2. MP Signaling Procedure
Upon receiving an RSVP Path message with a B-SFRR-Ready Extended Upon receiving an RSVP Path message with a B-SFRR-Ready Extended
ASSOCIATION object, the MP node processes all (there may be multiple ASSOCIATION object, the MP node processes all (there may be multiple
PLRs for a single MP) B-SFRR-Ready Extended ASSOCIATION objects that PLRs for a single MP) B-SFRR-Ready Extended ASSOCIATION objects that
have the MP node address as Bypass Destination address in the have the MP node address as Bypass Destination address in the
Association ID. Extended Association ID.
The MP node first ensures the existence of the bypass tunnel and that The MP node first ensures the existence of the bypass tunnel and that
the Bypass_Group_Identifier is not already FRR active. That is, an the Bypass_Group_Identifier is not already FRR active. That is, an
LSP cannot join a group that is already FRR rerouted. LSP cannot join a group that is already FRR rerouted.
The MP node builds a mirrored Summary FRR Group database per PLR, The MP node builds a mirrored Summary FRR Group database per PLR,
which is determined using the Bypass_Source_Address field. The which is determined using the Bypass_Source_Address field. The
MESSAGE_ID is extracted and recorded for the protected LSP PATH MESSAGE_ID is extracted and recorded for the protected LSP Path
state. The MP node signals a B-SFRR-Ready Extended Association state. The MP node signals a B-SFRR-Ready Extended Association
object and Association ID in the RSVP Resv message of the protected object and Extended Association ID in the RSVP Resv message of the
LSP. With exception of the MESSAGE_ID objects, all other fields of protected LSP. With exception of the MESSAGE_ID objects, all other
the received B-SFRR-Ready Extended ASSOCIATION object in the RSVP fields of the received B-SFRR-Ready Extended ASSOCIATION object in
Path message are copied into the B-SFRR-Ready Extended ASSOCIATION the RSVP Path message are copied into the B-SFRR-Ready Extended
object to be added in the Resv message. The MESSAGE_ID object is set ASSOCIATION object to be added in the Resv message. The MESSAGE_ID
according to [RFC2961] with the Flags being clear. object is set according to [RFC2961] with the Flags being clear.
Note, an MP may receive more than one RSVP Path message with the B- Note, an MP may receive more than one RSVP Path message with the B-
SFRR-Ready Extended ASSOCIATION object from different upstream PLR SFRR-Ready Extended ASSOCIATION object from different upstream PLR
node(s). In this case, the MP node is expected to save all the node(s). In this case, the MP node is expected to save all the
received MESSAGE_IDs from the different upstream PLR node(s). After received MESSAGE_IDs from the different upstream PLR node(s). After
a failure, the MP node determines and activates the associated a failure, the MP node determines and activates the associated
Summary Refresh ID to use once it receives and processes the RSVP Summary Refresh ID to use once it receives and processes the RSVP
Path message containing B-SFRR-Active Extended ASSOCIATION object Path message containing B-SFRR-Active Extended ASSOCIATION object
that is signaled over the bypass LSP from the PLR, as described that is signaled over the bypass tunnel from the PLR, as described
Section 3.4 Section 3.4
When forwarding an RSVP Path message downstream, the MP SHOULD remove When forwarding an RSVP Path message downstream, the MP SHOULD remove
any/all B-SFRR-Ready Extended ASSOCIATION object(s) whose Association any/all B-SFRR-Ready Extended ASSOCIATION object(s) whose Association
ID contains Bypass_Destination_Address matching the MP node address. ID contains Bypass_Destination_Address matching the MP node address.
3.4. Signaling Procedures Post Failure 3.4. Signaling Procedures Post Failure
Upon detection of the fault (egress link or node failure) the PLR Upon detection of the fault (egress link or node failure) the PLR
first performs the object modification procedures described by first performs the object modification procedures described by
Section 6.4.3 of [RFC4090] for all affected protected LSPs. For Section 6.4.3 of [RFC4090] for all affected protected LSPs. For the
Summary FRR LSPs assigned to the same bypass tunnel a common RSVP_HOP Summary FRR capable LSPs that are assigned to the same bypass tunnel
and SENDER_TEMPLATE MUST be used. a common RSVP_HOP and SENDER_TEMPLATE MUST be used.
The PLR MUST signal non-Summary FRR enabled LSPs over the bypass The PLR MUST signal non-Summary FRR capable LSPs over the bypass
tunnel before signaling the Summary FRR enabled LSPs. This is needed tunnel before signaling the Summary FRR capable LSPs. This is needed
to allow for the case when the PLR node has recently changed a bypass to allow for the case when the PLR node has recently changed a bypass
assignment and the MP has not processed the change yet. assignment and the MP has not processed the change yet.
The B-SFRR-Active Extended ASSOCIATION object is sent within the RSVP The B-SFRR-Active Extended ASSOCIATION object is sent within the RSVP
Path message of the bypass LSP to reroute RSVP state of Summary FRR Path message of the bypass tunnel to reroute RSVP state of Summary
enabled LSPs. FRR capable LSPs.
3.4.1. PLR Signaling Procedure 3.4.1. PLR Signaling Procedure
After a failure event, when using the Summary FRR path signaling After a failure event, when using the Summary FRR path signaling
procedures, an individual RSVP Path message for each Summary FRR LSP procedures, an individual RSVP Path message is not signaled for each
is not signaled. Instead, to reroute Summary FRR LSPs via the bypass Summary FRR LSP. Instead, to reroute Summary FRR LSPs via the bypass
tunnel, the PLR adds the B-SFRR-Active Extended Association object in tunnel, the PLR adds the B-SFRR-Active Extended Association object in
the RSVP Path message of the RSVP session of the bypass tunnel. the RSVP Path message of the RSVP session of the bypass tunnel.
The RSVP_HOP_Object field in the B-SFRR-Active Extended ASSOCIATION The RSVP_HOP_Object field in the B-SFRR-Active Extended ASSOCIATION
ID is set to the common RSVP_HOP that was used by the PLR in ID is set to the common RSVP_HOP that was used by the PLR in
Section 3.4 of this document. Section 3.4 of this document.
The previously received MESSAGE_ID from the MP is activated. As a The previously received MESSAGE_ID from the MP is activated. As a
result, the MP may refresh the protected rerouted RESV state using result, the MP may refresh the protected rerouted Resv state using
Summary Refresh procedures. Summary Refresh procedures.
The PLR adds the Bypass_Group_Identifier(s) of group(s) that have The PLR adds the Bypass_Group_Identifier(s) of group(s) that have
common group attributes, including the tunnel sender address, to the common group attributes, including the tunnel sender address, to the
same B-SFRR-Active Extended ASSOCIATION ID. Note that multiple same B-SFRR-Active Extended ASSOCIATION ID. Note that multiple
ASSOCIATION objects, each carrying a B-SFRR-Active Extended ASSOCIATION objects, each carrying a B-SFRR-Active Extended
ASSOCIATION ID, can be carried within a single RSVP Path message of ASSOCIATION ID, can be carried within a single RSVP Path message of
the bypass LSP and sent towards the MP as described in [RFC6780]. the bypass tunnel and sent towards the MP as described in [RFC6780].
3.4.2. MP Signaling Procedure 3.4.2. MP Signaling Procedure
Upon receiving an RSVP Path message with a B-SFRR-Active Extended Upon receiving an RSVP Path message with a B-SFRR-Active Extended
Association object, the MP performs normal merge point processing for Association object, the MP performs normal merge point processing for
each protected LSP associated with each Bypass_Group_Identifier, as each protected LSP associated with each Bypass_Group_Identifier, as
if it received individual RSVP Path messages for the LSP. if it received an individual RSVP Path messages for that LSP.
For each Summary FRR LSP being merged, the MP first modifies the Path For each Summary FRR capable LSP that is being merged, the MP first
state as follows: modifies the Path state as follows:
1. The RSVP_HOP object is copied from the B-SFRR-Active Extended 1. The RSVP_HOP object is copied from the B-SFRR-Active Extended
ASSOCIATION ID. ASSOCIATION ID.
2. The TIME_VALUES object is copied from the TIMES_VALUE field in 2. The TIME_VALUES object is copied from the TIMES_VALUE field in
the B-SFRR-Active Extended ASSOCIATION ID. The TIME_VALUES the B-SFRR-Active Extended ASSOCIATION ID. The TIME_VALUES
object contains the refresh time of the PLR to generate refreshes object contains the refresh time of the PLR to generate refreshes
and that would have exchanged in a Path message sent to the MP and that would have exchanged in a Path message sent to the MP
after the failure when no SFRR procedures are in effect. after the failure when no Summary FRR procedures are in effect.
3. The tunnel sender address field in the SENDER_TEMPLATE object is 3. The tunnel sender address field in the SENDER_TEMPLATE object is
copied from the tunnel sender address of the B-SFRR-Active copied from the tunnel sender address of the B-SFRR-Active
Extended ASSOCIATION ID. Extended ASSOCIATION ID.
4. The ERO object is modified as per Section 6.4.4 of [RFC4090]. 4. The ERO object is modified as per Section 6.4.4 of [RFC4090].
Once the above modifications are completed, the MP then performs Once the above modifications are completed, the MP node performs
the merge processing as per [RFC4090]. the merge processing as per [RFC4090].
5. The previously received MESSAGE_ID from the PLR is activated, 5. The previously received MESSAGE_ID from the PLR is activated,
meaning that the PLR may now refresh the protected rerouted PATH meaning that the PLR may now refresh the protected rerouted Path
state using Summary Refresh procedures. state using Summary Refresh procedures.
A failure during merge processing of any individual rerouted LSP MUST A failure during merge processing of any individual rerouted LSP MUST
result in an RSVP Path Error message. result in an RSVP Path Error message.
An individual RSVP Resv message for each successfully merged Summary An individual RSVP Resv message for each successfully merged Summary
FRR LSP is not signaled. The MP node SHOULD immediately use Summary FRR LSP is not signaled. The MP node SHOULD immediately use Summary
Refresh procedures to refresh the protected LSP RESV state. Refresh procedures to refresh the protected LSP Resv state.
3.5. Refreshing Summary FRR Active LSPs 3.5. Refreshing Summary FRR Active LSPs
Refreshing of Summary FRR active LSPs is performed using Summary Refreshing of Summary FRR active LSPs is performed using Summary
Refresh as defined by [RFC2961]. Refresh as defined by [RFC2961].
4. Backwards Compatibility 4. Backwards Compatibility
The (Extended) ASSOCIATION object is defined in [RFC4872] with a The (Extended) ASSOCIATION object is defined in [RFC4872] with a
class number in the form 11bbbbbb, which ensures compatibility with class number in the form 11bbbbbb, which ensures compatibility with
 End of changes. 39 change blocks. 
92 lines changed or deleted 96 lines changed or added

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