IPPFAX Requirements Spec

Status of Spec

• - complete, ready for PWG last-call

  Latest Draft

• - ftp://ftp.pwg.org/pub/pwg/QUALDOCS/requirements in file wd-ifxreq10-20031112.pdf

  Key Document Format Requirements

• - Support for streaming (low-cost to Senders and Receivers)

• - Support for multiple graphics formats
• - Support for Sender Identity embedded in document
• - Support for monochrome, gray-scale, and color images
• - Support for compatibility with PDF/A

  Key IFFAX Protocol Requirements

• - Support for a superset of CCITT PSTN facsimile service

• - Support for a strict subset of IPP/1.1 protocol (no options/no admin)
• - Support for strong security (data integrity and data privacy)
• - Support for Sender and Receiver (equipment) identity exchange
• - Support for Sending User and Receiving User (people) identity exchange

PDF/is Spec

Status of Spec

• - complete, ready for PWG last-call

  Latest Draft

• - ftp://ftp.pwg.org/pub/pwg/QUALDOCS/ in file wd-pdfis10-20031112.pdf

  Key PDF/is Features

• - Support for strict subset of PDF/1.4 (compatible with Acrobat 5)

• - Support for streaming (strict page layout and page ordering)
• - Support for multiple graphics formats (JPEG, JBIG2, CCITT Group 4)
• - Support for Sender Identity embedded in document (Originator ID)
• - Support for ICC-based gray-scale and color spaces (sRGB profile)
• - Support for compatibility with PDF/A (fully compatible)

IPPFAX Protocol Spec

Status of Spec

• - largely complete, needs edits to tables and conformance

  Latest Draft

• - ftp://ftp.pwg.org/pub/pwg/QUALDOCS/ in file wd-ifx10-20031105.pdf

  Key IPPFAX Protocol Features

• - Support for a superset of CCITT PSTN facsimile service

• - Support for a strict subset of IPP/1.1 protocol (no options/no admin)
• - Support for strong security (mandatory TLS/1.0 at connection startup)
• - Support for Sender and Receiver ID exchange (TLS/1.0 authentication)
• - Support for Sending User and Receiving User ID exchange (vCard/3.0)

Recent Simplifications of IPPFAX Protocol

Removed Optional Job Notifications

• - IPP subscriptions and notifications not allowed

• - Get-Job-Attributes and mandatory minimum job lifetime used instead

  Removed Optional Operations

• - All operations defined in IPP/1.1 extension documents not allowed

• - Job-Cancel only allowed for authenticated operator/admin (not owner)
• - All other IPP/1.1 admin operations not allowed
• - Print-URI, Create-Job, Send-Document, and Send-URI not allowed
• - Get-Jobs only allowed for authenticated operator/admin (not end user)
• - Get-Job-Attributes only allowed for authenticated job owner or operator/admin
• - Get-Printer-Attributes and Validate-Job only needed for non-standard media (other than na-letter or iso-a4)

  Removed Optional Job Template Attributes

• - "media" and "printer-resolution" job submission attributes allowed

• - All other Job Template job submission attributes not allowed

  Restricted Printer Description Attributes

• - "document-format-supported" must contain only 'application/pdf'

• - "document-format-version-supported" must contain 'PDF/is-1.0'
• - "document-format-version-supported" may contain other PDF subsets

Business Case for Implementation of IPPFAX

Embedded Devices

• - IPPFAX/1.0 is much smaller than full IPP/1.1 (or full Internet Ifax)

• - PDF/is is much smaller than full PDF/1.4 (or full TIFF/6.0)

  Compatibility

• - PDF/is compatible with installed PDF/1.4 readers and applications

• - PDF/is compatible with PDF/A (US government long-term archive format)

  Quality Documents

• - IPPFAX supports blind interoperability (only Print-Job needed)

• - PDF/is supports very high quality documents (invisible text, etc.)
• - CCITT Fax supports only a limited set of resolutions
• - IETF Ifax supports only profiles of TIFF (license/IPR issues)
• - IETF Ifax requires support for CONNEG for interoperability at higher resolutions
• - IETF Ifax requires support for (unreliable) email MDN/DSN for delivery confirmation

  Realtime Transmission

• - IPPFAX is realtime (limited only by Internet access speeds)

• - CCITT Fax is realtime (but much lower data transmission speeds)
• - IETF Ifax is email-based (no reliable delivery confirmations)

  Security

• - TLS/1.0 support is mandatory for all IPPFAX implementations

• - TLS/1.0 client and server authentication ensures correct endpoints
• - TLS/1.0 data integrity ensures reliablity across Internet
• - TLS/1.0 data encryption ensures privacy across Internet

Comments are owned by the poster. All other material is Copyright © 2001-2024 The Printer Working Group. All rights reserved. IPP Everywhere, the IPP Everywhere logo, and the PWG logo are trademarks of the IEEE-ISTO.
About the PWG · Privacy Policy · PWG Webmaster