Re: [lamps] Adam Roach's Yes on draft-ietf-lamps-rfc5750-bis-06: (with COMMENT)

Jim Schaad <ietf@augustcellars.com> Tue, 19 June 2018 02:54 UTC

From: Jim Schaad <ietf@augustcellars.com>
To: 'Adam Roach' <adam@nostrum.com>, 'The IESG' <iesg@ietf.org>
CC: draft-ietf-lamps-rfc5750-bis@ietf.org, 'Russ Housley' <housley@vigilsec.com>, lamps-chairs@ietf.org, housley@vigilsec.com, spasm@ietf.org
References: <152937589667.3120.11885793911908033876.idtracker@ietfa.amsl.com>
In-Reply-To: <152937589667.3120.11885793911908033876.idtracker@ietfa.amsl.com>
Date: Mon, 18 Jun 2018 19:54:31 -0700
Message-ID: <014f01d40778$da982120$8fc86360$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Language: en-us
Thread-Index: AQMizO8Tt+XNtfyVzYUX1lnWsk4Hx6HJVv+g
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/-Tge1e_7k1bQNNqXvskr_75HT7U>
Subject: Re: [lamps] Adam Roach's Yes on draft-ietf-lamps-rfc5750-bis-06: (with COMMENT)
Precedence: list


> -----Original Message-----
> From: Adam Roach <adam@nostrum.com>
> Sent: Monday, June 18, 2018 7:38 PM
> To: The IESG <iesg@ietf.org>
> Cc: draft-ietf-lamps-rfc5750-bis@ietf.org; Russ Housley
> <housley@vigilsec.com>; lamps-chairs@ietf.org; housley@vigilsec.com;
> spasm@ietf.org
> Subject: Adam Roach's Yes on draft-ietf-lamps-rfc5750-bis-06: (with
> COMMENT)
> 
> Adam Roach has entered the following ballot position for
> draft-ietf-lamps-rfc5750-bis-06: Yes
> 
> When responding, please keep the subject line intact and reply to all email
> addresses included in the To and CC lines. (Feel free to cut this introductory
> paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
> for more information about IESG DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-lamps-rfc5750-bis/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks to everyone for the work put into updating this document. I
> reviewed the diffs from the previous RFC, and the changes all seem to make
> sense.  I found a couple of minor editorial nits.
> 
> ---------------------------------------------------------------------------
> 
> §2.2.1:
> 
> >  Receiving agents MUST be able to parser and process a message
> > containing PKCS #6 extended certificates although ignoring those
> > certificates is expected behavior.
> 
> Nit: "...be able to parse..."
> 
> ---------------------------------------------------------------------------
> 
> §A.1:
> 
> >  -  Hash functions used to validate signatures on historic messages
> >     may longer be considered to be secure (see below).
> 
> Nit: "...may no longer..."
> 
> >     While there
> >     are not currently any known practical pre-image or second pre-
> >     image attacks against MD5 or SHA-1, the fact they are no longer
> >     considered to be collision resistant the security levels of the
> >     signatures are generally considered suspect.
> 
> This final clause appears to be missing some words. Consider rephrasing.
> 

          While there are not currently any known practical pre-image or second pre-image attacks against MD5 or SHA&nbhy;1, the fact they are no longer considered to be collision resistant implies that the security level of any signature that is created with that these hash algorithms should also be considered as suspect.

Re: [lamps] Adam Roach's Yes on draft-ietf-lamps-… Adam Roach
Re: [lamps] Adam Roach's Yes on draft-ietf-lamps-… Jim Schaad
[lamps] Adam Roach's Yes on draft-ietf-lamps-rfc5… Adam Roach