SRv6 Deployment and Operation Problem Summary
draft-liu-srv6ops-problem-summary-02
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Yisong Liu , Daniel Voyer , Thomas Graf , Zoltan Miklos , Luis M. Contreras , Nicolai Leymann , Linjian Song , Satoru Matsushima , Chongfeng Xie , Xinxin Yi , Weiqiang Cheng | ||
| Last updated | 2024-03-19 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-liu-srv6ops-problem-summary-02
Network Working Group Y. Liu
Internet-Draft China Mobile
Intended status: Experimental D. Voyer
Expires: 21 September 2024 Bell Canada
T. Graf
Swisscom
Z. Miklos
MTN
L. Contreras
Telefonica
N. Leymann
Deutsche Telekom
L. Song
Alibaba, Inc
S. Matsushima
SoftBank
C. Xie
China Telecom
X. Yi
China Unicom
W. Cheng
China Mobile
20 March 2024
SRv6 Deployment and Operation Problem Summary
draft-liu-srv6ops-problem-summary-02
Abstract
This document aims to provide a concise overview of the common
problems encountered during SRv6 deployment and operation, which
provides foundations for further work, including for example of
potential solutions and best practices to navigate deployment.
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.
Liu, et al. Expires 21 September 2024 [Page 1]
Internet-Draft Abbreviated-Title March 2024
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 21 September 2024.
Copyright Notice
Copyright (c) 2024 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 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 Revised BSD License text as
described in Section 4.e of the Trust Legal Provisions and are
provided without warranty as described in the Revised BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Simplified Inter-domain Implementation . . . . . . . . . . . 3
3. SRv6 Data Plane Visualization . . . . . . . . . . . . . . . . 4
3.1. Leveraging Existing Frameworks with new parameters . . . 4
3.2. Optimizing Network Analysis and Performance . . . . . . . 4
4. IPv6 Address Assignment for SRv6 . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. References . . . . . . . . . . . . . . . . . . . . . . . 5
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 5
Liu, et al. Expires 21 September 2024 [Page 2]
Internet-Draft Abbreviated-Title March 2024
1. Introduction
Segment Routing over IPv6 (SRv6) is a new technology that builds upon
the existing IPv6 infrastructure to offer programmable data plane
capabilities. This allows for more granular control over traffic
forwarding, enabling flexible and scalable network designs. While
SRv6 presents numerous potential benefits, such as improved traffic
engineering, optimized resource utilization, its deployment and
operation come with certain challenges. This document aims to
provide a concise overview of the common problems encountered during
SRv6 deployment and operation, which provides foundations for further
work, including for example potential solutions and best practices to
navigate deployment . By understanding these challenges and exploring
mitigation strategies, network administrators can make informed
decisions when implementing and managing SRv6 networks.
This document identifies a number of Deployment and Operation
Problems (DOPs) that require additional work within IETF.
2. Simplified Inter-domain Implementation
While traditional inter-domain implementations in service provider
networks often rely on MPLS and leverage Option A. Option A has
scalability limitations and is complex to deploy and maintain. The
ASBR needs to manage the routing of all VPNs and create VPN instances
for each VPN. At the same time, it requests associating separate
interfaces and corresponding VLANs for each inter-domain VPN. SRv6
presents an alternative approach with E2E inter-domain solution,
potentially leading to simplification and improved scalability from
the following 2 aspects: 1) SRv6naturally support end-to-end inter-
domain by utilizing IPv6 route reachability; 2) IPv6 route
aggregation reduces the number of SRv6 locators distribution for
inter-domain deployment. However it requests further work to deal
with the challenges of SRv6 inter-domain deployments including:
DOP-1 How to deploy SRv6 inter-domain in the existing MPLS network,
which requires consideration of existing mechanism and potential
migration strategies.
DOP-2 Utilizing SRv6 compression techniques in inter-domain scenario
to further optimize bandwidth usage, which requires effective IPv6
address planning and block allocation strategies to achieve optimal
aggregation benefits.
Also, protocol extension is out of scope and only implementation
experience is considered to deal with these challenges.
Liu, et al. Expires 21 September 2024 [Page 3]
Internet-Draft Abbreviated-Title March 2024
3. SRv6 Data Plane Visualization
Network visualization is a critical aspect for service providers,
especially when implementing new technologies like SRv6. It provides
essential insights into network traffic flow, resource utilization,
and potential performance bottlenecks. Visualizing the SRv6 data
plane requests further work in the aspects described next.
3.1. Leveraging Existing Frameworks with new parameters
The existing IETF work on data collection formats can be leveraged
for SRv6 data plane visualization. Further work is necessary to
define SRv6-specific customization information; For example:
DOP-3 Reuse Telemetry Framework: The telemetry framework, used for
collecting and transmitting network telemetry data, offers a solid
foundation. While specific content and parameters need to be defined
to capture SRv6-specific information relevant for visualization.
DOP-4 Reuse Netconf/Yang Framework: SRPING already defines the Yang
Model for protocol extension; for better operation and maintenance of
SRv6 network, the Yang Model for information collection, status
notification, failure handling and recovery may also be required.
3.2. Optimizing Network Analysis and Performance
Once data is collected from network devices using the defined format,
several techniques can be employed to utilize this information for
network analysis and performance optimization for SRv6, especially
traffic engineering. This brings the need for:
DOP-5 Identification of techniques for performance optimization in
operational scenarios.
4. IPv6 Address Assignment for SRv6
Existing IPv6 address planning approach ensures efficient address
utilization and simplifies network management for IPv6 netowrk, which
can't satisfy the SRv6 SID planning for service provider, especially
considering the complexities introduced by advanced features like
SRv6 compression. Further work is requested including: SRv6 SID
Block Assignment, SRv6 SID Assignment for P2P and P2MP, SRv6 Node ID
Assignment, SRv6 Function ID Assignment and so on. Some initial work
could refer to [I-D.liu-srv6ops-sid-address-assignment]. In summary:
DOP-6 Efficient assignment of addresses and identifiers.
Liu, et al. Expires 21 September 2024 [Page 4]
Internet-Draft Abbreviated-Title March 2024
5. IANA Considerations
This document makes no request of IANA.
Note to RFC Editor: this section may be removed on publication as an
RFC.
6. Security Considerations
7. Acknowledgements
8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
8.2. References
[I-D.liu-srv6ops-sid-address-assignment]
Liu, Y. and Y. Zhu, "IPv6 Address Assignment for SRv6",
Work in Progress, Internet-Draft, draft-liu-srv6ops-sid-
address-assignment-00, 7 February 2024,
<https://datatracker.ietf.org/doc/html/draft-liu-srv6ops-
sid-address-assignment-00>.
Authors' Addresses
Yisong Liu
China Mobile
China
Email: liuyisong@chinamobile.com
Daniel Voyer
Bell Canada
Email: daniel.voyer@bell.ca
Thomas Graf
Swisscom
Email: Thomas.Graf@swisscom.com
Liu, et al. Expires 21 September 2024 [Page 5]
Internet-Draft Abbreviated-Title March 2024
Zoltan Miklos
MTN
Email: Zoltan.Miklos@mtn.com
Luis Contreras
Telefonica
Email: luismiguel.contrerasmurillo@telefonica.com
Nicolai Leymann
Deutsche Telekom
Email: N.Leymann@telekom.de
Linjian Song
Alibaba, Inc
Email: linjian.slj@alibaba-inc.com
Satoru Matsushima
SoftBank
Email: satoru.matsushima@g.softbank.co.jp
Chongfeng Xie
China Telecom
Email: xiechf@chinatelecom.cn
Xinxin Yi
China Unicom
Email: yixx3@chinaunicom.cn
Weiqiang Cheng
China Mobile
Email: chengweiqiang@chinamobile.com
Liu, et al. Expires 21 September 2024 [Page 6]