Barry Leiba | 15 Apr 2012 00:25
Picon
Favicon
Gravatar

Re: [Technical Errata Reported] RFC6376 (3192)

I've checked this, and it's correct.  We copied the examples from 4871, and made the editorial error of adding a space without changing the hash.  I'll mark it as Verified if i hear no objections soon.


Barry

On Saturday, April 14, 2012, RFC Errata System wrote:

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_search.php?rfc=6376&eid=3192

--------------------------------------
Type: Technical
Reported by: John Hawthorn <john.hawthorn <at> gmail.com>

Section: Appendix A

Original Text
-------------
  From: Joe SixPack <joe <at> football.example.com>
  To: Suzie Q <suzie <at> shopping.example.net>
  Subject: Is dinner ready?
  Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
  Message-ID: <20030712040037.46341.5F8J <at> football.example.com>

  Hi.

  We lost the game.  Are you hungry yet?

  Joe.

Corrected Text
--------------
  From: Joe SixPack <joe <at> football.example.com>
  To: Suzie Q <suzie <at> shopping.example.net>
  Subject: Is dinner ready?
  Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
  Message-ID: <20030712040037.46341.5F8J <at> football.example.com>

  Hi.

  We lost the game. Are you hungry yet?

  Joe.

Notes
-----
This text appears three times, in A.1., A.2., and A.3.
Notice the double space after "game.", which renders the body hashes from A.2. and A.3. invalid.
The corrected text is the same as that in RFC 4871.

Instructions:
-------------
This errata 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 (IESG)
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
<div>
<p>I've checked this, and it's correct. &nbsp;We copied the examples from 4871, and made the editorial error of adding a space without changing the hash. &nbsp;I'll mark it as Verified if i hear no objections soon.</p>
<div><br></div>
<div>Barry<span></span><br><br>On Saturday, April 14, 2012, RFC Errata System  wrote:<br><blockquote class="gmail_quote">
<br>
The following errata report has been submitted for RFC6376,<br>
"DomainKeys Identified Mail (DKIM) Signatures".<br><br>
--------------------------------------<br>
You may review the report below and at:<br><a href="http://www.rfc-editor.org/errata_search.php?rfc=6376&amp;eid=3192" target="_blank">http://www.rfc-editor.org/errata_search.php?rfc=6376&amp;eid=3192</a><br><br>
--------------------------------------<br>
Type: Technical<br>
Reported by: John Hawthorn &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'john.hawthorn <at> gmail.com')">john.hawthorn <at> gmail.com</a>&gt;<br><br>
Section: Appendix A<br><br>
Original Text<br>
-------------<br>
 &nbsp; From: Joe SixPack &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'joe <at> football.example.com')">joe <at> football.example.com</a>&gt;<br>
 &nbsp; To: Suzie Q &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'suzie <at> shopping.example.net')">suzie <at> shopping.example.net</a>&gt;<br>
 &nbsp; Subject: Is dinner ready?<br>
 &nbsp; Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)<br>
 &nbsp; Message-ID: &lt;<a href="javascript:;" onclick="_e(event, 'cvml', '20030712040037.46341.5F8J <at> football.example.com')">20030712040037.46341.5F8J <at> football.example.com</a>&gt;<br><br>
 &nbsp; Hi.<br><br>
 &nbsp; We lost the game. &nbsp;Are you hungry yet?<br><br>
 &nbsp; Joe.<br><br>
Corrected Text<br>
--------------<br>
 &nbsp; From: Joe SixPack &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'joe <at> football.example.com')">joe <at> football.example.com</a>&gt;<br>
 &nbsp; To: Suzie Q &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'suzie <at> shopping.example.net')">suzie <at> shopping.example.net</a>&gt;<br>
 &nbsp; Subject: Is dinner ready?<br>
 &nbsp; Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)<br>
 &nbsp; Message-ID: &lt;<a href="javascript:;" onclick="_e(event, 'cvml', '20030712040037.46341.5F8J <at> football.example.com')">20030712040037.46341.5F8J <at> football.example.com</a>&gt;<br><br>
 &nbsp; Hi.<br><br>
 &nbsp; We lost the game. Are you hungry yet?<br><br>
 &nbsp; Joe.<br><br>
