PCE in Native IP Network
draft-ietf-teas-pce-native-ip-09

Document Type Active Internet-Draft (teas WG)
Last updated 2020-07-28 (latest revision 2020-06-07)
Replaces draft-wang-teas-pce-native-ip
Stream IETF
Intended RFC status Experimental
Formats plain text xml pdf htmlized (tools) htmlized bibtex
Reviews
Stream WG state Submitted to IESG for Publication
Document shepherd Lou Berger
Shepherd write-up Show (last changed 2020-06-07)
IESG IESG state Expert Review
Consensus Boilerplate Unknown
Telechat date
Responsible AD Deborah Brungard
Send notices to Lou Berger <lberger@labn.net>
TEAS Working Group                                               A. Wang
Internet-Draft                                             China Telecom
Intended status: Experimental                                B. Khasanov
Expires: December 10, 2020                           Huawei Technologies
                                                                 Q. Zhao
                                                        Etheric Networks
                                                                 H. Chen
                                                               Futurewei
                                                            June 8, 2020

                        PCE in Native IP Network
                    draft-ietf-teas-pce-native-ip-09

Abstract

   This document defines the framework for traffic engineering within
   native IP network, using multiple BGP sessions strategy and PCE
   -based central control architecture.  The procedures described in
   this document are experimental.  The experiment is intended to enable
   research for the usage of PCE in native IP scenarios.  For this
   purpose, this document describe the Central Control Dynamic Routing
   (CCDR) framework and the PCEP extension is specified in draft ietf-
   pce-pcep-extension-native-ip.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   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 December 10, 2020.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Wang, et al.            Expires December 10, 2020               [Page 1]
Internet-Draft          PCE in Native IP Network               June 2020

   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 Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  CCDR Framework in Simple Topology . . . . . . . . . . . . . .   4
   4.  CCDR Framework in Large Scale Topology  . . . . . . . . . . .   5
   5.  CCDR Multiple BGP Sessions Strategy . . . . . . . . . . . . .   6
   6.  PCEP Extension for Key Parameters Delivery  . . . . . . . . .   8
   7.  Deployment Consideration  . . . . . . . . . . . . . . . . . .   9
     7.1.  Scalability . . . . . . . . . . . . . . . . . . . . . . .   9
     7.2.  High Availability . . . . . . . . . . . . . . . . . . . .  10
     7.3.  Incremental deployment  . . . . . . . . . . . . . . . . .  10
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   10. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  11
   11. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     11.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     11.2.  Informative References . . . . . . . . . . . . . . . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   [RFC8735] describes the scenarios and simulation results for traffic
   engineering in the native IP network to provide End-to-End (E2E)
   performance assurance and QoS using PCE based central control,
   referred to as Centralized Control Dynamic Routing (CCDR).  Based on
   the various scenarios and analysis as per [RFC8735], the solution for
   traffic engineering in native IP network should have the following
   criteria:

   o  Support native IPv4 and IPv6 traffic simultaneously, no complex
      signaling procedures among network nodes like MPLS-TE and MPLS
      data plane.

   o  Same deployment guidline for intra-domain and inter-domain
      scenarios.

   o  Achieve End to End traffic assurance, determined QoS behavior.

Wang, et al.            Expires December 10, 2020               [Page 2]
Internet-Draft          PCE in Native IP Network               June 2020
Show full document text