Re: [Asdf] slight rewording of recharter proposal

Michael Richardson <mcr+ietf@sandelman.ca> Wed, 20 March 2024 09:43 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: asdf@ietfa.amsl.com
Delivered-To: asdf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 00CE9C151076 for <asdf@ietfa.amsl.com>; Wed, 20 Mar 2024 02:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C3798FbdXh1x for <asdf@ietfa.amsl.com>; Wed, 20 Mar 2024 02:43:47 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F977C14F605 for <asdf@ietf.org>; Wed, 20 Mar 2024 02:43:46 -0700 (PDT)
Received: from dyas.sandelman.ca (unknown [IPv6:2001:67c:370:128:116:fc1f:a863:7e73]) by relay.sandelman.ca (Postfix) with ESMTPS id 6189A1F4A8; Wed, 20 Mar 2024 09:43:43 +0000 (UTC)
Authentication-Results: relay.sandelman.ca; dkim=pass (2048-bit key; secure) header.d=sandelman.ca header.i=@sandelman.ca header.b="VxokstX0"; dkim-atps=neutral
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 0D232A0C77; Wed, 20 Mar 2024 19:43:39 +1000 (AEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=sandelman.ca; s=dyas; t=1710927819; bh=VVWBwbrYvWRsuRL+HBxsl3Dyh0C/7upsAvhLUG3Y8CM=; h=From:To:Subject:In-reply-to:References:Date:From; b=VxokstX0Pf89zfVKiirmURkvr/ojAVK+JpjfVrFYGruas2u/Cd9eAK5SNXJ5UHueA /e1V/Do/6F4TfskPCxtB1lV5L4UgHxHUu9GW1TUWIdM7Roplh5WlApfZmqcSxvuduJ /MbWVAkTTQEEHQWofzK0offjq/AmpdTc2TcHwjk0y1OJcY6UaqyMVMbxOWe6dHnwne Yi2XURf+fKr176SvxQ6guAB7KNjpCc4g4LemuFc7k83ErIJNDXwJBhg+C+ZA1aCE5T OcZRqQLxI8sP+mV0PuPZfQgNSGaR43VW2Y0UYQd1N1XHhRsf/P4nrclH04Naq3jCNF pWYwQtW5vuuug==
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 0AAC2A0A82; Wed, 20 Mar 2024 19:43:39 +1000 (AEST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@lear.ch>, asdf@ietf.org, Francesca Palombini <francesca.palombini@ericsson.com>
In-reply-to: <0bbf94c8-6b10-4ace-a4ca-5de0ab380acd@lear.ch>
References: <45325.1710652675@dyas> <0bbf94c8-6b10-4ace-a4ca-5de0ab380acd@lear.ch>
Comments: In-reply-to Eliot Lear <lear@lear.ch> message dated "Wed, 20 Mar 2024 10:32:43 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Wed, 20 Mar 2024 19:43:39 +1000
Message-ID: <168283.1710927819@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/asdf/iQndHKv6WPkD0UCI_Ruf0aCRR0g>
Subject: Re: [Asdf] slight rewording of recharter proposal
X-BeenThere: asdf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "A Semantic Description Format \(SDF\) for Things and their Interactions and Data" <asdf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/asdf>, <mailto:asdf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/asdf/>
List-Post: <mailto:asdf@ietf.org>
List-Help: <mailto:asdf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/asdf>, <mailto:asdf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Mar 2024 09:43:52 -0000

Eliot Lear <lear@lear.ch> wrote:
    > At the Prague IETF just about everyone in the room said they wanted to
    > work on NIPC, and then a bunch of people said they wanted to do so on
    > the mailing list.  I created a PR for this when you first came out with
    > a charter.  Where is that reflected?  And no, I don't think 24 hours

It's in the proposed charter text that was already there.

    > notice in the middle of an IETF is reasonable to close a charter
    > update.

Uhm, so this was a (hallway) request from Francesca that we detail what
extensions were envisioned, and I realized that the answer to that was
actually just the second paragraph, just poorly connected to the first.
Thus I introduced two words.

I could have waited *LONGER*, but isn't an entire IETF cycle long enough
already?

    > Frustratedly yours,

Trying to move this stuff forward as far as possible.


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