attachment
<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Paul,<div class=""><br class=""></div><div class="">No, the purpose of the IPP book is to document the basics that can be used on most/all printers. The document object extension does not meet that criteria...</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div><blockquote type="cite" class=""><div class="">On Mar 12, 2018, at 5:54 PM, Paul Tykodi <<a href="mailto:ptykodi@tykodi.com" class="">ptykodi@tykodi.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="content-type" content="text/html; charset=utf-8" class=""><div dir="auto" class="">Hi Ira,<div class=""><br class=""></div><div class="">Do you think the document object might be a good topic to cover in the IPP book we have been discussing?</div><div class=""><br class=""></div><div class="">Thanks.</div><div class=""><br class=""></div><div class="">Best Regards,</div><div class=""><br class=""></div><div class="">/Paul<br class=""><br class=""><div class="">Sent from my iPhone</div><div class=""><br class="">On Mar 12, 2018, at 2:24 PM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" class="">blueroofmusic@gmail.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class=""><div class="">Hi,<br class=""><br class=""></div>I agree with Mike. Document object has the complexity of the Job object plus bells and whistles.<br class=""></div>Subscription object covering multiple targets (System, Printer, Job, Document) is complex.<br class=""><br class=""></div>Even IPP/2.0 (w/ 2.1 and 2.2) is just brief lists of required attributes and operations for three levels<br class=""></div>of IPP Printer capabilities (and no longer even close to all inclusive).<br class=""><br class=""></div>RFCs 8010/8011 are meant to be strictly cleanups of RFCs 2910/2911 - the universe of IPP (over<br class=""></div>30 IETF and PWG specs) is too broad to cover in one spec, without major omissions.<br class=""><br class=""></div>Cheers,<br class=""></div>- Ira<br class=""><br class=""></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class="">Ira McDonald (Musician / Software Architect)<br class="">Co-Chair - TCG Trusted Mobility Solutions WG<br class="">Chair - Linux Foundation Open Printing WG<br class="">Secretary - IEEE-ISTO Printer Working Group<br class="">Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br class="">IETF Designated Expert - IPP & Printer MIB<br class="">Blue Roof Music / High North Inc<br class=""><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank" class="">http://sites.google.com/site/blueroofmusic</a><br class=""><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank" class="">http://sites.google.com/site/highnorthinc</a><br class="">mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank" class="">blueroofmusic@gmail.com</a><br class="">Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br class="">May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434<br class=""><br class=""><div style="display:inline" class=""></div><div style="display:inline" class=""></div><div style="display:inline" class=""></div><div class=""></div><div class=""></div><div class=""></div><div class=""></div></div></div></div></div></div>
<br class=""><div class="gmail_quote">On Mon, Mar 12, 2018 at 1:51 PM, Michael Sweet <span dir="ltr" class=""><<a href="mailto:msweet@apple.com" target="_blank" class="">msweet@apple.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Smith,<br class="">
<span class=""><br class="">
> On Mar 12, 2018, at 1:16 PM, Kennedy, Smith (Wireless & Standards Architec) <<a href="mailto:smith.kennedy@hp.com" class="">smith.kennedy@hp.com</a>> wrote:<br class="">
><br class="">
><br class="">
><br class="">
>> On Mar 9, 2018, at 2:54 PM, Michael Sweet <<a href="mailto:msweet@apple.com" class="">msweet@apple.com</a>> wrote:<br class="">
>><br class="">
>> Smith,<br class="">
>><br class="">
>> PWG 5100.5 is an extension to IPP/1.1 that defines the Document object, the document-attributes-tag (group) value, and the amended semantics for the Send-Document and Send-URI operations. None of that was part of the core IPP/1.1 (which is what RFC 8011 defines) and we've historically been conservative about requiring support for the Document object extension - right now only IPP/2.2 and IPP INFRA require it and most implementations only support a single document per job anyways...<br class="">
><br class="">
> I understand that we cannot add additional normative requirements. I was just thinking that, if the "document group" were mentioned even in passing as an optional group in 8011, with a reference to PWG 5100.5, that would help with the "cross referencing" thing.<br class="">
<br class="">
</span>We also have the Subscription object and its associated attribute group that can be included in Job Creation operations but which we don't say anything about (beyond a reference in the introduction)...<br class="">
<br class="">
I think the last thing we want to do is One Spec to Rule Them All™. And honestly I don't think that mentioning other attribute groups without providing any details will be all that useful, especially for something as complicated as the Document object extension.<br class="">
<div class="HOEnZb"><div class="h5"><br class="">
______________________________<wbr class="">___________________________<br class="">
Michael Sweet, Senior Printing System Engineer<br class="">
<br class="">
______________________________<wbr class="">_________________<br class="">
ipp mailing list<br class="">
<a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a><br class="">
<a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank" class="">https://www.pwg.org/mailman/<wbr class="">listinfo/ipp</a><br class="">
</div></div></blockquote></div><br class=""></div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">ipp mailing list</span><br class=""><span class=""><a href="mailto:ipp@pwg.org" class="">ipp@pwg.org</a></span><br class=""><span class=""><a href="https://www.pwg.org/mailman/listinfo/ipp" class="">https://www.pwg.org/mailman/listinfo/ipp</a></span><br class=""></div></blockquote></div></div></div></blockquote></div><br class=""><div class="">
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: 'Andale Mono'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; border-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-stroke-width: 0px;"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">_________________________________________________________<br class="">Michael Sweet, Senior Printing System Engineer</div></span></div></span>
</div>
<br class=""></div></body></html>