Notes<br>
-----<br>
This text appears three times, in A.1., A.2., and A.3.<br>
Notice the double space after "game.", which renders the body hashes from A.2. and A.3. invalid.<br>
The corrected text is the same as that in RFC 4871.<br><br>
Instructions:<br>
-------------<br>
This errata is currently posted as "Reported". If necessary, please<br>
use "Reply All" to discuss whether it should be verified or<br>
rejected. When a decision is reached, the verifying party (IESG)<br>
can log in to change the status and edit the report, if necessary.<br><br>
--------------------------------------<br>
RFC6376 (draft-ietf-dkim-rfc4871bis-15)<br>
--------------------------------------<br>
Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : DomainKeys Identified Mail (DKIM) Signatures<br>
Publication Date &nbsp; &nbsp;: September 2011<br>
Author(s) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed.<br>
Category &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: DRAFT STANDARD<br>
Source &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Domain Keys Identified Mail<br>
Area &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Security<br>
Stream &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: IETF<br>
Verifying Party &nbsp; &nbsp; : IESG<br>
</blockquote>
</div>
</div>
Barry Leiba | 15 Apr 2012 00:30
Picon
Favicon
Gravatar

Re: [Technical Errata Reported] RFC6376 (3192)

FWIW, the error was introduced by the RFC Editor, who surely used double-space-between-sentences style, and didn't know that in that particular case, the space matters.  And we didn't notice it in AUTH48 reviews.  Something we need to remember to check for, in the rare cases where it does matter.


Barry

On Saturday, April 14, 2012, Barry Leiba wrote:
I've checked this, and it's correct.  We copied the examples from 4871, and made the editorial error of adding a space without changing the hash.  I'll mark it as Verified if i hear no objections soon.

Barry

On Saturday, April 14, 2012, RFC Errata System wrote:

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_search.php?rfc=6376&eid=3192

--------------------------------------
Type: Technical
Reported by: John Hawthorn <john.hawthorn <at> gmail.com>

Section: Appendix A

Original Text
-------------
  From: Joe SixPack <joe <at> football.example.com>
  To: Suzie Q <suzie <at> shopping.example.net>
  Subject: Is dinner ready?
  Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
  Message-ID: <20030712040037.46341.5F8J <at> football.example.com>

  Hi.

  We lost the game.  Are you hungry yet?

  Joe.

Corrected Text
--------------
  From: Joe SixPack <joe <at> football.example.com>
  To: Suzie Q <suzie <at> shopping.example.net>
  Subject: Is dinner ready?
  Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
  Message-ID: <20030712040037.46341.5F8J <at> football.example.com>

  Hi.

  We lost the game. Are you hungry yet?

  Joe.

Notes
-----
This text appears three times, in A.1., A.2., and A.3.
Notice the double space after "game.", which renders the body hashes from A.2. and A.3. invalid.
The corrected text is the same as that in RFC 4871.

