PCEP extension to support reporting of dynamic tunnels
draft-paul-pce-dynamic-tunnel-00

Document Type Active Internet-Draft (individual)
Last updated 2018-11-20
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                                                    Arijit Paul
Internet-Draft                                         Juniper Networks        
Intended status: Standards Track                       November 20, 2018
Expires: May 20, 2019                                 

PCEP extension to support reporting of dynamic tunnels
                draft-paul-pce-dynamic-tunnel-00

Abstract

   In a SDN environment, path computation element protocol(PCEP)
   (RFC 5440) is used between a controller and the network devices, 
   using which controller can setup and tear down Resource ReserVation 
   Protocol (RSVP) based label switched paths(LSPs) in the network 
   having Path Computation Client (PCC) as Label Switched Router (LSR). 
   In an environment where dynamic tunnels are used to provide MPLS based 
   customer services instead of a Label Switched Path, the specifications 
   lacks a method to report the Dynamic tunnels over PCEP session to PCE.
   This draft defines a method to advertise the dynamic tunnels via PCEP 
   session to PCE.

   This document proposes new object TLV that can be used to report 
   dynamic tunnels to the PCE.
   
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 March 8, 2018

Paul            Expires May 20, 2019             [Page 1]
Internet-Draft       Reporting dynamic tunnel for PCEP        November 2018

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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   1
   2.  Conventions used in this document . . . . . . . . . . . . . .   2
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   4.  Overview of Protocol Extensions . . . . . . . . . . . . . . .   2
     4.1.  Capability Advertisement  . . . . . . . . . . . . . . . .   2
     4.2.  Dynamic-Tunnel Object   . . . . . . . . . . . . . . . . .   3
       4.2.1  IPV4-TUNNEL-IDENTIFIERS TLV  . . . . . . . . . . . . .   5
     4.3.  Metric Object   . . . . . . . . . . . . . . . . . . . . .   6
   5.  Backward Compatibility Consideration  . . . . . . . . . . . .   6
   6.  Management Considerations . . . . . . . . . . . . . . . . . .   6
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   6
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     9.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   As described in [RFC5440], PCEP can be used to create, modify or 
   delete LSPs between PCCs. PCEP can be used to create, modify and 
   delete RSVP and segment routing LSPs between PCCs. This document 
   specifies the way to report the dynamic nexthop based tunnels from PCC 
   to PCE server. This is helpful for PCE to have complete visibility
   of the network and help take intelligent decisions based on the 
   information available to it.

Paul            Expires May 20, 2019             [Page 2]
Internet-Draft       Reporting dynamic tunnel for PCEP        November 2018

   In this draft a method to report dynamic tunnels from PCC via PCEP is
   outlined.
   
   This document proposes one new pcep objects to carry the tunnels attributes 
   for individual dynamic tunnels. Since only reporting of dynamic tunnels
   is outlined here, only dynamic tunnel object and well-known metric objects
  are being carried in PCRpt [RFC8231] of PCEP message in order to report 
  the dynamic tunnel to PCE.

2.  Conventions used in this document

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text