draft-ietf-pce-pcep-mib-06.txt   draft-ietf-pce-pcep-mib-07.txt 
PCE Working Group A. Koushik PCE Working Group A. Koushik
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Intended status: Standards Track S. Emile Intended status: Standards Track E. Stephan
Expires: July 13, 2014 France Telecom Expires: August 10, 2014 France Telecom
Q. Zhao Q. Zhao
Huawei Technology Huawei Technology
D. King D. King
Old Dog Consulting Old Dog Consulting
J. Hardwick J. Hardwick
Metaswitch Metaswitch
January 9, 2014 February 6, 2014
PCE communication protocol (PCEP) Management Information Base Path Computation Element Protocol (PCEP) Management Information Base
draft-ietf-pce-pcep-mib-06 draft-ietf-pce-pcep-mib-07
Abstract Abstract
This memo defines an experimental portion of the Management This memo defines a portion of the Management Information Base for
Information Base for use with network management protocols in the use with network management protocols in the Internet community. In
Internet community. In particular, it describes managed objects for particular, it describes managed objects for modeling of Path
modeling of Path Computation Element communication Protocol (PCEP) Computation Element communication Protocol (PCEP) for communications
for communications between a Path Computation Client (PCC) and a Path between a Path Computation Client (PCC) and a Path Computation
Computation Element (PCE), or between two PCEs. Element (PCE), or between two PCEs.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted 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). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 13, 2014. This Internet-Draft will expire on August 10, 2014.
Copyright Notice Copyright Notice
Copyright (c) 2014 IETF Trust and the persons identified as the Copyright (c) 2014 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
skipping to change at page 2, line 33 skipping to change at page 2, line 33
5.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . . 5 5.4. PCEP Notifications . . . . . . . . . . . . . . . . . . . . 5
5.5. Relationship to other MIB modules . . . . . . . . . . . . 5 5.5. Relationship to other MIB modules . . . . . . . . . . . . 5
6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 6 6. Object Definitions . . . . . . . . . . . . . . . . . . . . . . 6
6.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 6 6.1. PCE-PCEP-MIB . . . . . . . . . . . . . . . . . . . . . . . 6
7. Security Considerations . . . . . . . . . . . . . . . . . . . 45 7. Security Considerations . . . . . . . . . . . . . . . . . . . 45
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 45
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . . 46
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 46
10.1. Normative References . . . . . . . . . . . . . . . . . . . 46 10.1. Normative References . . . . . . . . . . . . . . . . . . . 46
10.2. Normative References . . . . . . . . . . . . . . . . . . . 46 10.2. Normative References . . . . . . . . . . . . . . . . . . . 46
Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . . 46 Appendix A. Acknowledgement . . . . . . . . . . . . . . . . . . . 47
1. Introduction 1. Introduction
The Path Computation Element (PCE) defined in [RFC4655] is an entity The Path Computation Element (PCE) defined in [RFC4655] is an entity
that is capable of computing a network path or route based on a that is capable of computing a network path or route based on a
network graph, and applying computational constraints. A Path network graph, and applying computational constraints. A Path
Computation Client (PCC) may make requests to a PCE for paths to be Computation Client (PCC) may make requests to a PCE for paths to be
computed. computed.
The PCE communication protocol (PCEP) is the communication protocol The PCE communication protocol (PCEP) is the communication protocol
skipping to change at page 3, line 38 skipping to change at page 3, line 38
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 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and ATD 58, RFC 2580 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579], and STD 58, RFC 2580
[RFC2580]. [RFC2580].
3. Requirements Language 3. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in BCP 14, RFC 2119 document are to be interpreted as described in BCP 14, RFC 2119
[RFC2119]. [RFC2119].
4. Terminology 4. Terminology
skipping to change at page 6, line 33 skipping to change at page 6, line 33
MODULE-COMPLIANCE, MODULE-COMPLIANCE,
OBJECT-GROUP, OBJECT-GROUP,
NOTIFICATION-GROUP NOTIFICATION-GROUP
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; -- RFC 4001 FROM INET-ADDRESS-MIB; -- RFC 4001
pcePcepMIB MODULE-IDENTITY pcePcepMIB MODULE-IDENTITY
LAST-UPDATED LAST-UPDATED
"201307152200Z" -- 15 July 2013 "201402051200Z" -- 5 February 2014
ORGANIZATION ORGANIZATION
"IETF Path Computation Element (PCE) Working Group" "IETF Path Computation Element (PCE) Working Group"
CONTACT-INFO CONTACT-INFO
"Email: pce@ietf.org "Email: pce@ietf.org
WG charter: WG charter:
http://www.ietf.org/html.charters/pce-charter.html" 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).
Copyright (C) The IETF Trust (2013). This version of this Copyright (C) The IETF Trust (2014). This version of this
MIB module is part of RFC YYYY; see the RFC itself for full MIB module is part of RFC YYYY; see the RFC itself for full
legal notices." legal notices."
-- RFC Ed,: replace YYYY with actual RFC number & remove this note -- RFC Ed,: replace YYYY with actual RFC number & remove this note
REVISION REVISION
"201307152200Z" -- 15 July 2013 "201402051200Z" -- 5 February 2014
DESCRIPTION DESCRIPTION
"Initial version, published as RFC YYYY." "Initial version, published as RFC YYYY."
-- RFC Ed.: replace YYYY with actual RFC number & remove this note -- RFC Ed.: replace YYYY with actual RFC number & remove this note
::= { mib-2 XXX } ::= { mib-2 XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this note -- RFC Ed.: replace XXX with IANA-assigned number & remove this note
pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 } pcePcepNotifications OBJECT IDENTIFIER ::= { pcePcepMIB 0 }
pcePcepMIBObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 } pcePcepObjects OBJECT IDENTIFIER ::= { pcePcepMIB 1 }
pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 } pcePcepConformance OBJECT IDENTIFIER ::= { pcePcepMIB 2 }
pcePcepEntityObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 1 } pcePcepEntityObjects OBJECT IDENTIFIER ::= { pcePcepObjects 1 }
-- --
-- PCE Entity Objects -- PCE Entity Objects
-- --
pcePcepEntityTable OBJECT-TYPE pcePcepEntityTable OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepEntityEntry SYNTAX SEQUENCE OF PcePcepEntityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information about the PCEP Entity." "This table contains information about PCEP Entities."
::= { pcePcepEntityObjects 1 } ::= { pcePcepEntityObjects 1 }
pcePcepEntityEntry OBJECT-TYPE pcePcepEntityEntry OBJECT-TYPE
SYNTAX PcePcepEntityEntry SYNTAX PcePcepEntityEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table represents a PCEP entity." "An entry in this table represents a PCEP entity."
INDEX { pcePcepEntityIndex } INDEX { pcePcepEntityIndex }
::= { pcePcepEntityTable 1 } ::= { pcePcepEntityTable 1 }
skipping to change at page 8, line 34 skipping to change at page 8, line 34
adminStatusDown(2) adminStatusDown(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The administrative status of this PCEP Entity." "The administrative status of this PCEP Entity."
::= { pcePcepEntityEntry 2 } ::= { pcePcepEntityEntry 2 }
pcePcepEntityOperStatus OBJECT-TYPE pcePcepEntityOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
operStatusUp(1), -- active operStatusUp(1),
operStatusDown(2), -- inactive operStatusDown(2),
operStatusGoingUp(3), -- activating operStatusGoingUp(3),
operStatusGoingDown(4), -- deactivating operStatusGoingDown(4),
operStatusFailed(5), -- failed, will recover operStatusFailed(5),
-- when possible operStatusFailedPerm(6)
operStatusFailedPerm(6) -- operator intervention
-- required
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The operational status of the PCEP entity." "The operational status of the PCEP entity. Takes one of the
following values.
- operStatusUp(1): the PCEP entity is active.
- operStatusDown(2): the PCEP entity is inactive.
- operStatusGoingUp(3): the PCEP entity is activating.
- operStatusGoingDown(4): the PCEP entity is deactivating.
- operStatusFailed(5): the PCEP entity has failed and will
recover when possible.
- operStatusFailedPerm(6): the PCEP entity has failed and
will not recover without operator intervention."
::= { pcePcepEntityEntry 3 } ::= { pcePcepEntityEntry 3 }
pcePcepEntityAddrType OBJECT-TYPE pcePcepEntityAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the PCEP entity's Internet address. This object "The type of the PCEP entity's Internet address. This object
specifies how the value of the pcePcepPeerAddr object should specifies how the value of the pcePcepEntityAddr object
be interpreted." should be interpreted."
::= { pcePcepEntityEntry 4 } ::= { pcePcepEntityEntry 4 }
pcePcepEntityAddr OBJECT-TYPE pcePcepEntityAddr OBJECT-TYPE
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Internet address of this PCEP entity. The type is given "The local Internet address of this PCEP entity. The type is
by pcePcepEntityAddrType. given by pcePcepEntityAddrType.
If operating as a PCE server, the PCEP entity listens on If operating as a PCE server, the PCEP entity listens on
this address. If operating as a PCC, the PCEP entity binds this address. If operating as a PCC, the PCEP entity binds
outgoing TCP connections to this address." outgoing TCP connections to this address.
It is possible for the PCEP entity to operate both as a PCC
and a PCE Server, in which case it uses this address both to
listen for incoming TCP connections and to bind outgoing
TCP connections."
::= { pcePcepEntityEntry 5 } ::= { pcePcepEntityEntry 5 }
pcePcepEntityConnectTimer OBJECT-TYPE pcePcepEntityConnectTimer 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 time that the PCEP entity will wait to establish a TCP "The time that the PCEP entity will wait to establish a TCP
connection with a PCEP peer. If a TCP connection is not connection with a PCEP peer. If a TCP connection is not
established within this time then PCEP aborts the session established within this time then PCEP aborts the session
setup attempt." setup attempt."
::= { pcePcepEntityEntry 6 } ::= { pcePcepEntityEntry 6 }
pcePcepEntityConnectMaxRetry OBJECT-TYPE pcePcepEntityConnectMaxRetry OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The maximum number of times the system tries to establish "The maximum number of times the system tries to establish
a TCP connection to a peer before going back to the Idle a TCP connection to a peer before going back to the Idle
state." state."
::= { pcePcepEntityEntry 7 } ::= { pcePcepEntityEntry 7 }
pcePcepEntityOpenWaitTimer OBJECT-TYPE pcePcepEntityOpenWaitTimer OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
skipping to change at page 14, line 32 skipping to change at page 14, line 44
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 entity is willing to accept per minute." on this PCEP entity is willing to accept per minute."
::= { pcePcepEntityEntry 23 } ::= { pcePcepEntityEntry 23 }
-- --
-- The PCEP Peer Table -- The PCEP Peer Table
-- --
pcePcepPeerObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 2 } pcePcepPeerObjects OBJECT IDENTIFIER ::= { pcePcepObjects 2 }
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
DESCRIPTION DESCRIPTION
"Information about PCEP peers known by the local PCEP "Information about PCEP peers known by the local PCEP
speaker. speaker.
This MIB table gives PCEP peer information that spans PCEP This MIB table gives PCEP peer information that spans PCEP
skipping to change at page 16, line 19 skipping to change at page 16, line 29
pcePcepPeerNumReqRcvdClosed Counter32, pcePcepPeerNumReqRcvdClosed Counter32,
pcePcepPeerNumRepRcvdUnknown Counter32, pcePcepPeerNumRepRcvdUnknown Counter32,
pcePcepPeerNumReqRcvdUnknown Counter32 pcePcepPeerNumReqRcvdUnknown Counter32
} }
pcePcepPeerAddrType OBJECT-TYPE pcePcepPeerAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The peer Internet address type (IPv4 or IPv6). "The type of the peer's Internet address. This object
specifies how the value of the pcePcepPeerAddr object should
This specifies how pcePcepPeerAddr should be interpreted." be interpreted."
::= { pcePcepPeerEntry 1 } ::= { pcePcepPeerEntry 1 }
pcePcepPeerAddr OBJECT-TYPE pcePcepPeerAddr OBJECT-TYPE
SYNTAX InetAddress (SIZE (4..32)) SYNTAX InetAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The Internet address of the peer. "The Internet address of the peer. The type is given by
The type of this address is specified by
pcePcepPeerAddrType. " pcePcepPeerAddrType. "
::= { pcePcepPeerEntry 2 } ::= { pcePcepPeerEntry 2 }
pcePcepPeerRole OBJECT-TYPE pcePcepPeerRole OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
pcc(1), -- Path Computation Client (PCC) pcc(1),
pce(2), -- Path Computation Server (PCE) pce(2),
pccAndPce(3), -- Both PCC and PCE roles pccAndPce(3),
unknown(4) -- Peer role is unknown unknown(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The role that this peer took the last time a session was "The role that this peer took the last time a session was
established." established. Takes one of the following values.
- pcc(1): this peer is a Path Computation Client (PCC).
- pce(2): this peer is a Path Computation Server (PCE).
- pccAndPce(3): this peer is both a PCC and a PCE.
- unknown(4): this peer's role is not known."
::= { pcePcepPeerEntry 3 } ::= { pcePcepPeerEntry 3 }
pcePcepPeerDiscontinuityTime OBJECT-TYPE pcePcepPeerDiscontinuityTime 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 that the information and "The value of sysUpTime at the time that the information and
statistics in this row were last reset. statistics in this row were last reset."
sysUpTime is the time (in hundredths of a second) since the
network management portion of the system was last
re-initialized. It is defined in RFC 1907."
::= { pcePcepPeerEntry 4 } ::= { pcePcepPeerEntry 4 }
pcePcepPeerInitiateSession OBJECT-TYPE pcePcepPeerInitiateSession OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates whether the PCEP Entity initiates sessions to this "Indicates whether the PCEP Entity initiates sessions to this
peer, or waits for the peer to initiate a session." peer, or waits for the peer to initiate a session."
::= { pcePcepPeerEntry 5 } ::= { pcePcepPeerEntry 5 }
skipping to change at page 18, line 32 skipping to change at page 18, line 39
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of sysUpTime the last time a session with this "The value of sysUpTime the last time a session with this
peer failed to be established. peer failed to be established.
If pcePcepPeerNumSessSetupFail is zero, then this object If pcePcepPeerNumSessSetupFail is zero, then this object
contains zero." contains zero."
::= { pcePcepPeerEntry 10 } ::= { pcePcepPeerEntry 10 }
pcePcepPeerAvgRspTime OBJECT-TYPE pcePcepPeerAvgRspTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32
UNITS "seconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average response time for this peer. "The average response time for this peer.
If an average response time has not been calculated for this If an average response time has not been calculated for this
peer then this object has the value zero. peer then this object has the value zero.
If pcePcepPeerRole is pcc then this field is meaningless and If pcePcepPeerRole is pcc then this field is meaningless and
is set to zero." is set to zero."
::= { pcePcepPeerEntry 11 } ::= { pcePcepPeerEntry 11 }
pcePcepPeerLWMRspTime OBJECT-TYPE pcePcepPeerLWMRspTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32
UNITS "seconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smallest (low-water mark) response time seen from this "The smallest (low-water mark) response time seen from this
peer. peer.
If no responses have been received from this peer then this If no responses have been received from this peer then this
object has the value zero. object has the value zero.
If pcePcepPeerRole is pcc then this field is meaningless and If pcePcepPeerRole is pcc then this field is meaningless and
is set to zero." is set to zero."
::= { pcePcepPeerEntry 12 } ::= { pcePcepPeerEntry 12 }
pcePcepPeerHWMRspTime OBJECT-TYPE pcePcepPeerHWMRspTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32
UNITS "seconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The greatest (high-water mark) response time seen from this "The greatest (high-water mark) response time seen from this
peer. peer.
If no responses have been received from this peer then this If no responses have been received from this peer then this
object has the value zero. object has the value zero.
If pcePcepPeerRole is pcc then this field is meaningless and If pcePcepPeerRole is pcc then this field is meaningless and
skipping to change at page 26, line 32 skipping to change at page 26, line 40
DESCRIPTION DESCRIPTION
"The number of unknown requests that have been received from "The number of unknown requests that have been received from
a peer. An unknown request is a request whose RP object a peer. An unknown request is a request whose RP object
contains a request ID of zero." contains a request ID of zero."
::= { pcePcepPeerEntry 47 } ::= { pcePcepPeerEntry 47 }
-- --
-- The PCEP Sessions Table -- The PCEP Sessions Table
-- --
pcePcepSessObjects OBJECT IDENTIFIER ::= { pcePcepMIBObjects 3 } pcePcepSessObjects OBJECT IDENTIFIER ::= { pcePcepObjects 3 }
pcePcepSessTable OBJECT-TYPE pcePcepSessTable OBJECT-TYPE
SYNTAX SEQUENCE OF PcePcepSessEntry SYNTAX SEQUENCE OF PcePcepSessEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of PCEP sessions that involve the local PCEP "A table of PCEP sessions that involve the local PCEP
speaker. Each row in this table represents a single speaker. Each row in this table represents a single
session." session."
::= { pcePcepSessObjects 1 } ::= { pcePcepSessObjects 1 }
skipping to change at page 29, line 21 skipping to change at page 29, line 29
openWait(2), openWait(2),
keepWait(3), keepWait(3),
sessionUp(4) sessionUp(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current state of the session. "The current state of the session.
The set of possible states excludes the idle state since The set of possible states excludes the idle state since
entiries do not exist in this table in the idle state." entries do not exist in this table in the idle state."
::= { pcePcepSessEntry 3 } ::= { pcePcepSessEntry 3 }
pcePcepSessConnectRetry OBJECT-TYPE pcePcepSessConnectRetry OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times that the local PCEP speaker has "The number of times that the local PCEP speaker has
attempted to establish a TCP connection for this session attempted to establish a TCP connection for this session
without success. The PCEP speaker gives up when this without success. The PCEP speaker gives up when this
skipping to change at page 31, line 11 skipping to change at page 31, line 17
DESCRIPTION DESCRIPTION
"The DeadTimer interval for this PCEP session." "The DeadTimer interval for this PCEP session."
::= { pcePcepSessEntry 9 } ::= { pcePcepSessEntry 9 }
pcePcepSessPeerDeadTimer OBJECT-TYPE pcePcepSessPeerDeadTimer OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The peer's DeadTimer interval for for this PCEP session. "The peer's DeadTimer interval for this PCEP session.
If pcePcepSessState is tcpPending or openWait then this If pcePcepSessState is tcpPending or openWait then this
field is not used and MUST be set to zero." field is not used and MUST be set to zero."
::= { pcePcepSessEntry 10 } ::= { pcePcepSessEntry 10 }
pcePcepSessKAHoldTimeRem OBJECT-TYPE pcePcepSessKAHoldTimeRem OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 32, line 38 skipping to change at page 32, line 45
pcePcepSessDiscontinuityTime OBJECT-TYPE pcePcepSessDiscontinuityTime 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 that the statistics in "The value of sysUpTime at the time that the statistics in
this row were last reset." this row were last reset."
::= { pcePcepSessEntry 16 } ::= { pcePcepSessEntry 16 }
pcePcepSessAvgRspTime OBJECT-TYPE pcePcepSessAvgRspTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32
UNITS "seconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The average response time for this peer on this session. "The average response time for this peer on this session.
If an average response time has not been calculated for this If an average response time has not been calculated for this
peer then this object has the value zero." peer then this object has the value zero."
::= { pcePcepSessEntry 17 } ::= { pcePcepSessEntry 17 }
pcePcepSessLWMRspTime OBJECT-TYPE pcePcepSessLWMRspTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32
UNITS "seconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The smallest (low-water mark) response time seen from this "The smallest (low-water mark) response time seen from this
peer on this session. peer on this session.
If no responses have been received from this peer then this If no responses have been received from this peer then this
object has the value zero." object has the value zero."
::= { pcePcepSessEntry 18 } ::= { pcePcepSessEntry 18 }
pcePcepSessHWMRspTime OBJECT-TYPE pcePcepSessHWMRspTime OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32
UNITS "seconds" UNITS "milliseconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The greatest (high-water mark) response time seen from this "The greatest (high-water mark) response time seen from this
peer on this session. peer on this session.
If no responses have been received from this peer then this If no responses have been received from this peer then this
object has the value zero." object has the value zero."
::= { pcePcepSessEntry 19 } ::= { pcePcepSessEntry 19 }
skipping to change at page 46, line 7 skipping to change at page 46, line 14
Editor's Note (to be removed prior to publication): the IANA is Editor's Note (to be removed prior to publication): the IANA is
requested to assign a value for "XXX" under the 'mib-2' subtree and requested to assign a value for "XXX" under the 'mib-2' subtree and
to record the assignment in the SMI Numbers registry. When the to record the assignment in the SMI Numbers registry. When the
assignment has been made, the RFC Editor is asked to replace "XXX" assignment has been made, the RFC Editor is asked to replace "XXX"
(here and in the MIB module) with the assigned value and to remove (here and in the MIB module) with the assigned value and to remove
this note. this note.
9. Contributors 9. Contributors
Thanks to Dhruv Dhody for contributing the P2MP objects, and for his Thanks to Dhruv Dhody for his contribution and detailed review.
detailed review.
10. References 10. References
10.1. Normative References 10.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
skipping to change at page 47, line 12 skipping to change at page 47, line 20
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
Authors' Addresses Authors' Addresses
A S Kiran Koushik A S Kiran Koushik
Cisco Systems, Inc. Cisco Systems, Inc.
EMail: kkoushik@cisco.com EMail: kkoushik@cisco.com
Stephan Emile Emile Stephan
France Telecom France Telecom
2 avenue Pierre Marzin 2 avenue Pierre Marzin
Lannion F-22307 Lannion F-22307
France France
EMail: emile.stephan@orange-ftgroup.com EMail: emile.stephan@orange.com
Quintin Zhao Quintin Zhao
Huawei Technology Huawei Technology
125 Nagog Technology Park 125 Nagog Technology Park
Acton, MA 01719 Acton, MA 01719
US US
EMail: qzhao@huawei.com EMail: qzhao@huawei.com
Daniel King Daniel King
skipping to change at page 47, line 33 skipping to change at page 48, line 4
Acton, MA 01719 Acton, MA 01719
US US
EMail: qzhao@huawei.com EMail: qzhao@huawei.com
Daniel King Daniel King
Old Dog Consulting Old Dog Consulting
UK UK
EMail: daniel@olddog.co.uk EMail: daniel@olddog.co.uk
Jonathan Hardwick Jonathan Hardwick
Metaswitch Metaswitch
100 Church Street 100 Church Street
Enfield EN2 6BQ Enfield EN2 6BQ
UK UK
EMail: jon.hardwick@metaswitch.com EMail: jonathan.hardwick@metaswitch.com
 End of changes. 40 change blocks. 
73 lines changed or deleted 81 lines changed or added

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