Instructions:
-------------
This errata 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 (IESG)
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
<div>
<p>FWIW, the error was introduced by the RFC Editor, who surely used double-space-between-sentences style, and didn't know that in that particular case, the space matters. &nbsp;And we didn't notice it in AUTH48 reviews. &nbsp;Something we need to remember to check for, in the rare cases where it does matter.</p>
<div>
<br>
</div>
<div>Barry<span></span><br><br>On Saturday, April 14, 2012, Barry Leiba  wrote:<br><blockquote class="gmail_quote">I've checked this, and it's correct. &nbsp;We copied the examples from 4871, and made the editorial error of adding a space without changing the hash. &nbsp;I'll mark it as Verified if i hear no objections soon.<div>
<br>
</div>
<div>Barry<span></span><br><br>On Saturday, April 14, 2012, RFC Errata System  wrote:<br><blockquote class="gmail_quote">
<br>
The following errata report has been submitted for RFC6376,<br>
"DomainKeys Identified Mail (DKIM) Signatures".<br><br>
--------------------------------------<br>
You may review the report below and at:<br><a href="http://www.rfc-editor.org/errata_search.php?rfc=6376&amp;eid=3192" target="_blank">http://www.rfc-editor.org/errata_search.php?rfc=6376&amp;eid=3192</a><br><br>
--------------------------------------<br>
Type: Technical<br>
Reported by: John Hawthorn &lt;<a>john.hawthorn <at> gmail.com</a>&gt;<br><br>
Section: Appendix A<br><br>
Original Text<br>
-------------<br>
 &nbsp; From: Joe SixPack &lt;<a>joe <at> football.example.com</a>&gt;<br>
 &nbsp; To: Suzie Q &lt;<a>suzie <at> shopping.example.net</a>&gt;<br>
 &nbsp; Subject: Is dinner ready?<br>
 &nbsp; Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)<br>
 &nbsp; Message-ID: &lt;<a>20030712040037.46341.5F8J <at> football.example.com</a>&gt;<br><br>
 &nbsp; Hi.<br><br>
 &nbsp; We lost the game. &nbsp;Are you hungry yet?<br><br>
 &nbsp; Joe.<br><br>
Corrected Text<br>
--------------<br>
 &nbsp; From: Joe SixPack &lt;<a>joe <at> football.example.com</a>&gt;<br>
 &nbsp; To: Suzie Q &lt;<a>suzie <at> shopping.example.net</a>&gt;<br>
 &nbsp; Subject: Is dinner ready?<br>
 &nbsp; Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)<br>
 &nbsp; Message-ID: &lt;<a>20030712040037.46341.5F8J <at> football.example.com</a>&gt;<br><br>
 &nbsp; Hi.<br><br>
 &nbsp; We lost the game. Are you hungry yet?<br><br>
 &nbsp; Joe.<br><br>
Notes<br>
-----<br>
This text appears three times, in A.1., A.2., and A.3.<br>
Notice the double space after "game.", which renders the body hashes from A.2. and A.3. invalid.<br>
The corrected text is the same as that in RFC 4871.<br><br>
Instructions:<br>
-------------<br>
This errata is currently posted as "Reported". If necessary, please<br>
use "Reply All" to discuss whether it should be verified or<br>
rejected. When a decision is reached, the verifying party (IESG)<br>
can log in to change the status and edit the report, if necessary.<br><br>
--------------------------------------<br>
RFC6376 (draft-ietf-dkim-rfc4871bis-15)<br>
--------------------------------------<br>
Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : DomainKeys Identified Mail (DKIM) Signatures<br>
Publication Date &nbsp; &nbsp;: September 2011<br>
Author(s) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed.<br>
Category &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: DRAFT STANDARD<br>
Source &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Domain Keys Identified Mail<br>
Area &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Security<br>
Stream &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: IETF<br>
Verifying Party &nbsp; &nbsp; : IESG<br>
</blockquote>
</div>
</blockquote>
</div>
</div>
Dave Crocker | 15 Apr 2012 00:26
Favicon

Re: [Technical Errata Reported] RFC6376 (3192)

+1


/d

--

Dave Crocker
bbiw.net



-----Original Message-----
From: Barry Leiba <barryleiba <at> computer.org>
To: RFC Errata System <rfc-editor <at> rfc-editor.org>
Cc: "dcrocker <at> bbiw.net" <dcrocker <at> bbiw.net>, "tony+dkimov <at> maillennium.att.com" <tony+dkimov <at> maillennium.att.com>, "msk <at> cloudmark.com" <msk <at> cloudmark.com>, "stephen.farrell <at> cs.tcd.ie" <stephen.farrell <at> cs.tcd.ie>, "turners <at> ieca.com" <turners <at> ieca.com>, "barryleiba <at> computer.org" <barryleiba <at> computer.org>, "john.hawthorn <at> gmail.com" <john.hawthorn <at> gmail.com>, "ietf-dkim <at> mipassoc.org" <ietf-dkim <at> mipassoc.org>
Sent: Sat, 14 Apr 2012 3:25 PM
Subject: Re: [Technical Errata Reported] RFC6376 (3192)

