Re: [ietf-dkim] [Editorial Errata Reported] RFC6376 (5260)

[Pete Resnick <[e-mail]>]

Dave,

Our respective ages are getting up there and my senility is setting in 
in earnest, so I have some sympathy along these lines, but given that 
you are the author of RFC 5234, you might want to check section 2.3 of 
that document:

    ABNF permits the specification of literal text strings directly,
    enclosed in quotation marks.  Hence:

          command     =  "command string"

    Literal text strings are interpreted as a concatenated set of
    printable characters.

    NOTE:

       ABNF strings are case insensitive and the character set for these
       strings is US-ASCII.

    Hence:

          rulename = "abc"

    and:

          rulename = "aBc"

    will match "abc", "Abc", "aBc", "abC", "ABc", "aBC", "AbC", and
    "ABC".

       To specify a rule that is case sensitive, specify the characters
       individually.

RFC 7405 is also useful along these lines.

So, no error in 5322. As for the erratum below, not having ABNF for the 
header field does seem like a miss, though I'm not sure it should be 
marked as more than "Hold for document update".

pr
-- 
Pete Resnick <http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - [phone]

On 8 Feb 2018, at 9:30, Dave Crocker wrote:

> While possibly a nice addition to the specification, including this 
> ABNF rule does not correct an error in RFC 6376.
>
>
> As for header-field name case sensitivity, that is the purview of RFC 
> 5322, not RFC 6376.
>
> (FWIW, it does appear that there is an error in RFC 5322, since it 
> does not enforce case insensitity in the syntax, although it specifies 
> -- and intends -- it in the prose.)
>
> d/
>
>
>> The following errata report has been submitted for RFC6376,
>> "DomainKeys Identified Mail (DKIM) Signatures".
>>
>> --------------------------------------
>> You may review the report below and at:
>> http://www.rfc-editor.org/errata/eid5260
>>
>> --------------------------------------
>> Type: Editorial
>> Reported by: Ale <[e-mail]>
>>
>> Section: 3.5
>>
>> Original Text
>> -------------
>>
>>
>> Corrected Text
>> --------------
>> DKIM-Signature = "DKIM-Signature:" tag-list
>>
>> Notes
>> -----
>> A formal definition is needed to make it explicit that this header 
>> field name is case insensitive, like all the other header field 
>> names.
>>
>> 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.
>>
>> --------------------------------------
>> RFC6376 (draft-ietf-dkim-rfc4871bis-15)
>> --------------------------------------
>> Title               : DomainKeys Identified Mail (DKIM) Signatures
>> Publication Date    : September 2011
>> Author(s)           : D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, 
>> Ed.
>> Category            : DRAFT STANDARD
>> Source              : Domain Keys Identified Mail
>> Area                : Security
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>
>
> -- 
> Dave Crocker
> Brandenburg InternetWorking
> bbiw.net
_______________________________________________
NOTE WELL: This list operates according to
http://mipassoc.org/dkim/ietf-list-rules.html