attachment
<div dir="ltr"><div>Hi Smith,</div><div><br></div><div>If I visit the RFC Index page, 8010 and 8011 show as Internet Standard.</div><div><br></div><div>Almost no existing RFCs have changed their own cover page to list this</div><div>(and such a listing is deprecated in IETF process docs, because the IETF</div><div>can later mark an old RFC as Historic, for example).</div><div><br></div><div>I'm REALLY not happy about re-issuing RFC 8010 and 8011 to change</div><div>their cover pages. They say standards-track and they are.</div><div><br></div><div>Cheers,</div><div>- Ira<br></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr">Ira McDonald (Musician / Software Architect)<br>Co-Chair - TCG Trusted Mobility Solutions WG<br>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>Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br>May-Dec: 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>
<br><div class="gmail_quote">On Tue, Jul 3, 2018 at 12:42 PM, Kennedy, Smith (Wireless & Standards Architec) <span dir="ltr"><<a href="mailto:smith.kennedy@hp.com" target="_blank">smith.kennedy@hp.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Mike and Ira,<br>
<br>
Is editorial work needed to get the RFC itself to be listed as an "Internet Standard" when one visits the links? I see this one doesn't list its Internet Standard number in the header:<br>
<br>
<a href="https://tools.ietf.org/html/std90" rel="noreferrer" target="_blank">https://tools.ietf.org/html/<wbr>std90</a><br>
<br>
but this one does:<br>
<br>
<a href="https://tools.ietf.org/html/std91" rel="noreferrer" target="_blank">https://tools.ietf.org/html/<wbr>std91</a><br>
<br>
Ours is here:<br>
<br>
<a href="https://tools.ietf.org/html/std92" rel="noreferrer" target="_blank">https://tools.ietf.org/html/<wbr>std92</a><br>
<br>
which is a concatenation of RFC 8010 and 8011, but provides somewhat inadequate navigation IMHO - 8011 is concatenated after 8010. And when you visit the RFC pages directly for 8010 and 8011, they aren't yet labeled as "INTERNET STANDARD" but are still labeled as "PROPOSED STANDARD":<br>
<br>
<a href="https://tools.ietf.org/html/rfc8010" rel="noreferrer" target="_blank">https://tools.ietf.org/html/<wbr>rfc8010</a><br>
<a href="https://tools.ietf.org/html/rfc8011" rel="noreferrer" target="_blank">https://tools.ietf.org/html/<wbr>rfc8011</a><br>
<br>
RFC 3629 seems to have everything as "right" as is possible currently, presentation wise:<br>
<br>
<a href="https://tools.ietf.org/html/std63" rel="noreferrer" target="_blank">https://tools.ietf.org/html/<wbr>std63</a><br>
<a href="https://tools.ietf.org/html/rfc3629" rel="noreferrer" target="_blank">https://tools.ietf.org/html/<wbr>rfc3629</a><br>
<br>
Not trying to spend cycles on unnecessary stuff but this kind of presentation thing can cause issues to the uninitiated.<br>
<span class="im HOEnZb"><br>
Smith<br>
<br>
/**<br>
Smith Kennedy<br>
Wireless & Standards Architect - IPG-PPS<br>
Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF<br>
Chair, IEEE ISTO Printer Working Group<br>
HP Inc.<br>
*/<br>
<br>
<br>
<br>
</span><div class="HOEnZb"><div class="h5">> On Jun 28, 2018, at 8:33 AM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<br>
> <br>
> And "STD92" as the pointer:<br>
> <br>
> <a href="https://www.rfc-editor.org/info/std92" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>info/std92</a><br>
> <br>
> <br>
>> On Jun 28, 2018, at 10:22 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:<br>
>> <br>
>> Hi,<br>
>> <br>
>> This morning's RFC Index shows IPP/1.1 (RFC 8010/8011) as "Internet Standard"<br>
>> <br>
>> <a href="https://www.rfc-editor.org/rfc-index.html" rel="noreferrer" target="_blank">https://www.rfc-editor.org/<wbr>rfc-index.html</a><br>
>> <br>
>> Cheers,<br>
>> - Ira<br>
>> <br>
>> <br>
>> Ira McDonald (Musician / Software Architect)<br>
>> Co-Chair - TCG Trusted Mobility Solutions WG<br>
>> 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 href="http://sites.google.com/site/blueroofmusic" rel="noreferrer" target="_blank">http://sites.google.com/site/<wbr>blueroofmusic</a><br>
>> <a href="http://sites.google.com/site/highnorthinc" rel="noreferrer" target="_blank">http://sites.google.com/site/<wbr>highnorthinc</a><br>
>> mailto: <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>
>> Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br>
>> May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434<br>
>> <br>
>> <br>
>> On Tue, Jun 26, 2018 at 10:37 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a>> wrote:<br>
>> Hi,<br>
>> <br>
>> Normally they just assign an STD number and update std-index.txt (for the RFC set)<br>
>> and rfc-index.txt (for Internet Standard status). Only when any *future* update of the<br>
>> RFCs happens would be any cover page change. <br>
>> <br>
>> RFCs never state more than just "Standards Track" on their cover page and usually <br>
>> don't mention their own STD number (because an STD could become historic or <br>
>> deprecated via the underlying RFC status - although I think it's only happened once).<br>
>> <br>
>> I expect to see IPP/1.1 update in the RFC Index web page w/in a few weeks.<br>
>> <br>
>> Cheers,<br>
>> - Ira<br>
>> <br>
>> <br>
>> <br>
>> Ira McDonald (Musician / Software Architect)<br>
>> Co-Chair - TCG Trusted Mobility Solutions WG<br>
>> 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 href="http://sites.google.com/site/blueroofmusic" rel="noreferrer" target="_blank">http://sites.google.com/site/<wbr>blueroofmusic</a><br>
>> <a href="http://sites.google.com/site/highnorthinc" rel="noreferrer" target="_blank">http://sites.google.com/site/<wbr>highnorthinc</a><br>
>> mailto: <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>
>> Jan-April: 579 Park Place Saline, MI 48176 734-944-0094<br>
>> May-Dec: PO Box 221 Grand Marais, MI 49839 906-494-2434<br>
>> <br>
>> <br>
>> On Tue, Jun 26, 2018 at 10:28 AM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<br>
>> Smith,<br>
>> <br>
>> I'm not sure about the timing - a lot depends on the RFC editor's load and any editorial changes that we want to make. Ideally I'd like to just have them assign STD numbers and change the status on the cover page (minimal change) to speed this along... :)<br>
>> <br>
>> <br>
>>> On Jun 26, 2018, at 12:02 AM, Kennedy, Smith (Wireless & Standards Architec) <<a href="mailto:smith.kennedy@hp.com">smith.kennedy@hp.com</a>> wrote:<br>
>>> <br>
>>> Thanks for the update, Mike! Given this status change for RFC 8011 (and corresponding change for RFC 8010), when do we expect them to complete the move to Internet Standard?<br>
>>> <br>
>>> Smith<br>
>>> <br>
>>> /**<br>
>>> Smith Kennedy<br>
>>> Wireless & Standards Architect - IPG-PPS<br>
>>> Standards - IEEE ISTO PWG / Bluetooth SIG / Wi-Fi Alliance / NFC Forum / USB-IF<br>
>>> Chair, IEEE ISTO Printer Working Group<br>
>>> HP Inc.<br>
>>> */<br>
>>> <br>
>>> <br>
>>> <br>
>>>> On Jun 25, 2018, at 5:23 PM, Michael Sweet <<a href="mailto:msweet@apple.com">msweet@apple.com</a>> wrote:<br>
>>>> <br>
>>>> *Internet Standard*<br>
>>>> <br>
>>>>> Begin forwarded message:<br>
>>>>> <br>
>>>>> From: The IESG <<a href="mailto:iesg-secretary@ietf.org">iesg-secretary@ietf.org</a>><br>
>>>>> Subject: Protocol Action: Internet Printing Protocol/1.1: Model and Semantics to Internet Standard<br>
>>>>> Date: June 25, 2018 at 5:15:02 PM EDT<br>
>>>>> To: IETF-Announce <<a href="mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a>><br>
>>>>> Cc: The IESG <<a href="mailto:iesg@ietf.org">iesg@ietf.org</a>>, Barry Leiba <<a href="mailto:barryleiba@computer.org">barryleiba@computer.org</a>>, <a href="mailto:draft-sweet-rfc2911bis@ietf.org">draft-sweet-rfc2911bis@ietf.<wbr>org</a>, <a href="mailto:draft-sweet-rfc2910bis@ietf.org">draft-sweet-rfc2910bis@ietf.<wbr>org</a>, <a href="mailto:barryleiba@computer.org">barryleiba@computer.org</a>, <a href="mailto:rfc-editor@rfc-editor.org">rfc-editor@rfc-editor.org</a><br>
>>>>> Resent-From: <a href="mailto:alias-bounces@ietf.org">alias-bounces@ietf.org</a><br>
>>>>> Resent-To: <a href="mailto:msweet@apple.com">msweet@apple.com</a>, <a href="mailto:blueroofmusic@gmail.com">blueroofmusic@gmail.com</a><br>
>>>>> <br>
>>>>> The IESG has approved changing the status of the following document:<br>
>>>>> - Internet Printing Protocol/1.1: Model and Semantics<br>
>>>>> (rfc8011) to Internet Standard<br>
>>>>> <br>
>>>>> This protocol action is documented at:<br>
>>>>> <a href="https://datatracker.ietf.org/doc/status-change-change-ipp-to-internet-standard/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/<wbr>doc/status-change-change-ipp-<wbr>to-internet-standard/</a><br>
>>>>> <br>
>>>>> A URL of the affected document is:<br>
>>>>> <a href="https://datatracker.ietf.org/doc/rfc8011/" rel="noreferrer" target="_blank">https://datatracker.ietf.org/<wbr>doc/rfc8011/</a><br>
>>>>> <br>
>>>>> Status Change Details:<br>
>>>>> <br>
>>>>> As specified in RFC 6410:<br>
>>>>> <br>
>>>>> (1) There are at least two independent interoperating implementations<br>
>>>>> with widespread deployment and successful operational experience.<br>
>>>>> <br>
>>>>> - Over 98% of all digital network printers shipped in the last<br>
>>>>> decade support IPP/1.1 (originally defined in RFC 2910/2911,<br>
>>>>> September 2000).<br>
>>>>> <br>
>>>>> (2) There are no errata against the specification that would cause a<br>
>>>>> new implementation to fail to interoperate with deployed ones.<br>
>>>>> <br>
>>>>> - There are currently no errata against RFC 8010/8011.<br>
>>>>> <br>
>>>>> (3) There are no unused features in the specification that greatly<br>
>>>>> increase implementation complexity.<br>
>>>>> <br>
>>>>> - There are no unused features in RFC 8010/8011.<br>
>>>>> <br>
>>>>> - The Purge-Jobs operation (from RFC 2911) is DEPRECATED in<br>
>>>>> RFC 8011 (page 73) with "SHOULD NOT support" because it<br>
>>>>> destroys Printer accounting implementation. This operation<br>
>>>>> has never been widely implemented in digital network printers.<br>
>>>>> <br>
>>>>> - The Restart-Job operation (from RFC 2911) is DEPRECATED in<br>
>>>>> RFC 8011 (page 89) with "SHOULD NOT support" because it<br>
>>>>> destroys Printer accounting implementation. This operation<br>
>>>>> has never been widely implemented in digital network printers.<br>
>>>>> <br>
>>>>> (4) If the technology required to implement the specification<br>
>>>>> requires patented or otherwise controlled technology, then the<br>
>>>>> set of implementations must demonstrate at least two independent,<br>
>>>>> separate and successful uses of the licensing process.<br>
>>>>> <br>
>>>>> - There is no patented or otherwise controlled technology that<br>
>>>>> is required to implement IPP/1.1 per RFC 8010/8011.<br>
>>>>> <br>
>>>>> Personnel<br>
>>>>> <br>
>>>>> Alexey Melnikov is the responsible Area Director.<br>
>>>>> <br>
>>>>> <br>
>>>>> <br>
>>>> <br>
>>>> ______________________________<wbr>___________________________<br>
>>>> Michael Sweet, Senior Printing System Engineer<br>
>>>> <br>
>>>> ______________________________<wbr>_________________<br>
>>>> ipp mailing list<br>
>>>> <a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
>>>> <a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/<wbr>listinfo/ipp</a><br>
>>> <br>
>> <br>
>> ______________________________<wbr>___________________________<br>
>> Michael Sweet, Senior Printing System Engineer<br>
>> <br>
>> <br>
>> ______________________________<wbr>_________________<br>
>> ipp mailing list<br>
>> <a href="mailto:ipp@pwg.org">ipp@pwg.org</a><br>
>> <a href="https://www.pwg.org/mailman/listinfo/ipp" rel="noreferrer" target="_blank">https://www.pwg.org/mailman/<wbr>listinfo/ipp</a><br>
>> <br>
>> <br>
>> <br>
> <br>
> ______________________________<wbr>___________________________<br>
> Michael Sweet, Senior Printing System Engineer<br>
> <br>
<br>
</div></div></blockquote></div><br></div>