draft-ietf-ccamp-lmp-mib-04.txt   draft-ietf-ccamp-lmp-mib-05.txt 
Network Working Group Martin Dubuc Network Working Group Martin Dubuc
Internet Draft Editor Internet Draft
Expires: May 2003 Category: Standards Track Sudheer Dharanikota
Sudheer Dharanikota Expires: October 2003 Avici Systems
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Rincon Networks
Evan McGinnis Evan McGinnis
Calient Networks Calient Networks
November 2002 April 2003
Link Management Protocol Management Information Base Link Management Protocol Management Information Base
draft-ietf-ccamp-lmp-mib-04.txt draft-ietf-ccamp-lmp-mib-05.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 41 skipping to change at page 1, line 43
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community.
In particular, it describes managed objects for modeling the Link
Management Protocol (LMP).
Table of Contents Table of Contents
1. Abstract . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 1. The Internet-Standard Management Framework . . . . . . . . . . 2
2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 2. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The SNMP Management Framework . . . . . . . . . . . . . . . . . 3 4. The SNMP Management Framework . . . . . . . . . . . . . . . . . 4
5. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . 4 5. Feature Checklist . . . . . . . . . . . . . . . . . . . . . . . 5
6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 6. Outline . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
6.1. Summary of LMP MIB . . . . . . . . . . . . . . . . . . . . . . 5 6.1. Summary of LMP MIB . . . . . . . . . . . . . . . . . . . . . . 6
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 . . . . . . . . . . . . . . . . . . 7
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. Intellectual Property Considerations . . . . . . . . . . . . . 75
12. Security Considerations . . . . . . . . . . . . . . . . . . . . 77 12. Security Considerations . . . . . . . . . . . . . . . . . . . . 75
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 78 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 76
14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 79 14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 76
14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 79 14.1 Normative References . . . . . . . . . . . . . . . . . . . . . 76
14.2 Informative References . . . . . . . . . . . . . . . . . . . . 80 14.2 Informative References . . . . . . . . . . . . . . . . . . . . 78
15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 81 15. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 79
16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 81 16. Full Copyright Statement . . . . . . . . . . . . . . . . . . . 79
1. Abstract 1. The Internet-Standard Management Framework
This memo defines a portion of the Management Information Base (MIB) For a detailed overview of the documents that describe the current
for use with network management protocols in the Internet community. Internet-Standard Management Framework, please refer to section 7 of
In particular, it describes managed objects for modeling the Link RFC 3410 [RFC3410].
Management Protocol (LMP).
Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58,
RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580].
2. Introduction 2. Introduction
Current work is underway in the IETF to specify a suite of protocols Current work is underway in the IETF to specify a suite of protocols
to be used as a common control plane and a separate common measure- to be used as a common control plane and a separate common measure-
ment plane. Along with Generalized MPLS (GMPLS) [GMPLS], the Link ment plane. Along with Generalized MPLS (GMPLS) [RFC3471], the Link
Management Protocol [LMP], which primary purpose is to manage traffic Management Protocol [LMP], which primary purpose is to manage traffic
engineering (TE) links, is one of the key components of this stan- engineering (TE) links, is one of the key components of this stan-
dardization activity. Primary goals of LMP are the maintenance of the dardization activity. Primary goals of LMP are the maintenance of the
control channel connectivity, correlation of link properties, verifi- control channel connectivity, correlation of link properties, verifi-
cation of data-bearing links and detection and isolation of link cation of data-bearing links and detection and isolation of link
faults. faults.
We describe in this document a MIB that can be used to manage LMP We describe in this document a MIB that can be used to manage LMP
implementations. This MIB covers both configuration and performance implementations. This MIB covers both configuration and performance
monitoring aspects of LMP. monitoring aspects of LMP.
skipping to change at page 5, line 10 skipping to change at page 5, line 30
- The MIB is used to express the mapping between local and remote - The MIB is used to express the mapping between local and remote
TE links, as well as local and remote interface identifiers for TE links, as well as local and remote interface identifiers for
port or component link. port or component link.
- Performance counters are provided for measuring LMP - Performance counters are provided for measuring LMP
performance on a per-control channel basis. Performance counters performance on a per-control channel basis. Performance counters
are also provided for measuring LMP performance on the data- are also provided for measuring LMP performance on the data-
bearing links. bearing links.
Note that the LMP MIB goes hand-in-hand with the Link Bundling MIB Note that the LMP MIB goes hand-in-hand with the TE Link MIB [TELINK-
[BUNDLE-MIB]. The TE link table, which is used to associate data- MIB]. The TE link table, which is used to associate data-bearing
bearing links to TE links, is defined in the Link Bundling MIB. The links to TE links, is defined in the TE Link MIB. The TE link table
TE link table in the LMP MIB contains TE link information specific to in the LMP MIB contains TE link information specific to LMP.
LMP.
6. Outline 6. Outline
Configuring LMP through an optical device involves the following Configuring LMP through an optical device involves the following
steps: steps:
- Enabling LMP on LMP capable interfaces through control channel - Enabling LMP on LMP capable interfaces through control channel
configuration. configuration.
- Optionally specifying link verification parameters. - Optionally specifying link verification parameters.
skipping to change at page 9, line 7 skipping to change at page 9, line 30
ifIndex = 44, ifIndex = 44,
lmpDataLinkNumberingType = unnumbered(1), lmpDataLinkNumberingType = unnumbered(1),
lmpDataLinkRemoteIfId = 48, lmpDataLinkRemoteIfId = 48,
lmpDataLinkRowStatus = createAndGo(4) lmpDataLinkRowStatus = createAndGo(4)
} }
Note that the data-bearing link type (lmpDataLinkType) does Note that the data-bearing link type (lmpDataLinkType) does
not need to be provisioned as it is automatically populated by the not need to be provisioned as it is automatically populated by the
node. The definition of the protection role (primary or node. The definition of the protection role (primary or
secondary) for the data-bearing links is stored in the secondary) for the data-bearing links is stored in the
componentLinkTable of the Link Bundling MIB [BUNDLE-MIB]. componentLinkTable of the TE Link MIB [TELINK-MIB].
Then, a TE link is created as an ifEntry with ifType teLink in Then, a TE link is created as an ifEntry with ifType teLink in
the ifTable. the ifTable.
Once the TE link is created in the ifTable, a TE link entry Once the TE link is created in the ifTable, a TE link entry
is created in the LMP MIB to specify TE link information specific is created in the LMP MIB to specify TE link information specific
to LMP. to LMP.
In lmpTeLinkTable: In lmpTeLinkTable:
{ {
skipping to change at page 9, line 31 skipping to change at page 10, line 6
lmpTeLinkDwdm = false(1), lmpTeLinkDwdm = false(1),
lmpTeLinkBitRate = 100000, lmpTeLinkBitRate = 100000,
lmpTeLinkWavelength = 0, lmpTeLinkWavelength = 0,
lmpTeLinkRowStatus = createAndGo(4) lmpTeLinkRowStatus = createAndGo(4)
} }
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 Link Bundling MIB may be created in the teLinkTable of TE Link MIB
[BUNDLE-MIB]. [TELINK-MIB].
9. Application of the Interfaces Group to LMP 9. Application of the Interfaces Group to LMP
The Interfaces Group [RFC2863] defines generic managed objects for The Interfaces Group [RFC2863] defines generic managed objects for
managing interfaces. This memo contains the media-specific managing interfaces. This memo contains the media-specific
extensions to the Interfaces Group for managing LMP control channels extensions to the Interfaces Group for managing LMP control channels
that are modeled as interfaces. If the control channel as defined in that are modeled as interfaces. If the control channel as defined in
the lmpControlChannelTable is modeled as an ifEntry, then the the lmpControlChannelTable is modeled as an ifEntry, then the
following definition applies. An lmpControlChannelTable entry is following definition applies. An lmpControlChannelTable entry is
designated as being represented as an Interfaces MIB ifEntry if the designated as being represented as an Interfaces MIB ifEntry if the
skipping to change at page 12, line 22 skipping to change at page 12, line 45
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 TE-LINK-MIB;
lmpMIB MODULE-IDENTITY lmpMIB MODULE-IDENTITY
LAST-UPDATED "200211011200Z" -- 1 November 2002 12:00:00 EST LAST-UPDATED "200304181200Z" -- 18 April 2003 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@avici.com
Thomas D. Nadeau Thomas D. Nadeau
Postal: Cisco Systems, Inc.
300 Apollo Drive
Chelmsford, MA 01824
Tel: +1-978-244-3051
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Jonathan P. Lang Jonathan P. Lang
Postal: Calient Networks, Inc. Email: jplang@ieee.org
25 Castilian Drive
Goleta, CA 93117
Email: jplang@calient.net
Evan McGinnis Evan McGinnis
Postal: Calient Networks, Inc.
5853 Rue Ferrari
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., Basak, D., Rekhter, Y., Berger, L., Saha, D., 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-06.txt>, Internet Draft <draft-ietf-ccamp-lmp-08.txt>,
September 2002." March 2003."
-- Revision history. -- Revision history.
REVISION REVISION
"200211011200Z" -- November 1 2002 12:00:00 EST "200304181200Z" -- 18 April 2003 12:00:00 EST
DESCRIPTION DESCRIPTION
"Initial version published as RFC xxxx (to be assigned by RFC Editor)" "Initial version published as RFC xxxx (to be assigned by RFC Editor)"
::= { mib-2 xxx } -- To be assigned by IANA (experimental 113 can be used ::= { mib-2 xxx } -- To be assigned by IANA (experimental 113 can be used
-- in the interim) -- in the interim)
-- Textual Conventions -- Textual Conventions
LmpInterval ::= TEXTUAL-CONVENTION LmpInterval ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
skipping to change at page 36, line 21 skipping to change at page 36, line 28
DESCRIPTION DESCRIPTION
"This table contains a collection of TE link." "This table contains a collection of TE link."
::= { 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(TBD), i.e. for every TE link. An ifEntry ifType of teLink(200), i.e. for every TE link. An ifEntry
with an ifIndex must exist before the corresponding with an ifIndex must exist before the corresponding
teLinkEntry is created. If a TE link entry in the ifTable is teLinkEntry is created. If a TE link entry in the ifTable is
destroyed, then so is the corresponding entry in the destroyed, then so is the corresponding entry in the
teLinkTable. The administrative status value is controlled teLinkTable. The administrative status value is controlled
from the ifEntry. Setting the administrative status to from the ifEntry. Setting the administrative status to
testing prompts LMP to start link verification on the TE link. testing prompts LMP to start link verification on the TE link.
Information about the TE link that is not LMP specific is also Information about the TE link that is not LMP specific is also
contained in teLinkTable [BUNDLE-MIB]." contained in teLinkTable [TELINK-MIB]."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpTeLinkTable 1 } ::= { lmpTeLinkTable 1 }
LmpTeLinkEntry ::= SEQUENCE { LmpTeLinkEntry ::= SEQUENCE {
lmpTeLinkNbrNodeId InetAddress, lmpTeLinkNbrNodeId InetAddress,
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 50, line 33 skipping to change at page 50, line 44
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in this table exists for each ifEntry that represents "An entry in this table exists for each ifEntry that represents
a data-bearing link. An ifEntry with an ifIndex must exist a data-bearing link. An ifEntry with an ifIndex must exist
before the corresponding lmpDataLinkEntry is created. before the corresponding lmpDataLinkEntry is created.
If an entry representing the data-bearing link is destroyed in If an entry representing the data-bearing link is destroyed in
the ifTable, then so is the corresponding entry in the the ifTable, then so is the corresponding entry in the
lmpDataLinkTable. The administrative status value is lmpDataLinkTable. The administrative status value is
controlled from the ifEntry. The index to this table also controlled from the ifEntry. The index to this table also
used to get information in the componentLinkTable used to get information in the componentLinkTable
[BUNDLE-MIB]." [TELINK-MIB]."
INDEX { ifIndex } INDEX { ifIndex }
::= { lmpDataLinkTable 1 } ::= { lmpDataLinkTable 1 }
LmpDataLinkEntry ::= SEQUENCE { LmpDataLinkEntry ::= SEQUENCE {
lmpDataLinkType INTEGER, lmpDataLinkType INTEGER,
lmpDataLinkIpAddrType InetAddressType, lmpDataLinkIpAddrType InetAddressType,
lmpDataLinkIpAddr InetAddress, lmpDataLinkIpAddr InetAddress,
lmpDataLinkRemoteIpAddress InetAddress, lmpDataLinkRemoteIpAddress InetAddress,
lmpDataLinkRemoteIfId InterfaceIndexOrZero, lmpDataLinkRemoteIfId InterfaceIndexOrZero,
lmpDataLinkEncodingType INTEGER, lmpDataLinkEncodingType INTEGER,
skipping to change at page 52, line 29 skipping to change at page 52, line 40
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
"[GMPLS]" "[RFC3471]"
::= { 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
skipping to change at page 76, line 45 skipping to change at page 77, line 10
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.
[RFC2401] Kent, S., and Atkinson, R., "Security Architecture [RFC2401] Kent, S., and Atkinson, R., "Security Architecture
for the Internet Protocol", RFC 2401, November for the Internet Protocol", RFC 2401, November
1998. 1998.
[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.
[RFC3471] 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",
RFC 3471, January 2003.
[Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers",
RFC 1700, October 1994. See also: RFC 1700, October 1994. See also:
http://www.iana.org/assignments/smi-numbers http://www.iana.org/assignments/smi-numbers
[BUNDLE] Kompella, K., Rekhter, Y., and Berger, L., [BUNDLE] Kompella, K., Rekhter, Y., and Berger, L.,
"Link Bundling in MPLS Traffic Engineering", "Link Bundling in MPLS Traffic Engineering",
Internet Draft <draft-ietf-mpls-bundle-04.txt>, Internet Draft <draft-ietf-mpls-bundle-04.txt>,
July 2002. July 2002.
[BUNDLE-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J., [TELINK-MIB] Dubuc, M., Dharanikota, S. Nadeau, T., Lang, J.,
"Link Bundling Management Information Base", "Traffic Engineering Link Management Information
Internet Draft <draft-ietf-mpls-bundle-mib-04.txt>, Base", Internet Draft
November 2002. <draft-ietf-mpls-telink-mib-00.txt>, April 2003.
[IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS
FAMILY NUMBERS. See also: FAMILY NUMBERS. See also:
http://www.iana.org/assignments/address-family-numbers http://www.iana.org/assignments/address-family-numbers
For MIB see: http://www.iana.org/assignments/ For MIB see: http://www.iana.org/assignments/
ianaaddressfamilynumbers-mib 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., [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-06.txt>, Internet Draft <draft-ietf-ccamp-lmp-08.txt>,
September 2002. March 2003.
14.2. Informative References 14.2. Informative References
[RFC1155] Rose, M., and McCloghrie, K., "Structure and [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 McCloghrie, K., "Concise MIB Defini- [RFC1212] Rose, M., and McCloghrie, K., "Concise MIB Defini-
tions", 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] Rose, M., "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.
skipping to change at page 78, line 40 skipping to change at page 78, line 50
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.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
15. Authors' Addresses 15. Authors' Addresses
Martin Dubuc Jonathan P. Lang Martin Dubuc Jonathan P. Lang
Email: dubuc.consulting@rogers.com Calient Networks, Inc. Email: dubuc.consulting@rogers.com Rincon Networks, Inc.
25 Castilian Drive 110 El Paseo
Goleta, CA 93117 Santa Barbara, CA 93101
Email: jplang@calient.net Email: jplang@ieee.org
Sudheer Dharanikota Evan McGinnis Sudheer Dharanikota Evan McGinnis
Email: sudheer@ieee.org Calient Networks, Inc. Avici Systems, Inc. Calient Networks, Inc.
5853 Rue Ferrari 101 Billerica Avenue 5853 Rue Ferrari
San Jose, CA 95138 N Billerica, MA 08162 San Jose, CA 95138
Email: evan@calient.net Email: sudheer@avici.com Email: evan@calient.net
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
16. Full Copyright Statement 16. Full Copyright Statement
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2003). 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
copyright notice or references to the Internet Society or other copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of develop- Internet organizations, except as needed for the purpose of develop-
 End of changes. 

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