attachment
<div dir="ltr"><div>Hi Mike,</div><div><br></div><div>Prototype is not required for a Best Practice, but it's been done.</div><div><br></div><div>NOTHING in Process/3.0 or our PWG tradition says that, in fact,</div><div>everything has to be prototyped. A simple email from Smith that</div><div>says what HP has implemented would be a plus. Apple CUPS</div><div>has certainly done 'negotiate' and 'certificate' right? What about</div><div>'oauth'?<br></div><div><br></div><div>But specs that get Formal Vote do need to go Interim --> Prototype</div><div>--> Stable (and not just LC/Vote on Interim). I'd be happy to say that</div><div>the current draft was *meant* to be Prototype and voice vote it into</div><div>Stable for WG LC.</div><div><br></div><div>Cheers,</div><div>- Ira</div><div></div><div><br></div><div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG</div><div>Co-Chair - TCG Metadata Access Protocol SG<br></div><div dir="ltr">Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Jan 16, 2019 at 2:09 PM Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">Ira,<div><br></div><div>I don’t think Process/3.0 requires prototyping for non-standards track documents. All I see is a prototyping requirement for candidate standards.<br><br><div id="gmail-m_3502687052698557402AppleMailSignature" dir="ltr">Sent from my iPhone</div><div dir="ltr"><br>On Jan 16, 2019, at 12:22 PM, Kennedy, Smith (Wireless & Standards Architect) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:<br><br></div><div dir="ltr"><span></span></div><blockquote type="cite"><div dir="ltr">Hi Ira,<div>
<div><br><blockquote type="cite"><div>On Jan 16, 2019, at 10:05 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>> wrote:</div><br class="gmail-m_3502687052698557402Apple-interchange-newline"><div><div dir="ltr"><div>Hi Smith,</div><div><br></div><div>This *should* have been labeled Prototype (not current Interim) </div></div></div></blockquote><div><div><br></div><div>I remembered that when I started editing but forgot to change it. I will that change and post an updated draft to nudge that forward.</div><div><br></div></div><blockquote type="cite"><div><div dir="ltr"><div>and there</div><div>should be an email Prototype report (e.g.,"this spec documents all of the</div><div>existing IPP Authentication Methods, all of which have implementations")</div><div>so that, by voice approval, we can move it to Stable draft and WG LC.</div></div></div></blockquote><div><br></div><div><div>I know HP products have supported 'none', 'requesting-user-name', 'basic', and 'digest'. I suppose I need to solicit feedback from other members on whether the authentication methods not implemented by HP might be implemented by them? Has any other vendor or project implemented support for 'negotiate', 'oauth', or 'certificate'?</div></div></div><div><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>Bear in mind that, for a Best Practices document, we actually also need</div><div>PWG LC *and* PWG Formal Vote (not just PWG Call for Objections),</div><div>because this is a new spec and not errata and that's our process for</div><div>Best Practices documents.</div></div></div></blockquote><div><br></div>Thanks - I forgot about that. Even better reason to finish it off.</div><div><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>Cheers,</div><div>- Ira</div><div><br></div><div><div><div dir="ltr" class="gmail-m_3502687052698557402gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG</div><div>Co-Chair - TCG Metadata Access Protocol SG<br></div><div dir="ltr">Chair - Linux Foundation Open Printing WG<br>Secretary - IEEE-ISTO Printer Working Group<br>Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music / High North Inc<br><a style="color:rgb(51,51,255)" href="https://protect-us.mimecast.com/s/kkl1Cqx5v5uYOlwpiZjrr9?domain=sites.google.com" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a style="color:rgb(102,0,204)" href="https://protect-us.mimecast.com/s/6kLeCrk5w5fQAoJ5tz_F-q?domain=sites.google.com" target="_blank">http://sites.google.com/site/highnorthinc</a><br>mailto: <a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>PO Box 221 Grand Marais, MI 49839 906-494-2434<br><br><div style="display:inline"></div><div style="display:inline"></div><div style="display:inline"></div><div></div><div></div><div></div><div></div></div></div></div></div></div></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Jan 14, 2019 at 3:45 PM Kennedy, Smith (Wireless & Standards Architect) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Greetings again,<div><br></div><div>I'm hoping that we can discuss using this revision to start the Working Group Last Call. I'd like to discuss that at this week's IPP WG teleconference.</div><div><br></div><div>Cheers,</div><div><br></div><div><div>
Smith<br><br>/**<br> Smith Kennedy<br> HP Inc.<br>*/
</div>
<div><br><blockquote type="cite"><div>On Jan 9, 2019, at 8:52 AM, Kennedy, Smith (Wireless & Standards Architect) <<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>> wrote:</div><br class="gmail-m_3502687052698557402gmail-m_-1132779598293110733Apple-interchange-newline"><div>
<div>Greetings,<br>
<br>
I've posted another incremental draft of IPP Authentication Methods to the PWG FTP site:<br>
<br>
<a href="https://protect-us.mimecast.com/s/31gpCv25A5hwWKVDtzMnAi?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190109.pdf</a><br>
<a href="https://protect-us.mimecast.com/s/aDqhCwp5B5IlL9rDtKc97H?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190109.odt</a><br>
<a href="https://protect-us.mimecast.com/s/9N7YCxk5D5fEJwN2tRnLQj?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190109-rev.pdf</a><br>
<a href="https://protect-us.mimecast.com/s/V84ZCyP5E5uONkVltAlOXd?domain=ftp.pwg.org" target="_blank">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippauth-20190109-rev.odt</a><br>
<br>
This revision adds mention of the "oauth-authorization-server-uri" Printer Description attribute and a reference to PWG 5100.18 (IPP INFRA) since that attribute is listed in the sequence diagram. The -rev is compared against the last reviewed revision (20181109).<br>
<br>
Smith<br>
<br>
/**<br>
Smith Kennedy<br>
HP Inc.<br>
*/<br>
<br>
_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>
<a href="https://protect-us.mimecast.com/s/Kp0_Czp5G5IWR9V0CBcuVp?domain=pwg.org" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</div>
</div></blockquote></div><br></div></div>_______________________________________________<br>
ipp mailing list<br>
<a href="mailto:ipp@pwg.org" target="_blank">ipp@pwg.org</a><br>
<a href="https://protect-us.mimecast.com/s/Kp0_Czp5G5IWR9V0CBcuVp?domain=pwg.org" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/listinfo/ipp</a><br>
</blockquote></div>
</div></blockquote></div><br></div></div></blockquote></div></div></blockquote></div>