idnits 2.17.1 draft-nadeau-mpls-gmpls-te-mib-00.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 5 instances of too long lines in the document, the longest one being 3 characters in excess of 72. ** There are 5 instances of lines with control characters in the document. ** The abstract seems to contain references ([MPLSArch], [GMPLSARCH]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 5 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 508: '...PLS-TE-MIB. Entries in this table MUST...' RFC 2119 keyword, line 514: '...PLS tunnel there MUST be an entry in b...' RFC 2119 keyword, line 769: '... sonet. Encoding MUST adhere to that s...' Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (April 2001) is 8411 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 126, but not defined == Missing Reference: 'MPLSTEMIB' is mentioned on line 212, but not defined == Missing Reference: 'TBD' is mentioned on line 222, but not defined == Unused Reference: 'GMPLSCRLDP' is defined on line 1107, but no explicit reference was found in the text == Unused Reference: 'GMPLSRSVPTE' is defined on line 1115, but no explicit reference was found in the text == Unused Reference: 'LblStk' is defined on line 1134, but no explicit reference was found in the text == Unused Reference: 'LWFRN' is defined on line 1139, but no explicit reference was found in the text == Unused Reference: 'MLDPATM' is defined on line 1143, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 1152, but no explicit reference was found in the text == Unused Reference: 'IFMIB' is defined on line 1230, but no explicit reference was found in the text == Unused Reference: 'INETADDRMIB' is defined on line 1234, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSARCH' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSCRLDP' -- Possible downref: Non-RFC (?) normative reference: ref. 'GMPLSRSVPTE' -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2271 (ref. 'SNMPArch') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. 'SNMPv1Traps') ** Obsolete normative reference: RFC 1902 (ref. 'SMIv2') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. 'SNMPv2TC') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. 'SNMPv2Conf') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. 'SNMPv1') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. 'SNMPv2c') ** Obsolete normative reference: RFC 1906 (ref. 'SNMPv2TM') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. 'SNMPv3MP') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2575 (ref. 'SNMPv3VACM') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) ** Obsolete normative reference: RFC 2233 (ref. 'IFMIB') (Obsoleted by RFC 2863) ** Obsolete normative reference: RFC 2851 (ref. 'INETADDRMIB') (Obsoleted by RFC 3291) Summary: 25 errors (**), 0 flaws (~~), 13 warnings (==), 6 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau 2 Internet Draft Cisco Systems, Inc. 3 Expires: October 2001 4 Adrian Farrel 5 Movaz Networks, Inc. 7 Tim Hall 8 Edward Harrison 9 Data Connection Ltd. 11 Cheenu Srinivasan 12 Alphion 14 Arun Viswanathan 15 Force10 Networks, Inc. 17 April 2001 19 Extensions to the MPLS Traffic Engineering Management 20 Information Base in Support of Generalized Multi-Protocol 21 Label Switching. 23 draft-nadeau-mpls-gmpls-te-mib-00.txt 25 Status of this Memo 27 This document is an Internet-Draft and is in full 28 conformance with all provisions of Section 10 of RFC2026. 30 Internet-Drafts are working documents of the Internet 31 Engineering Task Force (IETF), its areas, and its working 32 groups. Note that other groups may also distribute working 33 documents as Internet-Drafts. 35 Internet-Drafts are draft documents valid for a maximum of 36 six months and may be updated, replaced, or obsoleted by 37 other documents at any time. It is inappropriate to use 38 Internet-Drafts as reference material or to cite them other 39 than as "work in progress." 41 The list of current Internet-Drafts can be accessed at 42 http://www.ietf.org/ietf/1id-abstracts.txt. 44 The list of Internet-Draft Shadow Directories can be 45 accessed at http://www.ietf.org/shadow.html. 47 Table of Contents 49 1. Abstract............................................ 50 2. Introduction........................................ 51 3. Terminology......................................... 53 4. The SNMP Management Framework....................... 54 4.1. Object Definitions.................................. 55 5. Feature Checklist................................... 56 6. Outline............................................. 57 6.1. Summary of GMPLS Traffic Engineering MIB............ 58 7. Brief Description of MIB Objects.................... 59 7.1. gmplsTunnelTable.................................... 60 7.2 gmplsTunnelHopTable................................. 61 8. Example of GMPLS Tunnel Setup....................... 62 9. GMPLS Traffic Engineering MIB Definitions........... 63 10. Security Considerations............................. 64 11. Acknowledgments..................................... 65 12. References.......................................... 66 13. Authors' Addresses.................................. 67 14. Full Copyright Statement............................ 69 1. Abstract 71 This memo defines an experimental portion of the Management 72 Information Base (MIB) for use with network management 73 protocols in the Internet community. In particular, it 74 describes managed objects for extending the Multi-Protocol 75 Label Switching (MPLS) [MPLSArch] Traffic Engineering 76 Management Information Base in order to support Generalized 77 MPLS [GMPLSARCH]. 79 2. Introduction 81 This memo defines an experimental portion of the Management 82 Information Base (MIB) for use with network management 83 protocols in the Internet community. In particular, it 84 describes managed objects for modeling a Multi-Protocol 85 Label Switching (MPLS) [MPLSArch] based traffic 86 engineering. This MIB should be used in conjunction with 87 the companion document [LSRMIB] for MPLS based traffic 88 engineering configuration and management. 90 Comments should be made directly to the MPLS mailing list 91 at mpls@uu.net. 93 This memo does not, in its draft form, specify a standard 94 for the Internet community. 96 3. Terminology 98 This document uses terminology from the MPLS architecture 99 document [MPLSArch] and MPLS Label Switch Router MIB 101 [LSRMIB]. Some frequently used terms are described next. 103 An explicitly routed LSP (ERLSP) is referred to as an MPLS 104 tunnel. It consists of one in-segment and/or one out- 105 segment at the ingress/egress LSRs, each segment being 106 associated with one MPLS interface. These are also 107 referred to as tunnel segments. Additionally, at an 108 intermediate LSR, we model a connection as consisting of 109 one or more in-segments and/or one or more out-segments. 110 The binding or interconnection between in-segments and out- 111 segments in performed using a cross-connect. These objects 112 are defined in the MPLS Label Switch Router MIB [LSRMIB]. 114 4. The SNMP Management Framework 116 The SNMP Management Framework presently consists of five 117 major components: 119 - An overall architecture, described in RFC 2271 120 [SNMPArch]. 122 - Mechanisms for describing and naming objects and events 123 for the purpose of management. The first version of 124 this Structure of Management Information (SMI) is 125 called SMIv1 and described in RFC 1155 [SMIv1], RFC 126 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. The 127 second version, called SMIv2, is described in RFC 1902 128 [SMIv2], RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. 130 - Message protocols for transferring management 131 information. The first version of the SNMP message 132 protocol is called SNMPv1 and described in RFC 1157 133 [SNMPv1]. A second version of the SNMP message 134 protocol, which is not an Internet standards track 135 protocol, is called SNMPv2c and described in RFC 1901 136 [SNMPv2c] and RFC 1906 [SNMPv2TM]. The third version 137 of the message protocol is called SNMPv3 and described 138 in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and RFC 139 2574 [SNMPv3USM]. 141 - Protocol operations for accessing management 142 information. The first set of protocol operations and 143 associated PDU formats is described in RFC 1157 144 [SNMPv1]. A second set of protocol operations and 145 associated PDU formats is described in RFC 1905 146 [SNMPv2PO]. 148 - A set of fundamental applications described in RFC 2273 149 [SNMPv3App] and the view-based access control mechanism 150 described in RFC 2575 [SNMPv3VACM]. 152 Managed objects are accessed via a virtual information 153 store, termed the Management Information Base or MIB. 154 Objects in the MIB are defined using the mechanisms defined 155 in the SMI. This memo specifies a MIB module that is 156 compliant to the SMIv2. A MIB conforming to the SMIv1 can 157 be produced through the appropriate translations. The 158 resulting translated MIB must be semantically equivalent, 159 except where objects or events are omitted because no 160 translation is possible (use of Counter64). Some machine- 161 readable information in SMIv2 will be converted into 162 textual descriptions in SMIv1 during the translation 163 process. However, this loss of machine-readable 164 information is not considered to change the semantics of 165 the MIB. 167 4.1. Object Definitions 169 Managed objects are accessed via a virtual information 170 store, termed the Management Information Base or MIB. 171 Objects in the MIB are defined using the subset of Abstract 172 Syntax Notation One (ASN.1) defined in the SMI. In 173 particular, each object type is named by an OBJECT 174 IDENTIFIER, an administratively assigned name. The object 175 type together with an object instance serves to uniquely 176 identify a specific instantiation of the object. For human 177 convenience, we often use a textual string, termed the 178 descriptor, to also refer to the object type. 180 5. Feature List 182 The GMPLS traffic engineering MIB is designed to satisfy the 183 following requirements and constraints. 185 - GMPLS tunnel entries extend and reuse the 186 mplsTunnelEntry from the MPLS-TE-MIB. 188 - The MIB supports manually configured GMPLS tunnels as 189 well as those set up via any GMPLS signaling protocol. 191 6. Outline 193 Support for GMPLS traffic-engineered tunnels requires the 194 following configuration. 196 - Setting up GMPLS-specific tunnel configuration parameters. 198 - Setting up MPLS-specific tunnel configuration parameters. 200 These actions may need to be accompanied with corresponding 201 actions using [MPLSTEMIB] to establish and configure 202 tunnels. 204 6.1. Summary of GMPLS Traffic Engineering MIB 206 The MIB objects for performing these actions consist of the 207 following tables. 209 - Tunnel Table (gmplsTunnelTable) for setting up GMPLS 210 tunnels. 212 - Other corresponding tables in the MPLS-TE-MIB [MPLSTEMIB] 213 and perhaps the MPLS-LSR-MIB [LSRMIB] 215 - Tunnel hop table (gmplsTunnelHopTable) to extend the hops 216 defined in the mplsTunnleHopTable, for example to indicate 217 the explicit labels to be used at each hop. 219 7. Brief Description of MIB Objects 221 The tables support both manually configured and signaled 222 tunnels as described in [TBD]. 224 7.1. gmplsTunnelTable 226 The mplsTunnelTable allows new GMPLS tunnels to be created 227 (provisioned) between an MPLS LSR and a remote endpoint, and 228 existing tunnels to be reconfigured or removed. This is 229 achieved by working with and extending, the existing 230 MPLS-TE-MIB. 232 7.2. gmplsTunnelHopTable 234 The gmplsTunnelHopTable is used to indicate the explicit labels 235 to be used on the hops of an GMPLS tunnel. This table extends 236 the mplsTunnelHopTable. Its use is only valid for tunnels 237 defined using both the mplsTunnelTable and the gmplsTunnelTable 239 8. Example of GMPLS Tunnel Setup 241 This section contains an example of which MIB objects 242 should be modified if one would like to create a best 243 effort, loosely routed, bi-directional traffic engineered 244 tunnel, which spans two hops of a simple network and uses 245 Generalized Label requests with Lambda encoding and shared 246 link layer protection. Note that these objects should be created 247 on the "head-end" LSR. 249 In this example an instance of gmplsTunnelEntry is created. 250 Subsequently an instance of mplsTunnelEntry is created which has 251 values that match the indices used in the gmplsTunnelEntry (i.e. 252 it is the associated mplsTunnelEntry for the gmplsTunnelEntry). 253 Finally instances of mplsTunnelResourceEntry and mplsTunnelHopEntry 254 are created. 256 The effect of this sequence is that at the point that the Tunnel 257 becomes active (e.g. mplsTunnelOperStatus becomes up), the tunnel 258 is signaled using a generalized label request object/TLV and 259 an upstream label object/TLV on the appropriate signaling message. 261 In gmplsTunnelTable: 262 INDEX { 1, 1, 123.123.125.1, 123.123.126.1 } 263 { 264 gmplsTunnelRowStatus = createAndGo (4), 265 gmplsTunnelLSPEncoding = tunnelLspLambda (8), 266 gmplsTunnelLinkProtection = shared (2), 267 gmplsTunnelGPid = lambda (37), 268 gmplsTunnelBiDirectional = true 269 } 271 In mplsTunnelTable: 272 { 273 mplsTunnelIndex = 1, 274 mplsTunnelInstance = 1, 275 mplsTunnelIngressLSRId = 123.123.125.1, 276 mplsTunnelEgressLSRId = 123.123.126.1, 277 mplsTunnelName = "My first tunnel", 278 mplsTunnelDescr = "Here to there and back again", 279 mplsTunnelIsIf = true (1), 280 mplsTunnelSignallingProto = none (1), 281 mplsTunnelSetupPrio = 0, 282 mplsTunnelHoldingPrio = 0, 283 mplsTunnelSessionAttributes = 0, 284 mplsTunnelOwner = snmp (1), 285 mplsTunnelLocalProtectInUse = false (0), 286 mplsTunnelResourcePointer = mplsTunnelResourceIndex.5, 287 mplsTunnelInstancePriority = 1, 288 mplsTunnelHopTableIndex = 1, 289 mplsTunnelPrimaryInstance = 0, 290 mplsTunnelIncludeAnyAffinity = 0, 291 mplsTunnelIncludeAllAffinity = 0, 292 mplsTunnelExcludeAllAffinity = 0, 293 mplsTunnelPathInUse = 1, 294 mplsTunnelRole = head(1), 295 mplsTunnelRowStatus = createAndGo (4) 296 } 297 Entries in the mplsTunnelResourceTable and mplsTunnelHopTable are 298 created and activated at this time. 300 In mplsTunnelResourceTable: 301 { 302 mplsTunnelResourceIndex = 5, 303 mplsTunnelResourceMaxRate = 0, 304 mplsTunnelResourceMeanRate = 0, 305 mplsTunnelResourceMaxBurstSize = 0, 306 mplsTunnelResourceRowStatus = createAndGo (4) 307 } 309 The next two instances of mplsTunnelHopEntry are used to 310 denote the hops this tunnel will take across the network. 312 The following denotes the beginning of the network, or the 313 first hop. We have used the fictitious LSR identified by 314 "123.123.125.1" as our example head-end router. 316 In mplsTunnelHopTable: 317 { 318 mplsTunnelHopListIndex = 1, 319 mplsTunnelPathOptionIndex = 1, 320 mplsTunnelHopIndex = 1, 321 mplsTunnelHopAddrType = 1, 322 mplsTunnelHopIpv4Addr = 123.123.125.1, 323 mplsTunnelHopIpv4PrefixLen = 9, 324 mplsTunnelHopType = loose (2), 325 mplsTunnelHopRowStatus = createAndGo (4) 326 } 328 The following denotes the end of the network, or the last 329 hop in our example. We have used the fictitious LSR 330 identified by "123.123.126.1" as our end router. 332 In mplsTunnelHopTable: 333 { 334 mplsTunnelHopListIndex = 1, 335 mplsTunnelPathOptionIndex = 1, 336 mplsTunnelHopIndex = 2, 337 mplsTunnelHopAddrType = 1, 338 mplsTunnelHopIpv4Addr = 123.123.126.1, 339 mplsTunnelHopIpv4PrefixLen = 9, 340 mplsTunnelHopType = loose (2), 341 mplsTunnelHopRowStatus = createAndGo (4) 342 } 344 Note that it would be possible to activate the row in the 345 mplsTunnelTable prior to creating the row in the gmplsTunnelTable. 346 In this case, the tunnel would be set-up using normal (non 347 generalized) label requests. When an associated gmplsTunnelEntry 348 was activated, the tunnel would be resignaled using generalized 349 label requests. 351 9. GMPLS Traffic Engineering MIB Definitions 353 MPLS-TE-MIB DEFINITIONS ::= BEGIN 355 IMPORTS 356 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 357 experimental, Integer32, Unsigned32, Counter32, 358 Counter64, TimeTicks, TimeStamp 359 FROM SNMPv2-SMI 361 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 362 FROM SNMPv2-CONF 364 TEXTUAL-CONVENTION, TruthValue, RowStatus, RowPointer, 365 StorageType, DisplayString 366 FROM SNMPv2-TC 368 InterfaceIndexOrZero 369 FROM IF-MIB 371 MplsBitRate, MplsBurstSize, MplsLSPID, MplsLabel, 372 mplsTunnelIndex, mplsTunnelInstance, 373 mplsTunnelIngressLSRId, mplsTunnelEgressLSRId 374 FROM MPLS-TC-MIB 376 InetAddressIPv4, InetAddressIPv6 377 FROM INET-ADDRESS-MIB; 379 mplsTeMIB MODULE-IDENTITY 380 LAST-UPDATED 381 "200104271200Z" -- April 27, 2001 12:00:00 EST 382 ORGANIZATION 383 "Multiprotocol Label Switching (MPLS) Working Group" 384 CONTACT-INFO 385 " Thomas D. Nadeau 386 Cisco Systems, Inc. 387 tnadeau@cisco.com 389 Cheenu Srinivasan 390 Alphion 391 cheenu@optosphere.com 393 Arun Viswanathan 394 Force10 Networks, Inc. 396 arun@force10networks.com 398 Adrian Farrel 399 Movaz Networks, Inc. 400 afarrel@movaz.com 402 Edward Harrison 403 Data Connection Ltd. 404 eph@dataconnection.com 406 Tim Hall 407 Data Connection Ltd. 408 TimHall@dataconnection.com 410 ccamp@ops.ietf.org" 411 DESCRIPTION 412 "This MIB module contains managed object definitions 413 for GMPLS Traffic Engineering (TE) as defined in: 414 Extensions to RSVP for LSP Tunnels, Awduche et al, 415 Internet Draft , February 2001; Constraint-Based LSP Setup 417 using LDP, B. Jamoussi, Internet Draft , July 2000; Requirements for 419 Traffic Engineering Over MPLS, Awduche, D., J. 420 Malcolm, J., Agogbua, J., O'Dell, M., J. McManus, 421 , September 1999., and 422 Generalized Multi-Protocol Label Switching (GMPLS) 423 Architecture, Ashwood-Smith, P, et al, 424 Internet Draft , 425 February 2001. Generalized MPLS - Signaling Functional 426 Description, Ashwood-Smith, P., et. al, Internet 427 Draft , 428 March 2001, Generalized MPLS Signaling - CR-LDP 429 Extensions, Ashwood-Smith, P., et al., Internet 430 Draft , 431 March 2001, Generalized MPLS Signaling - RSVP-TE Extensions, 432 Ashwood-Smith, P., et. al., Internet 433 Draft , 434 March, 2001." 436 -- Revision history. 438 REVISION 439 "200104301200Z" -- 16 July 1999 12:00:00 GMT 440 DESCRIPTION 441 "Initial draft version." 443 ::= { experimental XXX } -- To Be Assigned by IANA 445 -- Textual Conventions. 447 MplsGeneralizedLabel ::= TEXTUAL-CONVENTION 448 STATUS current 449 DESCRIPTION 450 "This value represents a generalized MPLS Label. 451 The label contents are specific to the label being 452 represented." 453 SYNTAX Unsigned64 455 MplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION 456 STATUS current 457 DESCRIPTION 458 "The label types that are defined for Generalized MPLS." 459 SYNTAX INTEGER { 460 MplsLabel(1), 461 GeneralizedLabel(2), 462 WavebandLabel(3) 463 } 465 -- Top level components of this MIB. 467 -- tables, scalars 468 gmplsTeNotifications OBJECT IDENTIFIER ::= { gmplsTeMIB 0 } 469 gmplsTeObjects OBJECT IDENTIFIER ::= { gmplsTeMIB 1 } 470 gmplsTeConformance OBJECT IDENTIFIER ::= { gmplsTeMIB 2 } 472 -- GMPLS Tunnel scalars. 474 gmplsTunnelsConfigured OBJECT-TYPE 475 SYNTAX Unsigned32 476 MAX-ACCESS read-only 477 STATUS current 478 DESCRIPTION 479 "The number of tunnels configured on this device 480 which are have the GMPLS functionallity configured. 481 A tunnel is considered configured if the 482 gmplsTunnelRowStatus is active(1)." 483 ::= { gmplsTeScalars 1 } 485 gmplsTunnelActive OBJECT-TYPE 486 SYNTAX Unsigned32 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION 490 "The number of GMPLS tunnels active on this 491 device. A tunnel is considered active if the 492 gmplsTunnelOperStatus is up(1)." 493 ::= { gmplsTeScalars 2 } 495 -- End of GMPLS Tunnel scalars. 497 -- GMPLS tunnel table. 499 gmplsTunnelTable OBJECT-TYPE 500 SYNTAX SEQUENCE OF GmplsTunnelEntry 501 MAX-ACCESS not-accessible 502 STATUS current 503 DESCRIPTION 504 "The gmplsTunnelTable allows new GMPLS tunnels to be 505 created between an LSR and a remote endpoint, and 506 existing tunnels to be reconfigured or removed. 507 This table extends the mplsTunnelTable found in 508 the MPLS-TE-MIB. Entries in this table MUST 509 correspond to those entries in the MPLS-TE-MIB 510 which are to be used with GMPLS functionallity. 512 Entries in the gmplsTunneltable and mplsTunnelTable 513 may be created independently, however, to activate 514 a GMPLS tunnel there MUST be an entry in both tables 515 with the same index values. Managers should create 516 a corresponding mplsTunnelEntry in the 517 mplsTunnelTable if a row in this table is created 518 first, and put that row in the create-and-wait state. 520 If an entry in this table is destroyed or disabled, 521 this indicates that the GMPLS functionallity on this 522 tunnel is disabled. 524 Ed Note: We should outline all 4 possible cases here 525 when we have some more time." 526 ::= { gmplsTeObjects 1 } 528 gmplsTunnelEntry OBJECT-TYPE 529 SYNTAX GmplsTunnelEntry 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION 533 "An entry in this table represents an MPLS tunnel 534 which has GMPLS configured." 535 INDEX { mplsTunnelIndex, mplsTunnelInstance, 536 mplsTunnelIngressLSRId, mplsTunnelEgressLSRId } 537 ::= { gmplsTunnelTable 1 } 539 GmplsTunnelEntry ::= SEQUENCE { 540 gmplsTunnelAdminStatus INTEGER, 541 gmplsTunnelOperStatus INTEGER, 542 gmplsTunnelRowStatus RowStatus, 543 gmplsTunnelStorageType StorageType, 544 gmplsTunnelLSPEncoding INTEGER, 545 gmplsTunnelLinkProtection BITS, 546 gmplsTunnelGPid Unsigned32, 547 gmplsTunnelRNC Unsigned32, 548 gmplsTunnelSignalType Unsigned32, 549 gmplsTunnelRGT Unsigned32, 550 gmplsTunnelSecondary TruthValue, 551 gmplsTunnelBiDirectional TruthValue 552 } 554 mplsTunnelAdminStatus OBJECT-TYPE 555 SYNTAX INTEGER { 556 up(1), -- GMPLS feature enabled 557 down(2), -- GMPLS feature disabled 558 testing(3) -- put in testing state 559 } 560 MAX-ACCESS read-create 561 STATUS current 562 DESCRIPTION 563 "Indicates the desired operational status of this 564 GMPLS tunnel." 565 ::= { mplsTunnelEntry 1 } 567 gmplsTunnelOperStatus OBJECT-TYPE 568 SYNTAX INTEGER { 569 up(1), 570 down(2), 571 testing(3), 572 unknown(4), 573 dormant(5), 574 notPresent(6), 575 lowerLayerDown(7) 576 } 577 MAX-ACCESS read-only 578 STATUS current 579 DESCRIPTION 580 "Indicates the actual operational status of GMPLS 581 on this tunnel, which is typically but not limited 582 to, a function of the state of individual segments of 583 this tunnel and the state of the corresponding 584 mplsTunnelEntry. 586 The states of this value are defined as follows. 588 up(1) -- ready to pass packets 589 down(2) 590 testing(3) -- in some test mode 591 unknown(4) -- status cannot be determined 592 dormant(5) -- some component is missing 593 notPresent(6) 594 lowerLayerDown(7) -- down due to the state 595 of lower layer interfaces " 596 ::= { gmplsTunnelEntry 1 } 598 gmplsTunnelRowStatus OBJECT-TYPE 599 SYNTAX RowStatus 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "This variable is used to create, modify, and/or 604 delete a row in this table." 605 ::= { gmplsTunnelEntry 2 } 607 gmplsTunnelStorageType OBJECT-TYPE 608 SYNTAX StorageType 609 MAX-ACCESS read-create 610 STATUS current 611 DESCRIPTION 612 "This variable indicates the storage type for this 613 object. This storage type must mimic that of the 614 corresponding mplsTunnelEntry to ensure predictable 615 behavior." 616 ::= { gmplsTunnelEntry 3 } 618 gmplsTunnelLSPEncoding OBJECT-TYPE 619 SYNTAX INTEGER { 620 tunnelLspPacket (1), 621 tunnelLspEthernetV2Dix (2), 622 tunnelLspAnsiPdh (3), 623 tunnelLspEtsiPdh (4), 624 tunnelLspSdhItutG7071996 (5), 625 tunnelLspSonetAnsiT11051995 (6), 626 tunnelLspDigitalWrapper (7), 627 tunnelLspLambda (8), 628 tunnelLspFiber (9), 629 tunnelLspEthernet8023 (10) 630 tunnelLspSdhItutG7072000 (11) 631 tunnelLspSonetAnsiT11052000(12) 632 } 633 MAX-ACCESS read-create 634 STATUS current 635 DESCRIPTION 636 "This object indicates the encoding of the LSP being requested. 637 It is only required when a generalized label request will be used 638 for this LSP. A value of 0 in this object indicates that a 639 generalized label request will not be used to set up this 640 LSP. Each type is defined specifically as: 642 tunnelLspPacket (1) - 643 tunnelLspEthernetV2Dix (2) - 644 tunnelLspAnsiPdh (3) - 645 tunnelLspEtsiPdh (4) - 646 tunnelLspSdhItutG7071996 (5) - 647 tunnelLspSonetAnsiT11051995 (6) - 648 tunnelLspDigitalWrapper (7) - 649 tunnelLspLambda (8) - 650 tunnelLspFiber (9) - 651 tunnelLspEthernet8023 (10) - 652 tunnelLspSdhItutG7072000 (11) - 653 tunnelLspSonetAnsiT11052000(12) - 655 Ed Note: Should these be assigned and maintained by IANA?" 656 ::= { gmplsTunnelEntry 4 } 658 gmplsTunnelLinkProtection OBJECT-TYPE 659 SYNTAX BITS { 660 extraTraffic(0), 661 unprotected(1), 662 shared (2), 663 dedicatedOneToOne (3), 664 dedicatedOnePlusOne(4), 665 enhanced(5) 666 } 667 MAX-ACCESS read-create 668 STATUS current 669 DESCRIPTION 670 "This bitmask indicates the level of link protection required. 671 A value of zero (no bits set) indicates that any protection 672 may be used. 674 The following describes these bitfields: 676 extraTraffic Indicates that the LSP should use links 677 that are protecting other (primary) 678 traffic. Such LSPs may be preempted 679 when the links carrying the (primary) 680 traffic being protected fail. 682 unprotected Indicates that the LSP should not use 683 any link layer protection. 685 shared Indicates that a shared link layer 686 protection scheme, such as 1:N 687 protection, should be used to support 688 the LSP. 690 dedicatedOneToOne Indicates that a dedicated link layer 691 protection scheme, i.e., 1:1 protection, 692 should be used to support the LSP. 694 dedicatedOnePlusOne Indicates that a dedicated link layer 695 protection scheme, i.e., 1+1 protection, 696 should be used to support the LSP. 698 enhanced Indicates that a protection scheme that 699 is more reliable than Dedicated 1+1 should 700 be used, e.g., 4 fiber BLSR/MS-SPRING. " 701 ::= { gmplsTunnelEntry 5 } 703 gmplsTunnelGPID OBJECT-TYPE 704 SYNTAX Unsigned32 705 MAX-ACCESS read-create 706 STATUS current 707 DESCRIPTION 708 "This object indicates the payload carried by the LSP. It 709 is only required when GMPLS will be used for this LSP." 710 by mplsTunnelLSPEncodingType. For Ethernet and packet LSPs, 711 the standard Ethertype values may also be used. 713 Ed note: Should IANA maintain these values? Is there a 714 better way of doing this? Say, having an enum 715 for these values, plus another bit mask for the 716 ethertypes and a flag to tell which to use? 718 Currently the following values are valid. 720 unknown(0), 721 ds1SF(1), 722 ds1ESF(2), 723 ds3M23(3) 724 ds3CBitParity(4), 725 asynchE4(5), 726 asynchDS3T3(6), 727 asynchE3(7), 728 bitsynchE3(8), 729 bytesynchE3(9), 730 asynchDS2T2(10), 731 bitsynchDS2T2(11), 732 bytesynchDS2T2(12), 733 asynchE1(13), 734 bytesynchE1(14), 735 bytesynch31ByDS0(15), 736 asynchDS1T1(16), 737 bitsynchDS1T1(17), 738 bytesynchDS1T1(18), 739 bytesynchDS2T2VC12(19), 740 asynchE1VC12(20), 741 bytesynchE1VC12(21), 742 atm(22), 743 ds1SFAsynch(23), 744 ds1ESFAsynch(24), 745 ds3M23Asynch(25), 746 ds3CBitParityAsynch(26), 747 vt(27), 748 sts(28), 749 posNoScrambe16BitCrc(29), 750 posNoScrambe32BitCrc(30), 751 posScrambe16BitCrc(31), 752 posNoScrambe32BitCrc(32), 753 ethernet(33), 754 sdh(34), 755 sonet(35), 756 digitalwrapper(36), 757 lambda(37)" 758 ::= { gmplsTunnelEntry 6 } 760 gmplsTunnelRNC OBJECT-TYPE 761 SYNTAX Unsigned32 762 MAX-ACCESS read-create 763 STATUS current 764 DESCRIPTION 765 "Requested Number of Components. Indicates the number of 766 identical SDH/SONET signal types that are requested to be 767 concatenated or inverse multiplexed in the LSP. 768 This field is only valid if gmplsTunnelLspEncoding 769 is sdh or sonet. Encoding MUST adhere to that specified in 770 the referred document." 771 DEFVAL { 0 } 772 REFERENCE "draft-ietf-mpls-generalized-signaling-02.txt 773 section 3.1.2 but it is about to move to a 774 standalone TDM GMPLS draft." 775 ::= { gmplsTunnelEntry 6 } 777 gmplsTunnelSignalType OBJECT-TYPE 778 SYNTAX Unsigned32 779 MAX-ACCESS read-create 780 STATUS current 781 DESCRIPTION 782 "Indicates the overhead termination type and is interpreted 783 in relation to the LSP Encoding Type. This field is only 784 valid if gmplsTunnelLspEncoding is sdh or sonet." 785 DEFVAL { 0 } 786 ::= { gmplsTunnelEntry 7 } 788 gmplsTunnelRGT OBJECT-TYPE 789 SYNTAX Unsigned32 790 MAX-ACCESS read-create 791 STATUS current 792 DESCRIPTION 793 "Requested Grouping Type. Indicates the SDH/SONET type of 794 grouping requested for the LSP. It is used to constrain 795 the type of concatenation. This field is only valid if 796 gmplsTunnelLspEncoding is sdh or sonet." 797 DEFVAL { 0 } 798 ::= { gmplsTunnelEntry 8 } 800 gmplsTunnelSecondary OBJECT-TYPE 801 SYNTAX TruthValue 802 MAX-ACCESS read-create 803 STATUS current 804 DESCRIPTION 805 "Indicates that the requested LSP is a secondary LSP. It 806 is only valid when GMPLS will be used for this LSP." 807 DEFVAL { false } 808 ::= { gmplsTunnelEntry 9 } 810 gmplsTunnelBiDirectional OBJECT-TYPE 811 SYNTAX TruthValue 812 MAX-ACCESS read-create 813 STATUS current 814 DESCRIPTION 815 "Whether this tunnel is bidirectional or 816 unidirectional. By default, tunnels are 817 unidirectional." 818 DEFVAL { false } 819 ::= { gmplsTunnelEntry 10 } 821 -- End of gmplsTunnelTable 823 -- Begin gmplsTunnelHopTable 825 gmplsTunnelHopTable OBJECT-TYPE 826 SYNTAX SEQUENCE OF GmplsTunnelHopEntry 827 MAX-ACCESS not-accessible 828 STATUS current 829 DESCRIPTION 830 "The gmplsTunnelHopTable is used to indicate the explicit 831 labels to be used on the hops of an GMPLS tunnel. 832 This table extends the mplsTunnelHopTable. Its use is 833 only valid for tunnels defined using both the mplsTunnelTable 834 and the gmplsTunnelTable." 835 ::= { gmplsTeObjects 2 } 837 gmplsTunnelHopEntry OBJECT-TYPE 838 SYNTAX GmplsTunnelHopEntry 839 MAX-ACCESS not-accessible 840 STATUS current 841 DESCRIPTION 842 "An entry in this table represents the explicit labels 843 for a specific tunnel hop. An 844 entry is created by a network administrator for 845 signaled ERLSP set up by an MPLS signaling 846 protocol. 847 Entries in this table must correspond to those entries 848 in the MPLS-TE-MIB which are configured for explicit 849 label control." 850 INDEX { mplsTunnelHopListIndex, 851 mplsTunnelHopPathOptionIndex, mplsTunnelHopIndex } 852 ::= { gmplsTunnelHopTable 1 } 854 GmplsTunnelHopEntry ::= SEQUENCE { 855 gmplsTunnelHopRowStatus RowStatus, 856 gmplsTunnelHopStorageType StorageType 857 gmplsTunnelHopUseExplicitLabel TruthValue, 858 gmplsTunnelHopExplicitLabelType MplsGeneralizedLabelType, 859 gmplsTunnelHopExplicitLabel MplsGeneralizedLabel, 860 gmplsTunnelHopUseReversePathExplicitLabel TruthValue, 861 gmplsTunnelHopReversePathExplicitLabelType MplsGeneralizedLabelType, 862 gmplsTunnelHopReversePathExplicitLabel MplsGeneralizedLabel, 863 } 865 gmplsTunnelHopRowStatus OBJECT-TYPE 866 SYNTAX RowStatus 867 MAX-ACCESS read-create 868 STATUS current 869 DESCRIPTION 870 "This variable is used to create, modify, and/or 871 delete a row in this table." 872 ::= { mplsTunnelHopEntry 1 } 874 gmplsTunnelHopStorageType OBJECT-TYPE 875 SYNTAX StorageType 876 MAX-ACCESS read-create 877 STATUS current 878 DESCRIPTION 879 "This variable indicates the storage type for this 880 object." 881 ::= { mplsTunnelHopEntry 2 } 883 gmplsTunnelHopUseExplicitLabel OBJECT-TYPE 884 SYNTAX TruthValue 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "If this hop should use an explicit out-segment 889 label for the forward path then set this to true. 890 This object is insignificant unless mplsTunnelHopAddrType 891 is set to ipV4 or ipV6 and mplsTunnelHopType is set to 892 strict. 894 If this object is set to false or is insignificant, 895 gmplsTunnelHopExplicitLabelType and 896 gmplsTunnelHopExplicitLabel are insignificant." 897 DEFVAL { false } 898 ::= { gmplsTunnelHopEntry 3 } 900 gmplsTunnelHopExplicitLabelType OBJECT-TYPE 901 SYNTAX MplsGeneralizedLabelType 902 MAX-ACCESS read-create 903 STATUS current 904 DESCRIPTION 905 "Denotes the Type of the label configured in 906 gmplsTunnelHopExplicitLabel." 907 ::= { gmplsTunnelHopEntry 4 } 909 gmplsTunnelHopExplicitLabel OBJECT-TYPE 910 SYNTAX MplsGeneralizedLabel 911 MAX-ACCESS read-create 912 STATUS current 913 DESCRIPTION 914 "The explicit out-segment label to use on the forward 915 path." 916 ::= { gmplsTunnelHopEntry 5 } 918 gmplsTunnelHopUseReversePathExplicitLabel OBJECT-TYPE 919 SYNTAX TruthValue 920 MAX-ACCESS read-create 921 STATUS current 922 DESCRIPTION 923 "If this hop should use an explicit in-segment label 924 for the reverse path then set this to true. 925 This object is insignificant unless mplsTunnelHopAddrType 926 is set to ipV4 or ipV6 and mplsTunnelHopType is set to 927 strict and gmplsTunnelBidirectional in the Tunnel 928 MIB is set to true. 929 If this object is set to false or is insignificant, 930 gmplsTunnelHopReversePathExplicitLabelType and 931 gmplsTunnelHopReversePathExplicitLabel are insignificant." 932 DEFVAL { false } 933 ::= { gmplsTunnelHopEntry 6 } 935 gmplsTunnelHopReversePathExplicitLabelType OBJECT-TYPE 936 SYNTAX MplsGeneralizedLabelType 937 MAX-ACCESS read-create 938 STATUS current 939 DESCRIPTION 940 "Denotes the Type of the label configured in 941 gmplsTunnelHopReversePathExplicitLabel." 942 ::= { mplsTunnelHopEntry 7 } 944 gmplsTunnelHopReversePathExplicitLabel OBJECT-TYPE 945 SYNTAX MplsGeneralizedLabel 946 MAX-ACCESS read-create 947 STATUS current 948 DESCRIPTION 949 "The explicit in-segment label to use on the reverse path." 950 ::= { mplsTunnelHopEntry 8 } 952 -- End of gmplsTunnelHopTable 954 -- Notifications. 956 TBD... 958 -- End of notifications. 960 -- Module compliance. 962 gmplsTeGroups 963 OBJECT IDENTIFIER ::= { gmplsTeConformance 1 } 965 gmplsTeCompliances 966 OBJECT IDENTIFIER ::= { gmplsTeConformance 2 } 968 gmplsTeModuleCompliance MODULE-COMPLIANCE 969 STATUS current 970 DESCRIPTION 971 "Compliance statement for agents that support the 972 GMPLS TE MIB." 973 MODULE -- this module 975 -- The mandatory group has to be implemented by all 976 -- LSRs that originate/terminate ESLSPs/tunnels. 977 -- In addition, depending on the type of tunnels 978 -- supported, other groups become mandatory as 979 -- explained below. 981 MANDATORY-GROUPS { 982 gmplsTunnelGroup, 983 gmplsTunnelScalarGroup 984 } 986 -- gmplsTunnelTable 988 OBJECT gmplsTunnelAdminStatus 989 SYNTAX INTEGER { up (1), down (2) } 990 MIN-ACCESS read-only 991 DESCRIPTION 992 "Only up and down states must be supported. Write 993 access is not required." 995 OBJECT gmplsTunnelOperStatus 996 SYNTAX INTEGER { up (1), down (2) } 997 DESCRIPTION 998 "Only up and down states must be supported. Write 999 access is not required." 1001 OBJECT gmplsTunnelRowStatus 1002 SYNTAX INTEGER { 1003 active(1), 1004 notInService(2), 1005 createAndGo(4), 1006 destroy(6) 1007 } 1008 MIN-ACCESS read-only 1009 DESCRIPTION 1010 "The notReady(3) and createAndWait(5) states need 1011 not be supported. Write access is not required." 1013 OBJECT gmplsTunnelStorageType 1014 SYNTAX INTEGER { other(1) } 1015 MIN-ACCESS read-only 1016 DESCRIPTION 1017 "Only other (1) needs to be supported." 1019 ::= { gmplsTeCompliances 1 } 1021 -- Units of conformance. 1023 gmplsTunnelGroup OBJECT-GROUP 1024 OBJECTS { 1025 gmplsTunnelAdminStatus, 1026 gmplsTunnelOperStatus, 1027 gmplsTunnelRowStatus, 1028 gmplsTunnelStorageType, 1029 gmplsTunnelLSPEncoding, 1030 gmplsTunnelLinkProtection, 1031 gmplsTunnelGPid, 1032 gmplsTunnelRNC, 1033 gmplsTunnelSignalType, 1034 gmplsTunnelRGT, 1035 gmplsTunnelSecondary, 1036 gmplsTunnelDirection, 1037 gmplsTunnelUseEgressLabel, 1038 gmplsTunnelEgressLabel 1039 } 1040 STATUS current 1041 DESCRIPTION 1042 " TBD " 1043 ::= { gmplsTeGroups 1 } 1045 mplsTunnelScalarGroup OBJECT-GROUP 1046 OBJECTS { 1047 gmplsTunnelsConfigured, 1048 gmplsTunnelsActive 1049 } 1050 STATUS current 1051 DESCRIPTION 1052 "Scalar objects needed to implement GMPLS tunnels." 1053 ::= { gmplsTeGroups 2 } 1055 -- End of GMPLS-TE-MIB 1056 END 1058 10. Security Considerations 1060 There are a number of management objects defined in this 1061 MIB that have a MAX-ACCESS clause of read-write and/or 1062 read-create. Such objects may be considered sensitive or 1063 vulnerable in some network environments. The support for 1064 SET operations in a non-secure environment without proper 1065 protection can have a negative effect on network 1066 operations. 1068 It is thus important to control even GET access to these 1069 objects and possibly to even encrypt the values of these 1070 object when sending them over the network via SNMP. Not 1071 all versions of SNMP provide features for such a secure 1072 environment. 1074 SNMPv1 by itself is not a secure environment. Even if the 1075 network itself is secure (for example by using IPSec 1076 [IPSEC]), there is no control as to who on the secure 1077 network is allowed to access and GET/SET 1078 (read/change/create/delete) the objects in this MIB. It is 1079 recommended that the implementers consider the security 1080 features as provided by the SNMPv3 framework. 1081 Specifically, the use of the User-based Security Model 1082 [SNMPv3USM] and the View- based Access Control 1083 [SNMPv3VACM] is recommended. It is then a customer/user 1084 responsibility to ensure that the SNMP entity giving 1085 access to an instance of this MIB, is properly configured 1086 to give access to the objects only to those principals 1087 (users) that have legitimate rights to indeed GET or SET 1088 (change/create/delete) them. 1090 11. Acknowledgments 1092 TBD... 1094 12. References 1096 [GMPLSARCH] Ashwood-Smith, P., Awduche, D., Banerjee, A., Basak, D, 1097 Berger, L., Bernstein, G., Drake, J., Fan, Y., 1098 Fedyk, D., Grammel, D., Kompella, K., Kullberg, A., 1099 Lang, J., Liaw, F., Papadimitriou, D., Pendarakis, 1100 D., Rajagopalan, B., Rekhter, Y., Saha, D., Sandick, 1101 H., Sharma, V., Swallow, G., Tang, Z., Yu, J., Zinin, 1102 A., Nadeau, T., Mannie, E., Generalized 1103 Multi-Protocol Label Switching (GMPLS) Architecture, 1104 Internet Draft , 1105 March 2001. 1107 [GMPLSCRLDP] Ashwood-Smith, P., Awduche, D., Banerjee, A., Basak, D, 1108 Berger, L., Bernstein, G., Drake, J., Fan, Y., 1109 Fedyk, D., Grammel, D., Kompella, K., Kullberg, A., 1110 Lang, Rajagopalan, B., Rekhter, Y., Saha, D., 1111 Sharma, V., Swallow, G., Bo Tang, Z., Generalized 1112 MPLS Signaling - CR-LDP Extensions, Internet Draft 1113 , March 2001. 1115 [GMPLSRSVPTE] Ashwood-Smith, P., Awduche, D., Banerjee, A., Basak, D, 1116 Berger, L., Bernstein, G., Drake, J., Fan, Y., 1117 Fedyk, D., Grammel, D., Kompella, K., Kullberg, A., 1118 Lang, Rajagopalan, B., Rekhter, Y., Saha, D., 1119 Sharma, V., Swallow, G., Bo Tang, Z., Generalized 1120 MPLS Signaling - RSVP-TE Extensions, Internet 1121 Draft , 1122 March, 2001 1124 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1125 "Multiprotocol Label Switching Architecture", 1126 RFC 3031, August 1999. 1128 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 1129 Nadeau, "MPLS Label Switch Router Management 1130 Information Base Using SMIv2", Internet 1131 Draft , July 1132 2000. 1134 [LblStk] Rosen, E., Rekhter, Y., Tappan, D., Farinacci, D., 1135 Federokow, G., Li, T., and A. Conta, "MPLS Label 1136 Stack Encoding", RFC 3032, January 2001. 1137 label-encaps-07.txt>, September 1999. 1139 [LWFRN] Conta, A., Doolan, P., Malis, A., "Use of Label 1140 Switching on Frame Relay Networks Specification", 1141 RFC 3034, January 2001. 1143 [MLDPATM] Davie, B., Lawrence, J., McCloghrie, K., Rosen, E., 1144 Swallow, G., Rekhter, Y., Doolan, P., "MPLS using 1145 LDP and ATM VC switching", RFC 3035, January 2001. 1147 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 1148 RFC 1700, October 1994. See also: 1149 http://www.isi.edu/in-notes/iana/assignments/smi- 1150 numbers 1152 [Assigned] Reynolds, J., and J. Postel, "Assigned 1153 Numbers", RFC 1700, October 1994. See also: 1154 http://www.isi.edu/in- 1155 notes/iana/assignments/smi-numbers 1157 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, 1158 "An Architecture for Describing SNMP 1159 Management Frameworks", RFC 2271, January 1160 1998. 1162 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 1163 Identification of Management Information for 1164 TCP/IP-based Internets", RFC 1155, May 1990. 1166 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 1167 Definitions", RFC 1212, March 1991. 1169 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps 1170 for use with the SNMP", RFC 1215, March 1171 1991. 1173 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 1174 Waldbusser, "Structure of Management 1175 Information for Version 2 of the Simple 1176 Network Management Protocol (SNMPv2)", RFC 1177 1902, January 1996. 1179 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 1180 Waldbusser, "Textual Conventions for Version 1181 2 of the Simple Network Management Protocol 1182 (SNMPv2)", RFC 1903, SNMP Research, Inc., 1183 Cisco Systems, Inc., January 1996. 1185 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 1186 Waldbusser, "Conformance Statements for 1187 Version 2 of the Simple Network Management 1188 Protocol (SNMPv2)", RFC 1904, January 1996. 1190 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. 1191 Davin, "Simple Network Management Protocol", 1192 RFC 1157, May 1990. 1194 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 1195 Waldbusser, "Introduction to Community-based 1196 SNMPv2", RFC 1901, January 1996. 1198 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 1199 Waldbusser, "Transport Mappings for Version 1200 2 of the Simple Network Management Protocol 1201 (SNMPv2)", RFC 1906, January 1996. 1203 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. 1204 Wijnen, "Message Processing and Dispatching 1205 for the Simple Network Management Protocol 1206 (SNMP)", RFC 2272, January 1998. 1208 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based 1209 Security Model (USM) for version 3 of the 1210 Simple Network Management Protocol 1211 (SNMPv3)", RFC 2574, April 1999. 1213 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 1214 Waldbusser, "Protocol Operations for Version 1215 2 of the Simple Network Management Protocol 1216 (SNMPv2)", RFC 1905, January 1996. 1218 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1219 Applications", RFC 2273, January 1998. 1221 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, 1222 "View-based Access Control Model (VACM) for 1223 the Simple Network Management Protocol 1224 (SNMP)", RFC 2575, April 1999. 1226 [IPSEC] Kent, S., and Atkinson, R., "Security 1227 Architecture for the Internet Protocol", RFC 1228 2401, November 1998. 1230 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The 1231 Interfaces Group MIB using SMIv2", RFC 2233, 1232 Nov. 1997. 1234 [INETADDRMIB] Daniele, M., Haberman, B., Routhier, S. and 1235 J. Schoenwaelder, "Textual Conventions for 1236 Internet Network Addresses", RFC 2851, June 1237 2000. 1239 13. Authors' Addresses 1241 Thomas D. Nadeau 1242 Cisco Systems, Inc. 1243 300 Apollo Drive 1244 Chelmsford, MA 01824 1245 Phone: +1-978-244-3051 1246 Email: tnadeau@cisco.com 1248 Cheenu Srinivasan 1249 Alphion 1250 Phone: +1-732-676-7066 1251 Email: cheenu@optosphere.com 1253 Arun Viswanathan 1254 Force10 Networks, Inc. 1255 1440 McCarthy Blvd 1256 Milpitas, CA 95035 1257 Phone: +1-408-571-3516 1258 Email: arun@force10networks.com 1260 Adrian Farrel 1261 Movaz Networks, Inc. 1262 7926 Jones Branch DriveSuite 615 1263 MCLean VA, 22102USA 1264 Phone: +1 703 847-???? 1265 Email: afarrel@movaz.com 1267 Tim Hall 1268 Data Connection Ltd. 1269 100 Church Street 1270 Enfield 1271 Middlesex 1272 EN2 6BQ 1273 UK 1274 Phone: +44 20 8366 1177 1275 Email: TimHall@dataconnection.com 1277 Edward Harrison 1278 Data Connection Ltd. 1279 100 Church Street 1280 Enfield 1281 Middlesex 1282 EN2 6BQ 1283 UK 1284 Phone: +44 20 8366 1177 1285 Email: eph@dataconnection.com 1287 14. Full Copyright Statement 1289 Copyright (C) The Internet Society (2000). All Rights 1290 Reserved. 1292 This document and translations of it may be copied and 1293 furnished to others, and derivative works that comment on 1294 or otherwise explain it or assist in its implementation may 1295 be prepared, copied, published and distributed, in whole or 1296 in part, without restriction of any kind, provided that the 1297 above copyright notice and this paragraph are included on 1298 all such copies and derivative works. However, this 1299 document itself may not be modified in any way, such as by 1300 removing the copyright notice or references to the Internet 1301 Society or other Internet organizations, except as needed 1302 for the purpose of developing Internet standards in which 1303 case the procedures for copyrights defined in the Internet 1304 Standards process must be followed, or as required to 1305 translate it into languages other than English. 1307 The limited permissions granted above are perpetual and 1308 will not be revoked by the Internet Society or its 1309 successors or assigns. This document and the information 1310 contained herein is provided on an "AS IS" basis and THE 1311 INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE 1312 DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 1313 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1314 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 1315 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR 1316 PURPOSE.