draft-ietf-pce-pcep-mib-00.txt   draft-ietf-pce-pcep-mib-01.txt 
Internet Draft Internet Engineering Task Force A S Kiran Koushik
Intended status: Standards Track A S Kiran Koushik Internet Draft Cisco Systems, Inc.
Expires: July 2009 Cisco Systems, Inc. Intended Status: Standards Track E. Stephan
E. Stephan Created: March 8, 2010 France Telecom
France Telecom Expires: September 8, 2010 Quintin Zhao
Huawei Technology
Daniel King
Old Dog Consulting
PCE communication protocol(PCEP) Management Information Base PCE communication protocol(PCEP) Management Information Base
draft-ietf-pce-pcep-mib-00.txt draft-ietf-pce-pcep-mib-01.txt
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 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 the
provisions of BCP 78 and BCP 79. 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.
skipping to change at page 1, line 33 skipping to change at page 1, line 45
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 July 9, 2009. This Internet-Draft will expire on September 8, 2010.
Abstract Copyright Notice
This memo defines an experimental portion of the Management Copyright (c) 2010 IETF Trust and the persons identified as the
Information Base for use with network management protocols in the document authors. All rights reserved.
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.
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009 This document is subject to BCP 78 and the IETF Trust's Legal
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 Table of Contents
Abstract............................................................1 Abstract............................................................
1 Introduction...................................................2 1. Introduction.....................................................
2 Terminology....................................................2 2. Terminology......................................................
3 The Internet-Standard Management Framework.....................3 3. The Internet-Standard Management Framework.......................
4 PCEP MIB modules Architecture..................................3 4. PCEP MIB modules Architecture....................................
4.1 Relations to other MIB modules.................................3 4.1 Relations to other MIB modules................................
5 Example of the PCEP MIB modules usage .........................3 5. Example of the PCEP MIB modules usage ...........................
6 Object definitions.............................................4 6. Object definitions...............................................
6.1 PCE-PCEP-DRAFT-MIB.............................................4 6.1 PCE-PCEP-DRAFT-MIB..........................................
7 Security considerations.......................................20 7. Security considerations..........................................
8 IANA Considerations...........................................20 8. IANA Considerations..............................................
9 References....................................................20 9. References.......................................................
9.1 Normative References..........................................20 9.1. Normative References........................................
9.2 Informative References........................................20 9.2. Informative References......................................
10 Acknowledgement ..............................................21 10. Acknowledgement ................................................
11 Author's Addresses............................................21 11. Author's Addresses..............................................
1 Introduction 1. Introduction
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 a MIB module that can be community. In particular, it defines a MIB module that can be
used to manage Path Computation Element communication used to manage Path Computation Element communication
Protocol (PCEP) for communications between a Path Computation Client Protocol (PCEP) [RFC5440] for communications between a Path
(PCC) and a Path Computation Element (PCE), or between two PCEs. Computation Client(PCC) and a Path Computation Element (PCE), or
between two PCEs.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
"OPTIONAL" in this document are to be interpreted as described in this document are to be interpreted as described in BCP 14,
RFC-2119 [BCP14]. RFC 2119 [RFC2119].
2 Terminology 2. Terminology
The terminology used in this document is built on notions introduced The terminology used in this document is built on notions introduced
and discussed in PCE WG documents. The reader should be familiar and discussed in PCE WG documents. The reader should be familiar
with these documents with these documents.
Domain: Domain:
any collection of network elements within a common sphere of any collection of network elements within a common sphere of
address management or path computational responsibility. address management or path computational responsibility.
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
IGP Area: IGP Area:
OSPF Area or ISIS level. OSPF Area or ISIS level.
PCC: This document also uses the terminology defined in [RFC4655]
Path Computation Client: any client application requesting a path and [RFC5440].
computation to be performed by a Path Computation Element.
PCE:
Path Computation Element: an entity (component, application, or
network node) that is capable of computing a network path or route
based on a network graph, and applying computational
constraints.
PCEP Client:
A PCEP client represents a PCE or a PCC for network management
purposes.
3 The Internet-Standard Management Framework 3. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 Internet-Standard Management Framework, please refer to section 7
of RFC 3410 [RFC3410]. of RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, Managed objects are accessed via a virtual information store,
termed the Management Information Base or MIB. MIB objects are termed the Management Information Base or MIB. MIB objects are
generally accessed through the Simple Network Management Protocol generally accessed through the Simple Network Management Protocol
(SNMP). Objects in the MIB are defined using the mechanisms (SNMP). Objects in the MIB are defined using the mechanisms
defined in the Structure of Management Information (SMI). This defined in the Structure of Management Information (SMI). This
memo specifies a MIB module that is compliant to the SMIv2, which memo specifies a MIB module that is compliant to the SMIv2, which
is described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579 is described in STD 58,RFC 2578 [RFC2578], STD 58, RFC 2579
[RFC2579] and STD 58, RFC 2580 [RFC2580]. [RFC2579] and STD 58, RFC 2580 [RFC2580].
4. PCEP MIB Module Architecture 4. PCEP MIB Module Architecture
The PCEP MIB will contain the following information: The PCEP MIB will contain the following information:
a. PCEP client configuration and status. a. PCEP client configuration and status.
b. PCEP peer configuration and information. b. PCEP peer configuration and information.
c. PCEP session configuration and information. c. PCEP session configuration and information.
d. Notifications to indicate PCEP session changes. d. Notifications to indicate PCEP session changes.
4.1. Relations to other MIB modules 4.1. Relations to other MIB modules
TBD TBD
5 Example of the PCEP MIB module usage 5. Example of the PCEP MIB module usage
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
TBD TBD
6 Object definitions 6. Object definitions
6.1 PCE-PCEP-DRAFT-MIB 6.1 PCE-PCEP-DRAFT-MIB
This MIB module makes references to the following documents. This MIB module makes references to the following documents.
[RFC2578], [RFC2579], [RFC2580], [RFC3411], [RFC2578], [RFC2579], [RFC2580], [RFC3411], [RFC2863], [RFC4001],
[RFC2863], [RFC4001], [RFC4265] and [RFC3813]. [RFC4265] and [RFC3813].
PCE-PCEP-DRAFT-MIB DEFINITIONS ::= BEGIN PCE-PCEP-DRAFT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
Counter32, Unsigned32, Gauge32, Integer32, IpAddress, Counter32, Unsigned32, Gauge32, Integer32, IpAddress,
experimental experimental
FROM SNMPv2-SMI FROM SNMPv2-SMI
RowStatus, TimeInterval, TruthValue, RowStatus, TimeInterval, TruthValue,
TimeStamp, StorageType,TEXTUAL-CONVENTION TimeStamp, StorageType,TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
skipping to change at page 5, line 4 skipping to change at page 5, line 6
Cisco Systems Inc. Cisco Systems Inc.
Stephan Emile Stephan Emile
France Telecom DR&D France Telecom DR&D
Email: kkoushik@cisco.com Email: kkoushik@cisco.com
Email: emile.stephan@orange-ft.com Email: emile.stephan@orange-ft.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
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
"This MIB module defines a collection of objects for managing "This MIB module defines a collection of objects for managing
PCE communication protocol(PCEP)." PCE communication protocol(PCEP)."
-- Revision history -- Revision history
REVISION REVISION
"200811031200Z" -- Nov 03 2008 12:00:00 EST "200811031200Z" -- Nov 03 2008 12:00:00 EST
DESCRIPTION DESCRIPTION
"Changes from -01- draft include support for the following "
Changes from -00- ietf draft include support for the following
in the MIB :
o Whether the PCEP speaker should initiate the PCEP session
or wait for initiation by the peer,
o A set of PCEP policies including the type of operations
allowed for the PCEP peer (e.g., diverse path computation,
synchronization, etc.),
o A scalar object restricting the set of PCEP peers
that can initiate a PCEP session with the PCEP speaker
(e.g., list of authorized PCEP peers, all PCEP peers in
the area, all PCEP peers in the AS).
Changes from -01- draft include support for the following
in the MIB : in the MIB :
o The SyncTimer, o The SyncTimer,
o The maximum number of sessions that can be setup, o The maximum number of sessions that can be setup,
o Request timer: amount of time a PCC waits for a reply o Request timer: amount of time a PCC waits for a reply
before resending its path computation requests before resending its path computation requests
(potentially to an alternate PCE). (potentially to an alternate PCE).
o The MAX-UNKNOWN-REQUESTS o The MAX-UNKNOWN-REQUESTS
o The MAX-UNKNOWN-MESSAGES o The MAX-UNKNOWN-MESSAGES
o Response time (minimum, average and maximum), on a o Response time (minimum, average and maximum), on a
per PCE Peer basis, per PCE Peer basis,
skipping to change at page 6, line 5 skipping to change at page 6, line 20
-- Textual Conventions used in this MIB module -- -- Textual Conventions used in this MIB module --
PcePcepIdentifier ::= TEXTUAL-CONVENTION PcePcepIdentifier ::= TEXTUAL-CONVENTION
DISPLAY-HINT "1d.1d.1d.1d:1d:1d" DISPLAY-HINT "1d.1d.1d.1d:1d:1d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The LDP identifier is a six octet "The LDP identifier is a six octet
quantity which is used to identify a quantity which is used to identify a
PCE client." PCE client."
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
SYNTAX OCTET STRING (SIZE (6)) SYNTAX OCTET STRING (SIZE (6))
-- Notifications -- -- Notifications --
pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepDraftMIB 0 } pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepDraftMIB 0 }
pcePcepMIBObjects OBJECT IDENTIFIER ::= { pcePcepDraftMIB 1 } pcePcepMIBObjects OBJECT IDENTIFIER ::= { pcePcepDraftMIB 1 }
pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepDraftMIB 2 } pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepDraftMIB 2 }
pcePcepClientObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 1 } pcePcepClientObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 1 }
skipping to change at page 6, line 50 skipping to change at page 7, line 17
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains an appropriate value to "This object contains an appropriate value to
be used for pcePcepClientIndex when creating be used for pcePcepClientIndex when creating
entries in the pcePcepClientTable. The value entries in the pcePcepClientTable. The value
0 indicates that no unassigned entries are 0 indicates that no unassigned entries are
available." available."
::= { pcePcepClientObjects 2 } ::= { pcePcepClientObjects 2 }
pcePcepClientSessionAuth OBJECT-TYPE
SYNTAX INTEGER {
AllPcepPeersInArea(1),
AllPcepPeersInAS(2),
OnlyAuthorizedPeers(3)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object indicates which peers can start
a PCEP session with the PCEP speaker. The value
of this object is only applicable if this system
can be a PCEP speaker."
::= { pcePcepClientObjects 2 }
pcePcepClientTable OBJECT-TYPE pcePcepClientTable OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepClientEntry SYNTAX SEQUENCE OF PcePcepClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
"This table contains information about the "This table contains information about the
PCEP Client." PCEP Client."
::= { pcePcepClientObjects 3 } ::= { pcePcepClientObjects 4 }
pcePcepClientEntry OBJECT-TYPE pcePcepClientEntry OBJECT-TYPE
SYNTAX PcePcepClientEntry SYNTAX PcePcepClientEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a PCEP client. "An entry in this table represents a PCEP client.
An entry can be created by a network administrator An entry can be created by a network administrator
or by an SNMP agent as instructed by PCEP." or by an SNMP agent as instructed by PCEP."
INDEX { pcePcepClientPcepId, pcePcepClientIndex } INDEX { pcePcepClientPcepId, pcePcepClientIndex }
skipping to change at page 7, line 31 skipping to change at page 8, line 14
PcePcepClientEntry ::= SEQUENCE { PcePcepClientEntry ::= SEQUENCE {
pcePcepClientPcepId PcePcepIdentifier, pcePcepClientPcepId PcePcepIdentifier,
pcePcepClientIndex Unsigned32, pcePcepClientIndex Unsigned32,
pcePcepClientAdminStatus INTEGER, pcePcepClientAdminStatus INTEGER,
pcePcepClientOperStatus INTEGER, pcePcepClientOperStatus INTEGER,
pcePcepClientTcpPort InetPortNumber, pcePcepClientTcpPort InetPortNumber,
pcePcepClientKeepAliveTimer Unsigned32, pcePcepClientKeepAliveTimer Unsigned32,
pcePcepClientStorageType StorageType, pcePcepClientStorageType StorageType,
pcePcepClientRowStatus RowStatus, pcePcepClientRowStatus RowStatus,
pcePcepClientDeadTimer Unsigned32 pcePcepClientDeadTimer Unsigned32,
pcePcepClientInitSession TruthValue,
pcePcepClientPoliciesAllowed INTEGER
} }
pcePcepClientPcepId OBJECT-TYPE pcePcepClientPcepId OBJECT-TYPE
SYNTAX PcePcepIdentifier SYNTAX PcePcepIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PCEP client identifier." "The PCEP client identifier."
::= { pcePcepClientEntry 1 } ::= { pcePcepClientEntry 1 }
skipping to change at page 8, line 4 skipping to change at page 8, line 39
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This index is used to uniquely identify the PCEP client. "This index is used to uniquely identify the PCEP client.
Before creating a row in this table, Before creating a row in this table,
the 'pcePcepClientIndexNext' object should be retrieved. the 'pcePcepClientIndexNext' object should be retrieved.
That value should be used for the value of this index That value should be used for the value of this index
when creating a row in this table. NOTE: if a value when creating a row in this table. NOTE: if a value
of zero (0) is retrieved, that indicates that no rows of zero (0) is retrieved, that indicates that no rows
can be created in this table at this time." can be created in this table at this time."
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
::= { pcePcepClientEntry 2 } ::= { pcePcepClientEntry 2 }
pcePcepClientAdminStatus OBJECT-TYPE pcePcepClientAdminStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
enable(1), enable(1),
disable(2) disable(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 9, line 5 skipping to change at page 9, line 52
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational status of this PCEP client. "The operational status of this PCEP client.
The value of unknown(1) indicates that the The value of unknown(1) indicates that the
operational status cannot be determined at operational status cannot be determined at
this time. The value of unknown should be this time. The value of unknown should be
a transient condition before changing a transient condition before changing
to enabled(2) or disabled(3)." to enabled(2) or disabled(3)."
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
::= { pcePcepClientEntry 5 } ::= { pcePcepClientEntry 5 }
pcePcepClientTcpPort OBJECT-TYPE pcePcepClientTcpPort OBJECT-TYPE
SYNTAX InetPortNumber SYNTAX InetPortNumber
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TCP Port for "The TCP Port for
PCEP. The default value is the well-known PCEP. The default value is the well-known
value of this port." -- To be assigned by IANA value of this port." -- To be assigned by IANA
skipping to change at page 10, line 4 skipping to change at page 10, line 51
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The status of this conceptual row. All writable "The status of this conceptual row. All writable
objects in this row may be modified at any objects in this row may be modified at any
time, however, as described in detail in time, however, as described in detail in
the section entitled, 'Changing Values After the section entitled, 'Changing Values After
Session Establishment', and again described Session Establishment', and again described
in the DESCRIPTION clause of the in the DESCRIPTION clause of the
pcePcepClientAdminStatus object, if a session pcePcepClientAdminStatus object, if a session
has been initiated with a Peer, changing objects has been initiated with a Peer, changing objects
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
in this table will wreak havoc with the session in this table will wreak havoc with the session
and interrupt traffic. To repeat again: and interrupt traffic. To repeat again:
the recommended procedure is to the recommended procedure is to
set the pcePcepClientAdminStatus to down, thereby set the pcePcepClientAdminStatus to down, thereby
explicitly causing a session to be torn down. Then, explicitly causing a session to be torn down. Then,
change objects in this entry, then set change objects in this entry, then set
the pcePcepClientAdminStatus to enable, the pcePcepClientAdminStatus to enable,
which enables a new session to be initiated." which enables a new session to be initiated."
::= { pcePcepClientEntry 9 } ::= { pcePcepClientEntry 9 }
skipping to change at page 10, line 30 skipping to change at page 11, line 24
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value which indicates a period of "The value which indicates a period of
time after the expiration of which a PCEP peer time after the expiration of which a PCEP peer
declares the session down if no PCEP message declares the session down if no PCEP message
has been received. The Deadtimer value is recommended to has been received. The Deadtimer value is recommended to
be 4 times the Keepalive value." be 4 times the Keepalive value."
::= { pcePcepClientEntry 10 } ::= { pcePcepClientEntry 10 }
pcepPcepClientInitSession OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value indicates if the PCEP client should initiate
PCEP session or wait for initiation by the peer.
If the value is true(1) then this client will initiate
the session. If the value is false(2) the it has to
wait for the peer to initiate a session."
DEFVAL{ false }
::= { pcePcepClientEntry 11 }
pcePcepClientPoliciesAllowed OBJECT-TYPE
SYNTAX INTEGER {
independentNonSyncPathComp(1)
independentSyncPathComp(2),
dependentSyncPathComp(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The value indicates the set of operation types allowed
for this client."
::= { pcePcepClientEntry 12 }
-- --
-- The PCEP Client Statistics Table -- The PCEP Client Statistics Table
-- TBD -- TBD
-- --
-- --
-- The PCEP Peer Table -- The PCEP Peer Table
-- --
pcePcepSessionObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 3 } pcePcepSessionObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 3 }
pcePcepPeerLastChange OBJECT-TYPE pcePcepPeerLastChange OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 11, line 4 skipping to change at page 12, line 24
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time of the most "The value of sysUpTime at the time of the most
recent addition or deletion to/from the recent addition or deletion to/from the
pcePcepPeerTable/pcePcepSessionTable." pcePcepPeerTable/pcePcepSessionTable."
::= { pcePcepSessionObjects 1 } ::= { pcePcepSessionObjects 1 }
pcePcepPeerTable OBJECT-TYPE pcePcepPeerTable OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepPeerEntry SYNTAX SEQUENCE OF PcePcepPeerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
DESCRIPTION DESCRIPTION
"Information about PCEP peers known by Entities in "Information about PCEP peers known by Entities in
the pcePcepClientTable. The information in this table the pcePcepClientTable. The information in this table
is based on information from the Client-Peer interaction is based on information from the Client-Peer interaction
during session initialization but is not appropriate during session initialization but is not appropriate
for the pcePcepSessionTable, because objects in this for the pcePcepSessionTable, because objects in this
table may or may not be used in session establishment." table may or may not be used in session establishment."
::= { pcePcepSessionObjects 2 } ::= { pcePcepSessionObjects 2 }
pcePcepPeerEntry OBJECT-TYPE pcePcepPeerEntry OBJECT-TYPE
skipping to change at page 11, line 52 skipping to change at page 13, line 21
pcePcepPeerTransportAddrType OBJECT-TYPE pcePcepPeerTransportAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the Internet address for the "The type of the Internet address for the
pcePcepPeerTransportAddr object. The PCEP pcePcepPeerTransportAddr object. The PCEP
specification describes this as being either specification describes this as being either
an IPv4 Transport Address or IPv6 Transport an IPv4 Transport Address or IPv6 Transport
This object specifies how the value of the This object specifies how the value of the
pcePcepPeerTransportAddr object should be pcePcepPeerTransportAddr object should be
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
interpreted." interpreted."
::= { pcePcepPeerEntry 2 } ::= { pcePcepPeerEntry 2 }
pcePcepPeerTransportAddr OBJECT-TYPE pcePcepPeerTransportAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Internet address advertised by the peer. "The Internet address advertised by the peer.
skipping to change at page 13, line 4 skipping to change at page 14, line 23
pcePcepSessionMaxUnknownRequests OBJECT-TYPE pcePcepSessionMaxUnknownRequests OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of unknown requests that any session "The maximum number of unknown requests that any session
on this PCEP client is willing to accept." on this PCEP client is willing to accept."
::= { pcePcepSessionObjects 4 } ::= { pcePcepSessionObjects 4 }
pcePcepSessionMaxUnknownMsgs OBJECT-TYPE pcePcepSessionMaxUnknownMsgs OBJECT-TYPE
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of unknown messages that any session "The maximum number of unknown messages that any session
on this PCEP client is willing to accept." on this PCEP client is willing to accept."
::= { pcePcepSessionObjects 5 } ::= { pcePcepSessionObjects 5 }
pcePcepSessionFailures OBJECT-TYPE pcePcepSessionFailures OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
skipping to change at page 14, line 4 skipping to change at page 15, line 27
PcePcepSessionEntry ::= SEQUENCE { PcePcepSessionEntry ::= SEQUENCE {
pcePcepSessionStateLastChange TimeStamp, pcePcepSessionStateLastChange TimeStamp,
pcePcepSessionState INTEGER, pcePcepSessionState INTEGER,
pcePcepSessionKeepAliveHoldTimeRem TimeInterval, pcePcepSessionKeepAliveHoldTimeRem TimeInterval,
pcePcepSessionKeepAliveTime Unsigned32, pcePcepSessionKeepAliveTime Unsigned32,
pcePcepSessionDiscontinuityTime TimeStamp, pcePcepSessionDiscontinuityTime TimeStamp,
pcePcepSessionSpeakerRole INTEGER, pcePcepSessionSpeakerRole INTEGER,
pcePcepSessionSyncTime Unsigned32, pcePcepSessionSyncTime Unsigned32,
pcePcepSessionActiveTime Unsigned32, pcePcepSessionActiveTime Unsigned32,
pcePcepSessionCorruptedMsgs Unsigned32, pcePcepSessionCorruptedMsgs Unsigned32,
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
pcePcepSessionFailedComps Unsigned32 pcePcepSessionFailedComps Unsigned32
} }
pcePcepSessionStateLastChange OBJECT-TYPE pcePcepSessionStateLastChange OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime at the time this "The value of sysUpTime at the time this
Session entered its current state as Session entered its current state as
skipping to change at page 15, line 4 skipping to change at page 16, line 23
pcePcepSessionKeepAliveTime OBJECT-TYPE pcePcepSessionKeepAliveTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The negotiated KeepAlive Time which "The negotiated KeepAlive Time which
represents the amount of seconds between represents the amount of seconds between
keep alive messages. The keep alive messages. The
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
pcePcepClientKeepAliveHoldTimer pcePcepClientKeepAliveHoldTimer
related to this Session is the related to this Session is the
value that was proposed as the value that was proposed as the
KeepAlive Time for this session KeepAlive Time for this session
This value is negotiated during This value is negotiated during
session initialization between session initialization between
the entity's proposed value the entity's proposed value
(i.e., the value configured in (i.e., the value configured in
pcePcepClientKeepAliveHoldTimer) pcePcepClientKeepAliveHoldTimer)
skipping to change at page 16, line 4 skipping to change at page 17, line 22
pcePcepSessionSpeakerRole OBJECT-TYPE pcePcepSessionSpeakerRole OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
pcc(1), pcc(1),
pce(2), pce(2),
pccandpce(3) pccandpce(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of this object indicates the PCEP "The value of this object indicates the PCEP
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
speaker role in this session." speaker role in this session."
::= { pcePcepSessionEntry 6 } ::= { pcePcepSessionEntry 6 }
pcePcepSessionSyncTime OBJECT-TYPE pcePcepSessionSyncTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of SYNC timer is used in the case "The value of SYNC timer is used in the case
skipping to change at page 17, line 5 skipping to change at page 18, line 26
pcePcepSessionActiveTime OBJECT-TYPE pcePcepSessionActiveTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The amount of time this session has been active "The amount of time this session has been active
since creation or a discontinuity." since creation or a discontinuity."
::= { pcePcepSessionEntry 9 } ::= { pcePcepSessionEntry 9 }
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
pcePcepSessionCorruptedMsgs OBJECT-TYPE pcePcepSessionCorruptedMsgs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of corrupted messages received on this "The number of corrupted messages received on this
session." session."
::= { pcePcepSessionEntry 10 } ::= { pcePcepSessionEntry 10 }
pcePcepSessionCorruptedMsgs OBJECT-TYPE pcePcepSessionCorruptedMsgs OBJECT-TYPE
skipping to change at page 18, line 5 skipping to change at page 19, line 23
pcePcepSessionDiscontinuityTime pcePcepSessionDiscontinuityTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is sent when the "This notification is sent when the
value of 'pcePcepSessionState' leaves value of 'pcePcepSessionState' leaves
the 'sessionUp(1)' state." the 'sessionUp(1)' state."
::= { pcePcepNotifications 2 } ::= { pcePcepNotifications 2 }
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
--**************************************************************** --****************************************************************
-- Module Conformance Statement -- Module Conformance Statement
--**************************************************************** --****************************************************************
pcePcepGroups pcePcepGroups
OBJECT IDENTIFIER ::= { pcePcepConformance 1 } OBJECT IDENTIFIER ::= { pcePcepConformance 1 }
pcePcepCompliances pcePcepCompliances
OBJECT IDENTIFIER ::= { pcePcepConformance 2 } OBJECT IDENTIFIER ::= { pcePcepConformance 2 }
skipping to change at page 19, line 4 skipping to change at page 20, line 22
"The Module is implemented with support "The Module is implemented with support
for read-only. In other words, only monitoring for read-only. In other words, only monitoring
is available by implementing this MODULE-COMPLIANCE." is available by implementing this MODULE-COMPLIANCE."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { pcePcepGeneralGroup, MANDATORY-GROUPS { pcePcepGeneralGroup,
pcePcepNotificationsGroup pcePcepNotificationsGroup
} }
::= { pcePcepCompliances 2 } ::= { pcePcepCompliances 2 }
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
-- units of conformance -- units of conformance
pcePcepGeneralGroup OBJECT-GROUP pcePcepGeneralGroup OBJECT-GROUP
OBJECTS { OBJECTS {
pcePcepClientLastChange, pcePcepClientLastChange,
pcePcepClientIndexNext, pcePcepClientIndexNext,
pcePcepClientAdminStatus, pcePcepClientAdminStatus,
pcePcepClientOperStatus, pcePcepClientOperStatus,
pcePcepClientTcpPort, pcePcepClientTcpPort,
pcePcepClientKeepAliveTimer, pcePcepClientKeepAliveTimer,
skipping to change at page 19, line 28 skipping to change at page 20, line 43
pcePcepClientRowStatus, pcePcepClientRowStatus,
pcePcepPeerLastChange, pcePcepPeerLastChange,
pcePcepPeerTransportAddrType, pcePcepPeerTransportAddrType,
pcePcepPeerTransportAddr, pcePcepPeerTransportAddr,
pcePcepSessionStateLastChange, pcePcepSessionStateLastChange,
pcePcepSessionState, pcePcepSessionState,
pcePcepSessionKeepAliveHoldTimeRem, pcePcepSessionKeepAliveHoldTimeRem,
pcePcepSessionKeepAliveTime, pcePcepSessionKeepAliveTime,
pcePcepSessionDiscontinuityTime, pcePcepSessionDiscontinuityTime,
pcePcepClientDeadTimer, pcePcepClientDeadTimer,
pcePcepClientInitSession,
pcePcepClientPoliciesAllowed,
pcePcepSessionMax, pcePcepSessionMax,
pcePcepSessionSpeakerRole, pcePcepSessionSpeakerRole,
pcePcepClientSyncTime, pcePcepClientSyncTime,
pcePcepClientRequestTime, pcePcepClientRequestTime,
pcePcepSessionMaxUnknownRequests, pcePcepSessionMaxUnknownRequests,
pcePcepSessionMaxUnknownMsgs, pcePcepSessionMaxUnknownMsgs,
pcePcepSessionSessionFailures, pcePcepSessionSessionFailures,
pcePcepSessionActiveTime, pcePcepSessionActiveTime,
pcePcepSessionCorruptedMsgs, pcePcepSessionCorruptedMsgs,
pcePcepSessionFailedComps pcePcepSessionFailedComps
skipping to change at page 19, line 50 skipping to change at page 21, line 17
DESCRIPTION DESCRIPTION
"Objects that apply to all PCEP MIB implementations." "Objects that apply to all PCEP MIB implementations."
::= { pcePcepGroups 1 } ::= { pcePcepGroups 1 }
pcePcepNotificationsGroup NOTIFICATION-GROUP pcePcepNotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS { pcePcepSessionUp, NOTIFICATIONS { pcePcepSessionUp,
pcePcepSessionDown pcePcepSessionDown
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The notifications for a PCEP MIB implementation." "The notifications for a PCEP MIB implementation."
::= { pcePcepGroups 2 } ::= { pcePcepGroups 2 }
END END
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
7. Security Considerations 7. Security Considerations
These MIB modules can be used for configuration of certain objects, These MIB modules can be used for configuration of certain objects,
and anything that can be configured can be incorrectly configured, and anything that can be configured can be incorrectly configured,
with potentially disastrous results. with potentially disastrous results.
There are a number of management objects defined in these MIB modules There are a number of management objects defined in these MIB modules
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
TBD
<The tables and objects and their sensitivies will be added in a
future version of this document>
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec),
even then, there is no control as to who on the secure network is
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
8. IANA Considerations 8. IANA Considerations
IANA is requested to make a MIB OID assignment for pceStdMIB under
the mib-2 branch. The MIB module in this document uses the following
IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers
registry:
9. References Descriptor OBJECT IDENTIFIER value
---------- -----------------------
pceStdMIB { mib-2 XXX }
IANA is requested to root MIB objects in the MIB module contained in
this document under the mib-2 subtree.
9. References
9.1 Normative References 9.1 Normative References
[PCEP] Path Computation Element (PCE) communication Protocol [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
(PCEP), Requirement Levels", BCP 14, RFC 2119, March 1997.
JP. Vasseur, JL. Le Roux
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance Statements J., Rose, M., and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999. for SMIv2", STD 58, RFC 2580, April 1999.
9.2. Informative References [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
10. Acknowledgement
The authors would like to thank Santanu Mazumder and Meral
Shirazipour for their valuable input.
11. Authors' Addresses
A S Kiran Koushik
Cisco Systems Inc.
Email: kkoushik@cisco.com
Stephan Emile [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
France Telecom Architecture for Describing Simple Network Management
2 avenue Pierre Marzin Protocol (SNMP) Management Frameworks", STD 62, RFC
Lannion, F-22307 3411, December 2002.
Email: emile.stephan@orange-ftgroup.com
Full Copyright Statement [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "MPLS
Multiprotocol Label Switching (MPLS) Label Switch Router
Management Information Base ", RFC 3813, June 2004
Copyright (c) 2009 IETF Trust and the persons identified as the [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
document authors. All rights reserved. Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005.
[RFC4265] Schliesser, B. and T. Nadeau, "Definition of Textual
Conventions for Virtual Private Network (VPN)
Management", RFC 4265, November 2005.
This document is subject to BCP 78 and the IETF Trust's Legal [RFC5440] Ayyangar, A., Farrel, A., Oki, E., Atlas, A., Dolganow
Provisions Relating to IETF Documents A. Ikejiri, Y., Kumaki, K., Vasseur, J., and J. Roux,
(http://trustee.ietf.org/license-info) in effect on the date of "Path Computation Element (PCE) communication Protocol
publication of this document. Please review these documents (PCEP)," RFC5440, March. 2009.
carefully, as they describe your rights and restrictions with respect
to this document.
All IETF Documents and the information contained therein are provided 9.2. Informative References
on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE
IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL
WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY
WARRANTY THAT THE USE OF THE INFORMATION THEREIN WILL NOT INFRINGE
ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE.
Intellectual Property Statement [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
The IETF takes no position regarding the validity or scope of any [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Intellectual Property Rights or other rights that might be claimed to Element (PCE)-Based Architecture", RFC 4655, August
pertain to the implementation or use of the technology described in 2006.
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
made any independent effort to identify any such rights.
draft-ietf-pce-pcep-mib-00 PCE-PCEP-MIB Jan 22, 2009 10. Acknowledgement
Copies of Intellectual Property disclosures made to the IETF The authors would like to thank Santanu Mazumder and Meral
Secretariat and any assurances of licenses to be made available, or Shirazipour for their valuable input.
the result of an attempt made to obtain a general license or
permission for the use of such proprietary rights by implementers or
users of this specification can be obtained from the IETF on-line IPR
repository at http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any Funding for the RFC Editor function is currently provided by the
copyrights, patents or patent applications, or other proprietary Internet Society.
rights that may cover technology that may be required to implement
any standard or specification contained in an IETF Document. Please
address the information to the IETF at ietf-ipr@ietf.org.
The definitive version of an IETF Document is that published by, or 11. Authors' Addresses
under the auspices of, the IETF. Versions of IETF Documents that are
published by third parties, including those that are translated into
other languages, should not be considered to be definitive versions
of IETF Documents. The definitive version of these Legal Provisions
is that published by, or under the auspices of, the IETF. Versions of
these Legal Provisions that are published by third parties, including
those that are translated into other languages, should not be
considered to be definitive versions of these Legal Provisions.
For the avoidance of doubt, each Contributor to the UETF Standards A S Kiran Koushik
Process licenses each Contribution that he or she makes as part of Cisco Systems Inc.
the IETF Standards Process to the IETF Trust pursuant to the Email: kkoushik@cisco.com
provisions of RFC 5378. No language to the contrary, or terms,
conditions or rights that differ from or are inconsistent with the
rights and licenses granted under RFC 5378, shall have any effect and
shall be null and void, whether published or posted by such
Contributor, or included with or in such Contribution.
Acknowledgment Stephan Emile
France Telecom
2 avenue Pierre Marzin
Lannion, F-22307
Email: emile.stephan@orange-ftgroup.com
Quintin Zhao
Huawei Technology
125 Nagog Technology Park
Acton, MA 01719
US
Email: qzhao@huawei.com
Funding for the RFC Editor function is currently provided by the Daniel King
Internet Society. Old Dog Consulting
UK
Email: daniel@olddog.co.uk
 End of changes. 70 change blocks. 
212 lines changed or deleted 236 lines changed or added

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