draft-ietf-ccamp-lmp-mib-03.txt   draft-ietf-ccamp-lmp-mib-04.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Meriton Networks Internet Draft Editor
Expires: December 2002 Expires: May 2003
Sudheer Dharanikota Sudheer Dharanikota
Nayna Networks
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Evan McGinnis Evan McGinnis
Calient Networks Calient Networks
June 2002 November 2002
Link Management Protocol Management Information Base Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-03.txt draft-ietf-ccamp-lmp-mib-04.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC 2026. all provisions of Section 10 of RFC 2026.
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 other Task Force (IETF), its areas, and its working groups. Note that other
groups may also distribute working documents as Internet- Drafts. groups may also distribute working documents as Internet- Drafts.
skipping to change at page 1, line 44 skipping to change at page 1, line 43
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.
Table of Contents Table of Contents
1. Abstract ..................................................... 2 1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Introduction ................................................. 2 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2
3. Terminology .................................................. 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The SNMP Management Framework ................................ 3 4. The SNMP Management Framework . . . . . . . . . . . . . . . . . 3
5. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . 4
5. Feature Checklist ............................................ 4 6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6. Outline ...................................................... 5 6.1. Summary of LMP MIB . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Summary of LMP MIB ........................................... 5 7. Brief Description of MIB Objects . . . . . . . . . . . . . . . 6
7. Brief Description of MIB Objects ............................. 6 7.1. lmpNbrTable . . . . . . . . . . . . . . . . . . . . . . . . . . 6
7.1. lmpNbrTable .................................................. 6 7.2. lmpControlChannelTable . . . . . . . . . . . . . . . . . . . . 6
7.2. lmpControlChannelTable ....................................... 6 7.3. lmpControlChannelPerfTable . . . . . . . . . . . . . . . . . . 6
7.3. lmpControlChannelPerfTable ................................... 6 7.4. lmpTeLinkTable . . . . . . . . . . . . . . . . . . . . . . . . 6
7.4. lmpTeLinkTable ............................................... 7 7.5. lmpLinkVerificationTable . . . . . . . . . . . . . . . . . . . 6
7.5. lmpLinkVerificationTable ..................................... 7 7.6. lmpTeLinkPerfTable . . . . . . . . . . . . . . . . . . . . . . 6
7.6. lmpTeLinkPerfTable ........................................... 7 7.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 7
7.7. lmpDataLinkTable ............................................. 7 7.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 7
7.8. lmpDataLinkPerfTable ......................................... 7 8. Example of LMP Control Channel Interface Setup . . . . . . . . 7
8. Example of LMP Control Channel Interface Setup ............... 7 9. Application of the Interfaces Group to LMP . . . . . . . . . . 9
9. Application of the Interfaces Group to LMP ................... 10 9.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 10
9.1. Support of the LMP Layer by ifTable .......................... 10 10. Link Management Protocol MIB Definitions . . . . . . . . . . . 11
10. Link Management Protocol MIB Definitions ..................... 12 11. Intellectual Property Considerations . . . . . . . . . . . . . 77
11. Security Considerations ...................................... 78 12. Security Considerations . . . . . . . . . . . . . . . . . . . . 77
12. Acknowledgments .............................................. 79 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 78
13. References ................................................... 79 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 79
14. Authors' Addresses ........................................... 82 14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 79
15. Full Copyright Statement ..................................... 82 14.2 Informative References . . . . . . . . . . . . . . . . . . . . 80
15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 81
16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 81
1. Abstract 1. Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling the Link In particular, it describes managed objects for modeling the Link
Management Protocol (LMP). Management Protocol (LMP).
2. Introduction 2. Introduction
skipping to change at page 3, line 34 skipping to change at page 3, line 34
ing capability (see [LMP] for distinction between port and component ing capability (see [LMP] for distinction between port and component
link). link).
Each TE link is associated with an LMP adjacency, and one or more Each TE link is associated with an LMP adjacency, and one or more
control channels are used to exchange LMP messages for a particular control channels are used to exchange LMP messages for a particular
adjacency. In turn, control channels are used to manage the TE links adjacency. In turn, control channels are used to manage the TE links
associated with the LMP adjacency. associated with the LMP adjacency.
4. The SNMP Management Framework 4. The SNMP Management Framework
The SNMP Management Framework presently consists of five major com- The SNMP Management Framework presently consists of five major compo-
ponents: nents:
- An overall architecture, described in RFC 2571 [RFC2571]. - An overall architecture, described in RFC 2571 [RFC2571].
- Mechanisms for describing and naming objects and events for the - Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described 1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580]. STD 58, RFC 2580 [RFC2580].
skipping to change at page 7, line 11 skipping to change at page 6, line 46
This table contains the objects to measure the LMP performance of LMP This table contains the objects to measure the LMP performance of LMP
capable interfaces and is an AUGMENT to the lmpControlChannelTable. capable interfaces and is an AUGMENT to the lmpControlChannelTable.
7.4. lmpTeLinkTable 7.4. lmpTeLinkTable
This table represents the TE link information specific to LMP. This table represents the TE link information specific to LMP.
7.5. lmpLinkVerificationTable 7.5. lmpLinkVerificationTable
This table augments the lmpTeLinkTable and represents the link verif- This table augments the lmpTeLinkTable and represents the link veri-
ication parameters associated with the TE links. fication parameters associated with the TE links.
7.6. lmpTeLinkPerfTable 7.6. lmpTeLinkPerfTable
This table contains the objects to measure the LMP performance of LMP This table contains the objects to measure the LMP performance of LMP
capable interfaces and is an AUGMENT to the lmpTeLinkTable. capable interfaces and is an AUGMENT to the lmpTeLinkTable.
7.7. lmpDataLinkTable 7.7. lmpDataLinkTable
The data-bearing link table enumerates the data-bearing links that The data-bearing link table enumerates the data-bearing links that
are associated with each TE link. are associated with each TE link.
skipping to change at page 8, line 4 skipping to change at page 7, line 34
nodes using two control channels. Suppose also that there are nodes using two control channels. Suppose also that there are
three data-bearing links. We also assume that the data-bearing three data-bearing links. We also assume that the data-bearing
links are ports (lambdas). We also assume that the link links are ports (lambdas). We also assume that the link
verification procedure is not enabled. The following example verification procedure is not enabled. The following example
illustrates which rows and corresponding objects might be created illustrates which rows and corresponding objects might be created
to accomplish this. to accomplish this.
First, LMP must be enabled between the pair of nodes. First, LMP must be enabled between the pair of nodes.
In lmpNbrTable: In lmpNbrTable:
{ {
lmpNbrNodeId = 'c0010101'H, -- 192.1.1.1 lmpNbrNodeId = 'c0010101'H, -- 192.1.1.1
lmpNbrRetransmitInterval = 10,
lmpNbrRetransmitTimeoutInterval = 0,
lmpNbrAdminStatus = up(1), lmpNbrAdminStatus = up(1),
lmpNbrRowStatus = createAndGo(4) lmpNbrRowStatus = createAndGo(4)
} }
Then, the control channels must be set up. These are created in Then, the control channels must be set up. These are created in
the lmpControlChannelTable. the lmpControlChannelTable.
In lmpControlChannelTable: In lmpControlChannelTable:
{ {
lmpCcId = 1, lmpCcId = 1,
lmpCcUnderlyingIfIndex = 1, lmpCcUnderlyingIfIndex = 1,
lmCcIsIf = false(1), lmCcIsIf = false(1),
lmpCcAuthentication = false(1), lmpCcAuthentication = false(1),
lmpCcConfigRetransmitInterval = 10,
lmpCcHelloInterval = 15, lmpCcHelloInterval = 15,
lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMin = 15,
lmpCcHelloIntervalMax = 1000, lmpCcHelloIntervalMax = 1000,
lmpCcHelloDeadInterval = 45, lmpCcHelloDeadInterval = 45,
lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMin = 45,
lmpCcHelloDeadIntervalMax = 1000, lmpCcHelloDeadIntervalMax = 1000,
lmpCcAdminStatus = up(1), lmpCcAdminStatus = up(1),
lmpCcRowStatus = createAndGo(4) lmpCcRowStatus = createAndGo(4)
} }
{ {
lmpCcId = 2, lmpCcId = 2,
lmpCcUnderlyingIfIndex = 2, lmpCcUnderlyingIfIndex = 2,
lmCcIsIf = false(1), lmCcIsIf = false(1),
lmpCcAuthentication = false(1), lmpCcAuthentication = false(1),
lmpCcConfigRetransmitInterval = 10,
lmpCcHelloInterval = 15, lmpCcHelloInterval = 15,
lmpCcHelloIntervalMin = 15, lmpCcHelloIntervalMin = 15,
lmpCcHelloIntervalMax = 1000, lmpCcHelloIntervalMax = 1000,
lmpCcHelloDeadInterval = 45, lmpCcHelloDeadInterval = 45,
lmpCcHelloDeadIntervalMin = 45, lmpCcHelloDeadIntervalMin = 45,
lmpCcHelloDeadIntervalMax = 1000, lmpCcHelloDeadIntervalMax = 1000,
lmpCcAdminStatus = up(1), lmpCcAdminStatus = up(1),
lmpCcRowStatus = createAndGo(4) lmpCcRowStatus = createAndGo(4)
} }
skipping to change at page 12, line 29 skipping to change at page 12, line 5
ifCounterDiscontinuityTime ifCounterDiscontinuityTime
See [RFC2863]. See [RFC2863].
10. LMP MIB Definitions 10. LMP MIB Definitions
LMP-MIB DEFINITIONS ::= BEGIN LMP-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE,
experimental, Unsigned32, Counter32, TimeTicks mib-2, Unsigned32, Counter32, TimeTicks
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType,
TimeStamp TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
teLinkRemoteIpAddr, teLinkIncomingIfId teLinkRemoteIpAddr, teLinkIncomingIfId
FROM LINK-BUNDLING-MIB; FROM LINK-BUNDLING-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200206251200Z" -- 25 June 2002 12:00:00 EST LAST-UPDATED "200211011200Z" -- 1 November 2002 12:00:00 EST
ORGANIZATION "Common Control and Measurement Protocols (CCAMP) ORGANIZATION "Common Control and Measurement Protocols (CCAMP)
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
" Martin Dubuc " Martin Dubuc
Postal: Meriton Networks Email: dubuc.consulting@rogers.com
3026 Solandt Road
Kanata, ON, CANADA K2K 2A5
Tel: +1-613-270-9279 x253
Email: martin.dubuc@meriton.com
Sudheer Dharanikota Sudheer Dharanikota
Postal: Nayna Networks, Inc. Email: sudheer@ieee.org
157 Topaz Street
Milipitas, CA 95035
Tel: +1-408-956-8000 x357
Email: sudheer@nayna.com
Thomas D. Nadeau Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Tel: +1-978-244-3051 Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Postal: Calient Networks, Inc. Postal: Calient Networks, Inc.
skipping to change at page 13, line 43 skipping to change at page 13, line 10
Evan McGinnis Evan McGinnis
Postal: Calient Networks, Inc. Postal: Calient Networks, Inc.
5853 Rue Ferrari 5853 Rue Ferrari
San Jose, CA 95138 San Jose, CA 95138
Email: evan@calient.net" Email: evan@calient.net"
DESCRIPTION DESCRIPTION
"This MIB contains managed object definitions for the "This MIB contains managed object definitions for the
Link Management Protocol (LMP) as Link Management Protocol (LMP) as
defined in: Lang, J., Mitra, K., Drake, J., Kompella, K., defined in: Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, D., Rekhter, Y., Berger, L., Saha, D., Basak, D.,
Basak, D., Sandick, H., Zinin, A., and Sandick, H., Zinin, A.,Rajagopalan, B., and
Rajagopalan, B., Link Management Protocol, Ramamoorthi, S., Link Management Protocol,
Internet Draft <draft-ietf-ccamp-lmp-03.txt>, Internet Draft <draft-ietf-ccamp-lmp-06.txt>,
March 2002." September 2002."
-- Revision history. -- Revision history.
REVISION REVISION
"200206251200Z" -- June 25 2002 12:00:00 EST "200211011200Z" -- November 1 2002 12:00:00 EST
DESCRIPTION
"- Shorten long identifiers length."
REVISION
"200205291200Z" -- 29 May 2002 12:00:00 EST
DESCRIPTION
"Addresses Last Call comments.
- Fixed syntax problems reported by SMICng and smilint.
- Added lmpRemoteCcIpAddrType and lmpRemoteCcIpAddr.
- Added lmpTeLinkPerfTable.
- Added lmpDataBearingLinkIpAddr.
- Added lmpTeLinkNotDegraded notification."
REVISION
"200202261200Z" -- 26 February 2002 12:00:00 EST
DESCRIPTION
"- Used latest MIB boiler plate.
- Added lmpFullModuleCompliance conformance statement.
- Replaced IpAddress with InetAddress.
- Added lmpOperStatus.
- Added lmpCcHelloIntervalNegotiated and
lmpCcHelloDeadIntervalNegotiated.
- Converted all 64-bit counters to 32-bit counters.
- Added counters for all LMP message types.
- Added counters to monitor data-bearing link tests.
- Reintroduced lmpNbrRetransmitTimeout.
- Added lmpDataBearingLinkNumberingType and
lmpDataBearingLinkRemoteIpAddress.
- Split data-bearing link operational status into active and
passive operational status.
- Updated description of all row status and storage type objects.
- Updated references."
REVISION
"200110211200Z" -- 21 October 2001 12:00:00 EST
DESCRIPTION
"- Minor syntax fixes.
- Added lmpCcId. Changed type of lmpRemoteCcId.
- Updated lmpTeLinkEncodingType.
- Removed lmpRemoteTeLinkType and lmpRemoteTeLinkId (their
content can be derived from LINK-BUNDLING-MIB).
- Added lmpCcLastChange, lmpCcCounterDiscontinuityTime and
lmpDataBearingLinkCounterDiscontinuityTime.
- Moved lmpTeLinkBitRate and lmpTeLinkWavelength to
lmpLinkVerificationTable.
- Updated lmpDataBearingLinkOperStatus.
- Modified performance counters to account for changes in
channel status message types.
- Changed indices for lmpTeLinkPropertyMismatch and
lmpDataBearingLinkPropertyMismatch notifications.
- Renamed lmpNbrLinkSumRetransmitInterval. Removed
lmpNbrRetransmitTimeout.
- Added lmpCcUnderlyingIfId, lmpCcIsIf and lmpCcSetupRole."
REVISION
"200105221200Z" -- 22 May 2001 12:00:00 EST
DESCRIPTION
"Updates based on IETF-50 feedback. Aligned with
upcoming version of LMP draft."
REVISION
"200102221200Z" -- 22 February 2001 12:00:00 EST
DESCRIPTION
"Updates based on MPLS mailing list feedback."
REVISION
"200101261200Z" -- 26 January 2001 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial draft version." "Initial version published as RFC xxxx (to be assigned by RFC Editor)"
::= { experimental 113 } -- See [Assigned] ::= { mib-2 xxx } -- To be assigned by IANA (experimental 113 can be used
-- in the interim)
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The interval delay in milliseconds." "The interval delay in milliseconds."
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
skipping to change at page 16, line 43 skipping to change at page 14, line 46
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table is created by a LMP-enabled device for "An entry in this table is created by a LMP-enabled device for
every pair of nodes that can establish control channels." every pair of nodes that can establish control channels."
INDEX { lmpNbrNodeId } INDEX { lmpNbrNodeId }
::= { lmpNbrTable 1 } ::= { lmpNbrTable 1 }
LmpNbrEntry ::= SEQUENCE { LmpNbrEntry ::= SEQUENCE {
lmpNbrNodeId InetAddress, lmpNbrNodeId InetAddress,
lmpNbrRetransmitInterval LmpRetransmitInterval, lmpNbrRetransmitInterval LmpRetransmitInterval,
lmpNbrRetransmitTimeout Unsigned32, lmpNbrRetryLimit Unsigned32,
lmpNbrRetransmitDelta Unsigned32,
lmpNbrAdminStatus INTEGER, lmpNbrAdminStatus INTEGER,
lmpNbrOperStatus INTEGER, lmpNbrOperStatus INTEGER,
lmpNbrRowStatus RowStatus, lmpNbrRowStatus RowStatus,
lmpNbrStorageType StorageType lmpNbrStorageType StorageType
} }
lmpNbrNodeId OBJECT-TYPE lmpNbrNodeId OBJECT-TYPE
SYNTAX InetAddress (SIZE(4)) SYNTAX InetAddress (SIZE(4))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is a unique index for an entry in the LmpNbrTable. "This is a unique index for an entry in the LmpNbrTable.
This value represents the remote Node ID. The Node ID This value represents the remote Node ID. The Node ID
address type must be IPv4." address type must be IPv4."
skipping to change at page 17, line 18 skipping to change at page 15, line 22
"This is a unique index for an entry in the LmpNbrTable. "This is a unique index for an entry in the LmpNbrTable.
This value represents the remote Node ID. The Node ID This value represents the remote Node ID. The Node ID
address type must be IPv4." address type must be IPv4."
::= { lmpNbrEntry 1 } ::= { lmpNbrEntry 1 }
lmpNbrRetransmitInterval OBJECT-TYPE lmpNbrRetransmitInterval OBJECT-TYPE
SYNTAX LmpRetransmitInterval SYNTAX LmpRetransmitInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the interval that is used for the "This object specifies the initial retransmission interval that
retransmission of LinkSummary, BeginVerify, EndVerify, is used for the retransmission of messages which require
TestStatusSuccess, TestStatusFailure, ChannelStatus and acknowledgement."
ChannelStatusRequest messages."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, DEFVAL { 500 }
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpNbrEntry 2 } ::= { lmpNbrEntry 2 }
lmpNbrRetransmitTimeout OBJECT-TYPE lmpNbrRetryLimit OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the LinkSummary, BeginVerify, EndVerify, "This object specifies the maximum number of times a message
TestStatusSuccess, TestStatusFailure, ChannelStatus and is transmitted without being acknowledged. A value of 0 is used
ChannelStatusRequest retransmission timeout period. If the specified
timeout expires and the message has not yet been acknowledged,
a node can stop retransmitting the message. A value of 0 is used
to indicate that a node should never stop retransmission." to indicate that a node should never stop retransmission."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter, DEFVAL { 3 }
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
DEFVAL { 0 }
::= { lmpNbrEntry 7 } ::= { lmpNbrEntry 7 }
lmpNbrRetransmitDelta OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object governs the speed with which the sender increases
the retransmission interval."
REFERENCE
"[LMP]"
DEFVAL { 1 }
::= { lmpNbrEntry 8 }
lmpNbrAdminStatus OBJECT-TYPE lmpNbrAdminStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The desired operational status of LMP to this remote node." "The desired operational status of LMP to this remote node."
::= { lmpNbrEntry 3 } ::= { lmpNbrEntry 3 }
lmpNbrOperStatus OBJECT-TYPE lmpNbrOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2) } SYNTAX INTEGER { up(1), down(2) }
skipping to change at page 18, line 49 skipping to change at page 17, line 8
lmpCcHelloIntervalDefault OBJECT-TYPE lmpCcHelloIntervalDefault OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default value for the HelloInterval "This object specifies the default value for the HelloInterval
parameter used in the Hello protocol keep-alive phase. It parameter used in the Hello protocol keep-alive phase. It
indicates how frequently LMP Hello messages will be sent. It indicates how frequently LMP Hello messages will be sent. It
is used a the default value for lmpCcHelloInterval." is used a the default value for lmpCcHelloInterval."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpObjects 4 } ::= { lmpObjects 4 }
lmpCcHelloIntervalDefaultMin OBJECT-TYPE lmpCcHelloIntervalDefaultMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default minimum value for the "This object specifies the default minimum value for the
HelloInterval parameter. It is used as a default value HelloInterval parameter. It is used as a default value
for lmpCcHelloIntervalMin." for lmpCcHelloIntervalMin."
skipping to change at page 19, line 40 skipping to change at page 17, line 43
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default HelloDeadInterval parameter to "This object specifies the default HelloDeadInterval parameter to
use in the Hello protocol keep-alive phase. It indicates how long use in the Hello protocol keep-alive phase. It indicates how long
a device should wait before declaring the control channel dead. a device should wait before declaring the control channel dead.
The HelloDeadInterval parameter should be at least three times the The HelloDeadInterval parameter should be at least three times the
value of HelloInterval. It is used as a default value for value of HelloInterval. It is used as a default value for
lmpCcHelloDeadInterval." lmpCcHelloDeadInterval."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpObjects 7 } ::= { lmpObjects 7 }
lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE lmpCcHelloDeadIntervalDefaultMin OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the default minimum value for the "This object specifies the default minimum value for the
HelloDeadInterval parameter. It is used as a default value HelloDeadInterval parameter. It is used as a default value
for lmpCcHelloDeadIntervalMin." for lmpCcHelloDeadIntervalMin."
skipping to change at page 20, line 50 skipping to change at page 18, line 50
LmpControlChannelEntry ::= SEQUENCE { LmpControlChannelEntry ::= SEQUENCE {
lmpCcId Unsigned32, lmpCcId Unsigned32,
lmpCcUnderlyingIfIndex InterfaceIndexOrZero, lmpCcUnderlyingIfIndex InterfaceIndexOrZero,
lmpCcIsIf TruthValue, lmpCcIsIf TruthValue,
lmpCcNbrNodeId InetAddress, lmpCcNbrNodeId InetAddress,
lmpRemoteCcId Unsigned32, lmpRemoteCcId Unsigned32,
lmpRemoteCcIpAddrType InetAddressType, lmpRemoteCcIpAddrType InetAddressType,
lmpRemoteCcIpAddr InetAddress, lmpRemoteCcIpAddr InetAddress,
lmpCcSetupRole INTEGER, lmpCcSetupRole INTEGER,
lmpCcAuthentication TruthValue, lmpCcAuthentication TruthValue,
lmpCcConfigRetransmitInterval LmpRetransmitInterval,
lmpCcConfigRetransmitTimeout Unsigned32,
lmpCcHelloInterval LmpInterval, lmpCcHelloInterval LmpInterval,
lmpCcHelloIntervalMin LmpInterval, lmpCcHelloIntervalMin LmpInterval,
lmpCcHelloIntervalMax LmpInterval, lmpCcHelloIntervalMax LmpInterval,
lmpCcHelloIntervalNegotiated LmpInterval, lmpCcHelloIntervalNegotiated LmpInterval,
lmpCcHelloDeadInterval LmpInterval, lmpCcHelloDeadInterval LmpInterval,
lmpCcHelloDeadIntervalMin LmpInterval, lmpCcHelloDeadIntervalMin LmpInterval,
lmpCcHelloDeadIntervalMax LmpInterval, lmpCcHelloDeadIntervalMax LmpInterval,
lmpCcHelloDeadIntervalNegotiated LmpInterval, lmpCcHelloDeadIntervalNegotiated LmpInterval,
lmpCcLastChange TimeTicks, lmpCcLastChange TimeTicks,
lmpCcAdminStatus INTEGER, lmpCcAdminStatus INTEGER,
skipping to change at page 23, line 19 skipping to change at page 21, line 17
::= { lmpControlChannelEntry 8 } ::= { lmpControlChannelEntry 8 }
lmpCcAuthentication OBJECT-TYPE lmpCcAuthentication OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the control channel should use "This object indicates whether the control channel should use
authentication." authentication."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpControlChannelEntry 9 } ::= { lmpControlChannelEntry 9 }
lmpCcConfigRetransmitInterval OBJECT-TYPE
SYNTAX LmpRetransmitInterval
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the interval that is used for the
retransmission of Config messages during the parameter
negotiation phase."
REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpControlChannelEntry 10 }
lmpCcConfigRetransmitTimeout OBJECT-TYPE
SYNTAX Unsigned32
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This object specifies the Config retransmission timeout
period. If the specified timeout expires and no Config,
ConfigAck or ConfigNack message has been received, a node
can stop retransmitting Config messages on the control
channel. A value of 0 is used to indicate that a node should
never stop retransmission. This parameter (if non-zero)
should be greater than lmpCcConfigRetransmitInterval."
REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP),
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
DEFVAL { 0 }
::= { lmpControlChannelEntry 11 }
lmpCcHelloInterval OBJECT-TYPE lmpCcHelloInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the value of the HelloInterval "This object specifies the value of the HelloInterval
parameter. The default value for this object should be parameter. The default value for this object should be
set to lmpCcHelloIntervalDefault." set to lmpCcHelloIntervalDefault."
::= { lmpControlChannelEntry 12 } ::= { lmpControlChannelEntry 12 }
skipping to change at page 39, line 52 skipping to change at page 37, line 13
::= { lmpTeLinkEntry 1 } ::= { lmpTeLinkEntry 1 }
lmpTeLinkVerification OBJECT-TYPE lmpTeLinkVerification OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the extended LMP link verification "This object indicates if the extended LMP link verification
procedure is enabled for this TE link." procedure is enabled for this TE link."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpTeLinkEntry 2 } ::= { lmpTeLinkEntry 2 }
lmpTeLinkFaultManagement OBJECT-TYPE lmpTeLinkFaultManagement OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the extended LMP fault management "This object indicates if the extended LMP fault management
procedure is enabled on this TE link." procedure is enabled on this TE link."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpTeLinkEntry 3 } ::= { lmpTeLinkEntry 3 }
lmpTeLinkDwdm OBJECT-TYPE lmpTeLinkDwdm OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates if the extended LMP DWDM procedure "This object indicates if the extended LMP DWDM procedure
is enabled on this TE link." is enabled on this TE link."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpTeLinkEntry 4 } ::= { lmpTeLinkEntry 4 }
lmpTeLinkOperStatus OBJECT-TYPE lmpTeLinkOperStatus OBJECT-TYPE
SYNTAX INTEGER { up(1), down(2), testing(3), init(4), degraded(5) } SYNTAX INTEGER { up(1), down(2), testing(3), init(4), degraded(5) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this TE link. The status "The actual operational status of this TE link. The status
is set to testing when the TE link is performing link is set to testing when the TE link is performing link
verification. A degraded state indicates that there are verification. A degraded state indicates that there are
skipping to change at page 42, line 28 skipping to change at page 39, line 28
lmpVerifyInterval OBJECT-TYPE lmpVerifyInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the VerifyInterval parameter used "This object specifies the VerifyInterval parameter used
in the LMP link verification process. It indicates the interval in the LMP link verification process. It indicates the interval
at which the Test messages are sent." at which the Test messages are sent."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpLinkVerificationEntry 1 } ::= { lmpLinkVerificationEntry 1 }
lmpVerifyDeadInterval OBJECT-TYPE lmpVerifyDeadInterval OBJECT-TYPE
SYNTAX LmpInterval SYNTAX LmpInterval
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the VerifyDeadInterval parameter used "This object specifies the VerifyDeadInterval parameter used
in the verification of the physical connectivity of data-bearing in the verification of the physical connectivity of data-bearing
links. It specifies the observation period used to detect a Test links. It specifies the observation period used to detect a Test
message at the remote node." message at the remote node."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpLinkVerificationEntry 2 } ::= { lmpLinkVerificationEntry 2 }
lmpVerifyTransportMechanism OBJECT-TYPE lmpVerifyTransportMechanism OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
-- SONET/SDH encoding type: -- SONET/SDH encoding type:
j016OverheadBytes(0), j016OverheadBytes(0),
j064OverheadBytes(1), j064OverheadBytes(1),
dccSectionOverheadBytes(2), dccSectionOverheadBytes(2),
dccLineOverheadBytes(3), dccLineOverheadBytes(3),
pos(4), pos(4),
skipping to change at page 43, line 24 skipping to change at page 40, line 18
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This defines the transport mechanism for the Test messages. The "This defines the transport mechanism for the Test messages. The
scope of this bit mask is restricted to each link encoding scope of this bit mask is restricted to each link encoding
type. The local node will set the bits corresponding to the type. The local node will set the bits corresponding to the
various mechanisms it can support for transmitting LMP Test various mechanisms it can support for transmitting LMP Test
messages. The receiver chooses the appropriate mechanism in the messages. The receiver chooses the appropriate mechanism in the
BeginVerifyAck message." BeginVerifyAck message."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpLinkVerificationEntry 3 } ::= { lmpLinkVerificationEntry 3 }
lmpVerifyAllLinks OBJECT-TYPE lmpVerifyAllLinks OBJECT-TYPE
SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) } SYNTAX INTEGER { verifyAllLinks(1), verifyNewLinks(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates whether the verification process checks "This object indicates whether the verification process checks
all entities or only the new entities that have been added to all entities or only the new entities that have been added to
this TE link." this TE link."
::= { lmpLinkVerificationEntry 4 } ::= { lmpLinkVerificationEntry 4 }
lmpTeLinkBitRate OBJECT-TYPE lmpTeLinkBitRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the bit rate at which the Test messages will be "This is the bit rate at which the Test messages will be
transmitted and is expressed in bytes per second." transmitted and is expressed in bytes per second."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpLinkVerificationEntry 5 } ::= { lmpLinkVerificationEntry 5 }
lmpTeLinkWavelength OBJECT-TYPE lmpTeLinkWavelength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value corresponds to the wavelength at "This value corresponds to the wavelength at
which the Test messages will be transmitted over and is which the Test messages will be transmitted over and is
measured in nanometers (nm). If each data-bearing link measured in nanometers (nm). If each data-bearing link
corresponds to a separate wavelength, than this value should be corresponds to a separate wavelength, than this value should be
set to 0." set to 0."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpLinkVerificationEntry 6 } ::= { lmpLinkVerificationEntry 6 }
-- End of lmpLinkVerificationTable -- End of lmpLinkVerificationTable
-- LMP TE Link Performance Table -- LMP TE Link Performance Table
lmpTeLinkPerfTable OBJECT-TYPE lmpTeLinkPerfTable OBJECT-TYPE
SYNTAX SEQUENCE OF LmpTeLinkPerfEntry SYNTAX SEQUENCE OF LmpTeLinkPerfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
skipping to change at page 54, line 30 skipping to change at page 51, line 15
port(1), port(1),
componentLink(2) componentLink(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies whether this data-bearing link is "This attribute specifies whether this data-bearing link is
a port or a component link. Component link are multiplex a port or a component link. Component link are multiplex
capable whereas, ports are not multiplex capable." capable whereas, ports are not multiplex capable."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpDataLinkEntry 1 } ::= { lmpDataLinkEntry 1 }
lmpDataLinkIpAddrType OBJECT-TYPE lmpDataLinkIpAddrType OBJECT-TYPE
SYNTAX InetAddressType SYNTAX InetAddressType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This attribute specifies the data-bearing link IP address "This attribute specifies the data-bearing link IP address
type. If the data-bearing link is unnumbered, the address type. If the data-bearing link is unnumbered, the address
type must be set to unknown(0)." type must be set to unknown(0)."
skipping to change at page 55, line 46 skipping to change at page 52, line 29
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
fiberChannel(11) fiberChannel(11)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The encoding type of the data-bearing link." "The encoding type of the data-bearing link."
REFERENCE REFERENCE
"draft-ietf-mpls-generalized-signaling-08.txt - Generalized "[GMPLS]"
MPLS Signaling Functional Description, P. Ashwood-Smith,
A. Banarjee, L. Berger, G. Bernstein, J. Drake, Y. Fan,
E. Mannie, J. Lang, B. Rajagopalan, Y. Rekhter, D. Saha,
V. Sharma, G. Swallow, Z. Tang, April 2002."
::= { lmpDataLinkEntry 6 } ::= { lmpDataLinkEntry 6 }
lmpDataLinkActiveOperStatus OBJECT-TYPE lmpDataLinkActiveOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
upAlloc(1), upAlloc(1),
upFree(2), upFree(2),
down(3), down(3),
testing(4) } testing(4) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this data-bearing link "The actual operational status of this data-bearing link
(active FSM)." (active FSM)."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-03.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpDataLinkEntry 7 } ::= { lmpDataLinkEntry 7 }
lmpDataLinkPassiveOperStatus OBJECT-TYPE lmpDataLinkPassiveOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
upAlloc(1), upAlloc(1),
upFree(2), upFree(2),
down(3), down(3),
psvTst(4) } psvTst(4) }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actual operational status of this data-bearing link "The actual operational status of this data-bearing link
(passive FSM)." (passive FSM)."
REFERENCE REFERENCE
"draft-ietf-ccamp-lmp-02.txt - Link Management Protocol (LMP), "[LMP]"
J. Lang, K. Mitra, J. Drake, K. Kompella, Y. Rekhter,
L. Berger, D. Saha, D. Basak, H. Sandick, A. Zinin,
B. Rajagopalan, March 2002."
::= { lmpDataLinkEntry 8 } ::= { lmpDataLinkEntry 8 }
lmpDataLinkRowStatus OBJECT-TYPE lmpDataLinkRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to create, modify, and/or "This variable is used to create, modify, and/or
delete a row in this table. All read-create objects delete a row in this table. All read-create objects
can only be changed when lmpDataLinkRowStatus is active." can only be changed when lmpDataLinkRowStatus is active."
skipping to change at page 67, line 46 skipping to change at page 64, line 20
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpNbrTable -- lmpNbrTable
OBJECT lmpNbrRetransmitInterval OBJECT lmpNbrRetransmitInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNbrRetransmitTimeout OBJECT lmpNbrRetryLimit
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpNbrRetransmitDelta
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpNbrRowStatus OBJECT lmpNbrRowStatus
SYNTAX INTEGER { active(1), notInService(2), SYNTAX INTEGER { active(1), notInService(2),
createAndGo(4), destroy(6) } createAndGo(4), destroy(6) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The notReady(3) and createAndWait(5) states need "The notReady(3) and createAndWait(5) states need
skipping to change at page 69, line 8 skipping to change at page 65, line 35
OBJECT lmpCcSetupRole OBJECT lmpCcSetupRole
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcAuthentication OBJECT lmpCcAuthentication
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcConfigRetransmitInterval
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcConfigRetransmitTimeout
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpCcHelloIntervalMin OBJECT lmpCcHelloIntervalMin
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcHelloIntervalMax OBJECT lmpCcHelloIntervalMax
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 73, line 24 skipping to change at page 69, line 39
lmpUnprotectedNotifEnable lmpUnprotectedNotifEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for LMP node configuration." "Collection of objects needed for LMP node configuration."
::= { lmpGroups 1 } ::= { lmpGroups 1 }
lmpControlChannelGroup OBJECT-GROUP lmpControlChannelGroup OBJECT-GROUP
OBJECTS { OBJECTS {
lmpNbrRetransmitInterval, lmpNbrRetransmitInterval,
lmpNbrRetransmitTimeout, lmpNbrRetryLimit,
lmpNbrRetransmitDelta,
lmpNbrAdminStatus, lmpNbrAdminStatus,
lmpNbrOperStatus, lmpNbrOperStatus,
lmpNbrRowStatus, lmpNbrRowStatus,
lmpNbrStorageType, lmpNbrStorageType,
lmpCcHelloIntervalDefault, lmpCcHelloIntervalDefault,
lmpCcHelloIntervalDefaultMin, lmpCcHelloIntervalDefaultMin,
lmpCcHelloIntervalDefaultMax, lmpCcHelloIntervalDefaultMax,
lmpCcHelloDeadIntervalDefault, lmpCcHelloDeadIntervalDefault,
lmpCcHelloDeadIntervalDefaultMin, lmpCcHelloDeadIntervalDefaultMin,
lmpCcHelloDeadIntervalDefaultMax, lmpCcHelloDeadIntervalDefaultMax,
lmpCcNbrNodeId, lmpCcNbrNodeId,
lmpRemoteCcId, lmpRemoteCcId,
lmpRemoteCcIpAddrType, lmpRemoteCcIpAddrType,
lmpRemoteCcIpAddr, lmpRemoteCcIpAddr,
lmpCcSetupRole, lmpCcSetupRole,
lmpCcAuthentication, lmpCcAuthentication,
lmpCcConfigRetransmitInterval,
lmpCcConfigRetransmitTimeout,
lmpCcHelloInterval, lmpCcHelloInterval,
lmpCcHelloIntervalMin, lmpCcHelloIntervalMin,
lmpCcHelloIntervalMax, lmpCcHelloIntervalMax,
lmpCcHelloIntervalNegotiated, lmpCcHelloIntervalNegotiated,
lmpCcHelloDeadInterval, lmpCcHelloDeadInterval,
lmpCcHelloDeadIntervalMin, lmpCcHelloDeadIntervalMin,
lmpCcHelloDeadIntervalMax, lmpCcHelloDeadIntervalMax,
lmpCcHelloDeadIntervalNegotiated, lmpCcHelloDeadIntervalNegotiated,
lmpCcOperStatus, lmpCcOperStatus,
lmpCcRowStatus, lmpCcRowStatus,
skipping to change at page 78, line 25 skipping to change at page 74, line 41
lmpDataLinkVerificationFailure } lmpDataLinkVerificationFailure }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Set of notifications implemented in this module. "Set of notifications implemented in this module.
None is mandatory." None is mandatory."
::= { lmpGroups 10 } ::= { lmpGroups 10 }
-- End of LMP-MIB -- End of LMP-MIB
END END
11. Security Considerations 11. Intellectual Property Considerations
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to per-
tain to the implementation or use of the technology described in this
document or the extent to which any license under such rights might
or might not be available; neither does it represent that it has made
any effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses
to be made available, or 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 Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
12. Security Considerations
It is clear that this MIB is potentially useful for monitoring of LMP It is clear that this MIB is potentially useful for monitoring of LMP
enabled devices. This MIB can also be used for configuration of cer- enabled devices. This MIB can also be used for configuration of cer-
tain objects, and anything that can be configured can be incorrectly tain objects, and anything that can be configured can be incorrectly
configured, with potentially disastrous results. configured, with potentially disastrous results.
At this writing, no security holes have been identified beyond those At this writing, no security holes have been identified beyond those
that SNMP Security [RFC2571] is itself intended to address. These that SNMP Security [RFC2571] is itself intended to address. These
relate to primarily controlled access to sensitive information and relate to primarily controlled access to sensitive information and
the ability to configure a device - or which might result from opera- the ability to configure a device - or which might result from opera-
skipping to change at page 79, line 22 skipping to change at page 76, line 10
There are a number of managed objects in this MIB that may contain There are a number of managed objects in this MIB that may contain
information that may be sensitive from a business perspective, in information that may be sensitive from a business perspective, in
that they can be used to derive the network topology, e.g. list of that they can be used to derive the network topology, e.g. list of
nodes and their IP address (lmpNbrTable) and list of data-bearing nodes and their IP address (lmpNbrTable) and list of data-bearing
links (lmpDataLinkTable). Allowing uncontrolled access to these links (lmpDataLinkTable). Allowing uncontrolled access to these
objects could result in malicious and unwanted disruptions of network objects could result in malicious and unwanted disruptions of network
traffic, incorrect network configurations or theft of competitive traffic, incorrect network configurations or theft of competitive
business information. There are no objects that are particularly sen- business information. There are no objects that are particularly sen-
sitive in their own right, such as passwords or monetary amounts. sitive in their own right, such as passwords or monetary amounts.
12. Acknowledgments 13. Acknowledgments
The general structure of this draft has been modeled around draft- The general structure of this draft has been modeled around draft-
ietf-mpls-lsr-mib-06.txt. ietf-mpls-lsr-mib-06.txt.
The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and The authors wish to thank Dmitry Ryumkin, Baktha Muralidharan and
George Wang. George Wang.
13. References 14. References
[RFC1155] Rose, M., and K. McCloghrie, "Structure and 14.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2401] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November
1998.
[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also:
http://www.iana.org/assignments/smi-numbers
[BUNDLE] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-04.txt>,
July 2002.
[BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,
"Link Bundling Management Information Base",
Internet Draft <draft-ietf-mpls-bundle-mib-04.txt>,
November 2002.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS. See also:
http://www.iana.org/assignments/address-family-numbers
For MIB see: http://www.iana.org/assignments/
ianaaddressfamilynumbers-mib
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Lang, J., Mannie, E., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, B.,
"Generalized MPLS Signaling Function Description",
Internet Draft
<draft-ietf-mpls-generalized-signaling-09.txt>,
August 2002.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, S., Basak, D.,
Sandick, H., Zinin, A., Rajagopalan, B., and
Ramamoorthi, S., "Link Management Protocol",
Internet Draft <draft-ietf-ccamp-lmp-06.txt>,
September 2002.
14.2. Informative References
[RFC1155] Rose, M., and McCloghrie, K., "Structure and
Identification of Management Information for TCP/IP- Identification of Management Information for TCP/IP-
based Internets", STD 16, RFC 1155, May 1990. based Internets", STD 16, RFC 1155, May 1990.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157, "Simple Network Management Protocol", STD 15, RFC 1157,
May 1990. May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", [RFC1212] Rose, M., and McCloghrie, K., "Concise MIB Defini-
tions",
STD 16, RFC 1212, March 1991. STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with [RFC1215] M. Rose, "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991. the SNMP", RFC 1215, March 1991.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, "Introduction to Community-based SNMPv2", RFC 1901,
January 1996. January 1996.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple "Protocol Operations for Version 2 of the Simple
Network Management Protocol (SNMPv2)", RFC 1905, Network Management Protocol (SNMPv2)", RFC 1905,
January 1996. January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard "Introduction to Version 3 of the Internet-standard
Network Management Framework", RFC 2570, April 1999. Network Management Framework", RFC 2570, April 1999.
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Architecture for Describing SNMP Management
Frameworks", RFC 2571, April 1999. Frameworks", RFC 2571, April 1999.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen,
"Message Processing and Dispatching for the Simple "Message Processing and Dispatching for the Simple
skipping to change at page 80, line 41 skipping to change at page 78, line 40
Applications", RFC 2573, April 1999. Applications", RFC 2573, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security
Model (USM) for version 3 of the Simple Network Model (USM) for version 3 of the Simple Network
Management Protocol (SNMPv3)", RFC 2574, April 1999. Management Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999. Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 15. Authors' Addresses
J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58,
RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2401] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November
1998.
[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also:
http://www.iana.org/assignments/smi-numbers
[BUNDLE] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-03.txt>,
May 2002.
[BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,
"Link Bundling Management Information Base",
Internet Draft <draft-ietf-mpls-bundle-mib-03.txt>,
June 2002.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS. See also:
http://www.iana.org/assignments/address-family-numbers
For MIB see: http://www.iana.org/assignments/
ianaaddressfamilynumbers-mib
[GMPLS] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Mannie, E., Lang, J., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, Z.,
"Generalized MPLS Signaling Function Description",
Internet Draft
<draft-ietf-mpls-generalized-signaling-08.txt>,
April 2002.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, S., Basak, D.,
Sandick, H., Zinin, A., and Rajagopalan, B.,
"Link Management Protocol", Internet Draft
<draft-ietf-ccamp-lmp-03.txt>, March 2002.
14. Authors' Addresses
Martin Dubuc Jonathan P. Lang Martin Dubuc Jonathan P. Lang
Meriton Networks Calient Networks, Inc. Email: dubuc.consulting@rogers.com Calient Networks, Inc.
25 Castilian Drive
3026 Solandt Road 25 Castilian Drive Goleta, CA 93117
Kanata, ON, CANADA K2K 2A5 Goleta, CA 93117 Email: jplang@calient.net
Phone: +1-613-270-9279 x253 Email: jplang@calient.net
Email: martin.dubuc@meriton.com
Sudheer Dharanikota Evan McGinnis Sudheer Dharanikota Evan McGinnis
Nayna Networks, Inc. Calient Networks, Inc. Email: sudheer@ieee.org Calient Networks, Inc.
157 Topaz Street 5853 Rue Ferrari 5853 Rue Ferrari
Milipitas, CA 95035 San Jose, CA 95138 San Jose, CA 95138
Phone: +1-408-956-8000 x357 Email: evan@calient.net Email: evan@calient.net
Email: sudheer@nayna.com
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
300 Apollo Drive 300 Apollo Drive
Chelmsford, MA 01824 Chelmsford, MA 01824
Phone: +1-978-244-3051 Phone: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
15. Full Copyright Statement 16. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2001). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this docu- included on all such copies and derivative works. However, this docu-
ment itself may not be modified in any way, such as by removing the ment itself may not be modified in any way, such as by removing the
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/