PCE auxiliary connections
draft-hu-pce-auxiliary-connections-00

Document Type Active Internet-Draft (individual)
Last updated 2016-12-12
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
PCE WG                                                       Fangwei. Hu
Internet-Draft                                                 Ran. Chen
Intended status: Standards Track                         ZTE Corporation
Expires: June 15, 2017                                 December 12, 2016

                       PCE auxiliary connections
               draft-hu-pce-auxiliary-connections-00.txt

Abstract

   This document provides a method to establish auxiliary connections
   between PCE and PCC to improve the reliability of the connection of
   PCE and PCC.  The real-time sample data and some state report flow
   are suggestion to transport by take use of the auxiliary connection.

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 http://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 June 15, 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.  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.

Hu & Chen                 Expires June 15, 2017                 [Page 1]
Internet-Draft            Auxiliary Connections            December 2016

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Conventions Used in This Document . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     2.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  New Functions to Support auxiliary connections  . . . . . . .   3
   4.  Overview of Protocol Extensions . . . . . . . . . . . . . . .   3
     4.1.  Auxiliary-Connections-Capability-TLV  . . . . . . . . . .   3
     4.2.  Capability Advertisement  . . . . . . . . . . . . . . . .   5
     4.3.  Initialization Phase  . . . . . . . . . . . . . . . . . .   5
     4.4.  Termination of the Auxiliary Connections PCEP Session . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  Informative References  . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The Path Computation Element Protocol (PCEP) defined in [RFC5440] is
   used between a Path Computation Element (PCE) and a Path Computation
   Client (PCC) (or other PCE) to enable computation of Multi-protocol
   Label Switching (MPLS) for Traffic Engineering Label Switched Path
   (TE LSP).

   PCEP is a recommendation south-bound interface protocol, and PCE acts
   as a controller, and PCCs are the SDN switch being managed by PCE.
   The PCC should report the link state and flow statistics in the SDN
   environment.  The data going through the PCEP channel may be very
   huge.  The PCEP session and the TCP connection may be occupied by the
   flow sample and be congested for the PCEP packet.  So it is important
   to improve the reliability of the PCE and the connection between PCE
   and PCC.

   This document provides to establish auxiliary connections between PCE
   and PCC to improve the reliability of the connection of PCE and PCC.
   The real-time sample data and some state report flow are suggestion
   to transport by take use of the auxiliary connection.  And the
   original connection (we name it main connection) are used to
   transport the PCEP protocol message (such as PCE PCReq message, PCRep
   message, PCRpt message, PCUpd mesage, PCInitiate message
   ,etc.)([RFC5440], [I-D.ietf-pce-stateful-pce],
   [I-D.ietf-pce-pce-initiated-lsp]).

Hu & Chen                 Expires June 15, 2017                 [Page 2]
Show full document text