Re: [EAT] [Rats] Attestation BoF charter updates?

Carsten Bormann <cabo@tzi.org> Thu, 11 October 2018 20:43 UTC

Return-Path: <cabo@tzi.org>
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 96584124C04; Thu, 11 Oct 2018 13:43:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 0H6pXo1oeKxB; Thu, 11 Oct 2018 13:43:22 -0700 (PDT)
Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 F31071277CC; Thu, 11 Oct 2018 13:43:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de
Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w9BKhDxc028365; Thu, 11 Oct 2018 22:43:18 +0200 (CEST)
Received: from client-0223.vpn.uni-bremen.de (client-0223.vpn.uni-bremen.de [134.102.107.223]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 42WNG93yn1z1Bq8; Thu, 11 Oct 2018 22:43:13 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <28763.1539288472@dooku.sandelman.ca>
Date: Thu, 11 Oct 2018 22:43:12 +0200
Cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>, "rats@ietf.org" <rats@ietf.org>, Laurence Lundblade <lgl@island-resort.com>, "eat@ietf.org" <eat@ietf.org>
X-Mao-Original-Outgoing-Id: 560983390.9626679-0aec4371ce3ad6f1ae9edc0d916b4b68
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F260DEF-6A53-40A7-AFA5-EF7C18AA46C6@tzi.org>
References: <5D773C02-5083-4B10-A705-782E28FD8ADB@island-resort.com> <f84515dd-2e1a-7e66-7c23-b16f8f425d2a@sit.fraunhofer.de> <28763.1539288472@dooku.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/mrbyLo4E54OZkXYNbfX5JhEGXLU>
Subject: Re: [EAT] [Rats] Attestation BoF charter updates?
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: Thu, 11 Oct 2018 20:43:24 -0000

On Oct 11, 2018, at 22:07, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
> 
> re: "Information Elements (IE)"
> 
> If you have some wiggle room (i.e. you aren't trying to align with some other
> pre-existing standards work elsehwere), it might be worth using another term,
> as I think that this term is used for layer-2 extensions in 802.15.4
> networks.

I prefer “data item” (about half the number of syllables), but maybe this is too much of a CBOR term.

>> Deliverables
>> Attestation information flows, consolidated terminology and corresponding
>> taxonomies (overview/architecture to be developed in parallel with solution
>> documents; can be separate document or go into 2, 3, 4 below)
> 
> In a break from the waterfall method of requirements, use-cases and then
> protocols (or rather, in this case, artifact formats), I suggest that that
> each be worked on in parallel,

Absolutely!  (This may now be so obvious to the charter authors that they neglected to state it.)

> and that the terminology and architecture
> documents be constrained to be published *LAST*.

Well, at the same time, because the other documents will want to use the terms.

> But, the WG should issue WG
> Consensus Calls on the documents at intervals such that the text is in them
> can be considered authoritative enough to answer questions in the protocol.

The charter doesn’t go into a lot of details of how the WG should work — that is normally not part of the IESG-WG contract (which we call charter).  But doing this in a sequence of milestones may be a good suggestion.

> Note that I cut out a bunch of text from the Introduction. It didn't help me
> understand the purpose of the group.  Also I note that IE is never used again
> after the first paragraph, so I think you could just call them artifacts.

Works for me, too.

Grüße, Carsten