Re: [smime] [Editorial Errata Reported] RFC3394 (3358)

"Jim Schaad" <jimsch@augustcellars.com> Wed, 19 September 2012 15:42 UTC

Return-Path: <jimsch@augustcellars.com>
X-Original-To: smime@ietfa.amsl.com
Delivered-To: smime@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4A7C21F856C for <smime@ietfa.amsl.com>; Wed, 19 Sep 2012 08:42:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5nobXzTP5p08 for <smime@ietfa.amsl.com>; Wed, 19 Sep 2012 08:42:57 -0700 (PDT)
Received: from smtp1.pacifier.net (smtp1.pacifier.net [64.255.237.171]) by ietfa.amsl.com (Postfix) with ESMTP id 20F3E21F850C for <smime@ietf.org>; Wed, 19 Sep 2012 08:42:56 -0700 (PDT)
Received: from Tobias (50-39-234-129.bvtn.or.frontiernet.net [50.39.234.129]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: schaad@nwlink.com) by smtp1.pacifier.net (Postfix) with ESMTPSA id 94A7C2CA27; Wed, 19 Sep 2012 08:42:55 -0700 (PDT)
From: Jim Schaad <jimsch@augustcellars.com>
To: rhousley@rsasecurity.com, stephen.farrell@cs.tcd.ie, turners@ieca.com, paul.hoffman@vpnc.org, blaker@gmail.com
References: <20120918032427.261FDB1E004@rfc-editor.org>
In-Reply-To: <20120918032427.261FDB1E004@rfc-editor.org>
Date: Wed, 19 Sep 2012 08:41:31 -0700
Message-ID: <00c301cd967d$3e6c0f40$bb442dc0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQGg2KVXljLfnjMqfy4E0I8zi8LnV5frSLww
Content-Language: en-us
Cc: dlitz@dlitz.net, smime@ietf.org
Subject: Re: [smime] [Editorial Errata Reported] RFC3394 (3358)
X-BeenThere: smime@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SMIME Working Group <smime.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/smime>, <mailto:smime-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/smime>
List-Post: <mailto:smime@ietf.org>
List-Help: <mailto:smime-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/smime>, <mailto:smime-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Sep 2012 15:42:57 -0000

As it stands I would say that this errata needs to be rejected.


I accept the basic premise of the errata, that when you start step 3 the
value of t might not be well defined, however

1.  the value of s is well defined and therefore does not need to be
redefined, and 
2. the value of t needs to be replaced with s in both locations that it
occurs.

Jim


> -----Original Message-----
> From: RFC Errata System [mailto:rfc-editor@rfc-editor.org]
> Sent: Monday, September 17, 2012 8:24 PM
> To: jimsch@exmsft.com; rhousley@rsasecurity.com;
> stephen.farrell@cs.tcd.ie; turners@ieca.com; paul.hoffman@vpnc.org;
> blaker@gmail.com
> Cc: dlitz@dlitz.net; smime@ietf.org; rfc-editor@rfc-editor.org
> Subject: [Editorial Errata Reported] RFC3394 (3358)
> 
> 
> The following errata report has been submitted for RFC3394,
> "Advanced Encryption Standard (AES) Key Wrap Algorithm".
> 
> --------------------------------------
> You may review the report below and at:
> http://www.rfc-editor.org/errata_search.php?rfc=3394&eid=3358
> 
> --------------------------------------
> Type: Editorial
> Reported by: Dwayne Litzenberger <dlitz@dlitz.net>
> 
> Section: 2.2.1
> 
> Original Text
> -------------
>    3) Output the results.
> 
>        Set C[0] = A[t]
>        For i = 1 to n
>            C[i] = R[t][i]
> 
> Corrected Text
> --------------
>    3) Output the results.
> 
>        Set C[0] = A[t]
>        For i = 1 to n
>            C[i] = R[s][i], where s = 6n
> 
> Notes
> -----
> 
> 
> 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.
> 
> --------------------------------------
> RFC3394 (draft-ietf-smime-aes-keywrap-00)
> --------------------------------------
> Title               : Advanced Encryption Standard (AES) Key Wrap
Algorithm
> Publication Date    : September 2002
> Author(s)           : J. Schaad, R. Housley
> Category            : INFORMATIONAL
> Source              : S/MIME Mail Security
> Area                : Security
> Stream              : IETF
> Verifying Party     : IESG