Re: [Rats] What's to EAT?

Laurence Lundblade <lgl@island-resort.com> Tue, 12 November 2019 18:58 UTC

Return-Path: <lgl@island-resort.com>
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 394A3120B1C for <rats@ietfa.amsl.com>; Tue, 12 Nov 2019 10:58:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level:
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 Ea5WT0zPeS9b for <rats@ietfa.amsl.com>; Tue, 12 Nov 2019 10:58:04 -0800 (PST)
Received: from p3plsmtpa09-01.prod.phx3.secureserver.net (p3plsmtpa09-01.prod.phx3.secureserver.net [173.201.193.230]) (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 1EF80120B0E for <rats@ietf.org>; Tue, 12 Nov 2019 10:58:04 -0800 (PST)
Received: from [10.141.0.10] ([45.56.150.139]) by :SMTPAUTH: with ESMTPA id UbMZimmZrnaIyUbMZiAtpV; Tue, 12 Nov 2019 11:58:03 -0700
From: Laurence Lundblade <lgl@island-resort.com>
Message-Id: <9AD0AC18-E959-428D-A6C0-D3E8E66A9AB7@island-resort.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_5CBA44E9-F41F-47F9-84A6-5DA34B180FE4"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Date: Tue, 12 Nov 2019 10:58:02 -0800
In-Reply-To: <01bbbb92-9b99-7636-50a4-a1b4a37e0903@sandelman.ca>
Cc: "rats@ietf.org" <rats@ietf.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <01bbbb92-9b99-7636-50a4-a1b4a37e0903@sandelman.ca>
X-Mailer: Apple Mail (2.3445.104.11)
X-CMAE-Envelope: MS4wfLmQWr75SXpZR5SQxcPQwT0HspnoEfpap7Sz2cJCiTM5tPxzqdvURW+O30uSVEpeRc67SxmmTbCVY/SKEVX1MBpQnhCv9L03hObUiIqpaVF08F8kbJ8u JmNddINMK11ZkhJ5EGKl3OPcvYjaTYnfCxRXA0C7QQbZTPfCsCFxkXKeUr3lI469zioU5IVHx6yjXohyOo7PXV4ZMsgK7u/qQ1c=
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/BKz1YvQIb29Xm8qtpB0PK5Y_Opw>
Subject: Re: [Rats] What's to EAT?
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: Tue, 12 Nov 2019 18:58:05 -0000

> On Nov 12, 2019, at 1:08 AM, Michael Richardson <mcr+ietf@sandelman.ca>; wrote:
> 
> 
> On 2019-11-12 12:19 p.m., Dave Thaler wrote:
>> 
>> Ned Smith wrote:
>> 
>>> So far the group has used the term "EAT" to refer to both the
>> information model and data serialization expressions.
>> 
>>  
>> 
>> I would rather see the term EAT (and any other terms ending in Token,
>> like JWT and CWT) only be used to refer to
>> 
>> data serialization expressions, not the information model.
>> 
> I concur.

I disagree with that.

I don’t think we want one information model for all of RATS. 

EAT has an information model and data model for what it expresses. 

The YANG Module has an information and data model for what it expresses.

The primary purpose for use of information models (plural!) is so we can described things like claims once and then have a largely mechanical way to serialize them in different ways, CBOR and JSON.

Note that CWT and JWT don’t use the information model concept. They are mostly two independently defined and loosely coordinated data models. We are trying to do different by having a common information model that covers both. One might argue that CWT and JWT should have done what we are doing in EAT.

LL