Extensions to the Path Computation Element Protocol(PCEP) Management Information Base(MIB) Module
draft-pce-mib-extensions-01

Document Type Active Internet-Draft (individual)
Last updated 2016-10-07
Stream (None)
Intended RFC status (None)
Formats plain text xml 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)
Internet Engineering Task Force                                V. Ramany
Internet-Draft                                               D. Parchuru
Intended status: Standards Track                                D. Kumar
Expires: April 10, 2017                     Brocade Communications, Inc.
                                                         October 7, 2016

  Extensions to the Path Computation Element Protocol(PCEP) Management
                      Information Base(MIB) Module
                      draft-pce-mib-extensions-01

Abstract

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it describes extensions to the managed objects for
   modeling of the Path Computation Element Communication Protocol
   (PCEP) for communications between a Path Computation Client (PCC) and
   a Path Computation Element (PCE), or between two PCEs, that support
   stateful capabilities.

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 April 10, 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

Ramany, et al.           Expires April 10, 2017                 [Page 1]
Internet-Draft       Extenstions to PCEP MIB Module         October 2016

   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
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  The Internet-Standard Management Framework  . . . . . . . . .   3
   3.  Overview  . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  pcePcepXEntityTable . . . . . . . . . . . . . . . . . . .   4
     3.2.  pcePcepXPeerTable . . . . . . . . . . . . . . . . . . . .   5
     3.3.  pcePcepXSessTable . . . . . . . . . . . . . . . . . . . .   5
   4.  Object Definitions  . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  PCE-PCEP-MIB  . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  20
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  20
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  20
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  20
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  22
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  22

1.  Introduction

   The PCE defined in [RFC4655] is an entity that is capable of
   computing a network path or route based on a network graph and
   applying computational constraints.  A PCC may make requests to a PCE
   for paths to be computed.

   PCEP is the communication protocol between a PCC and PCE and is
   defined in [RFC5440].  PCEP interactions include path computation
   requests and path computation replies as well as notifications of
   specific states related to the use of a PCE in the context of
   Multiprotocol Label Switching (MPLS) and Generalized MPLS (GMPLS)
   Traffic Engineering (TE).

   [RFC7420] defined a MIB module that can be used to monitor PCEP
   interactions between a PCC and a PCE, or between two PCEs.  This memo
   proposes extensions to the MIB module that can help monitor
   interactions between PCEP peers that have stateful capabilities as
   defined in [I-D.ietf-pce-stateful-pce],
   [I-D.ietf-pce-pce-initiated-lsp] and
   [I-D.ietf-pce-stateful-sync-optimizations].

   The scope of this document is to extend the MIB module for the PCEP
Show full document text