idnits 2.17.1 draft-ietf-ccamp-gmpls-tc-mib-01.txt: 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: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 8 longer pages, the longest (page 2) being 61 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == The document doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (August 2003) is 7560 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: 'GMPLSArch' is mentioned on line 82, but not defined == Unused Reference: 'GMPLS-ARCH' is defined on line 254, but no explicit reference was found in the text == Unused Reference: 'RFC3031' is defined on line 265, but no explicit reference was found in the text == Unused Reference: 'RFC3209' is defined on line 269, but no explicit reference was found in the text == Unused Reference: 'RFC3212' is defined on line 273, but no explicit reference was found in the text == Unused Reference: 'RFC3471' is defined on line 281, but no explicit reference was found in the text == Unused Reference: 'RFC3472' is defined on line 285, but no explicit reference was found in the text == Unused Reference: 'RFC3473' is defined on line 289, but no explicit reference was found in the text == Unused Reference: 'GMPLSSonetSDH' is defined on line 292, but no explicit reference was found in the text == Unused Reference: 'GMPLSLSRMIB' is defined on line 304, but no explicit reference was found in the text == Unused Reference: 'GMPLSTEMIB' is defined on line 310, but no explicit reference was found in the text -- Obsolete informational reference (is this intentional?): RFC 2434 (Obsoleted by RFC 5226) == Outdated reference: A later version (-15) exists of draft-ietf-ccamp-gmpls-lsr-mib-01 == Outdated reference: A later version (-16) exists of draft-ietf-ccamp-gmpls-te-mib-01 Summary: 2 errors (**), 0 flaws (~~), 17 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Network Working Group Thomas D. Nadeau 3 Internet Draft Cisco Systems, Inc. 4 Expires: February 2004 5 Cheenu Srinivasan 6 Bloomberg L.P. 8 Adrian Farrel 9 Old Dog Consulting 11 Tim Hall 12 Ed Harrison 13 Data Connection Ltd. 15 August 2003 17 Definitions of Textual Conventions for Generalized Multi-Protocol 18 Label Switching (GMPLS) Management 20 draft-ietf-ccamp-gmpls-tc-mib-01.txt 22 Status of this Memo 24 This document is an Internet-Draft and is in full conformance with 25 all provisions of Section 10 of RFC 2026. 27 Internet-Drafts are working documents of the Internet Engineering 28 Task Force (IETF), its areas, and its working groups. Note that 29 other groups may also distribute working documents as Internet- 30 Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months 33 and may be updated, replaced, or obsoleted by other documents at any 34 time. It is inappropriate to use Internet-Drafts as reference 35 material or to cite them other than as "work in progress." 37 The list of current Internet-Drafts can be accessed at 38 http://www.ietf.org/ietf/1id-abstracts.txt. 40 Abstract 42 This document defines a Management Information Base (MIB) module 43 which contains Textual Conventions to represent commonly used 44 Generalized Multi-Protocol Label Switching (GMPLS) management 45 information. The intent is that these TEXTUAL CONVENTIONS (TCs) will 46 be imported and used in GMPLS related MIB modules that would 47 otherwise define their own representations. 49 Table of Contents 51 1. Introduction 2 52 2. The SNMP Management Framework 2 53 3. GMPLS Textual Conventions MIB Definitions 3 54 4. Security Considerations 5 55 5. IANA Considerations 5 56 6. References 5 57 6.1. NORMATIVE REFERENCES 5 58 6.2. INFORMATIONAL REFERENCES 6 59 7. Authors' Addresses 7 60 8. Full Copyright Statement 7 61 9. Intellectual Property Notice 8 63 1. Introduction 65 This document defines a MIB module which contains Textual Conventions 66 for Generalized Multi-Protocol Label Switching (GMPLS) networks. 67 These Textual Conventions should be imported by MIB modules which 68 manage GMPLS networks. 70 This MIB module supplements the MIB module in [TCMIB] that defines 71 Textual Conventions for Multiprotocol Label Switching (MPLS) 72 Management. [TCMIB] may continue to be used without this MIB module 73 in networks that support only MPLS. 75 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 76 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 77 document are to be interpreted as described in RFC 2119 [RFC2119]. 79 Comments should be made directly to the CCAMP mailing list at 80 ccamp@ops.ietf.org. 82 For an introduction to the concepts of GMPLS, see [GMPLSArch]. 84 2. The SNMP Management Framework 86 For a detailed overview of the documents that describe the current 87 Internet-Standard Management Framework, please refer to section 7 of 88 RFC 3410 [RFC3410]. 90 Managed objects are accessed via a virtual information store, termed 91 the Management Information Base or MIB. MIB objects are generally 92 accessed through the Simple Network Management Protocol (SNMP). 93 Objects in the MIB are defined using the mechanisms defined in the 94 Structure of Management Information (SMI). This memo specifies a MIB 95 module that is compliant to the SMIv2, which is described in STD 58, 96 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 97 [RFC2580]. 99 3. GMPLS Textual Conventions MIB Definitions 101 GMPLS-TC-STD-MIB DEFINITIONS ::= BEGIN 103 IMPORTS 104 MODULE-IDENTITY, Unsigned32, Integer32 105 FROM SNMPv2-SMI 106 transmission 107 FROM RFC1213-MIB 108 TEXTUAL-CONVENTION 109 FROM SNMPv2-TC 110 ; 112 gmplsTCStdMIB MODULE-IDENTITY 113 LAST-UPDATED 114 "200308190900Z " -- 19 August 2003 9:00:00 GMT" 115 ORGANIZATION "Common Control And Management Protocols (CCAMP) 116 Working Group" 117 CONTACT-INFO 118 " Thomas D. Nadeau 119 Cisco Systems, Inc. 120 Email: tnadeau@cisco.com 122 Cheenu Srinivasan 123 Bloomberg L.P. 124 Email: cheenu@bloomberg.net 126 Adrian Farrel 127 Old Dog Consulting 128 Email: adrian@olddog.co.uk 130 Ed Harrison 131 Data Connection Ltd. 132 Email: ed.harrison@dataconnection.com 134 Tim Hall 135 Data Connection Ltd. 136 Email: timhall@dataconnection.com 138 Comments about this document should be emailed direct to the 139 CCAMP working group mailing list at ccamp@ops.ietf.org" 140 DESCRIPTION 141 "Copyright (C) The Internet Society (2003). This version of this 142 MIB module is part of RFCXXX; see the RFC itself for full legal 143 notices. 145 This MIB module defines Textual Conventions for concepts used in 146 Generalized Multi-Protocol Label Switching (GMPLS) networks." 148 -- Revision history. 149 REVISION 150 "2003080190900Z" -- 19 August 2003 09:00:00 GMT 151 DESCRIPTION 152 "Initial version published as part of RFC XXXX." 153 -- Please see the IANA Considerations Section. 154 -- The requested gmplsStdMIB subId is xx, i.e. 155 ::= { gmplsStdMIB xx } 156 gmplsStdMIB OBJECT IDENTIFIER 157 -- This object identifier needs to be assigned by IANA. 158 -- Since mpls has been assigned an ifType of 166 we recommend 159 -- that this OID be 166 as well, i.e. 160 ::= { transmission XXX } 162 -- Textual Conventions (sorted alphabetically). 164 GmplsFreeformLabel ::= TEXTUAL-CONVENTION 165 STATUS current 166 DESCRIPTION 167 "This value represents a freeform generalized MPLS Label. This 168 can be used to represent label types which are not standard 169 in the drafts. It may also be used by systems that do not 170 wish to represent the labels using the specific label types." 171 SYNTAX OCTET STRING (SIZE (0..64)) 173 GmplsGeneralizedLabelTypes ::= TEXTUAL-CONVENTION 174 STATUS current 175 DESCRIPTION 176 "Determines the interpretation that should be applied to a 177 label." 178 SYNTAX INTEGER { 179 gmplsMplsLabel(1), 180 gmplsPortWavelengthLabel(2), 181 gmplsFreeformGeneralizedLabel(3), 182 gmplsSonetLabel(4), 183 gmplsSdhLabel(5), 184 gmplsWavebandLabel(6) 185 } 187 GmplsSegmentDirection ::= TEXTUAL-CONVENTION 188 STATUS current 189 DESCRIPTION 190 "The direction of data flow on an LSP segment with respect to the 191 head of the LSP. 193 Where an LSP is signaled using a conventional signaling 194 protocol, the 'head' of the LSP is the source of the signaling 195 (also known as the ingress) and the 'tail' is the destination 196 (also known as the egress). 198 For manually configured LSPs an arbitrary decision must be made 199 about which LER is the 'head'." 200 SYNTAX INTEGER { 201 forward(1), 202 reverse(2) 203 } 205 END 207 4. Security Considerations 209 This module does not define any management objects. Instead, it 210 defines a set of textual conventions which may be used by other GMPLS 211 MIB modules to define management objects. 213 Meaningful security considerations can only be written in the MIB 214 modules that define management objects. Therefore, this document has 215 no impact on the security of the Internet. 217 5. IANA Considerations 219 IANA is requested to make a MIB OID assignment under the transmission 220 branch, that is, assign the gmplsStdMIB under { transmission 166 }. 222 This sub-id is requested because 166 is the ifType for mpls(166) and 223 is available under transmission. 225 In the future, GMPLS related standards track MIB modules should be 226 rooted under the mplsStdMIB (sic) subtree. IANA is requested to 227 manage that namespace. New assignments can only be made via a 228 Standards Action as specified in [RFC2434]. 230 This document also requests IANA to assign { gmplsStdMIB xx } to the 231 GMPLS-TC-STD-MIB specified in this document. 233 6. References 235 6.1. Normative References 237 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 238 Requirement Levels", BCP 14, RFC 2119, March 1997. 240 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., 241 Case, J., Rose, M. and S. Waldbusser, "Structure of 242 Management Information Version 2 (SMIv2)", STD 58, 243 RFC 2578, April 1999. 245 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., 246 Case, J., Rose, M. and S. Waldbusser, "Textual 247 Conventions for SMIv2", STD 58, RFC 2579, April 248 1999. 250 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., 251 Case, J., Rose, M. and S. Waldbusser, "Conformance 252 Statements for SMIv2", STD 58, RFC 2580, April 1999. 254 [GMPLS-ARCH] Mannie, E., (editor), et. al. "Generalized Multi- 255 Protocol Label Switching (GMPLS) Architecture", 256 draft-ietf-ccamp-gmpls-architecture-07.txt, May 257 2003. 259 6.2. Informational References 261 [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for 262 Writing an IANA Considerations Section in RFCs", 263 BCP: 26, RFC 2434, October 1998. 265 [RFC3031] Rosen, E., Viswananthan, A., and R. Callon, 266 Multiprotocol Label Switching Architecture", 267 RFC 3031, January 2001. 269 [RFC3209] Awduche, D., Berger, L., Gan, D., Li, T., 270 Srinivasan, V., Swallow, G., "RSVP-TE: Extensions to 271 RSVP for LSP Tunnels", RFC 3209, December 2001. 273 [RFC3212] Jamoussi, B., (editor), et. al. "Constraint-Based 274 LSP Setup using LDP", RFC 3212, January 2002. 276 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 277 "Introduction and Applicability Statements for 278 Internet-Standard Management Framework", RFC 3410, 279 December 2002. 281 [RFC3471] Berger, L. (Editor), "Generalized Multi-Protocol 282 Label Switching (GMPLS) Signaling Functional 283 Description", RFC 3471, January 2003. 285 [RFC3472] Ashwood-Smith, P., Berger, L. (Editors), 286 "Generalized MPLS Signaling - CR-LDP Extensions", 287 RFC 3472, January 2003. 289 [RFC3473] Berger, L. (Editor), "Generalized MPLS Signaling - 290 RSVP-TE Extensions", RFC 3473 January 2003. 292 [GMPLSSonetSDH] Mannie, E., Papadimitriou, D. (Editors), 293 "Generalized Multi-Protocol Label Switching 294 Extensions for SONET and SDH Control", Internet 295 Draft , 296 February 2003, work in progress. 298 [TCMIB] Nadeau, T., Cucchiara, J. (Editors) "Definitions 299 of Textual Conventions for Multiprotocol Label 300 Switching (MPLS) Management", Internet Draft 301 , August 2003, 302 work in progress. 304 [GMPLSLSRMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 305 and Harrison, E., " Generalized Multiprotocol Label 306 Switching (GMPLS) Label Switching Router (LSR) 307 Management Information Base", draft-ietf-ccamp- 308 gmpls-lsr-mib-01.txt, August 2003, work in progress. 310 [GMPLSTEMIB] Nadeau, T., Srinivasan, C., Farrel, A., Hall, T., 311 and Harrison, E., "Generalized Multiprotocol Label 312 Switching (GMPLS) Traffic Engineering Management 313 Information Base", draft-ietf-ccamp-gmpls-te-mib- 314 01.txt, August 2003, work in progress. 316 7. Authors' Addresses 318 Thomas D. Nadeau 319 Cisco Systems, Inc. 320 300 Apollo Drive 321 Chelmsford, MA 01824 322 Phone: +1-978-244-3051 323 Email: tnadeau@cisco.com 325 Cheenu Srinivasan 326 Bloomberg L.P. 327 499 Park Ave., 328 New York, NY 10022 329 Phone: +1-212-893-3682 330 Email: cheenu@bloomberg.net 332 Adrian Farrel 333 Old Dog Consulting 334 Phone: +44-(0)-1978-860944 335 Email: adrian@olddog.co.uk 337 Tim Hall 338 Data Connection Ltd. 339 100 Church Street 340 Enfield, Middlesex 341 EN2 6BQ, UK 342 Phone: +44 20 8366 1177 343 Email: timhall@dataconnection.com 345 Ed Harrison 346 Data Connection Ltd. 347 100 Church Street 348 Enfield, Middlesex 349 EN2 6BQ, UK 350 Phone: +44 20 8366 1177 351 Email: ed.harrison@dataconnection.com 353 8. Full Copyright Statement 355 Copyright (C) The Internet Society (2003). All Rights Reserved. 357 This document and translations of it may be copied and furnished 358 to others, and derivative works that comment on or otherwise explain 359 it or assist in its implementation may be prepared, copied, published 360 and distributed, in whole or in part, without restriction of any 361 kind, provided that the above copyright notice and this paragraph are 362 included on all such copies and derivative works. However, this 363 document itself may not be modified in any way, such as by removing 364 the copyright notice or references to the Internet Society or other 365 Internet organizations, except as needed for the purpose of 366 developing Internet standards in which case the procedures for 367 copyrights defined in the Internet Standards process must be 368 followed, or as required to translate it into languages other than 369 English. 371 The limited permissions granted above are perpetual and will not be 372 revoked by the Internet Society or its successors or assigns. This 373 document and the information contained herein is provided on an "AS 374 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 375 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 376 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL 377 NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY 378 OR FITNESS FOR A PARTICULAR PURPOSE. 380 9. Intellectual Property Notice 382 The IETF takes no position regarding the validity or scope of any 383 intellectual property or other rights that might be claimed to 384 pertain to the implementation or use of the technology described in 385 this document or the extent to which any license under such rights 386 might or might not be available; neither does it represent that it 387 has made any effort to identify any such rights. Information on the 388 IETF's procedures with respect to rights in standards-track and 389 standards-related documentation can be found in BCP-11 [RFC2028]. 391 Copies of claims of rights made available for publication and any 392 assurances of licenses to be made available, or the result of an 393 attempt made to obtain a general license or permission for the use of 394 such proprietary rights by implementers or users of this 395 specification can be obtained from the IETF Secretariat. 397 The IETF invites any interested party to bring to its attention any 398 copyrights, patents or patent applications, or other proprietary 399 rights that may cover technology that may be required to practice 400 this standard. Please address the information to the IETF Executive 401 Director.