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

"Eric Voit (evoit)" <evoit@cisco.com> Tue, 23 October 2018 23:20 UTC

Return-Path: <evoit@cisco.com>
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 E3B05130EAE; Tue, 23 Oct 2018 16:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 pNMy204CalM5; Tue, 23 Oct 2018 16:20:24 -0700 (PDT)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C35DF130F35; Tue, 23 Oct 2018 16:20:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1882; q=dns/txt; s=iport; t=1540336823; x=1541546423; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=FM4BUUrgmnlpaUBbokbVHLmHiJffIcWgr4bVv76KNZo=; b=Ad6aNqL/cPQOuuD1Kzk2/1fpNtAgUfoQgzQg7u0lSFn7fs/CzqDTAkZ5 ZiT5EwkfsKcabNrRQcfReOT8QZdkQDvWcU25CLQtvyTKgPFQVs5O/tzfP F7IFIDerCoQdC7RY74R7FKytIf4WyDNQtgW5ttfCDUTQtudM+A+8V+eSR k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AeAABOq89b/5pdJa1jGgEBAQEBAgEBAQEHAgEBAQGBVAIBAQEBCwGBWipmfygKg2uUNYINgz+VUAsBAR+BWIJ1AheCciE3Cg0BAwEBAgEBAm0cDIU6AQEBAwEjEUUFCwIBCA4HAwICJgICAjAVEAIEDgUIgk5MgXkIqA6BLoojgQuKSA8XgUE/gRGDEogBglcCnlIJApBsH4FShHSJbZZHAhEUgSYzIoFVcBWDJwmFKIsmb4sNgR8BAQ
X-IronPort-AV: E=Sophos;i="5.54,418,1534809600"; d="scan'208";a="190158543"
Received: from rcdn-core-3.cisco.com ([173.37.93.154]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Oct 2018 23:20:23 +0000
Received: from XCH-RTP-015.cisco.com (xch-rtp-015.cisco.com [64.101.220.155]) by rcdn-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id w9NNKM3T022534 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 23 Oct 2018 23:20:22 GMT
Received: from xch-rtp-013.cisco.com (64.101.220.153) by XCH-RTP-015.cisco.com (64.101.220.155) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 23 Oct 2018 19:20:22 -0400
Received: from xch-rtp-013.cisco.com ([64.101.220.153]) by XCH-RTP-013.cisco.com ([64.101.220.153]) with mapi id 15.00.1395.000; Tue, 23 Oct 2018 19:20:22 -0400
From: "Eric Voit (evoit)" <evoit@cisco.com>
To: Michael Richardson <mcr@sandelman.ca>
CC: Jeremy O'Donoghue <jodonogh@qti.qualcomm.com>, "rats@ietf.org" <rats@ietf.org>, "eat@ietf.org" <eat@ietf.org>
Thread-Topic: [EAT] [Rats] Attestation BoF charter updates?
Thread-Index: AQHUayYIxGIfFCDBbEOrnnilU7+Cm6UtdkFA
Date: Tue, 23 Oct 2018 23:20:22 +0000
Message-ID: <892ee6bc1728439fa3f5d70164b4a69c@XCH-RTP-013.cisco.com>
References: <5D773C02-5083-4B10-A705-782E28FD8ADB@island-resort.com> <f84515dd-2e1a-7e66-7c23-b16f8f425d2a@sit.fraunhofer.de> <3347AA26-3FA1-4067-8378-51B533BA77FB@island-resort.com> <570FEF0C-FD3A-4EBF-B8E6-7B13D2FD8E22@qti.qualcomm.com> <7544.1540242117@localhost> <46150D67-97E7-457F-9C8B-D2B3060978CA@qti.qualcomm.com> <f6602afcf1b0440d98f5ded158bfe572@XCH-RTP-013.cisco.com> <10963.1540336415@localhost>
In-Reply-To: <10963.1540336415@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.56.234]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.155, xch-rtp-015.cisco.com
X-Outbound-Node: rcdn-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/x9lIQj2q0owEx4UEgprytMlYAHE>
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: Tue, 23 Oct 2018 23:20:44 -0000

> From: Michael Richardson, October 23, 2018 7:14 PM
> 
> Eric Voit (evoit) <evoit@cisco.com> wrote:
>     > Could you talk about how these elements are covered (or not)? For
>     > context, I am working from the perspective of remote attestation
>     > application developer trying to standardize the interfaces between a
>     > controller (which is acting as a claim verifier) and a network element
>     > (which includes TCG based subsystems.)
> 
> These are good questions, but are they questions that the *CHARTER* of the
> *WORKING GROUP* needs to answer?  Sure the *WORKING GROUP* needs to
> answer them, but please remember that the charter is META.

If the WG needs to answer them, that is great.  My concern was that I didn't see these types of questions falling under the charter text proposed by Jeremy.  Maybe it is there, but I didn't see it.  Hence my question.

Eric
 
>     > · How do we know which root of trust which was used to generate the
>     > attestation evidence (e.g., application event logs), and how does a
> 
> Good question... put it in the Internet Draft.
> 
> --
> ]               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    [