I've checked this, and it's correct.  We copied the examples from 4871, and made the editorial error of adding a space without changing the hash.  I'll mark it as Verified if i hear no objections soon.

Barry

On Saturday, April 14, 2012, RFC Errata System wrote:

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_search.php?rfc=6376&eid=3192

--------------------------------------
Type: Technical
Reported by: John Hawthorn <john.hawthorn <at> gmail.com>

Section: Appendix A

Original Text
-------------
  From: Joe SixPack <joe <at> football.example.com>
  To: Suzie Q <suzie <at> shopping.example.net>
  Subject: Is dinner ready?
  Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
  Message-ID: <20030712040037.46341.5F8J <at> football.example.com>

  Hi.

  We lost the game.  Are you hungry yet?

  Joe.

Corrected Text
--------------
  From: Joe SixPack <joe <at> football.example.com>
  To: Suzie Q <suzie <at> shopping.example.net>
  Subject: Is dinner ready?
  Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
  Message-ID: <20030712040037.46341.5F8J <at> football.example.com>

  Hi.

  We lost the game. Are you hungry yet?

  Joe.

Notes
-----
This text appears three times, in A.1., A.2., and A.3.
Notice the double space after "game.", which renders the body hashes from A.2. and A.3. invalid.
The corrected text is the same as that in RFC 4871.

Instructions:
-------------
This errata 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 (IESG)
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
<div>
<div>
<p>+1<br><br><p><br>/d</p>
<p>--</p>
<p>Dave Crocker<br><a href="http://bbiw.net">bbiw.net</a></p>
</p>
<br><br>-----Original Message-----<br>From: Barry Leiba &lt;barryleiba <at> computer.org&gt;<br>To: RFC Errata System &lt;rfc-editor <at> rfc-editor.org&gt;<br>Cc: "dcrocker <at> bbiw.net" &lt;dcrocker <at> bbiw.net&gt;, "tony+dkimov <at> maillennium.att.com" &lt;tony+dkimov <at> maillennium.att.com&gt;, "msk <at> cloudmark.com" &lt;msk <at> cloudmark.com&gt;, "stephen.farrell <at> cs.tcd.ie" &lt;stephen.farrell <at> cs.tcd.ie&gt;, "turners <at> ieca.com" &lt;turners <at> ieca.com&gt;, "barryleiba <at> computer.org" &lt;barryleiba <at> computer.org&gt;, "john.hawthorn <at> gmail.com" &lt;john.hawthorn <at> gmail.com&gt;, "ietf-dkim <at> mipassoc.org" &lt;ietf-dkim <at> mipassoc.org&gt;<br>Sent: Sat, 14 Apr 2012 3:25 PM<br>Subject: Re: [Technical Errata Reported] RFC6376 (3192)<br><br>
</div>I've checked this, and it's correct. &nbsp;We copied the examples from 4871, and made the editorial error of adding a space without changing the hash. &nbsp;I'll mark it as Verified if i hear no objections soon.<div><br></div>
<div>Barry<span></span><br><br>On Saturday, April 14, 2012, RFC Errata System  wrote:<br><blockquote class="gmail_quote">
<br>
The following errata report has been submitted for RFC6376,<br>
"DomainKeys Identified Mail (DKIM) Signatures".<br><br>
--------------------------------------<br>
You may review the report below and at:<br><a href="http://www.rfc-editor.org/errata_search.php?rfc=6376&amp;eid=3192" target="_blank">http://www.rfc-editor.org/errata_search.php?rfc=6376&amp;eid=3192</a><br><br>
--------------------------------------<br>
Type: Technical<br>
Reported by: John Hawthorn &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'john.hawthorn <at> gmail.com')">john.hawthorn <at> gmail.com</a>&gt;<br><br>
Section: Appendix A<br><br>
Original Text<br>
-------------<br>
 &nbsp; From: Joe SixPack &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'joe <at> football.example.com')">joe <at> football.example.com</a>&gt;<br>
 &nbsp; To: Suzie Q &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'suzie <at> shopping.example.net')">suzie <at> shopping.example.net</a>&gt;<br>
 &nbsp; Subject: Is dinner ready?<br>
 &nbsp; Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)<br>
 &nbsp; Message-ID: &lt;<a href="javascript:;" onclick="_e(event, 'cvml', '20030712040037.46341.5F8J <at> football.example.com')">20030712040037.46341.5F8J <at> football.example.com</a>&gt;<br><br>
 &nbsp; Hi.<br><br>
 &nbsp; We lost the game. &nbsp;Are you hungry yet?<br><br>
 &nbsp; Joe.<br><br>
