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

Document Type Active Internet-Draft (teas WG)
Last updated 2018-06-27
Replaces draft-wang-teas-pce-native-ip
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf html 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: December 28, 2018                                   B. Khasanov
                                                                 H. Chen
                                                                   P. Mi
                                                     Huawei Technologies
                                                               R. Mallya
                                                        Juniper Networks
                                                                 S. Peng
                                                         ZTE Corporation
                                                           June 26, 2018

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

Abstract

   This document defines the framework for CCDR traffic engineering
   within Native IP network, using Dual/Multi-BGP session strategy and
   PCE-based central control architecture.  The proposed central mode
   control framework conforms to the concept that defined in [RFC8283].
   The scenario and simulation results of CCDR traffic engineering is
   described in draft [I-D.ietf-teas-native-ip-scenarios].

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 28, 2018.

Copyright Notice

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

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

   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.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Dual-BGP framework for simple topology  . . . . . . . . . . .   3
   4.  Dual-BGP in large Scale Topology  . . . . . . . . . . . . . .   4
   5.  Multi-BGP for Extended Traffic Differentiation  . . . . . . .   5
   6.  CCDR based framework for Multi-BGP strategy deployment  . . .   6
   7.  PCEP extension for key parameters delivery  . . . . . . . . .   7
   8.  Deployment Consideration  . . . . . . . . . . . . . . . . . .   7
     8.1.  Scalability . . . . . . . . . . . . . . . . . . . . . . .   8
     8.2.  High Availability . . . . . . . . . . . . . . . . . . . .   8
     8.3.  Incremental deployment  . . . . . . . . . . . . . . . . .   8
   9.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   11. Normative References  . . . . . . . . . . . . . . . . . . . .   9
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   Draft [I-D.ietf-teas-native-ip-scenarios] describes the scenario and
   simulation results for the CCDR traffic engineering.  In summary, the
   requirements for CCDR traffic engineering in Native IP network are
   the following:

   o  No complex MPLS signaling procedure.

   o  End to End traffic assurance, determined QoS behavior.

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

   o  No influence to existing router forward behavior.

   o  Can utilize the power of centrally control(PCE) and flexibility/
      robustness of distributed control protocol.

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

Wang, et al.            Expires December 28, 2018               [Page 2]
Internet-Draft          PCE in Native IP Network               June 2018

   o  Flexible deployment and automation control.

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