idnits 2.17.00 (12 Aug 2021) /tmp/idnits41232/draft-nadeau-pw-tc-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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. 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 (Dec 2001) is 7462 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: 'PWE3REQ' is mentioned on line 78, but not defined == Missing Reference: 'SNMPArch' is mentioned on line 85, but not defined == Missing Reference: 'SMIv1' is mentioned on line 90, but not defined == Missing Reference: 'SNMPv1MIBDef' is mentioned on line 90, but not defined == Missing Reference: 'SNMPv1Traps' is mentioned on line 90, but not defined == Missing Reference: 'SMIv2' is mentioned on line 91, but not defined == Missing Reference: 'SNMPv2TC' is mentioned on line 92, but not defined == Missing Reference: 'SNMPv2Conf' is mentioned on line 92, but not defined == Missing Reference: 'SNMPv1' is mentioned on line 105, but not defined == Missing Reference: 'SNMPv2c' is mentioned on line 98, but not defined == Missing Reference: 'SNMPv2TM' is mentioned on line 100, but not defined == Missing Reference: 'SNMPv3MP' is mentioned on line 100, but not defined == Missing Reference: 'SNMPv3USM' is mentioned on line 101, but not defined == Missing Reference: 'SNMPv2PO' is mentioned on line 106, but not defined == Missing Reference: 'SNMPv3App' is mentioned on line 109, but not defined == Missing Reference: 'SNMPv3VACM' is mentioned on line 110, but not defined == Unused Reference: 'RFC2571' is defined on line 208, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 212, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 216, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 219, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 222, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 227, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 231, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 235, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 239, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 243, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 248, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 253, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 257, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 262, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 265, but no explicit reference was found in the text == Unused Reference: 'MPLSArch' is defined on line 274, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 278, but no explicit reference was found in the text == Unused Reference: 'IPSEC' is defined on line 283, but no explicit reference was found in the text == Unused Reference: 'IFMIB' is defined on line 287, but no explicit reference was found in the text == Unused Reference: 'ATOMMIBTC' is defined on line 290, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. 'PWREQ' -- Possible downref: Non-RFC (?) normative reference: ref. 'PWFRM' ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** 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 1700 (ref. 'Assigned') (Obsoleted by RFC 3232) ** Obsolete normative reference: RFC 2401 (ref. 'IPSEC') (Obsoleted by RFC 4301) Summary: 17 errors (**), 0 flaws (~~), 39 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group Thomas D. Nadeau 2 Internet Draft Cisco Systems, Inc. 3 Expires: July 2002 4 Dave Danenberg 5 Litchfield Communications, Inc. 7 David Zelig 8 Corrigent Systems 10 Andrew G. Malis 11 Vivace Networks, Inc. 13 Dec 2001 15 Definitions for Textual Conventions and OBJECT-IDENTITIES 16 for Pseudo-Wires Management 18 draft-nadeau-pw-tc-mib-01.txt 20 Status of this Memo 22 This document is an Internet-Draft and is in full conformance with 23 all provisions of Section 10 of RFC2026. 25 Internet-Drafts are working documents of the Internet Engineering 26 Task Force (IETF), its areas, and its working groups. Note that 27 other groups may also distribute working documents as Internet- 28 Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html. 41 1.0 Abstract 43 This memo describes Textual Conventions and OBJECT-IDENTITIES used 44 for managing Pseudo-Wire services. 46 Table of Contents 48 1.0 Abstract......................................................1 49 2.0 Introduction..................................................2 50 3.0 Terminology...................................................2 51 4.0 The SNMP Management Framework.................................2 52 5.0 Definitions...................................................3 53 6.0 Security Considerations.......................................4 54 7.0 References....................................................4 55 8.0 Author's Addresses............................................6 56 9.0 Full Copyright Statement......................................7 58 2.0 Introduction 60 This memo defines a portion of the Management Information Base (MIB) 61 for use with network management protocols in the Internet community. 62 In particular, it defines Textual Conventions used in IETF PW and PW- 63 related MIBs. 65 Comments should be made directly to the MPLS mailing list at 66 pwe3@ietf.org. 68 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 69 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 70 document are to be interpreted as described in RFC-2119 [BCP14]. 72 For an introduction to the concepts of Pseudo-Wires, see [PWREQ] and 73 [PWFRM]. 75 3.0 Terminology 77 This document uses terminology from the document describing the 78 Pseudo-Wires Requirements [PWE3REQ]. 80 4.0 The SNMP Management Framework 82 The SNMP Management Framework presently consists of five major 83 components: 85 - An overall architecture, described in RFC 2271 [SNMPArch]. 87 - Mechanisms for describing and naming objects and events for the 88 purpose of management. The first version of this Structure of 89 Management Information (SMI) is called SMIv1 and described in RFC 90 1155 [SMIv1], RFC 1212 [SNMPv1MIBDef] and RFC 1215 [SNMPv1Traps]. 91 The second version, called SMIv2, is described in RFC 1902 [SMIv2], 92 RFC 1903 [SNMPv2TC] and RFC 1904 [SNMPv2Conf]. 94 - Message protocols for transferring management information. The 95 first version of the SNMP message protocol is called SNMPv1 and 96 described in RFC 1157 [SNMPv1]. A second version of the SNMP message 97 protocol, which is not an Internet standards track protocol, is 98 called SNMPv2c and described in RFC 1901 [SNMPv2c] and RFC 1906 99 [SNMPv2TM]. The third version of the message protocol is called 100 SNMPv3 and described in RFC 1906 [SNMPv2TM], RFC 2272 [SNMPv3MP] and 101 RFC 2574 [SNMPv3USM]. 103 - Protocol operations for accessing management information. The 104 first set of protocol operations and associated PDU formats is 105 described in RFC 1157 [SNMPv1]. A second set of protocol operations 106 and associated PDU formats is described in RFC 1905 [SNMPv2PO]. 108 - A set of fundamental applications described in RFC 2273 109 [SNMPv3App] and the view-based access control mechanism described in 110 RFC 2575 [SNMPv3VACM]. 112 A more detailed introduction to the current SNMP Management Framework 113 can be found in RFC 2570 [RFC2570]. 115 Managed objects are accessed via a virtual information store, termed 116 the Management Information Base or MIB. Objects in the MIB are 117 defined using the mechanisms defined in the SMI. 119 This memo specifies a MIB module that is compliant to the SMIv2. A 120 MIB conforming to the SMIv1 can be produced through the appropriate 121 translations. The resulting translated MIB must be semantically 122 equivalent, except where objects or events are omitted because no 123 translation is possible (use of Counter64). Some machine readable 124 information in SMIv2 will be converted into textual descriptions in 125 SMIv1 during the translation process. However, this loss of machine 126 readable information is not considered to change the semantics of the 127 MIB. 129 5.0 Definitions 131 PW-TC-MIB DEFINITIONS ::= BEGIN 133 IMPORTS 134 MODULE-IDENTITY, Unsigned32, transmission 135 FROM SNMPv2-SMI 137 TEXTUAL-CONVENTION 138 FROM SNMPv2-TC; 140 pwTCMIB MODULE-IDENTITY 141 LAST-UPDATED "200112201200Z" -- 20 Dec 2001 12:00:00 GMT 142 ORGANIZATION "Multiprotocol Label Switching (MPLS) Working Group, 143 Pseudo Wire Edge to Edge Emulation (PWE3) Working 144 Group" 145 CONTACT-INFO 146 "MPLS Working Group Mailing List: mpls@uu.net 147 PWE3 Working Group Mailing List: pwe3@ietf.org" 149 DESCRIPTION 150 "This MIB Module provides Textual Conventions 151 and OBJECT-IDENTITY Objects to be used PW services." 153 -- Revision history. 155 REVISION "200112201200Z" -- 20 Dec 2001 12:00:00 GMT 156 DESCRIPTION "Remove PwVcInstance" 158 REVISION "200107121200Z" -- 12 July 2001 12:00:00 GMT 159 DESCRIPTION "Initial version." 161 ::= { pwMIB 1 } -- pwMIB To Be Assigned by IANA 163 pwMIB OBJECT IDENTIFIER 164 ::= { transmission 7777 } -- To be assigned by IANA ?? 166 -- Textual Conventions defined below are organized alphabetically 168 PwGroupID ::= TEXTUAL-CONVENTION 169 STATUS current 170 DESCRIPTION 171 "An administrative identification mechanism for grouping a 172 set of service-specific pseudo-wire services. May only 173 have local significance." 174 SYNTAX Unsigned32 176 PwVcID ::= TEXTUAL-CONVENTION 177 STATUS current 178 DESCRIPTION 179 "Virtual Circuit Identifier. Uniquely identifies a VC 180 locally. Also uniquely identifies a VC at its end points." 181 SYNTAX Unsigned32 183 PwVcIndex ::= TEXTUAL-CONVENTION 184 STATUS current 185 DESCRIPTION 186 "Virtual Circuit Index. Locally unique index for indexing 187 one of several MIB tables associated with a particular VC." 188 SYNTAX Unsigned32 190 END 192 6.0 Security Considerations 194 This memo defines textual conventions and object identities for use 195 in MPLS MIB modules. Security issues for these MIB modules are 196 addressed in the memos defining those modules. 198 7.0 References 200 [PWREQ] Xiao, X., McPherson, D., et al, "Requirements for 201 Pseudo Wire Emulation Edge-to-Edge (PWE3)", 202 , Nov. 2001. 204 [PWFRM] Pate et al, "Framework for Pseudo Wire Emulation 205 Edge-to-Edge (PWE3)", , Sept. 2001. 208 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 209 Architecture for Describing SNMP Management 210 Frameworks", RFC 2571, April 1999. 212 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 213 Identification of Management Information for 214 TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 216 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 217 Definitions", STD 16, RFC 1212, March 1991. 219 [RFC1215] M. Rose, "A Convention for Defining Traps for use 220 with the SNMP", RFC 1215, March 1991. 222 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 223 J., Rose, M., and S. Waldbusser, "Structure of 224 Management Information Version 2 (SMIv2)", STD 58, RFC 225 2578, April 1999. 227 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 228 J., Rose, M., and S. Waldbusser, "Textual Conventions 229 for SMIv2", STD 58, RFC 2579, April 1999. 231 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 232 J., Rose, M., and S. Waldbusser, "Conformance 233 Statements for SMIv2", STD 58, RFC 2580, April 1999. 235 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 236 "Simple Network Management Protocol", STD 15, RFC 237 1157, May 1990. 239 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 240 "Introduction to Community-based SNMPv2", RFC 1901, 241 January 1996. 243 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 244 "Transport Mappings for Version 2 of the Simple 245 Network Management Protocol (SNMPv2)", RFC 1906, 246 January 1996. 248 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 249 "Message Processing and Dispatching for the Simple 250 Network Management Protocol (SNMP)", RFC 2572, April 251 1999. 253 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 254 Model (USM) for version 3 of the Simple Network 255 Management Protocol (SNMPv3)", RFC 2574, April 1999. 257 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 258 "Protocol Operations for Version 2 of the Simple 259 Network Management Protocol (SNMPv2)", RFC 1905, 260 January 1996. 262 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 263 Applications", RFC 2573, April 1999. 265 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 266 based Access Control Model (VACM) for the Simple 267 Network Management Protocol (SNMP)", RFC 2575, April 268 1999. 270 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 271 "Introduction to Version 3 of the Internet-standard 272 Network Management Framework", RFC 2570, April 1999. 274 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 275 "Multiprotocol Label Switching Architecture", 276 RFC 3031, August 1999. 278 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 279 RFC 1700, October 1994. See also: 280 http://www.isi.edu/in-notes/iana/assignments/smi- 281 numbers 283 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 284 for the Internet Protocol", RFC 2401, November 285 1998. 287 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 288 Group MIB", RFC 2863, June 2000. 290 [ATOMMIBTC] Noto, et. al., "Definitions of Textual Conventions and 291 OBJECT-IDENTITIES for ATM Management", RFC 2514, 292 Feb. 1999 294 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 295 Requirement Levels", BCP 14, RFC 2119, March 1997. 297 8.0 Author's Addresses 299 Thomas D. Nadeau 300 Cisco Systems, Inc. 301 250 Apollo Drive 302 Chelmsford, MA 01824 303 Email: tnadeau@cisco.com 305 Dave Danenberg 306 Litchfield Communications, Inc. 307 76 Westbury Park Rd 308 Princeton Building East 309 Watertown, CT 06795 310 Email: dave_danenberg@litchfieldcomm.com 312 David Zelig 313 Corrigent Systems LTD. 314 126, Yigal Alon st. 315 Tel Aviv, ISRAEL 316 Phone: +972-3-6945273 317 Email: davidz@corrigent.com 319 Andrew G. Malis 320 Vivace Networks, Inc. 321 2730 Orchard Parkway 322 San Jose, CA 95134 323 Email: Andy.Malis@vivacenetworks.com 325 9.0 Full Copyright Statement 327 "Copyright (C) The Internet Society (2001). All Rights Reserved. This 328 document and translations of it may be copied and furnished to 329 others, and derivative works that comment on or otherwise explain it 330 or assist in its implementation may be prepared, copied, published 331 and distributed, in whole or in part, without restriction of any 332 kind, provided that the above copyright notice and this paragraph are 333 included on all such copies and derivative works. However, this 334 document itself may not be modified in any way, such as by removing 335 the copyright notice or references to the Internet Society or other 336 Internet organizations, except as needed for the purpose of 337 developing Internet standards in which case the procedures for 338 copyrights defined in the Internet Standards process must be 339 followed, or as required to translate it into languages other than 340 English. 342 The limited permissions granted above are perpetual and will not be 343 revoked by the Internet Society or its successors or assigns. 345 This document and the information contained herein is provided on an 346 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 347 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 348 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 349 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 350 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 352 Acknowledgement 354 Funding for the RFC Editor function is currently provided by the 355 Internet Society.