Corrected Text<br>
--------------<br>
 &nbsp; From: Joe SixPack &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'joe <at> football.example.com')">joe <at> football.example.com</a>&gt;<br>
 &nbsp; To: Suzie Q &lt;<a href="javascript:;" onclick="_e(event, 'cvml', 'suzie <at> shopping.example.net')">suzie <at> shopping.example.net</a>&gt;<br>
 &nbsp; Subject: Is dinner ready?<br>
 &nbsp; Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)<br>
 &nbsp; Message-ID: &lt;<a href="javascript:;" onclick="_e(event, 'cvml', '20030712040037.46341.5F8J <at> football.example.com')">20030712040037.46341.5F8J <at> football.example.com</a>&gt;<br><br>
 &nbsp; Hi.<br><br>
 &nbsp; We lost the game. Are you hungry yet?<br><br>
 &nbsp; Joe.<br><br>
Notes<br>
-----<br>
This text appears three times, in A.1., A.2., and A.3.<br>
Notice the double space after "game.", which renders the body hashes from A.2. and A.3. invalid.<br>
The corrected text is the same as that in RFC 4871.<br><br>
Instructions:<br>
-------------<br>
This errata is currently posted as "Reported". If necessary, please<br>
use "Reply All" to discuss whether it should be verified or<br>
rejected. When a decision is reached, the verifying party (IESG)<br>
can log in to change the status and edit the report, if necessary.<br><br>
--------------------------------------<br>
RFC6376 (draft-ietf-dkim-rfc4871bis-15)<br>
--------------------------------------<br>
Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : DomainKeys Identified Mail (DKIM) Signatures<br>
Publication Date &nbsp; &nbsp;: September 2011<br>
Author(s) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed.<br>
Category &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: DRAFT STANDARD<br>
Source &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Domain Keys Identified Mail<br>
Area &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Security<br>
Stream &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: IETF<br>
Verifying Party &nbsp; &nbsp; : IESG<br>
</blockquote>
</div>
</div>
Dave Crocker | 15 Apr 2012 00:32
Favicon

Re: [Technical Errata Reported] RFC6376 (3192)

raises a small question of needing notes to the editor advising hands off for such segments.


/d

--

Dave Crocker
bbiw.net



-----Original Message-----
From: Barry Leiba <barryleiba <at> computer.org>
To: Barry Leiba <barryleiba <at> computer.org>
Cc: RFC Errata System <rfc-editor <at> rfc-editor.org>, "dcrocker <at> bbiw.net" <dcrocker <at> bbiw.net>, "tony+dkimov <at> maillennium.att.com" <tony+dkimov <at> maillennium.att.com>, "msk <at> cloudmark.com" <msk <at> cloudmark.com>, "stephen.farrell <at> cs.tcd.ie" <stephen.farrell <at> cs.tcd.ie>, "turners <at> ieca.com" <turners <at> ieca.com>, "john.hawthorn <at> gmail.com" <john.hawthorn <at> gmail.com>, "ietf-dkim <at> mipassoc.org" <ietf-dkim <at> mipassoc.org>
Sent: Sat, 14 Apr 2012 3:30 PM
Subject: Re: [Technical Errata Reported] RFC6376 (3192)

