PCE communication protocol (PCEP) Management Information Base
draft-ietf-pce-pcep-mib-05

The information below is for an old version of the document
Document Type Active Internet-Draft (pce WG)
Last updated 2013-07-15
Replaces draft-kkoushik-pce-pcep-mib
Stream IETF
Intended RFC status (None)
Formats plain text pdf html
Stream WG state WG Document Jan 2014
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PCE Working Group                                             A. Koushik
Internet-Draft                                       Cisco Systems, Inc.
Intended status: Standards Track                                S. Emile
Expires: January 16, 2014                                 France Telecom
                                                                 Q. Zhao
                                                       Huawei Technology
                                                                 D. King
                                                      Old Dog Consulting
                                                             J. Hardwick
                                                              Metaswitch
                                                           July 15, 2013

     PCE communication protocol (PCEP) Management Information Base
                       draft-ietf-pce-pcep-mib-05

Abstract

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

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 January 16, 2014.

Copyright Notice

   Copyright (c) 2013 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

Koushik, et al.         Expires January 16, 2014                [Page 1]
Internet-Draft                  PCEP MIB                       July 2013

   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  The Internet-Standard Management Framework . . . . . . . . . .  3
   3.  Requirements Language  . . . . . . . . . . . . . . . . . . . .  3
   4.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   5.  PCEP MIB Module Architecture . . . . . . . . . . . . . . . . .  4
     5.1.  Relations to other MIB modules . . . . . . . . . . . . . .  4
   6.  Object Definitions . . . . . . . . . . . . . . . . . . . . . .  4
     6.1.  PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . .  4
   7.  Security Considerations  . . . . . . . . . . . . . . . . . . . 43
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 44
   9.  Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 44
   10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 44
     10.1. Normative References . . . . . . . . . . . . . . . . . . . 44
     10.2. Normative References . . . . . . . . . . . . . . . . . . . 45
   Appendix A.  Acknowledgement . . . . . . . . . . . . . . . . . . . 45

Koushik, et al.         Expires January 16, 2014                [Page 2]
Internet-Draft                  PCEP MIB                       July 2013

1.  Introduction

   The Path Computation Element (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 Path
   Computation Client (PCC) may make requests to a PCE for paths to be
   computed.

   The PCE communication protocol (PCEP) is the communication protocol
   between a PCC and PCE for point-to-point (P2P) path computations and
   is defined in [RFC5440].  Such PCEP communication interactions
   include path computation requests and path computation replies as
   well as notifications of specific states related to the use of a PCE
Show full document text