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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2016-10-23
Replaced by draft-ietf-teas-pce-native-ip
Stream (None)
Intended RFC status (None)
Formats pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TEAS Working Group                                               A.Wang
Internet Draft                                            China Telecom
                                                           Quintin Zhao
                                                         Boris Khasanov
                                                    Huawei Technologies
                                                               Kevin Mi
                                                        Tencent Company
                                                     Raghavendra Mallya
                                                       Juniper Networks

Intended status: Standard Track                         October 24 2016
Expires: April 23, 2017

                         PCE in Native IP Network
                   draft-wang-teas-pce-native-ip-01.txt

Status of this Memo

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

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79. This document may not be modified,
   and derivative works of it may not be created, and it may not be
   published except as an Internet-Draft.

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79. This document may not be modified,
   and derivative works of it may not be created, except to publish it
   as an RFC and to translate it into languages other than English.

   it for publication as an RFC or to translate it into languages other
   than English.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

<A.Wang>                Expires April 23,2017                 [Page 1]
Internet-Draft        PCE in Native IP Network        October 24, 2016
   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html

   This Internet-Draft will expire on April 24, 2017.

Copyright Notice

   Copyright (c) 2016 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
   (http://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.

Abstract

   This document defines the scenario and solution for traffic
   engineering within Native IP network, using Dual/Multi-BGP session
   strategy and PCE-based central control architecture. The proposed
   central mode control solution conforms to the concept that defined
   in draft [I-D.draft-ietf-teas-pce-control-function], and together
   with draft [I-D.draft-zhao-teas-pcecc-use-cases], the solution
   portfolio for traffic engineering in MPLS and Native IP network is
   almost completed.

Table of Contents

   1. Introduction ....................................................3
   2. Conventions used in this document ...............................3
   3. Dual-BGP solution for simple topology.. .........................3
   4. Dual-BGP in large Scale Topology  ...............................5
   5. Multi-BGP for Extended Traffic Differentiation...................6
   6. SDN/PCE based solution for Multi-BGP strategy deployment.........7
   7. PCEP extension for key parameter transformation. ................8
   8. Deployment Consideration.............................................. 9
   9. Security Considerations ............................................10
   10. IANA Considerations............................................10
   11. Conclusions ...................................................10
   12. References ....................................................10
      12.1. Normative References .......................................10
      12.2. Informative References......................................11
   13. Acknowledgments ...............................................11

<A.Wang et.>           Expires April 23, 2017                 [Page 2]
Internet-Draft        PCE in Native IP Network        October 24, 2016
1. Introduction

   Currently, PCE based traffic assurance requires the underlying
   network devices support MPLS and the network must deploy multiple
Show full document text