FWIW, the error was introduced by the RFC Editor, who surely used double-space-between-sentences style, and didn't know that in that particular case, the space matters.  And we didn't notice it in AUTH48 reviews.  Something we need to remember to check for, in the rare cases where it does matter.

Barry

On Saturday, April 14, 2012, Barry Leiba wrote:
I've checked this, and it's correct.  We copied the examples from 4871, and made the editorial error of adding a space without changing the hash.  I'll mark it as Verified if i hear no objections soon.

Barry

On Saturday, April 14, 2012, RFC Errata System wrote:

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_search.php?rfc=6376&eid=3192

--------------------------------------
Type: Technical
Reported by: John Hawthorn <john.hawthorn <at> gmail.com>

Section: Appendix A

Original Text
-------------
  From: Joe SixPack <joe <at> football.example.com>
  To: Suzie Q <suzie <at> shopping.example.net>
  Subject: Is dinner ready?
  Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
  Message-ID: <20030712040037.46341.5F8J <at> football.example.com>

  Hi.

  We lost the game.  Are you hungry yet?

  Joe.

Corrected Text
--------------
  From: Joe SixPack <joe <at> football.example.com>
  To: Suzie Q <suzie <at> shopping.example.net>
  Subject: Is dinner ready?
  Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)
  Message-ID: <20030712040037.46341.5F8J <at> football.example.com>

  Hi.

  We lost the game. Are you hungry yet?

  Joe.

Notes
-----
This text appears three times, in A.1., A.2., and A.3.
Notice the double space after "game.", which renders the body hashes from A.2. and A.3. invalid.
The corrected text is the same as that in RFC 4871.

Instructions:
-------------
This errata 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 (IESG)
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
<div>
<div>
<p>raises a small question of needing notes to the editor advising hands off for such segments.<br><br><p><br>/d</p>
<p>--</p>
<p>Dave Crocker<br><a href="http://bbiw.net">bbiw.net</a></p>
</p>
<br><br>-----Original Message-----<br>From: Barry Leiba &lt;barryleiba <at> computer.org&gt;<br>To: Barry Leiba &lt;barryleiba <at> computer.org&gt;<br>Cc: RFC Errata System &lt;rfc-editor <at> rfc-editor.org&gt;, "dcrocker <at> bbiw.net" &lt;dcrocker <at> bbiw.net&gt;, "tony+dkimov <at> maillennium.att.com" &lt;tony+dkimov <at> maillennium.att.com&gt;, "msk <at> cloudmark.com" &lt;msk <at> cloudmark.com&gt;, "stephen.farrell <at> cs.tcd.ie" &lt;stephen.farrell <at> cs.tcd.ie&gt;, "turners <at> ieca.com" &lt;turners <at> ieca.com&gt;, "john.hawthorn <at> gmail.com" &lt;john.hawthorn <at> gmail.com&gt;, "ietf-dkim <at> mipassoc.org" &lt;ietf-dkim <at> mipassoc.org&gt;<br>Sent: Sat, 14 Apr 2012 3:30 PM<br>Subject: Re: [Technical Errata Reported] RFC6376 (3192)<br><br>
</div>FWIW, the error was introduced by the RFC Editor, who surely used double-space-between-sentences style, and didn't know that in that particular case, the space matters. &nbsp;And we didn't notice it in AUTH48 reviews. &nbsp;Something we need to remember to check for, in the rare cases where it does matter.<div>
<br>
</div>
<div>Barry<span></span><br><br>On Saturday, April 14, 2012, Barry Leiba  wrote:<br><blockquote class="gmail_quote">I've checked this, and it's correct. &nbsp;We copied the examples from 4871, and made the editorial error of adding a space without changing the hash. &nbsp;I'll mark it as Verified if i hear no objections soon.<div>
<br>
</div>
<div>Barry<span></span><br><br>On Saturday, April 14, 2012, RFC Errata System  wrote:<br><blockquote class="gmail_quote">
<br>
The following errata report has been submitted for RFC6376,<br>
"DomainKeys Identified Mail (DKIM) Signatures".<br><br>
--------------------------------------<br>
You may review the report below and at:<br><a href="http://www.rfc-editor.org/errata_search.php?rfc=6376&amp;eid=3192" target="_blank">http://www.rfc-editor.org/errata_search.php?rfc=6376&amp;eid=3192</a><br><br>
--------------------------------------<br>
Type: Technical<br>
Reported by: John Hawthorn &lt;<a>john.hawthorn <at> gmail.com</a>&gt;<br><br>
Section: Appendix A<br><br>
Original Text<br>
-------------<br>
 &nbsp; From: Joe SixPack &lt;<a>joe <at> football.example.com</a>&gt;<br>
 &nbsp; To: Suzie Q &lt;<a>suzie <at> shopping.example.net</a>&gt;<br>
 &nbsp; Subject: Is dinner ready?<br>
 &nbsp; Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)<br>
 &nbsp; Message-ID: &lt;<a>20030712040037.46341.5F8J <at> football.example.com</a>&gt;<br><br>
 &nbsp; Hi.<br><br>
 &nbsp; We lost the game. &nbsp;Are you hungry yet?<br><br>
 &nbsp; Joe.<br><br>
