idnits 2.17.1 draft-nadeau-mpls-ds-te-mib-01.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: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 25 longer pages, the longest (page 25) being 69 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 25 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack a Security Considerations section. ** 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 21 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1214 has weird spacing: '...for the purpo...' -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. 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 102, but not defined == Missing Reference: 'LSR-MIB' is mentioned on line 662, but not defined == Missing Reference: 'MPLS-LSR-MIB' is mentioned on line 593, but not defined == Unused Reference: 'LSRMIB' is defined on line 1030, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 1043, but no explicit reference was found in the text == Unused Reference: 'IANAFamily' is defined on line 1048, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 1068, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 1073, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 1078, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 1083, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 1086, but no explicit reference was found in the text == Unused Reference: 'RFC2570' is defined on line 1091, but no explicit reference was found in the text == Unused Reference: 'IPSEC' is defined on line 1148, but no explicit reference was found in the text == Unused Reference: 'IFMIB' is defined on line 1152, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'DSTEREQS' -- Possible downref: Non-RFC (?) normative reference: ref. 'DSTEEXTS' -- Possible downref: Non-RFC (?) normative reference: ref. 'DSTEISIS' -- Possible downref: Non-RFC (?) normative reference: ref. 'DSTEOSPF' ** Downref: Normative reference to an Informational RFC: RFC 2702 (ref. 'MPLSArch') -- Possible downref: Non-RFC (?) normative reference: ref. 'LSRMIB' -- Possible downref: Non-RFC (?) normative reference: ref. 'TEMIB' ** Obsolete normative reference: RFC 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) -- Possible downref: Non-RFC (?) normative reference: ref. 'IANAFamily' ** 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 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** 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) -- Duplicate reference: RFC2574, mentioned in 'SNMPv3USM', was also mentioned in 'RFC2574'. ** Obsolete normative reference: RFC 2574 (ref. 'SNMPv3USM') (Obsoleted by RFC 3414) -- Duplicate reference: RFC1905, mentioned in 'SNMPv2PO', was also mentioned in 'RFC1905'. ** Obsolete normative reference: RFC 1905 (ref. 'SNMPv2PO') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. 'SNMPv3App') (Obsoleted by RFC 2573) -- Duplicate reference: RFC2575, mentioned in 'SNMPv3VACM', was also mentioned in 'RFC2575'. ** 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) Summary: 31 errors (**), 0 flaws (~~), 18 warnings (==), 12 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Thomas D. Nadeau 3 Francois Le Faucheur 4 Cisco Systems, Inc. 6 Angela Chiu 7 Celion Networks 9 William Townsend 10 Tenor Networks 12 Darek Skalecki 13 Nortel Networks 15 Martin Tatham 16 British Telecom 18 IETF Internet Draft 19 Expires: January, 2001 20 Document: draft-nadeau-mpls-ds-te-mib-01.txt July, 2001 22 Diff-Serv-aware MPLS Traffic Engineering Network 23 Management Information Base Using SMIv2 25 Status of this Memo 27 This document is an Internet-Draft and is in full conformance with all 28 provisions of Section 10 of RFC2026. Internet-Drafts are 29 Working documents of the Internet Engineering Task Force (IETF), its 30 areas, and its working groups. Note that other groups may also distribute 31 working documents as Internet-Drafts. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference material 36 or to cite them other than as "work in progress." 38 The list of current Internet-Drafts can be accessed at 39 http://www.ietf.org/ietf/1id-abstracts.txt. 40 The list of Internet-Draft Shadow Directories can be accessed at 41 http://www.ietf.org/shadow.html. 43 Contents 45 1.0 ABSTRACT...............................................2 46 2.0 INTRODUCTION...........................................2 47 3.0 TERMINOLOGY............................................3 48 4.0 THE SNMP MANAGEMENT FRAMEWORK..........................3 49 5.0 OBJECT DEFINITIONS.....................................4 50 6.0 FEATURE CHECKLIST......................................4 51 7.0 OUTLINE................................................4 52 8.0 SUMMARY OF MPLS-DS-TE-MIB..............................4 53 9.0 BRIEF DESCRIPTION OF MIB OBJECTS.......................5 54 10.0 EXAMPLE CONFIGURATION..................................5 55 11.0 MPLS-DS-TE-MIB DEFINITIONS.............................5 56 12.0 ACKNOWLEDGMENTS.......................................21 57 13.0 REFERENCES............................................21 58 14.0 AUTHORS' ADDRESSES....................................24 59 15.0 FULL COPYRIGHT STATEMENT..............................24 61 1.0 Abstract 63 This memo defines an experimental portion of the Management 64 Information Base (MIB) for use with network management protocols in 65 the Internet community. In particular, in response to customer 66 demands and strong input from vendors, it describes managed objects 67 for modeling and managing Diff-Serv-aware MPLS Traffic Engineering 68 [DSTEREQS][DSTEEXTS]. 69 2.0 Introduction 71 This memo defines an experimental portion of the Management 72 Information Base (MIB) for use with network management protocols in 73 the Internet community. In particular, it describes managed objects 74 for modeling and managing Diff-Serv-aware MPLS Traffic Engineering 75 [DSTEREQS][DSTEEXTS]. 77 Comments should be made directly to the MPLS mailing list at mpls@uu.net. 79 This memo does not, in its draft form, specify a standard for the 80 Internet community. 82 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 83 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 84 document are to be interpreted as described in RFC 2119, reference [BCP14]. 86 3.0 Terminology 88 This document uses terminology from the document describing the MPLS 89 architecture [MPLSArch] and from the documents describing 90 Diff-Serv-Aware Traffic Engineering [DSTEREQS][DSTEEXTS][DSTEISIS] 91 [DSTEOSPF]. 93 4.0 The SNMP Management Framework 95 The SNMP Management Framework presently consists of five major components: 97 - An overall architecture, described in RFC 2271 [SNMPArch]. 99 - Mechanisms for describing and naming objects and events for the 100 purpose of management. The first version of this Structure of 101 Management Information (SMI) is called SMIv1 and described in RFC 102 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. 103 The second version, called SMIv2, is described in RFC 1902 [SMIv2], 104 RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. 106 - Message protocols for transferring management information. The 107 first version of the SNMP message protocol is called SNMPv1 and 108 described in RFC 1157 [SNMPv1]. A second version of the SNMP 109 message protocol, which is not an Internet standards track 110 protocol, is called SNMPv2c and described in RFC 1901 [SNMPv2c] and 111 RFC 1906 [SNMPv2TM]. The third version of the message protocol is 112 called SNMPv3 and described in RFC 1906 [SNMPv2TM], RFC 2272 113 [SNMPv3MP] and RFC 2574 [SNMPv3USM]. 115 - Protocol operations for accessing management information. The 116 first set of protocol operations and associated PDU formats is 117 described in RFC 1157 [SNMPv1]. A second set of protocol 118 operations and associated PDU formats is described in RFC 1905 119 [SNMPv2PO]. 121 - A set of fundamental applications described in RFC 2273 [SNMPv3App] 122 and the view-based access control mechanism described in RFC 2575 123 [SNMPv3VACM]. 125 Managed objects are accessed via a virtual information store, termed 126 the Management Information Base or MIB. Objects in the MIB are 127 defined using the mechanisms defined in the SMI. This memo specifies 128 a MIB module that is compliant to the SMIv2. A MIB conforming to the 129 SMIv1 can be produced through the appropriate translations. The 130 resulting translated MIB must be semantically equivalent, except where 131 objects or events are omitted because no translation is possible (use 132 of Counter64). Some machine-readable information in SMIv2 will be 133 converted into textual descriptions in SMIv1 during the translation 134 process. However, this loss of machine-readable information is not 135 considered to change the semantics of the MIB. 137 5.0 Object Definitions 139 Managed objects are accessed via a virtual information store, termed 140 the Management Information Base or MIB. Objects in the MIB are 141 defined using the subset of Abstract Syntax Notation One (ASN.1) 142 defined in the SMI. In particular, each object type is named by an 143 OBJECT IDENTIFIER, an administratively assigned name. The object type 144 together with an object instance serves to uniquely identify a 145 specific instantiation of the object. For human convenience, we often 146 use a textual string, termed the descriptor, to also refer to the 147 object type. 149 6.0 Feature Checklist 151 The Diff-Serv-aware Traffic Engineering MIB (DS-TE-MIB) is designed to 152 satisfy the following requirements and constraints: 154 - The MIB must support the requirements set forth by 155 Requirements for support of Diff-Serv-aware MPLS Traffic 156 Engineering[]. 158 - The MIB must support the extensions set forth by Extensions to 159 RSVP and CR-LDP for support of Diff-Serv-aware MPLS Traffic 160 Engineering[], Extensions to OSPF for support of 161 Diff-Serv-aware MPLS Traffic Engineering[], and Extensions to 162 IS-IS for support of Diff-Serv-aware MPLS Traffic Engineering[]. 164 - The MIB must support both configuration and monitoring of the 165 Diff-Serv-Aware TE features. 167 7.0 Outline 169 T.B.D. ... 171 8.0 Summary of MPLS-DS-TE-MIB 173 The MIB objects for performing these actions consist of the following 174 tables: 176 T.B.D. 178 9.0 Brief Description of MIB Objects 180 The following subsections describe the purpose of each of the objects 181 contained in the MPLS-DS-TE-MIB. 183 10.0 Example Configuration 185 11.0 MPLS-DS-TE-MIB Definitions 187 MPLS-DS-TE-MIB DEFINITIONS ::= BEGIN 189 IMPORTS 190 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 191 experimental, Integer32, Counter32, Unsigned32, 192 Counter64, Gauge32, TimeTicks 193 FROM SNMPv2-SMI 195 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 196 FROM SNMPv2-CONF 198 TEXTUAL-CONVENTION, TruthValue, RowStatus, StorageType, 199 RowPointer, TimeStamp 200 FROM SNMPv2-TC 202 InterfaceIndex, InterfaceIndexOrZero 203 FROM IF-MIB 205 SnmpAdminString 206 FROM SNMP-FRAMEWORK-MIB 208 AddressFamilyNumbers 209 FROM IANA-ADDRESS-FAMILY-NUMBERS-MIB 211 MplsLabel 212 FROM MPLS-LSR-MIB 214 InetAddress, InetAddressType 215 FROM INET-ADDRESS-MIB; 217 mplsDsTeMIB MODULE-IDENTITY 218 LAST-UPDATED "200107181200Z" -- 18 July 2001 12:00:00 EST 219 ORGANIZATION "Internet Engineering Task Force." 221 CONTACT-INFO 222 " Thomas D. Nadeau 223 Postal: Cisco Systems, Inc. 224 250 Apollo Drive 225 Chelmsford, MA 01824 226 USA 227 Tel: +1-978-244-3051 228 Email: tnadeau@cisco.com 230 Francois Le Faucheur 231 Postal: Cisco Systems, Inc. 232 Petra B - Les Lucioles - 291, 233 rue Albert Caquot - 06560 Valbonne 234 France 235 Tel: +33 4 92 96 75 64 236 Email: flefauch@cisco.com 238 Angela Chiu 239 Postal: Celion Networks 240 1 Sheila Drive, Suite 2 241 Tinton Falls, NJ 07724 242 Tel: +1-732-747-9987 243 Email: angela.chiu@celion.com 245 William Townsend 246 Postal: Tenor Networks 247 100 Nagog Park 248 Acton, MA 01720 249 USA 250 Tel: +1-978-264-4900 251 Email: btownsend@tenornetworks.com 253 Postal: Darek Skalecki 254 Nortel Networks 255 3500 Carling Ave, 256 Nepean K2H 8E9 257 CANADA 258 Tel: +1-613-765-2252 259 Email: dareks@nortelnetworks.com 261 General Discussion and Questions: mpls@uu.net 262 " 264 DESCRIPTION 265 "This MIB contains managed object definitions for 266 Diff-Serv-aware MPLS Traffic Engineering as described in 267 [DSTEREQS][DSTEEXTS]." 269 -- Revision history. 270 REVISION 271 "200107181200Z" -- 18 July 2001 12:00:00 EST 272 DESCRIPTION 273 "Updated draft to keep alive." 275 REVISION 276 "200102151200Z" -- 15 February 2001 12:00:00 EST 277 DESCRIPTION 278 "Initial draft version." 279 ::= { experimental 9999 } -- To be assigned 281 -- Textual Conventions. 283 -- Top level components of this MIB. 285 mplsDsTeNotifications OBJECT IDENTIFIER ::= { mplsDsTeMIB 0 } 286 mplsDsTeObjects OBJECT IDENTIFIER ::= { mplsDsTeMIB 1 } 287 mplsDsTeScalarObjects OBJECT IDENTIFIER ::= { mplsDsTeObjects 1 } 288 mplsDsTeConformance OBJECT IDENTIFIER ::= { mplsDsTeMIB 2 } 290 -- Scalars 292 mplsDsTeNumConfIfs OBJECT-TYPE 293 SYNTAX Unsigned32 294 MAX-ACCESS read-only 295 STATUS current 296 DESCRIPTION 297 "Indicates the number of interfaces which are configured for 298 DiffServ-Aware TE MPLS capability on this device." 299 ::= { mplsDsTeScalarObjects 1 } 301 -- DiffServ-Aware TE Interface Configuration Table 303 mplsDsTeIfConfTable OBJECT-TYPE 304 SYNTAX SEQUENCE OF MplsDsTeIfConfEntry 305 MAX-ACCESS not-accessible 306 STATUS current 307 DESCRIPTION 308 "This table specifies per-interface DiffServ-Aware TE MPLS 309 capability and associated information. The entries in this 310 table correspond to MPLS-enabled interfaces which must also be 311 present in the mplsInterfaceConfTable [LSR-MIB]." 312 ::= { mplsDsTeObjects 2 } 314 mplsDsTeIfConfEntry OBJECT-TYPE 315 SYNTAX MplsDsTeIfConfEntry 316 MAX-ACCESS not-accessible 317 STATUS current 318 DESCRIPTION 319 "An entry in this table is created by an LSR for every 320 interface capable of supporting MPLS DiffServ-Aware Traffic 321 Engineering. Each entry in this table should correspond to an 322 entry in the mplsInterfaceConfTable [LSR-MIB], and will have a 323 corresponding Interfaces MIB entry as well. Administrators 324 wishing to enable the DS-TE feature on an interface without 325 this feature already enabled should first create entries in 326 the MPLS interface conf table in the MPLS-LSR-MIB. Next, the 327 agent should create a corresponding entry in this table to 328 specifically enable the DS-TE feature on the MPLS 329 interface. This order or operation should be enforced by the 330 agent to preserve consistency and interoperability. This table 331 'extends' the Interfaces MIB in that each entry in this table 332 MUST correspond to an entry in the Interfaces MIB. Therefore 333 the index used in this table must correspond to one found in 334 the Interfaces MIB." 335 INDEX { mplsDsTeIfConfIndex } 336 ::= { mplsDsTeIfConfTable 1 } 338 MplsDsTeIfConfEntry ::= SEQUENCE { 339 mplsDsTeIfConfIndex InterfaceIndex, 340 mplsDsTeIfMaxAggrResBw Unsigned32, 341 mplsDsTeIfMaxAddrUnresBw Unsigned32, 342 mplsDsTeIfAggrResBwUsed Unsigned32, 343 mplsDsTeIfAggrUnresBwUsed Unsigned32, 344 mplsDsTeIfDsTeAdminStatus INTEGER, 345 mplsDsTeIfDsTeOperStatus INTEGER, 346 mplsDsTeIfRowStatus RowStatus, 347 mplsDsTeIfConfStorageType StorageType 348 } 350 mplsDsTeIfConfIndex OBJECT-TYPE 351 SYNTAX InterfaceIndex 352 MAX-ACCESS accessible-for-notify 353 STATUS current 354 DESCRIPTION 355 "This is a unique index for an entry in the 356 MplsDsTeIfConfTable. A non-zero index for an entry indicates 357 the ifIndex for the corresponding Interfaces MIB entry. Note 358 that this table does not necessarily correspond one-to-one with 359 all entries in the Interface MIB having an ifType of 360 MPLS-layer; rather, only those which are enabled for MPLS 361 DiffServ-Aware TE functionality." 362 REFERENCE 363 "RFC 2233 - The Interfaces Group MIB using SMIv2, 364 McCloghrie, K., and F. Kastenholtz, Nov. 1997" 365 ::= { mplsDsTeIfConfEntry 1 } 367 mplsDsTeIfMaxAggrResBw OBJECT-TYPE 368 SYNTAX Unsigned32 369 MAX-ACCESS read-create 370 STATUS current 371 DESCRIPTION 372 "The maximum bandwidth reservable on an aggregated basis among all 373 bandwidth classes. Note that overbooking of this value is 374 allowed, and sometimes desirable." 375 ::= { mplsDsTeIfConfEntry 2 } 377 mplsDsTeIfMaxAddrUnresBw OBJECT-TYPE 378 SYNTAX Unsigned32 379 MAX-ACCESS read-create 380 STATUS current 381 DESCRIPTION 382 "The maximum bandwidth which is un-reservable on an aggregated basis 383 among all bandwidth classes. Note that overbooking of this value 384 is allowed, and sometimes desirable." 385 ::= { mplsDsTeIfConfEntry 3 } 387 mplsDsTeIfAggrResBwUsed OBJECT-TYPE 388 SYNTAX Unsigned32 389 MAX-ACCESS read-only 390 STATUS current 391 DESCRIPTION 392 "The amount of reservable bandwidth which currently in use an 393 aggregated basis among all bandwidth classes." 394 ::= { mplsDsTeIfConfEntry 4 } 396 mplsDsTeIfAggrUnresBwUsed OBJECT-TYPE 397 SYNTAX Unsigned32 398 MAX-ACCESS read-only 399 STATUS current 400 DESCRIPTION 401 "The amount of un-reservable bandwidth which currently in use an 402 aggregated basis among all bandwidth classes." 403 ::= { mplsDsTeIfConfEntry 5 } 405 mplsDsTeIfAdminStatus OBJECT-TYPE 406 SYNTAX INTEGER { enabled(1), -- enables the feature 407 disabled(2), -- disables the feature 408 } 409 MAX-ACCESS read-create 410 STATUS current 411 DESCRIPTION 412 "This object is used to indicate the desired DiffServ-Aware TE 413 functionality status (i.e.: enable/disable) on the corresponding 414 MPLS interface." 415 ::= { mplsDsTeIfConfEntry 6 } 417 mplsDsTeIfOperStatus OBJECT-TYPE 418 SYNTAX INTEGER { up(1), -- ready to pass packets 419 down(2), 420 testing(3), -- in some test mode 421 unknown(4), -- status cannot be determined 422 dormant(5), 423 notPresent(6), -- some component is missing 424 lowerLayerDown(7) -- down due to the state of 425 -- lower layer interfaces 427 } 428 MAX-ACCESS read-only 429 STATUS current 430 DESCRIPTION 431 "This object is used to indicate the actual status of the 432 DiffServ-Aware TE feature on this interface." 433 ::= { mplsDsTeIfConfEntry 7 } 435 mplsDsTeIfConfRowStatus OBJECT-TYPE 436 SYNTAX RowStatus 437 MAX-ACCESS read-create 438 STATUS current 439 DESCRIPTION 440 "The row status for a row in this table." 441 ::= { mplsDsTeIfConfEntry 8 } 443 mplsDsTeIfConfStorageType OBJECT-TYPE 444 SYNTAX StorageType 445 MAX-ACCESS read-create 446 STATUS current 447 DESCRIPTION 448 "The storage type for this entry." 449 ::= { mplsDsTeIfConfEntry 9 } 451 -- DS TE Interface Class Type Table 453 mplsDsTeIfClassTypeTable OBJECT-TYPE 454 SYNTAX SEQUENCE OF MplsDsTeIfClassTypeEntry 455 MAX-ACCESS not-accessible 456 STATUS current 457 DESCRIPTION 458 "This table specifies per-interface DiffServ-Aware TE class 459 type information. This table AUGMENTS the 460 mplsDsTeIfConfTable." 461 ::= { mplsDsTeObjects 3 } 463 mplsDsTeIfClassTypeEntry OBJECT-TYPE 464 SYNTAX MplsDsTeIfClassTypeEntry 465 MAX-ACCESS not-accessible 466 STATUS current 467 DESCRIPTION 468 "An entry in this table is created by an LSR for every 469 interface capable of supporting MPLS DiffServ-Aware Traffic 470 Engineering. Specifically, an entry in this table must 471 correspond to an entry in the mplsDsTeIfConfTable. Each entry 472 in this table corresponds to a specific class type associated 473 with an interface. The entries in this table are used to 474 expose the bandwidth classes associated with each 475 interface. At the moment, only 4 bandwidth classes are 476 supported." 477 AUGMENTS { mplsDsTeIfConfTable } 478 ::= { mplsDsTeClassTypeTable 1 } 480 MplsDsTeIfClassTypeEntry ::= SEQUENCE { 481 mplsDsTeIfClassTypeZeroMaxResBw Unsigned32, 482 mplsDsTeIfClassTypeZeroUnresBw Unsigned32, 483 mplsDsTeIfClassTypeOneMaxResBw Unsigned32, 484 mplsDsTeIfClassTypeOneUnresBw Unsigned32, 485 mplsDsTeIfClassTypeTwoMaxResBw Unsigned32, 486 mplsDsTeIfClassTypeTwoUnresBw Unsigned32, 487 mplsDsTeIfClassTypeThreeMaxResBw Unsigned32, 488 mplsDsTeIfClassTypeThreeUnresBw Unsigned32, 489 } 491 mplsDsTeIfClassTypeZeroMaxResBw OBJECT-TYPE 492 SYNTAX InterfaceIndex 493 MAX-ACCESS read-create 494 STATUS current 495 DESCRIPTION 496 "This value indicates the maximum reservable bandwidth for 497 class type 0." 498 DEFVAL { 0 } 499 ::= { mplsDsTeIfClassTypeEntry 1 } 501 mplsDsTeIfClassTypeZeroUnresBw OBJECT-TYPE 502 SYNTAX InterfaceIndex 503 MAX-ACCESS read-create 504 STATUS current 505 DESCRIPTION 506 "This value indicates the maximum unreservable bandwidth for 507 class type 0." 508 DEFVAL { 0 } 509 ::= { mplsDsTeIfClassTypeEntry 2 } 511 mplsDsTeIfClassTypeOneMaxResBw OBJECT-TYPE 512 SYNTAX InterfaceIndex 513 MAX-ACCESS read-create 514 STATUS current 515 DESCRIPTION 516 "This value indicates the maximum reservable bandwidth for 517 class type 1." 518 DEFVAL { 0 } 519 ::= { mplsDsTeIfClassTypeEntry 3 } 521 mplsDsTeIfClassTypeOneUnresBw OBJECT-TYPE 522 SYNTAX InterfaceIndex 523 MAX-ACCESS read-create 524 STATUS current 525 DESCRIPTION 526 "This value indicates the maximum unreservable bandwidth for 527 class type 1." 528 DEFVAL { 0 } 529 ::= { mplsDsTeIfClassTypeEntry 4 } 531 mplsDsTeIfClassTypeTwoMaxResBw OBJECT-TYPE 532 SYNTAX InterfaceIndex 533 MAX-ACCESS read-create 534 STATUS current 535 DESCRIPTION 536 "This value indicates the maximum reservable bandwidth for 537 class type 2." 539 DEFVAL { 0 } 540 ::= { mplsDsTeIfClassTypeEntry 5 } 542 mplsDsTeIfClassTypeTwoUnresBw OBJECT-TYPE 543 SYNTAX InterfaceIndex 544 MAX-ACCESS read-create 545 STATUS current 546 DESCRIPTION 547 "This value indicates the maximum unreservable bandwidth for 548 class type 2." 549 DEFVAL { 0 } 550 ::= { mplsDsTeIfClassTypeEntry 6 } 552 mplsDsTeIfClassTypeThreeMaxResBw OBJECT-TYPE 553 SYNTAX InterfaceIndex 554 MAX-ACCESS read-create 555 STATUS current 556 DESCRIPTION 557 "This value indicates the maximum reservable bandwidth for class 558 type 3." 559 DEFVAL { 0 } 560 ::= { mplsDsTeIfClassTypeEntry 7 } 562 mplsDsTeIfClassTypeThreeUnresBw OBJECT-TYPE 563 SYNTAX InterfaceIndex 564 MAX-ACCESS read-create 565 STATUS current 566 DESCRIPTION 567 "This value indicates the maximum unreservable bandwidth for 568 class type 3." 569 DEFVAL { 0 } 570 ::= { mplsDsTeIfClassTypeEntry 8 } 572 -- LSP Table 574 mplsDsTeLspTable OBJECT-TYPE 575 SYNTAX SEQUENCE OF MplsDsTeLspEntry 576 MAX-ACCESS not-accessible 577 STATUS current 578 DESCRIPTION 579 "This table indicates which DiffServ-Aware TE class particular 580 LSPs. This table 'extends' the mplsXCTable, as it uses the 581 same indexing scheme utilized therein." 582 ::= { mplsDsTeObjects 4 } 584 mplsDsTeLspEntry OBJECT-TYPE 585 SYNTAX MplsDsTeLspEntry 586 MAX-ACCESS not-accessible 587 STATUS current 588 DESCRIPTION 589 "An entry in this table is created by an LSR for every LSP 590 capable of supporting MPLS DiffServ-Aware Traffic 591 Engineering. Specifically, an entry in this table must 592 correspond to an entry in the mplsXCTable from the 593 MPLS-LSR-MIB [MPLS-LSR-MIB]." 594 INDEX { mplsDsTeLspXCIndex, mplsDsTeLspInSegmentIfIndex, 595 mplsDsTeLspInSegmentLabel, mplsDsTeLspOutSegmentIndex } 596 ::= { mplsDsTeLspTable 1 } 598 MplsDsTeIfClassTypeEntry ::= SEQUENCE { 599 mplsDsTeLspXCIndex Integer32, 600 mplsDsTeLspInSegmentIfIndex InterfaceIndex, 601 mplsDsTeLspInSegmentLabel MplsLabel, 602 mplsDsTeLspOutSegmentIndex Integer32, 603 mplsDsTeLspClassType Integer32, 604 mplsDsTeLspAdminStatus INTEGER, 605 mplsDsTeLspOperStatus INTEGER, 606 mplsDsTeLspRowStatus RowStatus, 607 mplsDsTeLspStorageType StorageType 608 } 610 mplsDsTeLspXCIndex OBJECT-TYPE 611 SYNTAX Integer32 (0..2147483647) 612 MAX-ACCESS read-create 613 STATUS current 614 DESCRIPTION 615 "This value indicates the primary index of the LSP which can be 616 found in the MPLS-LSR-MIB's [LSR-MIB] XCTable. The entry MUST 617 exist in the MPLS-LSR-MIB before an entry in this table may be 618 transition into the operStatus of up(1). If the entry is not 619 ready or has not yet been created in the MPLS-LSR-MIB, the 620 operStatus of this value must contain the value notPresent(6) 621 to indicate that this entry will be activated as soon as the 622 entry is available in the MPLS-LSR-MIB." 623 ::= { mplsDsTeLspEntry 1 } 625 mplsDsTeLspInSegmentIfIndex OBJECT-TYPE 626 SYNTAX InterfaceIndex 627 MAX-ACCESS read-create 628 STATUS current 629 DESCRIPTION 630 "This value indicates the secondary index of the LSP which can be 631 found in the MPLS-LSR-MIB's [LSR-MIB] XCTable. The entry MUST 632 exist in the MPLS-LSR-MIB before an entry in this table may be 633 transition into the operStatus of up(1). If the entry is not 634 ready or has not yet been created in the MPLS-LSR-MIB, the 635 operStatus of this value must contain the value notPresent(6) 636 to indicate that this entry will be activated as soon as the 637 entry is available in the MPLS-LSR-MIB." 639 ::= { mplsDsTeLspEntry 2 } 641 mplsDsTeLspInSegmentLabel OBJECT-TYPE 642 SYNTAX MplsLabel 643 MAX-ACCESS read-create 644 STATUS current 645 DESCRIPTION 646 "This value indicates the tertiary index of the LSP which can be 647 found in the MPLS-LSR-MIB's [LSR-MIB] XCTable. The entry MUST 648 exist in the MPLS-LSR-MIB before an entry in this table may be 649 transition into the operStatus of up(1). If the entry is not 650 ready or has not yet been created in the MPLS-LSR-MIB, the 651 operStatus of this value must contain the value notPresent(6) 652 to indicate that this entry will be activated as soon as the 653 entry is available in the MPLS-LSR-MIB." 654 ::= { mplsDsTeLspEntry 3 } 656 mplsDsTeLspOutSegmentIndex OBJECT-TYPE 657 SYNTAX Integer32 (0..2147483647) 658 MAX-ACCESS read-create 659 STATUS current 660 DESCRIPTION 661 "This value indicates the fourth index of the LSP which can be 662 found in the MPLS-LSR-MIB's [LSR-MIB] XCTable. The entry MUST 663 exist in the MPLS-LSR-MIB before an entry in this table may be 664 transition into the operStatus of up(1). If the entry is not 665 ready or has not yet been created in the MPLS-LSR-MIB, the 666 operStatus of this value must contain the value notPresent(6) 667 to indicate that this entry will be activated as soon as the 668 entry is available in the MPLS-LSR-MIB." 669 ::= { mplsDsTeLspEntry 4 } 671 mplsDsTeLspClassType OBJECT-TYPE 672 SYNTAX Integer32 (0..3) 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION 676 "This object indicates the DiffServ-Aware TE class to which 677 this LSP has been assigned." 678 ::= { mplsDsTeLspEntry 5 } 680 mplsDsTeLspAdminStatus OBJECT-TYPE 681 SYNTAX INTEGER { enabled(1), -- enables the feature 682 disabled(2), -- disables the feature 683 } 684 MAX-ACCESS read-create 685 STATUS current 686 DESCRIPTION 687 "This object is used to indicate the desired DiffServ-Aware 688 TE functionality status (i.e.: enable/disable) on this LSP." 690 ::= { mplsDsTeLspEntry 6 } 692 mplsDsTeLspOperStatus OBJECT-TYPE 693 SYNTAX INTEGER { up(1), -- ready to pass packets 694 down(2), 695 testing(3), -- in some test mode 696 unknown(4), -- status cannot be determined 697 dormant(5), 698 notPresent(6), -- some component is missing 699 lowerLayerDown(7) -- down due to the state of 700 -- lower layer interfaces 702 } 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "This object is used to indicate the actual status of the 707 DiffServ-Aware TE feature on this LSP." 708 ::= { mplsDsTeLspEntry 7 } 710 mplsDsTeLspRowStatus OBJECT-TYPE 711 SYNTAX RowStatus 712 MAX-ACCESS read-create 713 STATUS current 714 DESCRIPTION 715 "The row status for a row in this table." 716 ::= { mplsDsTeLspEntry 8 } 718 mplsDsTeLspStorageType OBJECT-TYPE 719 SYNTAX StorageType 720 MAX-ACCESS read-create 721 STATUS current 722 DESCRIPTION 723 "The storage type for this entry." 724 ::= { mplsDsTeLspEntry 9 } 726 -- Tunnel Table (Applies only to tunnel heads at this LSR) 728 mplsDsTeTunTable OBJECT-TYPE 729 SYNTAX SEQUENCE OF MplsDsTeTunEntry 730 MAX-ACCESS not-accessible 731 STATUS current 732 DESCRIPTION 733 "This table indicates which DiffServ-Aware TE class particular 734 Traffic Engineering tunnels have been assigned to. This table 735 'extends' the mplsTunnelTable from the MPLS-TE-MIB[TEMIB], as 736 it uses the same indexing scheme utilized therein." 737 ::= { mplsDsTeObjects 5 } 739 mplsDsTeTunEntry OBJECT-TYPE 740 SYNTAX MplsDsTeTunEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "An entry in this table is created by an LSR for every traffic 745 engineering tunnel instance capable of supporting MPLS 746 DiffServ-Aware Traffic Engineering. We must include all 747 indexes here to indicate which instances of tunnels are in 748 which bandwidth class, as it is entirely possible (and 749 sometimes desirable) to include different instances in 750 different classes." 751 INDEX { mplsDsTeTunTunnelIndex, mplsDsTeTunTunnelInstance, 752 mplsDsTeTunTunnelIngressLSRId, mplsDsTeTunTunnelEgressLSRId } 753 ::= { mplsDsTeTunTable 1 } 755 MplsDsTeTunEntry ::= SEQUENCE { 756 mplsDsTeTunTunnelIndex MplsTunnelIndex, 757 mplsDsTeTunTunnelInstance MplsTunnelInstanceIndex, 758 mplsDsTeTunTunnelIngressLSRId MplsLsrId, 759 mplsDsTeTunTunnelEgressLSRId MplsLsrId, 760 mplsDsTeTunClassType Integer32, 761 mplsDsTeTunAdminStatus INTEGER, 762 mplsDsTeTunOperStatus INTEGER, 763 mplsDsTeTunRowStatus RowStatus, 764 mplsDsTeTunStorageType StorageType 765 } 767 mplsDsTeTunTunnelIndex OBJECT-TYPE 768 SYNTAX MplsTunnelIndex 769 MAX-ACCESS read-create 770 STATUS current 771 DESCRIPTION 772 "This value indicates the primary index of the tunnel entry 773 which can be found in the MPLS-TE-MIB's [TEMIB] 774 mplsTunnelTable. The entry MUST exist in the MPLS-TE-MIB before 775 an entry in this table may be transition into the operStatus of 776 up(1). If the entry is not ready or has not yet been created in 777 the MPLS-TE-MIB, the operStatus of this value must contain the 778 value notPresent(6) to indicate that this entry will be 779 activated as soon as the entry is available in the MPLS-TE-MIB." 780 ::= { mplsDsTeTunEntry 1 } 782 mplsDsTeTunTunnelInstance OBJECT-TYPE 783 SYNTAX MplsTunnelInstanceIndex 784 MAX-ACCESS read-create 785 STATUS current 786 DESCRIPTION 787 "This value indicates the secondary index of the tunnel entry 788 which can be found in the MPLS-TE-MIB's [TEMIB] 789 mplsTunnelTable. The entry MUST exist in the MPLS-TE-MIB before 790 an entry in this table may be transition into the operStatus of 791 up(1). If the entry is not ready or has not yet been created in 792 the MPLS-TE-MIB, the operStatus of this value must contain the 793 value notPresent(6) to indicate that this entry will be 794 activated as soon as the entry is available in the 795 MPLS-TE-MIB." 796 ::= { mplsDsTeTunEntry 2 } 798 mplsDsTeTunTunnelIngressLSRId OBJECT-TYPE 799 SYNTAX MplsLsrId 800 MAX-ACCESS read-create 801 STATUS current 802 DESCRIPTION 803 "This value indicates the third index of the tunnel entry 804 which can be found in the MPLS-TE-MIB's [TEMIB] 805 mplsTunnelTable. The entry MUST exist in the MPLS-TE-MIB before 806 an entry in this table may be transition into the operStatus of 807 up(1). If the entry is not ready or has not yet been created in 808 the MPLS-TE-MIB, the operStatus of this value must contain the 809 value notPresent(6) to indicate that this entry will be 810 activated as soon as the entry is available in the 811 MPLS-TE-MIB." 812 ::= { mplsDsTeTunEntry 3 } 814 mplsDsTeTunTunnelEgressLSRId OBJECT-TYPE 815 SYNTAX MplsLsrId 816 MAX-ACCESS read-create 817 STATUS current 818 DESCRIPTION 819 "This value indicates the fourth index of the tunnel entry 820 which can be found in the MPLS-TE-MIB's [TEMIB] 821 mplsTunnelTable. The entry MUST exist in the MPLS-TE-MIB before 822 an entry in this table may be transition into the operStatus of 823 up(1). If the entry is not ready or has not yet been created in 824 the MPLS-TE-MIB, the operStatus of this value must contain the 825 value notPresent(6) to indicate that this entry will be 826 activated as soon as the entry is available in the 827 MPLS-TE-MIB." 828 ::= { mplsDsTeTunEntry 4 } 830 mplsDsTeLspClassType OBJECT-TYPE 831 SYNTAX Integer32 (0..3) 832 MAX-ACCESS read-only 833 STATUS current 834 DESCRIPTION 835 "This object indicates the DiffServ-Aware TE class to which this 836 LSP has been assigned." 837 ::= { mplsDsTeTunEntry 5 } 839 mplsDsTeLspAdminStatus OBJECT-TYPE 840 SYNTAX INTEGER { enabled(1), -- enables the feature 841 disabled(2), -- disables the feature 842 } 843 MAX-ACCESS read-create 844 STATUS current 845 DESCRIPTION 846 "This object is used to indicate the desired DiffServ-Aware 847 TE functionality status (i.e.: enable/disable) on this LSP." 848 ::= { mplsDsTeTunEntry 6 } 850 mplsDsTeLspOperStatus OBJECT-TYPE 851 SYNTAX INTEGER { up(1), -- ready to pass packets 852 down(2), 853 testing(3), -- in some test mode 854 unknown(4), -- status cannot be determined 855 dormant(5), 856 notPresent(6), -- some component is missing 857 lowerLayerDown(7) -- down due to the state of 858 -- lower layer interfaces 859 } 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "This object is used to indicate the actual status of the 864 DiffServ-Aware TE feature on this LSP." 865 ::= { mplsDsTeTunEntry 7 } 867 mplsDsTeLspRowStatus OBJECT-TYPE 868 SYNTAX RowStatus 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "The row status for a row in this table." 873 ::= { mplsDsTeTunEntry 8 } 875 mplsDsTeLspStorageType OBJECT-TYPE 876 SYNTAX StorageType 877 MAX-ACCESS read-create 878 STATUS current 879 DESCRIPTION 880 "The storage type for this entry." 881 ::= { mplsDsTeTunEntry 9 } 883 -- Notifications 885 -- TBD. 887 -- Conformance Statement 889 mplsDsTeGroups 890 OBJECT IDENTIFIER ::= { mplsDsTeConformance 1 } 892 mplsDsTeCompliances 893 OBJECT IDENTIFIER ::= { mplsDsTeConformance 2 } 895 -- Module Compliance 897 mplsDsTeModuleCompliance MODULE-COMPLIANCE 898 STATUS current 899 DESCRIPTION 900 "Compliance statement for agents that support MPLS Diff-Serv 901 Aware Traffic Engineering." 902 MODULE -- this module 904 -- The mandatory groups have to be implemented 905 -- by all LSRs supporting MPLS DS TE. However, 906 -- they may all be supported 907 -- as read-only objects in the case where 908 -- configuration through this MIB is unsupported. 910 MANDATORY-GROUPS { mplsDsTeScalarGroup, 911 mplsDsTeIfGroup, 912 mplsDsTeIfClassGroup, 913 mplsDsTeLspGroup, 914 mplsDsTeTunGroup 915 } 917 ::= { mplsDsTeCompliances 1 } 919 -- Units of conformance. 921 mplsDsTeScalarGroup OBJECT-GROUP 922 OBJECTS { mplsDsTeNumConfIfs } 924 STATUS current 925 DESCRIPTION 926 "Collection of scalar objects required for DS TE 927 management." 928 ::= { mplsDsTeGroups 1 } 930 mplsDsTeIfGroup OBJECT-GROUP 931 OBJECTS { mplsDsTeIfConfIndex, 932 MplsDsTeIfMaxAggrResBw, 933 mplsDsTeIfMaxAddrUnresBw, 934 mplsDsTeIfAggrResBwUsed, 935 mplsDsTeIfAggrUnresBwUsed 936 MplsDsTeIfDsTeAdminStatus, 937 MplsDsTeIfDsTeOperStatus, 938 MplsDsTeIfRowStatus, 939 mplsDsTeIfConfStorageType 940 } 942 STATUS current 943 DESCRIPTION 944 "Collection of objects needed for MPLS DS TE interface 945 management." 946 ::= { mplsDsTeGroups 2 } 948 mplsDsTeIfClassGroup OBJECT-GROUP 949 OBJECTS { mplsDsTeIfClassTypeZeroMaxResBw, 950 mplsDsTeIfClassTypeZeroUnresBw, 951 mplsDsTeIfClassTypeOneMaxResBw, 952 mplsDsTeIfClassTypeOneUnresBw, 953 mplsDsTeIfClassTypeTwoMaxResBw, 954 mplsDsTeIfClassTypeTwoUnresBw, 955 mplsDsTeIfClassTypeThreeMaxResBw, 956 mplsDsTeIfClassTypeThreeUnresBw 957 } 958 STATUS current 959 DESCRIPTION 960 "Collection of objects needed for MPLS DS TE interface 961 class management." 962 ::= { mplsDsTeGroups 3 } 964 mplsDsTeLspGroup OBJECT-GROUP 965 OBJECTS { mplsDsTeLspXCIndex, 966 mplsDsTeLspInSegmentIfIndex, 967 mplsDsTeLspInSegmentLabel, 968 mplsDsTeLspOutSegmentIndex, 969 mplsDsTeLspClassType, 970 mplsDsTeLspAdminStatus, 971 mplsDsTeLspOperStatus, 972 mplsDsTeLspRowStatus, 973 mplsDsTeLspStorageType 974 } 975 STATUS current 976 DESCRIPTION 977 "Collection of objects needed for MPLS DS TE LSP management." 978 ::= { mplsDsTeGroups 4 } 980 mplsDsTeTunGroup OBJECT-GROUP 981 OBJECTS { mplsDsTeTunTunnelIndex, 982 mplsDsTeTunTunnelInstance, 983 mplsDsTeTunTunnelIngressLSRId, 984 mplsDsTeTunTunnelEgressLSRId, 985 mplsDsTeTunClassType, 986 mplsDsTeTunAdminStatus, 987 mplsDsTeTunOperStatus, 988 mplsDsTeTunRowStatus, 989 mplsDsTeTunStorageType 990 } 991 STATUS current 992 DESCRIPTION 993 "Collection of objects needed for MPLS DS TE Tunnel management." 994 ::= { mplsDsTeGroups 5 } 995 -- End of MPLS-DS-TE-MIB 997 END 999 12.0 Acknowledgments 1001 TBD. 1003 13.0 References 1005 [DSTEREQS] Le Faucheur, F., Nadeau, T., Chiu , A., Townsend , 1006 W., Skalecki, D., "Requirements for support of 1007 Diff-Serv-aware MPLS Traffic Engineering", Internet 1008 Draft , November 2000. 1010 [DSTEEXTS] Le Faucheur, F., Nadeau, T., Chiu , A., Townsend , 1011 W., Skalecki, D., "Extensions to RSVP-TE and CR-LDP 1012 for support of Diff-Serv-aware MPLS Traffic 1013 Engineering", Internet Draft 1014 , November 2000. 1016 [DSTEISIS] Le Faucheur, F., Nadeau, T., Chiu , A., Townsend , 1017 W., Skalecki, D., "Extensions to ISIS for support of 1018 Diff-Serv-aware MPLS Traffic Engineering", Internet 1019 Draft , November 2000. 1021 [DSTEOSPF] Le Faucheur, F., Nadeau, T., Chiu , A., Townsend , 1022 W., Skalecki, D., "Extensions to OSPF for support of 1023 Diff-Serv-aware MPLS Traffic Engineering ", Internet 1024 Draft , November 2000. 1026 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 1027 "Multiprotocol Label Switching Architecture", RFC2702, 1028 September 1999. 1030 [LSRMIB] Srinivasan, C., Viswanathan, A. and T. 1032 Nadeau, "MPLS Label Switch Router Management 1033 Information Base Using SMIv2", Internet 1034 Draft , July 1035 2000. 1037 [TEMIB] Srinivasan, C., Viswanathan, A. and T. 1038 Nadeau, "MPLS Traffic Engineering Management 1039 Information Base Using SMIv2", Internet 1040 Draft , November 1041 2000. 1043 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 1044 RFC 1700, October 1994. See also: 1045 http://www.isi.edu/in-notes/iana/assignments/smi- 1046 numbers 1048 [IANAFamily] Internet Assigned Numbers Authority (IANA), ADDRESS 1049 FAMILY NUMBERS,(http://www.isi.edu/in- 1050 notes/iana/assignements/address-family-numbers), 1051 for MIB see: 1052 ftp://ftp.isi.edu/mib/ianaaddressfamilynumbers.mib 1054 [SNMPArch] Harrington, D., Presuhn, R., and B. Wijnen, "An 1055 Architecture for Describing SNMP Management 1056 Frameworks", RFC 2271, January 1998. 1058 [SMIv1] Rose, M., and K. McCloghrie, "Structure and 1059 Identification of Management Information for 1060 TCP/IP-based Internets", RFC 1155, May 1990. 1062 [SNMPv1MIBDef]Rose, M., and K. McCloghrie, "Concise MIB 1063 Definitions", RFC 1212, March 1991. 1065 [SNMPv1Traps] M. Rose, "A Convention for Defining Traps for use 1066 with the SNMP", RFC 1215, March 1991. 1068 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1069 "Message Processing and Dispatching for the Simple 1070 Network Management Protocol (SNMP)", RFC 2572, 1071 April 1999. 1073 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 1074 Model (USM) for version 3 of the Simple Network 1075 Management Protocol (SNMPv3)", RFC 2574, April 1076 1999. 1078 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. 1079 Waldbusser, "Protocol Operations for Version 2 of 1080 the Simple Network Management Protocol (SNMPv2)", 1081 RFC 1905, January 1996. 1083 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1084 Applications", RFC 2573, April 1999. 1086 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 1087 based Access Control Model (VACM) for the Simple 1088 Network Management Protocol (SNMP)", RFC 2575, 1089 April 1999. 1091 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1092 "Introduction to Version 3 of the Internet-standard 1093 Network Management Framework", RFC 2570, April 1094 1999. 1096 [SMIv2] Case, J., McCloghrie, K., Rose, M., and S. 1097 Waldbusser, "Structure of Management Information 1098 for Version 2 of the Simple Network Management 1099 Protocol (SNMPv2)", RFC 1902, January 1996. 1101 [SNMPv2TC] Case, J., McCloghrie, K., Rose, M., and S. 1102 Waldbusser, "Textual Conventions for Version 2 of 1103 the Simple Network Management Protocol (SNMPv2)", 1104 RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 1105 January 1996. 1107 [SNMPv2Conf] Case, J., McCloghrie, K., Rose, M., and S. 1108 Waldbusser, "Conformance Statements for Version 2 1109 of the Simple Network Management Protocol 1110 (SNMPv2)", RFC 1904, January 1996. 1112 [SNMPv1] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 1113 "Simple Network Management Protocol", RFC 1157, May 1114 1990. 1116 [SNMPv2c] Case, J., McCloghrie, K., Rose, M., and S. 1117 Waldbusser, "Introduction to Community-based 1118 SNMPv2", RFC 1901, January 1996. 1120 [SNMPv2TM] Case, J., McCloghrie, K., Rose, M., and S. 1121 Waldbusser, "Transport Mappings for Version 2 of 1122 the Simple Network Management Protocol (SNMPv2)", 1123 RFC 1906, January 1996. 1125 [SNMPv3MP] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1126 "Message Processing and Dispatching for the Simple 1127 Network Management Protocol (SNMP)", RFC 2272, 1128 January 1998. 1130 [SNMPv3USM] Blumenthal, U., and B. Wijnen, "User-based Security 1131 Model (USM) for version 3 of the Simple Network 1132 Management Protocol (SNMPv3)", RFC 2574, April 1133 1999. 1135 [SNMPv2PO] Case, J., McCloghrie, K., Rose, M., and S. 1136 Waldbusser, "Protocol Operations for Version 2 of 1137 the Simple Network Management Protocol (SNMPv2)", 1138 RFC 1905, January 1996. 1140 [SNMPv3App] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 1141 Applications", RFC 2273, January 1998. 1143 [SNMPv3VACM] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 1144 based Access Control Model (VACM) for the Simple 1145 Network Management Protocol (SNMP)", RFC 2575, 1146 April 1999. 1148 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 1149 for the Internet Protocol", RFC 2401, November 1150 1998. 1152 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 1153 Group MIB using SMIv2", RFC 2233, Nov. 1997 1155 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 1156 Requirement Levels", BCP 14, RFC 2119, March 1997. 1158 14.0 Authors' Addresses 1160 Thomas D. Nadeau 1161 Cisco Systems, Inc. 1162 250 Apollo Drive 1163 Chelmsford, MA 01824 1164 Phone: +1-978-244-3051 1165 Email: tnadeau@cisco.com 1167 Francois Le Faucheur 1168 Cisco Systems, Inc. 1169 Petra B - Les Lucioles - 291, rue Albert Caquot - 06560 Valbonne - France 1170 Phone: +33 4 92 96 75 64 1171 Email: flefauch@cisco.com 1173 Angela Chiu 1174 Celion Networks 1175 1 Sheila Drive, Suite 2 1176 Tinton Falls, NJ 07724 1177 Phone: 732 747 9987 tel 1178 Email: angela.chiu@celion.com 1179 William Townsend 1180 Tenor Networks 1181 100 Nagog Park 1182 Acton, MA 01720 1183 Phone: +1-978-264-4900 1184 Email: btownsend@tenornetworks.com 1186 Darek Skalecki 1187 Nortel Networks 1188 3500 Carling Ave, 1189 Nepean K2H 8E9 1190 Phone: +1-613-765-2252 1191 Email: dareks@nortelnetworks.com 1193 Martin Tatham 1194 British Telecom 1195 BT Adastal Park, 1196 Martlesham Heath, 1197 Ipswich, IP5 3RE 1198 UK 1199 Tel: +44 1473 606349 1200 Fax: +44 1473 606727 1201 Email: martin.tatham@bt.com 1203 15.0 Full Copyright Statement 1205 Copyright (C) The Internet Society (2000). All Rights Reserved. 1206 This document and translations of it may be copied and furnished to 1207 others, and derivative works that comment on or otherwise explain it 1208 or assist in its implementation may be prepared, copied, published 1209 and distributed, in whole or in part, without restriction of any 1210 kind, provided that the above copyright notice and this paragraph 1211 are included on all such copies and derivative works. However, this 1212 document itself may not be modified in any way, such as by removing 1213 the copyright notice or references to the Internet Society or other 1214 Internet organizations, except as needed for the purpose of 1215 developing Internet standards in which case the procedures for 1216 copyrights defined in the Internet Standards process must be followed, 1217 or as required to translate it into languages other than English. 1219 The limited permissions granted above are perpetual and will not be 1220 revoked by the Internet Society or its successors or assigns. This 1221 document and the information contained herein is provided on an "AS 1222 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 1223 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 1224 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 1225 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 1226 OR FITNESS FOR A PARTICULAR PURPOSE.