Re: [Tools-discuss] [lamps] WG Last Call for draft-ietf-lamps-rfc7030est-clarify-02

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 27 April 2020 18:13 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC1183A1376 for <tools-discuss@ietfa.amsl.com>; Mon, 27 Apr 2020 11:13:08 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 rswQG6ssSn1A for <tools-discuss@ietfa.amsl.com>; Mon, 27 Apr 2020 11:13:04 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0A563A1443 for <tools-discuss@ietf.org>; Mon, 27 Apr 2020 11:13:03 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 1D62138980; Mon, 27 Apr 2020 14:11:11 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D7D9E10E; Mon, 27 Apr 2020 14:13:02 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Russ Housley <housley@vigilsec.com>, tools-discuss <tools-discuss@ietf.org>
In-Reply-To: <65EDFD81-BDF7-4F2B-B450-F8EB40AD1BF5@vigilsec.com>
References: <63B58892-60CB-42C9-8168-E5476E2F40CB@vigilsec.com> <7099E9D5-6254-4052-A881-0F86E7A68FA4@vigilsec.com> <65EDFD81-BDF7-4F2B-B450-F8EB40AD1BF5@vigilsec.com>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 25.1.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 27 Apr 2020 14:13:02 -0400
Message-ID: <7981.1588011182@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/tools-discuss/j3MRgdkljevmhS8LOz8XYbo7r3s>
Subject: Re: [Tools-discuss] [lamps] WG Last Call for draft-ietf-lamps-rfc7030est-clarify-02
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tools-discuss/>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Apr 2020 18:13:09 -0000

Russ Housley <housley@vigilsec.com> wrote:
    > Thanks for making the updates.  I compiled the ASN.1 module, and the
    > compiler caught something that I read past.  There is a missing letter
    > "a" in the ASN.1 module.  Also the text in Section 4.1 has a third
    > spelling.  Please make them all match ...

On a related topic,  I think that a significant place to offload the DT
infrastructure is in the draft submission system.

This could be split off *datatracker*.ietf.org, to something like
"submit.ietf.org" or some other name.

This would fit into the scalable stuff that Richard Barnes has been
advocating.   Splitting up idnits into several pieces would be good, I think.
We do YANG checks already.
I think we once had SNMP checks, but I'm unclear about that.

We should have some ASN.1 compile checks, and CDDL checks would come too.

These would all do very well inside a container that would execute with *no*
networking access: all references would need to be inside the container.
(Or it could run with very limited network access to our known sources)

The resulting container would be something that people could run locally if
they wanted.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-