idnits 2.17.1 draft-ietf-atommib-atm2TC-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-19) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** Expected the document's filename to be given on the first page, but didn't find any == 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 Abstract section. ** The document seems to lack an Introduction section. (A line matching the expected section header was found, but with an unexpected indentation: ' 2. Introduction' ) ** The document seems to lack a Security Considerations section. (A line matching the expected section header was found, but with an unexpected indentation: ' 6. Security Considerations' ) ** 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 an Authors' Addresses Section. ** There are 10 instances of too long lines in the document, the longest one being 4 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Couldn't figure out when the document was first submitted -- there may comments or warnings related to the use of a disclaimer for pre-RFC5378 work that could not be issued because of this. Please check the Legal Provisions document at https://trustee.ietf.org/license-info to determine if you need the pre-RFC5378 disclaimer. -- The document date (February 1996) is 10291 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 section? '1' on line 288 looks like a reference -- Missing reference section? '2' on line 293 looks like a reference Summary: 14 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Textual Convention and OBJECT-IDENTITY Objects 3 for ATM Management 5 February 1996 7 Michael Noto (editor) 8 Bell Communications Research 9 noto@cc.bellcore.com 11 Kaj Tesink (editor) 12 Bell Communications Research 13 kaj@cc.bellcore.com 15 1. Status of this Memo 17 This document is an Internet-Draft. Internet-Drafts are 18 working documents of the Internet Engineering Task Force 19 (IETF), its Areas, and its Working Groups. Note that other 20 groups may also distribute working documents as Internet- 21 Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six 24 months and may be updated, replaced, or obsoleted by other 25 documents at any time. It is inappropriate to use Internet- 26 Drafts as reference material or to cite them other than as a 27 "work in progress". 29 To learn the current status of any Internet-Draft, please 30 check the "1id-abstracts.txt" listing contained in the 31 Internet-Drafts Shadow Directories on ds.internic.net (US East 32 Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), 33 or munnari.oz.au (Pacific Rim). 35 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 37 2. Introduction 39 This memo describes Textual Conventions and OBJECT-IDENTITY 40 objects used for managing ATM-based interfaces, devices, 41 networks and services. 43 When designing a MIB module, it is often useful to define new 44 types similar to those defined in the SMI. In comparison to a 45 type defined in the SMI, each of these new types has a 46 different name, a similar syntax, but a more precise 47 semantics. These newly defined types are termed textual 48 conventions, and are used for the convenience of humans 49 reading the MIB module. This is done through Textual 50 Conventions as defined in RFC1443[1]. It is the purpose of 51 this document to define the set of textual conventions 52 available to ATM MIB modules. OBJECT-IDENTITY objects are also 53 defined to be used by ATM Devices. 55 This memo does not specify a standard for the Internet 56 community. 58 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 60 3. Definitions 62 ATMTC-MIB DEFINITIONS ::= BEGIN 64 IMPORTS 65 MODULE-IDENTITY, OBJECT-IDENTITY, 66 Integer32, experimental 67 FROM SNMPv2-SMI 68 TEXTUAL-CONVENTION 69 FROM SNMPv2-TC; 71 atmTCMIB MODULE-IDENTITY 72 LAST-UPDATED "9602121200Z" 73 ORGANIZATION "IETF AToMMIB Working Group" 74 CONTACT-INFO 75 " Michael Noto 76 Postal: Bell Communications Research 77 331 Newman Springs Road 78 Red Bank, NJ 07701 79 US 80 Tel: +1 908 758 5104 81 Fax: +1 908 758 4177 82 E-mail: noto@cc.bellcore.com 84 Kaj Tesink 85 Postal: Bell Communications Research 86 331 Newman Springs Road 87 Red Bank, NJ 07701 88 US 89 Tel: +1 908 758 5254 90 Fax: +1 908 758 4177 91 E-mail: kaj@cc.bellcore.com" 92 DESCRIPTION 93 "This MIB Module provides Textual Conventions 94 and OBJECT-IDENTITY Objects to be used by 95 ATM systems." 96 ::= { experimental XX } 98 atmTCMIBObjects OBJECT IDENTIFIER ::= {atmTCMIB 1} 100 -- This MIB Module contains the following 101 -- Textual Conventions: 103 IfIndex ::= TEXTUAL-CONVENTION 105 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 107 STATUS current 108 DESCRIPTION 109 "The value of this object identifies the 110 interface for which the entry contains 111 management information. The value of this 112 object for a particular interface has the 113 same value as the ifIndex object, defined in 114 RFC 1213 [2], for the same interface." 115 SYNTAX Integer32 117 InterfaceIndex ::= TEXTUAL-CONVENTION 118 STATUS current 119 DESCRIPTION 120 "The value of this object identifies the 121 atmLogicalPort interface for which the entry 122 contains management information. The value of 123 this object for a particular interface has the 124 same value as the ifIndex object, defined in 125 RFC 1213 [2], for the same atmLogicalPort 126 interface." 127 SYNTAX Integer32 129 AtmAddr ::= TEXTUAL-CONVENTION 130 STATUS current 131 DESCRIPTION 132 "The ATM address used by the network entity. 133 The address types are: no address (0 octets), 134 E.164 (8 octets), network prefix (13 octets), 135 and NSAP (20 octets). Note: The E.164 address 136 is encoded in BCD format." 137 SYNTAX OCTET STRING (SIZE(0|8|13|20)) 139 AtmSigDescrParamIndex ::= TEXTUAL-CONVENTION 140 STATUS current 141 DESCRIPTION 142 "The value of this object identifies a row in 143 the atmSigDescrParamTable. " 144 SYNTAX Integer32 146 AtmTrafficDescrParamIndex ::= TEXTUAL-CONVENTION 147 STATUS current 148 DESCRIPTION 149 "The value of this object identifies a row in the 150 atmTrafficDescrParamTable. The value 0 signifies 151 that no row has been identified." 153 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 155 SYNTAX Integer32 157 -- This MIB Module contains the following 158 -- OBJECT-IDENTITY objects: 160 atmTrafficDescriptorTypes OBJECT IDENTIFIER ::= 161 {atmTCMIBObjects 1} 163 -- The following values are defined for use as 164 -- possible values of the ATM traffic descriptor type. 166 atmNoTrafficDescriptor OBJECT-IDENTITY 167 STATUS current 168 DESCRIPTION 169 "This identifies the no ATM traffic 170 descriptor type. Parameters 1, 2, 3, 4, 171 and 5 are not used. This traffic descriptor 172 type can be used for best effort traffic." 173 ::= {atmTrafficDescriptorTypes 1} 175 atmNoClpNoScr OBJECT-IDENTITY 176 STATUS current 177 DESCRIPTION 178 "This traffic descriptor is for no CLP and 179 no Sustained Cell Rate. The use of the 180 parameter vector for this type: 181 Parameter 1: CLP=0+1 peak cell rate in 182 cells per second 183 Parameter 2: not used 184 Parameter 3: not used 185 Parameter 4: not used 186 Parameter 5: not used. 187 This traffic descriptor type can be used 188 for best effort traffic." 189 ::= {atmTrafficDescriptorTypes 2} 191 atmClpNoTaggingNoScr OBJECT-IDENTITY 192 STATUS current 193 DESCRIPTION 194 "This traffic descriptor is for CLP without 195 tagging and no Sustained Cell Rate. The use 196 of the parameter vector for this type: 197 Parameter 1: CLP=0+1 peak cell rate in 198 cells per second 200 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 202 Parameter 2: CLP=0 peak cell rate in 203 cells per second 204 Parameter 3: not used 205 Parameter 4: not used 206 Parameter 5: not used." 207 ::= {atmTrafficDescriptorTypes 3} 209 atmClpTaggingNoScr OBJECT-IDENTITY 210 STATUS current 211 DESCRIPTION 212 "This traffic descriptor is for CLP with 213 tagging and no Sustained Cell Rate. The use 214 of the parameter vector for this type: 215 Parameter 1: CLP=0+1 peak cell rate in 216 cells per second 217 Parameter 2: CLP=0 peak cell rate in 218 cells per second with excess 219 traffic tagged as CLP=1 220 Parameter 3: not used 221 Parameter 4: not used 222 Parameter 5: not used." 223 ::= {atmTrafficDescriptorTypes 4} 225 atmNoClpScr OBJECT-IDENTITY 226 STATUS current 227 DESCRIPTION 228 "This traffic descriptor is for no CLP with 229 Sustained Cell Rate. The use 230 of the parameter vector for this type: 231 Parameter 1: CLP=0+1 peak cell rate in 232 cells per second 233 Parameter 2: CLP=0+1 sustained cell rate in 234 cells per second 235 Parameter 3: CLP=0+1 maximum burst size in 236 cells 237 Parameter 4: not used 238 Parameter 5: not used." 239 ::= {atmTrafficDescriptorTypes 5} 241 atmClpNoTaggingScr OBJECT-IDENTITY 242 STATUS current 243 DESCRIPTION 244 "This traffic descriptor is for CLP with 245 Sustained Cell Rate and no tagging. 246 The use of the parameter vector for this type: 248 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 250 Parameter 1: CLP=0+1 peak cell rate in 251 cells per second 252 Parameter 2: CLP=0 sustained cell rate in 253 cells per second 254 Parameter 3: CLP=0 maximum burst size in 255 cells 256 Parameter 4: not used 257 Parameter 5: not used." 258 ::= {atmTrafficDescriptorTypes 6} 260 atmClpTaggingScr OBJECT-IDENTITY 261 STATUS current 262 DESCRIPTION 263 "This traffic descriptor is for CLP 264 with tagging and Sustained Cell Rate. 265 The use of the parameter vector for this type: 266 Parameter 1: CLP=0+1 peak cell rate in 267 cells per second 268 Parameter 2: CLP=0 sustained cell rate in 269 cells per second with excess 270 traffic tagged as CLP=1. 271 Parameter 3: CLP=0 maximum burst size in 272 cells 273 Parameter 4: not used 274 Parameter 5: not used." 275 ::= {atmTrafficDescriptorTypes 7} 277 END 278 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 280 4. Acknowledgments 282 This document is a product of the AToMMIB Working Group. 284 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 286 5. References 288 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 289 "Textual Conventions for SNMPv2", RFC1443, SNMP 290 Research,Inc., Hughes LAN Systems, Dover Beach 291 Consulting, Inc., Carnegie Mellon University, April 1993. 293 [2] McCloghrie, K., and M. Rose, Editors, "Management 294 Information Base for Network Management of TCP/IP-based 295 internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, 296 Performance Systems International, March 1991. 298 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 300 6. Security Considerations 302 Security issues are not discussed in this memo. 304 7. Authors' Addresses 306 Michael Noto 307 Bell Communications Research 308 Room 1E-348 309 331 Newman Springs Road 310 P.O. Box 7020 311 Red Bank, NJ 07701-7020 312 Phone: (908) 758-5104 313 EMail: noto@cc.bellcore.com 315 Kaj Tesink 316 Bell Communications Research 317 Room 1A-427 318 331 Newman Springs Road 319 P.O. Box 7020 320 Red Bank, NJ 07701-7020 321 Phone: (908) 758-5254 322 EMail: kaj@cc.bellcore.com 324 draft ATM Textual Convention and OBJECT-IDENTITY Objects~~Feb 1996 326 Table of Contents 328 1 Status of this Memo ................................... 1 329 2 Introduction .......................................... 2 330 3 Definitions ........................................... 3 331 4 Acknowledgments ....................................... 8 332 5 References ............................................ 9 333 6 Security Considerations ............................... 10 334 7 Authors' Addresses .................................... 10