Hi Mike,
We need to look into this errata on RFC 8011.
Cheers,
- Ira
Ira McDonald (Musician / Software Architect)
Co-Chair - TCG Trusted Mobility Solutions WG
Co-Chair - TCG Metadata Access Protocol SG
Chair - Linux Foundation Open Printing WG
Secretary - IEEE-ISTO Printer Working Group
Co-Chair - IEEE-ISTO PWG Internet Printing Protocol WG
IETF Designated Expert - IPP & Printer MIB
Blue Roof Music / High North Inc
http://sites.google.com/site/blueroofmusichttp://sites.google.com/site/highnorthinc
mailto: blueroofmusic at gmail.com
(permanent) PO Box 221 Grand Marais, MI 49839 906-494-2434
---------- Forwarded message ---------
From: RFC Errata System <rfc-editor at rfc-editor.org>
Date: Fri, Apr 10, 2020 at 1:59 PM
Subject: [Technical Errata Reported] RFC8011 (6085)
To: <msweet at apple.com>, <blueroofmusic at gmail.com>, <iesg at ietf.org>
Cc: <thomas.urban at cepharum.de>, <rfc-editor at rfc-editor.org>
The following errata report has been submitted for RFC8011,
"Internet Printing Protocol/1.1: Model and Semantics".
--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6085
--------------------------------------
Type: Technical
Reported by: Thomas Urban <thomas.urban at cepharum.de>
Section: 5.1.4
Original Text
-------------
The 'keyword' attribute syntax is a sequence of characters, of length
1 to 255, containing only the US-ASCII [RFC20] encoded values for
lowercase letters ("a"-"z"), digits ("0"-"9"), hyphen ("-"), dot
("."), and underscore ("_"). The first character MUST be a lowercase
letter.
Corrected Text
--------------
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 ("_").
Notes
-----
First, the "keyword" syntax is applicable to values of enumerations
according to section 5.1.5 stating
Each value has an associated 'keyword' name.
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.
Second, section 5.1.4 is stating
The first character MUST be a lowercase letter.
referring to "a"-"z" according to enumeration of accepted characters given
right before that. In opposition to that statement 5.4.14 is declaring
The following standard 'keyword' values are defined in this document:
* '1.0' [..]
* '1.1' [..]
Neither of the two "keywords" start with a lowercase letter.
Instructions:
-------------
This erratum is currently posted as "Reported". If necessary, please
use "Reply All" to discuss whether it should be verified or
rejected. When a decision is reached, the verifying party
can log in to change the status and edit the report, if necessary.
--------------------------------------
RFC8011 (draft-sweet-rfc2911bis-11)
--------------------------------------
Title : Internet Printing Protocol/1.1: Model and Semantics
Publication Date : January 2017
Author(s) : M. Sweet, I. McDonald
Category : PROPOSED STANDARD
Source : IETF - NON WORKING GROUP
Area : N/A
Stream : IETF
Verifying Party : IESG
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.pwg.org/pipermail/ipp/attachments/20200410/9e7eeb10/attachment.html>