draft-ietf-teas-native-ip-scenarios-05.txt   draft-ietf-teas-native-ip-scenarios-06.txt 
TEAS Working Group A. Wang TEAS Working Group A. Wang
Internet-Draft China Telecom Internet-Draft China Telecom
Intended status: Informational X. Huang Intended status: Informational X. Huang
Expires: December 14, 2019 C. Kou Expires: January 2, 2020 C. Kou
BUPT BUPT
Z. Li Z. Li
China Mobile China Mobile
P. Mi P. Mi
Huawei Technologies Huawei Technologies
June 12, 2019 July 1, 2019
Scenarios and Simulation Results of PCE in Native IP Network Scenarios and Simulation Results of PCE in Native IP Network
draft-ietf-teas-native-ip-scenarios-05 draft-ietf-teas-native-ip-scenarios-06
Abstract Abstract
This document describes the scenarios, simulation and suggestions for This document describes the scenarios and simulation results for PCE
PCE in native IP network, which integrates the merit of distributed in native IP network, which integrates the merit of distributed
protocols (IGP/BGP), and the power of centrally control technologies protocols (IGP/BGP), and the power of centrally control technologies
(PCE/SDN) to provide one feasible traffic engineering solution in (PCE/SDN) to provide one feasible traffic engineering solution in
various complex scenarios for the service provider. various complex scenarios for the service provider.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 14, 2019. This Internet-Draft will expire on January 2, 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 2, line 45 skipping to change at page 2, line 45
Service provider network is composed thousands of routers that run Service provider network is composed thousands of routers that run
distributed protocol to exchange the reachability information between distributed protocol to exchange the reachability information between
them. The path for the destination network is mainly calculated and them. The path for the destination network is mainly calculated and
controlled by the IGP/BGP protocols. These distributed protocols are controlled by the IGP/BGP protocols. These distributed protocols are
robust enough to support the current evolution of Internet but have robust enough to support the current evolution of Internet but have
some difficulties when application requires the end-to-end QoS some difficulties when application requires the end-to-end QoS
performance, or in the situation that the service provider wants to performance, or in the situation that the service provider wants to
maximize the link utilization within their network. maximize the link utilization within their network.
MPLS-TE technology is one solution for finely planned network but it MPLS-TE technology [RFC3209]is one solution for finely planned
will put heavy burden on the routers when we use it to meet the network but it will put heavy burden on the routers when we use it to
dynamic QoS assurance requirements within real time traffic network. meet the dynamic QoS assurance requirements within real time traffic
network.
SR(Segment Routing) is another solution that integrates some merits SR(Segment Routing) [RFC8402] is another solution that integrates
of distributed protocol and the advantages of centrally control mode, some merits of distributed protocol and the advantages of centrally
but it requires the underlying network, especially the provider edge control mode, but it requires the underlying network, especially the
router to do label push and pop action in-depth, and need complex provider edge router to do label push and pop action in-depth, and
mechanic for coexisting with the Non-SR network. Additionally, it need complex mechanic for coexisting with the Non-SR network.
can only maneuver the end-to-end path for MPLS and IPv6 traffic via Additionally, it can only maneuver the end-to-end path for MPLS and
different mechanisms. IPv6 traffic via different mechanisms.
DetNet[RFC8578] describes use cases for diverse industries that have DetNet[RFC8578] describes use cases for diverse industries that have
in common a need for "deterministic flows", which can provide a common need for "deterministic flows", which can provide guaranteed
guaranteed bandwidth, bounded latency, and other properties germane bandwidth, bounded latency, and other properties germane to the
to the transport of time-sensitive data. The use cases focus mainly transport of time-sensitive data. The use cases focus mainly on the
on the industrial critical applications within one centrally industrial critical applications within one centrally controlled
controlled network and are out of scope of this draft. network and are out of scope of this draft.
This draft describes scenarios that the centrally control dynamic This draft describes scenarios that the centrally control dynamic
routing (CCDR) framework can easily solve, without the change of the routing (CCDR) framework can easily solve, without the change of the
data plane behaviour on the router. It also gives the path data plane behaviour on the router. It also gives the path
optimization simulation results to illustrate the applicability of optimization simulation results to illustrate the applicability of
CCDR framework. CCDR framework.
2. CCDR Scenarios. 2. CCDR Scenarios.
The following sections describe some scenarios that the CCDR The following sections describe some scenarios that the CCDR
framework is suitable for deployment. framework is suitable for deployment.
2.1. QoS Assurance for Hybrid Cloud-based Application. 2.1. QoS Assurance for Hybrid Cloud-based Application.
With the emerge of cloud computing technologies, enterprises are With the emerge of cloud computing technologies, enterprises are
putting more and more services on the public oriented cloud putting more and more services on the public oriented cloud
environment, but keep core business within their private cloud. The environment, but keep core business within their private cloud. The
communication between the private and public cloud will span the WAN communication between the private and public cloud sites will span
network. The bandwidth requirements between them are variable and the WAN network. The bandwidth requirements between them are
the background traffic between these two sites changes from time to variable and the background traffic between these two sites changes
time. Enterprise applications just want to exploit the network from time to time. Enterprise applications just want to exploit the
capabilities to assure the end-to-end QoS performance on demand. network capabilities to assure the end-to-end QoS performance on
demand.
CCDR, which integrates the merits of distributed protocol and the CCDR, which integrates the merits of distributed protocol and the
power of centrally control, is suitable for this scenario. The power of centrally control, is suitable for this scenario. The
possible solution framework is illustrated below: possible solution framework is illustrated below:
+------------------------+ +------------------------+
| Cloud Based Application| | Cloud Based Application|
+------------------------+ +------------------------+
| |
+-----------+ +-----------+
skipping to change at page 12, line 13 skipping to change at page 12, line 13
<https://www.rfc-editor.org/info/rfc5440>. <https://www.rfc-editor.org/info/rfc5440>.
[RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody, [RFC8253] Lopez, D., Gonzalez de Dios, O., Wu, Q., and D. Dhody,
"PCEPS: Usage of TLS to Provide a Secure Transport for the "PCEPS: Usage of TLS to Provide a Secure Transport for the
Path Computation Element Communication Protocol (PCEP)", Path Computation Element Communication Protocol (PCEP)",
RFC 8253, DOI 10.17487/RFC8253, October 2017, RFC 8253, DOI 10.17487/RFC8253, October 2017,
<https://www.rfc-editor.org/info/rfc8253>. <https://www.rfc-editor.org/info/rfc8253>.
9.2. Informative References 9.2. Informative References
[RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., Srinivasan, V.,
and G. Swallow, "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, DOI 10.17487/RFC3209, December 2001,
<https://www.rfc-editor.org/info/rfc3209>.
[RFC8402] Filsfils, C., Ed., Previdi, S., Ed., Ginsberg, L.,
Decraene, B., Litkowski, S., and R. Shakir, "Segment
Routing Architecture", RFC 8402, DOI 10.17487/RFC8402,
July 2018, <https://www.rfc-editor.org/info/rfc8402>.
[RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases", [RFC8578] Grossman, E., Ed., "Deterministic Networking Use Cases",
RFC 8578, DOI 10.17487/RFC8578, May 2019, RFC 8578, DOI 10.17487/RFC8578, May 2019,
<https://www.rfc-editor.org/info/rfc8578>. <https://www.rfc-editor.org/info/rfc8578>.
Authors' Addresses Authors' Addresses
Aijun Wang Aijun Wang
China Telecom China Telecom
Beiqijia Town, Changping District Beiqijia Town, Changping District
Beijing, Beijing 102209 Beijing, Beijing 102209
 End of changes. 10 change blocks. 
26 lines changed or deleted 38 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/