Corrected Text<br>
--------------<br>
 &nbsp; From: Joe SixPack &lt;<a>joe <at> football.example.com</a>&gt;<br>
 &nbsp; To: Suzie Q &lt;<a>suzie <at> shopping.example.net</a>&gt;<br>
 &nbsp; Subject: Is dinner ready?<br>
 &nbsp; Date: Fri, 11 Jul 2003 21:00:37 -0700 (PDT)<br>
 &nbsp; Message-ID: &lt;<a>20030712040037.46341.5F8J <at> football.example.com</a>&gt;<br><br>
 &nbsp; Hi.<br><br>
 &nbsp; We lost the game. Are you hungry yet?<br><br>
 &nbsp; Joe.<br><br>
Notes<br>
-----<br>
This text appears three times, in A.1., A.2., and A.3.<br>
Notice the double space after "game.", which renders the body hashes from A.2. and A.3. invalid.<br>
The corrected text is the same as that in RFC 4871.<br><br>
Instructions:<br>
-------------<br>
This errata is currently posted as "Reported". If necessary, please<br>
use "Reply All" to discuss whether it should be verified or<br>
rejected. When a decision is reached, the verifying party (IESG)<br>
can log in to change the status and edit the report, if necessary.<br><br>
--------------------------------------<br>
RFC6376 (draft-ietf-dkim-rfc4871bis-15)<br>
--------------------------------------<br>
Title &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : DomainKeys Identified Mail (DKIM) Signatures<br>
Publication Date &nbsp; &nbsp;: September 2011<br>
Author(s) &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; : D. Crocker, Ed., T. Hansen, Ed., M. Kucherawy, Ed.<br>
Category &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: DRAFT STANDARD<br>
Source &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Domain Keys Identified Mail<br>
Area &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: Security<br>
Stream &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;: IETF<br>
Verifying Party &nbsp; &nbsp; : IESG<br>
</blockquote>
</div>
</blockquote>
</div>
</div>
Dave Crocker | 16 Apr 2012 17:15

Re: [Technical Errata Reported] RFC6376 (3192)


On 4/16/2012 8:10 AM, RFC Editor wrote:
> Just a heads up that we will be reviewing this one internally with the
> team to raise our awareness of the issue.  Additionally, we agree with
> Dave, and encourage the inclusion of notes to help avoid such errors
> in the future.   

My guess is that the existing notation for communicating inline to the RFC
editor is sufficient.  That is, I'd expect the real issue being one of getting
us all to tell you what not to format, rather than one of creating a new notation.

d/
--

-- 

  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

Gmane