Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Mark Delany
> I admit that I also got confused a few times while working on the DKIM > documents and keeping it straight as to which section was referring to > which set of arguments. Having them use different values and different > tags for items that were conceptually the same was an unfortunate aspect > asp

Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Tony Hansen
On 10/20/2013 3:55 PM, Dave Crocker wrote: > On 10/20/2013 3:50 PM, Tony Hansen wrote: >> Perhaps, if this document is ever cracked open again, it would be useful >> to tag things better to make it painfully obvious what is being >> discussed. For example, >> >> v= [Signature] Version (plain-t

Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Tony Hansen
On 10/20/2013 9:43 AM, Barry Leiba wrote: > No, wait: the reporter is confused, both about this errata report and > the companion one (h= vs a=). > > Majid & Nazilla: You are looking at the section related to the key > records in DNS, and reading it as though it were about the signature > header in

Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Dave Crocker
On 10/20/2013 4:00 PM, Tony Hansen wrote: > Use a "-" and I agree completely with this naming convention: > > Signature-v = > > Key-h = > > (Rulenames can use a hyphen, but not a period.) was staying with the email header field notational form and hadn't thought to make it work in the

Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Dave Crocker
On 10/20/2013 3:50 PM, Tony Hansen wrote: > Perhaps, if this document is ever cracked open again, it would be useful > to tag things better to make it painfully obvious what is being > discussed. For example, > > v= [Signature] Version (plain-text; REQUIRED) ... Within the definition text, p

Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Michael Thomas
On 10/20/2013 06:35 AM, Barry Leiba wrote: > This one's right, of course: no one uses "v=DKIM1"; it's always "v=1". > Authors, was this just left in from the "transition from DK" days? Hmm, my implementation (the first) has it as DKIM1. That says that it's been that way for a long time. Iirc, DK

Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Barry Leiba
No, wait: the reporter is confused, both about this errata report and the companion one (h= vs a=). Majid & Nazilla: You are looking at the section related to the key records in DNS, and reading it as though it were about the signature header in the message. It's true that "v=1" is correct in the

Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Barry Leiba
(Resending with Murray's new address.) This one's right, of course: no one uses "v=DKIM1"; it's always "v=1". Authors, was this just left in from the "transition from DK" days? Barry On Sun, Oct 20, 2013 at 8:01 AM, RFC Errata System wrote: > The following errata report has been submitted for

Re: [ietf-dkim] [Technical Errata Reported] RFC6376 (3758)

2013-10-20 Thread Barry Leiba
This one's right, of course: no one uses "v=DKIM1"; it's always "v=1". Authors, was this just left in from the "transition from DK" days? Barry On Sun, Oct 20, 2013 at 8:01 AM, RFC Errata System wrote: > The following errata report has been submitted for RFC6376, > "DomainKeys Identified Mail (