draft-ietf-mpls-lc-if-mib-05.txt   draft-ietf-mpls-lc-if-mib-06.txt 
Network Working Group Thomas D. Nadeau Network Working Group Thomas D. Nadeau
Internet Draft Subrahmanya Hegde Internet Draft Subrahmanya Hegde
Expires: October 2005 Cisco Systems, Inc. Expires: October 2005 Cisco Systems, Inc.
April 2005 April 2005
Multiprotocol Label Switching (MPLS) Label-Controlled ATM Multiprotocol Label Switching (MPLS) Label-Controlled ATM
and Frame-Relay Management Interface Definition and Frame-Relay Management Interface Definition
draft-ietf-mpls-lc-if-mib-05.txt draft-ietf-mpls-lc-if-mib-06.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that By submitting this Internet-Draft, each author represents that
any applicable patent or other IPR claims of which he or she is any applicable patent or other IPR claims of which he or she is
aware have been or will be disclosed, and any of which he or she aware have been or will be disclosed, and any of which he or she
becomes aware will be disclosed, in accordance with Section 6 of becomes aware will be disclosed, in accordance with Section 6 of
BCP 79. BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
skipping to change at page 4, line 7 skipping to change at page 4, line 7
FROM SNMPv2-TC FROM SNMPv2-TC
AtmVpIdentifier AtmVpIdentifier
FROM ATM-TC-MIB FROM ATM-TC-MIB
mplsStdMIB, MplsAtmVcIdentifier mplsStdMIB, MplsAtmVcIdentifier
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
mplsInterfaceIndex mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB FROM MPLS-LSR-STD-MIB
; ;
mplsLcAtmStdMIB MODULE-IDENTITY mplsLcAtmStdMIB MODULE-IDENTITY
LAST-UPDATED "200503011200Z" -- 01 March 2005 12:00:00 GMT LAST-UPDATED "200506171200Z" -- 17 June 2005 12:00:00 GMT
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Postal: Cisco Systems, Inc. Postal: Cisco Systems, Inc.
250 Apollo Drive 250 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
Subrahmanya Hegde Subrahmanya Hegde
skipping to change at page 4, line 36 skipping to change at page 4, line 36
MPLS Label Controlled ATM interfaces as defined in MPLS Label Controlled ATM interfaces as defined in
[RFC3035]. [RFC3035].
Copyright (C) The Internet Society (2005). This Copyright (C) The Internet Society (2005). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX -- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200504281200Z" -- 28 April 2005 12:00:00 GMT "200506171200Z" -- 17 June 2005 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial revision, published as part of RFC XXXX." "Initial revision, published as part of RFC XXXX."
::= { mplsStdMIB XXX } -- To Be Assigned by IANA ::= { mplsStdMIB XXX } -- To Be Assigned by IANA
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- Tables, Scalars, Notifications, Conformance -- Tables, Scalars, Notifications, Conformance
mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 } mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 }
skipping to change at page 5, line 38 skipping to change at page 5, line 38
MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE { MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE {
mplsLcAtmStdCtrlVpi AtmVpIdentifier, mplsLcAtmStdCtrlVpi AtmVpIdentifier,
mplsLcAtmStdCtrlVci MplsAtmVcIdentifier, mplsLcAtmStdCtrlVci MplsAtmVcIdentifier,
mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier, mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier,
mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier, mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier,
mplsLcAtmStdVcMerge TruthValue, mplsLcAtmStdVcMerge TruthValue,
mplsLcAtmVcDirectlyConnected TruthValue, mplsLcAtmVcDirectlyConnected TruthValue,
mplsLcAtmLcAtmVPI AtmVpIdentifier, mplsLcAtmLcAtmVPI AtmVpIdentifier,
mplsLcAtmStdIfConfRowStatus RowStatus, mplsLcAtmStdIfConfRowStatus RowStatus,
mplsLcAtmStdIfConfStoreType StorageType mplsLcAtmStdIfConfStorageType StorageType
} }
mplsLcAtmStdCtrlVpi OBJECT-TYPE mplsLcAtmStdCtrlVpi OBJECT-TYPE
SYNTAX AtmVpIdentifier SYNTAX AtmVpIdentifier
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the VPI value over which this "This is the VPI value over which this
LSR is willing to accept control traffic on LSR is willing to accept control traffic on
this interface." this interface."
skipping to change at page 7, line 39 skipping to change at page 7, line 39
MUST exist before hand. If an entry is attempted MUST exist before hand. If an entry is attempted
to be created by a manager for a corresponding to be created by a manager for a corresponding
mplsInterfaceConfEntry that does not support LC-ATM, mplsInterfaceConfEntry that does not support LC-ATM,
the agent MUST return an inconsistentValue error. the agent MUST return an inconsistentValue error.
If this table is implemented read-only, then the If this table is implemented read-only, then the
agent must set this object to active(1) when this agent must set this object to active(1) when this
row is made active. If this table is implemented row is made active. If this table is implemented
writable, then an agent MUST not allow modification writable, then an agent MUST not allow modification
to its objects once this value is set to active(1) to its objects once this value is set to active(1)
except mplsLcAtmStdIfConfRowStatus and except mplsLcAtmStdIfConfRowStatus and
mplsLcAtmStdIfConfStoreType." mplsLcAtmStdIfConfStorageType."
::= { mplsLcAtmStdInterfaceConfEntry 8 } ::= { mplsLcAtmStdInterfaceConfEntry 8 }
mplsLcAtmStdIfConfStoreType OBJECT-TYPE mplsLcAtmStdIfConfStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
objects in the row." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLcAtmStdInterfaceConfEntry 9 } ::= { mplsLcAtmStdInterfaceConfEntry 9 }
skipping to change at page 8, line 41 skipping to change at page 8, line 41
WRITE-SYNTAX RowStatus { active(1), notInService(2), WRITE-SYNTAX RowStatus { active(1), notInService(2),
createAndGo(4), destroy(6) createAndGo(4), destroy(6)
} }
DESCRIPTION "Support for createAndWait and notReady is DESCRIPTION "Support for createAndWait and notReady is
not required." not required."
::= { mplsLcAtmStdCompliances 1 } ::= { mplsLcAtmStdCompliances 1 }
-- Compliance requirement for read-only implementations. -- Compliance requirement for read-only implementations.
mplsLcAtmStdModuleROCompliance MODULE-COMPLIANCE mplsLcAtmStdModuleReadOnlyCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Compliance requirement for implementations that only "Compliance requirement for implementations that only
provide read-only support for MPLS-LC-ATM-STD-MIB. provide read-only support for MPLS-LC-ATM-STD-MIB.
Such devices can be monitored but cannot be configured Such devices can be monitored but cannot be configured
using this MIB module. using this MIB module.
" "
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
skipping to change at page 9, line 46 skipping to change at page 9, line 46
OBJECT mplsLcAtmVcDirectlyConnected OBJECT mplsLcAtmVcDirectlyConnected
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmLcAtmVPI OBJECT mplsLcAtmLcAtmVPI
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcAtmStdIfConfStoreType OBJECT mplsLcAtmStdIfConfStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLcAtmStdCompliances 2 } ::= { mplsLcAtmStdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLcAtmStdIfGroup OBJECT-GROUP mplsLcAtmStdIfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLcAtmStdCtrlVpi, mplsLcAtmStdCtrlVpi,
mplsLcAtmStdCtrlVci, mplsLcAtmStdCtrlVci,
mplsLcAtmStdUnlabTrafVpi, mplsLcAtmStdUnlabTrafVpi,
mplsLcAtmStdUnlabTrafVci, mplsLcAtmStdUnlabTrafVci,
mplsLcAtmStdVcMerge, mplsLcAtmStdVcMerge,
mplsLcAtmVcDirectlyConnected, mplsLcAtmVcDirectlyConnected,
mplsLcAtmLcAtmVPI, mplsLcAtmLcAtmVPI,
mplsLcAtmStdIfConfRowStatus, mplsLcAtmStdIfConfRowStatus,
mplsLcAtmStdIfConfStoreType mplsLcAtmStdIfConfStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS LC-ATM "Collection of objects needed for MPLS LC-ATM
interface configuration." interface configuration."
::= { mplsLcAtmStdGroups 1 } ::= { mplsLcAtmStdGroups 1 }
END END
6. MPLS Label Controlled Frame Relay MIB Definitions 6. MPLS Label Controlled Frame Relay MIB Definitions
skipping to change at page 10, line 45 skipping to change at page 10, line 45
RowStatus, StorageType RowStatus, StorageType
FROM SNMPv2-TC FROM SNMPv2-TC
mplsInterfaceIndex mplsInterfaceIndex
FROM MPLS-LSR-STD-MIB FROM MPLS-LSR-STD-MIB
DLCI DLCI
FROM FRAME-RELAY-DTE-MIB FROM FRAME-RELAY-DTE-MIB
mplsStdMIB mplsStdMIB
FROM MPLS-TC-STD-MIB FROM MPLS-TC-STD-MIB
; ;
mplsLcFrStdMIB MODULE-IDENTITY mplsLcFrStdMIB MODULE-IDENTITY
LAST-UPDATED "200503011200Z" -- 01 March 2005 12:00:00 GMT LAST-UPDATED "200506171200Z" -- 17 June 2005 12:00:00 GMT
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group"
CONTACT-INFO CONTACT-INFO
" Thomas D. Nadeau " Thomas D. Nadeau
Cisco Systems, Inc. Cisco Systems, Inc.
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
Subrahmanya Hegde Subrahmanya Hegde
Email: subrah@cisco.com Email: subrah@cisco.com
General comments should be sent to mpls@uu.net General comments should be sent to mpls@uu.net
" "
DESCRIPTION DESCRIPTION
"This MIB module contains managed object definitions for "This MIB module contains managed object definitions for
MPLS Label Controlled Frame-Relay interfaces as defined MPLS Label Controlled Frame-Relay interfaces as defined
in [RFC3034]. in (RFC3034).
Copyright (C) The Internet Society (2004). This Copyright (C) The Internet Society (2004). This
version of this MIB module is part of RFCXXXX; see version of this MIB module is part of RFCXXXX; see
the RFC itself for full legal notices." the RFC itself for full legal notices."
-- RFC Editor please fill in XXXX -- RFC Editor please fill in XXXX
-- Revision history. -- Revision history.
REVISION REVISION
"200503011200Z" -- 01 March 2005 12:00:00 GMT "200506171200Z" -- 17 June 2005 12:00:00 GMT
DESCRIPTION DESCRIPTION
"Initial draft revision." "Initial draft revision."
::= { mplsStdMIB XXX } -- To Be Assigned by IANA ::= { mplsStdMIB XXX } -- To Be Assigned by IANA
-- Top level components of this MIB module. -- Top level components of this MIB module.
-- Tables, Scalars, Notifications, Conformance -- Tables, Scalars, Notifications, Conformance
mplsLcFrStdNotifications OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 0 } mplsLcFrStdNotifications OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 0 }
mplsLcFrStdObjects OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 1 } mplsLcFrStdObjects OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 1 }
mplsLcFrStdConformance OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 2 } mplsLcFrStdConformance OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 2 }
skipping to change at page 12, line 14 skipping to change at page 12, line 14
thereafter. " thereafter. "
INDEX { mplsInterfaceIndex } INDEX { mplsInterfaceIndex }
::= { mplsLcFrStdInterfaceConfTable 1 } ::= { mplsLcFrStdInterfaceConfTable 1 }
MplsLcFrStdInterfaceConfEntry ::= SEQUENCE { MplsLcFrStdInterfaceConfEntry ::= SEQUENCE {
mplsLcFrStdTrafficMinDlci DLCI, mplsLcFrStdTrafficMinDlci DLCI,
mplsLcFrStdTrafficMaxDlci DLCI, mplsLcFrStdTrafficMaxDlci DLCI,
mplsLcFrStdCtrlMinDlci DLCI, mplsLcFrStdCtrlMinDlci DLCI,
mplsLcFrStdCtrlMaxDlci DLCI, mplsLcFrStdCtrlMaxDlci DLCI,
mplsLcFrStdInterfaceConfRowStatus RowStatus, mplsLcFrStdInterfaceConfRowStatus RowStatus,
mplsLcFrStdInterfaceConfStoreType StorageType mplsLcFrStdInterfaceConfStorageType StorageType
} }
mplsLcFrStdTrafficMinDlci OBJECT-TYPE mplsLcFrStdTrafficMinDlci OBJECT-TYPE
SYNTAX DLCI SYNTAX DLCI
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the minimum DLCI value over which this "This is the minimum DLCI value over which this
LSR is willing to accept traffic on this LSR is willing to accept traffic on this
interface." interface."
skipping to change at page 13, line 25 skipping to change at page 13, line 25
mplsInterfaceConfEntry MUST exist before hand. If an entry mplsInterfaceConfEntry MUST exist before hand. If an entry
is attempted to be created by a manager for a corresponding is attempted to be created by a manager for a corresponding
mplsInterfaceConfEntry that does not support LC-FR, mplsInterfaceConfEntry that does not support LC-FR,
the agent MUST return an inconsistentValue error. the agent MUST return an inconsistentValue error.
If this table is implemented read-only, then the If this table is implemented read-only, then the
agent must set this object to active(1) when this agent must set this object to active(1) when this
row is made active. If this table is implemented row is made active. If this table is implemented
writable, then an agent MUST not allow modification writable, then an agent MUST not allow modification
to its objects once this value is set to active(1) to its objects once this value is set to active(1)
except mplsLcFrStdInterfaceConfRowStatus and except mplsLcFrStdInterfaceConfRowStatus and
mplsLcFrStdInterfaceConfStoreType." mplsLcFrStdInterfaceConfStorageType."
::= { mplsLcFrStdInterfaceConfEntry 5 } ::= { mplsLcFrStdInterfaceConfEntry 5 }
mplsLcFrStdInterfaceConfStoreType OBJECT-TYPE mplsLcFrStdInterfaceConfStorageType OBJECT-TYPE
SYNTAX StorageType SYNTAX StorageType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The storage type for this conceptual row. "The storage type for this conceptual row.
Conceptual rows having the value 'permanent(4)' Conceptual rows having the value 'permanent(4)'
need not allow write-access to any columnar need not allow write-access to any columnar
objects in the row." objects in the row."
DEFVAL { nonVolatile } DEFVAL { nonVolatile }
::= { mplsLcFrStdInterfaceConfEntry 6 } ::= { mplsLcFrStdInterfaceConfEntry 6 }
skipping to change at page 15, line 18 skipping to change at page 15, line 18
OBJECT mplsLcFrStdCtrlMaxDlci OBJECT mplsLcFrStdCtrlMaxDlci
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT mplsLcFrStdInterfaceConfRowStatus OBJECT mplsLcFrStdInterfaceConfRowStatus
SYNTAX RowStatus { active(1) } SYNTAX RowStatus { active(1) }
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION "Write access is not required." DESCRIPTION "Write access is not required."
OBJECT mplsLcFrStdInterfaceConfStoreType OBJECT mplsLcFrStdInterfaceConfStorageType
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
::= { mplsLcFrStdCompliances 2 } ::= { mplsLcFrStdCompliances 2 }
-- Units of conformance. -- Units of conformance.
mplsLcFrStdIfGroup OBJECT-GROUP mplsLcFrStdIfGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mplsLcFrStdTrafficMinDlci, mplsLcFrStdTrafficMinDlci,
mplsLcFrStdTrafficMaxDlci, mplsLcFrStdTrafficMaxDlci,
mplsLcFrStdCtrlMinDlci, mplsLcFrStdCtrlMinDlci,
mplsLcFrStdCtrlMaxDlci, mplsLcFrStdCtrlMaxDlci,
mplsLcFrStdInterfaceConfRowStatus, mplsLcFrStdInterfaceConfRowStatus,
mplsLcFrStdInterfaceConfStoreType mplsLcFrStdInterfaceConfStorageType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for MPLS LC-FR "Collection of objects needed for MPLS LC-FR
interface configuration." interface configuration."
::= { mplsLcFrStdGroups 1 } ::= { mplsLcFrStdGroups 1 }
END END
7. Authors' Addresses 7. Authors' Addresses
skipping to change at page 17, line 5 skipping to change at page 17, line 5
these tables, could result in disruption of traffic on the these tables, could result in disruption of traffic on the
network. This is especially true if traffic has been network. This is especially true if traffic has been
established over these interfaces. The use of stronger established over these interfaces. The use of stronger
mechanisms such as SNMPv3 security should be considered mechanisms such as SNMPv3 security should be considered
where possible. Specifically,SNMPv3 VACM and USM MUST be where possible. Specifically,SNMPv3 VACM and USM MUST be
used with any v3 agent which implements this MIB module. used with any v3 agent which implements this MIB module.
Administrators should consider whether read access to Administrators should consider whether read access to
these objects should be allowed, since read access may be these objects should be allowed, since read access may be
undesirable under certain circumstances. undesirable under certain circumstances.
Some of the readable objects in this MIB module "i.e., objects with a Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible" may be considered sensitive or MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. It is thus important to vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
o the MplsLcAtmStdInterfaceConfTable and o the MplsLcAtmStdInterfaceConfTable and
mplsLcFrStdInterfaceConfTable collectively mplsLcFrStdInterfaceConfTable collectively
collectively show the LC-ATM and/or LC-FR interfaces, collectively show the LC-ATM and/or LC-FR interfaces,
their associated configurations and their linkages to other their associated configurations and their linkages to other
MPLS-related configuration and/or performanc statistics. MPLS-related configuration and/or performanc statistics.
Administrators not wishing to reveal this information should Administrators not wishing to reveal this information should
consider these objects sensitive/vulnerable and take consider these objects sensitive/vulnerable and take
precautions so they are not revealed. precautions so they are not revealed.
SNMP versions prior to SNMPv3 did not include adequate security. SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure "for example by using IPSec", Even if the network itself is secure (for example by using IPSec),
even then, there is no control as to who on the secure network is even then, there is no control as to who on the secure network is
allowed to access and GET/SET "read/change/create/delete" the objects allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module. in this MIB module.
It is RECOMMENDED that implementers consider the security features as It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework "see [RFC3410], section 8", provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms "for including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy". authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access instance of this MIB module, is properly configured to give access
to the objects only to those principals "users" that have legitimate to the objects only to those principals (users) that have legitimate
rights to indeed GET or SET "change/create/delete" them. rights to indeed GET or SET (change/create/delete) them.
11. IANA Considerations 11. IANA Considerations
As described in and as requested in the MPLS-TC-STD-MIB As described in and as requested in the MPLS-TC-STD-MIB
[RFC3811], MPLS related standards track MIB modules should be [RFC3811], MPLS related standards track MIB modules should be
rooted under the mplsStdMIB subtree. There are 2 MPLS MIB modules rooted under the mplsStdMIB subtree. There are 2 MPLS MIB modules
contained in this document, each of the following "IANA contained in this document, each of the following "IANA
Considerations" subsections requests IANA for a new assignment under Considerations" subsections requests IANA for a new assignment under
the mplsStdMIB subtree. New assignments can only be made via a the mplsStdMIB subtree. New assignments can only be made via a
Standards Action as specified in [RFC2434]. Standards Action as specified in [RFC2434].
skipping to change at page 19, line 33 skipping to change at page 19, line 33
October 1998. October 1998.
[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.
[RFC3815] J. Cucchiara, et al., "Definitions of [RFC3815] J. Cucchiara, et al., "Definitions of
Managed Objects for the Multiprotocol Label Managed Objects for the Multiprotocol Label
Switching, Label Distribution Protocol Switching, Label Distribution Protocol
(LDP)", <draft-ietf-mpls-ldp-mib-14.txt>, (LDP)", RFC3815, June 2004.
June 2004.
13. Intellectual Property 13. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
 End of changes. 

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