Re: [EAT] Scope, Goals & Background for RATS

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 18 September 2018 18:08 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: eat@ietfa.amsl.com
Delivered-To: eat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A0B3130E8E; Tue, 18 Sep 2018 11:08:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 KNekR1oQ4Zdw; Tue, 18 Sep 2018 11:08:29 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 832C9130E70; Tue, 18 Sep 2018 11:08:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 0FE7020496; Tue, 18 Sep 2018 14:27:45 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 9F26CA0; Tue, 18 Sep 2018 14:08:26 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9C0D588; Tue, 18 Sep 2018 14:08:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
cc: "rats\@ietf.org" <rats@ietf.org>, "eat\@ietf.org" <eat@ietf.org>
In-Reply-To: <710df01c-c45f-9d26-b578-e4baa53c6de8@sit.fraunhofer.de>
References: <710df01c-c45f-9d26-b578-e4baa53c6de8@sit.fraunhofer.de>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
Date: Tue, 18 Sep 2018 14:08:26 -0400
Message-ID: <17674.1537294106@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/8vQ-M9IEthF-OP4-a2gjXsQlk9s>
Subject: Re: [EAT] Scope, Goals & Background for RATS
X-BeenThere: eat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: EAT - Entity Attestation Token <eat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eat>, <mailto:eat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eat/>
List-Post: <mailto:eat@ietf.org>
List-Help: <mailto:eat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eat>, <mailto:eat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Sep 2018 18:08:32 -0000

Henk Birkholz <henk.birkholz@sit.fraunhofer.de> wrote:
    > we pushed an initial document to the RATS github in order to focus the
    > discussion about remote attestation procedures a bit.

    >> https://github.com/ietf-rats/charter/blob/master/ietf-rats-charter.md

    > We included a background section to better highlight the meaning of the
    > term "attestation" in general. Hence, there is a trade-off between
    > clarity and conciseness, which is one of the things we would like to
    > get feedback about.

1) RATS is not expanded anywhere near the top of the document!
2) I think that this document is okay as a working document going towards a
   BOF,  but in general it is too big.
   Bulky things like the Terminology and most of the problem statement
   probably need to go into IDs.

I understand why you have put them here at this point.
As Mark Twain(%) was alleged to have said, "I didn't have time to write a
shorter letter"... thus the length of your document.
Statements like:

    (4) The lack of generic models and commonly understood terminology that
    would allow for semantic interoperability and a...

absolutely go into the charter to explain what the goals are.
This needs to be reworded into a positive action.... i.e. "We will develop
generic models with commonly understood terminology..."

    > Naturally, we are also very interested in feedback about the
    > illustrated difference between explicit attestation and implicit
    > attestation.



(%) apparently, he didn't say that first, and may never have said it.
But I think he would have liked to have said it.

--
Michael Richardson <mcr+IETF@sandelman.ca>ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-