Re: [Rats] Call for agenda

Michael Richardson <mcr+ietf@sandelman.ca> Sat, 20 July 2019 00:16 UTC

Return-Path: <mcr@sandelman.ca>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B52F120041 for <rats@ietfa.amsl.com>; Fri, 19 Jul 2019 17:16:36 -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 LH2ox8OAfO_g for <rats@ietfa.amsl.com>; Fri, 19 Jul 2019 17:16:34 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [176.58.120.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EB84120033 for <rats@ietf.org>; Fri, 19 Jul 2019 17:16:33 -0700 (PDT)
Received: from dooku.sandelman.ca (ipv6.dooku.sandelman.ca [IPv6:2607:f0b0:f:6::1]) by relay.sandelman.ca (Postfix) with ESMTPS id B46931F44C for <rats@ietf.org>; Sat, 20 Jul 2019 00:16:31 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 3C6471B0D; Fri, 19 Jul 2019 20:16:36 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "rats@ietf.org" <rats@ietf.org>
In-reply-to: <099BB73F-1846-4D9D-A7B2-612F46D97899@island-resort.com>
References: <FDD59063-7A68-400F-BA41-87D5A854CF0C@cisco.com> <ef3fc36a-3fa7-01f7-17b9-6f7c771fbf27@sit.fraunhofer.de> <DBCDA177-56CE-45EA-91E4-BCD789610FDE@cisco.com> <099BB73F-1846-4D9D-A7B2-612F46D97899@island-resort.com>
Comments: In-reply-to Laurence Lundblade <lgl@island-resort.com> message dated "Thu, 18 Jul 2019 20:43:49 -0700."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 19 Jul 2019 20:16:36 -0400
Message-ID: <15662.1563581796@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/e_IJKSO0-rDgVJoneq0_QeiMvoI>
Subject: Re: [Rats] Call for agenda
X-BeenThere: rats@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Remote Attestation Procedures <rats.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rats>, <mailto:rats-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats/>
List-Post: <mailto:rats@ietf.org>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rats>, <mailto:rats-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Jul 2019 00:16:36 -0000

Laurence Lundblade <lgl@island-resort.com> wrote:
    > Another thing that I’m not sure there is consensus on is how EAT, CWT
    > and JWT relate. Personally I’m content with what I’ve written in the
    > latest EAT draft — an EAT is either a CWT or a JWT. The new EAT
    > attestation-related claims are described in CDDL for both CBOR and
    > JSON. If there isn’t consensus on this, then time to discuss it seems
    > important.

I mostly agree with this.

I'm not actually sure if the CDDL as it is being used is providing very much
benefit, but it doesn't seem to cost that much (in brain power to read or
write), so I'm pretty much okay with it.

For instance, 3.7.x have their CDDL in 3.7.6, I guess?
I think it belongs in the 3.7(.0) section.

The other pattern is to use YANG.  Having done this with RFC8366, I'm not
convinced it's a better choice; CDDL was not mature enough when we started,
and we had great YANG-fu.

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