draft-ietf-mpls-summary-frr-rsvpte-08.txt   draft-ietf-mpls-summary-frr-rsvpte-09.txt 
MPLS Working Group M. Taillon MPLS Working Group M. Taillon
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Updates: 4090 (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: July 15, 2020 R. Gandhi Expires: August 29, 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
January 12, 2020 February 26, 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-08 draft-ietf-mpls-summary-frr-rsvpte-09
Abstract Abstract
This document updates RFC 4090 for the Resource Reservation Protocol This document updates RFC 4090 for the Resource Reservation Protocol
(RSVP) Traffic-Engineering (TE) procedures defined for facility (RSVP) Traffic-Engineering (TE) procedures defined for facility
backup protection. The updates include extensions that reduce the backup protection. The updates include extensions that reduce the
amount of signaling and processing that occurs during Fast Reroute amount of signaling and processing that occurs during Fast Reroute
(FRR), and subsequently, improves scalability when undergoing FRR (FRR), and subsequently, improves scalability when undergoing FRR
convergence after a link or node failure. These extensions allow the convergence after a link or node failure. These extensions allow the
RSVP message exchange between the Point of Local Repair (PLR) and the RSVP message exchange between the Point of Local Repair (PLR) and the
Merge Point (MP) to be independent of the number of protected Label Merge Point (MP) nodes to be independent of the number of protected
Switched Paths (LSPs) traversing between them when facility bypass Label Switched Paths (LSPs) traversing between them when facility
FRR protection is used. The signaling extensions are fully backwards bypass FRR protection is used. The signaling extensions are fully
compatible with nodes that do not support them. 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 July 15, 2020. This Internet-Draft will expire on August 29, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 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
skipping to change at page 2, line 28 skipping to change at page 2, line 28
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 . . . . . . . . . . . . 5 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 . . . 7 3.1.1. IPv4 B-SFRR-Ready Extended ASSOCIATION ID . . . . . . 7
3.1.2. IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID . . . 8 3.1.2. IPv6 B-SFRR-Ready Extended ASSOCIATION ID . . . . . . 8
3.2. B-SFRR-Active Extended ASSOCIATION Object . . . . . . . . 11 3.1.3. Processing Rules for B-SFRR-Ready Extended
3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID . . . . . 12 ASSOCIATION Object . . . . . . . . . . . . . . . . . 9
3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID . . . . . 13 3.2. B-SFRR-Active Extended ASSOCIATION Object . . . . . . . . 10
3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID . . . . . 11
3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID . . . . . 12
3.3. Signaling Procedures Prior to Failure . . . . . . . . . . 14 3.3. Signaling Procedures Prior to Failure . . . . . . . . . . 14
3.3.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 15 3.3.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 15
3.3.2. MP Signaling Procedure . . . . . . . . . . . . . . . 15 3.3.2. MP Signaling Procedure . . . . . . . . . . . . . . . 15
3.4. Signaling Procedures Post Failure . . . . . . . . . . . . 16 3.4. Signaling Procedures Post Failure . . . . . . . . . . . . 16
3.4.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 16 3.4.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 16
3.4.2. MP Signaling Procedure . . . . . . . . . . . . . . . 17 3.4.2. MP Signaling Procedure . . . . . . . . . . . . . . . 17
3.5. Refreshing Summary FRR Active LSPs . . . . . . . . . . . 18 3.5. Refreshing Summary FRR Active LSPs . . . . . . . . . . . 18
4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 18 4. Backwards Compatibility . . . . . . . . . . . . . . . . . . . 18
5. Security Considerations . . . . . . . . . . . . . . . . . . . 18 5. Security Considerations . . . . . . . . . . . . . . . . . . . 18
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
skipping to change at page 3, line 9 skipping to change at page 3, line 9
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 19
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 19
9.1. Normative References . . . . . . . . . . . . . . . . . . 19 9.1. Normative References . . . . . . . . . . . . . . . . . . 19
9.2. Informative References . . . . . . . . . . . . . . . . . 20 9.2. Informative References . . . . . . . . . . . . . . . . . 20
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 20 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 Label Switched Path (LSP) onto the
event of a TE link or node failure. Such signaling procedures are bypass tunnel in the event of a TE link or node failure. Such
performed individually for each affected protected LSP. This may signaling procedures are performed individually for each affected
eventually lead to control plane scalability and latency issues on protected LSP. This may eventually lead to control plane scalability
the PLR and/or the Merge Point (MP) due to limited memory and CPU and latency issues on the PLR and/or the Merge Point (MP) nodes due
processing resources. This condition is exacerbated when the failure to limited memory and CPU processing resources. This condition is
affects a large number of protected LSPs that traverse the same PLR exacerbated when the failure affects a large number of protected LSPs
and MP nodes. that traverse the same PLR 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 Label
acting as a PLR node may host tens of thousands of protected RSVP-TE Switched Router (LSR) acting as a PLR node may host tens of thousands
LSPs egressing the same link, and also act as an MP node for a of protected RSVP-TE LSPs egressing the same protected link, and also
similar number of LSPs that ingress on the same link. In the event act as an MP node for a similar number of LSPs that ingress on the
of the failure of the link or neighbor node, the RSVP-TE control same link. In the event of the failure of the link or neighbor node,
plane of the node when acting as a PLR becomes busy rerouting the RSVP-TE control plane of the node (when acting as a PLR node)
protected LSPs signaling over the bypass tunnel(s) in one direction, becomes busy rerouting protected LSPs over the bypass tunnel(s) in
and when acting as an MP node becomes busy merging RSVP states from one direction, and (when acting as an MP node) becomes busy merging
signaling received over bypass tunnels for LSP(s) in the reverse RSVP states from signaling received over bypass tunnels for LSP(s) in
direction. Subsequently, the head-end LER(s) that are notified of the reverse direction. Subsequently, the head-end Label Edge Routers
the local repair at downstream LSR will attempt to (re)converge the (LERs) that are notified of the local repair at downstream LSR will
affected RSVP-TE LSPs onto newly computed paths - possibly traversing attempt to (re)converge the affected RSVP-TE LSPs onto newly computed
the same previously affected LSR(s). As a result, the RSVP-TE paths - possibly traversing the same previously affected LSR(s). As
control plane at the PLR and MP becomes overwhelmed by the amount of a result, the RSVP-TE control plane becomes overwhelmed by the amount
FRR RSVP-TE processing overhead following the link or node failure, of FRR RSVP-TE processing overhead following the link or node
and due to other control plane protocol(s) (e.g. the IGP) that failure, and due to other control plane protocol(s) (e.g. the IGP)
undergo convergence on the same node at the same time too. that undergo convergence on the same node at the same time too.
Today, each protected RSVP-TE LSP is signaled individually over the Today, each protected RSVP-TE LSP is signaled individually over the
bypass tunnel after FRR. The changes introduced in this document bypass tunnel after FRR. The changes introduced in this document
allow the PLR to assign multiple protected LSPs to a bypass tunnel allow the PLR node to assign multiple protected LSPs to a bypass
group and to communicate this assignment to the MP, such that upon tunnel group and to communicate this assignment to the MP, such that
failure, the signaling over the bypass tunnel happens on bypass upon failure, the signaling over the bypass tunnel happens on bypass
tunnel group(s). New extensions are defined in this document to tunnel group(s). New extensions are defined in this document to
update the procedures defined in [RFC4090] for facility backup update the procedures defined in [RFC4090] for facility backup
protection to enable the MP node to become aware of the PLR node's 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 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 the PLR and the MP nodes to be signaled and processed on per bypass
tunnel group(s). 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 scaling. The refresh the RSVP Path and Resv states to help with scaling. The
Summary FRR procedures introduced in this document build on those Summary FRR procedures introduced in this document build on those
skipping to change at page 4, line 39 skipping to change at page 4, line 39
LSP: Label Switched Path LSP: Label Switched Path
MP: Merge Point node as defined in [RFC4090] MP: Merge Point node as defined in [RFC4090]
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 node for each LSP protected by the
tunnel. bypass 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 that one or more groups of object. Used to notify the MP node that one or more groups of
protected LSP(s) have been rerouted over the associated bypass protected LSP(s) have been rerouted over the associated bypass
tunnel. tunnel.
MTU: Maximum transmission unit. 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 ASSOCIATION object is used to associate
LSPs with the LSP they are protecting. The Extended ASSOCIATION a recovery LSP with the LSP(s) it is protecting. The Extended
object is introduced in [RFC6780] to expand on the possible usage of ASSOCIATION object is introduced in [RFC6780] to expand on the
the ASSOCIATION object and generalize the definition of the Extended possible usage of the ASSOCIATION object and generalize the
Association ID field. definition of the Extended 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 document to describe the Bypass Summary FRR are proposed in this document to describe the Bypass Summary FRR
Ready (B-SFRR-Ready) and the Bypass Summary FRR Active (B-SFRR- Ready (B-SFRR-Ready) and the Bypass Summary FRR Active (B-SFRR-
Active) associations. Active) associations.
The PLR creates and manages the Summary FRR LSP groups (identified by The PLR node creates and manages the Summary FRR LSP groups
Bypass_Group_Identifiers) and shares the group identifier(s) with the (identified by Bypass_Group_Identifiers) and shares the group
MP via signaling. identifier(s) with the MP via signaling.
The PLR SHOULD assign the same Bypass_Group_Identifier to all A PLR node SHOULD assign the same Bypass_Group_Identifier to all
protected LSPs that egress the same protected interface and are protected LSPs provided that the protected LSPs:
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 o share the same outgoing protected interface,
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 o are protected by the same bypass tunnel, and
protected LSPs that share the egress link, and bypass tunnel as long
as the protected LSP(s) have the common group attributes, including
the modified tunnel sender address used for backup path
identification as described in [RFC4090].
The MP maintains the PLR group assignments learned via signaling, and o are assigned the same tunnel sender address that is used for
acknowledges the group assignments via signaling. Once the PLR backup path identification after FRR as described in [RFC4090].
receives the acknowledgment, FRR signaling can proceed as group
based.
The PLR node that supports Summary FRR procedures adds an Extended This minimizes the number of bypass tunnel SFRR groups, and optimizes
the amount of signaling that occurs between the PLR and the MP nodes
after FRR.
A PLR node that supports Summary FRR procedures adds an Extended
ASSOCIATION object with B-SFRR-Ready Extended Association ID in the ASSOCIATION object with B-SFRR-Ready Extended Association ID in the
RSVP Path message of the protected LSP. The PLR adds the protected RSVP Path message of the protected LSP. The PLR node adds the
LSP Bypass_Group_Identifier, information from the assigned bypass protected LSP Bypass_Group_Identifier, information from the assigned
tunnel, and MESSAGE_ID object into the B-SFRR-Ready Extended bypass tunnel, and MESSAGE_ID object into the B-SFRR-Ready Extended
Association ID. The MP uses the information contained in the Association ID. The MP uses the information contained in the
received B-SFRR-Ready Extended Association ID to refresh and merge received B-SFRR-Ready Extended Association ID to refresh and merge
the protected LSP Path state after FRR occurs. the protected LSP Path state after FRR occurs.
The MP node that supports Summary FRR procedures adds the B-SFRR- An MP node that supports Summary FRR procedures adds the B-SFRR-Ready
Ready Extended ASSOCIATION object and respective Extended Association Extended ASSOCIATION object and respective Extended Association ID in
ID in the RSVP Resv message of the protected LSP to acknowledge the the RSVP Resv message of the protected LSP to acknowledge the PLR's
PLR's bypass tunnel assignment, and provide the MESSAGE_ID object bypass tunnel assignment, and provide the MESSAGE_ID object that the
that the MP node will use to refresh the protected LSP Resv state MP node will use to refresh the protected LSP Resv state after FRR
after FRR occurs. occurs.
This document also defines a new Association Type for the Extended The MP maintains the PLR node group assignments learned from
ASSOCIATION object and new Extended Association ID to describe the B- signaling, and acknowledges the group assignments to the PLR node via
SFRR-Active association. The B-SFRR-Active Extended ASSOCIATION signaling. Once the PLR node receives the group assignment
object and Extended Association ID are sent by the PLR after acknowledgment from the MP, the FRR signaling can proceed based on
activating FRR procedures on the PLR. The B-SFRR-Active Extended Summary FRR procedures as described in this document.
ASSOCIATION object and Extended Association ID are sent within the
RSVP Path message of the bypass tunnel to inform the MP node that one The B-SFRR-Active Extended ASSOCIATION object with Extended
or more groups of protected LSPs protected by the bypass tunnel are Association ID is sent by the PLR node after activating the Summary
now being rerouted over the bypass tunnel. FRR procedures. The B-SFRR-Active Extended ASSOCIATION object with
Extended Association ID is sent within the RSVP Path 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 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 6, line 48 skipping to change at page 6, line 44
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:
A new Association Type is defined for B-SFRR-Ready as follows: A new Association Type is defined for B-SFRR-Ready as follows:
Value Type Value Type
------- ------ ------- ------
(TBD-1) Bypass Summary FRR Ready Association (B-SFRR-Ready) (TBD-1) Bypass Summary FRR Ready Association (B-SFRR-Ready)
Extended ASSOCIATION ID for B-SFRR-Ready: The Extended ASSOCIATION object's Global Association Source MUST be
set according to the rules defined in [RFC6780].
The B-SFRR-Ready Extended ASSOCIATION ID is The B-SFRR-Ready Extended ASSOCIATION ID is populated by the PLR node
populated by the PLR for the Bypass Summary FRR Ready association. when performing Bypass Summary FRR Ready association for a protected
The rules to populate the Extended ASSOCIATION ID in this case are LSP. The rules governing its population are described in the
described below. subsequent sections.
3.1.1. IPv4 B-SFRR-Ready IPv4 Extended ASSOCIATION ID 3.1.1. IPv4 B-SFRR-Ready Extended ASSOCIATION ID
The IPv4 Extended ASSOCIATION ID for the B-SFRR-Ready association The IPv4 Extended ASSOCIATION ID for the B-SFRR-Ready association
type has the following format: type is carried inside the IPv4 Extended ASSOCIATION object and has
the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bypass_Tunnel_ID | Reserved | | Bypass_Tunnel_ID | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bypass_Source_IPv4_Address | | Bypass_Source_IPv4_Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bypass_Destination_IPv4_Address | | Bypass_Destination_IPv4_Address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 8, line 11 skipping to change at page 7, line 33
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1: The IPv4 Extended ASSOCIATION ID for B-SFRR-Ready Figure 1: The IPv4 Extended ASSOCIATION ID for B-SFRR-Ready
Bypass_Tunnel_ID: 16 bits Bypass_Tunnel_ID: 16 bits
The bypass tunnel identifier. The bypass tunnel identifier.
Reserved: 16 bits Reserved: 16 bits
Reserved for future use. Reserved for future use. MUST be set to zero when sending
and ignored on receipt.
Bypass_Source_IPv4_Address: 32 bits Bypass_Source_IPv4_Address: 32 bits
The bypass tunnel source IPV4 address. The bypass tunnel source IPV4 address.
Bypass_Destination_IPv4_Address: 32 bits Bypass_Destination_IPv4_Address: 32 bits
The bypass tunnel destination IPV4 address. The bypass tunnel destination IPV4 address.
Bypass_Group_Identifier: 32 bits Bypass_Group_Identifier: 32 bits
The bypass tunnel group identifier. The bypass tunnel group identifier that is assigned to the
LSP.
MESSAGE_ID MESSAGE_ID
A MESSAGE_ID object as defined by [RFC2961]. A MESSAGE_ID object as defined by [RFC2961].
3.1.2. IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID 3.1.2. IPv6 B-SFRR-Ready Extended ASSOCIATION ID
The IPv6 Extended ASSOCIATION ID field for the B-SFRR-Ready The IPv6 Extended ASSOCIATION ID for the B-SFRR-Ready association
association type has the following format: type is carried inside the IPv6 Extended ASSOCIATION object and has
the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bypass_Tunnel_ID | Reserved | | Bypass_Tunnel_ID | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ + + +
| | | |
+ Bypass_Source_IPv6_Address + + Bypass_Source_IPv6_Address +
skipping to change at page 10, line 11 skipping to change at page 9, line 11
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: The IPv6 Extended ASSOCIATION ID for B-SFRR-Ready Figure 2: The IPv6 Extended ASSOCIATION ID for B-SFRR-Ready
Bypass_Tunnel_ID: 16 bits Bypass_Tunnel_ID: 16 bits
The bypass tunnel identifier. The bypass tunnel identifier.
Reserved: 16 bits Reserved: 16 bits
Reserved for future use. Reserved for future use. MUST be set to zero when sending
and ignored on receipt.
Bypass_Source_IPv6_Address: 128 bits Bypass_Source_IPv6_Address: 128 bits
The bypass tunnel source IPV6 address. The bypass tunnel source IPV6 address.
Bypass_Destination_IPv6_Address: 128 bits Bypass_Destination_IPv6_Address: 128 bits
The bypass tunnel destination IPV6 address. The bypass tunnel destination IPV6 address.
Bypass_Group_Identifier: 32 bits Bypass_Group_Identifier: 32 bits
The bypass tunnel group identifier. The bypass tunnel group identifier that is assigned to the
LSP.
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 3.1.3. Processing Rules for B-SFRR-Ready Extended ASSOCIATION Object
protected LSP. The same Bypass_Group_Identifier is used for the set
of protected LSPs that share the same bypass tunnel, traverse the
same egress link and are not already rerouted. The PLR MUST generate
a MESSAGE_ID object with Epoch and Message_Identifier set according
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 A PLR node assigns a bypass tunnel and Bypass_Group_Identifier for
of the B-SFRR-Ready Extended ASSOCIATION ID changes (e.g. when PLR each protected LSP. The same Bypass_Group_Identifier is used for the
node changes the bypass tunnel assignment). set of protected LSPs that share the same bypass tunnel, traverse the
same egress link and are not already rerouted. The PLR node MUST
generate a MESSAGE_ID object with Epoch and Message_Identifier set
according to [RFC2961]. The MESSAGE_ID object flags MUST be cleared
when transmitted by the PLR node and ignored when received at the MP
node.
The PLR node notifies the MP node of the bypass tunnel assignment via A PLR node MUST generate a new Message_Identifier each time the
contents of the B-SFRR-Ready Extended ASSOCIATION ID changes (e.g.
when the PLR node changes the bypass tunnel assignment).
A 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.3. procedures described in Section 3.3.
The MP node acknowledges the assignment to the PLR node by signaling An 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 the ID within the RSVP Resv message of the protected LSP. With the
exception of the MESSAGE_ID objects, all other fields of the received exception of the MESSAGE_ID objects, all other fields of the received
in the B-SFRR-Ready Extended ASSOCIATION ID in the RSVP Path message in the B-SFRR-Ready Extended ASSOCIATION ID in the RSVP Path message
are copied into the B-SFRR-Ready Extended ASSOCIATION ID to be added are copied into the B-SFRR-Ready Extended ASSOCIATION ID to be added
in the Resv message. The MESSAGE_ID object is set according to in the Resv message. The MESSAGE_ID object is set according to
[RFC2961]. The MESSAGE_ID object flags MUST be cleared when
transmitted by the MP node and ignored when received at the PLR node.
A new Message_Identifier MUST be used to acknowledge an updated PLR
node's assignment.
[RFC2961] with the Flags being clear. A new Message_Identifier MUST A PLR node considers the protected LSP as Summary FRR capable only if
be used to acknowledge an updated PLR assignment.
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 match the fields received in the RSVP sent in the RSVP Path message match the fields received in the RSVP
Resv message (with exception of the MESSAGE_ID). If the fields do Resv message (with exception of the MESSAGE_ID). If the fields do
not match, or if B-SFRR-Ready Extended ASSOCIATION object is absent not match, or if B-SFRR-Ready Extended ASSOCIATION object is absent
in a subsequent refresh, the PLR node MUST consider the protected LSP in a subsequent refresh, the PLR node MUST consider the protected LSP
as not Summary FRR capable. as not Summary FRR capable.
A race condition may arise for a previously Summary FRR capable
protected LSP when the MP node triggers a refresh that does not
contain the B-SFRR-Ready Extended ASSOCIATION object, while at the
same time, the PLR triggers Summary FRR procedures due to a fault
occurring concurrently. In this case, it is possible that the PLR
triggers Summary FRR procedurees on the protected LSP before it can
receive and process the refresh from the MP node. As a result, the
MP will receive a Srefresh with a Message_Identifier that is not
associated with any state. As per [RFC2961], this results in the MP
generating an Srefresh NACK for this Message_Identifier and sending
it back to the PLR. The PLR processes the Srefresh NACK and replays
the full Path state associated with the Message_Identifier, and
subsequently recovering from this condition.
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
Path message of the bypass tunnel and signaled downstream towards the Path message of the bypass tunnel and signaled downstream towards the
skipping to change at page 11, line 47 skipping to change at page 11, line 20
A new Association Type is defined for B-SFRR-Active as follows: A new Association Type is defined for B-SFRR-Active as follows:
Value Type Value Type
------- ------ ------- ------
(TBD-2) Bypass Summary FRR Active Association (B-SFRR-Active) (TBD-2) Bypass Summary FRR Active Association (B-SFRR-Active)
Extended ASSOCIATION ID for B-SFRR-Active: Extended ASSOCIATION ID for B-SFRR-Active:
The B-SFRR-Active Extended ASSOCIATION ID is The B-SFRR-Active Extended ASSOCIATION ID is
populated by the PLR for the Bypass Summary FRR Active association. populated by the PLR node for the Bypass Summary FRR Active
The rules to populate the Extended ASSOCIATION ID in this case are association. The rules to populate the Extended ASSOCIATION ID
described below. in this case are described below.
3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID 3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID
The IPv4 Extended ASSOCIATION ID for the B-SFRR-Active association The IPv4 Extended ASSOCIATION ID for the B-SFRR-Active association
type is carried inside the IPv4 Extended ASSOCIATION object and has type is carried inside the IPv4 Extended ASSOCIATION object and has
the following format: the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 12, line 41 skipping to change at page 12, line 13
Figure 3: The IPv4 Extended ASSOCIATION ID for B-SFRR-Active Figure 3: The IPv4 Extended ASSOCIATION ID for B-SFRR-Active
Num-BGIDs: 16 bits Num-BGIDs: 16 bits
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 each
The Bypass_Group_Identifier that is previously signaled by the PLR A Bypass_Group_Identifier that was previously signaled by the PLR
using the Extended Association object. One or more using the Extended ASSOCIATION object in the B-SFRR-Ready Extended
Bypass_Group_Identifiers MAY be included. Association ID. One or more 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
associated with each of the following Bypass_Group_Identifiers associated with each of the preceding Bypass_Group_Identifiers
after receiving the B-SFRR-Active Extended ASSOCIATION Object. after receiving the B-SFRR-Active Extended ASSOCIATION Object.
IPv4 tunnel sender address: IPv4 tunnel sender address:
The IPv4 address that the PLR sets to identify backup path(s) as The IPv4 address that the PLR node sets to identify backup path(s)
described in Section 6.1.1 of [RFC4090]. This address is as 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.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID 3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID
The IPv6 Extended ASSOCIATION ID for the B-SFRR-Active association The IPv6 Extended ASSOCIATION ID for the B-SFRR-Active association
type is carried inside the IPv6 Extended ASSOCIATION object and has type is carried inside the IPv6 Extended ASSOCIATION object and has
the following format: the following format:
0 1 2 3 0 1 2 3
skipping to change at page 14, line 13 skipping to change at page 13, line 41
Figure 4: The IPv6 Extended ASSOCIATION ID for B-SFRR-Active Figure 4: The IPv6 Extended ASSOCIATION ID for B-SFRR-Active
Num-BGIDs: 16 bits Num-BGIDs: 16 bits
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 each
The Bypass_Group_Identifier that is previously signaled by the PLR A Bypass_Group_Identifier that was previously signaled by the PLR
using the Extended Association object. One or more using the Extended ASSOCIATION object in the B-SFRR-Ready Extended
Bypass_Group_Identifiers may be included. Association ID. One or more 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 = 2 for IPv6 RSVP HOP. corresponds to C-Type = 2 for IPv6 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
associated with each of the following Bypass_Group_Identifiers associated with each of the following Bypass_Group_Identifiers
after receiving the B-SFRR-Active Extended ASSOCIATION Object. after receiving the B-SFRR-Active Extended ASSOCIATION Object.
skipping to change at page 14, line 33 skipping to change at page 14, line 16
corresponds to C-Type = 2 for IPv6 RSVP HOP. corresponds to C-Type = 2 for IPv6 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
associated with each of the following Bypass_Group_Identifiers associated with each of the following Bypass_Group_Identifiers
after receiving the B-SFRR-Active Extended ASSOCIATION Object. after receiving the B-SFRR-Active Extended ASSOCIATION Object.
IPv6 tunnel sender address: IPv6 tunnel sender address:
The IPv6 address that the PLR sets to identify backup path(s) as The IPv6 address that the PLR node sets to identify backup path(s)
described in Section 6.1.1 of [RFC4090]. This address is as 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 nodes. This handshake is performed
the Extended ASSOCIATION object that carries the B-SFRR-Ready using 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 The facility backup method introduced in [RFC4090] takes advantage of
MPLS label stacking (PLR imposing additional MPLS label post FRR) to MPLS label stacking (PLR node imposing additional MPLS label post
allow rerouting of protected traffic over backup path. The backup FRR) to allow rerouting of protected traffic over the backup path.
path may have stricter MTU requirement and due to label stacking at The backup path may have stricter MTU requirement and due to label
PLR, the protected traffic may exceed the backup path MTU. The stacking at PLR node, the protected traffic may exceed the backup
operator is assumed to engineer their network to allow rerouting of path MTU. The operator is assumed to engineer their network to allow
protected traffic and the additional label stacking at PLR to not rerouting of protected traffic and the additional label stacking at
exceed the backup path MTU. PLR node 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 node MUST
the bypass tunnel assignment can satisfy the protected LSP MTU ensure 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 backup path after traffic is due to exceeding the MTU size of the backup path after traffic is
rerouted on to the bypass tunnel post the failure. rerouted on to the bypass tunnel post the failure. Section 2.6 in
[RFC3209] describes a mechanism to determine whether a node needs to
fragment or drop a packet when it exceeds the Path MTU discovered
using RSVP signaling on primary LSP path. A PLR can leverage the
RSVP discovered Path MTU on the backup and primary LSP paths to
ensure MTU is not exceeded before or after rerouting the protected
traffic on to the bypass tunnel.
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
the RSVP Path message of the protected LSP to record the bypass node in the RSVP Path message of the protected LSP to record the
tunnel assignment. This object is updated every time the PLR updates bypass tunnel assignment. This object is updated every time the PLR
the bypass tunnel assignment and that triggers an RSVP Path change node updates the bypass tunnel assignment and that triggers an RSVP
message. Path change 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 Extended ASSOCIATION ID are present. If from the B-SFRR-Ready Extended ASSOCIATION ID are present. If
present, the PLR determines if the MP has acknowledged the current present, the PLR node determines if the MP has acknowledged the
PLR assignment. current PLR node's assignment.
To be a valid acknowledgement, the received B-SFRR-Ready Extended To be a valid acknowledgement, the received B-SFRR-Ready Extended
ASSOCIATION ID contents within the RSVP Resv message of the protected ASSOCIATION ID contents within the RSVP Resv message of the protected
LSP MUST match the latest B-SFRR-Ready Extended ASSOCIATION object LSP MUST match the latest B-SFRR-Ready Extended ASSOCIATION object
and Association ID contents that the PLR node had sent within the and Association ID contents that the PLR node had sent within the
RSVP 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. Bypass_Source_IPv4_Address or Bypass_Source_IPv6_Address field
matches any of the PLR node addresses.
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, an MP node processes all (there may be multiple
PLRs for a single MP) B-SFRR-Ready Extended ASSOCIATION objects that PLR nodes for a single MP node) B-SFRR-Ready Extended ASSOCIATION
have the MP node address as Bypass Destination address in the objects that have the MP node address as Bypass Destination address
Extended Association ID. in the 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 node
which is determined using the Bypass_Source_Address field. The by associating the Bypass_Source_IPv4_Address or
MESSAGE_ID is extracted and recorded for the protected LSP Path Bypass_Source_IPv6_Address that is carried in the IPv4 or IPv6 B-
SFRR-Ready Extended ASSOCIATION IDs respectively.
The 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 the exception of the MESSAGE_ID objects, all protected LSP. With the exception of the MESSAGE_ID objects, all
other fields of the received B-SFRR-Ready Extended ASSOCIATION object other fields of the received B-SFRR-Ready Extended ASSOCIATION object
in 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 received from the different upstream PLR
a failure, the MP node determines and activates the associated node(s). After a failure, the MP node determines and activates the
Summary Refresh ID to use once it receives and processes the RSVP state(s) associated with the Bypass_Group_Identifier(s) received in
Path message containing B-SFRR-Active Extended ASSOCIATION object the RSVP Path message containing B-SFRR-Active Extended ASSOCIATION
that is signaled over the bypass tunnel from the PLR, as described object that is signaled over the bypass tunnel from the PLR node, as
Section 3.4 described Section 3.4
When forwarding an RSVP Path message downstream, the MP SHOULD remove When forwarding an RSVP Path message downstream, the MP node SHOULD
any/all B-SFRR-Ready Extended ASSOCIATION object(s) whose Association remove any/all B-SFRR-Ready Extended ASSOCIATION object(s) whose
ID contains Bypass_Destination_Address matching the MP node address. Bypass_Destination_IPv4_Address or Bypass_Destination_IPv6_Address
field matches any of the MP node addresses.
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 a fault (egress link or node failure) the PLR node
first performs the object modification procedures described by will first perform 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 node 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 where the PLR node 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 node adds the B-SFRR-Active Extended Association
the RSVP Path message of the RSVP session of the bypass tunnel. object in 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 a common object that will be applied to all LSPs
Section 3.3 of this document. associated with the Bypass_Group_Identifiers that are carried in the
B-SFRR-Active Extended ASSOCIATION ID.
The previously received MESSAGE_ID from the MP is activated. As a
result, the MP may refresh the protected rerouted Resv state using
Summary Refresh procedures.
The PLR adds the Bypass_Group_Identifier(s) of group(s) that have The PLR node adds the Bypass_Group_Identifier(s) of group(s) that
common group attributes, including the tunnel sender address, to the have common group attributes, including the tunnel sender address, to
same B-SFRR-Active Extended ASSOCIATION ID. Note that multiple the 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 tunnel and sent towards the MP as described in [RFC6780]. the bypass tunnel and sent towards the MP as described in [RFC6780].
The previously received MESSAGE_ID(s) from the MP are activated on
the PLR. As a result, the PLR starts sending Srefresh messages
containing the specific Message_identifier(s) for the states to be
refreshed.
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 an individual RSVP Path messages for that LSP. if it had received an individual RSVP Path message for that LSP.
For each Summary FRR capable LSP that is being merged, the MP first For each Summary FRR capable LSP that is being merged, the MP first
modifies the Path 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 RSVP_HOP_Object field in
ASSOCIATION ID. the B-SFRR-Active Extended ASSOCIATION ID.
2. The TIME_VALUES object is copied from the TIMES_VALUE field in 2. The TIME_VALUES object is copied from the TIME_VALUES 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 node to generate
and that would have exchanged in a Path message sent to the MP refreshes and that would have exchanged in a Path message sent to
after the failure when no Summary FRR procedures are in effect. the MP 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 field 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 node 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(s) from the PLR node are
meaning that the PLR may now refresh the protected rerouted Path activated. The MP is allowed to send Srefresh messages
state using Summary Refresh procedures. containing the specific Message_identifier(s) for the states to
be refreshed.
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, where b=0 or 1. This ensures
non-supporting node(s). Such nodes will ignore the object and compatibility with non-supporting node(s) in accordance with the
forward it without modification. procedures specified in [RFC2205], Section 3.10 for unknown-class
objects, Such nodes will ignore the object and forward it without any
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. the case.
When using procedures defined in this document, FRR (or the reroute When using procedures defined in this document, FRR signaling for
of protected LSP(s) on to the bypass tunnel) can be activated on per rerouting of protected LSP(s) states on to the bypass tunnel can be
group of protected LSP(s). This allows an intruder to potentially performed on a group of protected LSP(s) with a single RSVP message.
impact and manipulate a set of protected LSP that are assigned to the This allows an intruder to potentially impact and manipulate a set of
same bypass tunnel group. protected LSP that are assigned to the same bypass tunnel group.
Note that such attack is even possible without the mechanisms
proposed in this document; albeit, at an extra cost resulting from
the excessive per LSP signaling that will occur.
Existing mechanisms for maintaining the integrity and authenticity of Existing mechanisms for maintaining the integrity and authenticity of
RSVP protocol messages [RFC2747] can be applied. Other RSVP protocol messages [RFC2747] can be applied. Other
considerations mentioned in [RFC4090] and [RFC5920] also apply. 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.
 End of changes. 71 change blocks. 
204 lines changed or deleted 249 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/