PCEP Extension for Native IP Network
draft-ietf-pce-pcep-extension-native-ip-07

The information below is for an old version of the document
Document Type Active Internet-Draft (pce WG)
Authors Aijun Wang  , Boris Khasanov  , Sheng Fang  , Ren Tan  , Chun Zhu 
Last updated 2020-09-10
Replaces draft-wang-pce-pcep-extension-native-ip
Stream IETF
Intended RFC status (None)
Formats pdf htmlized (tools) 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)
PCE Working Group                                                A. Wang
Internet-Draft                                             China Telecom
Intended status: Standards Track                             B. Khasanov
Expires: March 15, 2021                                          S. Fang
                                                                  R. Tan
                                             Huawei Technologies,Co.,Ltd
                                                                  C. Zhu
                                                         ZTE Corporation
                                                      September 11, 2020

                  PCEP Extension for Native IP Network
               draft-ietf-pce-pcep-extension-native-ip-07

Abstract

   This document defines the Path Computation Element Communication
   Protocol (PCEP) extension for Central Control Dynamic Routing (CCDR)
   based application in Native IP network.  The scenario and framework
   of CCDR in native IP is described in [RFC8735] and
   [I-D.ietf-teas-pce-native-ip].  This draft describes the key
   information that is transferred between Path Computation Element
   (PCE) and Path Computation Clients (PCC) to accomplish the End to End
   (E2E) traffic assurance in Native IP network under central control
   mode.

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 March 15, 2021.

Copyright Notice

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

Wang, et al.             Expires March 15, 2021                 [Page 1]
Internet-Draft    PCEP Extension for Native IP Network    September 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.  Conventions used in this document . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  STATEFUL-PCE-CAPABILITY TLV . . . . . . . . . . . . . . . . .   3
   5.  PCE-Initiated Native IP TE Procedures . . . . . . . . . . . .   4
   6.  New Objects Extension . . . . . . . . . . . . . . . . . . . .   4
   7.  Objects Formats . . . . . . . . . . . . . . . . . . . . . . .   4
     7.1.  BGP Peer Info Object  . . . . . . . . . . . . . . . . . .   5
     7.2.  Explicit Peer Route Object  . . . . . . . . . . . . . . .   9
     7.3.  Peer Prefix Association Object  . . . . . . . . . . . . .  12
   8.  New Error-Types and Error-Values Defined  . . . . . . . . . .  14
   9.  Management Consideration  . . . . . . . . . . . . . . . . . .  15
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  15
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
     11.1.  PCEP Object Types  . . . . . . . . . . . . . . . . . . .  16
   12. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . .  16
   13. Normative References  . . . . . . . . . . . . . . . . . . . .  16
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  17

1.  Introduction

   Traditionally, Multiprotocol Label Switching Traffic Engineering
   (MPLS-TE) traffic assurance requires the corresponding network
   devices support Multiprotocol Label Switching (MPLS) or the complex
   Resource ReSerVation Protocol (RSVP)/Label Distribution Protocol
   (LDP) /Segment Routing etc. technologies to assure the End-to-End
   (E2E) traffic performance.  But in native IP network, there will be
   no such signaling protocol to synchronize the action among different
   network devices.  It is necessary to use the central control mode
   that described in [RFC8283] to correlate the forwarding behavior
   among different network devices.  Draft [I-D.ietf-teas-pce-native-ip]
   describes the architecture and solution philosophy for the E2E
Show full document text