[IPP] Fate of "document-format-details" attribute

[IPP] Fate of "document-format-details" attribute

Michael Sweet msweet at apple.com
Thu Apr 18 11:28:56 UTC 2019


Cihan,

Whoops, yes of course.  Too much cut and paste... :/


> On Apr 17, 2019, at 9:31 PM, Cihan Colakoglu via ipp <ipp at pwg.org> wrote:
> 
> Hi Michael,
>  
> Just a quick note, it was pointed out to me that there appears to be a typo in some of the attribute names:
> (replace “format” with “source”)
>  
> document-format-application-name       à should be document-source-application-name
> document-format-application-version    à should be document-source-application-version
> document-format-os-name                         à should be document-source-os-name
> document-format-os-version                      à should be document-source-os-version
>  
> Best Regards,
> Cihan
>  
> -----Original Message-----
> From: ipp <ipp-bounces at pwg.org> On Behalf Of Michael Sweet via ipp
> Sent: Wednesday, April 17, 2019 1:16 PM
> To: PWG IPP Workgroup <ipp at pwg.org>
> Subject: [IPP] Fate of "document-format-details" attribute
>  
> All,
>  
> The following represents the consensus of those attending the IPP workgroup session at the April 2019 PWG Face-to-Face meeting concerning the "document-format-details" attribute and its related attributes:
>  
> - All of the definitions of the attribute will be moved to the IPP Job Extensions v2.0 specification update in development
>  
> - The "document-format-details" attribute will be DEPRECATED (still available for use) and will be reduced to the "collection" syntax (just a single value). This is compatible at the wire level and reflects that there are no uses for multiple values in a single document.
>  
> - The "document-format", "document-format-version", and "document-natural-language" member attributes will be made OBSOLETE because they are redundant with the corresponding top-level attributes and could be used to bypass security/format checks.
>  
> - The "document-format-device-id" member attribute will be made OBSOLETE because it is too short (127 octets vs. 1023 octets for "printer-device-id").
>  
> - The "document-format-application-name" and "document-format-application-version" member attributes will be retained for informational use with a cautionary notice about interoperability and authenticity issues and the potential for use as PII.
>  
> - The "document-format-os-name" and "document-format-os-version" member attributes will be retained for informational use with a cautionary notice about interoperability and authenticity issues and the potential for use as PII.
>  
> - A section will be added to the security considerations concerning the authenticity and PII issues of "document-format-details" in general, with a reference to the EFF work concerning user identification.
>  
> - An informational reference will be added to the EFF article on using User-Agent to track users:
>  
>   https://www.eff.org/deeplinks/2010/01/tracking-by-user-agent <https://www.eff.org/deeplinks/2010/01/tracking-by-user-agent>
>  
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer
>  
> _______________________________________________
> ipp mailing list
> ipp at pwg.org <mailto:ipp at pwg.org>
> https://www.pwg.org/mailman/listinfo/ipp <https://www.pwg.org/mailman/listinfo/ipp>_______________________________________________
> ipp mailing list
> ipp at pwg.org <mailto:ipp at pwg.org>
> https://www.pwg.org/mailman/listinfo/ipp <https://www.pwg.org/mailman/listinfo/ipp>
_________________________________________________________
Michael Sweet, Senior Printing System Engineer

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20190418/5e6bbb1f/attachment.html>


More information about the ipp mailing list