SRv6 Proxy Forwarding
draft-chen-rtgwg-srv6-midpoint-protection-00
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2019-03-10
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
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 H. Chen
Internet-Draft China Telecom
Intended status: Standards Track Z. Hu
Expires: September 11, 2019 H. Chen
Huawei Technologies
March 10, 2019
SRv6 Proxy Forwarding
draft-chen-rtgwg-srv6-midpoint-protection-00
Abstract
The endpoints of a SRv6 path are given by a SRv6 Policy. When an
endpoint node fails, we need bypass this failed endpoint node and
forward the packets to the failed node's next endpoint node.
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 September 11, 2019.
Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved.
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
Chen, et al. Expires September 11, 2019 [Page 1]
Internet-Draft SRv6 Proxy Forwarding March 2019
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. Endpoint Node Protection for Segment List . . . . . . . . . . 3
2.1. Transit Node as PLR . . . . . . . . . . . . . . . . . . . 3
2.2. Endpoint Node as PLR . . . . . . . . . . . . . . . . . . 3
2.3. Endpoint x Node as PLR . . . . . . . . . . . . . . . . . 4
2.4. Endpoint t Node as PLR . . . . . . . . . . . . . . . . . 5
3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
6. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
6.1. Normative References . . . . . . . . . . . . . . . . . . 6
6.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
"Segment Routing Proxy Forwarding" for IPv4 is defined in
[I-D.hu-spring-segment-routing-proxy-forwarding]. It provides the
protections for the middle endpoints of a SR path. This document
specifies the proxy forwarding for SRv6, which supports the
protections for the middle endpoints of a SRv6 path.
The endpoints of a SRv6 path are given by a SRv6 Policy. When an
endpoint node fails, we need bypass this failed endpoint node and
forward the packets to the failed node's next endpoint node. On the
PLR (i.e., the previous hop node of the failed endpoint node), it
performs the bypass protection as follows if NH = SRH and SL != 0.
If the outbound interface fails and the failed endpoint node (FN for
short) is directly connected to the PLR, then the PLR forwards the
packets through a bypass to the FN's next endpoint node. If it is
not directly connected, the normal Ti-LFA is executed.
If it is a FIB miss, the PLR forwards the packets through a bypass to
the FN's next endpoint node. There is no need to check if the failed
endpoint node is directly connected to the PLR.
Chen, et al. Expires September 11, 2019 [Page 2]
Internet-Draft SRv6 Proxy Forwarding March 2019
2. Endpoint Node Protection for Segment List
Show full document text