MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT teLinkDescrMaxLspBandwidthPrio7
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT teLinkDescrRowStatus
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 teLinkDescrStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- teLinkSrlgTable
OBJECT teLinkSrlgRowStatus
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 teLinkSrlgStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- teLinkBandwidthTable
OBJECT teLinkBandwidthRowStatus
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 teLinkBandwidthStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- componentLinkTable
OBJECT componentLinkMaxResBandwidth
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkPreferredProtection
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkRowStatus
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 componentLinkStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- componentLinkDescriptorTable
OBJECT componentLinkDescrSwitchingCapability
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrEncodingType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMinLspBandwidth
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMaxLspBandwidthPrio0
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMaxLspBandwidthPrio1
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMaxLspBandwidthPrio2
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMaxLspBandwidthPrio3
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMaxLspBandwidthPrio4
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMaxLspBandwidthPrio5
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMaxLspBandwidthPrio6
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrMaxLspBandwidthPrio7
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrInterfaceMtu
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrIndication
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
OBJECT componentLinkDescrRowStatus
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 componentLinkDescrStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
-- componentLinkBandwidthTable
OBJECT componentLinkBandwidthRowStatus
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 componentLinkBandwidthStorageType
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required."
::= { teLinkCompliances 2 }
-- Units of conformance
teLinkGroup OBJECT-GROUP
OBJECTS { teLinkAddressType,
teLinkLocalIpAddr,
teLinkRemoteIpAddr,
teLinkMetric,
teLinkProtectionType,
teLinkWorkingPriority,
teLinkResourceClass,
teLinkIncomingIfId,
teLinkOutgoingIfId,
teLinkRowStatus,
teLinkStorageType,
teLinkDescrSwitchingCapability,
teLinkDescrEncodingType,
teLinkDescrRowStatus,
teLinkDescrStorageType,
componentLinkPreferredProtection,
componentLinkCurrentProtection,
componentLinkRowStatus,
componentLinkStorageType,
componentLinkDescrSwitchingCapability,
componentLinkDescrEncodingType,
componentLinkDescrRowStatus,
componentLinkDescrStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for the management of
resources associated with TE links."
::= { teLinkGroups 1 }
teLinkSrlgGroup OBJECT-GROUP
OBJECTS { teLinkSrlgRowStatus,
teLinkSrlgStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for the management of
SRLG resources associated with TE links."
::= { teLinkGroups 2 }
teLinkBandwidthGroup OBJECT-GROUP
OBJECTS { teLinkMaximumReservableBandwidth,
teLinkDescrMaxLspBandwidthPrio0,
teLinkDescrMaxLspBandwidthPrio1,
teLinkDescrMaxLspBandwidthPrio2,
teLinkDescrMaxLspBandwidthPrio3,
teLinkDescrMaxLspBandwidthPrio4,
teLinkDescrMaxLspBandwidthPrio5,
teLinkDescrMaxLspBandwidthPrio6,
teLinkDescrMaxLspBandwidthPrio7,
teLinkBandwidthUnreserved,
teLinkBandwidthRowStatus,
teLinkBandwidthStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for the management of
the bandwidth resources associated with TE links and
component links."
::= { teLinkGroups 3 }
componentLinkBandwidthGroup OBJECT-GROUP
OBJECTS { componentLinkMaxResBandwidth,
componentLinkDescrMaxLspBandwidthPrio0,
componentLinkDescrMaxLspBandwidthPrio1,
componentLinkDescrMaxLspBandwidthPrio2,
componentLinkDescrMaxLspBandwidthPrio3,
componentLinkDescrMaxLspBandwidthPrio4,
componentLinkDescrMaxLspBandwidthPrio5,
componentLinkDescrMaxLspBandwidthPrio6,
componentLinkDescrMaxLspBandwidthPrio7,
componentLinkBandwidthUnreserved,
componentLinkBandwidthRowStatus,
componentLinkBandwidthStorageType
}
STATUS current
DESCRIPTION
"Collection of objects needed for the management of the
bandwidth parameters associated with component links."
::= { teLinkGroups 4 }
teLinkPscGroup OBJECT-GROUP
OBJECTS { teLinkDescrMinLspBandwidth,
teLinkDescrInterfaceMtu,
componentLinkDescrMinLspBandwidth,
componentLinkDescrInterfaceMtu
}
STATUS current
DESCRIPTION
"Collection of objects needed for devices that are
packet switch capable."
::= { teLinkGroups 5 }
teLinkTdmGroup OBJECT-GROUP
OBJECTS { teLinkDescrMinLspBandwidth,
teLinkDescrIndication,
componentLinkDescrMinLspBandwidth,
componentLinkDescrIndication
}
STATUS current
DESCRIPTION
"Collection of objects needed for devices that are
TDM switching capable."
::= { teLinkGroups 6 }
-- End of TE-LINK-STD-MIB
END
10. Security Considerations
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
objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their
sensitivity/vulnerability:
- All the tables in this MIB module have routing information in
them, so they all have the same security attributes. Unauthorized
changes to attributes of these tables can disrupt resource
allocation in the network.
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
vulnerable in some network environments. It is thus important to
control even GET and/or NOTIFY access to these objects and possibly
to even encrypt the values of these objects when sending them over
the network via SNMP. These are the tables and objects and their
sensitivity/vulnerability:
- IP address entries in the teLinkTable (teLinkLocalIpAddr and
teLinkRemoteIpAddr) may reveal the internals of a network provider
IP address space.
SNMP versions prior to SNMPv3 did not include adequate security.
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
allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is RECOMMENDED that implementers consider the security features as
provided by the SNMPv3 framework (see [RFC3410], section 8),
including full support for the SNMPv3 cryptographic mechanisms (for
authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
11. Contributors
Sudheer Dharanikota
EMail: sudheer@ieee.org
12. Acknowledgements
The authors would like to acknowledge the contribution of Dmitry
Ryumkin.
13. IANA Considerations
The following "IANA Considerations" subsection requests IANA for a
new assignment. New assignments can only be made via Standards
Action as specified in [RFC2434].
13.1. IANA Considerations for the TE-LINK-STD-MIB
The TE-LINK-STD-MIB should be rooted under the transmission subtree.
The IANA has assigned { transmission 200 } to the TE-LINK-STD-MIB
module specified in this document.
14. References
14.1. Normative References
[IANAifType] "IANAifType MIB Module",
http://www.iana.org/assignments/ianaiftype-mib.
[IEEE] IEEE, "IEEE Standard for Binary Floating-Point
Arithmetic", Standard 754-1985, 1985 (ISBN 1-5593-7653-
8).
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434,
October 1998.
[RFC2578] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Structure of Management Information Version 2 (SMIv2)",
STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Textual Conventions for SMIv2", STD 58, RFC 2579, April
1999.
[RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580,
April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000.
[RFC3471] Berger, L., "Generalized Multi-Protocol Label Switching
(GMPLS) Signaling Functional Description", RFC 3471,
January 2003.
[RFC3630] Katz, D., Kompella, K. and D. Yeung, "Traffic
Engineering (TE) Extensions to OSPF Version 2", RFC
3630, September 2003.
[RFC4201] Kompella, K., Rekhter, Y. and L. Berger, "Link Bundling
in MPLS Traffic Engineering (TE)", RFC 4201, October
2005.
[RFC4202] Kompella, K., Ed. and Y. Rekhter, Ed., "Routing
Extensions in Support of Generalized Multi-Protocol
Label Switching (GMPLS)", RFC 4202, October 2005.
[RFC4203] Kompella, K., Ed. and Y. Rekhter, Ed., "OSPF Extensions
in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 4203, October 2005.
[RFC4206] Kompella, K. and Y. Rekhter, "Label Switched Paths (LSP)
Hierarchy with Generalized Multi-Protocol Label
Switching (GMPLS) Traffic Engineering (TE)", RFC 4206,
October 2005.
[RFC4204] Lang, J., Ed., "Link Management Protocol (LMP)", RFC
4204, October 2005.
14.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for
Internet-Standard Management Framework", RFC 3410,
December 2002.
[RFC3945] Mannie, E., "Generalized Multi-Protocol Label Switching
(GMPLS) Architecture", RFC 3945, October 2004.
Authors’ Addresses
Martin Dubuc
EMail: mdubuc@ncf.ca
Thomas D. Nadeau
Cisco Systems
1414 Massachusetts Ave.
Boxborough, MA 01719
Phone: +1-978-244-3051
EMail: tnadeau@cisco.com
Jonathan P. Lang
Sonos, Inc.
223 E. De La Guerra St.
Santa Barbara, CA 93101
EMail: jplang@ieee.org
Full Copyright Statement
Copyright (C) The Internet Society (2005).
This document is subject to the rights, licenses and restrictions
contained in BCP 78, and except as set forth therein, the authors
retain all their rights.
This document and the information contained herein are provided on an
"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Intellectual Property
The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be
found in BCP 78 and BCP 79.
Copies of IPR disclosures made to the IETF Secretariat and any
assurances of licenses to be made available, or the result of an
attempt made to obtain a general license or permission for the use of
such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF at ietf-
ipr@ietf.org.
Acknowledgement
Funding for the RFC Editor function is currently provided by the
Internet Society.