IETF Logo Mail Archive

Re: [Cacao] Consensus call for CACAO Charter

Michael Richardson <mcr@sandelman.ca> Tue, 25 June 2019 20:07 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: cacao@ietfa.amsl.com
Delivered-To: cacao@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F8131201C7 for <cacao@ietfa.amsl.com>; Tue, 25 Jun 2019 13:07:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 O6PRTGtCCvpR for <cacao@ietfa.amsl.com>; Tue, 25 Jun 2019 13:07:40 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7C50120020 for <cacao@ietf.org>; Tue, 25 Jun 2019 13:07:39 -0700 (PDT)
Received: from sandelman.ca (unknown [IPv6:2607:f0b0:f:2:56b2:3ff:fe0b:d84]) by tuna.sandelman.ca (Postfix) with ESMTP id D1F7F3808A; Tue, 25 Jun 2019 16:05:55 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 21DC5109C; Tue, 25 Jun 2019 16:07:38 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 1F772E8C; Tue, 25 Jun 2019 16:07:38 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Chris Inacio <inacio@cert.org>
cc: "cacao@ietf.org" <cacao@ietf.org>
In-Reply-To: <71E2F960-274F-4DA9-938A-E31AB0C474A4@cert.org>
References: <71E2F960-274F-4DA9-938A-E31AB0C474A4@cert.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.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: Tue, 25 Jun 2019 16:07:38 -0400
Message-ID: <6103.1561493258@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cacao/Vg31tYKB0ilvT_p-_77gLHAT_F4>
X-Mailman-Approved-At: Tue, 25 Jun 2019 23:19:06 -0700
Subject: Re: [Cacao] Consensus call for CACAO Charter
X-BeenThere: cacao@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Collaborative Automated Course of Action Operations <cacao.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cacao>, <mailto:cacao-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cacao/>
List-Post: <mailto:cacao@ietf.org>
List-Help: <mailto:cacao-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cacao>, <mailto:cacao-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Jun 2019 20:07:42 -0000

Chris Inacio <inacio@cert.org> wrote:
    > We have a new charter revision posted to the list [1] and available as
    > an internet-draft [2].  The charter addresses the comments made during
    > the previous call and tightens the scope of the work.  Please send any
    > comments on the charter to the list by June 28, 2019.

I have read the charter.

I understand all the words and the sentences, and I find them well formed and
clear at the level of english.

I have very little understanding of some of the details of the form of we are
going to specify.   If I make an analogy, it is as if you have announced in
1810 in New York City, that we will travel by "coveyance" to LA, and then
inserted some new words.

While I have heard of something called "trains" (I've never been on one),
other words like "interstate", "air-traffic control", "737MAX" and
"Tesla" are not helping me understand how many pairs of underwear to pack.
(But, gosh, I'm excited!)

What I know: It's gonna be JSON, and it's gonna be signed.
Beyond that, I have very little understanding of what will be contained/specified.

I'm afraid of the Functional Specification work, but maybe it can be done well.

I can't help with the writing, sorry.

--
]               never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email