draft-ietf-pce-tc-mib-00.txt   draft-ietf-pce-tc-mib-01.txt 
Network Working Group E. Stephan Network Working Group E. Stephan
Internet-Draft France Telecom Internet-Draft France Telecom
Intended status: Standards Track December 6, 2006 Intended status: Standards Track March 4, 2007
Expires: June 9, 2007 Expires: September 5, 2007
Definitions of Textual Conventions for Path Computation Element Definitions of Textual Conventions for Path Computation Element
draft-ietf-pce-tc-mib-00 draft-ietf-pce-tc-mib-01
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of 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
skipping to change at page 1, line 34 skipping to change at page 1, line 34
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 June 9, 2007. This Internet-Draft will expire on September 5, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
Abstract Abstract
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.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Internet-Standard Management Framework . . . . . . . . . . 3 2. The Internet-Standard Management Framework . . . . . . . . . . 3
3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. PCE Textual Conventions MIB Definitions . . . . . . . . . . . . 3 4. Structure of the MIB Module . . . . . . . . . . . . . . . . . . 3
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 5 5. PCE Textual Conventions MIB Definitions . . . . . . . . . . . . 4
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5 6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 5 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 5
7.1. Normative References . . . . . . . . . . . . . . . . . . . 5 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.2. Informative References . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 6
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 6
Intellectual Property and Copyright Statements . . . . . . . . . . 7 Intellectual Property and Copyright Statements . . . . . . . . . . 8
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 38 skipping to change at page 3, line 38
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. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when they appear in this document, are to be interpreted "OPTIONAL", when they appear in this document, are to be interpreted
as described in BCP 14, RFC 2119 [RFC2119]. as described in BCP 14, RFC 2119 [RFC2119].
4. PCE Textual Conventions MIB Definitions 4. 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:
PCE-TC-STD-MIB (defined in this memo) defined the root for homing
Standard PCE MIB modules;
PCE-TC-DISC-MIB defines the management information for monitoring
PCE entities discovery;
PCE-TC-PCEP-MIB defines the information for managing PCE
communication protocol;
5. 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;
pceTCStdMIB MODULE-IDENTITY pceTCDraftMIB MODULE-IDENTITY
LAST-UPDATED "200610140000Z" -- October 14, 2006 LAST-UPDATED "200703040000Z" -- March 4, 2007
ORGANIZATION "Path Computation Element (PCE) Working Group" ORGANIZATION "Path Computation Element (PCE) Working Group"
CONTACT-INFO " CONTACT-INFO "
Stephan Emile Stephan Emile
France Telecom DR&D France Telecom
Email: emile.stephan@orange-ft.com Email: emile.stephan@orange-ftgroup.com
Email comments directly to the PCE WG Mailing List at pce@ietf.org Email comments directly to the PCE WG Mailing List at pce@ietf.org
WG-URL: http://www.ietf.org/html.charters/pce-charter.html WG-URL: http://www.ietf.org/html.charters/pce-charter.html
" "
DESCRIPTION DESCRIPTION
"This memo defines a portion of the Management Information Base "This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it defines Textual Conventions to community. In particular, it defines Textual Conventions to
represent commonly used Path Computation Element (PCE) management represent commonly used Path Computation Element (PCE) management
information. The intent is that these TEXTUAL CONVENTIONS (TCs) information. The intent is that these TEXTUAL CONVENTIONS (TCs)
will be imported and used in PCE related MIB modules to avoid will be imported and used in PCE related MIB modules to avoid
duplicating conventions." duplicating conventions."
::= { experimental 10000 } -- Temporary node ( for smilint) := { pceStdMIB 1 }
pceStdMIB OBJECT IDENTIFIER ::= { experimental 9999 } -- Temporary
node ( for smilint)
-- Textual Conventions (sorted alphabetically). -- Textual Conventions (sorted alphabetically).
PceRoutingDomainID ::= TEXTUAL-CONVENTION PceRoutingDomainID ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A PCE-DOMAINS information element or a A PCE-DEST-DOMAINS "A PCE-DOMAINS information element or a A PCE-DEST-DOMAINS
information element carries the identifier of a routing domain information element carries the identifier of a routing domain
(area, as) which type depends on both the routing protocol and (area, as) which type depends on both the routing protocol and
on the version of Internet protocol in use in this routing on the version of Internet protocol in use in this routing
skipping to change at page 5, line 21 skipping to change at page 5, line 36
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
5. Security Considerations 6. 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.
6. IANA Considerations 7. IANA Considerations
. IANA is requested to make a MIB OID assignment for pceStdMIB under
the mib-2 branch.
7. References 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.1. Normative References 8. References
8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. 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.
[RFC4674] Le Roux, J., "Requirements for Path Computation Element [RFC4674] Le Roux, J., "Requirements for Path Computation Element
(PCE) Discovery", RFC 4674, October 2006. (PCE) Discovery", RFC 4674, October 2006.
7.2. Informative References 8.2. Informative References
[RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768, [RFC0768] Postel, J., "User Datagram Protocol", STD 6, RFC 768,
August 1980. August 1980.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[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.
skipping to change at page 7, line 7 skipping to change at page 8, line 7
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
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2006). Copyright (C) The IETF Trust (2007).
This document is subject to the rights, licenses and restrictions This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors contained in BCP 78, and except as set forth therein, the authors
retain all their rights. retain all their rights.
This document and the information contained herein are provided on an This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
 End of changes. 18 change blocks. 
29 lines changed or deleted 52 lines changed or added

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