draft-ietf-teas-pce-native-ip-05.txt   draft-ietf-teas-pce-native-ip-06.txt 
TEAS Working Group A. Wang TEAS Working Group A. Wang
Internet-Draft China Telecom Internet-Draft China Telecom
Intended status: Experimental Q. Zhao Intended status: Experimental Q. Zhao
Expires: July 13, 2020 B. Khasanov Expires: November 15, 2020 Etheric Networks
B. Khasanov
Huawei Technologies Huawei Technologies
H. Chen H. Chen
Futurewei Futurewei
January 10, 2020 May 14, 2020
PCE in Native IP Network PCE in Native IP Network
draft-ietf-teas-pce-native-ip-05 draft-ietf-teas-pce-native-ip-06
Abstract Abstract
This document defines the framework for traffic engineering within This document defines the framework for traffic engineering within
native IP network, using Dual/Multi-Border Gateway Protocol (BGP) native IP network, using Dual/Multi-Border Gateway Protocol (BGP)
sessions strategy and Path Computation Engine (PCE) -based central sessions strategy and Path Computation Engine (PCE) -based central
control architecture. control architecture.
Status of This Memo Status of This Memo
skipping to change at page 1, line 37 skipping to change at page 1, line 38
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 July 13, 2020. This Internet-Draft will expire on November 15, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 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 32 skipping to change at page 2, line 33
10. Security Considerations . . . . . . . . . . . . . . . . . . . 9 10. Security Considerations . . . . . . . . . . . . . . . . . . . 9
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
12. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 9 12. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 9
13. References . . . . . . . . . . . . . . . . . . . . . . . . . 9 13. References . . . . . . . . . . . . . . . . . . . . . . . . . 9
13.1. Normative References . . . . . . . . . . . . . . . . . . 10 13.1. Normative References . . . . . . . . . . . . . . . . . . 10
13.2. Informative References . . . . . . . . . . . . . . . . . 10 13.2. Informative References . . . . . . . . . . . . . . . . . 10
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction 1. Introduction
Draft [I-D.ietf-teas-native-ip-scenarios] describes the scenarios and Draft [RFC8735] describes the scenarios and simulation results for
simulation results for traffic engineering in native IP network. To traffic engineering in native IP network. To meet the requirements
meet the requirements of various scenarios, the solution for traffic of various scenarios, the solution for traffic engineering in native
engineering in native IP network should have the following criteria: IP network should have the following criteria:
o No complex Multiprotocol Label Switching (MPLS) signaling o No complex Multiprotocol Label Switching (MPLS) signaling
procedures. procedures.
o End to End traffic assurance, determined Quality of Service (QoS) o End to End traffic assurance, determined Quality of Service (QoS)
behavior. behavior.
o Same deployment method for intra-domain and inter-domain. o Same deployment method for intra-domain and inter-domain.
o No upgrade to forwarding behavior of the router. o No upgrade to forwarding behavior of the router.
skipping to change at page 3, line 27 skipping to change at page 3, line 30
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119] . document are to be interpreted as described in RFC 2119 [RFC2119] .
3. Terminology 3. Terminology
This document uses the following terms defined in [RFC5440]: PCE, This document uses the following terms defined in [RFC5440]: PCE,
PCEP PCEP
The following terms are defined in this document: The following terms are used in this document:
o CCDR: Central Control Dynamic Routing o CCDR: Central Control Dynamic Routing
o E2E: End to End o E2E: End to End
o ECMP: Equal Cost Multi Path o ECMP: Equal Cost Multi Path
o QoS: Quality of Service o QoS: Quality of Service
o RR: Route Reflector o RR: Route Reflector
skipping to change at page 10, line 22 skipping to change at page 10, line 22
Element (PCE) Communication Protocol (PCEP)", RFC 5440, Element (PCE) Communication Protocol (PCEP)", RFC 5440,
DOI 10.17487/RFC5440, March 2009, DOI 10.17487/RFC5440, March 2009,
<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>.
[RFC8735] Wang, A., Huang, X., Kou, C., Li, Z., and P. Mi,
"Scenarios and Simulation Results of PCE in a Native IP
Network", RFC 8735, DOI 10.17487/RFC8735, February 2020,
<https://www.rfc-editor.org/info/rfc8735>.
13.2. Informative References 13.2. Informative References
[I-D.ietf-pce-pcep-extension-native-ip] [I-D.ietf-pce-pcep-extension-native-ip]
Wang, A., Khasanov, B., Cheruathur, S., Zhu, C., and S. Wang, A., Khasanov, B., Fang, S., and C. Zhu, "PCEP
Fang, "PCEP Extension for Native IP Network", draft-ietf- Extension for Native IP Network", draft-ietf-pce-pcep-
pce-pcep-extension-native-ip-04 (work in progress), August extension-native-ip-05 (work in progress), February 2020.
2019.
[I-D.ietf-teas-native-ip-scenarios]
Wang, A., Huang, X., Qou, C., Li, Z., and P. Mi,
"Scenarios and Simulation Results of PCE in Native IP
Network", draft-ietf-teas-native-ip-scenarios-12 (work in
progress), October 2019.
Authors' Addresses Authors' Addresses
Aijun Wang Aijun Wang
China Telecom China Telecom
Beiqijia Town, Changping District Beiqijia Town, Changping District
Beijing 102209 Beijing 102209
China China
Email: wangaj3@chinatelecom.cn Email: wangaj3@chinatelecom.cn
skipping to change at page 11, line 4 skipping to change at page 10, line 43
Authors' Addresses Authors' Addresses
Aijun Wang Aijun Wang
China Telecom China Telecom
Beiqijia Town, Changping District Beiqijia Town, Changping District
Beijing 102209 Beijing 102209
China China
Email: wangaj3@chinatelecom.cn Email: wangaj3@chinatelecom.cn
Quintin Zhao Quintin Zhao
Huawei Technologies Etheric Networks
125 Nagog Technology Park 1009 S CLAREMONT ST
Acton, MA 01719 SAN MATEO, CA 94402
USA USA
Email: quintin.zhao@huawei.com Email: qzhao@ethericnetworks.com
Boris Khasanov Boris Khasanov
Huawei Technologies Huawei Technologies
Moskovskiy Prospekt 97A Moskovskiy Prospekt 97A
St.Petersburg 196084 St.Petersburg 196084
Russia Russia
Email: khasanov.boris@huawei.com Email: khasanov.boris@huawei.com
Huaimo Chen Huaimo Chen
Futurewei Futurewei
 End of changes. 11 change blocks. 
24 lines changed or deleted 23 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/