< draft-dawra-bess-srv6-services-01.txt   draft-dawra-bess-srv6-services-02.txt >
BESS Working Group BESS Working Group
Internet-Draft Internet-Draft
Intended status: Standards Track G. Dawra, Ed. Intended status: Standards Track G. Dawra, Ed.
Expires: January 4, 2020 LinkedIn Expires: January 9, 2020 LinkedIn
C. Filsfils C. Filsfils
P. Brissette P. Brissette
S. Agrawal S. Agrawal
Cisco Systems Cisco Systems
J. Leddy J. Leddy
Comcast Comcast
D. Voyer D. Voyer
D. Bernier D. Bernier
Bell Canada Bell Canada
D. Steinberg D. Steinberg
skipping to change at page 1, line 28 skipping to change at page 1, line 28
R. Raszuk R. Raszuk
Bloomberg LP Bloomberg LP
B. Decraene B. Decraene
Orange Orange
S. Matsushima S. Matsushima
SoftBank SoftBank
S. Zhuang S. Zhuang
Huawei Technologies Huawei Technologies
J. Rabadan J. Rabadan
Nokia Nokia
July 3, 2019 July 8, 2019
SRv6 BGP based Overlay services SRv6 BGP based Overlay services
draft-dawra-bess-srv6-services-01 draft-dawra-bess-srv6-services-02
Abstract Abstract
This draft defines procedures and messages for SRv6-based BGP This draft 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".
Requirements Language Requirements Language
skipping to change at page 2, line 20 skipping to change at page 2, line 20
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 January 4, 2020. This Internet-Draft will expire on January 9, 2020.
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 9, line 24 skipping to change at page 9, line 24
BGP ingress nodes (ingress PEs) receive these advertisements and may BGP ingress nodes (ingress PEs) receive these advertisements and may
add the prefix to the RIB in an appropriate VRF. add the prefix to the RIB in an appropriate VRF.
Egress PEs which supports SRv6 based L3 services advertises overlay Egress PEs which supports SRv6 based L3 services advertises overlay
service prefixes along with a Service SID enclosed in a SRv6 L3 service prefixes along with a Service SID enclosed in a SRv6 L3
Service TLV within the BGP Prefix-SID Attribute. This TLV serves two Service TLV within the BGP Prefix-SID Attribute. This TLV serves two
purposes - first, it indicates that the egress PE is reachable via an purposes - first, it indicates that the egress PE is reachable via an
SRv6 underlay and the BGP ingress PE receiving this route MUST choose SRv6 underlay and the BGP ingress PE receiving this route MUST choose
to perform IPv6 encapsulation and optionally insert an SRH when to perform IPv6 encapsulation and optionally insert an SRH when
required; second ,it indicates the value of the Service SID to be required; second ,it indicates the value of the Service SID to be
used in the in the SRH encapsulation. used in the encapsulation.
The Service SID thus signaled only has local significance at the The Service SID thus signaled only has local significance at the
egress PE, where it may be allocated or configured on a per-CE or egress PE, where it may be allocated or configured on a per-CE or
per-VRF basis. In practice, the SID may encode a cross-connect to a per-VRF basis. In practice, the SID may encode a cross-connect to a
specific Address Family table (END.DT) or next-hop/interface (END.DX) specific Address Family table (END.DT) or next-hop/interface (END.DX)
as defined in [I-D.ietf-spring-srv6-network-programming]. as defined in [I-D.ietf-spring-srv6-network-programming].
The SRv6 Service SID SHOULD be routable within the AS of the egress The SRv6 Service SID SHOULD be routable within the AS of the egress
PE and serves the dual purpose of providing reachability between PE and serves the dual purpose of providing reachability between
ingress PE and egress PE while also encoding the endpoint behavior. ingress PE and egress PE while also encoding the endpoint behavior.
skipping to change at page 24, line 44 skipping to change at page 24, line 44
bess-evpn-prefix-advertisement-11 (work in progress), May bess-evpn-prefix-advertisement-11 (work in progress), May
2018. 2018.
[I-D.ietf-idr-bgp-prefix-sid] [I-D.ietf-idr-bgp-prefix-sid]
Previdi, S., Filsfils, C., Lindem, A., Sreekantiah, A., Previdi, S., Filsfils, C., Lindem, A., Sreekantiah, A.,
and H. Gredler, "Segment Routing Prefix SID extensions for and H. Gredler, "Segment Routing Prefix SID extensions for
BGP", draft-ietf-idr-bgp-prefix-sid-27 (work in progress), BGP", draft-ietf-idr-bgp-prefix-sid-27 (work in progress),
June 2018. June 2018.
[I-D.ietf-idr-segment-routing-te-policy] [I-D.ietf-idr-segment-routing-te-policy]
Previdi, S., Filsfils, C., Jain, D., Mattes, P., Rosen, Previdi, S., Filsfils, C., Mattes, P., Rosen, E., Jain,
E., and S. Lin, "Advertising Segment Routing Policies in D., and S. Lin, "Advertising Segment Routing Policies in
BGP", draft-ietf-idr-segment-routing-te-policy-06 (work in BGP", draft-ietf-idr-segment-routing-te-policy-07 (work in
progress), May 2019. progress), July 2019.
[I-D.ietf-isis-segment-routing-extensions] [I-D.ietf-isis-segment-routing-extensions]
Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A., Previdi, S., Ginsberg, L., Filsfils, C., Bashandy, A.,
Gredler, H., and B. Decraene, "IS-IS Extensions for Gredler, H., and B. Decraene, "IS-IS Extensions for
Segment Routing", draft-ietf-isis-segment-routing- Segment Routing", draft-ietf-isis-segment-routing-
extensions-25 (work in progress), May 2019. extensions-25 (work in progress), May 2019.
[I-D.matsushima-spring-srv6-deployment-status] [I-D.matsushima-spring-srv6-deployment-status]
Matsushima, S., Filsfils, C., Ali, Z., and Z. Li, "SRv6 Matsushima, S., Filsfils, C., Ali, Z., and Z. Li, "SRv6
Implementation and Deployment Status", draft-matsushima- Implementation and Deployment Status", draft-matsushima-
skipping to change at page 27, line 32 skipping to change at page 27, line 32
Swadesh Agrawal Swadesh Agrawal
Cisco Systems Cisco Systems
USA USA
Email: swaagraw@cisco.com Email: swaagraw@cisco.com
Jonn Leddy Jonn Leddy
Comcast Comcast
USA USA
Email: john_leddy@cable.comcast.com
Daniel Voyer Daniel Voyer
Bell Canada Bell Canada
Canada Canada
Email: daniel.voyer@bell.ca Email: daniel.voyer@bell.ca
Daniel Bernier Daniel Bernier
Bell Canada Bell Canada
Canada Canada
 End of changes. 7 change blocks. 
11 lines changed or deleted 9 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/