Re: [Cacao] [EXT] Consensus call for CACAO Charter

Chris Inacio <inacio@cert.org> Tue, 25 June 2019 15:20 UTC

Return-Path: <inacio@cert.org>
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 F2C3612047F for <cacao@ietfa.amsl.com>; Tue, 25 Jun 2019 08:20:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 nBnF4fedGpG9 for <cacao@ietfa.amsl.com>; Tue, 25 Jun 2019 08:20:15 -0700 (PDT)
Received: from veto.sei.cmu.edu (veto.sei.cmu.edu [147.72.252.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A502C12051C for <cacao@ietf.org>; Tue, 25 Jun 2019 08:20:14 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by veto.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x5PFK8ZH001541; Tue, 25 Jun 2019 11:20:09 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 veto.sei.cmu.edu x5PFK8ZH001541
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1561476009; bh=zNEIanQ4P+pprquokj1gbMcLAnFS6rJAH0sVeegCdS0=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=dBfW+yry39n/Wy2ub2wWxOe468e5Zg8VIdoRI8wZOUSGyE/DXDnLQDoH7+PpNLnYe TBAjE6SeoN9FhAIo+y205/Nbw54702j1XtrZdvz5Ee+RK6Gv5Mx29mk/SwYSIPYUWh XZ7AMVnD022sc8g7Yue9L/91XQBqP5fED0ialWdk=
Received: from CASCADE.ad.sei.cmu.edu (cascade.ad.sei.cmu.edu [10.64.28.248]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id x5PFK7tt007556; Tue, 25 Jun 2019 11:20:07 -0400
Received: from MARATHON.ad.sei.cmu.edu ([10.64.28.250]) by CASCADE.ad.sei.cmu.edu ([10.64.28.248]) with mapi id 14.03.0439.000; Tue, 25 Jun 2019 11:20:06 -0400
From: Chris Inacio <inacio@cert.org>
To: Carsten Bormann <cabo@tzi.org>, Bret Jordan <bret_jordan=40symantec.com@dmarc.ietf.org>
CC: "cacao@ietf.org" <cacao@ietf.org>
Thread-Topic: [Cacao] [EXT] Consensus call for CACAO Charter
Thread-Index: AQHVK2l3qibc51vyY0C8wiYiBP4TjA==
Date: Tue, 25 Jun 2019 15:20:06 +0000
Message-ID: <etPan.5d123ba6.6d0f767d.1c9@cert.org>
References: <71E2F960-274F-4DA9-938A-E31AB0C474A4@cert.org> <9BD47F64-D893-4416-8013-02AE2527271B@symantec.com> <2705E843-FAF1-4512-9B9C-D91625A9A383@tzi.org>
In-Reply-To: <2705E843-FAF1-4512-9B9C-D91625A9A383@tzi.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.64.201.7]
Content-Type: multipart/alternative; boundary="_000_etPan5d123ba66d0f767d1c9certorg_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/cacao/emFZf_yhmfPGAJPZTorC65Udl2g>
Subject: Re: [Cacao] [EXT] 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 15:20:22 -0000

I tried and clearly failed to state that a data model would be separate from the serialization and that JSON serializations (or others) would still be possible even if some other language were used for the data model.  Also - I agree that JSON (having serialization in its name) is generally not a data modeling language.  (I’m sure JSON as a data modeling language can be fixed with a sufficient amount of prose around the JSON text.)

Any language you would like to propose?

* CACAO data model
A data model will be developed in an appropriate language that will allow serialization into data serialization formats including at a minimum JSON and possibly others.

Any better?




On June 25, 2019 at 2:07:39 AM, Carsten Bormann (cabo@tzi.org<mailto:cabo@tzi.org>) wrote:

Well, you will need to make a change that is indicative of understanding the difference between a data serialization format (intended here: JSON) and a data modeling language (not decided, might be YANG, or tables written in English, or both).

How do you propose to fix this?

Grüße, Carsten


> On Jun 25, 2019, at 07:59, Bret Jordan <Bret_Jordan=40symantec.com@dmarc.ietf.org> wrote:
>
> I do not agree with that proposed change.
>
> Bret
>
> Sent from my Commodore 128D
>
> PGP Fingerprint: 63B4 FC53 680A 6B7D 1447 F2C0 74F8 ACAE 7415 0050
>
> On Jun 24, 2019, at 4:21 PM, 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.
>>
>> At this point the chairs (and the AD’s) are concerned with the number of people willing to volunteer to edit documents. There have been a number of people willing to review documents. This lack of volunteering to edit documents is the biggest factor slowing the chartering of this effort as a working group currently. If there are possible editors who have not participated in the IETF, please let them know to send an email to the list and volunteer.
>>
>> Lastly, with respect to the “JSON Data Model” concerns that have been voiced on the list from Med and Carsten, we propose the following from:
>>
>> —
>>
>> o CACAO JSON Data Model
>>
>> * Create a JSON data model that can capture and enable
>> collaborative courses of action
>>
>>
>> to
>>
>> o CACAO Data Model
>> * Create a data model that can capture and enable collaborative courses of action in
>> an appropriate format which can be realized in JSON and/or other wire formats as appropriate
>>
>> —
>>
>>
>> Thanks,
>>
>> Joe and Chris
>>
>> [1] https://mailarchive.ietf.org/arch/msg/cacao/k7XkqboXMJYkAmCBT99SJzQLTq8
>> [2] https://tools.ietf.org/html/draft-jordan-cacao-charter-06
>>
>> --
>> Cacao mailing list
>> Cacao@ietf.org
>> https://clicktime.symantec.com/3XykSkxSzK393g6kotqED3o7Vc?u=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Fcacao
> --
> Cacao mailing list
> Cacao@ietf.org
> https://www.ietf.org/mailman/listinfo/cacao