draft-ietf-pce-tc-mib-04.txt   draft-ietf-pce-tc-mib-05.txt 
Internet Engineering Task Force E. Stephan
Network Working Group E. Stephan
Internet-Draft France Telecom Internet-Draft France Telecom
Intended status: Standards Track March 2, 2009 Intended status: Standards Track Q. Zhao
Expires: September 3, 2009 Created: October 25, 2009 Huawei Technology
Expires: March 25, 2009 D. King
Old Dog Consulting
Definitions of Textual Conventions for Path Computation Element Definitions of Textual Conventions for Path Computation Element
draft-ietf-pce-tc-mib-04 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 Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with
provisions of BCP 78 and BCP 79. the provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 3, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
Abstract This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
This memo defines a portion of the Management Information Base (MIB) 10, 2008. The person(s) controlling the copyright in some of this
for use with network management protocols in the Internet community. material may not have granted the IETF Trust the right to allow
In particular, it defines Textual Conventions to represent commonly modifications of such material outside the IETF Standards Process.
used Path Computation Element (PCE) management information. The Without obtaining an adequate license from the person(s) controlling
intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and the copyright in such materials, this document may not be modified
used in PCE related MIB modules to avoid duplicating conventions. 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 Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 2
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 3
4. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 3 4. PCE Textual Conventions MIB Definitions . . . . . . . . . . . . 3
5. PCE Textual Conventions MIB Definitions . . . . . . . . . . . . 4 5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 7.1. Normative References . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 7.2. Informative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines Textual Conventions to represent commonly In particular, it defines Textual Conventions to represent commonly
used Path Computation Element (PCE) management information. The used Path Computation Element (PCE) management information. The
intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and intent is that these TEXTUAL CONVENTIONS (TCs) will be imported and
used in PCE related MIB modules to avoid duplicating conventions. used in PCE related MIB modules to avoid duplicating conventions.
skipping to change at page 3, line 31 skipping to change at page 3, line 14
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Conventions 3. Structure of the MIB Module
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when they appear in this document, are to be interpreted
as described in BCP 14, RFC 2119 [RFC2119].
4. Structure of the MIB Module
This MIB module defines PCE common SMI items. It defines the nodes 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 for the homing of the MIB modules and TC to be imported and used in
PCE related MIB modules. PCE related MIB modules.
PCE management information is arranged into 3 modules: PCE management information is arranged into 3 modules:
o PCE-TC-STD-MIB (defined in this memo) defined the root for homing o PCE-TC-STD-MIB (defined in this memo) defined the root for homing
Standard PCE MIB modules; Standard PCE MIB modules;
o PCE-DISC-STD-MIB defines the management information for monitoring o PCE-DISC-STD-MIB defines the management information for monitoring
PCE entities discovery; PCE entities discovery;
skipping to change at page 4, line 4 skipping to change at page 3, line 25
This MIB module defines PCE common SMI items. It defines the nodes 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 for the homing of the MIB modules and TC to be imported and used in
PCE related MIB modules. PCE related MIB modules.
PCE management information is arranged into 3 modules: PCE management information is arranged into 3 modules:
o PCE-TC-STD-MIB (defined in this memo) defined the root for homing o PCE-TC-STD-MIB (defined in this memo) defined the root for homing
Standard PCE MIB modules; Standard PCE MIB modules;
o PCE-DISC-STD-MIB defines the management information for monitoring o PCE-DISC-STD-MIB defines the management information for monitoring
PCE entities discovery; PCE entities discovery;
o PCE-PCEP-STD-MIB defines the information for managing PCE o PCE-PCEP-STD-MIB defines the information for managing PCE
communication protocol; communication protocol;
5. PCE Textual Conventions MIB Definitions 4. PCE Textual Conventions MIB Definitions
PCE-TC-STD-MIB DEFINITIONS ::= BEGIN PCE-TC-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
experimental FROM SNMPv2-SMI experimental FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
pceTCDraftMIB MODULE-IDENTITY pceTCDraftMIB MODULE-IDENTITY
skipping to change at page 6, line 5 skipping to change at page 5, line 24
PceRoutingDomainID type is OCTET STRING (SIZE (0..20)), PceRoutingDomainID type is OCTET STRING (SIZE (0..20)),
corresponding to the name of an ISIS area (see RFC 1195); corresponding to the name of an ISIS area (see RFC 1195);
asNumber(18) asNumber(18)
PceRoutingDomainID type is OCTET STRING (SIZE (2)) PceRoutingDomainID type is OCTET STRING (SIZE (2))
corresponding to the name of an Autonomous System. corresponding to the name of an Autonomous System.
" "
SYNTAX OCTET STRING (SIZE (0..20)) SYNTAX OCTET STRING (SIZE (0..20))
END END
6. Security Considerations 5. Security Considerations
This module defines only textual conventions. As security This module defines only textual conventions. As security
considerations can only be written in MIB modules that define considerations can only be written in MIB modules that define
management objects this document has no impact on the security of the management objects this document has no impact on the security of the
Internet. Internet.
7. IANA Considerations 6. IANA Considerations
IANA is requested to make a MIB OID assignment for pceStdMIB under IANA is requested to make a MIB OID assignment for pceStdMIB under
the mib-2 branch. the mib-2 branch.
PCE related standards track MIB modules should be homed under the PCE related standards track MIB modules should be homed under the
pceStdMIB subtree. This document also requests IANA to assign { pceStdMIB subtree. This document also requests IANA to assign {
pceStdMIB 1 } to the PCE-TC-STD-MIB specified in this document. pceStdMIB 1 } to the PCE-TC-STD-MIB specified in this document.
8. References 7. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 7.1. Normative References
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999. April 1999.
8.2. Informative References 7.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, August 2006. Element (PCE)-Based Architecture", RFC 4655, August 2006.
Author's Address Author's Address
skipping to change at page 7, line 11 skipping to change at page 6, line 20
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, August 2006. Element (PCE)-Based Architecture", RFC 4655, August 2006.
Author's Address Author's Address
Stephan Emile Stephan Emile
France Telecom France Telecom
2 avenue Pierre Marzin 2 avenue Pierre Marzin
Lannion, F-22307 Lannion, F-22307
Fax: +33 2 96 05 18 52 Fax: +33 2 96 05 18 52
Email: emile.stephan@orange-ftgroup.com 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
 End of changes. 17 change blocks. 
47 lines changed or deleted 45 lines changed or added

This html diff was produced by rfcdiff 1.37a. The latest version is available from http://tools.ietf.org/tools/rfcdiff/