proposed internet-draft€¦ · web view4.13 output 20. 4.14 alert 21. 5. new...

DRAFT Some issues are highlighted with yellow.ipp-mib-access-980503.pdf

S. IsaacsonNovell, Inc.T. Hastings

Xerox CorporationR. Herriot

Sun MicrosystemsMay 3, 1998

IPP Device and MIB accessVersion 0.03

Abstract

This document introduces a new Device object into the IPP object model. An IPP Printer object may support one or more Device objects which each represent a physical device as shown in the Internet Printing Protocol/1.0: Model and Semantics specification. This document provides read access to such device objects by defining a mapping from table entries in the Printer MIB to new algorithmically generated attribute names. New algorithmically generated attribute group names allow convenient read-only access to any row, any column, and any entire table in the Printer MIB, as well as the entire Printer MIB. A general algorithmically generated attribute name provides access to any single SNMP object in any MIB. These new attribute names and attribute group names are supplied in the "requested-attributes" Operation attribute of the current Get-Printer-Attributes operation. A new OPTIONAL "which-device" Operation attribute permits the requester to select a particular device for the case where an IPP Printer object is supporting more than one device.

Isaacson, Hastings []Expires -

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

21

22

23

24

1

2

DRAFT IPP Device and Medium Objects May 3, 1998

Table of Contents

1. Introduction.................................................................................................................................... 32. Object Relationships....................................................................................................................... 43. Issues Resolved in the Mapping..................................................................................................... 73.1 Terminology.............................................................................................................................. 73.2 Name vs Index..........................................................................Error! Bookmark not defined.3.3 Input objects and Media objects................................................................................................. 83.4 Interpreter Object vs. Document Format.................................................................................... 83.5 Scope Rules............................................................................................................................... 93.6 MIB Object names vs IPP Attribute names................................................................................93.7 Mapping of SMI data types to IPP syntax types.......................................................................124. IPP Sub-Units................................................................................Error! Bookmark not defined.4.1 New Printer Attributes..............................................................Error! Bookmark not defined.4.2 Console Display Buffer............................................................................................................ 164.3 Channel................................................................................................................................... 164.4 Cover........................................................................................Error! Bookmark not defined.4.5 Input........................................................................................................................................ 174.6 Interpreter................................................................................................................................ 174.7 Console Light.......................................................................................................................... 184.8 Marker..................................................................................................................................... 184.9 Marker Colorant...................................................................................................................... 184.10 Marker Supplies....................................................................................................................... 194.11 Media Path............................................................................................................................... 194.12 Medium................................................................................................................................... 194.13 Output...................................................................................................................................... 204.14 Alert........................................................................................................................................ 215. New "Get-Sub-Units" IPP Printer Operation..................................Error! Bookmark not defined.5.1.1 Get-MIB-Objects Operation..........................................Error! Bookmark not defined.5.1.1.1 Get-Sub-Units Request............................................Error! Bookmark not defined.5.1.1.2 Get-Sub-Units Response..........................................Error! Bookmark not defined.6. Conformance.................................................................................Error! Bookmark not defined.6.1 Client Conformance Requirements............................................Error! Bookmark not defined.6.2 Server Conformance Requirements...........................................Error! Bookmark not defined.6.2.1 Extensions.....................................................................Error! Bookmark not defined.7. Security Considerations.................................................................Error! Bookmark not defined.8. References.................................................................................................................................... 229. Copyright Notice.......................................................................................................................... 2210. Author's Address.......................................................................................................................... 22

Isaacson, Hastings, Herriot []Expires -

3

25

26

27

28

29

30

31

32

33

34

35

36

37

38

39

40

41

42

43

44

45

46

47

48

49

50

51

52

53

54

55

56

57

58

59

60

61

62

4

5


1. Introduction

