Skip to content

Planned PWG Errata Updates

Smith Kennedy edited this page Dec 13, 2020 · 3 revisions

PWG 5100.12-YYYY: Internet Printing Protocol/2.0: Fourth Edition

History:

  • PWG 5100.10-2009: Internet Printing Protocol Version 2.0 (IPP/2.0) (Candidate Standard): Defined protocol versions 2.0 and 2.1
  • PWG 5100.12-2011: Internet Printing Protocol Version 2.0 Second Edition (IPP/2.0 SE) (Candidate Standard): Added protocol version 2.2
  • PWG 5100.12-2015: IPP 2.0, 2.1, and 2.2 (Standard): IPP/2.0 promoted to full standard.

Most of the specifications this standard depends on have changed. Some key elements of Enterprise (2.1) and Production (2.2) have also changed, particularly with respect to core features such as proof print and job storage. And IPP Everywhere has largely supplanted the bar set for the base 2.0 conformance level.

The goals for an updated PWG 5100.12 are:

  1. Normalize the document version. Each document has used the name "ipp20" which doesn't match the file naming policy for the PWG. Because this will be the third update to 2.0, working drafts should be named "wd-ipp23-yyyymmdd[-rev].ext".

  2. Retitle the document, proposed as "Internet Printing Protocol/2.0: Fourth Edition" to be closer to the original and consistent with the STD92 "Internet Printing Protocol/1.1: Subtitle" format.

  3. Keep the IPP/2.0 conformance level as-is - IPP/1.1 + collections (which are part of STD92 now) and MSN2

  4. Redefine the IPP/2.1 conformance level as Enterprise Printers that SHOULD conform to EPX 2.0

  5. Redefine the IPP/2.2 conformance level as Production Printers that SHOULD conform to PPX 2.0

  6. Provide non-normative references to NODRIVER 2.0 (for ipp-features-supported) and text that explains that the old hammer of IPP version is no longer used to identify major features.

PWG 5100.14-YYYYY: IPP Everywhere v2.0

History:

  • PWG 5100.14-2013: IPP Everywhere v1.0: Initial version
  • PWG 5100.14-2020: IPP Everywhere v1.1: Changes for B&W printers, some clarifications and additional recommendations

The goals for an updated IPP Everywhere specification are:

  1. Mandate support for valuable features that were added as recommendations in v1.1.
    1. TLS 1.2
    2. Privacy
    3. Job Accounting
  2. Add feature definitions for important "vertical solution" use cases
    1. Cloud printing
    2. Finishings
    3. Authentication with different methods (e.g. Basic, Digest, OAuth2)
    4. Job Release
    5. Job Storage
  3. Define a complete IPP Everywhere MFD by adding new IPP Everywhere service definitions
    1. Scan
    2. FaxOut
    3. System
  4. Define tests to certify standard common features
    1. Sides
    2. Variations in page orientation (e.g. mixed portrait / landscape pages in source document tested with both short and long edge feed media)

These are the changes planned to satisfy the above goals:

  1. Make current RECOMMENDED attributes REQUIRED or CONDITIONALLY REQUIRED

    • General attributes: "job-mandatory-attributes-supported","job-presets-supported", "job-privacy-xxx","jpeg-xxx-supported", "max-page-ranges-supported", "pdf-xxx-supported", "print-content-optimize-xxx", "print-scaling-xxx", "printer-current-time", "printer-dns-sd-name", "printer-firmware-xxx", "printer-input-tray", "printer-output-tray", "printer-privacy-policy-uri", "printer-strings-xxx"
    • Job Accounting and Transaction attributes: "charge-info-message", "job-account-id-xxx", "job-account-type-xxx", "job-accounting-user-id-xxx", "job-authorization-uri-xxx", "job-charge-info", "job-impressions-estimated", "printer-charge-info-xxx" Enterprise attributes: "job-password-xxx", etc.
  2. Make IPPS/TLS support REQUIRED (all current 1.0/1.1 printers do)

  3. Maybe add RECOMMENDED/COND. REQUIRED for IPP INFRA/SYSTEM Proxy with OAuth support?

  4. Add requirement that printer support Get-Printer-Attributes on "/" path for static discovery (you know the IP address but not the resource path - all current 1.0/1.1 printers do)

Discussion:

  1. Require FaxOut support (for MFPs that support PC facsimile)?

  2. Add/test specific feature levels/classes of printers (finishings, enterprise, etc.)?

  3. Require System service support for MFPs and/or managed/cloud configurations (for Client too so they can discover printers given an IP address or hostname)?