draft-ietf-mpls-summary-frr-rsvpte-07.txt   draft-ietf-mpls-summary-frr-rsvpte-08.txt 
MPLS Working Group M. Taillon MPLS Working Group M. Taillon
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Updates: RFC4090 (if approved) T. Saad, Ed. Updates: 4090 (if approved) T. Saad, Ed.
Intended status: Standards Track Juniper Networks Intended status: Standards Track Juniper Networks
Expires: June 13, 2020 R. Gandhi Expires: July 15, 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
December 11, 2019 January 12, 2020
RSVP-TE Summary Fast Reroute Extensions for LSP Tunnels RSVP-TE Summary Fast Reroute Extensions for LSP Tunnels
draft-ietf-mpls-summary-frr-rsvpte-07 draft-ietf-mpls-summary-frr-rsvpte-08
Abstract Abstract
This document updates the Resource Reservation Protocol (RSVP) This document updates RFC 4090 for the Resource Reservation Protocol
Traffic-Engineering (TE) procedures that are defined in RFC 4090 for (RSVP) Traffic-Engineering (TE) procedures defined for facility
facility backup protection. The updates include extensions that backup protection. The updates include extensions that reduce the
reduce the amount of signaling and processing that occurs during Fast amount of signaling and processing that occurs during Fast Reroute
Reroute (FRR), and subsequently, improves scalability when undergoing (FRR), and subsequently, improves scalability when undergoing FRR
FRR convergence after a link or node failure. These extensions allow convergence after a link or node failure. These extensions allow the
the RSVP message exchange between the Point of Local Repair (PLR) and RSVP message exchange between the Point of Local Repair (PLR) and the
the Merge Point (MP) to be independent of the number of protected Merge Point (MP) to be independent of the number of protected Label
Label Switched Paths (LSPs) traversing between them when facility Switched Paths (LSPs) traversing between them when facility bypass
bypass FRR protection is used. The signaling extensions are fully FRR protection is used. The signaling extensions are fully backwards
backwards compatible with nodes that do not support them. 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 June 13, 2020. This Internet-Draft will expire on July 15, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2020 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . 4 2. Conventions Used in This Document . . . . . . . . . . . . . . 4
2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 2.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 4 2.2. Acronyms and Abbreviations . . . . . . . . . . . . . . . 4
3. Extensions for Summary FRR Signaling . . . . . . . . . . . . 4 3. Extensions for Summary FRR Signaling . . . . . . . . . . . . 5
3.1. B-SFRR-Ready Extended ASSOCIATION Object . . . . . . . . 6 3.1. B-SFRR-Ready Extended ASSOCIATION Object . . . . . . . . 6
3.1.1. IPv4 B-SFRR-Ready IPv4 Extended ASSOCIATION ID . . . 6 3.1.1. IPv4 B-SFRR-Ready IPv4 Extended ASSOCIATION ID . . . 7
3.1.2. IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID . . . 7 3.1.2. IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID . . . 8
3.2. B-SFRR-Active Extended ASSOCIATION Object . . . . . . . . 10 3.2. B-SFRR-Active Extended ASSOCIATION Object . . . . . . . . 11
3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID . . . . . 11 3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID . . . . . 12
3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID . . . . . 12 3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID . . . . . 13
3.3. Signaling Procedures Prior to Failure . . . . . . . . . . 13 3.3. Signaling Procedures Prior to Failure . . . . . . . . . . 14
3.3.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 14 3.3.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 15
3.3.2. MP Signaling Procedure . . . . . . . . . . . . . . . 14 3.3.2. MP Signaling Procedure . . . . . . . . . . . . . . . 15
3.4. Signaling Procedures Post Failure . . . . . . . . . . . . 15 3.4. Signaling Procedures Post Failure . . . . . . . . . . . . 16
3.4.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 15 3.4.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 16
3.4.2. MP Signaling Procedure . . . . . . . . . . . . . . . 16 3.4.2. MP Signaling Procedure . . . . . . . . . . . . . . . 17
3.5. Refreshing Summary FRR Active LSPs . . . . . . . . . . . 17 3.5. Refreshing Summary FRR Active LSPs . . . . . . . . . . . 18
4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 17 4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 18
5. Security Considerations . . . . . . . . . . . . . . . . . . . 17 5. Security Considerations . . . . . . . . . . . . . . . . . . . 18
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 19
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 18 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.1. Normative References . . . . . . . . . . . . . . . . . . 18 9.1. Normative References . . . . . . . . . . . . . . . . . . 19
9.2. Informative References . . . . . . . . . . . . . . . . . 19 9.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20
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
performed individually for each affected protected LSP. This may performed individually for each affected protected LSP. This may
eventually lead to control plane scalability and latency issues on eventually lead to control plane scalability and latency issues on
the PLR and/or the MP due to limited memory and CPU processing the PLR and/or the Merge Point (MP) due to limited memory and CPU
resources. This condition is exacerbated when the failure affects processing resources. This condition is exacerbated when the failure
large number of protected LSPs that traverse the same PLR and Merge affects a large number of protected LSPs that traverse the same PLR
Point (MP) nodes. and MP nodes.
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 an MP node for a
number of LSPs that ingress on the same link. In the event of the similar number of LSPs that ingress on the same link. In the event
failure of the link or neighbor node, the RSVP-TE control plane of of the failure of the link or neighbor node, the RSVP-TE control
the node when acting as PLR becomes busy rerouting protected LSPs plane of the node when acting as a PLR becomes busy rerouting
signaling over the bypass tunnel(s) in one direction, and when acting protected LSPs signaling over the bypass tunnel(s) in one direction,
as an MP node becomes busy merging RSVP states from signaling and when acting as an MP node becomes busy merging RSVP states from
received over bypass tunnels for LSP(s) in the reverse direction. signaling received over bypass tunnels for LSP(s) in the reverse
Subsequently, the head-end LER(s) that are notified of the local direction. Subsequently, the head-end LER(s) that are notified of
repair at downstream LSR will attempt to (re)converge the affected the local repair at downstream LSR will attempt to (re)converge the
RSVP-TE LSPs onto newly computed paths - possibly traversing the same affected RSVP-TE LSPs onto newly computed paths - possibly traversing
previously affected LSR(s). As a result, the RSVP-TE control plane the same previously affected LSR(s). As a result, the RSVP-TE
at the PLR and MP becomes overwhelmed by the amount of FRR RSVP-TE control plane at the PLR and MP becomes overwhelmed by the amount of
processing overhead following the link or node failure, and due to FRR RSVP-TE processing overhead following the link or node failure,
other control plane protocol(s) (e.g. the IGP) that undergo and due to other control plane protocol(s) (e.g. the IGP) that
convergence on the same node at the same time too. undergo convergence on the same node at the same time too.
The extensions defined in this document update the procedures defined Today, each protected RSVP-TE LSP is signaled individually over the
in [RFC4090] for facility backup protection to enable a MP node to bypass tunnel after FRR. The changes introduced in this document
become aware of the PLR node's bypass tunnel assignment group and allow the PLR to assign multiple protected LSPs to a bypass tunnel
allow the FRR procedures between PLR node and MP node to be signaled group and to communicate this assignment to the MP, such that upon
and processed on groups of protected LSPs. failure, the signaling over the bypass tunnel happens on bypass
tunnel group(s). New extensions are defined in this document to
update the procedures defined in [RFC4090] for facility backup
protection to enable the MP node to become aware of the PLR node's
bypass tunnel assignment group(s) and to allow FRR procedures between
the PLR and the MP nodes to be signaled and processed on per bypass
tunnel group(s).
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 scaling. The
extensions defined in this document allow the MESSAGE_ID information Summary FRR procedures introduced in this document build on those
for the rerouted Path and Resv states to be exchanged between PLR and concepts to allow the MESSAGE_ID(s) to be exchanged on per bypass
MP nodes a priori to the fault such that Summary Refresh procedures tunnel assignment group, and continue use Summary Refresh procedures
can continue to be used to refresh the rerouted state(s) after FRR while reducing the amount of messaging that occurs after rerouting
has occurred. signaling over the bypass tunnel post FRR.
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 4, line 41 skipping to change at page 4, line 43
PLR: Point of Local Repair node as defined in [RFC4090] PLR: Point of Local Repair node as defined in [RFC4090]
FRR: Fast Reroute as defined in [RFC4090] FRR: Fast Reroute as defined in [RFC4090]
B-SFRR-Ready: Bypass Summary FRR Ready Extended ASSOCIATION B-SFRR-Ready: Bypass Summary FRR Ready Extended ASSOCIATION
object. Added by the PLR for each LSP protected by the bypass object. Added by the PLR for each LSP protected by the bypass
tunnel. tunnel.
B-SFRR-Active: Bypass Summary FRR Active Extended ASSOCIATION B-SFRR-Active: Bypass Summary FRR Active Extended ASSOCIATION
object. Used to notify the MP node of one ore more groups of object. Used to notify the MP node that one or more groups of
protected LSP(s) that are being protected by the specified bypass protected LSP(s) have been rerouted over the associated bypass
tunnel are being rerouted. tunnel.
MTU: Maximum transmission unit.
3. Extensions for Summary FRR Signaling 3. Extensions for Summary FRR Signaling
The RSVP ASSOCIATION object is defined in [RFC4872] as a means to The RSVP ASSOCIATION object is defined in [RFC4872] as a means to
associate LSPs with each other. For example, in the context of associate LSPs with each other. For example, in the context of
GMPLS-controlled LSP(s), the object is used to associate recovery GMPLS-controlled LSP(s), the object is used to associate recovery
LSPs with the LSP they are protecting. The Extended ASSOCIATION LSPs with the LSP they are protecting. The Extended ASSOCIATION
object is introduced in [RFC6780] to expand on the possible usage of object is introduced in [RFC6780] to expand on the possible usage of
the ASSOCIATION object and generalize the definition of the Extended the ASSOCIATION object and generalize the definition of the Extended
Association ID field. Association ID field.
This document defines the use of the Extended ASSOCIATION object to This document defines the use of the Extended ASSOCIATION object to
carry the Summary FRR information and associate the protected LSP(s) carry the Summary FRR information and associate the protected LSP(s)
with the bypass tunnel that protects them. Two new Association Types with the bypass tunnel that protects them. Two new Association Types
for the Extended ASSOCIATION object, and new Extended Association IDs for the Extended ASSOCIATION object, and new Extended Association IDs
are proposed in this draft to describe the Bypass Summary FRR Ready are proposed in this document to describe the Bypass Summary FRR
(B-SFRR-Ready) and the Bypass Summary FRR Active (B-SFRR-Active) Ready (B-SFRR-Ready) and the Bypass Summary FRR Active (B-SFRR-
associations. Active) associations.
The PLR creates and manages the Summary FRR LSP groups (identified by The PLR creates and manages the Summary FRR LSP groups (identified by
Bypass_Group_Identifiers) and shares the group identifier(s) with the Bypass_Group_Identifiers) and shares the group identifier(s) with the
MP via signaling. MP via signaling.
The PLR SHOULD assign the same Bypass_Group_Identifier to all The PLR SHOULD assign the same Bypass_Group_Identifier to all
protected LSPs that egress the same protected interface and are
protected by the same bypass tunnel. This minimizes the number of
bypass tunnel SFRR groups, and optimizes the amount of signaling
needed between the PLR and the MP after FRR.
The PLR MUST ensure all protected LSP(s) that are assigned the same
Bypass_Group_Identifier use the same modified tunnel sender address
for the backup path identification after FRR as described in
[RFC4090].
The PLR SHOULD assign the same Bypass_Group_Identifier to all
protected LSPs that share the egress link, and bypass tunnel as long protected LSPs that share the egress link, and bypass tunnel as long
as the protected LSP(s) have the common group attributes, including as the protected LSP(s) have the common group attributes, including
the modified tunnel sender address used for backup path the modified tunnel sender address used for backup path
identification as described in [RFC4090]. identification as described in [RFC4090].
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 an Extended
ASSOCIATION object with Type B-SFRR-Ready and respective Extended ASSOCIATION object with B-SFRR-Ready Extended Association ID in the
Association ID in the RSVP Path message of the protected LSP to RSVP Path message of the protected LSP. The PLR adds the protected
inform the MP of the PLR's assigned bypass tunnel, Summary FRR LSP Bypass_Group_Identifier, information from the assigned bypass
Bypass_Group_Identifier, and the MESSAGE_ID that the PLR will use to tunnel, and MESSAGE_ID object into the B-SFRR-Ready Extended
refresh the protected LSP Path state after FRR occurs. Association ID. The MP uses the information contained in the
received B-SFRR-Ready Extended Association ID to refresh and merge
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 the PLR after
FRR procedures on the PLR. The B-SFRR-Active Extended ASSOCIATION activating FRR procedures on the PLR. The B-SFRR-Active Extended
object and Extended Association ID are sent within the RSVP Path ASSOCIATION object and Extended Association ID are sent within the
message of the bypass tunnel to inform the MP node that one or more RSVP Path message of the bypass tunnel to inform the MP node that one
groups of protected LSPs protected by the bypass tunnel are now being or more groups of protected LSPs protected by the bypass tunnel are
rerouted over the bypass tunnel. now being 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 tunnel 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:
skipping to change at page 9, line 32 skipping to change at page 10, line 32
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, 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 MUST generate
generates a MESSAGE_ID object (flags SHOULD be clear, Epoch and a MESSAGE_ID object with Epoch and Message_Identifier set according
Message_Identifier MUST be set according to [RFC2961]). to [RFC2961]. The MESSAGE_ID object flags SHOULD be cleared when
transmitted by the PLR and ignored when received at the MP.
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 Extended adding a B-SFRR-Ready Extended ASSOCIATION object and Extended
Association ID in the RSVP Path message for the protected LSP using Association ID in the RSVP Path message for the protected LSP using
procedures described in Section 3.4. procedures described in Section 3.3.
The MP node acknowledges the assignment to the PLR node by signaling The MP node acknowledges the assignment to the PLR node by signaling
the B-SFRR-Ready Extended ASSOCIATION object and Extended Association the B-SFRR-Ready Extended ASSOCIATION object and Extended Association
ID within the RSVP Resv message of the protected LSP. With exception ID within the RSVP Resv message of the protected LSP. With the
of the MESSAGE_ID objects, all other fields of the received in the B- exception of the MESSAGE_ID objects, all other fields of the received
SFRR-Ready Extended ASSOCIATION ID in the RSVP Path message are in the B-SFRR-Ready Extended ASSOCIATION ID in the RSVP Path message
copied into the B-SFRR-Ready Extended ASSOCIATION ID to be added in are copied into the B-SFRR-Ready Extended ASSOCIATION ID to be added
the Resv message. The MESSAGE_ID object is set according to in the Resv message. The MESSAGE_ID object is set according to
[RFC2961] with the Flags being clear. A new Message_Identifier MUST [RFC2961] with the Flags being clear. A new Message_Identifier MUST
be used to acknowledge an updated PLR assignment. 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 match the fields received in the RSVP
message (with exception of the MESSAGE_ID) match. If it does not Resv message (with exception of the MESSAGE_ID). If the fields do
match, or if B-SFRR-Ready Extended ASSOCIATION object is absent in a not match, or if B-SFRR-Ready Extended ASSOCIATION object is absent
subsequent refresh, the PLR node MUST consider the protected LSP as in a subsequent refresh, the PLR node MUST consider the protected LSP
not Summary FRR capable. as 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 Summary FRR protected LSPs destination) that one or more groups of Summary FRR protected LSPs
that are being protected by the bypass tunnel are being rerouted over that are being protected by the bypass tunnel are being rerouted over
the 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
skipping to change at page 11, line 45 skipping to change at page 12, line 45
Number of Bypass_Group_Identifier fields. Number of Bypass_Group_Identifier fields.
Reserved: 16 bits Reserved: 16 bits
Reserved for future use. Reserved for future use.
Bypass_Group_Identifier: 32 bits Bypass_Group_Identifier: 32 bits
The Bypass_Group_Identifier that is previously signaled by the PLR The Bypass_Group_Identifier that is previously signaled by the PLR
using the Extended Association object. One or more using the Extended Association object. One or more
Bypass_Group_Identifiers may be included. Bypass_Group_Identifiers MAY be included.
RSVP_HOP_Object: Class 3, as defined by [RFC2205] RSVP_HOP_Object: Class 3, as defined by [RFC2205]
Replacement RSVP HOP object to be applied to all LSPs associated Replacement RSVP HOP object to be applied to all LSPs associated
with each of the following Bypass_Group_Identifiers. This with each of the following Bypass_Group_Identifiers. This
corresponds to C-Type = 1 for IPv4 RSVP HOP. corresponds to C-Type = 1 for IPv4 RSVP HOP.
TIME_VALUES object: Class 5, as defined by [RFC2205] TIME_VALUES object: Class 5, as defined by [RFC2205]
Replacement TIME_VALUES object to be applied to all LSPs Replacement TIME_VALUES object to be applied to all LSPs
skipping to change at page 13, line 46 skipping to change at page 14, line 46
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
the Extended ASSOCIATION object that carries the B-SFRR-Ready the Extended ASSOCIATION object that carries the B-SFRR-Ready
Extended Association ID in both the RSVP Path and Resv messages of Extended Association ID in both the RSVP Path and Resv messages of
the protected LSP. the protected LSP.
The facility backup method introduced in [RFC4090] takes advantage of
MPLS label stacking (PLR imposing additional MPLS label post FRR) to
allow rerouting of protected traffic over backup path. The backup
path may have stricter MTU requirement and due to label stacking at
PLR, the protected traffic may exceed the backup path MTU. The
operator is assumed to engineer their network to allow rerouting of
protected traffic and the additional label stacking at PLR to not
exceed the backup path MTU.
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 the 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 backup path after traffic is
rerouted on the bypass tunnel post failure. rerouted on to the bypass tunnel post the 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
skipping to change at page 14, line 46 skipping to change at page 16, line 6
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 Extended Association ID in the RSVP Resv message of the object and Extended Association ID in the RSVP Resv message of the
protected LSP. With exception of the MESSAGE_ID objects, all other protected LSP. With the exception of the MESSAGE_ID objects, all
fields of the received B-SFRR-Ready Extended ASSOCIATION object in other fields of the received B-SFRR-Ready Extended ASSOCIATION object
the RSVP Path message are copied into the B-SFRR-Ready Extended in the RSVP Path message are copied into the B-SFRR-Ready Extended
ASSOCIATION object to be added in the Resv message. The MESSAGE_ID ASSOCIATION object to be added in the Resv message. The MESSAGE_ID
object is set 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
skipping to change at page 15, line 29 skipping to change at page 16, line 36
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 the Section 6.4.3 of [RFC4090] for all affected protected LSPs. For the
Summary FRR capable LSPs that are assigned to the same bypass tunnel Summary FRR capable LSPs that are assigned to the same bypass tunnel
a common RSVP_HOP and SENDER_TEMPLATE MUST be used. a common RSVP_HOP and SENDER_TEMPLATE MUST be used.
The PLR MUST signal non-Summary FRR capable LSPs over the bypass The PLR MUST signal non-Summary FRR capable LSPs over the bypass
tunnel before signaling the Summary FRR capable 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 where the PLR node 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 tunnel to reroute RSVP state of Summary Path message of the bypass tunnel to reroute RSVP state of Summary
FRR capable 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 is not signaled for each procedures, an individual RSVP Path message is not signaled for each
Summary FRR LSP. 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.3 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
skipping to change at page 17, line 22 skipping to change at page 18, line 26
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
non-supporting node(s). Such nodes will ignore the object and non-supporting node(s). Such nodes will ignore the object and
forward it without modification. forward it without modification.
5. Security Considerations 5. Security Considerations
This document updates an existing RSVP object. Thus, in the event of This document updates an existing RSVP object. Thus, in the event of
the interception of a signaling message, slightly more information the interception of a signaling message, slightly more information
could be deduced about the state of the network than was previously could be deduced about the state of the network than was previously
the case. Existing mechanisms for maintaining the integrity and the case.
authenticity of RSVP protocol messages [RFC2747] can be applied.
Other considerations mentioned in [RFC4090] and [RFC5920] also apply. When using procedures defined in this document, FRR (or the reroute
of protected LSP(s) on to the bypass tunnel) can be activated on per
group of protected LSP(s). This allows an intruder to potentially
impact and manipulate a set of protected LSP that are assigned to the
same bypass tunnel group.
Existing mechanisms for maintaining the integrity and authenticity of
RSVP protocol messages [RFC2747] can be applied. Other
considerations mentioned in [RFC4090] and [RFC5920] also apply.
6. IANA Considerations 6. IANA Considerations
IANA maintains the "Generalized Multi-Protocol Label Switching IANA maintains the "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Parameters" registry. The "Association Type" sub- (GMPLS) Signaling Parameters" registry. The "Association Type" sub-
registry is included in this registry. registry is included in this registry.
This registry has been updated by new Association Type for Extended This registry has been updated by new Association Type for Extended
ASSOCIATION Object defined in this document as follows: ASSOCIATION Object defined in this document as follows:
 End of changes. 31 change blocks. 
114 lines changed or deleted 153 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/