< draft-ietf-bess-srv6-services-12.txt   draft-ietf-bess-srv6-services-13.txt >
BESS Working Group G. Dawra, Ed. BESS Working Group G. Dawra, Ed.
Internet-Draft LinkedIn Internet-Draft LinkedIn
Intended status: Standards Track C. Filsfils Intended status: Standards Track C. Filsfils
Expires: September 6, 2022 K. Talaulikar, Ed. Expires: September 20, 2022 K. Talaulikar, Ed.
Cisco Systems Cisco Systems
R. Raszuk R. Raszuk
NTT Network Innovations NTT Network Innovations
B. Decraene B. Decraene
Orange Orange
S. Zhuang S. Zhuang
Huawei Technologies Huawei Technologies
J. Rabadan J. Rabadan
Nokia Nokia
March 5, 2022 March 19, 2022
SRv6 BGP based Overlay Services SRv6 BGP based Overlay Services
draft-ietf-bess-srv6-services-12 draft-ietf-bess-srv6-services-13
Abstract Abstract
This document defines procedures and messages for SRv6-based BGP This document defines procedures and messages for SRv6-based BGP
services including L3VPN, EVPN, and Internet services. It builds on services including L3VPN, EVPN, and Internet services. It builds on
RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and RFC7432 RFC4364 "BGP/MPLS IP Virtual Private Networks (VPNs)" and RFC7432
"BGP MPLS-Based Ethernet VPN". "BGP MPLS-Based Ethernet VPN".
Status of This Memo Status of This Memo
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 September 6, 2022. This Internet-Draft will expire on September 20, 2022.
Copyright Notice Copyright Notice
Copyright (c) 2022 IETF Trust and the persons identified as the Copyright (c) 2022 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 26 skipping to change at page 2, line 26
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 4
2. SRv6 Services TLVs . . . . . . . . . . . . . . . . . . . . . 4 2. SRv6 Services TLVs . . . . . . . . . . . . . . . . . . . . . 4
3. SRv6 Service Sub-TLVs . . . . . . . . . . . . . . . . . . . . 5 3. SRv6 Service Sub-TLVs . . . . . . . . . . . . . . . . . . . . 5
3.1. SRv6 SID Information Sub-TLV . . . . . . . . . . . . . . 6 3.1. SRv6 SID Information Sub-TLV . . . . . . . . . . . . . . 6
3.2. SRv6 Service Data Sub-Sub-TLVs . . . . . . . . . . . . . 7 3.2. SRv6 Service Data Sub-Sub-TLVs . . . . . . . . . . . . . 7
3.2.1. SRv6 SID Structure Sub-Sub-TLV . . . . . . . . . . . 8 3.2.1. SRv6 SID Structure Sub-Sub-TLV . . . . . . . . . . . 8
4. Encoding SRv6 SID Information . . . . . . . . . . . . . . . . 10 4. Encoding SRv6 SID Information . . . . . . . . . . . . . . . . 10
5. BGP based L3 Service over SRv6 . . . . . . . . . . . . . . . 11 5. BGP based L3 Service over SRv6 . . . . . . . . . . . . . . . 11
5.1. IPv4 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 12 5.1. IPv4 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 13
5.2. IPv6 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 13 5.2. IPv6 VPN Over SRv6 Core . . . . . . . . . . . . . . . . . 13
5.3. Global IPv4 over SRv6 Core . . . . . . . . . . . . . . . 13 5.3. Global IPv4 over SRv6 Core . . . . . . . . . . . . . . . 13
5.4. Global IPv6 over SRv6 Core . . . . . . . . . . . . . . . 13 5.4. Global IPv6 over SRv6 Core . . . . . . . . . . . . . . . 13
6. BGP based Ethernet VPN (EVPN) over SRv6 . . . . . . . . . . . 14 6. BGP based Ethernet VPN (EVPN) over SRv6 . . . . . . . . . . . 14
6.1. Ethernet Auto-discovery Route over SRv6 Core . . . . . . 15 6.1. Ethernet Auto-discovery Route over SRv6 Core . . . . . . 15
6.1.1. Ethernet A-D per ES Route . . . . . . . . . . . . . . 16 6.1.1. Ethernet A-D per ES Route . . . . . . . . . . . . . . 16
6.1.2. Ethernet A-D per EVI Route . . . . . . . . . . . . . 16 6.1.2. Ethernet A-D per EVI Route . . . . . . . . . . . . . 16
6.2. MAC/IP Advertisement Route over SRv6 Core . . . . . . . . 17 6.2. MAC/IP Advertisement Route over SRv6 Core . . . . . . . . 17
6.2.1. MAC/IP Advertisement Route with MAC Only . . . . . . 18 6.2.1. MAC/IP Advertisement Route with MAC Only . . . . . . 18
6.2.2. MAC/IP Advertisement Route with MAC+IP . . . . . . . 18 6.2.2. MAC/IP Advertisement Route with MAC+IP . . . . . . . 18
skipping to change at page 7, line 22 skipping to change at page 7, line 22
[RFC8986] [RFC8986]
o SRv6 Service SID Flags (1 octet): Encodes SRv6 Service SID Flags - o SRv6 Service SID Flags (1 octet): Encodes SRv6 Service SID Flags -
none are currently defined. SHOULD be set to 0 by the sender and none are currently defined. SHOULD be set to 0 by the sender and
any unknown flags MUST be ignored by the receiver. any unknown flags MUST be ignored by the receiver.
o SRv6 Endpoint Behavior (2 octets): Encodes SRv6 Endpoint behavior o SRv6 Endpoint Behavior (2 octets): Encodes SRv6 Endpoint behavior
codepoint value that is associated with SRv6 SID. The codepoints codepoint value that is associated with SRv6 SID. The codepoints
used are from the "SRv6 Endpoint Behavior" registry under the IANA used are from the "SRv6 Endpoint Behavior" registry under the IANA
"Segment Routing" parameters registry that was introduced by "Segment Routing" parameters registry that was introduced by
[RFC8986]. An unrecognized endpoint behavior MUST NOT be [RFC8986]. The opaque endpoint behavior (i.e., value 0xFFFF) MAY
considered invalid by the receiver. The opaque endpoint behavior be used when the advertising router wishes to abstract the actual
(i.e., value 0xFFFF) MAY be used when the advertising router behavior of it's locally instantiated SRv6 SID.
wishes to abstract the actual behavior of it's locally
instantiated SRv6 SID.
o RESERVED2 (1 octet): MUST be set to 0 by the sender and ignored by o RESERVED2 (1 octet): MUST be set to 0 by the sender and ignored by
the receiver. the receiver.
o SRv6 Service Data Sub-Sub-TLV Value (variable): Used to advertise o SRv6 Service Data Sub-Sub-TLV Value (variable): Used to advertise
properties of the SRv6 SID. It is encoded as a set of SRv6 properties of the SRv6 SID. It is encoded as a set of SRv6
Service Data Sub-Sub-TLVs. Service Data Sub-Sub-TLVs.
The choice of SRv6 Endpoint behavior of the SRv6 SID is entirely up
to the originator of the advertisement. While Section 5 and
Section 6 list the SRv6 Endpoint Behaviors that are normally expected
to be used by the specific route advertisements, the reception of
other SRv6 Endpoint behaviors (e.g., new behaviors that may be
introduced in the future) is not considered an error. An
unrecognized endpoint behavior MUST NOT be considered invalid by the
receiver. An implementation MAY log a rate-limited warning when it
receives an unexpected behavior.
When multiple SRv6 SID Information Sub-TLVs are present, the ingress When multiple SRv6 SID Information Sub-TLVs are present, the ingress
PE SHOULD use the SRv6 SID from the first instance of the Sub-TLV. PE SHOULD use the SRv6 SID from the first instance of the Sub-TLV.
An implementation MAY provide a local policy to override this An implementation MAY provide a local policy to override this
selection. selection.
3.2. SRv6 Service Data Sub-Sub-TLVs 3.2. SRv6 Service Data Sub-Sub-TLVs
The format of the SRv6 Service Data Sub-Sub-TLV is depicted below: The format of the SRv6 Service Data Sub-Sub-TLV is depicted below:
0 1 2 3 0 1 2 3
skipping to change at page 13, line 4 skipping to change at page 13, line 14
5.1. IPv4 VPN Over SRv6 Core 5.1. IPv4 VPN Over SRv6 Core
The MP_REACH_NLRI over SRv6 core is encoded according to IPv4 VPN The MP_REACH_NLRI over SRv6 core is encoded according to IPv4 VPN
Over IPv6 Core defined in [RFC8950]. Over IPv6 Core defined in [RFC8950].
Label field of IPv4-VPN NLRI is encoded as specified in [RFC8277] Label field of IPv4-VPN NLRI is encoded as specified in [RFC8277]
with the 20-bit Label Value set to the whole or a portion of the with the 20-bit Label Value set to the whole or a portion of the
Function part of the SRv6 SID when the Transposition Scheme of Function part of the SRv6 SID when the Transposition Scheme of
encoding (Section 4) is used and otherwise set to Implicit NULL. encoding (Section 4) is used and otherwise set to Implicit NULL.
When using the Transposition Scheme, the Transposition Length MUST be When using the Transposition Scheme, the Transposition Length MUST be
less than or equal to 20 and less than or equal to the Function less than or equal to 20 and less than or equal to the Function
Length. Length.
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
SRv6 Endpoint behavior of the SRv6 SID is entirely up to the SRv6 Endpoint behavior SHOULD be one of these: End.DX4, End.DT4,
originator of the advertisement. In practice, the SRv6 Endpoint End.DT46.
behavior is End.DX4 or End.DT4.
5.2. IPv6 VPN Over SRv6 Core 5.2. IPv6 VPN Over SRv6 Core
The MP_REACH_NLRI over SRv6 core is encoded according to IPv6 VPN The MP_REACH_NLRI over SRv6 core is encoded according to IPv6 VPN
over IPv6 Core is defined in [RFC4659]. over IPv6 Core is defined in [RFC4659].
Label field of the IPv6-VPN NLRI is encoded as specified in [RFC8277] Label field of the IPv6-VPN NLRI is encoded as specified in [RFC8277]
with the 20-bit Label Value set to the whole or a portion of the with the 20-bit Label Value set to the whole or a portion of the
Function part of the SRv6 SID when the Transposition Scheme of Function part of the SRv6 SID when the Transposition Scheme of
encoding (Section 4) is used and otherwise set to Implicit NULL. encoding (Section 4) is used and otherwise set to Implicit NULL.
When using the Transposition Scheme, the Transposition Length MUST be When using the Transposition Scheme, the Transposition Length MUST be
less than or equal to 20 and less than or equal to the Function less than or equal to 20 and less than or equal to the Function
Length. Length.
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
SRv6 Endpoint behavior of the SRv6 SID is entirely up to the SRv6 Endpoint behavior SHOULD be one of these: End.DX6, End.DT6,
originator of the advertisement. In practice, the SRv6 Endpoint End.DT46.
behavior is End.DX6 or End.DT6.
5.3. Global IPv4 over SRv6 Core 5.3. Global IPv4 over SRv6 Core
The MP_REACH_NLRI over SRv6 core is encoded according to IPv4 over The MP_REACH_NLRI over SRv6 core is encoded according to IPv4 over
IPv6 Core is defined in [RFC8950]. IPv6 Core is defined in [RFC8950].
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
SRv6 Endpoint behavior of the SRv6 SID is entirely up to the SRv6 Endpoint behavior SHOULD be one of these: End.DX4, End.DT4,
originator of the advertisement. In practice, the SRv6 Endpoint End.DT46.
behavior is End.DX4 or End.DT4.
5.4. Global IPv6 over SRv6 Core 5.4. Global IPv6 over SRv6 Core
The MP_REACH_NLRI over SRv6 core is encoded according to [RFC2545] The MP_REACH_NLRI over SRv6 core is encoded according to [RFC2545]
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
SRv6 Endpoint behavior of the SRv6 SID is entirely up to the SRv6 Endpoint behavior SHOULD be one of these: End.DX6, End.DT6,
originator of the advertisement. In practice, the SRv6 Endpoint End.DT46.
behavior is End.DX6 or End.DT6.
6. BGP based Ethernet VPN (EVPN) over SRv6 6. BGP based Ethernet VPN (EVPN) over SRv6
[RFC7432] provides an extendable method of building an Ethernet VPN [RFC7432] provides an extendable method of building an Ethernet VPN
(EVPN) overlay. It primarily focuses on MPLS based EVPNs and (EVPN) overlay. It primarily focuses on MPLS based EVPNs and
[RFC8365] extends to IP-based EVPN overlays. [RFC7432] defines Route [RFC8365] extends to IP-based EVPN overlays. [RFC7432] defines Route
Types 1, 2, and 3 which carry prefixes and MPLS Label fields; the Types 1, 2, and 3 which carry prefixes and MPLS Label fields; the
Label fields have a specific use for MPLS encapsulation of EVPN Label fields have a specific use for MPLS encapsulation of EVPN
traffic. Route Type 5 carrying MPLS label information (and thus traffic. Route Type 5 carrying MPLS label information (and thus
encapsulation information) for EVPN is defined in [RFC9136]. Route encapsulation information) for EVPN is defined in [RFC9136]. Route
skipping to change at page 16, line 33 skipping to change at page 16, line 33
carries the whole or a portion of the Argument part of the SRv6 SID carries the whole or a portion of the Argument part of the SRv6 SID
when the ESI filtering approach is used along with the Transposition when the ESI filtering approach is used along with the Transposition
Scheme of encoding (Section 4) and otherwise set to Implicit NULL Scheme of encoding (Section 4) and otherwise set to Implicit NULL
value. In either case, the value is set in the high order 20 bits value. In either case, the value is set in the high order 20 bits
(e.g., as 0x000030 in the case of Implicit NULL). When using the (e.g., as 0x000030 in the case of Implicit NULL). When using the
Transposition Scheme, the Transposition Length MUST be less than or Transposition Scheme, the Transposition Length MUST be less than or
equal to 24 and less than or equal to the Argument Length. equal to 24 and less than or equal to the Argument Length.
A Service SID enclosed in an SRv6 L2 Service TLV within the BGP A Service SID enclosed in an SRv6 L2 Service TLV within the BGP
Prefix-SID attribute is advertised along with the A-D route. The Prefix-SID attribute is advertised along with the A-D route. The
SRv6 Endpoint behavior of the Service SID thus signaled is entirely SRv6 Endpoint behavior SHOULD be End.DT2M. When the ESI filtering
up to the originator of the advertisement. When the ESI filtering
approach is used, the Service SID is used to signal Arg.FE2 SID approach is used, the Service SID is used to signal Arg.FE2 SID
Argument for applicable End.DT2M behavior [RFC8986]. When the local- Argument for applicable End.DT2M behavior [RFC8986]. When the local-
bias approach [RFC8365] is used, the Service SID MAY be of value 0. bias approach [RFC8365] is used, the Service SID MAY be of value 0.
6.1.2. Ethernet A-D per EVI Route 6.1.2. Ethernet A-D per EVI Route
Ethernet A-D per EVI route NLRI encoding over SRv6 core is similar to Ethernet A-D per EVI route NLRI encoding over SRv6 core is similar to
[RFC7432] and [RFC8214] with the following change: [RFC7432] and [RFC8214] with the following change:
o MPLS Label: 24-bit field carries the whole or a portion of the o MPLS Label: 24-bit field carries the whole or a portion of the
Function part of the SRv6 SID when the Transposition Scheme of Function part of the SRv6 SID when the Transposition Scheme of
encoding (Section 4) is used and otherwise set to Implicit NULL encoding (Section 4) is used and otherwise set to Implicit NULL
value. In either case, the value is set in the high order 20 bits value. In either case, the value is set in the high order 20 bits
(e.g., as 0x000030 in the case of Implicit NULL). When using the (e.g., as 0x000030 in the case of Implicit NULL). When using the
Transposition Scheme, the Transposition Length MUST be less than Transposition Scheme, the Transposition Length MUST be less than
or equal to 24 and less than or equal to the Function Length. or equal to 24 and less than or equal to the Function Length.
A Service SID enclosed in an SRv6 L2 Service TLV within the BGP A Service SID enclosed in an SRv6 L2 Service TLV within the BGP
Prefix-SID attribute is advertised along with the A-D route. The Prefix-SID attribute is advertised along with the A-D route. The
SRv6 Endpoint behavior of the Service SID thus signaled is entirely SRv6 Endpoint behavior SHOULD be one of these: End.DX2, End.DX2V,
up to the originator of the advertisement. In practice, the SRv6 End.DT2U.
Endpoint behavior is End.DX2, End.DX2V or End.DT2U.
6.2. MAC/IP Advertisement Route over SRv6 Core 6.2. MAC/IP Advertisement Route over SRv6 Core
EVPN Route Type 2 is used to advertise unicast traffic MAC+IP address EVPN Route Type 2 is used to advertise unicast traffic MAC+IP address
reachability through MP-BGP to all other PEs in a given EVPN reachability through MP-BGP to all other PEs in a given EVPN
instance. instance.
As a reminder, EVPN Route Type 2 is encoded as follows: As a reminder, EVPN Route Type 2 is encoded as follows:
+---------------------------------------+ +---------------------------------------+
skipping to change at page 18, line 33 skipping to change at page 18, line 33
24-bit field carries the whole or a portion of the Function part 24-bit field carries the whole or a portion of the Function part
of the SRv6 SID when the Transposition Scheme of encoding of the SRv6 SID when the Transposition Scheme of encoding
(Section 4) is used and otherwise set to Implicit NULL value. In (Section 4) is used and otherwise set to Implicit NULL value. In
either case, the value is set in the high order 20 bits (e.g., as either case, the value is set in the high order 20 bits (e.g., as
0x000030 in the case of Implicit NULL). When using the 0x000030 in the case of Implicit NULL). When using the
Transposition Scheme, the Transposition Length MUST be less than Transposition Scheme, the Transposition Length MUST be less than
or equal to 24 and less than or equal to the Function Length. or equal to 24 and less than or equal to the Function Length.
A Service SID enclosed in an SRv6 L2 Service TLV within the BGP A Service SID enclosed in an SRv6 L2 Service TLV within the BGP
Prefix-SID attribute is advertised along with the route. The SRv6 Prefix-SID attribute is advertised along with the route. The SRv6
Endpoint behavior of the Service SID thus signaled is entirely up to Endpoint behavior SHOULD be one of these: End.DX2, End.DT2U.
the originator of the advertisement. In practice, the SRv6 Endpoint
behavior is End.DX2 or End.DT2U.
6.2.2. MAC/IP Advertisement Route with MAC+IP 6.2.2. MAC/IP Advertisement Route with MAC+IP
o MPLS Label1: Is associated with the SRv6 L2 Service TLV. This o MPLS Label1: Is associated with the SRv6 L2 Service TLV. This
24-bit field carries the whole or a portion of the Function part 24-bit field carries the whole or a portion of the Function part
of the SRv6 SID when the Transposition Scheme of encoding of the SRv6 SID when the Transposition Scheme of encoding
(Section 4) is used and otherwise set to Implicit NULL value. In (Section 4) is used and otherwise set to Implicit NULL value. In
either case, the value is set in the high order 20 bits (e.g., as either case, the value is set in the high order 20 bits (e.g., as
0x000030 in the case of Implicit NULL). When using the 0x000030 in the case of Implicit NULL). When using the
Transposition Scheme, the Transposition Length MUST be less than Transposition Scheme, the Transposition Length MUST be less than
skipping to change at page 19, line 12 skipping to change at page 19, line 11
(Section 4) is used and otherwise set to Implicit NULL value. In (Section 4) is used and otherwise set to Implicit NULL value. In
either case, the value is set in the high order 20 bits (e.g., as either case, the value is set in the high order 20 bits (e.g., as
0x000030 in the case of Implicit NULL). When using the 0x000030 in the case of Implicit NULL). When using the
Transposition Scheme, the Transposition Length MUST be less than Transposition Scheme, the Transposition Length MUST be less than
or equal to 24 and less than or equal to the Function Length. or equal to 24 and less than or equal to the Function Length.
An L2 Service SID enclosed in an SRv6 L2 Service TLV within the BGP An L2 Service SID enclosed in an SRv6 L2 Service TLV within the BGP
Prefix-SID attribute is advertised along with the route. In Prefix-SID attribute is advertised along with the route. In
addition, an L3 Service SID enclosed in an SRv6 L3 Service TLV within addition, an L3 Service SID enclosed in an SRv6 L3 Service TLV within
the BGP Prefix-SID attribute MAY also be advertised along with the the BGP Prefix-SID attribute MAY also be advertised along with the
route. The SRv6 Endpoint behavior of the Service SID(s) thus route. The SRv6 Endpoint behavior SHOULD be one of these: for the L2
signaled is entirely up to the originator of the advertisement. In Service SID - End.DX2, End.DT2U; for the L3 Service SID - End.DT46,
practice, the SRv6 Endpoint behavior is End.DX2 or End.DT2U for the End.DT4, End.DT6, End.DX4, End.DX6.
L2 Service SID, and End.DT6/4 or End.DX6/4 for the L3 Service SID.
6.3. Inclusive Multicast Ethernet Tag Route over SRv6 Core 6.3. Inclusive Multicast Ethernet Tag Route over SRv6 Core
EVPN Route Type 3 is used to advertise multicast traffic reachability EVPN Route Type 3 is used to advertise multicast traffic reachability
information through MP-BGP to all other PEs in a given EVPN instance. information through MP-BGP to all other PEs in a given EVPN instance.
As a reminder, EVPN Route Type 3 is encoded as follows: As a reminder, EVPN Route Type 3 is encoded as follows:
+---------------------------------------+ +---------------------------------------+
| RD (8 octets) | | RD (8 octets) |
skipping to change at page 20, line 32 skipping to change at page 20, line 32
the Function part of the SRv6 SID when ingress replication is used the Function part of the SRv6 SID when ingress replication is used
and the Transposition Scheme of encoding (Section 4) is used and and the Transposition Scheme of encoding (Section 4) is used and
otherwise, it is set as defined in [RFC6514]. When using the otherwise, it is set as defined in [RFC6514]. When using the
Transposition Scheme, the Transposition Length MUST be less than Transposition Scheme, the Transposition Length MUST be less than
or equal to 24 and less than or equal to the Function Length. or equal to 24 and less than or equal to the Function Length.
o Tunnel Identifier: IP address of egress PE o Tunnel Identifier: IP address of egress PE
A Service SID enclosed in an SRv6 L2 Service TLV within the BGP A Service SID enclosed in an SRv6 L2 Service TLV within the BGP
Prefix-SID attribute is advertised along with the route. The SRv6 Prefix-SID attribute is advertised along with the route. The SRv6
Endpoint behavior of the Service SID thus signaled, is entirely up to Endpoint behavior SHOULD be End.DT2M.
the originator of the advertisement. In practice, the SRv6 Endpoint
behavior of the SRv6 SID is as follows:
o End.DT2M behavior.
o When ESI-based filtering is used for Multi-Homing or E-Tree o When ESI-based filtering is used for Multi-Homing or E-Tree
procedures, the ESI Filtering Argument (the Arg.FE2 notation procedures, the ESI Filtering Argument (the Arg.FE2 notation
introduced in [RFC8986]) of the Service SID carried along with introduced in [RFC8986]) of the Service SID carried along with
EVPN Route Type 1 route SHOULD be merged with the applicable EVPN Route Type 1 route SHOULD be merged with the applicable
End.DT2M SID of Type 3 route advertised by remote PE by doing a End.DT2M SID of Type 3 route advertised by remote PE by doing a
bit-wise logical-OR operation to create a single SID on the bit-wise logical-OR operation to create a single SID on the
ingress PE. Details of split-horizon ESI-based filtering ingress PE. Details of split-horizon ESI-based filtering
mechanisms for multihoming are described in [RFC7432]. Details of mechanisms for multihoming are described in [RFC7432]. Details of
filtering mechanisms for Leaf-originated BUM traffic in EVPN filtering mechanisms for Leaf-originated BUM traffic in EVPN
skipping to change at page 22, line 35 skipping to change at page 22, line 35
o MPLS Label: This 24-bit field carries the whole or a portion of o MPLS Label: This 24-bit field carries the whole or a portion of
the Function part of the SRv6 SID when the Transposition Scheme of the Function part of the SRv6 SID when the Transposition Scheme of
encoding (Section 4) is used and otherwise set to Implicit NULL encoding (Section 4) is used and otherwise set to Implicit NULL
value. In either case, the value is set in the high order 20 bits value. In either case, the value is set in the high order 20 bits
(e.g., as 0x000030 in the case of Implicit NULL). When using the (e.g., as 0x000030 in the case of Implicit NULL). When using the
Transposition Scheme, the Transposition Length MUST be less than Transposition Scheme, the Transposition Length MUST be less than
or equal to 24 and less than or equal to the Function Length. or equal to 24 and less than or equal to the Function Length.
SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The SRv6 Service SID is encoded as part of the SRv6 L3 Service TLV. The
SRv6 Endpoint behavior of the SRv6 SID is entirely up to the SRv6 Endpoint behavior SHOULD be one of these: End.DT4, End.DT6,
originator of the advertisement. In practice, the SRv6 Endpoint End.DT46, End.DX4, End.DX6.
behavior is End.DT4/6 or End.DX4/6.
6.6. EVPN Multicast Routes (Route Types 6, 7, 8) over SRv6 Core 6.6. EVPN Multicast Routes (Route Types 6, 7, 8) over SRv6 Core
These routes do not require the advertisement of SRv6 Service TLVs These routes do not require the advertisement of SRv6 Service TLVs
along with them. Similar to EVPN Route Type 4, the BGP Nexthop is along with them. Similar to EVPN Route Type 4, the BGP Nexthop is
equal to the IPv6 address of egress PE. equal to the IPv6 address of egress PE.
7. Implementation Status 7. Implementation Status
[Note to RFC Editor: This section needs to be removed before [Note to RFC Editor: This section needs to be removed before
skipping to change at page 32, line 22 skipping to change at page 32, line 22
A. Sajassi, "IP Prefix Advertisement in Ethernet VPN A. Sajassi, "IP Prefix Advertisement in Ethernet VPN
(EVPN)", RFC 9136, DOI 10.17487/RFC9136, October 2021, (EVPN)", RFC 9136, DOI 10.17487/RFC9136, October 2021,
<https://www.rfc-editor.org/info/rfc9136>. <https://www.rfc-editor.org/info/rfc9136>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-idr-segment-routing-te-policy] [I-D.ietf-idr-segment-routing-te-policy]
Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P., Previdi, S., Filsfils, C., Talaulikar, K., Mattes, P.,
Jain, D., and S. Lin, "Advertising Segment Routing Jain, D., and S. Lin, "Advertising Segment Routing
Policies in BGP", draft-ietf-idr-segment-routing-te- Policies in BGP", draft-ietf-idr-segment-routing-te-
policy-14 (work in progress), November 2021. policy-16 (work in progress), March 2022.
[I-D.ietf-lsr-flex-algo] [I-D.ietf-lsr-flex-algo]
Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and Psenak, P., Hegde, S., Filsfils, C., Talaulikar, K., and
A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex- A. Gulko, "IGP Flexible Algorithm", draft-ietf-lsr-flex-
algo-18 (work in progress), October 2021. algo-18 (work in progress), October 2021.
[I-D.ietf-spring-segment-routing-policy] [I-D.ietf-spring-segment-routing-policy]
Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and Filsfils, C., Talaulikar, K., Voyer, D., Bogdanov, A., and
P. Mattes, "Segment Routing Policy Architecture", draft- P. Mattes, "Segment Routing Policy Architecture", draft-
ietf-spring-segment-routing-policy-18 (work in progress), ietf-spring-segment-routing-policy-21 (work in progress),
February 2022. March 2022.
[I-D.matsushima-spring-srv6-deployment-status] [I-D.matsushima-spring-srv6-deployment-status]
Matsushima, S., Filsfils, C., Ali, Z., Li, Z., Rajaraman, Matsushima, S., Filsfils, C., Ali, Z., Li, Z., Rajaraman,
K., and A. Dhamija, "SRv6 Implementation and Deployment K., and A. Dhamija, "SRv6 Implementation and Deployment
Status", draft-matsushima-spring-srv6-deployment-status-12 Status", draft-matsushima-spring-srv6-deployment-status-12
(work in progress), February 2022. (work in progress), February 2022.
[RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering: [RFC2827] Ferguson, P. and D. Senie, "Network Ingress Filtering:
Defeating Denial of Service Attacks which employ IP Source Defeating Denial of Service Attacks which employ IP Source
Address Spoofing", BCP 38, RFC 2827, DOI 10.17487/RFC2827, Address Spoofing", BCP 38, RFC 2827, DOI 10.17487/RFC2827,
 End of changes. 21 change blocks. 
47 lines changed or deleted 39 lines changed or added

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