idnits 2.17.1 draft-ietf-charmib-ppl-mib-02.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. ** 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. == 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 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 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 (26 May 1994) is 10921 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) ** Obsolete normative reference: RFC 1442 (ref. '1') (Obsoleted by RFC 1902) ** Downref: Normative reference to an Historic RFC: RFC 1445 (ref. '3') ** Obsolete normative reference: RFC 1448 (ref. '4') (Obsoleted by RFC 1905) ** Obsolete normative reference: RFC 1573 (ref. '5') (Obsoleted by RFC 2233) -- Possible downref: Non-RFC (?) normative reference: ref. '6' -- Possible downref: Non-RFC (?) normative reference: ref. '7' Summary: 14 errors (**), 0 flaws (~~), 1 warning (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Parallel-printer-like MIB 3 26 May 1994 5 Bob Stewart 6 Xyplex, Inc. 7 rlstewart@eng.xyplex.com 9 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, and 15 its Working Groups. Note that other groups may also distribute working 16 documents as Internet Drafts. 18 Internet Drafts are valid for a maximum of six months and may be 19 updated, replaced, or obsoleted by other documents at any time. It is 20 inappropriate to use Internet Drafts as reference material or to cite 21 them other than as a "work in progress". 23 draft Parallel-printer-like MIB 26 May 1994 25 1. Introduction 27 This memo defines an extension to the Management Information Base (MIB) 28 for use with network management protocols in the Internet community. In 29 particular, it defines objects for the management of Parallel-printer- 30 like devices. 32 draft Parallel-printer-like MIB 26 May 1994 34 2. The SNMPv2 Network Management Framework 36 The SNMPv2 Network Management Framework consists of four major 37 components. They are: 39 o RFC 1442 [1] which defines the SMI, the mechanisms used for 40 describing and naming objects for the purpose of management. 42 o STD 17, RFC 1213 [2] defines MIB-II, the core set of managed 43 objects for the Internet suite of protocols. 45 o RFC 1445 [3] which defines the administrative and other 46 architectural aspects of the framework. 48 o RFC 1448 [4] which defines the protocol used for network access to 49 managed objects. 51 The Framework permits new objects to be defined for the purpose of 52 experimentation and evaluation. 54 2.1. Object Definitions 56 Managed objects are accessed via a virtual information store, termed the 57 Management Information Base or MIB. Objects in the MIB are defined 58 using the subset of Abstract Syntax Notation One (ASN.1) defined in the 59 SMI. In particular, each object object type is named by an OBJECT 60 IDENTIFIER, an administratively assigned name. The object type together 61 with an object instance serves to uniquely identify a specific 62 instantiation of the object. For human convenience, we often use a 63 textual string, termed the descriptor, to refer to the object type. 65 draft Parallel-printer-like MIB 26 May 1994 67 3. Overview 69 The Parallel-printer-like Hardware Device MIB applies to interface ports 70 that would most probably support the Character MIB. The most common 71 example is Centronics-like printer port. 73 The Parallel-printer-like Hardware Device MIB is mandatory for all 74 systems that have such a hardware port supporting services managed 75 through some other MIB. 77 The Parallel-printer-like Hardware Port MIB includes Centronics-like and 78 Data-Products-like parallel physical links with a similar set of control 79 signals. 81 The MIB contains objects that relate to physical layer connections. 83 The MIB comprises one base object and three tables, detailed in the 84 following sections. The tables contain objects for ports and input and 85 output control signals. 87 3.1. Relationship to Interface MIB 89 The Parallel-printer-like MIB is one of many MIBs designed for layered 90 use as described in the Interface MIB [5]. In most implementations 91 where it is present, it will be in the lowest interface sublayer, that 92 is, the Parallel-printer-like MIB represents the physical layer, 93 providing service to higher layers such as the Character MIB [6]. 95 Although it is unlikely that a parallel printer port will actually be 96 used as a network interface, which is the intent of the Interface MIB, 97 the Parallel-printer-like MIB is closely connected to the Character MIB, 98 which can share hardware interfaces with network operation, and relate 99 to the RS-232 MIB [7]. 101 The Interface MIB's ifTestTable and ifRcvAddressTable are not relevant 102 to the Parallel-printer-like MIB. 104 The Parallel-printer-like MIB is relevant for ifType values para(34) and 105 perhaps others. 107 The Parallel-printer-like MIB requires the conformance groups 108 ifGeneralGroup, and ifFixedLengthGroup. 110 Usefulness of error counters in this MIB depends on the octet counters 111 draft Parallel-printer-like MIB 26 May 1994 113 in ifFixedLengthGroup. 115 draft Parallel-printer-like MIB 26 May 1994 117 4. Definitions 119 PARALLEL-MIB DEFINITIONS ::= BEGIN 121 IMPORTS 122 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 123 Counter32, Integer32 124 FROM SNMPv2-SMI 125 InterfaceIndex 126 FROM IF-MIB 127 transmission 128 FROM RFC1213-MIB 129 MODULE-COMPLIANCE, OBJECT-GROUP 130 FROM SNMPv2-CONF; 132 para MODULE-IDENTITY 133 LAST-UPDATED "9405261700Z" 134 ORGANIZATION "IETF Character MIB Working Group" 135 CONTACT-INFO 136 " Bob Stewart 137 Postal: Xyplex, Inc. 138 295 Foster Street 139 Littleton, MA 01460 141 Tel: 508-952-4816 142 Fax: 508-952-4887 143 E-mail: rlstewart@eng.xyplex.com" 144 DESCRIPTION 145 "The MIB module for Parallel-printer-like hardware devices." 146 ::= { transmission 34 } 148 draft Parallel-printer-like MIB 26 May 1994 150 -- Generic Parallel-printer-like information 152 paraNumber OBJECT-TYPE 153 SYNTAX Integer32 154 MAX-ACCESS read-only 155 STATUS current 156 DESCRIPTION 157 "The number of ports (regardless of their current 158 state) in the Parallel-printer-like port table." 159 ::= { para 1 } 161 -- the Parallel-printer-like Port table 163 paraPortTable OBJECT-TYPE 164 SYNTAX SEQUENCE OF ParaPortEntry 165 MAX-ACCESS not-accessible 166 STATUS current 167 DESCRIPTION 168 "A list of port entries. The number of entries is 169 given by the value of paraNumber." 170 ::= { para 2 } 172 paraPortEntry OBJECT-TYPE 173 SYNTAX ParaPortEntry 174 MAX-ACCESS not-accessible 175 STATUS current 176 DESCRIPTION 177 "Status and parameter values for a port." 178 INDEX { paraPortIndex } 179 ::= { paraPortTable 1 } 181 ParaPortEntry ::= 182 SEQUENCE { 183 paraPortIndex 184 InterfaceIndex, 185 paraPortType 186 INTEGER, 187 paraPortInSigNumber 188 Integer32, 189 paraPortOutSigNumber 190 Integer32 191 } 193 paraPortIndex OBJECT-TYPE 194 draft Parallel-printer-like MIB 26 May 1994 196 SYNTAX InterfaceIndex 197 MAX-ACCESS read-only 198 STATUS current 199 DESCRIPTION 200 "The value of ifIndex for the port. By convention 201 and if possible, hardware port numbers map directly 202 to external connectors. The value for each port must 203 remain constant at least from one re-initialization 204 of the network management agent to the next." 205 ::= { paraPortEntry 1 } 207 paraPortType OBJECT-TYPE 208 SYNTAX INTEGER { 209 other(1), 210 centronics(2), 211 dataproducts(3) 212 } 213 MAX-ACCESS read-only 214 STATUS current 215 DESCRIPTION 216 "The port's hardware type." 217 ::= { paraPortEntry 2 } 219 paraPortInSigNumber OBJECT-TYPE 220 SYNTAX Integer32 221 MAX-ACCESS read-only 222 STATUS current 223 DESCRIPTION 224 "The number of input signals for the port in the 225 input signal table (paraPortInSigTable). The table 226 contains entries only for those signals the software 227 can detect and that are useful to observe." 228 ::= { paraPortEntry 3 } 230 paraPortOutSigNumber OBJECT-TYPE 231 SYNTAX Integer32 232 MAX-ACCESS read-only 233 STATUS current 234 DESCRIPTION 235 "The number of output signals for the port in the 236 output signal table (paraPortOutSigTable). The 237 table contains entries only for those signals the 238 software can assert and that are useful to observe." 239 ::= { paraPortEntry 4 } 241 draft Parallel-printer-like MIB 26 May 1994 243 -- Parallel-printer-like Input Signal Table 245 paraInSigTable OBJECT-TYPE 246 SYNTAX SEQUENCE OF ParaInSigEntry 247 MAX-ACCESS not-accessible 248 STATUS current 249 DESCRIPTION 250 "A list of port input control signal entries." 251 ::= { para 3 } 253 paraInSigEntry OBJECT-TYPE 254 SYNTAX ParaInSigEntry 255 MAX-ACCESS not-accessible 256 STATUS current 257 DESCRIPTION 258 "Input control signal status for a hardware port." 259 INDEX { paraInSigPortIndex, paraInSigName } 260 ::= { paraInSigTable 1 } 262 ParaInSigEntry ::= 263 SEQUENCE { 264 paraInSigPortIndex 265 InterfaceIndex, 266 paraInSigName 267 INTEGER, 268 paraInSigState 269 INTEGER, 270 paraInSigChanges 271 Counter32 272 } 274 paraInSigPortIndex OBJECT-TYPE 275 SYNTAX InterfaceIndex 276 MAX-ACCESS read-only 277 STATUS current 278 DESCRIPTION 279 "The value of paraPortIndex for the port to which 280 this entry belongs." 281 ::= { paraInSigEntry 1 } 283 paraInSigName OBJECT-TYPE 284 SYNTAX INTEGER { power(1), online(2), busy(3), 285 paperout(4), fault(5) } 286 MAX-ACCESS read-only 287 STATUS current 289 draft Parallel-printer-like MIB 26 May 1994 291 DESCRIPTION 292 "Identification of a hardware signal." 293 ::= { paraInSigEntry 2 } 295 paraInSigState OBJECT-TYPE 296 SYNTAX INTEGER { none(1), on(2), off(3) } 297 MAX-ACCESS read-only 298 STATUS current 299 DESCRIPTION 300 "The current signal state." 301 ::= { paraInSigEntry 3 } 303 paraInSigChanges OBJECT-TYPE 304 SYNTAX Counter32 305 MAX-ACCESS read-only 306 STATUS current 307 DESCRIPTION 308 "The number of times the signal has changed from 309 'on' to 'off' or from 'off' to 'on'." 310 ::= { paraInSigEntry 4 } 312 draft Parallel-printer-like MIB 26 May 1994 314 -- Output Signal Table 316 paraOutSigTable OBJECT-TYPE 317 SYNTAX SEQUENCE OF ParaOutSigEntry 318 MAX-ACCESS not-accessible 319 STATUS current 320 DESCRIPTION 321 "A list of port output control signal entries." 322 ::= { para 4 } 324 paraOutSigEntry OBJECT-TYPE 325 SYNTAX ParaOutSigEntry 326 MAX-ACCESS not-accessible 327 STATUS current 328 DESCRIPTION 329 "Output control signal status for a hardware port." 330 INDEX { paraOutSigPortIndex, paraOutSigName } 331 ::= { paraOutSigTable 1 } 333 ParaOutSigEntry ::= 334 SEQUENCE { 335 paraOutSigPortIndex 336 InterfaceIndex, 337 paraOutSigName 338 INTEGER, 339 paraOutSigState 340 INTEGER, 341 paraOutSigChanges 342 Counter32 343 } 345 paraOutSigPortIndex OBJECT-TYPE 346 SYNTAX InterfaceIndex 347 MAX-ACCESS read-only 348 STATUS current 349 DESCRIPTION 350 "The value of paraPortIndex for the port to which 351 this entry belongs." 352 ::= { paraOutSigEntry 1 } 354 paraOutSigName OBJECT-TYPE 355 SYNTAX INTEGER { power(1), online(2), busy(3), 356 paperout(4), fault(5) } 357 MAX-ACCESS read-only 358 STATUS current 360 draft Parallel-printer-like MIB 26 May 1994 362 DESCRIPTION 363 "Identification of a hardware signal." 364 ::= { paraOutSigEntry 2 } 366 paraOutSigState OBJECT-TYPE 367 SYNTAX INTEGER { none(1), on(2), off(3) } 368 MAX-ACCESS read-only 369 STATUS current 370 DESCRIPTION 371 "The current signal state." 372 ::= { paraOutSigEntry 3 } 374 paraOutSigChanges OBJECT-TYPE 375 SYNTAX Counter32 376 MAX-ACCESS read-only 377 STATUS current 378 DESCRIPTION 379 "The number of times the signal has changed from 380 'on' to 'off' or from 'off' to 'on'." 381 ::= { paraOutSigEntry 4 } 383 draft Parallel-printer-like MIB 26 May 1994 385 -- conformance information 387 paraConformance OBJECT IDENTIFIER ::= { para 5 } 389 paraGroups OBJECT IDENTIFIER ::= { paraConformance 1 } 390 paraCompliances OBJECT IDENTIFIER ::= { paraConformance 2 } 392 -- compliance statements 394 paraCompliance MODULE-COMPLIANCE 395 STATUS current 396 DESCRIPTION 397 "The compliance statement for SNMPv2 entities 398 which have Parallel-printer-like hardware 399 interfaces." 401 MODULE -- this module 402 MANDATORY-GROUPS { paraGroup } 403 ::= { paraCompliances 1 } 405 draft Parallel-printer-like MIB 26 May 1994 407 -- units of conformance 409 paraGroup OBJECT-GROUP 410 OBJECTS { paraNumber, paraPortIndex, paraPortType, 411 paraPortInSigNumber, paraPortOutSigNumber, 412 paraInSigPortIndex, paraInSigName, 413 paraInSigState, paraInSigChanges, 414 paraOutSigPortIndex, paraOutSigName, 415 paraOutSigState, paraOutSigChanges } 416 STATUS current 417 DESCRIPTION 418 "A collection of objects providing information 419 applicable to all Parallel-printer-like interfaces." 420 ::= { paraGroups 1 } 422 END 423 draft Parallel-printer-like MIB 26 May 1994 425 5. Acknowledgements 427 This memo was produced by the IETF Character MIB Working Group. 429 draft Parallel-printer-like MIB 26 May 1994 431 6. References 433 [1] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 434 of Management Information for version 2 of the Simple Network 435 Management Protocol (SNMPv2)", RFC 1442, SNMP Research,Inc., Hughes 436 LAN Systems, Dover Beach Consulting, Inc., Carnegie Mellon 437 University, April 1993. 439 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 440 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 441 RFC 1213, Hughes LAN Systems, Performance Systems International, 442 March 1991. 444 [3] Galvin, J., and K. McCloghrie, "Administrative Model for version 2 445 of the Simple Network Management Protocol (SNMPv2)", RFC 1445, 446 Trusted Information Systems, Hughes LAN Systems, April 1993. 448 [4] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 449 Operations for version 2 of the Simple Network Management Protocol 450 (SNMPv2)", RFC 1448, SNMP Research,Inc., Hughes LAN Systems, Dover 451 Beach Consulting, Inc., Carnegie Mellon University, April 1993. 453 [5] McCloghrie, K., and F.J. Kastenholz, "Evolution of the Interfaces 454 Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, 455 January 1994. 457 [6] Stewart, B., "Definitions of Managed Objects for Character Stream 458 Devices", RFC ????, Xyplex, Inc., ?Mon?, 1994. 460 [7] Stewart, B., "Definitions of Managed Objects for RS-232-like 461 Devices", RFC ????, Xyplex, Inc., 463 draft Parallel-printer-like MIB 26 May 1994 465 7. Security Considerations 467 Security issues are not discussed in this memo. 469 8. Author's Address 471 Bob Stewart 472 Xyplex, Inc. 473 295 Foster Street 474 Littleton, MA 01460 476 Tel: 508-952-4816 477 Fax: 508-952-4887 478 E-mail: rlstewart@eng.xyplex.com 480 Phone: 508-952-4816 481 Email: rlstewart@eng.xyplex.com 483 draft Parallel-printer-like MIB 26 May 1994 485 Table of Contents 487 1 Introduction .................................................... 2 488 2 The SNMPv2 Network Management Framework ......................... 3 489 2.1 Object Definitions ............................................ 3 490 3 Overview ........................................................ 4 491 3.1 Relationship to Interface MIB ................................. 4 492 4 Definitions ..................................................... 6 493 5 Acknowledgements ................................................ 15 494 6 References ...................................................... 16 495 7 Security Considerations ......................................... 17 496 8 Author's Address ................................................ 17