This document introduces a new Device object into the IPP object model. An IPP Printer object may support one or more Device objects which each represent a physical device as shown in the Internet Printing Protocol/1.0: Model and Semantics specification. This document provides read access to such device objects by defining a mapping from table entries in the Printer MIB to new algorithmically generated attribute names. New algorithmically generated attribute group names allow convenient read-only access to any row, any column, and any entire table in the Printer MIB, as well as the entire Printer MIB. A general algorithmically generated attribute name provides access to any single SNMP object in any MIB. These new attribute names and attribute group names are supplied in the "requested-attributes" Operation attribute of the current Get-Printer-Attributes operation. A new OPTIONAL "which-device" Operation attribute permits the requester to select a particular device for the case where an IPP Printer object is supporting more than one device.

This mapping allows for Printer MIB information to be queried (no setting or modification of information) using the IPP protocol rather than SNMP. This is not to say that the use of SNMP is invalid or improper, in fact just the opposite is true. The implementation of SNMP based Printer MIBs is almost universal for modern, network-attached printers. Therefore, since the information model as already been established and implemented, this document is simply a "IPP window" onto the Printer MIB. This mapping gives yet another way to access the same information that has already been validated and deployed using SNMP and Printer MIB technologies. It is expected that printer vendors that already support the Printer MIB and IPP/1.0 will find the implementation of the mapping defined in this document to be trivial with almost no additional overhead (i.e., no additional memory or processing resources).

The basic approach for this mapping is to define a simple, non-table driven, algorithm for converting an attribute name to an SNMP OID and for converting an attribute group name to a row, column, or table in the MIB. Then the MIB objects can be retrieved using the Get-Printer-Attributes request by specifying the attribute name or attribute group name in the "requested-attributes" Operation attribute. In order to be able to access each device when an IPP Printer object supports more than one device, a "which-device" Operation attribute MAY be supplied by the client. If the IPP Printer object only supports one device, the "which-device" Operation attribute NEED NOT be supported by the IPP Printer and NEED NOT be supplied by a client in a request.

The following Printer MIB Tables are mapped to IPP object types:

Printer MIB Table IPP table number (t)prtGeneral 5


6

63

64

65

66

67

68

69

70

71

72

73

7475

76

77

78

79

80

81

82

83

84

8586

87

88

89

90

91

92

93

9495

96

97

98

99100

7

8


prtCover 6prtLocalization 7Input 8Output 9Marker 10MarkerSupplies 11MarkerColorant 12MediaPath 13Channel 14Interpreter 15ConsoleDisplayBuffer 16ConsoleLights 17Alert 18Finisher (future) 19future Printer MIB table additions … ??

In addition, references to external tables (external to the Printer MIB itself) are not mapped (such as the Host Resources MIB and the Interfaces MIB). Instead, the Model introduces new "device-state" and "device-state-reasons" attributes which represents the state of the Device. These states and reasons are a subset of the values of the IPP Printer "printer-state" and "printer-state-reasons" attributes. These attributes provide a simpler state representation than the Host Resources MIB.

A new object type, not part of the existing Printer MIB or its tables is introduced. This object type is called "medium". This object type is introduced to support the idea of medium characteristic attributes for both "ready" and "supported" media. The Printer MIB is only concerned with "ready" media (media loaded in one of the input trays). The attributes of medium objects are requested using an algorithmic naming scheme that includes the medium characteristic attribute and the medium instance name. For example, "medium-weight-iso-a4-white"

Additional objects can be added in the future, such as start-sheets, fonts, forms, etc., using a similar attribute naming scheme.

2. Printer object and the Device object

This document adds the semantics of the Device object to the IPP model, including a query interface. The Device object is represented in the IPP/1.0 Model and Semantics document, but without any defined interface. From the Internet Printing Protocol/1.0 Model and Semantics document we have the following illustrations of the IPP Printer object and its relationship to devices:


9

101

102

103

104

105

106107

108

109

110

111

112

113114

115

116

117

118

119

120

121122

10

11


Since a Printer object is an abstraction of a generic document output device and print service provider, a Printer object could be used to represent any real or virtual device with semantics consistent with the Printer object, such as a fax device, an imager, or even a CD writer.

Some examples of configurations supporting a Printer object include:

1) An output device, with no spooling capabilities2) An output device, with a built-in spooler3) A print server supporting IPP with one or more associated output devices

