draft-ietf-mpls-summary-frr-rsvpte-03.txt   draft-ietf-mpls-summary-frr-rsvpte-04.txt 
MPLS Working Group M. Taillon MPLS Working Group M. Taillon
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track T. Saad, Ed. Intended status: Standards Track T. Saad, Ed.
Expires: November 3, 2019 Juniper Networks Expires: November 23, 2019 Juniper Networks
R. Gandhi 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
May 02, 2019 May 22, 2019
RSVP-TE Summary Fast Reroute Extensions for LSP Tunnels RSVP-TE Summary Fast Reroute Extensions for LSP Tunnels
draft-ietf-mpls-summary-frr-rsvpte-03 draft-ietf-mpls-summary-frr-rsvpte-04
Abstract Abstract
This document defines Resource Reservation Protocol (RSVP) Traffic- This document defines Resource Reservation Protocol (RSVP) Traffic-
Engineering (TE) signaling extensions that reduce the amount of RSVP Engineering (TE) signaling extensions that reduce the amount of RSVP
signaling required for Fast Reroute (FRR) procedures and subsequently signaling required for Fast Reroute (FRR) procedures and subsequently
improve the scalability of the RSVP-TE signaling when undergoing FRR improve the scalability of the RSVP-TE signaling when undergoing FRR
convergence after a link or node failure. Such extensions allow the convergence after a link or node failure. Such 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) to be independent of the number of protected Label
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 November 3, 2019. This Internet-Draft will expire on November 23, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 31 skipping to change at page 2, line 31
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 . . . . . . . . . . . . 4
3.1. B-SFRR-Ready Extended ASSOCIATION Object . . . . . . . . 5 3.1. B-SFRR-Ready Extended ASSOCIATION Object . . . . . . . . 5
3.1.1. IPv4 B-SFRR-Ready IPv4 Extended ASSOCIATION ID . . . 6 3.1.1. IPv4 B-SFRR-Ready IPv4 Extended ASSOCIATION ID . . . 6
3.1.2. IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID . . . 7 3.1.2. IPv6 B-SFRR-Ready IPv6 Extended ASSOCIATION ID . . . 7
3.2. B-SFRR-Active Extended ASSOCIATION Object . . . . . . . . 10 3.2. B-SFRR-Active Extended ASSOCIATION Object . . . . . . . . 10
3.2.1. B-SFRR-Active Extended ASSOCIATION ID . . . . . . . . 11 3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID . . . . . 11
3.3. Signaling Procedures Prior to Failure . . . . . . . . . . 12 3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID . . . . . 12
3.3.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 12 3.3. Signaling Procedures Prior to Failure . . . . . . . . . . 13
3.3.2. MP Signaling Procedure . . . . . . . . . . . . . . . 12 3.3.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 13
3.4. Signaling Procedures Post Failure . . . . . . . . . . . . 13 3.3.2. MP Signaling Procedure . . . . . . . . . . . . . . . 14
3.4.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 13 3.4. Signaling Procedures Post Failure . . . . . . . . . . . . 15
3.4.2. MP Signaling Procedure . . . . . . . . . . . . . . . 14 3.4.1. PLR Signaling Procedure . . . . . . . . . . . . . . . 15
3.5. Refreshing Summary FRR Active LSPs . . . . . . . . . . . 15 3.4.2. MP Signaling Procedure . . . . . . . . . . . . . . . 15
4. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 15 3.5. Refreshing Summary FRR Active LSPs . . . . . . . . . . . 16
5. Security Considerations . . . . . . . . . . . . . . . . . . . 15 4. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 16
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 5. Security Considerations . . . . . . . . . . . . . . . . . . . 17
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 16 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 16 7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 17
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 8. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 17
9.1. Normative References . . . . . . . . . . . . . . . . . . 16 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 17
9.2. Informative References . . . . . . . . . . . . . . . . . 17 9.1. Normative References . . . . . . . . . . . . . . . . . . 17
9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 17 9.2. Informative References . . . . . . . . . . . . . . . . . 18
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 17 9.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 19
1. Introduction 1. Introduction
The Fast Reroute (FRR) procedures defined in [RFC4090] describe the The Fast Reroute (FRR) procedures defined in [RFC4090] describe the
mechanisms for the Point of Local Repair (PLR) to reroute traffic and mechanisms for the Point of Local Repair (PLR) to reroute traffic and
signaling of a protected RSVP-TE LSP onto the bypass tunnel in the signaling of a protected RSVP-TE LSP onto the bypass tunnel in the
event of a TE link or node failure. Such signaling procedures are event of a TE link or node failure. Such signaling procedures are
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 MP due to limited memory and CPU processing
skipping to change at page 11, line 5 skipping to change at page 11, line 5
------- ------ ------- ------
(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 for the Bypass Summary FRR Active association.
The rules to populate the Extended ASSOCIATION ID in this case are The rules to populate the Extended ASSOCIATION ID in this case are
described below. described below.
3.2.1. B-SFRR-Active Extended ASSOCIATION ID 3.2.1. IPv4 B-SFRR-Active Extended ASSOCIATION ID
The Extended ASSOCIATION ID for the B-SFRR-Active association type The IPv4 Extended ASSOCIATION ID for the B-SFRR-Active association
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num-BGIDs | Reserved | | Num-BGIDs | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bypass_Group_Identifier | | Bypass_Group_Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : | | : |
// : // // : //
| : | | : |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bypass_Group_Identifier | | Bypass_Group_Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RSVP_HOP_Object | // RSVP_HOP_Object //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| TIME_VALUES | // TIME_VALUES //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 tunnel sender address |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: The 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
The Bypass_Group_Identifier that is previously signaled by the The Bypass_Group_Identifier that is previously signaled by the PLR
PLR using the Extended Association object. One or using the Extended Association object. One or more
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 corresponds with each of the following Bypass_Group_Identifiers. This
to C-Type = 1 for IPv4 RSVP HOP, or C-Type = 2 for IPv6 RSVP HOP corresponds to C-Type = 1 for IPv4 RSVP HOP.
depending on the IP address family carried within the object.
TIME_VALUES object: Class 5, as defined by [RFC2205]
Replacement TIME_VALUES object to be applied to all LSPs
associated with each of the following Bypass_Group_Identifiers
after receiving the B-SFRR-Active Extended ASSOCIATION Object.
IPv4 tunnel sender address:
The IPv4 address that the PLR sets to identify backup path(s) as
described in Section 6.1.1 of [RFC4090].
3.2.2. IPv6 B-SFRR-Active Extended ASSOCIATION ID
The IPv6 Extended ASSOCIATION ID for the B-SFRR-Active association
type is carried inside the IPv6 Extended ASSOCIATION object and has
the following format:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num-BGIDs | Reserved |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bypass_Group_Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| : |
// : //
| : |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bypass_Group_Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// RSVP_HOP_Object //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
// TIME_VALUES //
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
+ +
| |
+ IPv6 tunnel sender address +
| |
+ +
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: The IPv6 Extended ASSOCIATION ID for B-SFRR-Active
Num-BGIDs: 16 bits
Number of Bypass_Group_Identifier fields.
Reserved: 16 bits
Reserved for future use.
Bypass_Group_Identifier: 32 bits
The Bypass_Group_Identifier that is previously signaled by the PLR
using the Extended Association object. One or more
Bypass_Group_Identifiers may be included.
RSVP_HOP_Object: Class 3, as defined by [RFC2205]
Replacement RSVP HOP object to be applied to all LSPs associated
with each of the following Bypass_Group_Identifiers. This
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 associated
with each of the following Bypass_Group_Identifiers after receiving Replacement TIME_VALUES object to be applied to all LSPs
the B-SFRR-Active Extended ASSOCIATION Object. associated with each of the following Bypass_Group_Identifiers
after receiving the B-SFRR-Active Extended ASSOCIATION Object.
IPv6 tunnel sender address:
The IPv6 address that the PLR sets to identify backup path(s) as
described in Section 6.1.1 of [RFC4090].
3.3. Signaling Procedures Prior to Failure 3.3. Signaling Procedures Prior to Failure
Before Summary FRR procedures can be used, a handshake MUST be Before Summary FRR procedures can be used, a handshake MUST be
completed between the PLR and MP. This handshake is performed using completed between the PLR and MP. This handshake is performed using
Extended ASSOCIATION object that carries the B-SFRR-Ready Extended Extended ASSOCIATION object that carries the B-SFRR-Ready Extended
Association ID in both the RSVP Path and Resv messages of the Association ID in both the RSVP Path and Resv messages of the
protected LSP. protected LSP.
When using procedures defined in this document, the PLR MUST ensure
bypass tunnel assignment can satisfy the protected LSP MTU
requirements post FRR. This avoids any packets from being dropped
due to exceeding the MTU size of the bypass tunnel after traffic is
rerouted on the bypass tunnel post failure.
3.3.1. PLR Signaling Procedure 3.3.1. PLR Signaling Procedure
The B-SFRR-Ready Extended ASSOCIATION object is added by each PLR in The B-SFRR-Ready Extended ASSOCIATION object is added by each PLR in
the RSVP Path message of the protected LSP to record the bypass the RSVP Path message of the protected LSP to record the bypass
tunnel assignment. This object is updated every time the PLR updates tunnel assignment. This object is updated every time the PLR updates
the bypass tunnel assignment and that triggers an RSVP Path change the bypass tunnel assignment and that triggers an RSVP Path change
message. message.
Upon receiving an RSVP Resv message with B-SFRR-Ready Extended Upon receiving an RSVP Resv message with B-SFRR-Ready Extended
ASSOCIATION object, the PLR node checks if the expected subobjects ASSOCIATION object, the PLR node checks if the expected subobjects
skipping to change at page 14, line 37 skipping to change at page 16, line 19
1. The RSVP_HOP object is copied from the B-SFRR-Active Extended 1. The RSVP_HOP object is copied from the B-SFRR-Active Extended
ASSOCIATION ID. ASSOCIATION ID.
2. The TIME_VALUES object is copied from the TIMES_VALUE field in 2. The TIME_VALUES object is copied from the TIMES_VALUE field in
the B-SFRR-Active Extended ASSOCIATION ID. The TIME_VALUES the B-SFRR-Active Extended ASSOCIATION ID. The TIME_VALUES
object contains the refresh time of the PLR to generate refreshes object contains the refresh time of the PLR to generate refreshes
and that would have exchanged in a Path message sent to the MP and that would have exchanged in a Path message sent to the MP
after the failure when no SFRR procedures are in effect. after the failure when no SFRR procedures are in effect.
3. The SENDER_TEMPLATE object SrcAddress field is copied from the 3. The tunnel sender address field in the SENDER_TEMPLATE object is
bypass tunnel SENDER_TEMPLATE object. For the case where PLR is copied from the tunnel sender address of the B-SFRR-Active
also the head-end, and SENDER_TEMPLATE SrcAddress of the Extended ASSOCIATION ID.
protected LSP and bypass tunnel are the same, the MP MUST use the
modified HOP Address field instead.
4. The ERO object is modified as per Section 6.4.4. of [RFC4090]. 4. The ERO object is modified as per Section 6.4.4 of [RFC4090].
Once the above modifications are completed, the MP then performs Once the above modifications are completed, the MP then performs
the merge processing as per [RFC4090]. the merge processing as per [RFC4090].
5. The previously received MESSAGE_ID from the PLR is activated, 5. The previously received MESSAGE_ID from the PLR is activated,
meaning that the PLR may now refresh the protected rerouted PATH meaning that the PLR may now refresh the protected rerouted PATH
state using Summary Refresh procedures. state using Summary Refresh procedures.
A failure during merge processing of any individual rerouted LSP MUST A failure during merge processing of any individual rerouted LSP MUST
result in an RSVP Path Error message. result in an RSVP Path Error message.
skipping to change at page 16, line 7 skipping to change at page 17, line 35
----- ---- --------- ----- ---- ---------
TBD-1 B-SFRR-Ready Association Section 3.1 TBD-1 B-SFRR-Ready Association Section 3.1
TBD-2 B-SFRR-Active Association Section 3.2 TBD-2 B-SFRR-Active Association Section 3.2
IANA also maintains and assigns the values for the RSVP-TE protocol IANA also maintains and assigns the values for the RSVP-TE protocol
parameters "Resource Reservation Protocol (RSVP) Parameters" (see parameters "Resource Reservation Protocol (RSVP) Parameters" (see
http://www.iana.org/assignments/rsvp-parameters). http://www.iana.org/assignments/rsvp-parameters).
7. Acknowledgments 7. Acknowledgments
The authors would like to thank Loa Andersson, Lou Berger, Eric The authors would like to thank Alexander Okonnikov, Loa Andersson,
Osborne, Gregory Mirsky, and Mach Chen for reviewing and providing Lou Berger, Eric Osborne, Gregory Mirsky, Mach Chen for reviewing and
valuable comments to this document. providing valuable comments to this document.
8. Contributors 8. Contributors
Nicholas Tan Nicholas Tan
Arista Networks Arista Networks
Email: ntan@arista.com Email: ntan@arista.com
9. References 9. References
 End of changes. 17 change blocks. 
47 lines changed or deleted 124 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/