draft-ietf-mpls-telink-mib-05.txt   draft-ietf-mpls-telink-mib-06.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: July 2004 Expires: August 2004
Thomas D. Nadeau Thomas D. Nadeau
Cisco Systems Cisco Systems
Jonathan P. Lang Jonathan P. Lang
Rincon Networks Rincon Networks
January 2004 February 2004
Traffic Engineering Link Management Information Base Traffic Engineering Link Management Information Base
draft-ietf-mpls-telink-mib-05.txt draft-ietf-mpls-telink-mib-06.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 22 skipping to change at page 2, line 22
6.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 4 6.2. teLinkDescriptorTable . . . . . . . . . . . . . . . . . . . . . 4
6.3. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 4 6.3. teLinkSrlgTable . . . . . . . . . . . . . . . . . . . . . . . . 4
6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4 6.4. teLinkBandwidthTable . . . . . . . . . . . . . . . . . . . . . 4
6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 5 6.5. componentLinkTable . . . . . . . . . . . . . . . . . . . . . . 5
6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5 6.6. componentLinkDescriptorTable . . . . . . . . . . . . . . . . . 5
6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5 6.7. componentLinkBandwidthTable . . . . . . . . . . . . . . . . . . 5
7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5 7. Example of Bundled Link Setup . . . . . . . . . . . . . . . . . . 5
8. Application of the Interfaces Group to TE Links . . . . . . . . . 9 8. Application of the Interfaces Group to TE Links . . . . . . . . . 9
8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9 8.1 Support of the TE Link Layer by ifTable . . . . . . . . . . . . 9
8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11 8.2 Using ifStackTable . . . . . . . . . . . . . . . . . . . . . . . 11
8.3 Applicability of ifRcvAddressTable . . . . . . . . . . . . . . . 13
9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13 9. TE Link MIB Module Definitions . . . . . . . . . . . . . . . . . 13
10. Intellectual Property Considerations . . . . . . . . . . . . . . 50 10. Intellectual Property Considerations . . . . . . . . . . . . . . 50
11. Security Considerations . . . . . . . . . . . . . . . . . . . . 50 11. Security Considerations . . . . . . . . . . . . . . . . . . . . 51
12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 51 12. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 52
13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 13. References . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 52 13.1 Normative References . . . . . . . . . . . . . . . . . . . . . 53
13.2 Informative References . . . . . . . . . . . . . . . . . . . . 53 13.2 Informative References . . . . . . . . . . . . . . . . . . . . 53
14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 53 14. Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 54
15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 54 15. Full Copyright Statement . . . . . . . . . . . . . . . . . . . . 54
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
skipping to change at page 3, line 44 skipping to change at page 3, line 45
traffic of a group of one or more TE links. There should be more than traffic of a group of one or more TE links. There should be more than
one TE Link in a link bundle, but this is not a requirement. one TE Link in a link bundle, but this is not a requirement.
Furthermore, if there are more than one TE link in a link bundle at Furthermore, if there are more than one TE link in a link bundle at
some time, and at some point later, all but one of the links are some time, and at some point later, all but one of the links are
deleted, the agent may choose to either delete the link bundle, or it deleted, the agent may choose to either delete the link bundle, or it
may choose to leave it intact. Traffic counters on a link bundle are may choose to leave it intact. Traffic counters on a link bundle are
cumulative for all subinterfaces which it binds together. cumulative for all subinterfaces which it binds together.
4. Feature Checklist 4. Feature Checklist
The TE Link MIB module (TE-LINK-MIB) is designed to satisfy the The TE Link MIB module (TE-LINK-STD-MIB) is designed to satisfy the
following requirements and constraints: following requirements and constraints:
- The MIB module supports the management of TE links, including - The MIB module supports the management of TE links, including
bundled links. bundled links.
- Support is provided for configuration of traffic engineering - Support is provided for configuration of traffic engineering
parameters associated with TE links. parameters associated with TE links.
- The MIB module is used to monitor the priority-based component - The MIB module is used to monitor the priority-based component
link and TE link bandwidth values. link and TE link bandwidth values.
skipping to change at page 13, line 5 skipping to change at page 13, line 5
various interfaces. various interfaces.
ifStackTable Entries ifStackTable Entries
HigherLayer LowerLayer HigherLayer LowerLayer
0 1 0 1
1 2 1 2
2 3 2 3
3 0 3 0
8.3. Applicability of ifRcvAddressTable
TE link interfaces are logical interfaces with no media-level
addresses. As such, the ifRcvAddressTable is not applicable
to these interfaces.
9. TE Link MIB Module Definitions 9. TE Link MIB Module Definitions
TE-LINK-STD-MIB DEFINITIONS ::= BEGIN TE-LINK-STD-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, transmission, Integer32, Unsigned32 MODULE-IDENTITY, OBJECT-TYPE, transmission, Integer32, Unsigned32
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
skipping to change at page 13, line 26 skipping to change at page 13, line 32
TEXTUAL-CONVENTION, RowStatus, StorageType TEXTUAL-CONVENTION, RowStatus, StorageType
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;
teLinkStdMIB MODULE-IDENTITY teLinkStdMIB MODULE-IDENTITY
LAST-UPDATED "200401101200Z" -- 10 January 2004 12:00:00 EST LAST-UPDATED "200402011200Z" -- 1 February 2004 12:00:00 EST
ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" ORGANIZATION "Multiprotocol Label Switching (MPLS) 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
Email: tnadeau@cisco.com Email: tnadeau@cisco.com
skipping to change at page 14, line 4 skipping to change at page 14, line 10
the MPLS working group mailing list at mpls@uu.net." the MPLS working group mailing list at mpls@uu.net."
DESCRIPTION DESCRIPTION
"Copyright (C) 2004 The Internet Society. This version of "Copyright (C) 2004 The Internet Society. This version of
this MIB module is part of RFC XXXX; see the RFC this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices. itself for full legal notices.
This MIB module contains managed object definitions for This MIB module contains managed object definitions for
MPLS traffic engineering links as defined in MPLS traffic engineering links as defined in
'Link Bundling in MPLS Traffic Engineering'." 'Link Bundling in MPLS Traffic Engineering'."
-- Revision history. -- Revision history.
REVISION REVISION
"200401101200Z" -- 10 January 2004 12:00:00 EST "200402011200Z" -- 1 February 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 200 which is -- Request to assign 200 which is
-- ifType value for teLink. -- ifType value for teLink.
-- Textual Conventions -- Textual Conventions
TeLinkBandwidth ::= TEXTUAL-CONVENTION TeLinkBandwidth ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to represent link bandwidth in bps. This "This type is used to represent link bandwidth in bps. This
value is represented using a 32 bit IEEE floating point value is represented using a 4 octet IEEE floating point
format." format."
REFERENCE REFERENCE
"IEEE Standard for Binary Floating-Point Arithmetic, "IEEE Standard for Binary Floating-Point Arithmetic,
Standard 754-1985" Standard 754-1985"
SYNTAX Unsigned32 SYNTAX OCTET STRING (SIZE(4))
TeLinkPriority ::= TEXTUAL-CONVENTION TeLinkPriority ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d" DISPLAY-HINT "d"
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This type is used to represent a priority. Each connection is "This type is used to represent a priority. Each connection is
assigned a priority. This priority is used when accounting for assigned a priority. This priority is used when accounting for
bandwidth on TE links or component links, for resource bandwidth on TE links or component links, for resource
allocation and for rerouting purposes. Value 0 is the highest allocation and for rerouting purposes. Value 0 is the highest
priority. Value 7 is the lowest priority." priority. Value 7 is the lowest priority."
skipping to change at page 15, line 39 skipping to change at page 15, line 45
digitalWrapper(7), digitalWrapper(7),
lambda(8), lambda(8),
fiber(9), fiber(9),
fiberChannel(11) fiberChannel(11)
} }
TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION TeLinkSonetSdhIndication ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention is used to indicate whether the interface "This convention is used to indicate whether the interface
supports Standard or Arbitrary SONET/SDH. The values used supports Standard or Arbitrary SONET/SDH. To simplify the
in this textual convention are as specified in the mapping process, the values used in this textual convention
interface switching capability specific information field." match the values specified in the interface switching
capability specific information field, i.e. 0 for Standard
SONET/SDH and 1 for Arbitrary SONET/SDH."
REFERENCE REFERENCE
"OSPF Extensions in Support of Generalized MPLS, RFC xxxx" "OSPF Extensions in Support of Generalized MPLS, RFC xxxx"
-- RFC Editor to fill in RFC number that will be assigned to -- RFC Editor to fill in RFC number that will be assigned to
-- [GMPLS-OSPF] -- [GMPLS-OSPF]
SYNTAX INTEGER { SYNTAX INTEGER {
standard(0), standard(0),
arbitrary(1) arbitrary(1)
} }
-- Top level components of this MIB module -- Top level components of this MIB module
skipping to change at page 50, line 14 skipping to change at page 50, line 22
componentLinkDescrMinLspBandwidth, componentLinkDescrMinLspBandwidth,
componentLinkDescrIndication componentLinkDescrIndication
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Collection of objects needed for devices that are "Collection of objects needed for devices that are
TDM switching capable." TDM switching capable."
::= { teLinkGroups 6 } ::= { teLinkGroups 6 }
-- End of TE-LINK-STD-MIB
END END
10. Intellectual Property Considerations 10. Intellectual Property Considerations
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 or other rights that might be claimed to intellectual property 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; neither does it represent that it might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the has made any effort to identify any such rights. Information on the
skipping to change at page 53, line 6 skipping to change at page 53, line 19
[HIERARCHY] Kompella, K., Rekhter, Y., "LSP Hierarchy with [HIERARCHY] Kompella, K., Rekhter, Y., "LSP Hierarchy with
Generalized MPLS TE", Internet Draft Generalized MPLS TE", Internet Draft
<draft-ietf-mpls-lsp-hierarchy-08.txt>, <draft-ietf-mpls-lsp-hierarchy-08.txt>,
September 2002. September 2002.
[IANAifType] "IANAifType MIB Module", [IANAifType] "IANAifType MIB Module",
http://www.iana.org/assignments/ianaiftype-mib. http://www.iana.org/assignments/ianaiftype-mib.
[LMP] Lang, J., Mitra, K., Drake, J., Kompella, K., [LMP] Lang, J., Mitra, K., Drake, J., Kompella, K.,
Rekhter, Y., Berger, L., Rajagopalan, B., Rekhter, Y., Berger, L., Saha, D.,
Basak, D., Sandick, H., Zinin, A., Basak, D., Sandick, H., Zinin, A.,
Rajagopalan, B., and Ramamoorthi, S., Rajagopalan, B., and Ramamoorthi, S.,
"Link Management Protocol", "Link Management Protocol",
Internet Draft <draft-ietf-ccamp-lmp-10.txt>, Internet Draft <draft-ietf-ccamp-lmp-10.txt>,
October 2003. October 2003.
[OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic [OSPF] Katz, D., Yeung, D., and Kompella, K., "Traffic
Engineering Extensions to OSPF", Internet Draft Engineering Extensions to OSPF", Internet Draft
<draft-katz-yeung-ospf-traffic-10.txt>, June 2003. <draft-katz-yeung-ospf-traffic-10.txt>, June 2003.
skipping to change at page 53, line 28 skipping to change at page 53, line 41
Support of Generalized MPLS", Internet Draft Support of Generalized MPLS", Internet Draft
<draft-ietf-ccamp-gmpls-routing-09.txt>, October 2003. <draft-ietf-ccamp-gmpls-routing-09.txt>, October 2003.
13.2. Informative References 13.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.
[GMPLS-ARCH] Mannie, E., Ashwood-Smith, P., Awduche, D., [GMPLS-ARCH] Ashwood-Smith, P., Awduche, D.,
Banarjee, A., Basak, D., Berger, L., Bernstein, G., Banarjee, A., Basak, D., Berger, L., Bernstein, G.,
Dharanikota, S., Drake, J., Fan, Y., Fedyk, D., Dharanikota, S., Drake, J., Fan, Y., Fedyk, D.,
Grammel, G., Guo, D., Kompella, K., Kullberg, A., Grammel, G., Guo, D., Kompella, K., Kullberg, A.,
Lang, J., Liaw, F., Nadeau, T., Ong, L., Lang, J., Liaw, Mannie, E., F., Nadeau, T., Ong, L.,
Papadimitriou, D., Pendarakis, D., Rajagopalan, B., Papadimitriou, D., Pendarakis, D., Rajagopalan, B.,
Rekhter, Y., Saha, D., Sandick, H., Sharma, V., Rekhter, Y., Saha, D., Sandick, H., Sharma, V.,
Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J., Swallow, G., Tang, Z., Yates, J., Young, G., Yu, J.,
Zinin, A., "Generalized Multi-Protocol Label Switching Zinin, A., "Generalized Multi-Protocol Label Switching
(GMPLS) Architecture", Internet Draft (GMPLS) Architecture", Internet Draft
<draft-ietf-ccamp-gmpls-architecture-07.txt>, <draft-ietf-ccamp-gmpls-architecture-07.txt>,
May 2003. May 2003.
14. Authors' Addresses 14. Authors' Addresses
 End of changes. 

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