--- 1/draft-ietf-ccamp-gmpls-ted-mib-03.txt 2008-08-05 00:12:23.000000000 +0200 +++ 2/draft-ietf-ccamp-gmpls-ted-mib-04.txt 2008-08-05 00:12:23.000000000 +0200 @@ -1,23 +1,24 @@ INTERNET-DRAFT Masanori Miyazawa Intended status: Standard Truck Tomohiro Otani -Expires: August 31, 2008 Kenji Kumaki +Expires: Jan 31, 2009 KDDI R&D Labs + Thomas Nadeau + BT + Kenji Kumaki KDDI R&D Labs - Thomas D. Nadeau - Cisco Systems, Inc. - February 21, 2008 + July 13, 2008 - Traffic Engineering Database Management Information Base - in support of GMPLS +Traffic Engineering Database Management Information Base in support of + MPLS-TE/GMPLS - Document: draft-ietf-ccamp-gmpls-ted-mib-03.txt + Document: draft-ietf-ccamp-gmpls-ted-mib-04.txt Status of this Memo By submitting this Internet-Draft, each author represents that 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 becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other @@ -30,99 +31,102 @@ The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. Abstract This memo defines the Management Information Base (MIB) objects in order to manage traffic engineering database (TED) information with - extension in support of Multi-Protocol Label Switching (MPLS) as well - as Generalized MPLS (GMPLS) for use with network management protocols. + extension in support of Multi-Protocol Label Switching (MPLS) with + traffic engineering (TE) as well as Generalized MPLS (GMPLS) for use + with network management protocols. Table of Contents - Status of this Memo................................................ 1 - Abstract........................................................... 1 - 1. The Internet-Standard Management Framework...................... 3 - 2. Introduction.................................................... 3 - 3. Overview........................................................ 3 - 3.1 Conventions used in this document.............................. 3 - 3.2 Terminology.................................................... 3 - 3.3 Acronyms....................................................... 3 - 4. Motivations..................................................... 4 - 5. Brief description of MIB Objects................................ 4 - 5.1 tedTable....................................................... 4 - 5.2 teLocalIntIpAddrTable.......................................... 4 - 5.3 teRemoteIntIpAddrTable......................................... 4 - 5.4 teSwCapTable................................................... 5 - 5.5 teSrlgTable.................................................... 5 - 6. TED MIB Definitions in support of GMPLS......................... 5 - 7. Security consideration......................................... 21 - 8. IANA Considerations............................................ 21 - 8.1 IANA Considerations for TED-MIB............................... 21 - 9. References..................................................... 21 - 9.1 Normative References.......................................... 21 - 9.2 Informative References........................................ 22 - 10. Acknowledgment................................................ 23 - 11. Author's Address.............................................. 23 - 12. Intellectual Property Statement............................... 24 - Copyright statement............................................... 24 +Status of this Memo................................................... 1 +Abstract.............................................................. 1 +1. The Internet-Standard Management Framework......................... 3 +2. Introduction....................................................... 3 +3. Overview........................................................... 3 + +3.1 Conventions used in this document................................. 3 +3.2 Terminology....................................................... 3 +3.3 Acronyms.......................................................... 3 +4. Motivations........................................................ 4 +5. Brief description of MIB Objects................................... 4 +5.1 tedTable.......................................................... 4 +5.2 teLocalIntIpAddrTable............................................. 4 +5.3 teRemoteIntIpAddrTable............................................ 4 +5.4 teSwCapTable...................................................... 5 +5.5 teSrlgTable....................................................... 5 +6.Example of the TED MIB module usage + ................................ 5 +7. TED MIB Definitions in support of GMPLS............................ 6 +8. Security consideration............................................ 22 +9. IANA Considerations............................................... 23 +9.1 IANA Considerations for TED-MIB.................................. 23 +10. References....................................................... 23 +10.1 Normative References............................................ 23 +11. Acknowledgment................................................... 25 +12. Author's Address................................................. 25 +13. Intellectual Property Statement.................................. 25 +Copyright Statement.................................................. 26 1. The Internet-Standard Management Framework For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410]. 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 - The OSPF MIB is defined as [RFC1850] being extended by [RFC4750] and - The ISIS MIB as [RFC4444]. On the other side, MPLS/GMPLS based - traffic engineering has so far extended OSPF/ISIS routing protocol - with TE functionality [RFC4202, RFC3630, RFC4205, RFC3784]. To manage - such MPLS/GMPLS networks effectively, routing information associated - with MPLS/GMPLS TE parameters (TED) is preferred for the network - management, however, there is no clear definition of MPLS/GMPLS TE - information in existing MIBs related with OSPF/ISIS. + The OSPF MIB is defined as [RFC4750] and the ISIS MIB as [RFC4444]. + On the other side, MPLS/GMPLS based traffic engineering has so far + extended OSPF/ISIS routing protocol with TE functionality [RFC4202], + [RFC3630], [RFC4205], [RFC3784]. To manage such MPLS-TE/GMPLS + networks effectively, routing information associated with MPLS/GMPLS + TE parameters (TED) is preferred for the network management, however, + there is no clear definition of MPLS/GMPLS TE information in existing + MIBs related with OSPF/ISIS. This memo defines the Management Information Base (MIB) objects for - managing TED in support of MPLS/GMPLS for use with network management - protocols. + managing TED in support of MPLS-TE/GMPLS for use with network + management protocols. This MIB module should be used in conjunction with OSPF/ISIS MIB as - well as other MIBs defined in [RFC3812, RFC3813, RFC4802, RFC4803] - for the management of MPLS/GMPLS based traffic engineering + well as other MIBs defined in [RFC3812], [RFC3813], [RFC4802], + [RFC4803] for the management of MPLS/GMPLS based traffic engineering information. 3. Overview 3.1 Conventions used in this document The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC-2119 [RFC2119]. 3.2 Terminology - Definitions of key terms for MPLS OAM and GMPLS are found in [MPLS- - OAM, RFC3945] and the reader is assumed to be familiar with those + Definitions of key terms for MPLS OAM and GMPLS are found in [RFC4377, + RFC3945] and the reader is assumed to be familiar with those definitions which are not repeated here. 3.3 Acronyms GMPLS: Generalized Multi-Protocol Label Switching LDP: Label Distribution Protocol LSP: Label Switching Path LSR: Label Switching Router MIB: Management Information Base OAM: Operations and Management @@ -134,22 +138,22 @@ LSC: Lambda switch capable FSC: Fiber switch capable TDM: Time Division Multiplexing SRLG: Shared risk link group LSA: Link state advertisement 4. Motivations The existing OSPF, MPLS and GMPLS MIBs do not provide for the management of all of the extensions to the OSPF protocol. To manage - GMPLS TE attributes, MIB objects to indicate such GMPLS TED is - significant. + MPLS/GMPLS TE attributes, MIB objects to indicate such MPLS/GMPLS TED + is significant. 5. Brief description of MIB Objects The objects described in this section support the management of TED described in [RFC4202], [RFC4203] and [RFC4205] for GMPLS extensions as well as in [RFC3630] and [RFC3784] for MPLS/GMPLS. 5.1 tedTable The tedTable is basically used to indicate TED information of OSPF-TE @@ -177,66 +181,143 @@ The teSwCapTable represents Interface Switching Capability Descriptor information. This is independently defined due to the possibility of multiple appearances of the sub TLV within the same Link-TLV. 5.5 teSrlgTable The teSrlgTable contains the Sub-TLV information of Shared Risk Link Group (SRLG) information. This is separately defined, because more than one sub TLVs may appear in the same Link-TLV. -6. TED MIB Definitions in support of GMPLS +6.Example of the TED MIB module usage + + In this section, we provide an example of the TED MIB module usage. + The following indicates the information of a numbered TE link + originated in a GMPLS controlled node. When TE link information is + retrieved in a MPLS network, GMPLS specific objects such as + teLocalIntAddrTable, teRemoteIntAddrTable, teSwCapTable and + teSrlgTable are not supported. + + Note that the TE MIB modules are only limited to "read-only" access + except for tedNotificationEnabled and tedNotificationMaxRate. The TED + MIB is designed to be independent of OSPF or ISIS MIBs, however each + TE information is belonging to a node or a link, which is managed by + the routing protocol. Therefore it should not be locally changed + without triggering from the routing protocol. + + In tedTable: + { + teAreaId.0.842150510.167772640 0 + teRouterId.0.842150510.16777264 1848783410 + teLinkStateId.0.842150510.16777264 805306369 + teLinkInformationSource.0.842150510.16777264 ospf(2) + teLinkInformationData.0.842150510.16777264 zeroDotZero + teLinkType.0.842150510.16777264 pointToPoint(1) + teRouterIdAddr.0.842150510.16777264 50.50.50.110 + teRouterIdAddr.0.842150530.16777296 50.50.50.130 + teLinkIdAddr.0.842150510.16777264 50.50.50.120 + teMetric.0.842150510.167772641 + teMaxBandwidth.0.842150510.16777264 1376193201 + teMaxReservableBandwidth.0.842150510.167772641376193201 + teUnreservedBandwidthPri0.0.842150510.16777264 1375888025 + teUnreservedBandwidthPri1.0.842150510.16777264 1375888025 + teUnreservedBandwidthPri2.0.842150510.16777264 1375888025 + teUnreservedBandwidthPri3.0.842150510.16777264 1375888025 + teUnreservedBandwidthPri4.0.842150510.16777264 1375888025 + teUnreservedBandwidthPri5.0.842150510.16777264 1375888025 + teUnreservedBandwidthPri6.0.842150510.16777264 1375888025 + teUnreservedBandwidthPri7.0.842150510.16777264 1375888025 + teAdministrativeGroup.0.842150510.16777264 0 + teLocalId.0.842150510.16777264 0 + teRemoteId.0.842150510.16777264 0 + teLinkProtectionType.0.842150510.16777264 01 00 00 00 7 + + In teLocalIntAddrTable: + { + teLocalIntAddr.0.842150510.16777264.010.10.10.1 + } + + In teRemoteIntAddrTable: + { + teRemoteIntAddr.0.842150510.16777264.0 10.10.10.2 + } + + In teSwCapTable: + { + teSwitchingType.0.842150510.16777264.1 lsc(150) + teEncoding.0.842150510.16777264.1 ethernet(2) + teMaxLspBandwidthPri0.0.842150510.16777264.1 1375888025 + teMaxLspBandwidthPri1.0.842150510.16777264.1 1375888025 + teMaxLspBandwidthPri2.0.842150510.16777264.1 1375888025 + teMaxLspBandwidthPri3.0.842150510.16777264.1 1375888025 + teMaxLspBandwidthPri4.0.842150510.16777264.1 1375888025 + teMaxLspBandwidthPri5.0.842150510.16777264.1 1375888025 + teMaxLspBandwidthPri6.0.842150510.16777264.1 1375888025 + teMaxLspBandwidthPri7.0.842150510.16777264.1 1375888025s + teMinLspBandwidth.0.842150510.16777264.1 0 + teIntMtu.0.842150510.16777264.1 0 + teIndication.0.842150510.16777264.1 standard(0) + } + + In teSrlgTable: + { + teSrlg.0.842150510.16777264.00 + } + +7. TED MIB Definitions in support of GMPLS TED-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, Unsigned32, transmission, IpAddress, NOTIFICATION-TYPE - FROM SNMPv2-SMI --[RFC2578] + FROM SNMPv2-SMI -- RFC2578 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP - FROM SNMPv2-CONF --[RFC2580] + FROM SNMPv2-CONF -- RFC2580 RowPointer, TruthValue - FROM SNMPv2-TC --[RFC2579] + FROM SNMPv2-TC -- RFC2579 + IANAGmplsLSPEncodingTypeTC, IANAGmplsSwitchingTypeTC + FROM IANA-GMPLS-TC-MIB -- RFC4801 ; tedMIB MODULE-IDENTITY - LAST-UPDATED "200707060000Z" -- 06 July 2005 00:00:00 GMT + LAST-UPDATED "200807030000Z" -- 03 July 2008 00:00:00 GMT ORGANIZATION "IETF CCAMP Working Group." CONTACT-INFO " Tomohiro Otani otani@kddilabs.jp Masanori Miyazawa ma-miyazawa@kddilabs.jp Thomas D. Nadeau - tnadeau@cisco.com + tnadeau@bt.com Kenji Kumaki ke-kumaki@kddilabs.jp Comments and discussion to ccamp@ietf.org" DESCRIPTION "This MIB contains managed object definitions for TED in - support of MPLS/GMPLS Traffic Engienering (TE) Database. + support of MPLS/GMPLS TE Database. - Copyright (C) The Internet Society (2008). This version of - this MIB module is part of RFCXXX; see the RFC itself for - full legal notices." + Copyright (C) The IETF Trust (2008). This version of this + MIB module is part of RFCXXX; see the RFC itself for full + legal notices." -- Revision history. REVISION - "200506041200Z" -- 04 July 2005 12:00:00 GMT + "200807030000Z" -- 04 July 2008 00:00:00 GMT DESCRIPTION "Initial version. Published as RFC xxxx." -- RFC-editor pls fill in xxx ::= { transmission xxx } - -- assigned by IANA, see section 7.1 for details + -- assigned by IANA, see section 8.1 for details -- Textual Conventions. -- Top level components of this MIB. tedNotifications OBJECT IDENTIFIER ::= { tedMIB 0 } tedObjects OBJECT IDENTIFIER ::= { tedMIB 1 } tedScalars OBJECT IDENTIFIER ::= { tedObjects 1 } tedTables OBJECT IDENTIFIER ::= { tedObjects 2 } tedConformance OBJECT IDENTIFIER ::= { tedMIB 2 } @@ -342,21 +424,21 @@ "This object indicates the router identifier. If OSPF is used to advertise LSA, this represents a Router ID. If ISIS is used, this represents a System ID. Otherwise, this represents zero." ::= { tedEntry 2 } teLinkStateId OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS read-only STATUS current DESCRIPTION - "This object jndicates the link state identifier. If OSPF + "This object indicates the link state identifier. If OSPF is used, this represents an ospfLsdbID. If ISIS is used, this represents an isisLSPID. Otherwise, this represents a unique identifier within a node." ::= { tedEntry 3 } teLinkInformationSource OBJECT-TYPE SYNTAX INTEGER { unknown(0), locallyConfigured(1), ospf(2), @@ -374,34 +456,36 @@ SYNTAX RowPointer MAX-ACCESS read-only STATUS current DESCRIPTION "This object cross-references the source of the information about this TE link and should be interpretted in the context of teLinkInformationSource. If teLinkInformationSource has the value unknown(0), this object SHOULD contain a value of zeroDotZero.If teLinkInformationSource has the value locallyConfigured(1), this - object MAY contain the identifier of the corresponding row entry in - the teLinkTable of TE-LINK-STD-MIB, the identifier of the - corresponding row in a local proprietary TE link MIB module, or the - value of zeroDotZero otherwise. - If teLinkInformationSource has the value ospf(2), this - object MAY contain the identifier of the corresponding row entry in - the ospfLocalLsdbTable of [OSPF-MIB], or the value of zeroDotZero - otherwise. + object MAY contain the identifier of the corresponding row entry + in the teLinkTable of TE-LINK-STD-MIB, the identifier of the + corresponding row in a local proprietary TE link MIB module, or + the value of zeroDotZero otherwise. + If teLinkInformationSource has the value ospf(2), this object + MAY contain the identifier of the corresponding row entry in the + ospfLocalLsdbTable of OSPF-MIB [RFC4750], or the value of + zeroDotZero otherwise. If teLinkInformationSource has the value isis(3) this object MAY contain the identifier of the corresponding row entry in the - isisAreaAddr of [ISIS-MIB], or the value of zeroDotZero otherwise. - If teLinkInformationSource has the value other(4) this - object MAY contain the identifier of the corresponding row entry a - local proprietary MIB module, or the value of zeroDotZero otherwise." + isisAreaAddr of ISIS-MIB [RFC4444], or the value of zeroDotZero + otherwise. + If teLinkInformationSource has the value other(4) this object + MAY contain the identifier of the corresponding row entry a + local proprietary MIB module, or the value of zeroDotZero + otherwise." ::= { tedEntry 5 } teLinkType OBJECT-TYPE SYNTAX INTEGER { pointToPoint (1), multiAccess (2) } MAX-ACCESS read-only STATUS current DESCRIPTION @@ -688,80 +771,64 @@ DESCRIPTION "This entry relates each TE link with its GMPLS TE switching capability information. IF the MIB deals with only OSPF-TE information, the value of each object related with GMPLS TE extensions should be null." INDEX { teAreaId, teRouterId, teLinkStateId, teSwCapIndex } ::= { teSwCapTable 1 } TeSwCapEntry ::= SEQUENCE { teSwCapIndex Unsigned32, - teSwitchingType INTEGER, - teEncoding INTEGER, + teSwitchingType IANAGmplsSwitchingTypeTC, + teEncoding IANAGmplsLSPEncodingTypeTC, teMaxLspBandwidthPri0 Unsigned32, teMaxLspBandwidthPri1 Unsigned32, teMaxLspBandwidthPri2 Unsigned32, teMaxLspBandwidthPri3 Unsigned32, teMaxLspBandwidthPri4 Unsigned32, teMaxLspBandwidthPri5 Unsigned32, teMaxLspBandwidthPri6 Unsigned32, teMaxLspBandwidthPri7 Unsigned32, teMinLspBandwidth Unsigned32, teIntMtu Integer32, teIndication INTEGER } teSwCapIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "This index is utilized to identify multiple switching - functions on a local or remote TE link." + functions on a local or remote TE link according to definitions of + textual conventions of GMPLS [RFC4801]." ::= { teSwCapEntry 1 } teSwitchingType OBJECT-TYPE - SYNTAX INTEGER { - unknown (0), - psc1 (1), - psc2 (2), - psc3 (3), - psc4 (4), - l2sc (51), - tdm (100), - lsc (150), - fsc (200) - } + SYNTAX IANAGmplsSwitchingTypeTC MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the GMPLS switching capability - assigned to the TE link." + assigned to the TE link according to definitions of textual + conventions of GMPLS [RFC4801]. " ::= { teSwCapEntry 2 } teEncoding OBJECT-TYPE - SYNTAX INTEGER { - packet (1), - ethernet (2), - ansiEtsiPdh (3), - sdhSonet (5), - digitalWrapper (7), - lambda (8), - fiber (9), - fiberChannel (11) - } + SYNTAX IANAGmplsLSPEncodingTypeTC MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the GMPLS encoding type assigned to the TE link." ::= { teSwCapEntry 3 } + teMaxLspBandwidthPri0 OBJECT-TYPE SYNTAX Unsigned32 (0..4294967295) UNITS "Byte per seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the maximum bandwidth of the TE link at the priority 0 for GMPLS LSP creation." ::= { teSwCapEntry 4 } @@ -957,30 +1023,30 @@ teModuleFullCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "Compliance statement for agents provides full support for the TED MIB" MODULE -- this module MANDATORY-GROUPS { tedMainGroup } ::= { tedCompliances 1 } - -- -- ReadOnly Compliance -- + teModuleReadOnlyCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION - "Compliance requirement for implementations only provide - read-only support for TED. Such devices can then be monitored - but cannot be configured using this MIB module. + "Compliance requirement for implementations only provide read-only + support for TED. Such devices can then be monitored but cannot be + configured using this MIB module. " MODULE -- this module MANDATORY-GROUPS { tedMainGroup } ::= { tedCompliances 2 } -- Units of conformance. tedMainGroup OBJECT-GROUP OBJECTS { @@ -1038,154 +1104,188 @@ tedTeDeletion } STATUS current DESCRIPTION "This indicates a set of notifications implemented in this module" ::= { tedGroups 2 } END -7. Security consideration +8. Security consideration - This document introduces no new security issues beyond those detailed - in the OSPF MIB. + There are no management objects defined in this MIB module that have + a MAX-ACCESS clause of read-write and/or read-create. So, if this MIB + module is implemented correctly, then there is no risk that an + intruder can alter or create any management objects of this MIB + module via direct SNMP SET operations. -8. IANA Considerations + 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: + + - teTEDtable, teLocalIntAddrTable, teRemoteIntAddrTable, + teSWcaptable and teSrlgtable contain topology information for the + MPLS/GMPLS network. If an administrator does not want to reveal this + information, then these tables should be considered + sensitive/vulnerable. + + 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 principles (users) that have legitimate + rights to indeed GET or SET (change/create/delete) them. + +9. IANA Considerations The following "IANA Considerations" subsection requests IANA for a new assignment under the transmission subtree. New assignments can - only be made via a Standards Action as specified in [RFC2434]. + only be made via a Standards Action as specified in [RFC5226]. -8.1 IANA Considerations for TED-MIB +9.1 IANA Considerations for TED-MIB The IANA is requested to assign { transmission XXX } to the TED-MIB module specified in this document. -9. References +10. References -9.1 Normative References +10.1 Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. [RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, - "Structure of Management Information Version 2 - (SMIv2)", STD 58, RFC 2578, April 1999. + "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. + "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. -9.2 Informative References - - [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. - - [RFC1850] F. Baker, et al, "OSPF Version 2 Management - Information Base", RFC1850, Nov. 1995. + [RFC4801] T. Nadeau and A. Farrel, Ed., "Definitions of Textual + Conventions for Generalized Multiprotocol Label Switching + (GMPLS) Management", RFC4801, Feb. 2007. - [RFC4750] Dan Joyal, et al, "OSPF Version 2 Management - Information Base", RFC4750, December 2006. +10.2 Informative References + [RFC4750] Dan Joyal, et al, "OSPF Version 2 Management Information + Base", RFC4750, December 2006. [RFC4444] J. Parker, et al, "Management Information Base for - Intermediate System to Intermediate System (IS-IS)", - RFC 4444, April 2006. + Intermediate System to Intermediate System (IS-IS)", RFC + 4444, April 2006. [RFC4202] K. Kompella, and Y. Rekhter, "Routing Extensions in - Support of Generalized Multi-Protocol Label - Switching", RFC4202, Oct. 2005. + Support of Generalized Multi-Protocol Label Switching", + RFC4202, Oct. 2005. - [RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions - to OSPF Version2", RFC3630, September 2003. + [RFC3630] D. Katz, et al, "Traffic Engineering (TE) Extensions to + OSPF Version2", RFC3630, September 2003. [RFC4205] K. Kompella, and Y. Rekhter, "Intermediate System to Intermediate System (IS-IS) Extensions in Support of Multi-Protocol Label Switching (GMPLS)", RFC4205, Oct. 2005. [RFC3784] H. Smit and T. Li, "IS-IS extensions for Traffic - Engineering”, RFC 3784, June 2004. + Engineering", RFC 3784, June 2004. [RFC3812] Srinivasan, C., Viswanathan, A., and T. Nadeau, - "Multiprotocol Label Switching (MPLS) Traffic - Engineering (TE) Management Information Base (MIB)", - RFC 3812, June 2004. + "Multiprotocol Label Switching (MPLS) Traffic Engineering + (TE) Management Information Base (MIB)", RFC 3812, June + 2004. [RFC3813] Srinivasan, C., Viswanathan, A., and T. Nadeau, "Multiprotocol Label Switching (MPLS) Label Switching - (LSR) Router Management Information Base (MIB)", RFC - 3813, June 2004. + (LSR) Router Management Information Base (MIB)", RFC 3813, + June 2004. [RFC4802] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol - Label Switching (GMPLS) Traffic Engineering - Management Information Base", RFC4802, Feb., 2007. + Label Switching (GMPLS) Traffic Engineering Management + Information Base", RFC4802, Feb., 2007. [RFC4803] T. D. Nadeu and A. Farrel, "Generalized Multiprotocol Label Switching (GMPLS) Label Switching Router (LSR) Management Information Base", RFC4803, Feb., 2007. - [MPLS OAM] T. Nadeau, Allan D., et al., "OAM Requirements for - MPLS Network" draft-ietf-mpls-oam-requirements-05.txt, - June 2005. + [RFC4377] T. Nadeau, Allan D., et al., "OAM Requirements for MPLS + Network", RFC4377, Feb., 2006. - [RFC3945] E. Mannie, "Generalized Multi-Protocol Label - Switching Architecture", RFC3945, October, 2004. + [RFC3945] E. Mannie, "Generalized Multi-Protocol Label Switching + Architecture", RFC3945, October, 2004. - [RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in - Support of Generalized Multi-Protocol Label - Switching", RFC4203, Oct. 2005. + [RFC4203] K. Kompella, and Y. Rekhter, "OSPF Extensions in Support + of Generalized Multi-Protocol Label Switching", RFC4203, + Oct. 2005. - [RFC3630] Katz, D., et al, "Traffic Engineering (TE) Extensions - to OSPF Version 2", RFC3630, September 2003. + [RFC3630] Katz, D., et al, "Traffic Engineering (TE) Extensions to + OSPF Version 2", RFC3630, September 2003. - [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for - Writing an IANA Considerations Section in RFCs" BCP - 26, RFC 2434, October 1998. + [RFC5226] Narten, T. and H. Alvestrand., " Guidelines for Writing an + IANA Considerations Section in RFCs" BCP 26, RFC 5226, May + 2008. -10. Acknowledgment + [RFC3410] J. Case, R. Mundy, D. pertain, B.Stewart, "Introduction + and Applicability Statement for Internet Standard + Management Framework", RFC 3410, December 2002. + +11. Acknowledgment The authors wish to acknowledge and thank the following individuals for their valuable comments to this document: Ken Nagami, Shuichi Okamoto, Adrian Farrel and Diego Caviglia. -11. Author's Address +12. Author's Address Tomohiro Otani KDDI R&D Laboratories, Inc. 2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan Phone: +81-49-278-7357 Email: otani@kddilabs.jp Masanori Miyazawa KDDI R&D Laboratories, Inc. 2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan. Phone: +81-49-278-7559 Email: ma-miyazawa@kddilabs.jp Thomas D. Nadeau - Cisco Systems, Inc. - 300 Beaver Brook Road, Boxboro, MA 01719 - Phone: +1-978-936-1470 - Email: tnadeau@cisco.com + BT + Email: tom.nadeau@bt.com Kenji Kumaki KDDI R&D Laboratories, Inc. 2-1-15 Ohara Fujimino, Saitama, 356-8502. Japan Phone: +81-49-278-7863 Email: ke-kumaki@kddilabs.jp -12. Intellectual Property Statement +13. Intellectual Property Statement 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. @@ -1193,21 +1293,21 @@ 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. -Copyright statement +Copyright Statement Copyright (C) The IETF Trust (2008). 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, THE IETF TRUST AND