< draft-dukes-spring-sr-for-sdwan-02.txt   draft-dukes-spring-sr-for-sdwan-03.txt >
Network Working Group D. Dukes, Ed. Network Working Group D. Dukes, Ed.
Internet-Draft C. Filsfils Internet-Draft C. Filsfils
Intended status: Standards Track Cisco Systems Intended status: Standards Track Cisco Systems
Expires: December 12, 2019 G. Dawra Expires: August 26, 2021 G. Dawra
LinkedIn LinkedIn
X. Xu X. Xu
Alibaba Alibaba
D. Voyer D. Voyer
Bell Canada Bell Canada
P. Camarillo P. Camarillo
F. Clad F. Clad
Cisco Systems Cisco Systems
S. Salsano S. Salsano
Univ. of Rome Tor Vergata Univ. of Rome Tor Vergata
June 10, 2019 February 22, 2021
SR For SDWAN: VPN with Underlay SLA SR For SDWAN: VPN with Underlay SLA
draft-dukes-spring-sr-for-sdwan-02 draft-dukes-spring-sr-for-sdwan-03
Abstract Abstract
This document describes how SR enables underlay Service Level This document describes how SR enables underlay Service Level
Agreements (SLA) to a VPN with scale and security while ensuring Agreements (SLA) to a VPN with scale and security while ensuring
service opacity. This solution applies to Over-The-Top VPN (OTT VPN) service opacity. This solution applies to Over-The-Top VPN (OTT VPN)
and Software-Defined WAN (SDWAN). and Software-Defined WAN (SDWAN).
Status of This Memo Status of This Memo
skipping to change at page 1, line 44 skipping to change at page 1, line 44
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 December 12, 2019. This Internet-Draft will expire on August 26, 2021.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2021 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 3, line 22 skipping to change at page 3, line 22
The body of this text uses SRv6 for illustration. A similar solution The body of this text uses SRv6 for illustration. A similar solution
leveraging SR-MPLS is illustrated in an appendix. leveraging SR-MPLS is illustrated in an appendix.
This document assumes familiarity with the following IETF documents: This document assumes familiarity with the following IETF documents:
o Segment Routing Architecture [I-D.ietf-spring-segment-routing] o Segment Routing Architecture [I-D.ietf-spring-segment-routing]
o Segment Routing with MPLS data plane o Segment Routing with MPLS data plane
[I-D.ietf-spring-segment-routing-mpls] [I-D.ietf-spring-segment-routing-mpls]
o IPv6 Segment Routing Header [I-D.ietf-6man-segment-routing-header] o IPv6 Segment Routing Header [RFC8754]
o SRv6 Network Programming o SRv6 Network Programming
[I-D.filsfils-spring-srv6-network-programming] [I-D.filsfils-spring-srv6-network-programming]
o Segment Routing Policy For Traffic Engineering o Segment Routing Policy For Traffic Engineering
[I-D.filsfils-spring-segment-routing-policy] [I-D.filsfils-spring-segment-routing-policy]
o IS-IS Extensions to Support Segment Routing over IPv6 Dataplane o IS-IS Extensions to Support Segment Routing over IPv6 Dataplane
[I-D.bashandy-isis-srv6-extensions] [I-D.bashandy-isis-srv6-extensions]
skipping to change at page 16, line 20 skipping to change at page 16, line 20
[I-D.filsfils-spring-segment-routing-policy] [I-D.filsfils-spring-segment-routing-policy]
Filsfils, C., Sivabalan, S., Hegde, S., Filsfils, C., Sivabalan, S., Hegde, S.,
daniel.voyer@bell.ca, d., Lin, S., bogdanov@google.com, daniel.voyer@bell.ca, d., Lin, S., bogdanov@google.com,
b., Krol, P., Horneffer, M., Steinberg, D., Decraene, B., b., Krol, P., Horneffer, M., Steinberg, D., Decraene, B.,
Litkowski, S., Mattes, P., Ali, Z., Talaulikar, K., Liste, Litkowski, S., Mattes, P., Ali, Z., Talaulikar, K., Liste,
J., Clad, F., and K. Raza, "Segment Routing Policy J., Clad, F., and K. Raza, "Segment Routing Policy
Architecture", draft-filsfils-spring-segment-routing- Architecture", draft-filsfils-spring-segment-routing-
policy-06 (work in progress), May 2018. policy-06 (work in progress), May 2018.
[I-D.ietf-6man-segment-routing-header]
Filsfils, C., Dukes, D., Previdi, S., Leddy, J.,
Matsushima, S., and d. daniel.voyer@bell.ca, "IPv6 Segment
Routing Header (SRH)", draft-ietf-6man-segment-routing-
header-19 (work in progress), May 2019.
[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., Talaulikar, K., Mattes, P.,
E., and S. Lin, "Advertising Segment Routing Policies in Rosen, E., Jain, D., and S. Lin, "Advertising Segment
BGP", draft-ietf-idr-segment-routing-te-policy-06 (work in Routing Policies in BGP", draft-ietf-idr-segment-routing-
progress), May 2019. te-policy-11 (work in progress), November 2020.
[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.ietf-spring-segment-routing] [I-D.ietf-spring-segment-routing]
Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B.,
Litkowski, S., and R. Shakir, "Segment Routing Litkowski, S., and R. Shakir, "Segment Routing
skipping to change at page 17, line 46 skipping to change at page 17, line 40
"Encapsulating MPLS in UDP", RFC 7510, "Encapsulating MPLS in UDP", RFC 7510,
DOI 10.17487/RFC7510, April 2015, DOI 10.17487/RFC7510, April 2015,
<https://www.rfc-editor.org/info/rfc7510>. <https://www.rfc-editor.org/info/rfc7510>.
[RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and [RFC7752] Gredler, H., Ed., Medved, J., Previdi, S., Farrel, A., and
S. Ray, "North-Bound Distribution of Link-State and S. Ray, "North-Bound Distribution of Link-State and
Traffic Engineering (TE) Information Using BGP", RFC 7752, Traffic Engineering (TE) Information Using BGP", RFC 7752,
DOI 10.17487/RFC7752, March 2016, DOI 10.17487/RFC7752, March 2016,
<https://www.rfc-editor.org/info/rfc7752>. <https://www.rfc-editor.org/info/rfc7752>.
[RFC8754] Filsfils, C., Ed., Dukes, D., Ed., Previdi, S., Leddy, J.,
Matsushima, S., and D. Voyer, "IPv6 Segment Routing Header
(SRH)", RFC 8754, DOI 10.17487/RFC8754, March 2020,
<https://www.rfc-editor.org/info/rfc8754>.
10.2. Normative References 10.2. Normative References
[I-D.filsfils-spring-srv6-network-programming] [I-D.filsfils-spring-srv6-network-programming]
Filsfils, C., Camarillo, P., Leddy, J., Filsfils, C., Camarillo, P., Leddy, J.,
daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6 daniel.voyer@bell.ca, d., Matsushima, S., and Z. Li, "SRv6
Network Programming", draft-filsfils-spring-srv6-network- Network Programming", draft-filsfils-spring-srv6-network-
programming-07 (work in progress), February 2019. programming-07 (work in progress), February 2019.
Authors' Addresses Authors' Addresses
skipping to change at page 18, line 42 skipping to change at page 19, line 4
Bell Canada Bell Canada
Canada Canada
Email: daniel.voyer@bell.ca Email: daniel.voyer@bell.ca
Pablo Camarillo Garvia Pablo Camarillo Garvia
Cisco Systems Cisco Systems
Spain Spain
Email: pcamaril@cisco.com Email: pcamaril@cisco.com
Francois Clad Francois Clad
Cisco Systems Cisco Systems
France France
Email: fclad@cisco.com
Stefano Salsano Stefano Salsano
Univ. of Rome Tor Vergata Univ. of Rome Tor Vergata
Italy Italy
Email: stefano.salsano@uniroma2.it Email: stefano.salsano@uniroma2.it
 End of changes. 11 change blocks. 
17 lines changed or deleted 18 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/