[lamps] Zaheduzzaman Sarker's No Objection on draft-ietf-lamps-cmp-updates-20: (with COMMENT)

Zaheduzzaman Sarker via Datatracker <noreply@ietf.org> Thu, 02 June 2022 11:10 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 95819C14CF0A; Thu, 2 Jun 2022 04:10:27 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Zaheduzzaman Sarker 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: Zaheduzzaman Sarker <Zaheduzzaman.Sarker@ericsson.com>
Message-ID: <165416822760.63579.6135080480690515830@ietfa.amsl.com>
Date: Thu, 02 Jun 2022 04:10:27 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/spasm/gai6azJRE2ET0sS4Ss7vjnV4Rz8>
Subject: [lamps] Zaheduzzaman Sarker's No Objection on draft-ietf-lamps-cmp-updates-20: (with COMMENT)
X-BeenThere: spasm@ietf.org
X-Mailman-Version: 2.1.39
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: Thu, 02 Jun 2022 11:10:27 -0000

Zaheduzzaman Sarker has entered the following ballot position for
draft-ietf-lamps-cmp-updates-20: No Objection

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:
----------------------------------------------------------------------

I share the concerns from my fellow ADs. This is a long diff/change document,
which not nice to read and can lead to confusion. I ,however, see this as a
short term fix and want to believe the implementer's and consumers of this doc
have given their consent to publish the document like it is . So I am balloting
no objection.

That said, this document need to describe the motivation to this publication.
so why updates and why not a -bis? to bring us on the same page. The shepherd's
write up hints the plan and reason but I would suggest to add those reasoning
and plans in the document itself.