IETF Logo Mail Archive

Re: [Rats] What's to EAT? - terminology clarification

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 18 November 2019 04:30 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 19134120848 for <rats@ietfa.amsl.com>; Sun, 17 Nov 2019 20:30:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-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 Z9u4DnEKfmXC for <rats@ietfa.amsl.com>; Sun, 17 Nov 2019 20:30:12 -0800 (PST)
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 28F64120096 for <rats@ietf.org>; Sun, 17 Nov 2019 20:30:12 -0800 (PST)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:1ca0:aaff:fe40:7c9]) by relay.sandelman.ca (Postfix) with ESMTPS id 3C9C91F450 for <rats@ietf.org>; Mon, 18 Nov 2019 04:30:10 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 8D55910EF; Mon, 18 Nov 2019 12:30:08 +0800 (+08)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "rats@ietf.org" <rats@ietf.org>
In-reply-to: <20191114141138.dipzizem6a6wh6cr@anna.jacobs.jacobs-university.de>
References: <229E0A72-4B44-4C9A-AD0A-142A13020C9A@intel.com> <MWHPR21MB0784058F591C52EEB31E0736A3770@MWHPR21MB0784.namprd21.prod.outlook.com> <4F586E15-9CF7-4824-87F2-8E2C20D1AF1D@intel.com> <MWHPR21MB078439E9EB07E3BB72E15137A3760@MWHPR21MB0784.namprd21.prod.outlook.com> <71173EC8-A167-47B9-B0F1-05759D59890B@akamai.com> <20191113071244.onqdgo2roqt7efb6@anna.jacobs.jacobs-university.de> <B555FC8E-FF3B-468A-B3DF-9F10DD6FBBF6@island-resort.com> <20191114141138.dipzizem6a6wh6cr@anna.jacobs.jacobs-university.de>
Comments: In-reply-to =?iso-8859-1?Q?Sch=F6nw=E4lder=2C_J=FCrgen?= <J.Schoenwaelder@jacobs-university.de> message dated "Thu, 14 Nov 2019 14:11:39 +0000."
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: Mon, 18 Nov 2019 12:30:08 +0800
Message-ID: <24439.1574051408@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/do60LWyylvg_JOST7JFtRz05jsI>
Subject: Re: [Rats] What's to EAT? - terminology clarification
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: Mon, 18 Nov 2019 04:30:14 -0000

If we are going to use JWT/CWT for the security of EATs, then I am skeptical
that CDDL (or any other Data Modeling language) brings anything to the table.

What we need are clear semantic descriptions of claims.
Often we will need some anciliary data associated with the claim, and
sometimes that data will be more complex than a single binary blob.  In those
cases, a bit of CDDL will benefit us.

I don't think that a YANG model will help us at all for this.

-- 
]               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    [

v2.23.0 | Report a Bug | By Email