draft-ietf-pce-pcep-mib-01.txt   draft-ietf-pce-pcep-mib-02.txt 
Internet Engineering Task Force A S Kiran Koushik Internet Engineering Task Force A S Kiran Koushik
Internet Draft Cisco Systems, Inc. Internet Draft Cisco Systems, Inc.
Intended Status: Standards Track E. Stephan Intended Status: Standards Track E. Stephan
Created: March 8, 2010 France Telecom Expires: January 6, 2011 France Telecom
Expires: September 8, 2010 Quintin Zhao Quintin Zhao
Huawei Technology Huawei Technology
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
July 6 2010
PCE communication protocol(PCEP) Management Information Base PCE communication protocol(PCEP) Management Information Base
draft-ietf-pce-pcep-mib-01.txt draft-ietf-pce-pcep-mib-02.txt
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines an experimental portion of the Management
Information Base for use with network management protocols in the Information Base for use with network management protocols in the
Internet community. In particular, it describes managed objects Internet community. In particular, it describes managed objects
for modeling of Path Computation Element communication for modeling of Path Computation Element communication
Protocol (PCEP) for communications between a Path Computation Client Protocol (PCEP) for communications between a Path Computation Client
(PCC) and a Path Computation Element (PCE), or between two PCEs. (PCC) and a Path Computation Element (PCE), or between two PCEs.
skipping to change at page 1, line 45 skipping to change at page 1, line 46
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 8, 2010. This Internet-Draft will expire on January 6, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with carefully, as they describe your rights and restrictions with
respect to this document. Code Components extracted from this respect to this document. Code Components extracted from this
document must include Simplified BSD License text as described in document must include Simplified BSD License text as described in
Section 4.e of the Trust Legal Provisions and are provided without Section 4.e of the Trust Legal Provisions and are provided without
warranty as described in the Simplified BSD License. warranty as described in the Simplified BSD License.
Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in BCP 14,
RFC 2119 [RFC2119].
Table of Contents Table of Contents
Abstract............................................................ Abstract.........................................................
1. Introduction..................................................... 1. Introduction..................................................
2. Terminology...................................................... 2. Terminology...................................................
3. The Internet-Standard Management Framework....................... 3. The Internet-Standard Management Framework....................
4. PCEP MIB modules Architecture.................................... 4. PCEP MIB modules Architecture.................................
4.1 Relations to other MIB modules................................ 4.1 Relations to other MIB modules.............................
5. Example of the PCEP MIB modules usage ........................... 5. Example of the PCEP MIB modules usage ........................
6. Object definitions............................................... 6. Object Definitions............................................
6.1 PCE-PCEP-DRAFT-MIB.......................................... 6.1 PCE-PCEP-DRAFT-MIB.......................................
7. Security considerations.......................................... 7. Security Considerations.......................................
8. IANA Considerations.............................................. 8. IANA Considerations...........................................
9. References....................................................... 9. References....................................................
9.1. Normative References........................................ 9.1. Normative References.....................................
9.2. Informative References...................................... 9.2. Informative References...................................
10. Acknowledgement ................................................ 10. Acknowledgement .............................................
11. Author's Addresses.............................................. 11. Author's Addresses...........................................
1. Introduction 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 the communication protocol
between a PCC and PCE for point-to-point (P2P) path computations and
is defined in [RFC5440]. Such PCEP communication interactions include
path computation requests and path computation replies as well as
notifications of specific states related to the use of a PCE in the
context of Multiprotocol Label Switching (MPLS) and Generalized MPLS
(GMPLS) Traffic Engineering.
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 PCEP communications between a PCC and a PCE, or
Protocol (PCEP) [RFC5440] for communications between a Path
Computation Client(PCC) and a Path Computation Element (PCE), or
between two PCEs. between two PCEs.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL
NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in
[RFC2119].
Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in BCP 14,
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.
skipping to change at page 3, line 54 skipping to change at page 4, line 16
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 PCEP relies on existing protocols which have specialized MIB
objects to monitor their own activities. Consequently this document
considers that the monitoring underlying protocols are out of scope
of the PCEP MIB module.
5. Example of the PCEP MIB module usage 5. Example of the PCEP MIB module usage
TBD In this section we provide an example of using the MIB objects
described in Section 6. (Object definitions) to monitor. While
this example is not meant to illustrate every permutation of the
MIB, it is intended as an aid to understanding some of the key
concepts. It is meant to be read after going through the MIB
itself.
6. Object definitions In the PCE-PCEP-DRAFT-MIB module:
{
pcePcepClientPcepId (1d.1d.1d.1d:1d:1d)
pcePcepClientIndex (10)
pcePcepClientAdminStatus enable(1),
pcePcepClientTcpPort (4189),
pcePcepClientKeepAliveTimer (10),
pcePcepClientStorageType permanent(4),
pcePcepClientDeadTimer (40),
pcePcepClientInitSession true (1),
pcePcepClientPoliciesAllowed independentSyncPathComp(2),
}
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], [RFC2863], [RFC4001], [RFC2578], [RFC2579], [RFC2580], [RFC3411], [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, Unsigned32,
experimental experimental
FROM SNMPv2-SMI FROM SNMPv2-SMI
PcePcepIdentifier,
FROM PCE-TC-STD-MIB
RowStatus, TimeInterval, TruthValue, RowStatus, TimeInterval, TruthValue,
TimeStamp, StorageType,TEXTUAL-CONVENTION TimeStamp, StorageType,TEXTUAL-CONVENTION
FROM SNMPv2-TC -- [RFC2579] FROM SNMPv2-TC -- [RFC2579]
InetAddressPrefixLength,
InetAddressType, InetAddressType,
InetAddress, InetAddress,
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF; FROM SNMPv2-CONF;
pcePcepDraftMIB MODULE-IDENTITY pcePcepDraftMIB MODULE-IDENTITY
LAST-UPDATED "200811030000Z" --Nov 3, 2008 LAST-UPDATED "201006181200Z" --July 6, 2010
ORGANIZATION "Path Computation Element (PCE) Working Group" ORGANIZATION "Path Computation Element (PCE) Working Group"
CONTACT-INFO " CONTACT-INFO "
A S Kiran Koushik A S Kiran Koushik
Cisco Systems Inc. Cisco Systems Inc.
Stephan Emile Stephan Emile
France Telecom DR&D France Telecom DR&D
Quintin Zhao
Huawei Technology
Daniel King
OldDog Consulting
Email: kkoushik@cisco.com Email: kkoushik@cisco.com
Email: emile.stephan@orange-ft.com Email: emile.stephan@orange-ft.com
Email: zhao@huawei.com
Email: daniel@oldog.co.uk
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 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
"201006181200Z" -- 18 Jun 2010 12:00:00 EST
DESCRIPTION
"
Changes from -01- ietf draft include support for the
following in the MIB :
o Cleanup all the compiling errors;
o added text to Introduction, PCEP Module usage. "
REVISION REVISION
"200811031200Z" -- Nov 03 2008 12:00:00 EST "200811031200Z" -- Nov 03 2008 12:00:00 EST
DESCRIPTION DESCRIPTION
" "
Changes from -01- ietf draft include support for the
following in the MIB :
o Text added describing the relations to other MIB modules,
o Example of the PCEP MIB module usage added.
Changes from -00- ietf draft include support for the following Changes from -00- ietf draft include support for the following
in the MIB : in the MIB :
o Whether the PCEP speaker should initiate the PCEP session o Whether the PCEP speaker should initiate the PCEP session
or wait for initiation by the peer, or wait for initiation by the peer,
o A set of PCEP policies including the type of operations o A set of PCEP policies including the type of operations
allowed for the PCEP peer (e.g., diverse path computation, allowed for the PCEP peer (e.g., diverse path computation,
synchronization, etc.), synchronization, etc.),
o A scalar object restricting the set of PCEP peers o A scalar object restricting the set of PCEP peers
that can initiate a PCEP session with the PCEP speaker that can initiate a PCEP session with the PCEP speaker
(e.g., list of authorized PCEP peers, all PCEP peers in (e.g., list of authorized PCEP peers, all PCEP peers in
skipping to change at page 6, line 11 skipping to change at page 7, line 20
3. Did not add all the objects to manage the recommendations 3. Did not add all the objects to manage the recommendations
in draft-ietf-pce-pcep-08.txt to control the complexity of in draft-ietf-pce-pcep-08.txt to control the complexity of
the MIB." the MIB."
REVISION REVISION
"200702201200Z" -- 20 Feb 2007 12:00:00 EST "200702201200Z" -- 20 Feb 2007 12:00:00 EST
DESCRIPTION DESCRIPTION
"draft-00 version" "draft-00 version"
::= { experimental 9999 } -- ::= { experimental 9999 } --
-- Textual Conventions used in this MIB module --
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 (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 7, line 19 skipping to change at page 8, line 19
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 pcePcepClientSessionAuth OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
AllPcepPeersInArea(1), allPcepPeersInArea(1),
AllPcepPeersInAS(2), allPcepPeersInAS(2),
OnlyAuthorizedPeers(3) onlyAuthorizedPeers(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates which peers can start "This object indicates which peers can start
a PCEP session with the PCEP speaker. The value a PCEP session with the PCEP speaker. The value
of this object is only applicable if this system of this object is only applicable if this system
can be a PCEP speaker." can be a PCEP speaker."
::= { pcePcepClientObjects 2 } ::= { pcePcepClientObjects 3 }
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
"This table contains information about the "This table contains information about the
PCEP Client." PCEP Client."
::= { pcePcepClientObjects 4 } ::= { pcePcepClientObjects 4 }
skipping to change at page 9, line 33 skipping to change at page 10, line 20
to that session cease to exist). to that session cease to exist).
At this point the operator is able to change values At this point the operator is able to change values
which are related to this entity. which are related to this entity.
When the admin status is set back to 'enable', then When the admin status is set back to 'enable', then
this Entity will attempt to establish a new session this Entity will attempt to establish a new session
with the Peer." with the Peer."
DEFVAL { enable } DEFVAL { enable }
::= { pcePcepClientEntry 4 } ::= { pcePcepClientEntry 3 }
pcePcepClientOperStatus OBJECT-TYPE pcePcepClientOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
enabled(2), enabled(2),
disabled(3) disabled(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
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)."
::= { pcePcepClientEntry 5 } ::= { pcePcepClientEntry 4 }
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
::= { pcePcepClientEntry 6 } ::= { pcePcepClientEntry 5 }
pcePcepClientKeepAliveTimer OBJECT-TYPE pcePcepClientKeepAliveTimer OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The integer value which is the proposed keep "The integer value which is the proposed keep
alive timer for this PCEP client." alive timer for this PCEP client."
::= { pcePcepClientEntry 7 } ::= { pcePcepClientEntry 6 }
pcePcepClientStorageType OBJECT-TYPE pcePcepClientStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
objects in the row." objects in the row."
DEFVAL{ nonVolatile } DEFVAL{ nonVolatile }
::= { pcePcepClientEntry 8 } ::= { pcePcepClientEntry 7 }
pcePcepClientRowStatus OBJECT-TYPE pcePcepClientRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
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
skipping to change at page 11, line 9 skipping to change at page 11, line 49
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
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 8 }
pcePcepClientDeadTimer OBJECT-TYPE pcePcepClientDeadTimer OBJECT-TYPE
SYNTAX Unsigned32 (4..262140) SYNTAX Unsigned32 (4..262140)
UNITS "seconds" UNITS "seconds"
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 9 }
pcepPcepClientInitSession OBJECT-TYPE pcePcepClientInitSession OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value indicates if the PCEP client should initiate "The value indicates if the PCEP client should initiate
PCEP session or wait for initiation by the peer. PCEP session or wait for initiation by the peer.
If the value is true(1) then this client will initiate If the value is true(1) then this client will initiate
the session. If the value is false(2) the it has to the session. If the value is false(2) the it has to
wait for the peer to initiate a session." wait for the peer to initiate a session."
DEFVAL{ false } DEFVAL{ false }
::= { pcePcepClientEntry 11 } ::= { pcePcepClientEntry 10 }
pcePcepClientPoliciesAllowed OBJECT-TYPE pcePcepClientPoliciesAllowed OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
independentNonSyncPathComp(1) independentNonSyncPathComp(1),
independentSyncPathComp(2), independentSyncPathComp(2),
dependentSyncPathComp(3) dependentSyncPathComp(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value indicates the set of operation types allowed "The value indicates the set of operation types allowed
for this client." for this client. Need to explain these three values.
::= { pcePcepClientEntry 12 } Are the mutually incombaitble. Is it a set (bits - 1 2 4)
or choice (integer)"
::= { pcePcepClientEntry 11 }
--
-- The PCEP Client Statistics Table -- The PCEP Client Statistics Table
-- 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
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 }
skipping to change at page 12, line 47 skipping to change at page 13, line 41
DESCRIPTION DESCRIPTION
"Information about a single Peer which is related "Information about a single Peer which is related
to a Session. This table is augmented by to a Session. This table is augmented by
the pcePcepSessionTable." the pcePcepSessionTable."
INDEX { pcePcepClientPcepId, INDEX { pcePcepClientPcepId,
pcePcepClientIndex, pcePcepClientIndex,
pcePcepPeerPcepId } pcePcepPeerPcepId }
::= { pcePcepPeerTable 1 } ::= { pcePcepPeerTable 1 }
PcePcepPeerEntry ::= SEQUENCE { PcePcepPeerEntry ::= SEQUENCE {
pcePcepPeerPcepId PcePcepIdentifier, pcePcepPeerPcepId PcePcepIdentifier,
pcePcepPeerTransportAddrType InetAddressType, pcePcepPeerTransportAddrType InetAddressType,
pcePcepPeerTransportAddr InetAddress pcePcepPeerTransportAddr InetAddress,
pcePcepPeerResponseTime Unsigned32
} }
pcePcepPeerPcepId OBJECT-TYPE pcePcepPeerPcepId OBJECT-TYPE
SYNTAX PcePcepIdentifier SYNTAX PcePcepIdentifier
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The PCEP identifier of this PCE Peer." "The PCEP identifier of this PCE Peer."
::= { pcePcepPeerEntry 1 } ::= { pcePcepPeerEntry 1 }
pcePcepPeerTransportAddrType OBJECT-TYPE pcePcepPeerTransportAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
skipping to change at page 15, line 25 skipping to change at page 16, line 13
::= { pcePcepSessionTable 1 } ::= { pcePcepSessionTable 1 }
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,
pcePcepSessionRequestTime Unsigned32,
pcePcepSessionActiveTime Unsigned32, pcePcepSessionActiveTime Unsigned32,
pcePcepSessionCorruptedMsgs Unsigned32, pcePcepSessionCorruptedMsgs Unsigned32,
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
skipping to change at page 18, line 35 skipping to change at page 19, line 24
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 pcePcepSessionFailedComps OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of requests which had failed "The number of requests which had failed
computations." computations."
::= { pcePcepSessionEntry 11 } ::= { pcePcepSessionEntry 11 }
--- ---
--- Notifications --- Notifications
skipping to change at page 19, line 41 skipping to change at page 20, line 36
OBJECT IDENTIFIER ::= { pcePcepConformance 2 } OBJECT IDENTIFIER ::= { pcePcepConformance 2 }
-- --
-- Full Compliance -- Full Compliance
-- --
pcePcepModuleFullCompliance MODULE-COMPLIANCE pcePcepModuleFullCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Module is implemented with support "The Module is implemented with support
for read-create and read-write. In other for read-create. In other
words, both monitoring and configuration words, both monitoring and configuration
are available when using this MODULE-COMPLIANCE." are available when using this MODULE-COMPLIANCE."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { pcePcepGeneralGroup, MANDATORY-GROUPS { pcePcepGeneralGroup,
pcePcepNotificationsGroup pcePcepNotificationsGroup
} }
::= { pcePcepCompliances 1 } ::= { pcePcepCompliances 1 }
skipping to change at page 20, line 47 skipping to change at page 21, line 42
pcePcepSessionStateLastChange, pcePcepSessionStateLastChange,
pcePcepSessionState, pcePcepSessionState,
pcePcepSessionKeepAliveHoldTimeRem, pcePcepSessionKeepAliveHoldTimeRem,
pcePcepSessionKeepAliveTime, pcePcepSessionKeepAliveTime,
pcePcepSessionDiscontinuityTime, pcePcepSessionDiscontinuityTime,
pcePcepClientDeadTimer, pcePcepClientDeadTimer,
pcePcepClientInitSession, pcePcepClientInitSession,
pcePcepClientPoliciesAllowed, pcePcepClientPoliciesAllowed,
pcePcepSessionMax, pcePcepSessionMax,
pcePcepSessionSpeakerRole, pcePcepSessionSpeakerRole,
pcePcepClientSyncTime, pcePcepSessionSyncTime,
pcePcepClientRequestTime, pcePcepSessionRequestTime,
pcePcepSessionMaxUnknownRequests, pcePcepSessionMaxUnknownRequests,
pcePcepSessionMaxUnknownMsgs, pcePcepSessionMaxUnknownMsgs,
pcePcepSessionSessionFailures,
pcePcepSessionActiveTime, pcePcepSessionActiveTime,
pcePcepSessionCorruptedMsgs, pcePcepSessionCorruptedMsgs,
pcePcepClientSessionAuth,
pcePcepPeerResponseTime,
pcePcepSessionFailures,
pcePcepSessionSyncTime,
pcePcepSessionRequestTime,
pcePcepSessionFailedComps pcePcepSessionFailedComps
} }
STATUS current STATUS current
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,
skipping to change at page 21, line 25 skipping to change at page 22, line 26
} }
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
7. Security Considerations 7. Security Considerations
These MIB modules can be used for configuration of certain objects, This MIB module 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 this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of 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:
<The tables and objects and their sensitivies will be added in a o pcePcepClientTcpPort: A PCC or PCE listening in on the wrong TCO
future version of this document> port would mean PCEP communications would fail.
o pcePcepClientKeepAliveTimer: Changing the PCEP session keepalive
timer to a value lower than the default value, may force premature
PCEP communication time-outs.
o pcePcepClientStorageType: Changing this value may cause persitance
failure for the configuration.
o pcePcepClientRowStatus: Setting row status incorrectly may turn
off the PCEP client.
o pcePcepClientDeadTimer: Changing the PCEP session deadtimer timer
to a value lower than the default value, may force premature PCEP
communication time-outs.
o pcepPcepClientInitSession: Setting this value incorrectly may cause
the PCEP session not to come up.
o pcePcepClientPoliciesAllowed: Setting this value incorrectly may
cause specific PCE requests to fail.
The user of the PCE-PCEP-DRAFT-MIB module must therefore be aware
that support for SET operations in a non-secure environment without
proper protection can have a negative effect on network operations.
The readable objects in the PCE-PCEP-DRAFT-MIB module (i.e., those
with MAX-ACCESS other than not-accessible) may be considered
sensitive in some environments since, collectively, they provide
information about the amount and frequency of path computation
requests and responses within the network and can reveal some
aspects of their configuration.
In such environments it is important to control also GET and NOTIFY
access to these objects and possibly even to encrypt their values
when sending them over the network via SNMP.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPsec), 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 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 allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8), provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for including full support for the SNMPv3 cryptographic mechanisms (for
 End of changes. 51 change blocks. 
88 lines changed or deleted 166 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/