3a) The associated output devices might or might not be capable of spooling jobs3b) The associated output devices might or might not support IPP

The following figures show some examples of how Printer objects can be realized on top of various distributed printing configurations. The embedded case below represents configurations 1 and 2. The hosted and fan-out figures below represent configuration 3.

Legend:


12

123

124

125

126

127

128

129

130

131132

133

134

135

136137

13

14


##### indicates a Printer object which is either embedded in an output device or is hosted in a server. The Printer object might or might not be capable of queuing/spooling.

any indicates any network protocol or direct connect, including IPP

embedded printer: output device +---------------+ O +--------+ | ########### |/|\ | client |------------IPP------------># Printer # |/ \ +--------+ | # Object # | | ########### | +---------------+

hosted printer: +---------------+ O +--------+ ########### | |/|\ | client |--IPP--># Printer #-any->| output device |/ \ +--------+ # Object # | | ########### +---------------+

+---------------+fan out: | | +-->| output device | any/ | | O +--------+ ########### / +---------------+/|\ | client |-IPP-># Printer #--*/ \ +--------+ # Object # \ +---------------+ ########### any\ | | +-->| output device | | | +---------------+


15

138

139

140

141142

143

144145

146

147

148

149

150

151

152

153

154155

156

157

158

159

160

161

162

163164

165

166

167

168

169

170

171

172

173

174

175

176177

178

16

17


3. Object Relationships

This document introduces the Device object and the Medium object. Their object relationship to the IPP Printer object is shown below: +-------------------+ | Printer | +--+----------------+ | | +-------------------+ +-| Device | | +-------------------+ + | +-------------------+ +-| Medium | | +-------------------+

Figure 1 illustrates the containment relationship. All IPP Sub-Unit objects are contained by an IPP Printer object.

ISSUE: Why a containment relationship for the Device object? Would association be good enough?

ISSUE: Can a Device object be controlled by more than one IPP Printer object? I think yes, so we need to show.

4. Issues Resolved in the Mapping

Several issues must be reconciled when supporting the Printer MIB tables as IPP attributes contained by an IPP Printer object.

4.1 Terminology

IPP Object Type (or just Object Type): The IPP Model document uses this term to describe the attributes and operations associated with a modeled entity. In other OO contexts, the term "class" is used.

IPP Object: The instantiation of an IPP Object Type. Each IPP Object instance has a distinct name using the IPP 'name' attribute syntax.


18

179

180

181182

183

184

185

186

187

188

189

190

191

192193

194

195

196197

198199

200

201

202

203

204

205

206

207

208

209

210

211

19

20


ISSUE: Are these two above terms still needed?

MIB Object: A cell in a MIB table - maps to an attribute in the IPP model.

MIB Table: A set of rows and columns in a MIB table.

4.2 Input objects and Media objects

IPP uses "media-ready" and "media-supported" attributes in order to identify what media is ready and supported, respectively. The Printer MIB does not contain the notion of a MediaTable. A separate descriptive object is useful for each media type when characteristics such as size, weight, color, grain, transparency, etc. need to be associated with the media. The Printer MIB chooses to associate these characteristics with the each row in the InputTable. The reasoning behind this decision is found in the Printer MIBs stated objective of only returning "ready" information (not "supported" type information).

To rationalize these two different models, the Medium object is introduced as a new object and an Input object already contains a named reference to a Medium object (prtInputMediaName). The Medium object which has all the characteristics about that instances (size, color, weight, etc.). The set of "media- ready" is the set of Medium objects referenced by Input objects. In addition, the following Printer MIB objects in the Input object are duplicated in the Medium Object:

prtInputMediaWeight "medium-weight-i"prtInputMediaType "medium-type-i"prtInputMediaColor "medium-color-i"prtInputMediaFormParts "medium-form-parts-i"

where i is a medium instance name, such as 'iso-a4-white', so that the full IPP attribute name is:

"medium-weight-iso-a4-white"

4.3 Interpreter Object vs. Document Format

