SRv6 Path Egress Protection
draft-hu-rtgwg-srv6-egress-protection-03
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-10-29
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
htmlized
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group Z. Hu
Internet-Draft Huawei Technologies
Intended status: Standards Track H. Chen
Expires: May 1, 2020 Futurewei
H. Chen
China Telecom
P. Wu
Huawei Technologies
October 29, 2019
SRv6 Path Egress Protection
draft-hu-rtgwg-srv6-egress-protection-03
Abstract
This document describes protocol extensions for protecting the egress
node of a Segment Routing for IPv6 (SRv6) path or tunnel.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on May 1, 2020.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
Hu, et al. Expires May 1, 2020 [Page 1]
Internet-Draft Egress Protection October 2019
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminologies . . . . . . . . . . . . . . . . . . . . . . . . 3
3. SR Path Egress Protection . . . . . . . . . . . . . . . . . . 4
4. Extensions to IGP for Egress Protection . . . . . . . . . . . 5
4.1. Extensions to IS-IS . . . . . . . . . . . . . . . . . . . 5
4.2. Extensions to OSPF . . . . . . . . . . . . . . . . . . . 7
5. Behavior for SRv6 Mirror SID . . . . . . . . . . . . . . . . 9
6. Security Considerations . . . . . . . . . . . . . . . . . . . 9
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
7.1. IS-IS . . . . . . . . . . . . . . . . . . . . . . . . . . 10
7.2. OSPFv3 . . . . . . . . . . . . . . . . . . . . . . . . . 10
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 11
9.1. Normative References . . . . . . . . . . . . . . . . . . 11
9.2. Informative References . . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 13
1. Introduction
The fast protection of a transit node of a Segment Routing (SR) path
or tunnel is described in [I-D.ietf-rtgwg-segment-routing-ti-lfa] and
[I-D.hu-spring-segment-routing-proxy-forwarding]. [RFC8400]
specifies the fast protection of egress node(s) of an MPLS TE LSP
tunnel including P2P TE LSP tunnel and P2MP TE LSP tunnel in details.
However, these documents do not discuss the fast protection of the
egress node of a Segment Routing for IPv6 (SRv6) path or tunnel.
This document fills that void and presents protocol extensions for
the fast protection of the egress node of an SRv6 path or tunnel.
Egress node and egress, fast protection and protection as well as
SRv6 path and SRv6 tunnel will be used exchangeably below.
Hu, et al. Expires May 1, 2020 [Page 2]
Internet-Draft Egress Protection October 2019
2. Terminologies
The following terminologies are used in this document.
SR: Segment Routing
SRv6: SR for IPv6
SRH: Segment Routing Header
Show full document text