[Docs] [txt|pdf] [Tracker] [WG] [Email] [Diff1] [Diff2] [Nits]

Versions: (draft-stephan-pce-tc-mib) 00 01 02 03 04 05

Internet Engineering Task Force                               E. Stephan
Internet-Draft                                            France Telecom
Intended status: Standards Track                                 Q. Zhao
Created: October 25, 2009                              Huawei Technology
Expires: March 25, 2009                                          D. King
                                                      Old Dog Consulting


    Definitions of Textual Conventions for Path Computation Element
                        draft-ietf-pce-tc-mib-05


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 defines Textual Conventions to represent commonly
   used Path Computation Element (PCE) management information.  The
   intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and
   used in PCE related MIB modules to avoid duplicating conventions.


Status of this Memo

   This Internet-Draft is submitted to IETF in full conformance with
   the provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   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."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.


Copyright Notice

   Copyright (c) 2009 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 in effect on the date of
   publication of this document (http://trustee.ietf.org/license-info).
   Please review these documents carefully, as they describe your rights
   and restrictions with respect to this document.

Stephan, et al.                                                [Page 1]


draft-ietf-pce-tc-mib-05                                  October 2009

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008. The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.


Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2
   2.  The Internet-Standard Management Framework  . . . . . . . . . . 2
   3.  Structure of the MIB Module . . . . . . . . . . . . . . . . . . 3
   4.  PCE Textual Conventions MIB Definitions . . . . . . . . . . . . 3
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . . . 5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . . . 5
     7.2.  Informative References  . . . . . . . . . . . . . . . . . . 6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 6


1.  Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it defines Textual Conventions to represent commonly
   used Path Computation Element (PCE) management information.  The
   intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and
   used in PCE related MIB modules to avoid duplicating conventions.

   For an introduction to the concepts of PCE, see [RFC4655].


2.  The Internet-Standard Management Framework

   For a detailed overview of the documents that describe the current
   Internet-Standard Management Framework, please refer to section 7 of
   RFC 3410 [RFC3410].






Stephan, et al.                                                [Page 2]


draft-ietf-pce-tc-mib-05                                  October 2009


   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  MIB objects are generally
   accessed through the Simple Network Management Protocol (SNMP).
   Objects in the MIB are defined using the mechanisms defined in the
   Structure of Management Information (SMI).  This memo specifies a MIB
   module that is compliant to the SMIv2, which is described in STD 58,
   RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
   [RFC2580].


3.  Structure of the MIB Module

   This MIB module defines PCE common SMI items.  It defines the nodes
   for the homing of the MIB modules and TC to be imported and used in
   PCE related MIB modules.

   PCE management information is arranged into 3 modules:
   o  PCE-TC-STD-MIB (defined in this memo) defined the root for homing
      Standard PCE MIB modules;
   o  PCE-DISC-STD-MIB defines the management information for monitoring
      PCE entities discovery;
   o  PCE-PCEP-STD-MIB defines the information for managing PCE
      communication protocol;


4.  PCE Textual Conventions MIB Definitions

   PCE-TC-STD-MIB DEFINITIONS ::= BEGIN

   IMPORTS
      MODULE-IDENTITY,
      experimental FROM SNMPv2-SMI
      TEXTUAL-CONVENTION
         FROM SNMPv2-TC;

   pceTCDraftMIB MODULE-IDENTITY
      LAST-UPDATED "200903020000Z" -- March 2, 2009
      ORGANIZATION "Path Computation Element (PCE) Working Group"
      CONTACT-INFO "
         Stephan Emile
         France Telecom
      Email: emile.stephan@orange-ftgroup.com









Stephan, et al.                                                [Page 3]


draft-ietf-pce-tc-mib-05                                  October 2009


      Email comments directly to the PCE WG Mailing List at pce@ietf.org
      WG-URL: http://www.ietf.org/html.charters/pce-charter.html"
      DESCRIPTION
         "This memo defines a portion of the Management Information Base
         (MIB) for use with network management protocols in the Internet
         community.  In particular, it defines Textual Conventions to
         represent commonly used Path Computation Element (PCE)
         management information.  The intent is that these TEXTUAL
         CONVENTIONS (TCs) will be imported and used in PCE related MIB
         modules to avoid duplicating conventions."
      ::= { pceStdMIB 1 }

   pceStdMIB OBJECT IDENTIFIER ::= { experimental 9999 }

   -- RFC Editor: Please see the IANA Considerations Section.

   -- 'experimental 9999' is a temporary root for running smilint.

   -- 'pceStdMIB' will be homed in 'mib-2'

   -- Textual Conventions (sorted alphabetically).

   PcePcepIdentifier ::= TEXTUAL-CONVENTION
      DISPLAY-HINT "1d.1d.1d.1d:1d:1d"
      STATUS current
      DESCRIPTION
         "The LDP identifier is a six octet quantity which is used to
         identify a PCE client."
      SYNTAX OCTET STRING (SIZE (0..6))

   PceRoutingDomainID ::= TEXTUAL-CONVENTION
      STATUS current
      DESCRIPTION
         "A PCE-DOMAINS information element or a A PCE-DEST-DOMAINS
         information element carries the identifier of a routing domain
         (area, as) which type depends on both the routing protocol and
         on the version of Internet protocol in use in this routing
         domain.

         This TC defines a common SMI type for the different kinds of
         routing domain identifiers.

         A PceRoutingDomainID value is always interpreted within the
         context of an AddressFamilyNumbers value.  Every usage of the
         PceRoutingDomainID textual convention is required to specify
         the AddressFamilyNumbers object which provides the context.

         The value of an PceRoutingDomainID object must always be
         consistent with the value of the associated
         AddressFamilyNumbers object.

Stephan, et al.                                                [Page 4]


draft-ietf-pce-tc-mib-05                                  October 2009


         Following is the mapping between AddressFamilyNumbers type and
         PceRoutingDomainID size:
            ipV4(1):
               PceRoutingDomainID is an InetAddressIPv4 corresponding to
               the name of an OSPF area;
            ipV6(2):
               PceRoutingDomainID is an InetAddressIPv6 corresponding to
               the name of an OSPF area;
            nsap(3):
               PceRoutingDomainID type is OCTET STRING (SIZE (0..20)),
               corresponding to the name of an ISIS area (see RFC 1195);
            asNumber(18)
               PceRoutingDomainID type is OCTET STRING (SIZE (2))
               corresponding to the name of an Autonomous System.
         "
      SYNTAX OCTET STRING (SIZE (0..20))

   END


5.  Security Considerations

   This module defines only textual conventions.  As security
   considerations can only be written in MIB modules that define
   management objects this document has no impact on the security of the
   Internet.


6.  IANA Considerations

   IANA is requested to make a MIB OID assignment for pceStdMIB under
   the mib-2 branch.

   PCE related standards track MIB modules should be homed under the
   pceStdMIB subtree.  This document also requests IANA to assign {
   pceStdMIB 1 } to the PCE-TC-STD-MIB specified in this document.


7.  References

7.1.  Normative References

   [RFC2578]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Structure of Management Information
              Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

   [RFC2579]  McCloghrie, K., Ed., Perkins, D., Ed., and J.
              Schoenwaelder, Ed., "Textual Conventions for SMIv2",
              STD 58, RFC 2579, April 1999.

   [RFC2580]  McCloghrie, K., Perkins, D., and J. Schoenwaelder,
              "Conformance Statements for SMIv2", STD 58, RFC 2580,
              April 1999.

Stephan, et al.                                                [Page 5]


draft-ietf-pce-tc-mib-05                                  October 2009


7.2.  Informative References

   [RFC3410]  Case, J., Mundy, R., Partain, D., and B. Stewart,
              "Introduction and Applicability Statements for Internet-
              Standard Management Framework", RFC 3410, December 2002.

   [RFC4655]  Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
              Element (PCE)-Based Architecture", RFC 4655, August 2006.


Author's Address

   Stephan Emile
   France Telecom
   2 avenue Pierre Marzin
   Lannion,   F-22307
   Fax:   +33 2 96 05 18 52
   Email: emile.stephan@orange-ftgroup.com

   Quintin Zhao
   Huawei Technology
   125 Nagog Technology Park
   Acton, MA  01719
   US
   Email: qzhao@huawei.com

   Daniel King
   Old Dog Consulting
   UK
   Email: daniel@olddog.co.uk


















Stephan, et al.                                                [Page 6]

draft-ietf-pce-tc-mib-05                                  October 2009

Html markup produced by rfcmarkup 1.127, available from https://tools.ietf.org/tools/rfcmarkup/