idnits 2.17.1 draft-ietf-mpls-lc-if-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 18. -- Found old boilerplate from RFC 3978, Section 5.5 on line 875. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 1058. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 1065. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 1071. ** The document seems to lack an RFC 3978 Section 5.4 (updated by RFC 4748) Copyright Line. ** The document seems to lack an RFC 3978 Section 5.4 Reference to BCP 78. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to 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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: It should be noted that the label partition model utilized by the authors of this document reflects widespread implementation, and is seen by the MPLS working group as sufficiently flexible to meet the operational needs, even if it is more restrictive than [RFC3035] allows. To this end, we have limited the control and unlabeled VPI and VCI to single values. It should be noted mplsLcAtmStdUnlabTrafVci and mplsLcAtmStdCtrlVci MUST not be equal, nor should mplsLcAtmStdCtrlVpi or mplsLcAtmStdUnlabTrafVpi be equal. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: It should be noted that even though the architecture as described in [RFC3034] calls for supporting mixed labeled and unlabeled traffic, this MIB does not support that as this capability does not seem to be used operationally. It should be noted that the DLCI ranges represented by mplsLcFrStdTrafficMinDlci and mplsLcFrStdTrafficMaxDlci mplsLcFrStdCtrlMinDlci and mplsLcFrStdCtrlMaxDlci MUST not overlap. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: mplsLcAtmStdIfConfRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This is object is used to create and delete entries in this table. When configuring entries in this table, the corresponding ifEntry and mplsInterfaceConfEntry MUST exist before hand. If an entry is attempted to be created by a manager for a corresponding mplsInterfaceConfEntry that does not support LC-ATM, the agent MUST return an inconsistentValue error. If this table is implemented read-only, then the agent must set this object to active(1) when this row is made active. If this table is implemented writable, then an agent MUST not allow modification to its objects once this value is set to active(1) except mplsLcAtmStdIfConfRowStatus and mplsLcAtmStdIfConfStorageType." ::= { mplsLcAtmStdInterfaceConfEntry 8 } == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This is object is used to create and delete entries in this table. When configuring entries in this table, the corresponding ifEntry and mplsInterfaceConfEntry MUST exist before hand. If an entry is attempted to be created by a manager for a corresponding mplsInterfaceConfEntry that does not support LC-FR, the agent MUST return an inconsistentValue error. If this table is implemented read-only, then the agent must set this object to active(1) when this row is made active. If this table is implemented writable, then an agent MUST not allow modification to its objects once this value is set to active(1) except mplsLcFrStdInterfaceConfRowStatus and mplsLcFrStdInterfaceConfStorageType." ::= { mplsLcFrStdInterfaceConfEntry 5 } -- 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 (October 2005) is 6768 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) -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) -- Duplicate reference: draft-ietf-mpls-lc-if-mib, mentioned in 'RFC3410', was also mentioned in 'RFC2514'. Summary: 4 errors (**), 0 flaws (~~), 6 warnings (==), 9 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 Subrahmanya Hegde 3 Expires: April 2006 Cisco Systems, Inc. 5 October 2005 7 Multiprotocol Label Switching (MPLS) Label-Controlled ATM 8 and Frame-Relay Management Interface Definition 10 draft-ietf-mpls-lc-if-mib-08.txt 12 Status of this Memo 14 By submitting this Internet-Draft, each author represents that 15 any applicable patent or other IPR claims of which he or she is 16 aware have been or will be disclosed, and any of which he or she 17 becomes aware will be disclosed, in accordance with Section 6 of 18 BCP 79. 20 Internet-Drafts are working documents of the Internet Engineering 21 Task Force (IETF), its areas, and its working groups. Note that other 22 groups may also distribute working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/1id-abstracts.html 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html. 35 Abstract 37 This memo defines two MIB modules and corresponding MIB Object 38 Definitions that describe how label switching controlled 39 Frame-Relay and ATM interfaces can be managed given the 40 interface stacking as defined in the MPLS-LSR-STD-MIB and 41 MPLS-TE-STD-MIB. 43 Table of Contents 44 1. Introduction .............................................. 3 45 2. Terminology ............................................... 3 46 3. The SNMP Management Framework ............................. 3 47 4. Interface Stacking of LC-ATM and LC-FR .................... 5 48 5. Structure of the MPLS-LC-ATM-STD-MIB module ............... 14 49 6. Structure of the MPLS-LC-FR-STD-MIB module ................ 14 50 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 52 7. MPLS Label Controlled ATM MIB Definitions ................. 13 53 8. MPLS Label Controlled Frame Relay MIB Definitions ......... 15 54 9. Authors' Addresses ........................................ 54 55 10. Full Copyright Statement................................... 55 56 11. Acknowledgments............................................ 52 57 12. Security Considerations ................................... 51 58 13. IANA Considerations........................................ 55 59 14. References ................................................ 52 60 14.1 Normative References ..................................... 52 61 14.2 Informative References ................................... 53 62 15. Intellectual Property...................................... 55 64 1. Introduction 66 This memo defines how label switching controlled Frame-Relay 67 [RFC3034] and ATM [RFC3035] interfaces can be realized given 68 the interface stacking as defined in the MPLS-LSR-STD [RFC3813] 69 and MPLS-TE-STD [RFC3812] MIBs. This document also contains a 70 MIB module that sparsely extends the MPLS-LSR-STD MIB's 71 mplsInterfaceConfTable in such a way as to identify which 72 MPLS-type interfaces have LC-ATM or LC-FR capabilities. 73 Comments should be made directly to the MPLS mailing list at 74 mpls@uu.net. 76 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 77 NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and 78 "OPTIONAL" in this document are to be interpreted as described in 79 RFC 2119, reference [RFC2119]. 81 2. Terminology 83 This document uses terminology from the document describing the 84 MPLS architecture [RFC3031], as well as RFC3035 and RFC3034. 85 Specifically, the following terms will be used in this document. 87 LC-FR RFC3034 defines a label switching controlled Frame Relay 88 (LC-FR) interface a Frame-Relay interface controlled by the 89 label switching control component. Packets traversing 90 such an interface carry labels in the DLCI field 92 LC-ATM RFC3035 defines a label switching controlled ATM (LC-ATM) 93 interface as an ATM interface controlled by the label 94 switching control component. When a packet traversing such 95 an interface is received, it is treated as a labeled packet. 96 The packet's top label is inferred either from the contents 97 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 99 of the VCI field or the combined contents of the VPI and VCI 100 fields. Any two LDP peers which are connected via an LC-ATM 101 interface will use LDP negotiations to determine which of 102 these cases is applicable to that interface. 103 Static configuration of labels is also possible. 105 When LDP is used to distribute labels for use on label-controlled 106 interfaces, label configuration information may be available in the 107 MPLS-LDP-ATM-STD-MIB [RFC3815] when LC-ATM interfaces are used, or 108 the MPLS-LDP-FRAME-RELAY-STD-MIB [RFC3815] when LC-FR interfaces 109 are used. Specifically, 111 3. The SNMP Management Framework 113 For a detailed overview of the documents that describe the current 114 Internet-Standard Management Framework, please refer to section 7 of 115 RFC 3410 [RFC3410]. 117 Managed objects are accessed via a virtual information store, termed 118 the Management Information Base or MIB. MIB objects are generally 119 accessed through the Simple Network Management Protocol (SNMP). 120 Objects in the MIB are defined using the mechanisms defined in the 121 Structure of Management Information (SMI). This memo specifies a MIB 122 module that is compliant to the SMIv2, which is described in STD 58, 123 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 124 [RFC2580]. 126 4. Interface Stacking of LC-ATM 128 Since LC-ATM interfaces [RFC2863] can carry labeled MPLS 129 traffic, they too are considered MPLS subinterfaces with 130 ifType = mpls(166). They differ slightly in their capability 131 from a packet-oriented MPLS interface in that they may 132 carry ATM or Frame-Relay encapsulated traffic. It is 133 thus beneficial to identify them as such. To identify 134 them as such, two tables are defined which extend the 135 MPLS-LSR-STD MIB's mplsInterfaceTable (see section 5 for 136 LC-ATM or 6 for LC-FR). 138 5. Structure of the MPLS-LC-ATM-STD-MIB module 140 The MPLS-LC-ATM-STD-MIB module is structured simply 141 as a table of entries which sparesely extend those 142 found in the interfaces table. In particular, the 143 entries in the mplsLcAtmStdInterfaceConfTable 144 extend those interfaces capable of supporting 145 MPLS, as is defined in [RFC3813] to include those 146 entries which also support LC-ATM (and their unique 147 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 149 attributes). Therefore, the module can be 150 visualized as follows. Note that the ifTable 151 comes from [RFC2863], mplsInterfaceTable from 152 [RFC3813] and mplsLcAtmStdInterfaceConfTable from 153 the MPLS-LC-ATM-STD-MIB module described below. 155 ifTable mplsInterfaceTable mplsLcAtmStdInterfaceConfTable 156 .1 157 .2 .2 158 .3 159 .4 .4 .4 160 .5 162 In the example shown above, five interfaces exist on the 163 device in question. Of those interfaces, those with 164 ifIndex = .2 and .4 are of ifType = mpls(166) indicating 165 that they are capable of MPLS. Of those two, the entry 166 with index .4 is capable of MPLS LC-ATM operations. 168 It should be noted that the label partition model 169 utilized by the authors of this document reflects widespread 170 implementation, and is seen by the MPLS working group as 171 sufficiently flexible to meet the operational needs, even 172 if it is more restrictive than [RFC3035] allows. To this 173 end, we have limited the control and unlabeled VPI and 174 VCI to single values. It should be noted 175 mplsLcAtmStdUnlabTrafVci and mplsLcAtmStdCtrlVci MUST 176 not be equal, nor should mplsLcAtmStdCtrlVpi or 177 mplsLcAtmStdUnlabTrafVpi be equal. 179 6. Structure of the MPLS-LC-FR-STD-MIB module 181 The MPLS-LC-FR-STD-MIB module is structured simply 182 as a table of entries which sparesely extend those 183 found in the interfaces table. In particular, the 184 entries in the mplsLcFrStdInterfaceConfTable 185 extend those interfaces capable of supporting 186 MPLS, as is defined in [RFC3813] to include those 187 entries which also support LC-Frame Relay (and their 188 unique attributes). Therefore, the module can be 189 visualized as follows. Note that the ifTable 190 comes from [RFC2863], mplsInterfaceTable from 191 [RFC3813] and mplsLcAtmStdInterfaceConfTable from 192 the MPLS-LC-FR-STD-MIB module described below. 194 ifTable mplsInterfaceTable mplsLcFrStdInterfaceConfTable 195 .1 196 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 198 .2 .2 199 .3 200 .4 .4 .4 201 .5 203 In the example shown above, five interfaces exist on the 204 device in question. Of those interfaces, those with 205 ifIndex = .2 and .4 are of ifType = mpls(166) indicating 206 that they are capable of MPLS. Of those two, the entry 207 with index .4 is capable of MPLS LC-Frame Relay operations. 209 It should be noted that even though the architecture as 210 described in [RFC3034] calls for supporting mixed labeled 211 and unlabeled traffic, this MIB does not support that 212 as this capability does not seem to be used operationally. 213 It should be noted that the DLCI ranges represented by 214 mplsLcFrStdTrafficMinDlci and mplsLcFrStdTrafficMaxDlci 215 mplsLcFrStdCtrlMinDlci and mplsLcFrStdCtrlMaxDlci MUST 216 not overlap. 218 7. MPLS Label Controlled ATM MIB Definitions 220 The following MIB module imports from [RFC2514], 221 [RFC3811], [RFC3813]. 223 MPLS-LC-ATM-STD-MIB DEFINITIONS ::= BEGIN 224 IMPORTS 225 MODULE-IDENTITY, OBJECT-TYPE 226 FROM SNMPv2-SMI 227 MODULE-COMPLIANCE, OBJECT-GROUP 228 FROM SNMPv2-CONF 229 RowStatus, StorageType, TruthValue 230 FROM SNMPv2-TC 231 AtmVpIdentifier 232 FROM ATM-TC-MIB 233 mplsStdMIB, MplsAtmVcIdentifier 234 FROM MPLS-TC-STD-MIB 235 mplsInterfaceIndex 236 FROM MPLS-LSR-STD-MIB 237 ; 239 mplsLcAtmStdMIB MODULE-IDENTITY 240 LAST-UPDATED "200506171200Z" -- 17 June 2005 12:00:00 GMT 241 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 242 CONTACT-INFO 243 " Thomas D. Nadeau 244 Postal: Cisco Systems, Inc. 245 250 Apollo Drive 247 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 249 Chelmsford, MA 01824 250 Tel: +1-978-244-3051 251 Email: tnadeau@cisco.com 253 Subrahmanya Hegde 254 Postal: Cisco Systems, Inc. 255 225 East Tazman Drive 256 Tel: +1-408-525-6562 257 Email: subrah@cisco.com 258 General comments should be sent to mpls@uu.net 259 " 260 DESCRIPTION 261 "This MIB module contains managed object definitions for 262 MPLS Label Controlled ATM interfaces as defined in 263 [RFC3035]. 265 Copyright (C) The Internet Society (2005). This 266 version of this MIB module is part of RFCXXXX; see 267 the RFC itself for full legal notices." 268 -- RFC Editor please fill in XXXX 270 -- Revision history. 271 REVISION 272 "200506171200Z" -- 17 June 2005 12:00:00 GMT 273 DESCRIPTION 274 "Initial revision, published as part of RFC XXXX." 275 ::= { mplsStdMIB XXX } -- To Be Assigned by IANA 277 -- Top level components of this MIB module. 279 -- Tables, Scalars, Notifications, Conformance 281 mplsLcAtmStdNotifications OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 0 } 283 mplsLcAtmStdObjects OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 1 } 285 mplsLcAtmStdConformance OBJECT IDENTIFIER ::= { mplsLcAtmStdMIB 2 } 287 -- MPLS LC-ATM Interface Configuration Table. 288 mplsLcAtmStdInterfaceConfTable OBJECT-TYPE 289 SYNTAX SEQUENCE OF MplsLcAtmStdInterfaceConfEntry 290 MAX-ACCESS not-accessible 291 STATUS current 292 DESCRIPTION 293 "This table specifies per-interface MPLS LC-ATM 294 capability and associated information. In particular, 295 this table sparsely extends the MPLS-LSR-STD-MIB's 296 mplsInterfaceConfTable." 297 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 299 ::= { mplsLcAtmStdObjects 1 } 301 mplsLcAtmStdInterfaceConfEntry OBJECT-TYPE 302 SYNTAX MplsLcAtmStdInterfaceConfEntry 303 MAX-ACCESS not-accessible 304 STATUS current 305 DESCRIPTION 306 "An entry in this table is created by an LSR for 307 every interface capable of supporting MPLS LC-ATM. 308 Each entry in this table will exist only if a 309 corresponding entry in ifTable and mplsInterfaceConfTable 310 exist. If the associated entries in ifTable and 311 mplsInterfaceConfTable are deleted, the corresponding 312 entry in this table must also be deleted shortly 313 thereafter. " 314 INDEX { mplsInterfaceIndex } 315 ::= { mplsLcAtmStdInterfaceConfTable 1 } 317 MplsLcAtmStdInterfaceConfEntry ::= SEQUENCE { 318 mplsLcAtmStdCtrlVpi AtmVpIdentifier, 319 mplsLcAtmStdCtrlVci MplsAtmVcIdentifier, 320 mplsLcAtmStdUnlabTrafVpi AtmVpIdentifier, 321 mplsLcAtmStdUnlabTrafVci MplsAtmVcIdentifier, 322 mplsLcAtmStdVcMerge TruthValue, 323 mplsLcAtmVcDirectlyConnected TruthValue, 324 mplsLcAtmLcAtmVPI AtmVpIdentifier, 325 mplsLcAtmStdIfConfRowStatus RowStatus, 326 mplsLcAtmStdIfConfStorageType StorageType 327 } 329 mplsLcAtmStdCtrlVpi OBJECT-TYPE 330 SYNTAX AtmVpIdentifier 331 MAX-ACCESS read-create 332 STATUS current 333 DESCRIPTION 334 "This is the VPI value over which this 335 LSR is willing to accept control traffic on 336 this interface." 337 ::= { mplsLcAtmStdInterfaceConfEntry 1 } 339 mplsLcAtmStdCtrlVci OBJECT-TYPE 340 SYNTAX MplsAtmVcIdentifier 341 MAX-ACCESS read-create 342 STATUS current 343 DESCRIPTION 344 "This is the VCI value over which this 345 LSR is willing to accept control traffic 346 on this interface." 347 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 349 ::= { mplsLcAtmStdInterfaceConfEntry 2 } 351 mplsLcAtmStdUnlabTrafVpi OBJECT-TYPE 352 SYNTAX AtmVpIdentifier 353 MAX-ACCESS read-create 354 STATUS current 355 DESCRIPTION 356 "This is the VPI value over which this 357 LSR is willing to accept unlabeled traffic 358 on this interface." 359 ::= { mplsLcAtmStdInterfaceConfEntry 3 } 361 mplsLcAtmStdUnlabTrafVci OBJECT-TYPE 362 SYNTAX MplsAtmVcIdentifier 363 MAX-ACCESS read-create 364 STATUS current 365 DESCRIPTION 366 "This is the VCI value over which this 367 LSR is willing to accept unlabled traffic 368 on this interface." 369 ::= { mplsLcAtmStdInterfaceConfEntry 4 } 371 mplsLcAtmStdVcMerge OBJECT-TYPE 372 SYNTAX TruthValue 373 MAX-ACCESS read-create 374 STATUS current 375 DESCRIPTION 376 "If set to true(1), indicates that this interface 377 is capabile of ATM VC merge, otherwise it MUST 378 be set to false(2)." 379 DEFVAL { false } 380 ::= { mplsLcAtmStdInterfaceConfEntry 5 } 382 mplsLcAtmVcDirectlyConnected OBJECT-TYPE 383 SYNTAX TruthValue 384 MAX-ACCESS read-create 385 STATUS current 386 DESCRIPTION 387 "This value indicates whether an LC-ATM is directly 388 or indirectly (by means of a VP) connected. If set to 389 true(1), indicates that this interface is directly 390 connected LC-ATM, otherwise it MUST be set to 391 false(2). It should be noted that although 392 it can be intimated from RFC 3057 that multiple 393 VPs maybe used, that in practice only a single 394 one is used, and therefore the authors of 395 this MIB module have chosen to model it as such." 396 DEFVAL { true } 397 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 399 ::= { mplsLcAtmStdInterfaceConfEntry 6 } 401 mplsLcAtmLcAtmVPI OBJECT-TYPE 402 SYNTAX AtmVpIdentifier 403 MAX-ACCESS read-create 404 STATUS current 405 DESCRIPTION 406 "This is the VPI value used for indirectly 407 connected LC-ATM interfaces. For these 408 interfaces, the VPI field is not 409 available to MPLS, and the label MUST be 410 encoded entirely within the VCI field. 411 (see [RFC3035]). If the interface is directly 412 connected, this value MUST be set to zero." 413 DEFVAL { 0 } 414 ::= { mplsLcAtmStdInterfaceConfEntry 7 } 416 mplsLcAtmStdIfConfRowStatus OBJECT-TYPE 417 SYNTAX RowStatus 418 MAX-ACCESS read-create 419 STATUS current 420 DESCRIPTION 421 "This is object is used to create and 422 delete entries in this table. When configuring 423 entries in this table, the corresponding 424 ifEntry and mplsInterfaceConfEntry 425 MUST exist before hand. If an entry is attempted 426 to be created by a manager for a corresponding 427 mplsInterfaceConfEntry that does not support LC-ATM, 428 the agent MUST return an inconsistentValue error. 429 If this table is implemented read-only, then the 430 agent must set this object to active(1) when this 431 row is made active. If this table is implemented 432 writable, then an agent MUST not allow modification 433 to its objects once this value is set to active(1) 434 except mplsLcAtmStdIfConfRowStatus and 435 mplsLcAtmStdIfConfStorageType." 436 ::= { mplsLcAtmStdInterfaceConfEntry 8 } 438 mplsLcAtmStdIfConfStorageType OBJECT-TYPE 439 SYNTAX StorageType 440 MAX-ACCESS read-create 441 STATUS current 442 DESCRIPTION 443 "The storage type for this conceptual row. 444 Conceptual rows having the value 'permanent(4)' 445 need not allow write-access to any columnar 446 objects in the row." 447 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 449 DEFVAL { nonVolatile } 450 ::= { mplsLcAtmStdInterfaceConfEntry 9 } 452 -- End of mplsLcAtmStdInterfaceConfTable 454 -- Module compliance. 456 mplsLcAtmStdCompliances 457 OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 1 } 459 mplsLcAtmStdGroups 460 OBJECT IDENTIFIER ::= { mplsLcAtmStdConformance 2 } 462 -- Compliance requirement for full compliance 464 mplsLcAtmStdModuleFullCompliance MODULE-COMPLIANCE 465 STATUS current 466 DESCRIPTION 467 "Compliance statement for agents that provide 468 full support for MPLS-LC-ATM-STD-MIB. Such 469 devices can be monitored and also be configured 470 using this MIB module." 471 MODULE -- this module 472 MANDATORY-GROUPS { 473 mplsLcAtmStdIfGroup 474 } 476 OBJECT mplsLcAtmStdIfConfRowStatus 477 SYNTAX RowStatus { active(1), notInService(2) } 478 WRITE-SYNTAX RowStatus { active(1), notInService(2), 479 createAndGo(4), destroy(6) 480 } 481 DESCRIPTION "Support for createAndWait and notReady is 482 not required." 484 ::= { mplsLcAtmStdCompliances 1 } 486 -- Compliance requirement for read-only implementations. 488 mplsLcAtmStdModuleReadOnlyCompliance MODULE-COMPLIANCE 489 STATUS current 490 DESCRIPTION 491 "Compliance requirement for implementations that only 492 provide read-only support for MPLS-LC-ATM-STD-MIB. 493 Such devices can be monitored but cannot be configured 494 using this MIB module. 495 " 496 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 498 MODULE -- this module 499 MANDATORY-GROUPS { 500 mplsLcAtmStdIfGroup 501 } 503 -- mplsLcAtmStdInterfaceConfTable 505 OBJECT mplsLcAtmStdCtrlVpi 506 MIN-ACCESS read-only 507 DESCRIPTION 508 "Write access is not required." 510 OBJECT mplsLcAtmStdCtrlVci 511 MIN-ACCESS read-only 512 DESCRIPTION 513 "Write access is not required." 515 OBJECT mplsLcAtmStdUnlabTrafVpi 516 MIN-ACCESS read-only 517 DESCRIPTION 518 "Write access is not required." 520 OBJECT mplsLcAtmStdUnlabTrafVci 521 MIN-ACCESS read-only 522 DESCRIPTION 523 "Write access is not required." 525 OBJECT mplsLcAtmStdVcMerge 526 MIN-ACCESS read-only 527 DESCRIPTION 528 "Write access is not required." 530 OBJECT mplsLcAtmStdIfConfRowStatus 531 SYNTAX RowStatus { active(1) } 532 MIN-ACCESS read-only 533 DESCRIPTION "Write access is not required." 535 OBJECT mplsLcAtmVcDirectlyConnected 536 MIN-ACCESS read-only 537 DESCRIPTION 538 "Write access is not required." 540 OBJECT mplsLcAtmLcAtmVPI 541 MIN-ACCESS read-only 542 DESCRIPTION 543 "Write access is not required." 545 OBJECT mplsLcAtmStdIfConfStorageType 546 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 548 MIN-ACCESS read-only 549 DESCRIPTION 550 "Write access is not required." 551 ::= { mplsLcAtmStdCompliances 2 } 553 -- Units of conformance. 555 mplsLcAtmStdIfGroup OBJECT-GROUP 556 OBJECTS { 557 mplsLcAtmStdCtrlVpi, 558 mplsLcAtmStdCtrlVci, 559 mplsLcAtmStdUnlabTrafVpi, 560 mplsLcAtmStdUnlabTrafVci, 561 mplsLcAtmStdVcMerge, 562 mplsLcAtmVcDirectlyConnected, 563 mplsLcAtmLcAtmVPI, 564 mplsLcAtmStdIfConfRowStatus, 565 mplsLcAtmStdIfConfStorageType 566 } 567 STATUS current 568 DESCRIPTION 569 "Collection of objects needed for MPLS LC-ATM 570 interface configuration." 571 ::= { mplsLcAtmStdGroups 1 } 572 END 574 8. MPLS Label Controlled Frame Relay MIB Definitions 576 The following MIB module imports from [RFC2115], 577 [RFC3811], [RFC3813]. 579 MPLS-LC-FR-STD-MIB DEFINITIONS ::= BEGIN 580 IMPORTS 581 MODULE-IDENTITY, OBJECT-TYPE 582 FROM SNMPv2-SMI 583 MODULE-COMPLIANCE, OBJECT-GROUP 584 FROM SNMPv2-CONF 585 RowStatus, StorageType 586 FROM SNMPv2-TC 587 mplsInterfaceIndex 588 FROM MPLS-LSR-STD-MIB 589 DLCI 590 FROM FRAME-RELAY-DTE-MIB 591 mplsStdMIB 592 FROM MPLS-TC-STD-MIB 593 ; 594 mplsLcFrStdMIB MODULE-IDENTITY 595 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 597 LAST-UPDATED "200506171200Z" -- 17 June 2005 12:00:00 GMT 598 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group" 599 CONTACT-INFO 600 " Thomas D. Nadeau 601 Cisco Systems, Inc. 602 Email: tnadeau@cisco.com 604 Subrahmanya Hegde 605 Email: subrah@cisco.com 607 General comments should be sent to mpls@uu.net 608 " 609 DESCRIPTION 610 "This MIB module contains managed object definitions for 611 MPLS Label Controlled Frame-Relay interfaces as defined 612 in (RFC3034). 614 Copyright (C) The Internet Society (2004). This 615 version of this MIB module is part of RFCXXXX; see 616 the RFC itself for full legal notices." 617 -- RFC Editor please fill in XXXX 619 -- Revision history. 620 REVISION 621 "200506171200Z" -- 17 June 2005 12:00:00 GMT 622 DESCRIPTION 623 "Initial draft revision." 624 ::= { mplsStdMIB XXX } -- To Be Assigned by IANA 626 -- Top level components of this MIB module. 627 -- Tables, Scalars, Notifications, Conformance 629 mplsLcFrStdNotifications OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 0 } 630 mplsLcFrStdObjects OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 1 } 631 mplsLcFrStdConformance OBJECT IDENTIFIER ::= { mplsLcFrStdMIB 2 } 633 -- MPLS LC-FR Interface Configuration Table. 634 mplsLcFrStdInterfaceConfTable OBJECT-TYPE 635 SYNTAX SEQUENCE OF MplsLcFrStdInterfaceConfEntry 636 MAX-ACCESS not-accessible 637 STATUS current 638 DESCRIPTION 639 "This table specifies per-interface MPLS LC-FR 640 capability and associated information. In particular, 641 this table sparsely extends the MPLS-LSR-STD-MIB's 642 mplsInterfaceConfTable." 643 ::= { mplsLcFrStdObjects 1 } 644 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 646 mplsLcFrStdInterfaceConfEntry OBJECT-TYPE 647 SYNTAX MplsLcFrStdInterfaceConfEntry 648 MAX-ACCESS not-accessible 649 STATUS current 650 DESCRIPTION 651 "An entry in this table is created by an LSR for 652 every interface capable of supporting MPLS LC-FR. 653 Each entry in this table will exist only if a 654 corresponding entry in ifTable and mplsInterfaceConfTable 655 exist. If the associated entries in ifTable and 656 mplsInterfaceConfTable are deleted, the corresponding 657 entry in this table must also be deleted shortly 658 thereafter. " 659 INDEX { mplsInterfaceIndex } 660 ::= { mplsLcFrStdInterfaceConfTable 1 } 662 MplsLcFrStdInterfaceConfEntry ::= SEQUENCE { 663 mplsLcFrStdTrafficMinDlci DLCI, 664 mplsLcFrStdTrafficMaxDlci DLCI, 665 mplsLcFrStdCtrlMinDlci DLCI, 666 mplsLcFrStdCtrlMaxDlci DLCI, 667 mplsLcFrStdInterfaceConfRowStatus RowStatus, 668 mplsLcFrStdInterfaceConfStorageType StorageType 669 } 671 mplsLcFrStdTrafficMinDlci OBJECT-TYPE 672 SYNTAX DLCI 673 MAX-ACCESS read-create 674 STATUS current 675 DESCRIPTION 676 "This is the minimum DLCI value over which this 677 LSR is willing to accept traffic on this 678 interface." 679 ::= { mplsLcFrStdInterfaceConfEntry 1 } 681 mplsLcFrStdTrafficMaxDlci OBJECT-TYPE 682 SYNTAX DLCI 683 MAX-ACCESS read-create 684 STATUS current 685 DESCRIPTION 686 "This is the max DLCI value over which this 687 LSR is willing to accept traffic on this 688 interface." 689 ::= { mplsLcFrStdInterfaceConfEntry 2 } 691 mplsLcFrStdCtrlMinDlci OBJECT-TYPE 692 SYNTAX DLCI 693 MAX-ACCESS read-create 694 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 696 STATUS current 697 DESCRIPTION 698 "This is the min DLCI value over which this 699 LSR is willing to accept control traffic 700 on this interface." 701 ::= { mplsLcFrStdInterfaceConfEntry 3 } 703 mplsLcFrStdCtrlMaxDlci OBJECT-TYPE 704 SYNTAX DLCI 705 MAX-ACCESS read-create 706 STATUS current 707 DESCRIPTION 708 "This is the max DLCI value over which this 709 LSR is willing to accept control traffic 710 on this interface." 711 ::= { mplsLcFrStdInterfaceConfEntry 4 } 713 mplsLcFrStdInterfaceConfRowStatus OBJECT-TYPE 714 SYNTAX RowStatus 715 MAX-ACCESS read-create 716 STATUS current 717 DESCRIPTION 718 "This is object is used to create and 719 delete entries in this table. When configuring 720 entries in this table, the corresponding ifEntry and 721 mplsInterfaceConfEntry MUST exist before hand. If an entry 722 is attempted to be created by a manager for a corresponding 723 mplsInterfaceConfEntry that does not support LC-FR, 724 the agent MUST return an inconsistentValue error. 725 If this table is implemented read-only, then the 726 agent must set this object to active(1) when this 727 row is made active. If this table is implemented 728 writable, then an agent MUST not allow modification 729 to its objects once this value is set to active(1) 730 except mplsLcFrStdInterfaceConfRowStatus and 731 mplsLcFrStdInterfaceConfStorageType." 732 ::= { mplsLcFrStdInterfaceConfEntry 5 } 734 mplsLcFrStdInterfaceConfStorageType OBJECT-TYPE 735 SYNTAX StorageType 736 MAX-ACCESS read-create 737 STATUS current 738 DESCRIPTION 739 "The storage type for this conceptual row. 740 Conceptual rows having the value 'permanent(4)' 741 need not allow write-access to any columnar 742 objects in the row." 743 DEFVAL { nonVolatile } 744 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 746 ::= { mplsLcFrStdInterfaceConfEntry 6 } 748 -- End of mplsLcFrStdInterfaceConfTable 750 -- Module compliance. 752 mplsLcFrStdCompliances 753 OBJECT IDENTIFIER ::= { mplsLcFrStdConformance 1 } 755 mplsLcFrStdGroups 756 OBJECT IDENTIFIER ::= { mplsLcFrStdConformance 2 } 758 -- Compliance requirement for full compliance 760 mplsLcFrStdModuleFullCompliance MODULE-COMPLIANCE 761 STATUS current 762 DESCRIPTION 763 "Compliance statement for agents that provide 764 full support for MPLS-LC-FR-STD-MIB. Such 765 devices can be monitored and also be configured 766 using this MIB module." 767 MODULE -- this module 768 MANDATORY-GROUPS { 769 mplsLcFrStdIfGroup 770 } 772 OBJECT mplsLcFrStdInterfaceConfRowStatus 773 SYNTAX RowStatus { active(1), notInService(2) } 774 WRITE-SYNTAX RowStatus { active(1), notInService(2), 775 createAndGo(4), destroy(6) 776 } 777 DESCRIPTION "Support for createAndWait and notReady is 778 not required." 780 ::= { mplsLcFrStdCompliances 1 } 782 -- Compliance requirement for read-only implementations. 784 mplsLcFrStdModuleReadOnlyCompliance MODULE-COMPLIANCE 785 STATUS current 786 DESCRIPTION 787 "Compliance requirement for implementations that only 788 provide read-only support for MPLS-LC-FR-STD-MIB. 789 Such devices can be monitored but cannot be configured 790 using this MIB module. 791 " 792 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 794 MODULE -- this module 795 MANDATORY-GROUPS { 796 mplsLcFrStdIfGroup 797 } 799 -- mplsLcFrStdInterfaceConfTable 801 OBJECT mplsLcFrStdTrafficMinDlci 802 MIN-ACCESS read-only 803 DESCRIPTION 804 "Write access is not required." 806 OBJECT mplsLcFrStdTrafficMaxDlci 807 MIN-ACCESS read-only 808 DESCRIPTION 809 "Write access is not required." 811 OBJECT mplsLcFrStdCtrlMinDlci 812 MIN-ACCESS read-only 813 DESCRIPTION 814 "Write access is not required." 816 OBJECT mplsLcFrStdCtrlMaxDlci 817 MIN-ACCESS read-only 818 DESCRIPTION 819 "Write access is not required." 821 OBJECT mplsLcFrStdInterfaceConfRowStatus 822 SYNTAX RowStatus { active(1) } 823 MIN-ACCESS read-only 824 DESCRIPTION "Write access is not required." 826 OBJECT mplsLcFrStdInterfaceConfStorageType 827 MIN-ACCESS read-only 828 DESCRIPTION 829 "Write access is not required." 830 ::= { mplsLcFrStdCompliances 2 } 832 -- Units of conformance. 834 mplsLcFrStdIfGroup OBJECT-GROUP 835 OBJECTS { 836 mplsLcFrStdTrafficMinDlci, 837 mplsLcFrStdTrafficMaxDlci, 838 mplsLcFrStdCtrlMinDlci, 839 mplsLcFrStdCtrlMaxDlci, 840 mplsLcFrStdInterfaceConfRowStatus, 841 mplsLcFrStdInterfaceConfStorageType 842 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 844 } 845 STATUS current 847 DESCRIPTION 848 "Collection of objects needed for MPLS LC-FR 849 interface configuration." 850 ::= { mplsLcFrStdGroups 1 } 851 END 853 9. Authors' Addresses 855 Thomas D. Nadeau Subrahmanya Hegde 856 Cisco Systems, Inc. Cisco Systems, Inc. 857 300 Beaver Brook Road 225 East Tazman Drive 858 Boxboro, MA 01719 San Jose, CA 859 Phone: +1-978-936-1470 Phone: +1-408-525-6562 860 Email: tnadeau@cisco.com Email: subrah@cisco.com 862 10. Full Copyright Statement 863 Copyright (C) The Internet Society (2005). This document is 864 subject to the rights, licenses and restrictions contained in BCP 865 78, and except as set forth therein, the authors retain all their 866 rights. 868 This document and the information contained herein are provided 869 on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE 870 REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND 871 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, 872 EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT 873 THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR 874 ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A 875 PARTICULAR PURPOSE. 877 11. Acknowledgments 879 We wish to thank Joan Cucchiara and Carlos Pignataro for 880 their comments on this document. 882 12. Security Considerations 884 It is clear that these MIB modules are potentially useful for 885 monitoring of MPLS LSRs supporting LC-ATM and/or LC-FR. These 886 MIB can also be used for configuration of certain objects, and 887 anything that can be configured can be incorrectly configured, 888 with potentially disastrous results. 890 There are a number of management objects defined in this MIB module 891 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 893 with a MAX-ACCESS clause of read-write and/or read-create. Such 894 objects may be considered sensitive or vulnerable in some network 895 environments. The support for SET operations in a non-secure 896 environment without proper protection can have a negative effect on 897 network operations. These are the tables and objects and their 898 sensitivity/vulnerability: 900 o the MplsLcAtmStdInterfaceConfTable and 901 mplsLcFrStdInterfaceConfTable collectively 902 contain objects which may be used to provision MPLS LC or 903 FR-enabled interfaces. Unauthorized access to objects in 904 these tables, could result in disruption of traffic on the 905 network. This is especially true if traffic has been 906 established over these interfaces. The use of stronger 907 mechanisms such as SNMPv3 security should be considered 908 where possible. Specifically,SNMPv3 VACM and USM MUST be 909 used with any v3 agent which implements this MIB module. 910 Administrators should consider whether read access to 911 these objects should be allowed, since read access may be 912 undesirable under certain circumstances. 914 Some of the readable objects in this MIB module (i.e., objects with a 915 MAX-ACCESS other than not-accessible) may be considered sensitive or 916 vulnerable in some network environments. It is thus important to 917 control even GET and/or NOTIFY access to these objects and possibly 918 to even encrypt the values of these objects when sending them over 919 the network via SNMP. These are the tables and objects and their 920 sensitivity/vulnerability: 922 o the MplsLcAtmStdInterfaceConfTable and 923 mplsLcFrStdInterfaceConfTable collectively 924 collectively show the LC-ATM and/or LC-FR interfaces, 925 their associated configurations and their linkages to other 926 MPLS-related configuration and/or performanc statistics. 927 Administrators not wishing to reveal this information should 928 consider these objects sensitive/vulnerable and take 929 precautions so they are not revealed. 931 SNMP versions prior to SNMPv3 did not include adequate security. 932 Even if the network itself is secure (for example by using IPSec), 933 even then, there is no control as to who on the secure network is 934 allowed to access and GET/SET (read/change/create/delete) the objects 935 in this MIB module. 937 It is RECOMMENDED that implementers consider the security features as 938 provided by the SNMPv3 framework (see [RFC3410], section 8), 939 including full support for the SNMPv3 cryptographic mechanisms (for 940 authentication and privacy). 942 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 944 Further, deployment of SNMP versions prior to SNMPv3 is NOT 945 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 946 enable cryptographic security. It is then a customer/operator 947 responsibility to ensure that the SNMP entity giving access to an 948 instance of this MIB module, is properly configured to give access 949 to the objects only to those principals (users) that have legitimate 950 rights to indeed GET or SET (change/create/delete) them. 952 13. IANA Considerations 954 As described in and as requested in the MPLS-TC-STD-MIB 955 [RFC3811], MPLS related standards track MIB modules should be 956 rooted under the mplsStdMIB subtree. There are 2 MPLS MIB modules 957 contained in this document, each of the following "IANA 958 Considerations" subsections requests IANA for a new assignment under 959 the mplsStdMIB subtree. New assignments can only be made via a 960 Standards Action as specified in [RFC2434]. 962 13.1. IANA Considerations for MPLS-LC-ATM-STD-MIB 964 The IANA is requested to assign { mplsStdMIB 9 } to the 965 MPLS-LC-ATM-STD-MIB module specified in this document. 967 13.2. IANA Considerations for MPLS-LC-FR-STD-MIB 969 The IANA is requested to assign { mplsStdMIB 10 } to the 970 MPLS-LC-FR-STD-MIB module specified in this document. 972 14. References 974 14.1 Normative References 976 [RFC3034] Conta, A., Doolan, P., Malis, A., "Use 977 of Label Switching on Frame Relay Networks 978 Specification", Rfc3034, JANUARY 2001. 980 [RFC3035] Davie, B., mcCloghhrie, K., Rosen., E., Swallow, G., 981 Rekhter, Y., Doolan, P., "MPLS using LDP and ATM VC 982 Switching", RFC3035, January 2001. 984 [RFC2115] Brown, C., Baker, F., "Management Information Base 985 for Frame Relay DTEs Using SMIv2", RFC2115, September 986 1997. 988 [RFC2514] Noto, M., Spiegel, E., Tesink, K., et al., "Definitions 989 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 991 of Textual Conventions and OBJECT-IDENTITIES for ATM 992 Management", RFC2514, February 1999. 994 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces 995 Group MIB", RFC 2863, June 2000. 997 [RFC3031] Rosen, E., Viswanathan, A., and R. Callon, 998 "Multiprotocol Label Switching Architecture", RFC 999 3031, January 2001. 1001 [RFC3811] Nadeau, T., Cucchiara, J., Editors, 1002 "Definition of Textual Conventions and OBJECT- 1003 IDENTITIES for Multi-Protocol Label Switching (MPLS) 1004 Management", RFC3811, June 2004. 1006 [RFC3812] Srinivasan, C., Viswanathan, A. and Nadeau, T., "MPLS 1007 Traffic Engineering Management Information Base ", 1008 RFC3812, June 2004. 1010 [RFC3813] Srinivasan, C., Viswanathan, A. and T. 1011 Nadeau, "MPLS Multiprotocol Label Switching 1012 (MPLS) Label Switch Router Management 1013 Information Base ", RFC3813, June 2004. 1015 [RFC2119] S. Bradner, "Key Words for use in RFCs to Indicate 1016 Requirement Levels", RFC 2119, BCP 14, March 1997. 1018 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1019 J., Rose, M., and S. Waldbusser, "Structure of 1020 Management Information Version 2 (SMIv2)", STD 58, RFC 1021 2578, April 1999. 1023 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1024 J., Rose, M., and S. Waldbusser, "Textual Conventions 1025 for SMIv2", STD 58, RFC 2579, April 1999. 1027 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 1028 J., Rose, M., and S. Waldbusser, "Conformance 1029 Statements for SMIv2", STD 58, RFC 2580, April 1999. 1031 14.2 Informative References 1033 [RFC2434] Narten, T. and H. Alvestrand., "Guidelines for Writing an 1034 IANA Considerations Section in RFCs", BCP 26, RFC 2434, 1035 October 1998. 1037 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1038 draft-ietf-mpls-lc-if-mib-08.txt October 12, 2005 1040 "Introduction and Applicability Statements for 1041 Internet-Standard Management Framework", RFC 3410, 1042 December 2002. 1044 [RFC3815] J. Cucchiara, et al., "Definitions of 1045 Managed Objects for the Multiprotocol Label 1046 Switching, Label Distribution Protocol 1047 (LDP)", RFC3815, June 2004. 1049 15. Intellectual Property 1051 The IETF takes no position regarding the validity or scope of any 1052 Intellectual Property Rights or other rights that might be claimed to 1053 pertain to the implementation or use of the technology described in 1054 this document or the extent to which any license under such rights 1055 might or might not be available; nor does it represent that it has 1056 made any independent effort to identify any such rights. Information 1057 on the procedures with respect to rights in RFC documents can be 1058 found in BCP 78 and BCP 79. 1060 Copies of IPR disclosures made to the IETF Secretariat and any 1061 assurances of licenses to be made available, or the result of an 1062 attempt made to obtain a general license or permission for the use of 1063 such proprietary rights by implementers or users of this 1064 specification can be obtained from the IETF on-line IPR repository at 1065 http://www.ietf.org/ipr. 1067 The IETF invites any interested party to bring to its attention any 1068 copyrights, patents or patent applications, or other proprietary 1069 rights that may cover technology that may be required to implement 1070 this standard. Please address the information to the IETF at ietf- 1071 ipr@ietf.org.