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

Russ Housley <housley@vigilsec.com> Wed, 20 June 2018 15:21 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: spasm@ietfa.amsl.com
Delivered-To: spasm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 141851310C7 for <spasm@ietfa.amsl.com>; Wed, 20 Jun 2018 08:21:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M3H8wzg0oon2 for <spasm@ietfa.amsl.com>; Wed, 20 Jun 2018 08:21:13 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19F621310C6 for <spasm@ietf.org>; Wed, 20 Jun 2018 08:21:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 1D32630063A for <spasm@ietf.org>; Wed, 20 Jun 2018 11:11:54 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id wX3HjZpeQVwF for <spasm@ietf.org>; Wed, 20 Jun 2018 11:11:52 -0400 (EDT)
Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 3A3FE3004B7; Wed, 20 Jun 2018 11:11:52 -0400 (EDT)
From: Russ Housley <housley@vigilsec.com>
Message-Id: <7C1AAC8D-BF70-4A8F-A486-77731EB8BC74@vigilsec.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_D9F0A6F7-B2BC-4697-A5A6-38774F7448C8"
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Date: Wed, 20 Jun 2018 11:11:52 -0400
In-Reply-To: <56E0819D-6A8C-45A0-A90A-3585AE2DA580@nostrum.com>
Cc: Jim Schaad <ietf@augustcellars.com>, SPASM <spasm@ietf.org>, IESG <iesg@ietf.org>, draft-ietf-lamps-rfc5750-bis@ietf.org
To: Ben Campbell <ben@nostrum.com>
References: <152938120582.3146.786592198431535201.idtracker@ietfa.amsl.com> <000701d40843$c29d0b50$47d721f0$@augustcellars.com> <56E0819D-6A8C-45A0-A90A-3585AE2DA580@nostrum.com>
X-Mailer: Apple Mail (2.3445.8.2)
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/MoTrMBF4qXsjee6gDYl-MMD0GEA>
Subject: Re: [lamps] Ben Campbell's Yes on draft-ietf-lamps-rfc5750-bis-06: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "This is a venue for discussion of doing Some Pkix And SMime \(spasm\) work." <spasm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spasm>, <mailto:spasm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spasm/>
List-Post: <mailto:spasm@ietf.org>
List-Help: <mailto:spasm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spasm>, <mailto:spasm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Jun 2018 15:21:14 -0000

Ben:
> 
>>> §1.4 (and subsequent change version): I infer from the section titles that the
>>> normative keywords in these sections are intended to describe
>>> requirements added to those versions, not new requirements in _this_
>>> version. It would be better to make that explicit; the body text should stand
>>> alone without the titles.
>> 
>> Yes that is what is intended to be said.  I agree and thus did not use keywords in section 1.6.
>> 
>> This is historic text copied from a previous version and as such I am slightly reluctant to change.
>> EKR and Russ - what do you think?
> 
> It’s not a big deal one way or another, but a simple note that says “Version X.Y added the following:” would help.

I do not understand your suggestion.  This document specifies Version 4.0, and these sections describe the evolution from version 3 (the first one that the IETF produced) to this version.

1.4.  Changes from S/MIME v3 to S/MIME v3.1
1.5.  Changes from S/MIME v3.1 to S/MIME v3.2
1.6.  Changes since S/MIME 3.2

Russ