draft-ietf-teas-gmpls-lsp-fastreroute-08.txt   draft-ietf-teas-gmpls-lsp-fastreroute-09.txt 
TEAS Working Group M. Taillon TEAS Working Group M. Taillon
Internet-Draft T. Saad, Ed. Internet-Draft T. Saad, Ed.
Intended Status: Standards Track R. Gandhi, Ed. Intended Status: Standards Track R. Gandhi, Ed.
Expires: November 13, 2017 Z. Ali Expires: November 16, 2017 Z. Ali
Cisco Systems, Inc. Cisco Systems, Inc.
M. Bhatia M. Bhatia
Nokia Nokia
May 12, 2017 May 15, 2017
Extensions to Resource Reservation Protocol For Fast Reroute of Extensions to Resource Reservation Protocol For Fast Reroute of
Traffic Engineering GMPLS LSPs Traffic Engineering GMPLS LSPs
draft-ietf-teas-gmpls-lsp-fastreroute-08 draft-ietf-teas-gmpls-lsp-fastreroute-09
Abstract Abstract
This document defines Resource Reservation Protocol - Traffic This document defines Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) signaling extensions to support Fast Reroute Engineering (RSVP-TE) signaling extensions to support Fast Reroute
(FRR) of Packet Switched Capable (PSC) Generalized Multi-Protocol (FRR) of Packet Switched Capable (PSC) Generalized Multi-Protocol
Label Switching (GMPLS) Label Switched Paths (LSPs). These signaling Label Switching (GMPLS) Label Switched Paths (LSPs). These signaling
extensions allow the coordination of a bidirectional bypass tunnel extensions allow the coordination of a bidirectional bypass tunnel
assignment protecting a common facility in both forward and reverse assignment protecting a common facility in both forward and reverse
directions of a co-routed bidirectional LSP. In addition, these directions of a co-routed bidirectional LSP. In addition, these
skipping to change at page 2, line 47 skipping to change at page 2, line 47
5.1. Link Protection for Bidirectional GMPLS LSPs . . . . . . . 11 5.1. Link Protection for Bidirectional GMPLS LSPs . . . . . . . 11
5.1.1. Behavior After Link Failure . . . . . . . . . . . . . 12 5.1.1. Behavior After Link Failure . . . . . . . . . . . . . 12
5.1.2. Revertive Behavior After Fast Reroute . . . . . . . . 12 5.1.2. Revertive Behavior After Fast Reroute . . . . . . . . 12
5.2. Node Protection for Bidirectional GMPLS LSPs . . . . . . . 12 5.2. Node Protection for Bidirectional GMPLS LSPs . . . . . . . 12
5.2.1. Behavior After Link Failure . . . . . . . . . . . . . 13 5.2.1. Behavior After Link Failure . . . . . . . . . . . . . 13
5.2.2. Behavior After Link Failure To Re-coroute . . . . . . 13 5.2.2. Behavior After Link Failure To Re-coroute . . . . . . 13
5.2.2.1. Re-coroute in Data-plane After Link Failure . . . 14 5.2.2.1. Re-coroute in Data-plane After Link Failure . . . 14
5.2.3. Revertive Behavior After Fast Reroute . . . . . . . . 15 5.2.3. Revertive Behavior After Fast Reroute . . . . . . . . 15
5.3. Unidirectional Link Failures . . . . . . . . . . . . . . . 15 5.3. Unidirectional Link Failures . . . . . . . . . . . . . . . 15
6. Fast Reroute For Bidirectional GMPLS LSPs with Out-of-band 6. Fast Reroute For Bidirectional GMPLS LSPs with Out-of-band
Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . 15 Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . 16
7. Message and Object Definitions . . . . . . . . . . . . . . . . 16 7. Message and Object Definitions . . . . . . . . . . . . . . . . 16
7.1. BYPASS_ASSIGNMENT Subobject . . . . . . . . . . . . . . . 16 7.1. BYPASS_ASSIGNMENT Subobject . . . . . . . . . . . . . . . 16
7.2. FRR Bypass Assignment Error Notify Message . . . . . . . . 18 7.2. FRR Bypass Assignment Error Notify Message . . . . . . . . 18
8. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 18 8. Compatibility . . . . . . . . . . . . . . . . . . . . . . . . 18
9. Security Considerations . . . . . . . . . . . . . . . . . . . 18 9. Security Considerations . . . . . . . . . . . . . . . . . . . 18
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19
10.1. BYPASS_ASSIGNMENT Subobject . . . . . . . . . . . . . . . 19 10.1. BYPASS_ASSIGNMENT Subobject . . . . . . . . . . . . . . . 19
10.2. FRR Bypass Assignment Error Notify Message . . . . . . . 19 10.2. FRR Bypass Assignment Error Notify Message . . . . . . . 19
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
11.1. Normative References . . . . . . . . . . . . . . . . . . 20 11.1. Normative References . . . . . . . . . . . . . . . . . . 20
11.2. Informative References . . . . . . . . . . . . . . . . . 20 11.2. Informative References . . . . . . . . . . . . . . . . . 20
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 21 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . . 21
Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 22
1. Introduction 1. Introduction
skipping to change at page 5, line 30 skipping to change at page 5, line 30
2.1. Key Word Definitions 2.1. Key Word Definitions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2.2. Terminology 2.2. Terminology
The reader is assumed to be familiar with the terminology in The reader is assumed to be familiar with the terminology in
[RFC2205], [RFC3209], [RFC3471], [RFC3473] and [RFC4090]. [RFC2205], [RFC3209], [RFC3471], [RFC3473], and [RFC4090].
Downstream PLR: Downstream Point of Local Repair. The PLR that Downstream PLR: Downstream Point of Local Repair. The PLR that
locally detects a failure in the downstream direction of the locally detects a failure in the downstream direction of the
traffic flow and reroutes traffic in the same direction of the traffic flow and reroutes traffic in the same direction of the
protected bidirectional LSP RSVP Path signaling. A downstream PLR protected bidirectional LSP RSVP Path signaling. A downstream PLR
has a corresponding downstream MP. has a corresponding downstream MP.
Downstream MP: Downstream Merge Point. The LSR where one or more Downstream MP: Downstream Merge Point. The LSR where one or more
backup tunnels rejoin the path of the protected LSP in the backup tunnels rejoin the path of the protected LSP in the
downstream direction of the traffic flow. The same LSR may be downstream direction of the traffic flow. The same LSR may be
skipping to change at page 12, line 32 skipping to change at page 12, line 32
The revertive behavior defined in [RFC4090], Section 6.5.2, is The revertive behavior defined in [RFC4090], Section 6.5.2, is
applicable to the link protection of bidirectional GMPLS LSPs. When applicable to the link protection of bidirectional GMPLS LSPs. When
using the local revertive mode, after the link R3-R4 (in Figure 1) is using the local revertive mode, after the link R3-R4 (in Figure 1) is
restored, following node behaviors apply: restored, following node behaviors apply:
o The downstream PLR R3 starts sending the Path messages and traffic o The downstream PLR R3 starts sending the Path messages and traffic
flow of the protected LSP over the restored link and stops sending flow of the protected LSP over the restored link and stops sending
them over the bypass tunnel. them over the bypass tunnel.
o The upstream PLR R4 starts sending the Resv messages and traffic o The upstream PLR R4 starts sending the traffic flow of the
flow of the protected LSP over the restored link and stops sending protected LSP over the restored link and stops sending it over the
them over the bypass tunnel. bypass tunnel.
o When upstream PLR R4 receives the protected LSP Path messages over o When upstream PLR R4 receives the protected LSP Path messages over
the restored link, if not already done, it starts sending Resv the restored link, if not already done, it starts sending Resv
messages and traffic flow of the protected LSP over the restored messages and traffic flow of the protected LSP over the restored
link and stops sending them over the bypass tunnel. link and stops sending them over the bypass tunnel.
5.2. Node Protection for Bidirectional GMPLS LSPs 5.2. Node Protection for Bidirectional GMPLS LSPs
T1 T1
+<<------->>+ +<<------->>+
skipping to change at page 15, line 17 skipping to change at page 15, line 17
The revertive behavior defined in [RFC4090], Section 6.5.2, is The revertive behavior defined in [RFC4090], Section 6.5.2, is
applicable to the node protection of bidirectional GMPLS LSPs. When applicable to the node protection of bidirectional GMPLS LSPs. When
using the local revertive mode, after the link R3-R4 (in Figures 2 using the local revertive mode, after the link R3-R4 (in Figures 2
and 3) is restored, following node behaviors apply: and 3) is restored, following node behaviors apply:
o The downstream PLR R3 starts sending the Path messages and traffic o The downstream PLR R3 starts sending the Path messages and traffic
flow of the protected LSP over the restored link and stops sending flow of the protected LSP over the restored link and stops sending
them over the bypass tunnel. them over the bypass tunnel.
o The upstream PLR R4 starts sending the traffic flow of the
protected LSP over the restored link towards downstream PLR R3 and
forwarding the Path messages towards PRR R5 and stops sending the
traffic over the bypass tunnel.
o When upstream PLR R4 receives the protected LSP Path messages over o When upstream PLR R4 receives the protected LSP Path messages over
the restored link, if not already done, it starts sending Resv the restored link, if not already done, it starts sending Resv
messages and traffic flow over the restored link towards messages and traffic flow over the restored link towards
downstream PLR R3 and forwarding the Path messages towards PRR R5 downstream PLR R3 and forwarding the Path messages towards PRR R5
and stops sending them over the bypass tunnel. and stops sending them over the bypass tunnel.
o When PRR R5 receives the protected LSP Path messages over the o When PRR R5 receives the protected LSP Path messages over the
restored path, it starts sending Resv messages and traffic flow restored path, it starts sending Resv messages and traffic flow
over the restored path and stops sending them over the bypass over the restored path and stops sending them over the bypass
tunnel. tunnel.
 End of changes. 8 change blocks. 
9 lines changed or deleted 14 lines changed or added

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