draft-ietf-ccamp-lmp-mib-08.txt   draft-ietf-ccamp-lmp-mib-09.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Internet Draft
Category: Standards Track Sudheer Dharanikota Category: Standards Track Sudheer Dharanikota
Expires: September 2004 Expires: November 2004
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Rincon Networks Rincon Networks
Evan McGinnis Evan McGinnis
Calient Networks Calient Networks
March 2004 May 2004
Link Management Protocol Management Information Base Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-08.txt draft-ietf-ccamp-lmp-mib-09.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 2, line 25 skipping to change at page 2, line 25
6.3. lmpControlChannelPerfTable . . . . . . . . . . . . . . . . . . 5 6.3. lmpControlChannelPerfTable . . . . . . . . . . . . . . . . . . 5
6.4. lmpTeLinkTable . . . . . . . . . . . . . . . . . . . . . . . . 5 6.4. lmpTeLinkTable . . . . . . . . . . . . . . . . . . . . . . . . 5
6.5. lmpLinkVerificationTable . . . . . . . . . . . . . . . . . . . 5 6.5. lmpLinkVerificationTable . . . . . . . . . . . . . . . . . . . 5
6.6. lmpTeLinkPerfTable . . . . . . . . . . . . . . . . . . . . . . 5 6.6. lmpTeLinkPerfTable . . . . . . . . . . . . . . . . . . . . . . 5
6.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 5 6.7. lmpDataLinkTable . . . . . . . . . . . . . . . . . . . . . . . 5
6.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 5 6.8. lmpDataLinkPerfTable . . . . . . . . . . . . . . . . . . . . . 5
7. Example of LMP Control Channel Interface Setup . . . . . . . . . 5 7. Example of LMP Control Channel Interface Setup . . . . . . . . . 5
8. Application of the Interfaces Group to LMP . . . . . . . . . . . 8 8. Application of the Interfaces Group to LMP . . . . . . . . . . . 8
8.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 9 8.1. Support of the LMP Layer by ifTable . . . . . . . . . . . . . . 9
9. Link Management Protocol MIB Module Definitions . . . . . . . . . 11 9. Link Management Protocol MIB Module Definitions . . . . . . . . . 11
10. Intellectual Property Considerations . . . . . . . . . . . . . . 77 10. Intellectual Property Considerations . . . . . . . . . . . . . . 78
11. Security Considerations . . . . . . . . . . . . . . . . . . . . 77 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 78
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 78 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 79
13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 79 13. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 80
13.1 IANA Considerations for lmp ifType . . . . . . . . . . . . . . 79 13.1 IANA Considerations for lmp ifType . . . . . . . . . . . . . . 80
13.2 IANA Considerations for LMP-MIB . . . . . . . . . . . . . . . . 79 13.2 IANA Considerations for LMP-MIB . . . . . . . . . . . . . . . . 80
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 79 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 79 14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 80
14.2 Informative References . . . . . . . . . . . . . . . . . . . . 80 14.2 Informative References . . . . . . . . . . . . . . . . . . . . 81
15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 80 15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 82
16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 81 16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 82
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 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).
skipping to change at page 8, line 35 skipping to change at page 8, line 35
In lmpTeLinkTable: In lmpTeLinkTable:
{ {
ifIndex = 20, ifIndex = 20,
lmpTeLinkVerification = true(2), lmpTeLinkVerification = true(2),
lmpTeLinkFaultManagement = true(2), lmpTeLinkFaultManagement = true(2),
lmpTeLinkDwdm = false(1), lmpTeLinkDwdm = false(1),
lmpTeLinkRowStatus = createAndGo(4), lmpTeLinkRowStatus = createAndGo(4),
lmpTeLinkStorageType = nonVolatile(3) lmpTeLinkStorageType = nonVolatile(3)
} }
and in lmpVerifyTable: and in lmpLinkVerificationTable:
{ {
lmpVerifyInterval = 100, ifIndex = 20,
lmpVerifyDeadInterval = 300, lmpLinkVerifyInterval = 100,
lmpVerifyTransportMechanism = j0Trace(3), lmpLinkVerifyDeadInterval = 300,
lmpVerifyAllLinks = true(2), lmpLinkVerifyTransportMechanism = j0Trace(3),
lmpVerifyTransmissionRate = 100000, lmpLinkVerifyAllLinks = true(2),
lmpVerifyWavelength = 0 lmpLinkVerifyTransmissionRate = 100000,
lmpLinkVerifyWavelength = 0,
lmpLinkVerifyRowStatus = createAndGo(4),
lmpLinkVerifyStorageType = nonVolatile(3)
} }
The association between the data-bearing links and the TE links is The association between the data-bearing links and the TE links is
stored in the ifStackTable [IF-MIB]. stored in the ifStackTable [IF-MIB].
In parallel with the entry created in the lmpTeLinkTable, an entry In parallel with the entry created in the lmpTeLinkTable, an entry
may be created in the teLinkTable of TE Link MIB module may be created in the teLinkTable of TE Link MIB module
[TELINK-MIB]. [TELINK-MIB].
8. Application of the Interfaces Group to LMP 8. Application of the Interfaces Group to LMP
skipping to change at page 12, line 4 skipping to change at page 12, line 4
InterfaceIndexOrZero, ifIndex InterfaceIndexOrZero, ifIndex
FROM IF-MIB FROM IF-MIB
InetAddressType, InetAddress InetAddressType, InetAddress
FROM INET-ADDRESS-MIB FROM INET-ADDRESS-MIB
teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType teLinkRemoteIpAddr, teLinkIncomingIfId, TeLinkEncodingType
FROM TE-LINK-STD-MIB; FROM TE-LINK-STD-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200403031200Z" -- 3 March 2004 12:00:00 EST LAST-UPDATED "200405241200Z" -- 24 May 2004 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
Email: dubuc.consulting@rogers.com Email: dubuc.consulting@rogers.com
Sudheer Dharanikota Sudheer Dharanikota
Email: sudheer@ieee.org Email: sudheer@ieee.org
Thomas D. Nadeau Thomas D. Nadeau
skipping to change at page 12, line 34 skipping to change at page 12, line 34
"Copyright (C) 2004 The Internet Society. This version of "Copyright (C) 2004 The Internet Society. This version of
the MIB module is part of RFC XXXX; see the RFC itself the MIB module is part of RFC XXXX; see the RFC itself
for full legal notices. for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
the Link Management Protocol (LMP) as the Link Management Protocol (LMP) as
defined in 'Link Management Protocol'." defined in 'Link Management Protocol'."
-- Revision history. -- Revision history.
REVISION REVISION
"200403031200Z" -- 3 March 2004 12:00:00 EST "200405241200Z" -- 24 May 2004 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC "Initial version published as RFC xxxx (to be assigned by RFC
Editor)" Editor)"
::= { transmission xxx } -- To be assigned by IANA. ::= { transmission xxx } -- To be assigned by IANA.
-- Request to assign same number as LMP -- Request to assign same number as LMP
-- ifType. -- ifType.
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
skipping to change at page 37, line 19 skipping to change at page 37, line 19
TE link information. ifIndex is the common index to all TE link information. ifIndex is the common index to all
tables." tables."
::= { lmpObjects 12 } ::= { lmpObjects 12 }
lmpTeLinkEntry OBJECT-TYPE lmpTeLinkEntry OBJECT-TYPE
SYNTAX LmpTeLinkEntry SYNTAX LmpTeLinkEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry with an "An entry in this table exists for each ifEntry with an
ifType of teLink(200), i.e. for every TE link. An ifEntry ifType of teLink(200) that is managed by LMP. An ifEntry with
with an ifIndex must exist before the corresponding an ifIndex must exist before the corresponding lmpTeLinkEntry is
lmpTeLinkEntry is created. If a TE link entry in the ifTable created. If a TE link entry in the ifTable is destroyed, then so
is destroyed, then so is the corresponding entry in the is the corresponding entry in the lmpTeLinkTable. The
lmpTeLinkTable. The administrative status value is controlled administrative status value is controlled from the ifEntry.
from the ifEntry. Setting the administrative status to Setting the administrative status to testing prompts LMP to
testing prompts LMP to start link verification on the TE link. start link verification on the TE link. Information about the TE
Information about the TE link that is not LMP specific is link that is not LMP specific is contained in teLinkTable of the
contained in teLinkTable of the TE-LINK-STD-MIB MIB module." TE-LINK-STD-MIB MIB module."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpTeLinkTable 1 } ::= { lmpTeLinkTable 1 }
LmpTeLinkEntry ::= SEQUENCE { LmpTeLinkEntry ::= SEQUENCE {
lmpTeLinkNbrRemoteNodeId LmpNodeId, lmpTeLinkNbrRemoteNodeId LmpNodeId,
lmpTeLinkVerification TruthValue, lmpTeLinkVerification TruthValue,
lmpTeLinkFaultManagement TruthValue, lmpTeLinkFaultManagement TruthValue,
lmpTeLinkDwdm TruthValue, lmpTeLinkDwdm TruthValue,
lmpTeLinkOperStatus INTEGER, lmpTeLinkOperStatus INTEGER,
lmpTeLinkRowStatus RowStatus, lmpTeLinkRowStatus RowStatus,
skipping to change at page 38, line 10 skipping to change at page 38, line 10
may be learned during control channel parameter negotiation may be learned during control channel parameter negotiation
phase (in the Config message). Node ID address type must phase (in the Config message). Node ID address type must
be IPv4." be IPv4."
::= { 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 LMP link verification procedure
procedure is enabled for this TE link." is enabled for this TE link."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { 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 LMP fault management procedure
procedure is enabled on this TE link." is enabled on this TE link."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { 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 LMP DWDM procedure is enabled
is enabled on this TE link." on this TE link."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol (LMP) for Dense Wavelength Division
Multiplexing (DWDM) Optical Line Systems, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP-WDM]
::= { lmpTeLinkEntry 4 } ::= { lmpTeLinkEntry 4 }
lmpTeLinkOperStatus OBJECT-TYPE lmpTeLinkOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), down(2), testing(3), init(4), degraded(5) 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
skipping to change at page 39, line 36 skipping to change at page 39, line 37
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row in the "The storage type for this conceptual row in the
lmpTeLinkTable. Conceptual rows having the value lmpTeLinkTable. Conceptual rows having the value
'permanent' need not allow write-access to any 'permanent' need not allow write-access to any
columnar object in the row." columnar object in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { lmpTeLinkEntry 7 } ::= { lmpTeLinkEntry 7 }
-- End of lmpTeLinkTable -- End of lmpTeLinkTable
lmpLinkVerificationInterval OBJECT-TYPE lmpGlobalLinkVerificationInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "ms" UNITS "ms"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates how often the link verification "This object indicates how often the link verification
procedure is executed. The interval is in milliseconds. procedure is executed. The interval is in milliseconds.
A value of 0 is used to indicate that the link A value of 0 is used to indicate that the link
verification procedure should not be executed. The verification procedure should not be executed. The
interval specified in this object should be large enough interval specified in this object should be large enough
skipping to change at page 40, line 25 skipping to change at page 40, line 26
::= { lmpObjects 14 } ::= { lmpObjects 14 }
lmpLinkVerificationEntry OBJECT-TYPE lmpLinkVerificationEntry OBJECT-TYPE
SYNTAX LmpLinkVerificationEntry SYNTAX LmpLinkVerificationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
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 TE link that supports the LMP verification every TE link that supports the LMP verification
procedure." procedure."
AUGMENTS { lmpTeLinkEntry } INDEX { ifIndex }
::= { lmpLinkVerificationTable 1 } ::= { lmpLinkVerificationTable 1 }
LmpLinkVerificationEntry ::= SEQUENCE { LmpLinkVerificationEntry ::= SEQUENCE {
lmpVerifyInterval LmpInterval, lmpLinkVerifyInterval LmpInterval,
lmpVerifyDeadInterval LmpInterval, lmpLinkVerifyDeadInterval LmpInterval,
lmpVerifyTransportMechanism BITS, lmpLinkVerifyTransportMechanism BITS,
lmpVerifyAllLinks TruthValue, lmpLinkVerifyAllLinks TruthValue,
lmpVerifyTransmissionRate Unsigned32, lmpLinkVerifyTransmissionRate Unsigned32,
lmpVerifyWavelength Unsigned32 lmpLinkVerifyWavelength Unsigned32,
lmpLinkVerifyRowStatus RowStatus,
lmpLinkVerifyStorageType StorageType
} }
lmpVerifyInterval OBJECT-TYPE lmpLinkVerifyInterval 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 in the LMP link verification process. It indicates the
interval at which the Test messages are sent." interval at which the Test messages are sent."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpLinkVerificationEntry 1 } ::= { lmpLinkVerificationEntry 1 }
lmpVerifyDeadInterval OBJECT-TYPE lmpLinkVerifyDeadInterval 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- in the verification of the physical connectivity of data-
bearing links. It specifies the observation period used to bearing links. It specifies the observation period used to
detect a Test message at the remote node." detect a Test message at the remote node."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpLinkVerificationEntry 2 } ::= { lmpLinkVerificationEntry 2 }
lmpVerifyTransportMechanism OBJECT-TYPE lmpLinkVerifyTransportMechanism OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
-- All encoding types: -- All encoding types:
payload(0), payload(0),
-- SONET/SDH encoding type: -- SONET/SDH encoding type:
dccSectionOverheadBytes(1), dccSectionOverheadBytes(1),
dccLineOverheadBytes(2), dccLineOverheadBytes(2),
j0Trace(3), j0Trace(3),
j1Trace(4), j1Trace(4),
j2Trace(5) j2Trace(5)
} }
skipping to change at page 41, line 48 skipping to change at page 41, line 50
messages. The receiver chooses the appropriate mechanism in the messages. The receiver chooses the appropriate mechanism in the
BeginVerifyAck message." BeginVerifyAck message."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx and "Link Management Protocol, RFC xxx and
SONET/SDH Encoding for Link Management Protocol (LMP) SONET/SDH Encoding for Link Management Protocol (LMP)
Test Messages, RFC xxx" Test Messages, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] and [LMP-TEST] -- [LMP] and [LMP-TEST]
::= { lmpLinkVerificationEntry 3 } ::= { lmpLinkVerificationEntry 3 }
lmpVerifyAllLinks OBJECT-TYPE lmpLinkVerifyAllLinks OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value of true(2) for this object indicates that the "A value of true(2) for this object indicates that the
verification process checks all unallocated links, otherwise verification process checks all unallocated links, otherwise
only the new ports or component links that have been added to only the new ports or component links that have been added to
this TE link are verified." this TE link are verified."
::= { lmpLinkVerificationEntry 4 } ::= { lmpLinkVerificationEntry 4 }
lmpVerifyTransmissionRate OBJECT-TYPE lmpLinkVerifyTransmissionRate OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "bytes per second" UNITS "bytes per second"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the transmission rate of the data link over which "This is the transmission rate of the data link over which
the Test messages will be transmitted and is expressed in the Test messages will be transmitted and is expressed in
bytes per second." bytes per second."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpLinkVerificationEntry 5 } ::= { lmpLinkVerificationEntry 5 }
lmpVerifyWavelength OBJECT-TYPE lmpLinkVerifyWavelength OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "nm" UNITS "nanometers"
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 corresponds to a separate wavelength, than this value should
be set to 0." be set to 0."
REFERENCE REFERENCE
"Link Management Protocol, RFC xxx" "Link Management Protocol, RFC xxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [LMP] -- [LMP]
::= { lmpLinkVerificationEntry 6 } ::= { lmpLinkVerificationEntry 6 }
lmpLinkVerifyRowStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"This variable is used to create, modify, and/or
delete a row in this table. None of the writable objects
in a row can be changed if the status is active(1).
All read-create objects must have valid and consistent
values before the row can be activated."
::= { lmpLinkVerificationEntry 7 }
lmpLinkVerifyStorageType OBJECT-TYPE
SYNTAX StorageType
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The storage type for this conceptual row in the
lmpLinkVerificationTable. Conceptual rows having the value
'permanent' need not allow write-access to any
columnar object in the row."
DEFVAL { nonVolatile }
::= { lmpLinkVerificationEntry 8 }
-- 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
DESCRIPTION DESCRIPTION
"This table specifies LMP TE link performance counters." "This table specifies LMP TE link performance counters."
skipping to change at page 60, line 41 skipping to change at page 61, line 21
DESCRIPTION DESCRIPTION
"This notification is generated when a TE link property "This notification is generated when a TE link property
mismatch is detected on the node. The received remote TE link mismatch is detected on the node. The received remote TE link
id of the misconfigured TE link is represented by either id of the misconfigured TE link is represented by either
teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether teLinkRemoteIpAddr or teLinkIncomingIfId depending on whether
the TE link is numbered or unnumbered. This notification the TE link is numbered or unnumbered. This notification
should not be sent unless lmpLinkPropertyNotificationsEnabled should not be sent unless lmpLinkPropertyNotificationsEnabled
is true. It is recommended that this notification be reported is true. It is recommended that this notification be reported
only the first time a mismatch is detected. Otherwise, for a only the first time a mismatch is detected. Otherwise, for a
given TE link, this notification can occur no more than once given TE link, this notification can occur no more than once
per verification interval (lmpLinkVerificationInterval)." per verification interval (lmpGlobalLinkVerificationInterval)."
::= { lmpNotifications 1 } ::= { lmpNotifications 1 }
lmpDataLinkPropertyMismatch NOTIFICATION-TYPE lmpDataLinkPropertyMismatch NOTIFICATION-TYPE
OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId } OBJECTS { lmpDataLinkType, lmpDataLinkRemoteIfId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a data-bearing link "This notification is generated when a data-bearing link
property mismatch is detected on the node. lmpDataLinkType property mismatch is detected on the node. lmpDataLinkType
is used to identify the local identifiers associated with is used to identify the local identifiers associated with
the data link (the data link interface index can be used the data link (the data link interface index can be used
to determine the TE link interface index as this to determine the TE link interface index as this
relationship is captured in the interface stack table). relationship is captured in the interface stack table).
The remote entity interface id is the remote entity The remote entity interface id is the remote entity
interface id received in the LinkSummary message. interface id received in the LinkSummary message.
This notification should not be sent unless This notification should not be sent unless
lmpLinkPropertyNotificationsEnabled is true. It is lmpLinkPropertyNotificationsEnabled is true. It is
recommended that this notification be reported only the recommended that this notification be reported only the
first time a mismatch is detected. Otherwise, for a given first time a mismatch is detected. Otherwise, for a given
data link, this notification can occur no more than once data link, this notification can occur no more than once
per verification interval (lmpLinkVerificationInterval)." per verification interval (lmpGlobalLinkVerificationInterval)."
::= { lmpNotifications 2 } ::= { lmpNotifications 2 }
-- Neighbor Notification -- Neighbor Notification
lmpUnprotected NOTIFICATION-TYPE lmpUnprotected NOTIFICATION-TYPE
OBJECTS { lmpCcNbrNodeId } OBJECTS { lmpCcNbrNodeId }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when there are more than one "This notification is generated when there are more than one
control channels between LMP neighbors and the last redundant control channels between LMP neighbors and the last redundant
skipping to change at page 62, line 39 skipping to change at page 63, line 18
lmpDataLinkVerificationFailure NOTIFICATION-TYPE lmpDataLinkVerificationFailure NOTIFICATION-TYPE
OBJECTS { lmpDataLinkActiveOperStatus, OBJECTS { lmpDataLinkActiveOperStatus,
lmpDataLinkPassiveOperStatus } lmpDataLinkPassiveOperStatus }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This notification is generated when a data-bearing "This notification is generated when a data-bearing
link verification fails. This notification should not be sent link verification fails. This notification should not be sent
unless lmpDataLinkNotificationsEnabled is true. For a given unless lmpDataLinkNotificationsEnabled is true. For a given
data link, this notification can occur no more than once per data link, this notification can occur no more than once per
verification interval (lmpLinkVerificationInterval)." verification interval (lmpGlobalLinkVerificationInterval)."
::= { lmpNotifications 8 } ::= { lmpNotifications 8 }
-- End of notifications -- End of notifications
-- Module compliance -- Module compliance
lmpCompliances lmpCompliances
OBJECT IDENTIFIER ::= { lmpConformance 1 } OBJECT IDENTIFIER ::= { lmpConformance 1 }
lmpGroups lmpGroups
skipping to change at page 66, line 19 skipping to change at page 66, line 46
DESCRIPTION DESCRIPTION
"This group is optional." "This group is optional."
-- Scalars -- Scalars
OBJECT lmpAdminStatus OBJECT lmpAdminStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpLinkVerificationInterval OBJECT lmpGlobalLinkVerificationInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcHelloIntervalDefault OBJECT lmpCcHelloIntervalDefault
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpCcHelloIntervalDefaultMin OBJECT lmpCcHelloIntervalDefaultMin
skipping to change at page 69, line 24 skipping to change at page 69, line 51
"A value of configSnd(3), configRcv(4), active(5), "A value of configSnd(3), configRcv(4), active(5),
goingDown(6) need not be supported." goingDown(6) need not be supported."
OBJECT lmpCcStorageType OBJECT lmpCcStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpLinkVerificationTable -- lmpLinkVerificationTable
OBJECT lmpVerifyInterval OBJECT lmpLinkVerifyInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpVerifyDeadInterval OBJECT lmpLinkVerifyDeadInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpVerifyAllLinks OBJECT lmpLinkVerifyAllLinks
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpTeLinkTable -- lmpTeLinkTable
OBJECT lmpTeLinkNbrRemoteNodeId OBJECT lmpTeLinkNbrRemoteNodeId
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required if the link verification "Write access is not required if the link verification
skipping to change at page 70, line 25 skipping to change at page 71, line 4
SYNTAX INTEGER { up(1), down(2), degraded(5) } SYNTAX INTEGER { up(1), down(2), degraded(5) }
DESCRIPTION DESCRIPTION
"The testing(3) and init(4) state need not be supported." "The testing(3) and init(4) state need not be supported."
OBJECT lmpTeLinkRowStatus OBJECT lmpTeLinkRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required and active(1) is the "Write access is not required and active(1) is the
only status that needs to be supported." only status that needs to be supported."
OBJECT lmpTeLinkStorageType OBJECT lmpTeLinkStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpTeLinkVerificationTable -- lmpTeLinkVerificationTable
OBJECT lmpVerifyTransmissionRate OBJECT lmpLinkVerifyTransmissionRate
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT lmpVerifyWavelength OBJECT lmpLinkVerifyWavelength
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT lmpLinkVerifyRowStatus
SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required and active(1) is the
only status that needs to be supported."
OBJECT lmpLinkVerifyStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
-- lmpDataLinkTable -- lmpDataLinkTable
OBJECT lmpDataLinkAddressType OBJECT lmpDataLinkAddressType
SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) } SYNTAX INTEGER { unknown(0), ipv4(1), ipv6(2) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 73, line 44 skipping to change at page 74, line 36
lmpLinkPropertyCorrelationGroup OBJECT-GROUP lmpLinkPropertyCorrelationGroup OBJECT-GROUP
OBJECTS { lmpLinkPropertyNotificationsEnabled } OBJECTS { lmpLinkPropertyNotificationsEnabled }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects used to configure the link "Collection of objects used to configure the link
property correlation procedure." property correlation procedure."
::= { lmpGroups 5 } ::= { lmpGroups 5 }
lmpLinkVerificationGroup OBJECT-GROUP lmpLinkVerificationGroup OBJECT-GROUP
OBJECTS { lmpLinkVerificationInterval, OBJECTS { lmpGlobalLinkVerificationInterval,
lmpVerifyInterval, lmpLinkVerifyInterval,
lmpVerifyDeadInterval, lmpLinkVerifyDeadInterval,
lmpVerifyTransportMechanism, lmpLinkVerifyTransportMechanism,
lmpVerifyAllLinks, lmpLinkVerifyAllLinks,
lmpVerifyTransmissionRate, lmpLinkVerifyTransmissionRate,
lmpVerifyWavelength, lmpLinkVerifyWavelength,
lmpLinkVerifyRowStatus,
lmpLinkVerifyStorageType,
lmpDataLinkNotificationsEnabled lmpDataLinkNotificationsEnabled
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects that represent the link "Collection of objects that represent the link
verification procedure configuration." verification procedure configuration."
::= { lmpGroups 6 } ::= { lmpGroups 6 }
lmpPerfGroup OBJECT-GROUP lmpPerfGroup OBJECT-GROUP
OBJECTS { lmpCcInOctets, OBJECTS { lmpCcInOctets,
skipping to change at page 77, line 49 skipping to change at page 78, line 42
be obtained from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
By submitting this Internet Draft, we certify that any applicable By submitting this Internet Draft, we certify that any applicable
patent or other IPR claims of which we are aware have been disclosed, patent or other IPR claims of which we are aware have been disclosed,
in accordance with RFC 3667. and any of which we become aware will be disclosed, in accordance
with RFC 3668.
11. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB module There are a number of management objects defined in this MIB module
with a MAX-ACCESS clause of read-write and/or read-create. Such with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
skipping to change at page 79, line 34 skipping to change at page 80, line 26
LMP-MIB should be rooted under the transmission subtree. The IANA is LMP-MIB should be rooted under the transmission subtree. The IANA is
requested to assign { transmission TBD } to the LMP-MIB module requested to assign { transmission TBD } to the LMP-MIB module
specified in this document. The IANA is requested to use same number specified in this document. The IANA is requested to use same number
as the lmp ifType. as the lmp ifType.
14. References 14. References
14.1. Normative References 14.1. Normative References
[RFC2026] Bradner, S., "The Internet Standards Process -
Revision 3", RFC 2026, October 1996.
[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.
[RFC2434] Narten, T., Alvestrand, H., "Guidelines for Writing [RFC2434] Narten, T., Alvestrand, H., "Guidelines for Writing
an IANA Considerations Section in RFCs", RFC 2434, an IANA Considerations Section in RFCs", RFC 2434,
October 1998. October 1998.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Structure of J., Rose, M., and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, Management Information Version 2 (SMIv2)", STD 58,
skipping to change at page 80, line 12 skipping to change at page 81, line 6
J., Rose, M., and S. Waldbusser, "Textual Conventions J., Rose, M., and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M., and S. Waldbusser, "Conformance J., Rose, M., and S. Waldbusser, "Conformance
Statements for SMIv2", STD 58, RFC 2580, April 1999. Statements for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces [RFC2863] McCloghrie, K., and Kastenholtz, F., "The Interfaces
Group MIB", RFC 2863, June 2000. Group MIB", RFC 2863, June 2000.
[RFC2914] Floyd, S., "Congestion Control Principles", RFC 2914,
September 2000.
[RFC3291] Daniele, M., Haberman, B., Routhier, S., and [RFC3291] Daniele, M., Haberman, B., Routhier, S., and
Shoenwaelder, J., "Textual Conventions for Internet Shoenwaelder, J., "Textual Conventions for Internet
Network Addresses", RFC 3291, May 2002. Network Addresses", RFC 3291, May 2002.
[RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L., [RFC3471] Ashwood-Smith, P., Banarjee, A., Berger, L.,
Bernstein, G., Drake, J., Fan, Y., Kompella, K., Bernstein, G., Drake, J., Fan, Y., Kompella, K.,
Lang, J., Mannie, E., Rajagopalan, B., Rekhter, Y., Lang, J., Mannie, E., Rajagopalan, B., Rekhter, Y.,
Saha, D., Sharma, V., Swallow, G., and Tang, B., Saha, D., Sharma, V., Swallow, G., and Tang, B.,
"Generalized MPLS Signaling Functional Description", "Generalized MPLS Signaling Functional Description",
RFC 3471, January 2003. RFC 3471, January 2003.
[RFC3667] Bradner, S., "IETF Rights in Contributions", [RFC3667] Bradner, S., "IETF Rights in Contributions",
RFC 3667, February 2004. RFC 3667, February 2004.
[BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., [RFC3668] Bradner, S., "Intellectual Property Rights in IETF
"Link Bundling in MPLS Traffic Engineering", Technology", RFC 3668, February 2004.
Internet Draft <draft-ietf-mpls-bundle-04.txt>,
July 2002.
[TELINK-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., [TELINK-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,
"Traffic Engineering Link Management Information "Traffic Engineering Link Management Information
Base", Internet Draft Base", Internet Draft
<draft-ietf-mpls-telink-mib-06.txt>, February 2004. <draft-ietf-mpls-telink-mib-07.txt>, May 2004.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Saha, S., Basak, D., Rekhter, Y., Berger, L., Saha, S., Basak, D.,
Sandick, H., Zinin, A., Rajagopalan, B., and Sandick, H., Zinin, A., Rajagopalan, B., and
Ramamoorthi, S., "Link Management Protocol", Ramamoorthi, S., "Link Management Protocol",
Internet Draft <draft-ietf-ccamp-lmp-10.txt>, Internet Draft <draft-ietf-ccamp-lmp-10.txt>,
October 2003. October 2003.
[LMP-WDM] Fredette, A., Lang, J., "Link Management Protocol (LMP)
for Dense Wavelength Division Multiplexing (DWDM)
Optical Line Systems", Internet Draft
<draft-ietf-ccamp-lmp-wdm-03.txt>, December 2003.
[LMP-TEST] Lang, J., Papadimitriou, D., "SONET/SDH Encoding [LMP-TEST] Lang, J., Papadimitriou, D., "SONET/SDH Encoding
for Link Management (LMP) Test Messages", Internet for Link Management (LMP) Test Messages", Internet
Draft <draft-ietf-ccamp-lmp-test-sonet-sdh-04.txt>, Draft <draft-ietf-ccamp-lmp-test-sonet-sdh-04.txt>,
December 2003. December 2003.
14.2. Informative References 14.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for "Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410, Internet-Standard Management Framework", RFC 3410,
December 2002. December 2002.
[BUNDLING] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-04.txt>,
July 2002.
15. Authors' Addresses 15. Authors' Addresses
Martin Dubuc Jonathan P. Lang Martin Dubuc Jonathan P. Lang
Email: dubuc.consulting@rogers.com Rincon Networks, Inc. Email: mdubuc@ncf.ca Rincon Networks, Inc.
110 El Paseo 110 El Paseo
Santa Barbara, CA 93101 Santa Barbara, CA 93101
Email: jplang@ieee.org Email: jplang@ieee.org
Sudheer Dharanikota Evan McGinnis Sudheer Dharanikota Evan McGinnis
Email: sudheer@ieee.org Calient Networks, Inc. Email: sudheer@ieee.org 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
 End of changes. 

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