ftp.pwg.org€¦ · Web view28.11.2012 · The IEEE-ISTO takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to

November 28, 2012Working Draft

The Printer Working Group

IPP FaxOut Service

Status: Interim

Abstract: This standard defines an IPP extension to support the PWG Semantic Model FaxOut service over IPP.

This document is a PWG Working Draft. For a definition of a "PWG Working Draft", see: ftp://ftp.pwg.org/pub/pwg/general/pwg-process30.pdf

This document is available electronically at:

ftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20121128.docxftp://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippfaxout10-20121128.pdf

Copyright © 2011-2012 The Printer Working Group. All rights reserved.

12345678910

11

12

13

14

1516

1718

19

2021

22

Working Draft – IPP FaxOut Service November 28, 2012

Copyright © 2011-2012 The Printer Working Group. All rights reserved.

This document may be copied and furnished to others, and derivative works that comment on, or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice, this paragraph and the title of the Document as referenced below are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the IEEE-ISTO and the Printer Working Group, a program of the IEEE-ISTO.

Title: IPP FaxOut Service

The IEEE-ISTO and the Printer Working Group DISCLAIM ANY AND ALL WARRANTIES, WHETHER EXPRESS OR IMPLIED INCLUDING (WITHOUT LIMITATION) ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

The Printer Working Group, a program of the IEEE-ISTO, reserves the right to make changes to the document without further notice. The document may be updated, replaced or made obsolete by other documents at any time.

The IEEE-ISTO takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights.

The IEEE-ISTO invites any interested party to bring to its attention any copyrights, patents, or patent applications, or other proprietary rights which may cover technology that may be required to implement the contents of this document. The IEEE-ISTO and its programs shall not be responsible for identifying patents for which a license may be required by a document and/or IEEE-ISTO Industry Group Standard or for conducting inquiries into the legal validity or scope of those patents that are brought to its attention. Inquiries may be submitted to the IEEE-ISTO by e-mail at: [email protected].

The Printer Working Group acknowledges that the IEEE-ISTO (acting itself or through its designees) is, and shall at all times, be the sole entity that may authorize the use of certification marks, trademarks, or other special designations to indicate compliance with these materials.

Use of this document is wholly voluntary. The existence of this document does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to its scope.

Page 2 of 26 Copyright © 2011-2012 The Printer Working Group. All rights reserved.

12

23

24252627282930

31

32333435

363738

3940414243

44454647484950

51525354

55565758

3


About the IEEE-ISTO