IPP uses a MIME media type ('mimeMediaType') to identify the "document-formats-supported" by a Printer and the format of any documents supplied to the Printer. The Printer MIB uses rows the Interpreter Table with the following MIB Objects:

prtInterpreterLangFamilyprtInterpreterLangLevelprtInterpreterLangVersion


21

212

213

214

215

216

217

218

219

220

221222

223

224

225

226

227228

229

230

231

232233

234

235

236237

238

239

240

241242

243

244

245246

22

23


If an IPP Printer object supports both the "document-format" Job Template attribute and one or more contained Interpreter objects, then the implementation for that IPP Printer object MUST correctly map between the two forms of representing the PDLs that are supported.

4.4 Scope Rules

The existing Get-Printer-Attributes operation will be used to query ANY and/or ALL Device objects contained by an IPP Printer object. This operation can be used to query:

1. All tables in the Printer MIB.2. All MIB tables of a certain type (all Input or Output objects)3. A specific row in the Printer MIB (Input object "tray 1")4. A specific column in the Printer MIB (Input media names for all the input trays)5. A specific cell in the Printer MIB (Input media name for tray 1)

4.5 MIB Object names vs. IPP Attribute names

All MIB object names follow the ASN.1 naming convention of "prt" followed by the some string of multiple words or abbreviations with each word or abbreviation being all lower-case letters and except for an initial upper-case letter. For example: "prtInputMediaType".

