[lamps] John Scudder's Abstain on draft-ietf-lamps-cmp-updates-20: (with COMMENT)

John Scudder via Datatracker <noreply@ietf.org> Wed, 01 June 2022 00:14 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: spasm@ietf.org
Delivered-To: spasm@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 72A05C159490; Tue, 31 May 2022 17:14:05 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: John Scudder via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-lamps-cmp-updates@ietf.org, lamps-chairs@ietf.org, spasm@ietf.org, housley@vigilsec.com, housley@vigilsec.com
X-Test-IDTracker: no
X-IETF-IDTracker: 8.3.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: John Scudder <jgs@juniper.net>
Message-ID: <165404244529.54811.9230884631422537145@ietfa.amsl.com>
Date: Tue, 31 May 2022 17:14:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/pwEPfdk0ZJEmwTjSr5r5cGPVWZY>
Subject: [lamps] John Scudder's Abstain on draft-ietf-lamps-cmp-updates-20: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.34
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, 01 Jun 2022 00:14:05 -0000

John Scudder has entered the following ballot position for
draft-ietf-lamps-cmp-updates-20: Abstain

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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-lamps-cmp-updates/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks to Russ Housley for the shepherd writeup and in particular for this
paragraph:

  When this update was started, the number of updates was expected to
  be smaller.  It is recognized that complex update documents place a
  burden on implementers.  So, when LAMPS WG tries to progress CMP to
  Internet Standard, a bis document will be produced to combine the
  base specification and the updates.

I can see that the effort that went into this document was needed. I can see
that it will be invaluable for preparing the bis. What I can't see is why
publishing it as an RFC will be beneficial, as opposed to keeping it as a WG
draft and using it to prepare the bis.