The IEEE-ISTO is a not-for-profit corporation offering industry groups an innovative and flexible operational forum and support services. The IEEE-ISTO provides a forum not only to develop standards, but also to facilitate activities that support the implementation and acceptance of standards in the marketplace. The organization is affiliated with the IEEE (http://www.ieee.org/) and the IEEE Standards Association (http://standards.ieee.org/).

For additional information regarding the IEEE-ISTO and its industry programs visit:

http://www.ieee-isto.org

About the IEEE-ISTO PWG

The Printer Working Group (or PWG) is a Program of the IEEE Industry Standards and Technology Organization (ISTO) with member organizations including printer manufacturers, print server developers, operating system providers, network operating systems providers, network connectivity vendors, and print management application developers. The group is chartered to make printers and the applications and operating systems supporting them work together better. All references to the PWG in this document implicitly mean “The Printer Working Group, a Program of the IEEE ISTO.” In order to meet this objective, the PWG will document the results of their work as open standards that define print related protocols, interfaces, procedures and conventions. Printer manufacturers and vendors of printer related software will benefit from the interoperability provided by voluntary conformance to these standards.

In general, a PWG standard is a specification that is stable, well understood, and is technically competent, has multiple, independent and interoperable implementations with substantial operational experience, and enjoys significant public support.

For additional information regarding the Printer Working Group visit:

http://www.pwg.org

Contact information:

The Printer Working Groupc/o The IEEE Industry Standards and Technology Organization445 Hoes LanePiscataway, NJ 08854USA


45

59

606162636465

66

67

68

6970717273747576777879

808182

83

84

85

868788899091

6

http://www.ieee-isto.org/

http://standards.ieee.org/)

http://www.ieee.org/


About the Internet Printing Protocol Work Group

The Internet Printing Protocol (IPP) working group has developed a modern, full-featured network printing protocol, which is now the industry standard. IPP allows a print client to query a printer for its supported capabilities, features, and parameters to allow the selection of an appropriate printer for each print job. IPP also provides job information prior to, during, and at the end of job processing.

For additional information regarding IPP visit:

http://www.pwg.org/ipp/

Implementers of this specification are encouraged to join the IPP mailing list in order to participate in any discussions of the specification. Suggested additions, changes, or clarification to this specification, should be sent to the IPP mailing list for consideration.


78

92

9394959697

98

99

100101102

9


Table of Contents1. Introduction......................................................................................................................72. Terminology.....................................................................................................................7

2.1 Conformance Terminology.........................................................................................72.2 Printing Terminology..................................................................................................72.3 Acronyms and Organizations.....................................................................................8

3. Requirements..................................................................................................................83.1 Rationale for the IPP FaxOut Service........................................................................83.2 Use Cases.................................................................................................................8

3.2.1 Fax from an Application.......................................................................................83.2.2 Fax to Multiple Recipients with Retry and Failure................................................93.2.3 Fax Using a Resource-Constrained MFD............................................................9

3.3 Out of Scope..............................................................................................................93.4 Design Requirements................................................................................................9

4. FaxOut Service Definition..............................................................................................104.1 FaxOut Job Processing............................................................................................10

4.1.1 Spooling Printers...............................................................................................104.1.2 Streaming Printers.............................................................................................10

4.2 IPP Operations.........................................................................................................104.3 IPP Printer Description Attributes.............................................................................114.4 IPP Operation Attributes..........................................................................................124.5 IPP Job Template Attributes....................................................................................134.6 IPP Job Description Attributes.................................................................................13

5. Document Formats........................................................................................................146. New Attributes...............................................................................................................14

6.1 Job Template Attributes...........................................................................................146.1.1 confirmation-sheet-print (boolean).....................................................................146.1.2 cover-sheet-info (collection | no-value)..............................................................156.1.3 destination-uris (1setOf collection)....................................................................166.1.4 number-of-retries (integer(0:MAX))...................................................................166.1.5 retry-interval (integer(1:MAX))...........................................................................166.1.6 retry-time-out (integer(1:MAX))..........................................................................16

6.2 Job Description Attributes........................................................................................176.2.1 destination-statuses (1setOf collection).............................................................17

6.3 Printer Description Attributes...................................................................................176.3.1 confirmation-sheet-print-default (boolean).........................................................176.3.2 cover-sheet-info-default (collection | no-value)..................................................186.3.3 cover-sheet-info-supported (1setOf type2 keyword)..........................................186.3.4 destination-uri-schemes-supported (1setOf uriScheme)...................................186.3.5 logo-uri-schemes-supported (1setOf uriScheme)..............................................186.3.6 multiple-destination-uris-supported (boolean)...................................................186.3.7 number-of-retries-default (integer(0:MAX)).......................................................186.3.8 number-of-retries-supported (rangeOfInteger(0:MAX)).....................................186.3.9 printer-fax-log-uri (uri)........................................................................................186.3.10 printer-fax-modem-info (1setOf text(MAX)).....................................................186.3.11 printer-fax-modem-name (1setOf name(MAX))...............................................19


1011

103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148

12


6.3.12 printer-fax-modem-number (1setOf uri)...........................................................196.3.13 retry-interval-default (integer(1:MAX)).............................................................196.3.14 retry-interval-supported (rangeOfInteger(1:MAX))...........................................196.3.15 retry-time-out-default (integer(1:MAX))............................................................196.3.16 retry-time-out-supported (rangeOfInteger(1:MAX)).........................................19

7. Additional Values and Semantics for Existing Attributes...............................................197.1 ipp-features-supported (1setOf type2 keyword).......................................................197.2 job-state-reasons (1setOf type2 keyword)...............................................................19

8. Conformance Requirements..........................................................................................209. Internationalization Considerations................................................................................2010. Security Considerations...............................................................................................2011. IANA Considerations...................................................................................................21

11.1 Attribute Registrations............................................................................................2111.2 Attribute Value Registrations..................................................................................2211.3 Type2 enum Attribute Value Registrations.............................................................23

12. References..................................................................................................................2312.1 Normative References...........................................................................................2312.2 Informative References..........................................................................................24

13. Author's Address.........................................................................................................2514. Change History............................................................................................................26

14.1 November 28, 2012...............................................................................................2614.2 September 22, 2011..............................................................................................26

List of TablesTable 1 - Required Operations for FaxOut........................................................................10Table 2 - Required Printer Description Attributes..............................................................11Table 3 - Required Operation Attributes............................................................................12Table 4 - Required Job Template Attributes......................................................................13Table 5 - Required Job Description Attributes...................................................................13Table 2 - New "job-state-reasons" Keyword Values..........................................................19


1314149150151152153154155156157158159160161162163164165166167168169170171172173

174175176177178179180181182

15


1. IntroductionThis document specifies an IPP binding of the PWG FaxOut Service Semantic Model and Service Interface [PWG5108.05]. Because outgoing facsimile and printing share the same general output model, this binding is essentially an extension of IPP that defines a small number of new attributes specific to facsimile.

2. Terminology

2.1 Conformance Terminology

Capitalized terms, such as MUST, MUST NOT, RECOMMENDED, REQUIRED, SHOULD, SHOULD NOT, MAY, and OPTIONAL, have special meaning relating to conformance as defined in Key words for use in RFCs to Indicate Requirement Levels [RFC2119]. The term CONDITIONALLY REQUIRED is additionally defined for a conformance requirement that applies to a particular capability or feature.

2.2 Printing Terminology

Normative definitions and semantics of printing terms are imported from IETF Printer MIB v2 [RFC3805], IETF Finisher MIB [RFC3806], and IETF Internet Printing Protocol/1.1: Model and Semantics [RFC2911].

This document also defines the following terms in order to specify unambiguous conformance requirements:

Client: Initiator of outgoing IPP session requests and sender of outgoing IPP operation requests (Hypertext Transfer Protocol -- HTTP/1.1 [RFC2616] User Agent).

Document: An object created and managed by a Printer that contains the description, processing, and status information. A Document object may have attached data and is bound to a single Job.

Job: An object created and managed by a Printer that contains description, processing, and status information. The Job also contains zero or more Document objects.

Job Description: Attributes supplied by the Client or end user including job processing instructions which are intended to override any Printer object defaults and/or instructions embedded within the document data (IPP Model and Semantics [RFC2911]).

Job Template: Attributes describing the Job object's identification, state, size, etc. (IPP Model and Semantics [RFC2911])

Job Ticket: The combination of Job Description and Job Template attributes.


1617

183

184185186187

188

189

190191192193194

195

196197198

199200

201202

203204205

206207

208209210

211212

213

18


Logical Device: a print server, software service, or gateway that processes jobs and either forwards or stores the processed job or uses one or more Physical Devices to render output.

Physical Device: a device that renders output (typically on paper.)

Printer: Listener for incoming IPP session requests and receiver of incoming IPP operation requests (Hypertext Transfer Protocol -- HTTP/1.1 [RFC2616] Server) that represents one or more Physical Devices or a Logical Device.

2.3 Acronyms and Organizations

IANA: Internet Assigned Numbers Authority, http://www.iana.org/

IETF: Internet Engineering Task Force, http://www.ietf.org/

ISO: International Organization for Standardization, http://www.iso.org/

PWG: Printer Working Group, http://www.pwg.org/

3. Requirements

3.1 Rationale for the IPP FaxOut Service

The Internet Printing Protocol Version 2.0 Second Edition [PWG5100.12] defines a collection of existing IPP specifications that form the basis for IPP/2.0.

The MFD Model and Common Semantics [PWG5108.1] defines a common semantic model and service interface for multi-function devices based on IPP.

The FaxOut Service Semantic Model and Service Interface v1.0 [PWG5108.05] defines the semantics and interfaces specific to outgoing facsimile.

The PWG Raster Format [PWG5102.4] defines simple page-based raster format for printing.

Therefore, this IPP FaxOut Service specification should support outgoing facsimile using IPP based on the semantics and interfaces defined by the FaxOut Service Semantic Model and Service Interface v1.0.

3.2 Use Cases

3.2.1 Fax from an Application

Jane wishes to send a contract to a customer via her multi-function device with facsimile capabilities. She opens the contract in her word processor, initiates a print operation,


1920214215216

217

218219220

221

222

223

224

225

226

227

228229

230231

232233

234235

236237238

239

240

241242

21


selects the facsimile service for her MFD, supplies the recipient's name, fax number, and a subject and message for the fax cover page, and then confirms the submission of the fax job. The document is then transformed as needed and queued on the MFD for sending. Jane is able to monitor the status of the transmission from her computer. Finally, her customer receives the fax with the contract.

3.2.2 Fax to Multiple Recipients with Retry and Failure

John needs to submit a printed report to several government entities using his multi-function device with facsimile capabilities. He opens the report program, initiates a print operation, selects the facsimile service for his MFD, supplies the recipient names, fax numbers, and a subject and message for the fax cover pages, and then confirms the submission of the fax job. John is able to monitor the status of the transmissions from his computer for each recipient. As the MFD sends the report to each recipient, it negotiates the necessary format and resolution of the transmission separately and without any action by John.

When a transmission error occurs for the first recipient, John is notified through the client user interface and the MFD automatically retries the transmission. The last recipient turned their fax machine off and so the MFD reports each failed transmission to John's computer and aborts the transmission after five failed attempts.

3.2.3 Fax Using a Resource-Constrained MFD

Mary has a MFD with facsimile capabilities but only enough memory to hold a single page of output in memory at any given time. When faxing, Mary's computer streams simple page-based raster data to the MFD, pausing and retrying as needed to allow the fax job to complete.

3.3 Out of Scope

The design of the client's user interface and the methods of performing facsimile are out of scope for this specification.

3.4 Design Requirements

The use cases in section 3.2 identify several design requirements:

1. FaxOut should closely mirror the semantic model for printing.2. The Client must be able to supply information for a cover page to be generated

by the Printer.3. The Client must be able to specify one or more recipients by name and telephone

number.4. The Printer must handle negotiation and conversion of documents for facsimile

when the receiving facsimile does not support the Client-supplied document data.


2223243244245246247

248

249250251252253254255256

257258259260

261

262263264265

266

267268

269

270

271272273274275276277

24


5. The Client must be able to stream basic page-based raster data and resubmit jobs when the Printer is unable to send the document to the recipient(s).

6. The Client must be able to monitor the status of transmission to each recipient.

4. FaxOut Service Definition

4.1 FaxOut Job Processing

From the Client's perspective, FaxOut jobs are largely processed the same way as a print job. Spooling Printers handle retransmission of whole jobs automatically while streaming Printers put the burden of retransmission on the Client.

One primary difference with FaxOut is that the output resolution and color space depends on the receiver of the fax job, and can be different for each destination. In order to simplify implementation and preserve the IPP model and semantics, Printers MUST support scaling and color space conversion of document data to match the negotiated facsimile image format at job processing time.

4.1.1 Spooling Printers

Printers that spool print jobs MUST automatically retry fax transmission and support multiple destination URIs.

4.1.2 Streaming Printers

Printers that can only stream print jobs to a single destination URI MUST support retransmission of the current page. When an error occurs that requires retransmission of larger portions of the job by the Client, Printers MUST move the job to the aborted state , add the appropriate keyword to the "job-state-reasons" Job Description attribute for the Job, and return the server-error-device-error status code to the Client.

4.2 IPP Operations

Table 1 lists the REQUIRED operations for a Printer. The Create-Job and Send-Document operations are required in order to support reliable job management (e.g., cancellation) during fax job submission, but Printers are not required to support multiple document jobs.

Table 1 - Required Operations for FaxOut

Code Operation Name Reference0x0002 Print-Job RFC 29110x0004 Validate-Job RFC 29110x0005 Create-Job RFC 29110x0006 Send-Document RFC 29110x0008 Cancel-Job RFC 2911


2526278279280

281

282

283284285

286287288289290

291

292293

294

295296297298299

300

301302303304

305

27


0x0009 Get-Job-Attributes RFC 29110x000A Get-Jobs RFC 29110x000B Get-Printer-Attributes RFC 29110x0039 Cancel-My-Jobs PWG 5100.110x003B Close-Job PWG 5100.11

4.3 IPP Printer Description Attributes

Table 2 lists the REQUIRED Printer Description attributes for a Printer.

Table 2 - Required Printer Description Attributes

Attribute Referencecharset-configured RFC 2911charset-supported RFC 2911color-supported RFC 2911compression-supported RFC 2911document-format-default RFC 2911document-format-supported RFC 2911generated-natural-language-supported RFC 2911ipp-extensions-supported PWG 5100.13ipp-versions-supported RFC 2911job-ids-supported PWG 5100.11media-bottom-margin-supported PWG 5100.13media-col-database PWG 5100.11media-col-default PWG 5100.3media-col-supported PWG 5100.3media-default RFC 2911media-left-margin-supported PWG 5100.13media-right-margin-supported PWG 5100.13media-size-supported PWG 5100.3media-supported RFC 2911media-top-margin-supported PWG 5100.13multiple-document-jobs-supported RFC 2911multiple-operation-timeout RFC 2911multiple-operation-timeout-action PWG 5100.13natural-language-configured RFC 2911operations-supported RFC 2911overrides-supported PWG 5100.6page-ranges-supported (note 1) RFC 2911pages-per-minute RFC 2911pages-per-minute-color RFC 2911print-quality-default RFC 2911print-quality-supported RFC 2911printer-alert PWG 5100.9printer-alert-description PWG 5100.9


2829

306

307

308

30


printer-config-change-date-time PWG 5100.13printer-config-change-time PWG 5100.13printer-device-id PWG 5107.2printer-geo-location PWG 5100.13printer-get-attributes-supported PWG 5100.13printer-icons PWG 5100.13printer-info RFC 2911printer-is-accepting-jobs RFC 2911printer-location RFC 2911printer-make-and-model RFC 2911printer-more-info RFC 2911printer-name RFC 2911printer-organization PWG 5100.13printer-organizational-unit PWG 5100.13printer-resolution-default RFC 2911printer-resolution-supported RFC 2911printer-state RFC 2911printer-state-change-date-time RFC 3995printer-state-change-time RFC 3995printer-state-message RFC 2911printer-state-reasons RFC 2911printer-up-time RFC 2911printer-uri-supported RFC 2911printer-uuid PWG 5100.13pwg-raster-document-resolution-supported PWG 5102.4pwg-raster-document-type-supported PWG 5102.4queued-job-count RFC 2911uri-security-supported RFC 2911uri-authentication-supported RFC 2911which-jobs-supported PWG 5100.11

Note 1: CONDITIONALLY REQUIRED for Printers that support the "application/openxps" or "application/pdf" MIME media types.

4.4 IPP Operation Attributes

Table 3 lists the REQUIRED operation attributes for a Printer.

Table 3 - Required Operation Attributes

Attribute Referencecompression RFC 2911document-format RFC 2911document-format-version PWG 5100.7document-name RFC 2911, PWG 5100.5first-index PWG 5100.13


3132

309310

311

312

313

33


first-job-id RFC 2911ipp-attribute-fidelity RFC 2911job-ids PWG 5100.11job-name RFC 2911last-document RFC 2911limit RFC 2911requesting-user-name RFC 2911requesting-user-uri PWG 5100.13which-jobs RFC 2911, PWG 5100.11

4.5 IPP Job Template Attributes

Table 4 lists the REQUIRED Job Template attributes for a Printer.

Table 4 - Required Job Template Attributes

Attribute Referenceconfirmation-sheet-print PWG 5100.FAXcopies (note 1) RFC 2911cover-sheet-info PWG 5100.FAXdestination-uris PWG 5100.FAXmedia RFC 2911media-col PWG 5100.3media-col.media-bottom-margin PWG 5100.13media-col.media-left-margin PWG 5100.13media-col.media-right-margin PWG 5100.13media-col.media-size PWG 5100.3media-col.media-top-margin PWG 5100.13multiple-document-handling (note 1) RFC 2911number-of-retries PWG 5100.FAXpage-ranges (note 1) RFC 2911print-quality RFC 2911printer-resolution RFC 2911retry-interval PWG 5100.FAXretry-timeout PWG 5100.FAX

Note 1: CONDITIONALLY REQUIRED for Printers that support the "application/openxps", "application/pdf", or "image/jpeg" MIME media types.

4.6 IPP Job Description Attributes

Table 5 lists the REQUIRED Job Description attributes for a Printer.

Table 5 - Required Job Description Attributes

Attribute Sourcecompression-supplied PWG 5100.7date-time-at-completed RFC 2911


3435

314

315

316

317318

319

320

321

36


date-time-at-creation RFC 2911date-time-at-processing RFC 2911destination-statuses PWG 5100.FAXdocument-format-supplied PWG 5100.7document-format-version-supplied PWG 5100.7document-name-supplied PWG 5100.7job-id RFC 2911job-impressions RFC 2911job-impressions-completed RFC 2911job-name RFC 2911job-originating-user-name RFC 2911job-printer-up-time RFC 2911job-printer-uri RFC 2911job-state RFC 2911job-state-message RFC 2911job-state-reasons RFC 2911job-uri RFC 2911job-uuid PWG 5100.13time-at-completed RFC 2911time-at-creation RFC 2911time-at-processing RFC 2911

5. Document FormatsPrinters MUST support documents conforming to the PWG Raster Format [PWG5102.4] ("image/pwg-raster"). IPP/2.1 and IPP/2.2 Printers MUST and IPP/2.0 Printers SHOULD support documents conforming to Document management — Portable document format — Part 1: PDF 1.7 [ISO32000] ("application/pdf"). IPP/2.0, IPP/2.1, and IPP/2.2 Printers are defined in IPP/2.0 Second Edition [PWG5100.12].

Printers SHOULD support documents conforming to the Open XML Paper Specification [ECMA388] ("application/openxps").

6. New Attributes

6.1 Job Template Attributes

6.1.1 confirmation-sheet-print (boolean)

The REQUIRED "confirmation-sheet-print" Job Template attribute specifies whether a confirmation sheet is printed when the Job reaches a terminating state.

6.1.1.1


3738

322

323324325326327

328329

330

331

332

333334

335

336

39


6.1.2 cover-sheet-info (collection | no-value)

The REQUIRED "cover-sheet-info" Job Template attribute specifies the information that is shown on the fax cover sheet sent to each recipient. The no-value value disables the Printer-generated cover sheet. The "cover-sheet-info-supported" Printer attribute list the member attributes that are supported by the Printer.

6.1.2.1 company-name (text(255))

The "company-name" member attribute provides the company or organization name to be shown on the cover page.

6.1.2.2 date-time (dateTime)

The "date-time" member attribute provides the date and time to be shown on the cover page.

6.1.2.3 from (text(255))

The "from" member attribute provides the name to be shown on the cover page.

6.1.2.4 logo (uri)

The "logo" member attribute provides a URI to a logo image to be shown on the cover page.

6.1.2.5 message (text(MAX))

The "message" member attribute provides freeform plain text to be shown on the cover page. Long lines are typically wrapped to fit within a message area on the cover page with newlines starting new paragraphs.

6.1.2.6 subject (text(255))

The "subject" member attribute provides a subject line to be shown on the cover page.

6.1.2.7 to (text(255))

The "to" member attribute provides a recipient name to be shown on the cover page.

6.1.2.8 cover-sheet-info-default (collection)

The default values supplied by the Printer if the client omits the "cover-sheet-info" Job Template attribute or any of its members. This value may be set by the Set-Printer-Attributes operation.


4041337

338339340341

342

343344

345

346347

348

349

350

351352

353

354355356

357

358

359

360

361

362363364

42


6.1.3 destination-uris (1setOf collection)

The REQUIRED "destination-uris" Job Template attribute specifies the recipients of the fax job. The destination is "tel" URI with optional pre- and post-dial strings of the form:

DialString = 1*(phonedigit / dtmf-digit / pause-character)pause-character = one-second-pause / wait-for-dial-toneone-second-pause = "p"wait-for-dial-tone = "w"dtmf-digit = "*" / "A" | "B" / "C" / "D" / “#”phonedigit = DIGIT / [ visual-separator ]visual-separator = "-" / "." / "(" / ")" / "'" / "(" / ")"

6.1.3.1 destination-uri (uri)

The REQUIRED "destination-uri" member attribute specifies the phone number to dial as a "tel" URI [RFC3966].

6.1.3.2 post-dial-string (text(127))

The "post-dial-string" member attribute specifies additional numbers to dial after the number specified by "destination-uri" has connected.

6.1.3.3 pre-dial-string (text(127))

The "pre-dial-string" member attribute specifies additional numbers to dial before the number specified by "destination-uri" has been dialed.

6.1.3.4 t33-subaddress (integer(0:MAX))

The "t33-subaddress" member attribute specifies additional numbers (typically an extension) to dial after any "post-dial-string" numbers have been sent.

6.1.4 number-of-retries (integer(0:MAX))

The REQUIRED "number-of-retries" Job Template attribute specifies the number of retries that will be performed in order to successfully transmit the job to the recipient. When specified, the Printer MUST try sending the document at least "number-of-retries + 1" times in order to successfully send it to the recipient.

6.1.4.1

6.1.4.2


4344365

366367

368369370371372373374

375

376377

378

379380

381

382383

384

385386

387

388389390391

392

393

394

395

45


6.1.5 retry-interval (integer(1:MAX))

The REQUIRED "retry-interval" Job Template attribute specifies the number of seconds the Printer will wait between subsequent retries.

6.1.5.1

6.1.5.2

6.1.6 retry-time-out (integer(1:MAX))

The REQUIRED "retry-time-out" Job Template attribute specifies the maximum number of seconds the Printer will wait to successfully negotiate a facsimile connection.

6.1.6.1

6.1.6.2

6.2 Job Description Attributes

6.2.1 destination-statuses (1setOf collection)

The REQUIRED "destination-statuses" Job attribute provides the transmission status of each recipient specified by the "destination-uris" Job Template attribute. This attribute MUST have the same cardinality (contain the same number of values) as the "destination-uris" attribute. The "i th" value in the "destination-statuses" attribute corresponds to the "i th" value in the "destination-uris" attribute.

6.2.1.1 destination-uri (uri)

The "destination-uri" member attribute specifies the destination telephone number as found in the corresponding Job Template attribute value.

6.2.1.2 images-completed (integer(0:MAX))

The "images-completed" member attribute specifies the number of images (sides) that have been successfully transmitted to the recipient.


4647396

397398

399

400

401

402

403

404405

406

407

408

409

410

411

412413414415416

417

418419

420

421422

48


6.2.1.3 transmission-status (type2 enum)

The "transmission-status" member attribute specifies the status of the transmission to the recipient. Table 6 lists the values that may be used and purposely mirrors the allowed "job-state" values.

Table 6 - "transmission-status" Enumeration Values

Value Symbolic Name and Description'3' 'pending': Job is in queue waiting to be sent'4' 'pending-retry': Job is in queue waiting to be retried'5' 'processing': Job is being sent'7' 'canceled': Job has been canceled'8' 'aborted': Job has been aborted'9' 'completed; Job has successfully been sent

6.3 Printer Description Attributes

6.3.1 confirmation-sheet-print-default (boolean)

The default value supplied by the Printer if the Client omits the "confirmation-sheet-print" Job Template attribute.This value may be set by the Set-Printer-Attributes operation.

6.3.2 cover-sheet-info-default (collection | no-value)

The REQUIRED "cover-sheet-info-default" Printer attribute provides the default value of the "cover-sheet-info" Job Template attribute. The no-value value disables the Printer-generated cover sheet.

6.3.3 cover-sheet-info-supported (1setOf type2 keyword)

The REQUIRED "cover-sheet-info-supported" Printer attribute lists the supported member attributes in the "cover-sheet-info" Job Template attribute. Printers MUST support the "date-time", "from", "subject", and "to" member attributes.

6.3.4 destination-uri-schemes-supported (1setOf uriScheme)

The REQUIRED "destination-rui-schemes-supported" Printer attribute lists the supported "destination-uri" URI schemes. Printers MUST support the "tel" URI scheme.

6.3.5 logo-uri-schemes-supported (1setOf uriScheme)

The "logo-uri-schemes-supported" Printer attribute lists the supported "logo" URI schemes. Printers that support the "logo" member attribute of the "cover-sheet-info" Job Template attribute MUST support the "logo-uri-schemes-supported" Printer attribute.


4950423

424425426

427

428

429

430431

432

433434435

436

437438439

440

441442

443

444445446

51


6.3.6 multiple-destination-uris-supported (boolean)

The REQUIRED "multiple-destination-uris-supported" Printer attribute specifies whether the Printer supports more than one "destination-uris" Job Template attribute value in a Job creation request.

6.3.7 number-of-retries-default (integer(0:MAX))

The default value supplied by the Printer if the Client omits the "number-of-retries" Job Template attribute. This value may be set by the Set-Printer-Attributes operation.

6.3.8 number-of-retries-supported (rangeOfInteger(0:MAX))

The range of allowed values for the "number-of-retries" Job Template attribute. This value may be set by the Set-Printer-Attributes operation.

6.3.9 printer-fax-log-uri (uri)

The REQUIRED "printer-fax-log-uri" Printer attribute provides the location of the persistent log that is maintained for every Job that is created.

6.3.10 printer-fax-modem-info (1setOf text(MAX))

The REQUIRED READ-ONLY "printer-fax-modem-info" Printer attribute provides a description of every fax modem used by the FaxOut service.

6.3.11 printer-fax-modem-name (1setOf name(MAX))

The REQUIRED READ-ONLY "printer-fax-modem-name" Printer attribute provides the name of every fax modem used by the FaxOut service. These names are used to populate the "output-device-assigned" Job Description attribute.

6.3.12 printer-fax-modem-number (1setOf uri)

The REQUIRED READ-ONLY "printer-fax-modem-number" Printer attribute provides a "tel" URI [RFC3966] representing the line (source) number for every fax modem used by the FaxOut service.

6.3.13 retry-interval-default (integer(1:MAX))

The default value supplied by the Printer if the Client omits the "retry-interval" Job Template attribute. This value may be set by the Set-Printer-Attributes operation.

6.3.14 retry-interval-supported (rangeOfInteger(1:MAX))

The range of allowed values for the "retry-interval" Job Template attribute. This value may be set by the Set-Printer-Attributes operation.


5253447

448449450

451

452453

454

455456

457

458459

460

461462

463

464465466

467

468469470

471

472473

474

475476

54

Michael Sweet, 11/28/12,

ISSUE: I've added what I think are the minimum important elements from the SM FaxOut service; I omitted most of the subunit and configuration details - we should decide whether we want a complete binding of everything or which additional elements/attributes should be added. There is a LOT of optional stuff...


READ-ONLY because subunit values are read-only at the service level in SM.


6.3.15 retry-time-out-default (integer(1:MAX))

The default value supplied by the Printer if the Client omits the "retry-time-out" Job Template attribute. This value may be set by the Set-Printer-Attributes operation.

6.3.16 retry-time-out-supported (rangeOfInteger(1:MAX))

The range of allowed values for the "retry-time-out" Job Template attribute. This value may be set by the Set-Printer-Attributes operation.

7. Additional Values and Semantics for Existing Attributes

7.1 ipp-features-supported (1setOf type2 keyword)

This specification defines the REQUIRED keyword 'faxout' for the "ipp-features-supported" Printer attribute.

7.2 job-state-reasons (1setOf type2 keyword)

Table 7 lists new "job-state-reasons" keyword values.

Table 7 - New "job-state-reasons" Keyword Values

Keyword Description'fax-modem-carrier-lost' Lost carrier during send.'fax-modem-equipment-failure' Fax modem failed during send.'fax-modem-inactivity-timeout' Job timed out due to inactivity.'fax-modem-line-busy' Destination line was busy.'fax-modem-no-answer' Destination did not answer.'fax-modem-no-dial-tone' No dial tone.'fax-modem-protocol-error' Fax protocol error.'fax-modem-training-failure' Unable to train/connect modems.'fax-modem-voice-detected' Fax modem detected a voice at

destination.'job-transferring' Job is being transmitted.'job-transforming' Job is being transformed to conform to

the recipient capabilities.

8. Conformance RequirementsTBD


5556477

478479

480

481482

483

484

485486

487

488

489

490

491

57


From MFD Alerts; this solves the "sticky keyword" problem for reasons that are only failure while a job is processing.


9. Internationalization ConsiderationsFor interoperability and basic support for multiple languages, conforming implementations MUST support:

1. The Universal Character Set (UCS) Transformation Format -- 8 bit (UTF-8) [STD63] encoding of Unicode [UNICODE] [ISO10646]; and

2. The Unicode Format for Network Interchange [RFC5198] which requires transmission of well-formed UTF-8 strings and recommends transmission of normalized UTF-8 strings in Normalization Form C (NFC) [UAX15].

Unicode NFC is defined as the result of performing Canonical Decomposition (into base characters and combining marks) followed by Canonical Composition (into canonical composed characters wherever Unicode has assigned them).

WARNING – Performing normalization on UTF-8 strings received from IPP Clients and subsequently storing the results (e.g., in IPP Job objects) could cause false negatives in IPP Client searches and failed access (e.g., to IPP Printers with percent-encoded UTF-8 URIs now 'hidden').

10. Security ConsiderationsThe IPP extensions defined in this document require the same security considerations as defined in the IPP Model and Semantics [RFC2911].

11. IANA Considerations

11.1 Attribute Registrations

The attributes defined in this document will be published by IANA according to the procedures in IPP Model and Semantics [RFC2911] section 6.2 in the following file:

http://www.iana.org/assignments/ipp-registrations

The registry entries will contain the following information:

Job Template attributes: Reference----------------------- ---------confirmation-sheet-print (boolean) [PWG5100.FAX]confirmation-sheet-print-default (boolean) [PWG5100.FAX]cover-sheet-info (collection) [PWG5100.FAX]cover-sheet-info-default (collection) [PWG5100.FAX] company-name (text(255)) [PWG5100.FAX] date-time (dateTime) [PWG5100.FAX] from (text(255)) [PWG5100.FAX] logo (uri) [PWG5100.FAX] message (text(MAX)) [PWG5100.FAX]


5859

492

493494

495496497498499

500501502

503504505506

507

508509

510

511

512513

514

515

516517518519520521522523524525526

60


subject (text(255)) [PWG5100.FAX] to (text(255)) [PWG5100.FAX]destination-uris (1setOf collection) [PWG5100.FAX] destination-uri (uri) [PWG5100.FAX] post-dial-string (text(127)) [PWG5100.FAX] pre-dial-string (text(127)) [PWG5100.FAX] t33-subaddress (integer(0:MAX)) [PWG5100.FAX]number-of-retries (integer(0:MAX)) [PWG5100.FAX]number-of-retries-default (integer(0:MAX)) [PWG5100.FAX]number-of-retries-supported (rangeOfInteger(0:MAX)) [PWG5100.FAX]retry-interval (integer(1:MAX)) [PWG5100.FAX]retry-interval-default (integer(1:MAX)) [PWG5100.FAX]retry-interval-supported (rangeOfInteger(1:MAX)) [PWG5100.FAX]retry-timeout (integer(1:MAX)) [PWG5100.FAX]retry-timeout-default (integer(1:MAX)) [PWG5100.FAX]retry-timeout-supported (rangeOfInteger(1:MAX)) [PWG5100.FAX]

Job Description attributes: Reference--------------------------- ---------destination-statuses (1setOf collection) [PWG5100.FAX] destination-uri (uri) [PWG5100.FAX] images-completed (integer(0:MAX)) [PWG5100.FAX] transmission-status (type2 enum) [PWG5100.FAX]

[PWG5100.FAX][PWG5100.FAX][PWG5100.FAX]

Printer Description attributes: Reference------------------------------- ---------confirmation-sheet-print-default (boolean) [PWG5100.FAX]cover-sheet-info-supported (1setOf type2 keyword) [PWG5100.FAX]destination-uri-schemes-supported (1setOf uriScheme) [PWG5100.FAX]logo-uri-schemes-supported (1setOf uriScheme) [PWG5100.FAX]multiple-destination-uris-supported (boolean) [PWG5100.FAX]number-of-retries-default (integer(0:MAX)) [PWG5100.FAX]number-of-retries-supported (rangeOfInteger(0:MAX)) [PWG5100.FAX]printer-fax-log-uri (uri) [PWG5100.FAX]printer-fax-modem-info (1setOf text(MAX)) [PWG5100.FAX]printer-fax-modem-name (1setOf name(MAX)) [PWG5100.FAX]printer-fax-modem-number (1setOf uri) [PWG5100.FAX]retry-interval-default (integer(1:MAX)) [PWG5100.FAX]retry-interval-supported (rangeOfInteger(1:MAX)) [PWG5100.FAX]retry-time-out-default (integer(1:MAX) [PWG5100.FAX]retry-time-out-supported (rangeOfInteger(1:MAX)) [PWG5100.FAX]

11.2 Attribute Value Registrations

The keyword attribute values defined in this document will be published by IANA according to the procedures in the IPP Model and Semantics [RFC2911] section 6.1 in the following file:



6162527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571

572

573574575

576

63



Attributes (attribute syntax) Keyword Attribute Value Reference ----------------------- ---------cover-sheet-info-supported (1setOf type2 keyword) [PWG5100.FAX] company-name [PWG5100.FAX] date-time [PWG5100.FAX] from [PWG5100.FAX] logo [PWG5100.FAX] message [PWG5100.FAX] subject [PWG5100.FAX] to [PWG5100.FAX]

ipp-features-supported (1setOf type2 keyword) [PWG5100.13] faxout [PWG5100.FAX]

job-state-reasons (1setOf type2 keyword) [RFC2911] fax-modem-carrier-lost [PWG5100.FAX] fax-modem-equipment-failure [PWG5100.FAX] fax-modem-inactivity-timeout [PWG5100.FAX] fax-modem-line-busy [PWG5100.FAX] fax-modem-no-answer [PWG5100.FAX] fax-modem-no-dial-tone [PWG5100.FAX] fax-modem-protocol-error [PWG5100.FAX] fax-modem-training-failure [PWG5100.FAX] fax-modem-voice-detected [PWG5100.FAX] job-transferring [PWG5100.FAX] job-transforming [PWG5100.FAX]

11.3 Type2 enum Attribute Value Registrations

The enumerations defined in this document will be published by IANA according to the procedures in the IPP Model and Semantics [RFC2911] section 6.2 in the following file:



Attributes (attribute syntax) Enum Value Enum Symbolic Name Reference ---------- ------------------ ---------transmission-status (type2 enum) [PWG5100.FAX] 3 pending [PWG5100.FAX] 4 pending-retry [PWG5100.FAX] 5 processing [PWG5100.FAX] 7 canceled [PWG5100.FAX] 8 aborted [PWG5100.FAX] 9 completed [PWG5100.FAX]


6465577

578579580581582583584585586587588589590591592593594595596597598599600601602603604

605

606607

608

609

610611612613614615616617618619

66


12. References

12.1 Normative References

[ISO10646] "Information technology -- Universal Coded Character Set (UCS)", ISO/IEC 10646:2011

[PWG5100.3] K. Ocke, T. Hastings, "Internet Printing Protocol (IPP): Production Printing Attributes – Set1", PWG 5100.3-2001, February 2001, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippprodprint10-20010212-5100.3.pdf

[PWG5100.7] T. Hastings, P. Zehler, "Standard for The Internet Printing Protocol (IPP): Job Extensions", PWG 5100.7-2003, October 2003, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippjobext10-20031031-5100.7.pdf

[PWG5100.9] I. McDonald, C. Whittle, "Internet Printing Protocol (IPP)/ Printer State Extensions v1.0", PWG 5100.9-2009, July 2009, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippstate10-20090731-5100.9.pdf

[PWG5100.11] T. Hastings, D. Fullman, "IPP: Job and Printer Operations - Set 2", PWG 5100.11-2010, October 2010, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext10-20101030-5100.11.pdf

[PWG5100.12] R. Bergman, H. Lewis, I. McDonald, M. Sweet, "IPP/2.0 Second Edition", PWG 5100.12-2011, February 2011, ftp://www.pwg.org/pub/pwg/candidates/cs-ipp20-2011MMDD-5100.12.pdf

[PWG5100.13] M. Sweet, I. McDonald, "IPP: Job and Printer Extensions - Set 3 (JPS3)", PWG 5100.13-2012, July 2012, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippjobprinterext3v10-20120727-5100.13.pdf

[PWG5102.4] M. Sweet, "PWG Raster Format", PWG 5102.4-2012, April 2012, ftp://ftp.pwg.org/pub/pwg/candidates/cs-ippraster10-20120420-5102.4.pdf

[PWG5108.1] W. Wagner, P. Zehler, "MFD Model and Common Semantics", PWG 5108.1-2011, April 2011, ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-mfdmodel10-20110415-5108.1.pdf


6768

620

621

622623

624625626627

628629630631

632633634635

636637638639

640641642643

644645646647

648649650

651652653

69


[PWG5108.05] P. Zehler, "FaxOut Semantic Model and Service Interface", PWG 5108.05-2011, August 2011, ftp://ftp.pwg.org/pub/pwg/candidates/cs-sm20-faxout10-20110809-5108.05.pdf

[RFC2911] T. Hastings, R. Herriot, R. deBry, S. Isaacson, P. Powell, "Internet Printing Protocol/1.1: Model and Semantics", RFC 2911, September 2000, http://www.ietf.org/rfc/rfc2911.txt

[RFC3382] R. deBry, R. Herriot, T. Hastings, K. Ocke, P. Zehler, "Internet Printing Protocol (IPP): The 'collection' attribute syntax", RFC 3382, September 2002, http://www.ietf.org/rfc/rfc3382.txt

[RFC3805] R. Bergman, H. Lewis, I. McDonald, "Printer MIB v2", RFC 3805, June 2004, http://www.ietf.org/rfc/rfc3805.txt

[RFC3966] H. Schulzrinne, "The tel URI for Telephone Numbers", RFC 3966, December 2004, http://www.ietf.org/rfc/rfc3966.txt

[RFC5198] J. Klensin, M. Padlipsky, "Unicode Format for Network Interchange", RFC 5198, March 2008, http://www.ietf.org/rfc/rfc5198.txt

[STD63] F. Yergeau, "UTF-8, a transformation format of ISO 10646", RFC 3629/STD 63, November 2003, http://www.ietf.org/rfc/rfc3629.txt

12.2 Informative References

TBD

13. Author's AddressMichael SweetApple Inc.1 Infinite LoopM/S 111-HOMCCupertino CA 95014

The author would also like to thank the following individuals for their contributions to this standard:

Smith Kennedy (Hewlett Packard)


7071654655656

657658659

660661662

663664

665666

667668

669670

671

672

673

674675676677678

679680

681

72


14. Change History

14.1 November 28, 2012

1. Updated to latest template and boilerplate text.2. Updated list of references3. Added cover-sheet-info-default, multiple-destination-uris-supported, printer-fax-

log-uri, printer-fax-modem-info, printer-fax-modem-name, and printer-fax-modem-number attributes

4. Added job-state-reasons values from MFD Alerts.5. Changed cover-sheet-info/-default to allow no-value.6. Moved -default and -supported attributes to Printer attributes section7. Added missing attributes to IANA section.8. Added new section 5 providing background on operation and a list of required

operations, attributes, and document formats.

14.2 September 22, 2011

Initial revision.


7374

682

683

684685686687688689690691692693694

695

696

75

Documents

ftp.pwg.org€¦ · Web view28.11.2012 · The IEEE-ISTO takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to