idnits 2.17.00 (12 Aug 2021) /tmp/idnits42245/draft-nadeau-pw-tc-mib-00.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 (July 2001) is 7615 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 215, but no explicit reference was found in the text == Unused Reference: 'RFC1155' is defined on line 219, but no explicit reference was found in the text == Unused Reference: 'RFC1212' is defined on line 223, but no explicit reference was found in the text == Unused Reference: 'RFC1215' is defined on line 226, but no explicit reference was found in the text == Unused Reference: 'RFC2578' is defined on line 229, but no explicit reference was found in the text == Unused Reference: 'RFC2579' is defined on line 234, but no explicit reference was found in the text == Unused Reference: 'RFC2580' is defined on line 238, but no explicit reference was found in the text == Unused Reference: 'RFC1157' is defined on line 242, but no explicit reference was found in the text == Unused Reference: 'RFC1901' is defined on line 246, but no explicit reference was found in the text == Unused Reference: 'RFC1906' is defined on line 250, but no explicit reference was found in the text == Unused Reference: 'RFC2572' is defined on line 255, but no explicit reference was found in the text == Unused Reference: 'RFC2574' is defined on line 260, but no explicit reference was found in the text == Unused Reference: 'RFC1905' is defined on line 264, but no explicit reference was found in the text == Unused Reference: 'RFC2573' is defined on line 269, but no explicit reference was found in the text == Unused Reference: 'RFC2575' is defined on line 272, but no explicit reference was found in the text == Unused Reference: 'MPLSArch' is defined on line 281, but no explicit reference was found in the text == Unused Reference: 'Assigned' is defined on line 285, but no explicit reference was found in the text == Unused Reference: 'IPSEC' is defined on line 290, but no explicit reference was found in the text == Unused Reference: 'IFMIB' is defined on line 294, but no explicit reference was found in the text == Unused Reference: 'ATOMMIBTC' is defined on line 297, 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: Jan 2002 4 Dave Danenberg 5 Litchfield Communications, Inc. 7 David Zelig 8 Corrigent Systems 10 Andrew G. Malis 11 Vivace Networks, Inc. 13 July 2001 15 Definitions for Textual Conventions and OBJECT-IDENTITIES 16 for Pseudo-Wires Management 18 draft-nadeau-pw-tc-mib-00.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 "200107121200Z" -- 12 July 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 "200107121200Z" -- 12 July 2001 12:00:00 GMT 156 DESCRIPTION "Initial version." 158 ::= { pwMIB 1 } -- pwMIB To Be Assigned by IANA 160 pwMIB OBJECT IDENTIFIER 161 ::= { transmission 7777 } -- To be assigned by IANA ?? 163 -- Textual Conventions defined below are organized alphabetically 165 PwGroupID ::= TEXTUAL-CONVENTION 166 STATUS current 167 DESCRIPTION 168 "An administrative identification mechanism for grouping a 169 set of service-specific pseudo-wire services. May only 170 have local significance" 171 SYNTAX Unsigned32 173 PwVcID ::= TEXTUAL-CONVENTION 174 STATUS current 175 DESCRIPTION 176 "Virtual Circuit Identifier. Uniquely identifies a VC 177 locally. Also uniquely identifies a VC at its end points." 178 SYNTAX Unsigned32 180 PwVcIndex ::= TEXTUAL-CONVENTION 181 STATUS current 182 DESCRIPTION 183 "Virtual Circuit Index. Locally unique index for indexing 184 one of several MIB tables associated with a particular VC." 185 SYNTAX Unsigned32 187 PwVcInstance ::= TEXTUAL-CONVENTION 188 STATUS current 189 DESCRIPTION 190 "Virtual Circuit Instance. Use in conjunction with 191 PwVcIndex when it is required to have more than one 192 instance of a particular VC. The primary application 193 for instances is APS where there are primary and backup 194 VCs." 195 SYNTAX Unsigned32 197 END 199 6.0 Security Considerations 201 This memo defines textual conventions and object identities for use 202 in MPLS MIB modules. Security issues for these MIB modules are 203 addressed in the memos defining those modules. 205 7.0 References 207 [PWREQ] Xiao, X., McPherson, D., et al, "Requirements for 208 Pseudo Wire Emulation Edge-to-Edge (PWE3)", 209 , May 2001. 211 [PWFRM] Pate et al, "Framework for Pseudo Wire Emulation 212 Edge-to-Edge (PWE3)", , July 2001. 215 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 216 Architecture for Describing SNMP Management 217 Frameworks", RFC 2571, April 1999. 219 [RFC1155] Rose, M., and K. McCloghrie, "Structure and 220 Identification of Management Information for 221 TCP/IP-based Internets", STD 16, RFC 1155, May 1990. 223 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB 224 Definitions", STD 16, RFC 1212, March 1991. 226 [RFC1215] M. Rose, "A Convention for Defining Traps for use 227 with the SNMP", RFC 1215, March 1991. 229 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 230 J., Rose, M., and S. Waldbusser, "Structure of 231 Management Information Version 2 (SMIv2)", STD 58, RFC 232 2578, April 1999. 234 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 235 J., Rose, M., and S. Waldbusser, "Textual Conventions 236 for SMIv2", STD 58, RFC 2579, April 1999. 238 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, 239 J., Rose, M., and S. Waldbusser, "Conformance 240 Statements for SMIv2", STD 58, RFC 2580, April 1999. 242 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 243 "Simple Network Management Protocol", STD 15, RFC 244 1157, May 1990. 246 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 247 "Introduction to Community-based SNMPv2", RFC 1901, 248 January 1996. 250 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 251 "Transport Mappings for Version 2 of the Simple 252 Network Management Protocol (SNMPv2)", RFC 1906, 253 January 1996. 255 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 256 "Message Processing and Dispatching for the Simple 257 Network Management Protocol (SNMP)", RFC 2572, April 258 1999. 260 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security 261 Model (USM) for version 3 of the Simple Network 262 Management Protocol (SNMPv3)", RFC 2574, April 1999. 264 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 265 "Protocol Operations for Version 2 of the Simple 266 Network Management Protocol (SNMPv2)", RFC 1905, 267 January 1996. 269 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 270 Applications", RFC 2573, April 1999. 272 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View- 273 based Access Control Model (VACM) for the Simple 274 Network Management Protocol (SNMP)", RFC 2575, April 275 1999. 277 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 278 "Introduction to Version 3 of the Internet-standard 279 Network Management Framework", RFC 2570, April 1999. 281 [MPLSArch] Rosen, E., Viswanathan, A., and R. Callon, 282 "Multiprotocol Label Switching Architecture", 283 RFC 3031, August 1999. 285 [Assigned] Reynolds, J., and J. Postel, "Assigned Numbers", 286 RFC 1700, October 1994. See also: 287 http://www.isi.edu/in-notes/iana/assignments/smi- 288 numbers 290 [IPSEC] Kent, S., and Atkinson, R., "Security Architecture 291 for the Internet Protocol", RFC 2401, November 292 1998. 294 [IFMIB] McCloghrie, K., and F. Kastenholtz, "The Interfaces 295 Group MIB", RFC 2863, June 2000. 297 [ATOMMIBTC] Noto, et. al., "Definitions of Textual Conventions and 298 OBJECT-IDENTITIES for ATM Management", RFC 2514, 299 Feb. 1999 301 [BCP14] Bradner, S., "Key words for use in RFCs to Indicate 302 Requirement Levels", BCP 14, RFC 2119, March 1997. 304 8.0 Author's Addresses 306 Thomas D. Nadeau 307 Cisco Systems, Inc. 308 250 Apollo Drive 309 Chelmsford, MA 01824 310 Email: tnadeau@cisco.com 312 Dave Danenberg 313 Litchfield Communications, Inc. 314 76 Westbury Park Rd 315 Princeton Building East 316 Watertown, CT 06795 317 Email: dave_danenberg@litchfieldcomm.com 319 David Zelig 320 Corrigent Systems LTD. 321 126, Yigal Alon st. 322 Tel Aviv, ISRAEL 323 Phone: +972-3-6945273 324 Email: davidz@corrigent.com 326 Andrew G. Malis 327 Vivace Networks, Inc. 328 2730 Orchard Parkway 329 San Jose, CA 95134 330 Email: Andy.Malis@vivacenetworks.com 332 9.0 Full Copyright Statement 334 "Copyright (C) The Internet Society (2001). All Rights Reserved. This 335 document and translations of it may be copied and furnished to 336 others, and derivative works that comment on or otherwise explain it 337 or assist in its implementation may be prepared, copied, published 338 and distributed, in whole or in part, without restriction of any 339 kind, provided that the above copyright notice and this paragraph are 340 included on all such copies and derivative works. However, this 341 document itself may not be modified in any way, such as by removing 342 the copyright notice or references to the Internet Society or other 343 Internet organizations, except as needed for the purpose of 344 developing Internet standards in which case the procedures for 345 copyrights defined in the Internet Standards process must be 346 followed, or as required to translate it into languages other than 347 English. 349 The limited permissions granted above are perpetual and will not be 350 revoked by the Internet Society or its successors or assigns. 352 This document and the information contained herein is provided on an 353 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 354 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 355 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 356 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 357 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 359 Acknowledgement 361 Funding for the RFC Editor function is currently provided by the 362 Internet Society.