datatracker.ietf.org
Sign in
Version 5.6.2.p6, 2014-09-03
Report a bug

Management Information Base (MIB) for the PCE Communications Protocol (PCEP) for Path-Key based Confidentiality in Inter-Domain Path Computation.
draft-dhody-pce-pcep-pathkey-mib-08

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-08-04
Intended RFC status: Unknown
Other versions: plain text, xml, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

PCE Working Group                                               D. Dhody
Internet-Draft                                                  U. Palle
Intended status: Standards Track                                 Q. Zhao
Expires: February 5, 2015                              Huawei Technology
                                                                 D. King
                                                      Old Dog Consulting
                                                          August 4, 2014

 Management Information Base (MIB) for the PCE Communications Protocol
     (PCEP) for Path-Key based Confidentiality in Inter-Domain Path
                              Computation.
                  draft-dhody-pce-pcep-pathkey-mib-08

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 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 when path-key-based
   confidentiality in inter-domain path computation is requested.

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 February 5, 2015.

Copyright Notice

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

Dhody, et al.           Expires February 5, 2015                [Page 1]
Internet-Draft              PCEP PATHKEY MIB                 August 2014

   (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  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  The Internet-Standard Management Framework  . . . . . . . . .   3
   4.  PCEP Pathkey MIB Module Architecture  . . . . . . . . . . . .   3
     4.1.  Relations to other MIB modules  . . . . . . . . . . . . .   4
   5.  Example of the PCEP PathKey MIB module usage  . . . . . . . .   4
   6.  Object definitions  . . . . . . . . . . . . . . . . . . . . .   5
     6.1.  PCEP-PATHKEY-MIB  . . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  21
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  21
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  21
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  22

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 designed as a communication
   protocol between PCCs and PCEs for path computations and is defined
   in [RFC5440].

   If confidentiality is required between domains, Path-Key based
   mechanism is described in [RFC5520].  For preserving the
   confidentiality of the "Confidential Path Segment (CPS)"; the PCE
   returns a path containing a loose hop in place of the segment that
   must be kept confidential.

   [PCEP-MIB] defines a portion of the MIB for use with network
   management protocols in the Internet community that can be used to
   manage PCEP communications between a PCC and a PCE, or between two

[include full document text]