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

Document Type Active Internet-Draft (teas WG)
Last updated 2020-01-09
Replaces draft-wang-teas-pce-native-ip
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TEAS Working Group                                               A. Wang
Internet-Draft                                             China Telecom
Intended status: Experimental                                    Q. Zhao
Expires: July 13, 2020                                       B. Khasanov
                                                     Huawei Technologies
                                                                 H. Chen
                                                               Futurewei
                                                        January 10, 2020

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

Abstract

   This document defines the framework for traffic engineering within
   native IP network, using Dual/Multi-Border Gateway Protocol (BGP)
   sessions strategy and Path Computation Engine (PCE) -based central
   control architecture.

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 July 13, 2020.

Copyright Notice

   Copyright (c) 2020 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

Wang, et al.              Expires July 13, 2020                 [Page 1]
Internet-Draft          PCE in Native IP Network            January 2020

   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.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  CCDR Framework in Simple Topology . . . . . . . . . . . . . .   3
   5.  CCDR Framework in Large Scale Topology  . . . . . . . . . . .   5
   6.  CCDR Multi-BGP Strategy . . . . . . . . . . . . . . . . . . .   5
   7.  CCDR Framework for Multi-BGP Strategy . . . . . . . . . . . .   6
   8.  PCEP Extension for Key Parameters Delivery  . . . . . . . . .   7
   9.  Deployment Consideration  . . . . . . . . . . . . . . . . . .   8
     9.1.  Scalability . . . . . . . . . . . . . . . . . . . . . . .   8
     9.2.  High Availability . . . . . . . . . . . . . . . . . . . .   8
     9.3.  Incremental deployment  . . . . . . . . . . . . . . . . .   9
   10. Security Considerations . . . . . . . . . . . . . . . . . . .   9
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   12. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .   9
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  10
     13.2.  Informative References . . . . . . . . . . . . . . . . .  10
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Draft [I-D.ietf-teas-native-ip-scenarios] describes the scenarios and
   simulation results for traffic engineering in native IP network.  To
   meet the requirements of various scenarios, the solution for traffic
   engineering in native IP network should have the following criteria:

   o  No complex Multiprotocol Label Switching (MPLS) signaling
      procedures.

   o  End to End traffic assurance, determined Quality of Service (QoS)
      behavior.

   o  Same deployment method for intra-domain and inter-domain.

   o  No upgrade to forwarding behavior of the router.

   o  Can exploit the power of centrally control and flexibility/
      robustness of distributed control protocol.

   o  Coping with the differentiation requirements for large amount
      traffic and prefixes.

Wang, et al.              Expires July 13, 2020                 [Page 2]
Internet-Draft          PCE in Native IP Network            January 2020

   o  Flexible deployment and automation control.

   This document defines the framework for traffic engineering within
Show full document text