Re: [Cacao] Call for CACAO Charter Consensus

Joseph Salowey <joe@salowey.net> Fri, 31 May 2019 04:47 UTC

Return-Path: <joe@salowey.net>
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 F084F120019 for <cacao@ietfa.amsl.com>; Thu, 30 May 2019 21:47:34 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 E1n92xlLtKWQ for <cacao@ietfa.amsl.com>; Thu, 30 May 2019 21:47:33 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 26793120004 for <cacao@ietf.org>; Thu, 30 May 2019 21:47:33 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id h1so9912540qtp.1 for <cacao@ietf.org>; Thu, 30 May 2019 21:47:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rpKlzz2z7veokjGkKQxteP/2usEnylG7mfSpMg4OdIg=; b=c6sI9vq13hhfCHwjFtQpaeSYgSJnShf2SyzwW//4QLsM95MeyYRFa9SIiBGOYNTsgc R2YsFulPZaT/hf7JRkicllb4mgVeBikePcsfw78Aw5SmEEjDT6Yj/VmfvNty9OJ8/L1W d4WqQKQg7PbzhRX6CfYxLxpg+SQJaK4+jp9+0VWXRAXatwsKyHGk4chER6BBSS+gYUUL 99/+UqGK7W7qNbUhMVMiRsD63X2bk4EFK6oYiTcabsVS9OMA7vyiaQ8bzkyUjTHtXkIH zCdDHEsCZFmsTigkys1YJfPJeudRuMMgLbeBskOM18lliccqUJZ0UKvVPunRsJuDRPyH Clgg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rpKlzz2z7veokjGkKQxteP/2usEnylG7mfSpMg4OdIg=; b=bs525/PCfGkc2Jz8dlCwe/lyniz7I8jVuNgnYKmXlyoRkD3qBSMcb1vKsVA3YmMq3J 4d1R0+VGwA6UtOcU5SlqocSqULMvMm9wvvu0/kKgcA3Ih2hG/4j71AjnTzNWyJ15Sz2q /pJn5sbRCFuQhpKC7mcLdhqlaqecmoppRLc9+Lppt6XD24hBmwOG1aHqntUrf351aatz RY6LgWyuMRzgu71sFEQfc3rxgKuoJOioa2sgO7GE7O27pvgSHaGwh4IYSjkLT638rUlq p+LisgxAhgfb5z7Mcu0sPpQwly6Iu/h/h5e2EJXFGiJAR1U0RT/BU8PaxVo9ybH4n2PL N8wg==
X-Gm-Message-State: APjAAAWfNaaGcGCSFU4WWdICao1e9GYcI0ScGfYKT21Jn/VhxD85+g5U g6xIBwYt1k645J9mmv6GKXxVpnwqc/iq/mWEdW4y3Q==
X-Google-Smtp-Source: APXvYqzHqc956aFC4CK53h6uKFG3kdNMysihpTTMlpj95KwwHmYUFgBm0VuzZtl8AaxUmW2ePy00WfXS7vqUJDgmYL0=
X-Received: by 2002:ac8:525a:: with SMTP id y26mr7265901qtn.297.1559278051861; Thu, 30 May 2019 21:47:31 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoAkj_QqPUzZe+O1W3f=P=EqARE5GCu6kMeO76kBWUK27A@mail.gmail.com> <727F25EC-DD08-4A81-957C-072AC94FF6B9@gmail.com> <16ae05d913e.c75683dd278058.2765926039818296187@nerd.ninja> <23404.1558667773@localhost> <C287C63D-1770-4548-A1CC-0A6D570506AA@gmail.com>
In-Reply-To: <C287C63D-1770-4548-A1CC-0A6D570506AA@gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 30 May 2019 21:47:20 -0700
Message-ID: <CAOgPGoC6W370f=GpM76n1hfAoWe3aEtuKf4H6eW8kjagG-RjFA@mail.gmail.com>
To: Bret Jordan <jordan.ietf@gmail.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, cacao <cacao@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006375e3058a27b61e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/cacao/GFSquMa6HV4MBAsp5o9vUaLHqSM>
Subject: Re: [Cacao] Call for CACAO Charter Consensus
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: Fri, 31 May 2019 04:47:35 -0000

On Fri, May 24, 2019 at 8:53 AM Bret Jordan <jordan.ietf@gmail.com> wrote:

> Michael,
>
> Thank you for your comments. The text around an application level protocol
> is really about calling out which application level protocol to use for
> CACAO (MQTT, RabbitMQ, HTTP, etc) and how one would use it.  You can not
> just leave it wide open, nor could you say just use HTTP or MQTT for
> example.  The hope is we could call out one, and how you would use it with
> examples, then we could build some interoperability test suites to help
> ensure vendors do it right.  Give them a way to self-verify.  We have done
> this in other projects and it has worked pretty well.
>
>
[Joe] I think the question is more about what the protocol would do.  The
charter suggests protocols to do the following:

1. Retrieve playbooks from a source  (numbered item 3)
1.5 Way to discover playbooks (this is probably heavily reliant on another
protocol)
2. Submit a playbook to be executed and obtain success/failure and a list
of results (numbered item 5)
3. Submit a playbook for verification and obtain a result of valid/invalid
(combination of 2 and 4?)

It seems like 1 is basic.  1.5 seems fundamental as well, although its
possible this could be work for another WG or SDO.

I think we are having some discussion on whether 2 is in scope.   I'm not
sure if 3 is a thing or not.