attachment
<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Ira,<div class=""><br class=""></div><div class="">Yes, the consensus (with corrections) is to use the following text:</div><div class=""><br class=""></div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">The 'keyword' attribute syntax is a sequence of characters, of length 1 to 255, containing only the US-ASCII [RFC20] encoded values for uppercase letters ("A"-"Z"), lowercase letters ("a"-"z"), digits ("0"-"9"), hyphen ("-"), dot ("."), and underscore ("_"). The first character SHOULD be a lowercase letter, and all letters SHOULD be lowercase.</div></blockquote><div class=""><br class=""><br class=""><blockquote type="cite" class="">On May 18, 2020, at 11:33 AM, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" class="">blueroofmusic@gmail.com</a>> wrote:<br class=""><br class="">Hi Mike,<br class=""><br class="">I think we still have an open action to send a consensus errata text to the RFC Editor?<br class=""><br class="">Cheers,<br class="">- Ira<br class=""><br class="">Ira McDonald (Musician / Software Architect)<br class="">Co-Chair - TCG Trusted Mobility Solutions WG<br class="">Co-Chair - TCG Metadata Access Protocol SG<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 href="http://sites.google.com/site/blueroofmusic" class="">http://sites.google.com/site/blueroofmusic</a><br class="">http://sites.google.com/site/highnorthinc<br class="">mailto: blueroofmusic@gmail.com<br class="">(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434<br class=""><br class=""><br class="">On Fri, Apr 24, 2020 at 9:21 AM Ira McDonald <blueroofmusic@gmail.com> wrote:<br class="">Hi,<br class=""><br class="">And of course "lowercase" (one word) and not "lower case"<br class=""><br class="">Cheers,<br class="">- Ira<br class=""><br class="">Ira McDonald (Musician / Software Architect)<br class="">Co-Chair - TCG Trusted Mobility Solutions WG<br class="">Co-Chair - TCG Metadata Access Protocol SG<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="">http://sites.google.com/site/blueroofmusic<br class="">http://sites.google.com/site/highnorthinc<br class="">mailto: blueroofmusic@gmail.com<br class="">(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434<br class=""><br class=""><br class="">On Fri, Apr 24, 2020 at 6:54 AM Michael Sweet via ipp <ipp@pwg.org> wrote:<br class="">Bill,<br class=""><br class="">Yes, of course. I guess I should proofread my minutes better... :)<br class=""><br class=""><br class="">> On Apr 24, 2020, at 12:10 AM, wamwagner@comcast.net wrote:<br class="">> <br class="">> I suggest that “…The first character SHOULD be a lower letter…” read “The first character SHOULD be a lower case letter” <br class="">> Thanks., <br class="">> Bill W.<br class="">> <br class="">> From: Michael Sweet via ipp<br class="">> Sent: Thursday, April 23, 2020 7:39 PM<br class="">> To: Michael Sweet<br class="">> Cc: PWG IPP Workgroup<br class="">> Subject: Re: [IPP] [Technical Errata Reported] RFC8011 (6085)<br class="">> <br class="">> Follow-up from today's IPP WG conference call - the consensus is to change section 5.1.4 to read:<br class="">> <br class="">> The 'keyword' attribute syntax is a sequence of characters, of length 1 to 255, containing only the US-ASCII [RFC20] encoded values for uppercase letters ("A"-"Z"), lowercase letters ("a"-"z"), digits ("0"-"9"), hyphen ("-"), dot ("."), and underscore ("_"). The first character SHOULD be a lower letter, and all letters SHOULD be lowercase.<br class="">> <br class="">> Status should change to "confirmed", and we (at some point) will want to do an update (sigh).<br class="">> <br class="">> <br class="">> <br class="">> On Apr 10, 2020, at 8:31 PM, Michael Sweet via ipp <ipp@pwg.org> wrote:<br class="">> <br class="">> Ira,<br class="">> <br class="">> Looks like my attempts to get my contact email changed haven't completely been successful, either... :/ Comments below...<br class="">> <br class="">> <br class="">> <br class="">> On Apr 10, 2020, at 2:07 PM, Ira McDonald <blueroofmusic@gmail.com> wrote:<br class="">> <br class="">> Hi Mike,<br class="">> <br class="">> We need to look into this errata on RFC 8011.<br class="">> ...<br class="">> --------------------------------------<br class="">> Type: Technical<br class="">> Reported by: Thomas Urban <thomas.urban@cepharum.de><br class="">> <br class="">> Section: 5.1.4<br class="">> <br class="">> Original Text<br class="">> -------------<br class="">> The 'keyword' attribute syntax is a sequence of characters, of length<br class="">> 1 to 255, containing only the US-ASCII [RFC20] encoded values for<br class="">> lowercase letters ("a"-"z"), digits ("0"-"9"), hyphen ("-"), dot<br class="">> ("."), and underscore ("_"). The first character MUST be a lowercase<br class="">> letter.<br class="">> <br class="">> Corrected Text<br class="">> --------------<br class="">> The 'keyword' attribute syntax is a sequence of characters, of length<br class="">> 1 to 255, containing only the US-ASCII [RFC20] encoded values for<br class="">> uppercase letters ("A"-"Z"), lowercase letters ("a"-"z"), digits <br class="">> ("0"-"9"), hyphen ("-"), dot ("."), and underscore ("_").<br class="">> <br class="">> I think we need to be careful about changing this, but AFAIK this change shouldn't cause a problem (CUPS will accept this, at least...)<br class="">> <br class="">> <br class="">> Notes<br class="">> -----<br class="">> First, the "keyword" syntax is applicable to values of enumerations according to section 5.1.5 stating<br class="">> <br class="">> Each value has an associated 'keyword' name.<br class="">> <br class="">> However, section 5.4.15 is declaring some enum-type attribute with names per integer value using uppercase letters in violation of 5.1.4. Those names are commonly used all over the specification and thus it is rather common to assume those values are meant to be keyword-compliant names of given enumeration.<br class="">> <br class="">> First, these are operation names, and second the keyword associated with an enum is informative and not transmitted over the wire...<br class="">> <br class="">> <br class="">> Second, section 5.1.4 is stating<br class="">> <br class="">> The first character MUST be a lowercase letter.<br class="">> <br class="">> referring to "a"-"z" according to enumeration of accepted characters given right before that. In opposition to that statement 5.4.14 is declaring<br class="">> <br class="">> The following standard 'keyword' values are defined in this document:<br class="">> <br class="">> * '1.0' [..]<br class="">> * '1.1' [..]<br class="">> <br class="">> Neither of the two "keywords" start with a lowercase letter.<br class="">> <br class="">> True.<br class="">> <br class="">> ________________________<br class="">> Michael Sweet<br class="">> <br class="">> <br class="">> <br class="">> _______________________________________________<br class="">> ipp mailing list<br class="">> ipp@pwg.org<br class="">> https://www.pwg.org/mailman/listinfo/ipp<br class="">> <br class="">> <br class="">> ________________________<br class="">> Michael Sweet<br class="">> <br class=""><br class="">________________________<br class="">Michael Sweet<br class=""><br class=""><br class=""><br class="">_______________________________________________<br class="">ipp mailing list<br class="">ipp@pwg.org<br class="">https://www.pwg.org/mailman/listinfo/ipp<br class=""></blockquote><br class=""><div class="">________________________<br class="">Michael Sweet<br class=""><br class=""><br class=""></div><br class=""></div></body></html>