attachment

<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>Hi Smith,</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Since we missed a required section in the template, I personally like the re-publish and re-start option as opposed to considering it as a last call comment.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Generally I am seeing this as a process failure (i. e. template used was missing a required section) rather than a content related issue.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">I realize adding the section into the document adds content so I think either proposed solution will  work fine within PWG process rules.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Thanks.</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">Best Regards,</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">/Paul</div><div id="AppleMailSignature"><br></div><div id="AppleMailSignature">P.S. - Thanks Mike for catching this issue.</div><div id="AppleMailSignature"><br>Sent from my iPhone</div><div><br>On Nov 17, 2017, at 10:02 AM, Kennedy, Smith (Wireless & Standards Architec) <<a href="mailto:smith.kennedy@hp.com">smith.kennedy@hp.com</a>> wrote:<br><br></div><blockquote type="cite"><div>

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">


Wow, I wonder how I missed that too! I can hammer out another revision and we can re-issue the last call. Or we can just treat this as conventional last call feedback. Which do you and the IPP WG prefer?<br>
<br>
<div id="AppleMailSignature">
<div id="AppleMailSignature">
<div><span style="background-color: rgba(255, 255, 255, 0);">Cheers,<br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">Smith<br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">---<br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);"><br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">   Smith Kennedy<br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">   Wireless Architect - Client Software - IPG-PPS<br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">   Standards - PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum<br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">   Chair, IEEE ISTO Printer Working Group<br>
</span></div>
<div><span style="background-color: rgba(255, 255, 255, 0);">   HP Inc.</span></div>
<div style="font-family: UICTFontTextStyleBody; font-size: 19px;"><span style="background-color: rgba(255, 255, 255, 0);"><br>
</span></div>
</div>
</div>
<div><br>
On Nov 17, 2017, at 6:34 AM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<br>
<br>
</div>
<blockquote type="cite">
<div><span>One Apple comment: there is no IANA Considerations section! (and I don't believe I missed this with all of the reviews we did!)</span><br>
<span></span><br>
<span>You'll need two subsections to register the new operation and its corresponding value, to insert before the current section 8 (references) - the current reg-template.docx has the necessary text you can copy from:</span><br>
<span></span><br>
<span>N IANA Considerations</span><br>
<span></span><br>
<span></span><br>
<span>N.1 Type2 enum Registrations</span><br>
<span></span><br>
<span>The attributes defined in this registration will be published by IANA according to the procedures in IPP Model and Semantics [RFC8011] section 7.1 in the following file:</span><br>
<span></span><br>
<span>   <a href="http://www.iana.org/assignments/ipp-registrations">http://www.iana.org/assignments/ipp-registrations</a></span><br>
<span></span><br>
<span>The registry entries will contain the following information:</span><br>
<span></span><br>
<span>   Attributes (attribute syntax)</span><br>
<span>     Enum Value      Enum Symbolic Name                     Reference</span><br>
<span>     ----------      ------------------                     ---------</span><br>
<span>   operations-supported (1setOf type2 enum)                 [RFC8011]</span><br>
<span>     0x0066          Get-User-Printer-Attributes            [IPPGUPA]</span><br>
<span></span><br>
<span></span><br>
<span>N.2 Operation Registrations</span><br>
<span></span><br>
<span>The attributes defined in this registration will be published by IANA according to the procedures in IPP/1.1 Model and Semantics [RFC8011] section 7.4 in the following file:</span><br>
<span></span><br>
<span>   <a href="http://www.iana.org/assignments/ipp-registrations">http://www.iana.org/assignments/ipp-registrations</a></span><br>
<span></span><br>
<span>The registry entries will contain the following information:</span><br>
<span></span><br>
<span>   Operation Name                                           Reference</span><br>
<span>   --------------                                           ---------</span><br>
<span>   Get-User-Printer-Attributes                              [IPPGUPA]</span><br>
<span></span><br>
<span></span><br>
<blockquote type="cite"><span>On Nov 16, 2017, at 10:25 PM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>All,</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>This message begins the IPP Last Call of the IPP Get-User-Printer-Attributes registration which is available at the following URLs:</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>  <a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippgupa-20171117.pdf">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippgupa-20171117.pdf</a></span><br>
</blockquote>
<blockquote type="cite"><span>  <a href="https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippgupa-20171117.odt">https://ftp.pwg.org/pub/pwg/ipp/wd/wd-ippgupa-20171117.odt</a></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Please review this registration and respond to the IPP mailing list (reply-all to this message is fine) with any feedback you have for the proposed registration.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>This IPP Last Call ends at 10pm PT on December 1, 2017.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>_________________________________________________________</span><br>
</blockquote>
<blockquote type="cite"><span>Michael Sweet, Senior Printing System Engineer</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>_______________________________________________</span><br>
</blockquote>
<blockquote type="cite"><span>ipp mailing list</span><br>
</blockquote>
<blockquote type="cite"><span><a href="mailto:ipp@pwg.org">ipp@pwg.org</a></span><br>
</blockquote>
<blockquote type="cite"><span><a href="https://www.pwg.org/mailman/listinfo/ipp">https://www.pwg.org/mailman/listinfo/ipp</a></span><br>
</blockquote>
<span></span><br>
<span>_________________________________________________________</span><br>
<span>Michael Sweet, Senior Printing System Engineer</span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>ipp mailing list</span><br>
<span><a href="mailto:ipp@pwg.org">ipp@pwg.org</a></span><br>
<span><a href="https://www.pwg.org/mailman/listinfo/ipp">https://www.pwg.org/mailman/listinfo/ipp</a></span><br>
</div>
</blockquote>


</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>ipp mailing list</span><br><span><a href="mailto:ipp@pwg.org">ipp@pwg.org</a></span><br><span><a href="https://www.pwg.org/mailman/listinfo/ipp">https://www.pwg.org/mailman/listinfo/ipp</a></span><br></div></blockquote></body></html>