idnits 2.17.1 draft-gmggm-ccamp-gencons-snmp-mib-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 327 has weird spacing: '...ual row avail...' == Line 378 has weird spacing: '... tabble is de...' == Line 399 has weird spacing: '...ual row avail...' == 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. -- The document date (July 14, 2013) is 3901 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Missing Reference: 'EDITOR NOTE' is mentioned on line 105, but not defined == Missing Reference: 'TEMPLATE TODO' is mentioned on line 257, but not defined == Unused Reference: 'RFC2863' is defined on line 621, but no explicit reference was found in the text == Unused Reference: 'RFC2629' is defined on line 661, but no explicit reference was found in the text == Unused Reference: 'RFC4181' is defined on line 664, but no explicit reference was found in the text == Unused Reference: 'I-D.ietf-ccamp-rwa-info' is defined on line 680, but no explicit reference was found in the text == Outdated reference: A later version (-20) exists of draft-ietf-ccamp-general-constraint-encode-11 == Outdated reference: A later version (-10) exists of draft-ietf-ccamp-gmpls-general-constraints-ospf-te-05 -- Obsolete informational reference (is this intentional?): RFC 2629 (Obsoleted by RFC 7749) == Outdated reference: A later version (-24) exists of draft-ietf-ccamp-rwa-info-18 Summary: 0 errors (**), 0 flaws (~~), 14 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Engineering Task Force G. Galimberti, Ed. 3 Internet-Draft G. Martinelli, Ed. 4 Intended status: Standards Track Cisco 5 Expires: January 15, 2014 D. Hiremagalur 6 G. Grammel 7 Juniper 8 July 14, 2013 10 A SNMP MIB to manage GMPLS with General Constraints support 11 draft-gmggm-ccamp-gencons-snmp-mib-02 13 Abstract 15 This memo defines a portion of the Management Information Base (MIB) 16 used by Simple Network Management Protocol (SNMP) for GMPLS based 17 networks. 19 In particular in the context Wavelength Switching Optical Network 20 (WSON) two sets of information were defined: a general constrains set 21 (reusable by other technologies) and a WSON specific set. This 22 document defines a MIB module for supporting general constrain 23 information. 25 Copyright Notice 27 Copyright (c) 2011 IETF Trust and the persons identified as the 28 document authors. All rights reserved. 30 Status of This Memo 32 This Internet-Draft is submitted in full conformance with the 33 provisions of BCP 78 and BCP 79. 35 Internet-Drafts are working documents of the Internet Engineering 36 Task Force (IETF). Note that other groups may also distribute 37 working documents as Internet-Drafts. The list of current Internet- 38 Drafts is at http://datatracker.ietf.org/drafts/current/. 40 Internet-Drafts are draft documents valid for a maximum of six months 41 and may be updated, replaced, or obsoleted by other documents at any 42 time. It is inappropriate to use Internet-Drafts as reference 43 material or to cite them other than as "work in progress." 45 This Internet-Draft will expire on January 15, 2014. 47 Copyright Notice 48 Copyright (c) 2013 IETF Trust and the persons identified as the 49 document authors. All rights reserved. 51 This document is subject to BCP 78 and the IETF Trust's Legal 52 Provisions Relating to IETF Documents 53 (http://trustee.ietf.org/license-info) in effect on the date of 54 publication of this document. Please review these documents 55 carefully, as they describe your rights and restrictions with respect 56 to this document. Code Components extracted from this document must 57 include Simplified BSD License text as described in Section 4.e of 58 the Trust Legal Provisions and are provided without warranty as 59 described in the Simplified BSD License. 61 Table of Contents 63 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 64 2. The Internet-Standard Management Framework . . . . . . . . . 3 65 3. Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 3 66 4. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 3 67 5. Structure of the MIB Module . . . . . . . . . . . . . . . . . 4 68 5.1. gmplsGenConsAvailableLabelsTable . . . . . . . . . . . . 4 69 5.2. gmplsGenConsSharedBackupLabelsTable . . . . . . . . . . . 5 70 5.3. gmplsGenConsConnMatrixTable . . . . . . . . . . . . . . . 5 71 5.4. gmplsGenConsPortLabelRestrictionTable . . . . . . . . . . 5 72 6. Relationship to Other MIB Modules . . . . . . . . . . . . . . 6 73 6.1. Relationship to the [TEMPLATE TODO] MIB . . . . . . . . . 6 74 6.2. MIB modules required for IMPORTS . . . . . . . . . . . . 6 75 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 6 76 8. Security Considerations . . . . . . . . . . . . . . . . . . . 12 77 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 78 10. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 13 79 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 14 80 11.1. Normative References . . . . . . . . . . . . . . . . . . 14 81 11.2. Informative References . . . . . . . . . . . . . . . . . 14 82 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 15 83 Appendix B. Open Issues . . . . . . . . . . . . . . . . . . . . 15 84 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 15 86 1. Introduction 88 This memo defines a portion of the Management Information Base (MIB) 89 used by Simple Network Management Protocol (SNMP) in GMPLS networks 90 in patricular for Wavelength Switched Optical Networks (WSON) as 91 defined in [RFC6163]. 93 Those extensions were divided in two parts: generic constrains (as 94 they can be easily applied to other technologies) and WSON specific 95 contraints. This document aim to defines MIBs extentions to conver 96 only the generic constrain part. The WSON specific MIB extentions 97 will be covered by a separate document 98 [I-D.gmggm-ccamp-wson-snmp-mib]. 100 As such, document [I-D.ietf-ccamp-general-constraint-encode] defines 101 specific TLVs while [RFC6825] implement OSPF-TE related extentions. 102 This MIB document aim to cover information defined in those general 103 constrain drafts. 105 [EDITOR NOTE] Very early draft to start MIB activity on GMPSL-WSON 106 related extentions and collect feedback from working group. 108 2. The Internet-Standard Management Framework 110 For a detailed overview of the documents that describe the current 111 Internet-Standard Management Framework, please refer to section 7 of 112 RFC 3410 [RFC3410]. 114 Managed objects are accessed via a virtual information store, termed 115 the Management Information Base or MIB. MIB objects are generally 116 accessed through the Simple Network Management Protocol (SNMP). 117 Objects in the MIB are defined using the mechanisms defined in the 118 Structure of Management Information (SMI). This memo specifies a MIB 119 module that is compliant to the SMIv2, which is described in STD 58, 120 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 121 [RFC2580]. 123 3. Conventions 125 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 126 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 127 document are to be interpreted as described in RFC 2119 [RFC2119] In 128 the description of OIDs the convention: Set (S) Get (G) and Trap (T) 129 conventions will describe the action allowed by the paramenter. 131 4. Overview 133 Regarding exsting GMPLS MIBs modules, since the TED module [RFC6825] 134 already provide and extention to previous GMPLS modules, we provide 135 here a direct extention to it. Additional GMPLS MIB modules this 136 document uses are [RFC4802] and [RFC4803]. 138 Current GMPLS MIBs are covered by several documents. The most 139 important to refererence here are the [RFC4802] and [RFC4803]. Most 140 recent works on GMPLS MIBs is in [RFC6825], whenever possible this 141 document will reuse the same approach. 143 General constrains can be classified in two broads categories: link 144 information (as other GMPLS TED information) and Node information 145 (this is different from what currently available). For link 146 information the most similar definions are the ones from [RFC4803] 147 where the label table is defined. For node information however, new 148 specific information has to be defined. 150 5. Structure of the MIB Module 152 Modules defined here provide additional information to existing GMPLS 153 MIBS in order to represent the general constrains information as 154 reported in [I-D.ietf-ccamp-general-constraint-encode]. This module 155 is organized into two tables as reported in the following sub 156 sections. 158 5.1. gmplsGenConsAvailableLabelsTable 160 This object represent the Labels availability as defined by 161 [I-D.ietf-ccamp-general-constraint-encode] section 2.3. This 162 information may be introduced by specific technologies but is 163 represented in a general form. An application example is [draft- 164 ietf-ccamp-wson-signal-compatibility-ospf] that advertise such 165 information under its specific ISC values. 167 The table entry is composed by: 169 o gmplsGenConsLabelIndex (type: Unsigned 32) 171 o gmplgGenConsLabelInterface (type: typesInterfaceIndexOrZero) 173 o gmplsGenConsISCD (type: IANAGmplsSwitchingTypeTC needs to be 174 properly extended). 175 [EDITOR NOTE1: could we assume that ISCD=151 for WSON hence the 176 associated label follows RFC6205. Likely flexgrid will have the 177 same constrain.] 178 [EDITOR NOTE2: we could probably add an index reference to the 179 tedSwCabTable so we have all switching capability info through one 180 pointer.] 182 o gmplsGenConsLabelValue (type: a value that might be greater than 183 32 bits, not sure about max length). Value format may vary upon 184 the ISCD however the generic label format defined in the past 185 still apply. A type might be reused could be 186 (gmplsLabelPortWavelength Unsigned32) defined in GMPLS LSR MIB. 187 However we need to support labels bigger than 32 bits. 189 Depending on switching capability available on an interface, this 190 table MUST initialized with all possible available labels values. As 191 long an tunnels are created and labels are used, the existing 192 gmplsLabelTable defined in [RFC4803], is filled up while entries are 193 removed from this gmplsGenConsAvailableLabelsTable. 195 5.2. gmplsGenConsSharedBackupLabelsTable 197 The purpose of shared backup labels is defined in 198 [I-D.ietf-ccamp-general-constraint-encode]. As in the previous case 199 the information is advertised through the specific ISCD. 201 The entry for this table is equal to definitions in Section 5.1 hence 202 we have the same table format. 204 5.3. gmplsGenConsConnMatrixTable 206 The Connectivity Matrix indicates the Node constraints introduced by 207 [I-D.ietf-ccamp-general-constraint-encode] as additional constrains 208 compared to link/label constrains. 210 The table entry shall have the following information: 212 o An identifier of the local node. E.g. tedLocalRouterId (type: 213 TedRouterIdTC). 215 o Connectivity Matrix Type (1: RWA, 2: Optical Impairments) 217 o Connectivity Matrix ID: the unique identifier for the current 218 connectivity matrix. Type: integer. 220 o Link Ingress: (Type: TedLinkIndexTC) the link identifier for the 221 ingress link (ingress and egress link identify a possible 222 connectivty for the node). 224 o Link Egress: (Type: TedLinkIndexTC) the link identifier for the 225 egress link (ingress and egress link indentify a possible 226 connectivty for the node). 228 5.4. gmplsGenConsPortLabelRestrictionTable 230 This table the port label constraints introduced by 231 [I-D.ietf-ccamp-general-constraint-encode] as an additional 232 constrains on the port or vs permitted labels. This constrains 233 related to the connectivity matrix (from previous section) and are 234 advertised through 235 [I-D.ietf-ccamp-gmpls-general-constraints-ospf-te]. 237 The entry for this table has the following elements: 239 o An identifier for the local node. E.g. tedLocalRouterId (type: 240 TedRouterIdTC). 242 o Connectivity matrix id: an index in the previous table 244 o Restriction Type (Values: 0 Simple Label, 1 Channel Count, 2 Label 245 Range1, 3 Simple Label and Channel Count, 4 Link Label 246 Exclusivity) 248 o Label Set: used depending on restriction type 250 o Max Channel Count / Max Label Set (Integer): used depending on 251 restriction type 253 o Link Set: used depending on restrictio type 255 6. Relationship to Other MIB Modules 257 6.1. Relationship to the [TEMPLATE TODO] MIB 259 6.2. MIB modules required for IMPORTS 261 7. Definitions 263 TED-GENCONS-MIB DEFINITIONS ::= BEGIN 265 IMPORTS 266 MODULE-IDENTITY, OBJECT-TYPE, TimeTicks, NOTIFICATION-TYPE, 267 Unsigned32, Counter32, Integer32 268 FROM SNMPv2-SMI 269 DateAndTime, TEXTUAL-CONVENTION, RowStatus, TruthValue 270 FROM SNMPv2-TC 271 IANAGmplsSwitchingTypeTC 272 FROM IANA-GMPLS-TC-MIB 273 GmplsFreeformLabelTC 274 FROM GMPLS-TC-STD-MIB 275 ifIndex, ifDescr 276 FROM IF-MIB; 278 tedGenConsGMPLSMibModule MODULE-IDENTITY 279 LAST-UPDATED 280 "201307070000Z" -- Thu Jul 7 10:00:00 PST 2013 281 ORGANIZATION 282 " IETF Common Control And Measurement Plane (CCAMP) Working 283 Group " 284 CONTACT-INFO 285 "WG charter: 286 http://www.ietf.org/html.charters/ 288 Mailing Lists: 289 Editor: Gabriele Galimberti 290 Email: ggalimbe@cisco.com" 292 DESCRIPTION 293 "This MIB module defines objects used for managing the 294 the generic constraints for switched networks in GMPLS 295 networks ." 296 REVISION "201201270000Z" 297 DESCRIPTION 298 "Draft version 1.0" 299 ::= { tedGenConsGMPLSMibRoot 1 } 301 -- 302 -- Textual Conventions 303 -- 304 TedGenConsInterfaceIndexOrZero ::= TEXTUAL-CONVENTION 305 STATUS current 306 DESCRIPTION "interface index from 0 ..2147483647" 307 SYNTAX INTEGER (0..2147483647) 309 tedGenConsGmpls OBJECT IDENTIFIER ::= { tedGenConsGMPLSMibModule 1 } 311 gmplsGenConsAvailableLabelsTable OBJECT-TYPE 312 SYNTAX SEQUENCE OF GmplsGenConsAvailableLabelsEntry 313 MAX-ACCESS not-accessible 314 STATUS current 315 DESCRIPTION 316 "Information about the shared backup Labels 317 availability as defined by 318 [I-D.ietf-ccamp-general-constraint-encode] 319 section 2.3. " 320 ::= { tedGenConsGmpls 1 } 322 gmplsGenConsAvailableLabelsEntry OBJECT-TYPE 323 SYNTAX GmplsGenConsAvailableLabelsEntry 324 MAX-ACCESS not-accessible 325 STATUS current 326 DESCRIPTION 327 "A conceptual row availability labels Table." 328 INDEX { gmplsGenConspLabelIndex } 329 ::= { gmplsGenConsAvailableLabelsTable 1 } 331 GmplsGenConsAvailableLabelsEntry ::= 332 SEQUENCE { 333 gmplsGenConsLabelIndex 334 Unsigned32, 335 gmplsGenConsLabelInterface 336 TedGenConsInterfaceIndexOrZero, 337 gmplsGenConsISCD 338 IANAGmplsSwitchingTypeTC, 339 gmplsGenConsLabelValue 340 Unsigned32 341 } 343 gmplsGenConsLabelIndex OBJECT-TYPE 344 SYNTAX Unsigned32 345 MAX-ACCESS not-accessible 346 STATUS current 347 DESCRIPTION 348 " Label Index for this table" 349 ::= { gmplsGenConsAvailableLabelsEntry 1 } 351 gmplsGenConsLabelInterface OBJECT-TYPE 352 SYNTAX TedGenConsInterfaceIndexOrZero 353 MAX-ACCESS read-write 354 STATUS current 355 DESCRIPTION 356 "The interface Index of this interface" 357 ::= { gmplsGenConsAvailableLabelsEntry 2 } 359 gmplsGenConsISCD OBJECT-TYPE 360 SYNTAX IANAGmplsSwitchingTypeTC 361 MAX-ACCESS read-write 362 STATUS current 363 DESCRIPTION 364 "The interface switching type as defined in rfc4802. 365 The type needs to be extended for eg flex grid" 366 ::= { gmplsGenConsAvailableLabelsEntry 3 } 368 gmplsGenConsLabelValue OBJECT-TYPE 369 SYNTAX Unsigned32 370 MAX-ACCESS read-write 371 STATUS current 372 DESCRIPTION 373 "The Label value." 374 ::= { gmplsGenConsAvailableLabelsEntry 4 } 376 -- 377 -- 378 -- This purpose of the shared backup tabble is defined by 379 -- [I-D.ietf-ccamp-general-constraint-encode]. 380 -- As if the available table the information is advertised through 381 -- the specific ISCD 382 -- 383 gmplsGenConsSharedBackupLabelsTable OBJECT-TYPE 384 SYNTAX SEQUENCE OF GmplsGenConsSharedBackupLabelsEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "Information about the shared backup Labels 389 availability as defined by 390 [I-D.ietf-ccamp-general-constraint-encode] 391 section 2.3. " 392 ::= { tedGenConsGmpls 2 } 394 gmplsGenConsSharedBackupLabelsEntry OBJECT-TYPE 395 SYNTAX GmplsGenConsSharedBackupLabelsEntry 396 MAX-ACCESS not-accessible 397 STATUS current 398 DESCRIPTION 399 "A conceptual row availability labels Table." 400 INDEX { gmplsGenConsBackupLabelIndex } 401 ::= { gmplsGenConsSharedBackupLabelsTable 1 } 403 GmplsGenConsSharedBackupLabelsEntry ::= 404 SEQUENCE { 405 gmplsGenConsBackupLabelIndex 406 Unsigned32, 407 gmplsGenConsBackupLabelInterface 408 TedGenConsInterfaceIndexOrZero, 409 gmplsGenConsBackupISCD 410 IANAGmplsSwitchingTypeTC, 411 gmplsGenConsBackupLabelValue 412 Unsigned32 413 } 415 gmplsGenConsBackupLabelIndex OBJECT-TYPE 416 SYNTAX Unsigned32 417 MAX-ACCESS not-accessible 418 STATUS current 419 DESCRIPTION 420 " Label Index for this table" 421 ::= { gmplsGenConsSharedBackupLabelsEntry 1 } 423 gmplsGenConsBackupLabelInterface OBJECT-TYPE 424 SYNTAX TedGenConsInterfaceIndexOrZero 425 MAX-ACCESS read-write 426 STATUS current 427 DESCRIPTION 428 "The interface Index of this interface" 429 ::= { gmplsGenConsSharedBackupLabelsEntry 2 } 431 gmplsGenConsBackupISCD OBJECT-TYPE 432 SYNTAX IANAGmplsSwitchingTypeTC 433 MAX-ACCESS read-write 434 STATUS current 435 DESCRIPTION 436 "The interface switching type as defined in rfc4802. 437 The type needs to be extended for eg flex grid" 438 ::= { gmplsGenConsSharedBackupLabelsEntry 3 } 440 gmplsGenConsBackupLabelValue OBJECT-TYPE 441 SYNTAX Unsigned32 442 MAX-ACCESS read-write 443 STATUS current 444 DESCRIPTION 445 "The Label value." 446 ::= { gmplsGenConsSharedBackupLabelsEntry 4 } 448 -- 449 -- gmplsGenConsPortNodeTable 450 -- This table indicates the Node constraints introduced by 451 -- [I-D.ietf-ccamp-general-constraint-encode] as additional 452 -- constraints compared to link/label constrains reported above 454 gmplsGenConsiPortNodeTable OBJECT-TYPE 455 SYNTAX SEQUENCE OF GmplsGeniPortConsNodeEntry 456 MAX-ACCESS not-accessible 457 STATUS current 458 DESCRIPTION 459 "Information about the Port-label Node constraints." 460 ::= { tedGenConsGmpls 3 } 462 gmplsGenConsPortNodeEntry OBJECT-TYPE 463 SYNTAX GmplsGenConsPortNodeEntry 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "A conceptual row in the Node Table." 468 INDEX { gmplsGenConsPortNodeIndex } 469 ::= { gmplsGenConsPortNodeTable 1 } 471 GmplsGenConsPortNodeEntry ::= 472 SEQUENCE { 473 gmplsGenConsPortNodeIndex 474 Unsigned32, 476 gmplsGenConsPortLabelRestriction 477 Unsigned32 478 } 480 gmplsGenConsPortNodeIndex OBJECT-TYPE 481 SYNTAX Unsigned32 482 MAX-ACCESS not-accessible 483 STATUS current 484 DESCRIPTION 485 " Port node restristion Index for this table" 486 ::= { gmplsGenConsPortNodeEntry 1 } 488 gmplsGenConsBackupLabelInterface OBJECT-TYPE 489 SYNTAX Unsigned32 490 MAX-ACCESS read-write 491 STATUS current 492 DESCRIPTION 493 "This information represent a constain on ports vs 494 labels (i.e. some ports may not support all 495 wavelenghts)." 496 ::= { gmplsGenConsPortNodeEntry 2 } 498 -- gmplsGenConsConnectvityNodeTable 499 -- This table indicates the Node's connectivity matrix 500 -- ie some internal constraints in terms of connectivity 501 gmplsGenConsiConnectvityNodeTable OBJECT-TYPE 502 SYNTAX SEQUENCE OF GmplsGeniConnectvityConsNodeEntry 503 MAX-ACCESS not-accessible 504 STATUS current 505 DESCRIPTION 506 "Information about the constraints in terms of 507 connectivity for the node. " 508 ::= { tedGenConsGmpls 4 } 510 gmplsGenConsConnectvityNodeEntry OBJECT-TYPE 511 SYNTAX GmplsGenConsConnectvityNodeEntry 512 MAX-ACCESS not-accessible 513 STATUS current 514 DESCRIPTION 515 "A conceptual row in the Connectvity Node Table." 516 INDEX { gmplsGenConsConnectvityNodeIndex } 517 ::= { gmplsGenConsPortConnectvityTable 1 } 519 GmplsGenConsConnectvityNodeEntry ::= 520 SEQUENCE { 521 gmplsGenConsConnectvityNodeIndex 522 Unsigned32, 524 gmplsGenConsConnectvityMatrix 525 Unsigned32 526 } 528 gmplsGenConsConnectvityNodeIndex OBJECT-TYPE 529 SYNTAX Unsigned32 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION 533 " Connectivity matrix node Index for this table" 534 ::= { gmplsGenConsConnectvityNodeEntry 1 } 536 gmplsGenConsConnectvityMatrix OBJECT-TYPE 537 SYNTAX Unsigned32 538 MAX-ACCESS read-write 539 STATUS current 540 DESCRIPTION 541 "This information represent some node internal 542 constraint in term of connectivity." 543 ::= { gmplsGenConsConnectvityNodeEntry 2 } 545 END 547 8. Security Considerations 549 There are a number of management objects defined in this MIB module 550 with a MAX-ACCESS clause of read-write and/or read-create. Such 551 objects may be considered sensitive or vulnerable in some network 552 environments. The support for SET operations in a non-secure 553 environment without proper protection can have a negative effect on 554 network operations. These are the tables and objects and their 555 sensitivity/vulnerability: 557 Some of the readable objects in this MIB module (i.e., objects with a 558 MAX-ACCESS other than not-accessible) may be considered sensitive or 559 vulnerable in some network environments. It is thus important to 560 control even GET and/or NOTIFY access to these objects and possibly 561 to even encrypt the values of these objects when sending them over 562 the network via SNMP. 564 SNMP versions prior to SNMPv3 did not include adequate security. 565 Even if the network itself is secure (for example by using IPsec), 566 even then, there is no control as to who on the secure network is 567 allowed to access and GET/SET (read/change/create/delete) the objects 568 in this MIB module. 570 It is RECOMMENDED that implementers consider the security features as 571 provided by the SNMPv3 framework (see [RFC3410], section 8), 572 including full support for the SNMPv3 cryptographic mechanisms (for 573 authentication and privacy). 575 Further, deployment of SNMP versions prior to SNMPv3 is NOT 576 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 577 enable cryptographic security. It is then a customer/operator 578 responsibility to ensure that the SNMP entity giving access to an 579 instance of this MIB module is properly configured to give access to 580 the objects only to those principals (users) that have legitimate 581 rights to indeed GET or SET (change/create/delete) them. 583 9. IANA Considerations 585 Option #1: 587 The MIB module in this document uses the following IANA-assigned 588 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 590 Descriptor OBJECT IDENTIFIER value 591 ---------- ----------------------- 593 sampleMIB { mib-2 XXX } 595 Option #2: 597 Editor's Note (to be removed prior to publication): the IANA is 598 requested to assign a value for "XXX" under the 'mib-2' subtree and 599 to record the assignment in the SMI Numbers registry. When the 600 assignment has been made, the RFC Editor is asked to replace "XXX" 601 (here and in the MIB module) with the assigned value and to remove 602 this note. 604 Note well: prior to official assignment by the IANA, an internet 605 draft MUST use placeholders (such as "XXX" above) rather than actual 606 numbers. See RFC4181 Section 4.5 for an example of how this is done 607 in an internet draft MIB module. 609 Option #3: 611 This memo includes no request to IANA. 613 10. Contributors 615 to be added. 617 11. References 619 11.1. Normative References 621 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 622 MIB", RFC 2863, June 2000. 624 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 625 Requirement Levels", BCP 14, RFC 2119, March 1997. 627 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 628 Schoenwaelder, Ed., "Structure of Management Information 629 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 631 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 632 Schoenwaelder, Ed., "Textual Conventions for SMIv2", STD 633 58, RFC 2579, April 1999. 635 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 636 "Conformance Statements for SMIv2", STD 58, RFC 2580, 637 April 1999. 639 [RFC6825] Miyazawa, M., Otani, T., Kumaki, K., and T. Nadeau, 640 "Traffic Engineering Database Management Information Base 641 in Support of MPLS-TE/GMPLS", RFC 6825, January 2013. 643 [I-D.ietf-ccamp-general-constraint-encode] 644 Bernstein, G., Lee, Y., Li, D., and W. Imajuku, "General 645 Network Element Constraint Encoding for GMPLS Controlled 646 Networks", draft-ietf-ccamp-general-constraint-encode-11 647 (work in progress), May 2013. 649 [I-D.ietf-ccamp-gmpls-general-constraints-ospf-te] 650 Zhang, F., Lee, Y., Han, J., Bernstein, G., and Y. Xu, 651 "OSPF-TE Extensions for General Network Element 652 Constraints", draft-ietf-ccamp-gmpls-general-constraints- 653 ospf-te-05 (work in progress), June 2013. 655 11.2. Informative References 657 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 658 "Introduction and Applicability Statements for Internet- 659 Standard Management Framework", RFC 3410, December 2002. 661 [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, 662 June 1999. 664 [RFC4181] Heard, C., "Guidelines for Authors and Reviewers of MIB 665 Documents", BCP 111, RFC 4181, September 2005. 667 [RFC4802] Nadeau, T. and A. Farrel, "Generalized Multiprotocol Label 668 Switching (GMPLS) Traffic Engineering Management 669 Information Base", RFC 4802, February 2007. 671 [RFC4803] Nadeau, T. and A. Farrel, "Generalized Multiprotocol Label 672 Switching (GMPLS) Label Switching Router (LSR) Management 673 Information Base", RFC 4803, February 2007. 675 [RFC6163] Lee, Y., Bernstein, G., and W. Imajuku, "Framework for 676 GMPLS and Path Computation Element (PCE) Control of 677 Wavelength Switched Optical Networks (WSONs)", RFC 6163, 678 April 2011. 680 [I-D.ietf-ccamp-rwa-info] 681 Lee, Y., Bernstein, G., Li, D., and W. Imajuku, "Routing 682 and Wavelength Assignment Information Model for Wavelength 683 Switched Optical Networks", draft-ietf-ccamp-rwa-info-18 684 (work in progress), May 2013. 686 [I-D.gmggm-ccamp-wson-snmp-mib] 687 Galimberti, G., Martinelli, G., Hiremagalur, D., and G. 688 Grammel, "A SNMP MIB to manage GMPLS TED with WSON 689 specific support", draft-gmggm-ccamp-wson-snmp-mib-00 690 (work in progress), July 2012. 692 Appendix A. Change Log 694 This optional section should be removed before the internet draft is 695 submitted to the IESG for publication as an RFC. 697 Note to RFC Editor: please remove this appendix before publication as 698 an RFC. 700 Appendix B. Open Issues 702 Note to RFC Editor: please remove this appendix before publication as 703 an RFC. 705 Authors' Addresses 706 Gabriele M. Galimberti (editor) 707 Cisco 708 Via Philips,12 709 20900 - Monza 710 Italy 712 Phone: +390392091462 713 Email: ggalimbe@cisco.com 715 Giovanni Martinelli (editor) 716 Cisco 717 Via Philips,12 718 20900 - Monza 719 Italy 721 Email: giomarti@cisco.com 723 Dharini Hiremagalur 724 Juniper 725 1194 N Mathilda Avenue 726 Sunnyvale - 94089 CA 727 USA 729 Email: dharinih@juniper.net 731 Gert Grammel 732 Juniper 733 1194 N Mathilda Avenue 734 Sunnyvale - 94089 CA 735 USA 737 Email: ggrammel@juniper.net