All IPP attribute names are special keywords (all lowercase letters and digits, starting with a letter and being separated by a ‘-'). The special characters "_" and "." can also be included. For example: "document-format-supported", "prt-att-8-12-3", or "mib-1.3.6.1.2.1.43.8.2.1.12.1.3".

4.5.1 Rules for IPP attribute names and group names from Printer MIB Object names

The following rules will apply in creating IPP attribute names and attribute group names from Printer MIB Object names:

1. The attribute name will begin with "prt-".2. The rest of the words or abbreviations in the MIB object name (after the initial "prt") will be separated by a ‘-' 3. The remainder of the name will be decimal numbers separated by "-" to indicate table numbers, column numbers and row numbers.

For example: prtInputMediaName for the 3rd tray becomes "prt-att-8-12-3"

For IPP attribute names from any MIB Object names:


24

247

248

249250

251

252

253254

255

256

257

258

259260

261

262

263

264265

266

267

268269

270

271

272273

274

275

276

277

278279

280281

282

25

26


1. The attribute name will begin with "mib-".2. The rest of the attribute name will be the decimalized OBJECT IDENTIFIER of the Object in the MIB.

For example: "prtInputMediaName" for device 10 tray 3 becomes:

"mib-1.3.6.1.2.1.43.8.2.1.12.10.3""

4.5.2 Attribute names for use in "requested-attributes" Operation attribute

The following are attribute names that can be values of the "requested-attributes" Operation attributes in a Get-Printer-Attributes request:

'mib-x' specifies a single object within any MIB, where x is the full decimalized OBJECT IDENTIFIER (OID). For example, the attribute name 'mib-1.3.6.1.2.1.43.8.2.1.12.1.3' identifies the prtInputMediaName MIB object for the third input tray in device 1. These attribute names are not restricted to the Printer MIB, so that any MIB, including private MIBs may be accessed. In other words, the IPP Printer object has the attribute:

mib-1.3.6.1.2.1.43.8.2.1.12.1.3 (name (127))

The Get-Printer-Attributes response for each requested attribute (that is supported) consists of the attribute name and the value, i.e., the attribute name: 'mib-1.3.6.1.2.1.43.8.2.1.12.1.3' and the text string value, say, "iso-a4-white".

'prt-att-t-c-r' specifies a single object in the Printer MIB [prtmib], where t is the table number, c is the column number, and r is the row number. For example, the attribute name 'prt-att-8-12-3' identifies the prtInputMediaName MIB object for the third input tray in the specified device. These attribute names are restricted to the Printer MIB. In other words, the IPP Printer object has the attribute:

prt-att-8-12-3 (name (127))

The Get-Printer-Attributes response for each requested attribute (that is supported) consists of the attribute name and the value, i.e., the attribute name: 'prt-att-8-12-3' and the text string value, say, "iso-a4-white".


27

283

284

285

286287

288289

290291

292

293

294

295296

297

298

299

300

301

302

303

304

305

306

307308

309

310

311

312

313

314

315

316

317

318

319320

28

29


4.5.3 Attribute group names for use in "requested-attributes" Operation attribute

In addition to the above attribute names, the following attribute group names are defined to represent a group of attributes:

'prt-col-t-c' specifies a single column in the Printer MIB, where t is the table number and c is the column number. For example, the attribute group name 'prt-col-8-12' identifies the prtInputMediaName MIB object for all input trays in the specified device. Thus the client can request all of the values of a single input tray attribute by supplying a single column group name.

The Get-Printer-Attributes response for a requested column attribute group (that is supported) consists of the set of attribute names and their values in increasing attribute name order, i.e., the response to the 'prt-col-8-12' attribute group is:

'prt-att-8-12-1' and the first tray's value, say, "letter-white", 'prt-att-8-12-2' and the second tray's value, say, "letter-transparency", 'prt-att-8-12-3' and the third tray's value, say, "iso-a4-white"

'prt-row-t-r' specifies a single row in the Printer MIB, where t is the table number and r is the row number. For example, the attribute group name 'prt-row-8-3' identifies the entire third row of the Input table, i.e., all the columns that are supported for the third input tray. Thus the requester can request all of the attributes of a specified input tray by supplying a single row group name.

The Get-Printer-Attributes response for a requested row attribute group (that is supported) consists of the set of attribute names and their values in increasing attribute name order, i.e., the response to the 'prt-row-8-3' attribute group is:

'prt-att-8-2-3' and the 3rd tray's prtInputType, say, sheetFeedManual(5), 'prt-att-8-3-3' and the 3rd tray's prtInputDimUnit, say, micrometers(4), ... 'prt-att-8-12-3' and the 3rd tray's prtInputMediaName, say, 'iso-a4-white' ...

'prt-tab-t' specifies an entire table in the Printer MIB, where t is the table number. For example, the attribute group name 'prt-tab-8' identifies the entire Input table, i.e., all the rows and columns that are supported for the Input table. Thus the requester can request all of the attributes of all the input trays by supplying a single table group name.

The Get-Printer-Attributes response for a requested table attribute group (that is supported)


30

321

322

323324

325

326

327

328

329

330

331

332

333

334

335

336

337338

339

340

341

342

343

344

345

346

347

348

349

350

351

352

353354

355

356

357

358

359

360

31

32


consists of the set of attribute names and their values in increasing attribute name order, i.e., the response to the 'prt-tab-8' attribute group is:

'prt-att-8-2-1' and the 1st tray's prtInputType, say, sheetFeedManual(5), 'prt-att-8-2-2' and the 2nd tray's prtInputType, say, sheetFeedManual(5), 'prt-att-8-2-3' and the 3rd tray's prtInputType, say, sheetFeedManual(5), 'prt-att-8-3-1' and the 1st tray's prtInputDimUnit, say, micrometers(4), 'prt-att-8-3-2' ... ... 'prt-att-8-12-3' and the 3rd tray's prtInputMediaName, say, 'iso-a4-white' ...

'prt-tab-all' specifies the entire Printer MIB. Each attribute is returned separately in increasing attribute name order.

4.6 Mapping of SMI data types to IPP syntax types

The following rules apply:

1. ‘Interger32' and ‘Counter32' just map to ‘integer"2. ‘OCTET STRING' generally maps to ‘text', however some may map to ‘name' and some may map to ‘octetString'3. ‘Prt<whatever>TC' maps to ‘enum'4. ‘presentOnOff' is just a special TC and it maps to ‘enum' as well

5. New "which-device" Operation attribute for the Get-Printer-Attributes operation

The following new (post IPP/1.0) "which-device" Operation attribute is introduced for use with the existing Get-Printer-Attributes operation.:

"which-device" (name) :The client OPTIONALLY supplies this attribute. The Printer object MUST support this attribute, if it supports more than one device and supports the IPP attribute and attribute group names for Printer MIB access. This attribute is useful to select which device for an IPP Printer object that supports more than on Device object instance.


33

361

362

363

364

365

366

367

368

369

370

371372

373

374375

376

377378

379

380

381

382

383384

385

386

387

388389

390

391

392

393

394395

34

35


If the client omits this attribute, but requests attributes from the Printer MIB and the Printer supports multiple devices, the Printer object SHALL select a particular Device in an implementation-dependent manner.

If the client supplies a value for the "which-device" Operation attribute that is not supported by the Printer, i.e., is not among the values of the Printer object's "devices-supported" attribute, the Printer object SHALL reject the operation and return the 'client-error-attributes-or-values-not-supported' status code.

5.1 New "devices-supported" Printer attribute

The following description is for the new "devices-supported" Printer attribute:

devices-supported (1setOf name)

This OPTIONAL Printer attribute identifies the devices that this IPP Printer supports.

5.2 New "device-state" Device attribute

Specifies the state of the Device. Contains a subset of the enum values of the "printer-state" Printer attribute.

5.3 New "device-state-reasons" Device attribute

Specifies the state reasons of the Device. Contains a subset of the enum values of the "printer-state" Printer attribute.

6. Conformance

TBD

6.1 Client Conformance Requirements

TBD


36

396

397

398399

400

401

402

403404

405

406407

408409

410411

412

413

414415

416

417

418419

420

421

422

423

37

38


6.2 Server Conformance Requirements

TBD

6.2.1 Extensions

TBD

7. Security Considerations

TBD


39

424

425

426

427

428

429

430

40

41


8. Appendix

This Appendix lists all of the Printer MIB objects and their data types, table and column number, and their equivalent IPP attribute name and attribute syntax. IPP Device object types are defined in the same way as other IPP object types: for each type, all known attributes are listed and qualified.

It is OPTIONAL for an IPP Printer to support any Device object. However, if the Printer object supports the functionality or physical characteristics corresponding the appropriate Table in the MIB, then the Printer object SHOULD implement support for that (those) corresponding attributes and attribute groups.

8.1 The General Table (5)

prtGeneralConfigChanges Counter32 prtGeneralCurrentLocalization Integer32, prtGeneralReset PrtGeneralResetTC, prtGeneralCurrentOperator OCTET STRING, prtGeneralServicePerson OCTET STRING, prtInputDefaultIndex Integer32, prtOutputDefaultIndex Integer32, prtMarkerDefaultIndex Integer32, prtMediaPathDefaultIndex Integer32, prtConsoleLocalization Integer32 prtConsoleNumberOfDisplayLines Integer32, prtConsoleNumberOfDisplayChars Integer32, prtConsoleDisable INTEGER, prtAuxiliarySheetStartupPage PresentOnOff, prtAuxiliarySheetBannerPage PresentOnOff, prtGeneralPrinterName OCTET STRING, prtGeneralSerialNumber OCTET STRING, prtAlertCriticalEvents Counter32, prtAlertAllEvents Counter32

These map to:


42

431

432

433

434435

436

437

438

439440

441

442

443

444

445

446

447

448

449

450

451

452

453

454

455

456

457

458

459

460

461462

463464

43

44


prt-att-5-1(integer(0:MAX) prt-5-2(integer(1:65535) prt-5-3(enum) prt-5-4(text(127)) prt-5-5(text(127)) ...

8.2 Cover (6)

prtCoverDescription OCTET STRING, prtCoverStatus PrtCoverStatusTC

8.3 Localization (7)

8.4 Console Display Buffer (16)

prtConsoleDisplayBufferText OCTET STRING

This maps to:

prt-att-6-

8.5 Channel(14)

prtChannelType PrtChannelTypeTC, prtChannelProtocolVersion OCTET STRING, prtChannelCurrentJobCntlLangIndex Integer32, prtChannelDefaultPageDescLangIndex Integer32, prtChannelState PrtChannelStateTC, prtChannelIfIndex Integer32, prtChannelStatus PrtSubUnitStatusTC, prtChannelInformation OCTET STRING


45

465

466

467

468

469

470

471

472

473474

475

476

477478

479480

481482

483

484

485

486

487

488

489

490

491492

46

47


8.6 Input (8)

prtInputType PrtInputTypeTC, prtInputDimUnit PrtMediaUnitTC, prtInputMediaDimFeedDirDeclared Integer32, prtInputMediaDimXFeedDirDeclared Integer32, prtInputMediaDimFeedDirChosen Integer32, prtInputMediaDimXFeedDirChosen Integer32, prtInputCapacityUnit PrtCapacityUnitTC, prtInputMaxCapacity Integer32, prtInputCurrentLevel Integer32, prtInputStatus PrtSubUnitStatusTC, prtInputMediaName OCTET STRING, prtInputName OCTET STRING, prtInputVendorName OCTET STRING, prtInputModel OCTET STRING, prtInputVersion OCTET STRING, prtInputSerialNumber OCTET STRING, prtInputDescription OCTET STRING, prtInputSecurity PresentOnOff, prtInputMediaWeight Integer32, prtInputMediaType OCTET STRING, prtInputMediaColor OCTET STRING, prtInputMediaFormParts Integer32, prtInputMediaLoadTimeout Integer32, prtInputNextIndex Integer32


48

493

494

495

496

497

498

499

500

501

502

503

504

505

506

507

508

509

510

511

512

513

514

515

516

517518

49

50


8.7 Interpreter (15)

prtInterpreterLangFamily PrtInterpreterLangFamilyTC, prtInterpreterLangLevel OCTET STRING, prtInterpreterLangVersion OCTET STRING, prtInterpreterDescription OCTET STRING, prtInterpreterVersion OCTET STRING, prtInterpreterDefaultOrientation PrtPrintOrientationTC, prtInterpreterFeedAddressability Integer32, prtInterpreterXFeedAddressability Integer32, prtInterpreterDefaultCharSetIn CodedCharSet, prtInterpreterDefaultCharSetOut CodedCharSet, prtInterpreterTwoWay PrtInterpreterTwoWayTC

8.8 Console Lights (17)

prtConsoleOnTime Integer32, prtConsoleOffTime Integer32, prtConsoleColor PrtConsoleColorTC, prtConsoleDescription OCTET STRING

8.9 Marker (10)

prtMarkerMarkTech PrtMarkerMarkTechTC, prtMarkerCounterUnit PrtMarkerCounterUnitTC, prtMarkerLifeCount Counter32, prtMarkerPowerOnCount Counter32, prtMarkerProcessColorants Integer32, prtMarkerSpotColorants Integer32, prtMarkerAddressabilityUnit INTEGER, prtMarkerAddressabilityFeedDir Integer32, prtMarkerAddressabilityXFeedDir Integer32, prtMarkerNorthMargin Integer32, prtMarkerSouthMargin Integer32, prtMarkerWestMargin Integer32, prtMarkerEastMargin Integer32, prtMarkerStatus PrtSubUnitStatusTC


51

519

520

521

522

523

524

525

526

527

528

529

530531

532

533

534

535

536537

538

539

540

541

542

543

544

545

546

547

548

549

550

551

552553

52

53


8.10 Marker Colorant (12)

prtMarkerColorantMarkerIndex Integer32, prtMarkerColorantRole PrtMarkerColorantRoleTC, prtMarkerColorantValue OCTET STRING, prtMarkerColorantTonality Integer32

8.11 Marker Supplies (11)

prtMarkerSuppliesMarkerIndex Integer32, prtMarkerSuppliesColorantIndex Integer32, prtMarkerSuppliesClass PrtMarkerSuppliesClassTC, prtMarkerSuppliesType PrtMarkerSuppliesTypeTC, prtMarkerSuppliesDescription OCTET STRING, prtMarkerSuppliesSupplyUnit PrtMarkerSuppliesSupplyUnitTC, prtMarkerSuppliesMaxCapacity Integer32, prtMarkerSuppliesLevel Integer32

8.12 Media Path (13)

prtMediaPathMaxSpeedPrintUnit PrtMediaPathMaxSpeedPrintUnitTC, prtMediaPathMediaSizeUnit PrtMediaUnitTC, prtMediaPathMaxSpeed Integer32, prtMediaPathMaxMediaFeedDir Integer32, prtMediaPathMaxMediaXFeedDir Integer32, prtMediaPathMinMediaFeedDir Integer32, prtMediaPathMinMediaXFeedDir Integer32, prtMediaPathType PrtMediaPathTypeTC, prtMediaPathDescription OCTET STRING, prtMediaPathStatus PrtSubUnitStatusTC

8.13 Medium (needs more work)

From Mapping:

prt-sub-unit-nameprt-sub-unit-index

From DPA:


54

554

555

556

557

558559

560

561

562

563

564

565

566

567

568569

570

571

572

573

574

575

576

577

578

579

580581

582

583584

585

586587

588

55

56


medium-associated-media medium-assured-reproduction-area medium-dimensions medium-grain medium-holes-axis-offset medium-holes-count medium-holes-diameter medium-holes-locations medium-holes-reference-edge medium-realization medium-sides medium-size medium-tooth


57

589

590

591

592

593

594

595

596

597

598

599

600

601

602603

58

59


8.14 Output (9)

prtOutputType PrtOutputTypeTC, prtOutputCapacityUnit PrtCapacityUnitTC, prtOutputMaxCapacity Integer32, prtOutputRemainingCapacity Integer32, prtOutputStatus PrtSubUnitStatusTC, prtOutputName OCTET STRING, prtOutputVendorName OCTET STRING, prtOutputModel OCTET STRING, prtOutputVersion OCTET STRING, prtOutputSerialNumber OCTET STRING, prtOutputDescription OCTET STRING, prtOutputSecurity PresentOnOff, prtOutputDimUnit PrtMediaUnitTC, prtOutputMaxDimFeedDir Integer32, prtOutputMaxDimXFeedDir Integer32, prtOutputMinDimFeedDir Integer32, prtOutputMinDimXFeedDir Integer32, prtOutputStackingOrder PrtOutputStackingOrderTC, prtOutputPageDeliveryOrientation PrtOutputPageDeliveryOrientationTC, prtOutputBursting PresentOnOff, prtOutputDecollating PresentOnOff, prtOutputPageCollated PresentOnOff, prtOutputOffsetStacking PresentOnOff

8.15 Alert (18)

prtAlertSeverityLevel PrtAlertSeverityLevelTC, prtAlertTrainingLevel PrtAlertTrainingLevelTC, prtAlertGroup PrtAlertGroupTC, prtAlertGroupIndex Integer32, prtAlertLocation Integer32, prtAlertCode PrtAlertCodeTC, prtAlertDescription OCTET STRING, prtAlertTime TimeTicks


60

604

605

606

607

608

609

610

611

612

613

614

615

616

617

618

619

620

621

622

623

624

625

626

627

628629

630

631

632

633

634

635

636

637

638639

640

61

62


9. References

[IPP-MOD]

[prtmib]

10. Copyright Notice

None,

11. Author's Address

Scott A. Isaacson (Editor)Novell, Inc.122 E 1700 SProvo, UT 84606

Phone: 801-861-7366Fax: 801-861-2517e-mail: [email protected]

Tom HastingsXerox Corporation701 S. Aviation Blvd.El Segundo, CA 90245

Phone: 310-333-6413Fax: 310-333-5514e-mail: [email protected]

Robert HerriotSun Microsystems Inc.901 San Antonio.Road, MPK-17Palo Alto, CA 94303

Phone: 650-786-8995Fax: 650-786-7077


63

641

642643

644645

646

647

648

649

650

651

652653

654

655

656657

658

659

660

661662

663

664

665666

667

668

669

670671

672

673

64

65


e-mail: [email protected]


66

674675

676

67

68

proposed internet-draft€¦ · web view4.13 output 20. 4.14 alert 21. 5. new...

Documents