Re: [EAT] Organizing IETF attestation work

Carl Wallace <carl@redhoundsoftware.com> Tue, 04 September 2018 10:43 UTC

Return-Path: <carl@redhoundsoftware.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 540F3130E10 for <eat@ietfa.amsl.com>; Tue, 4 Sep 2018 03:43:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhoundsoftware.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 W5hBPGzJhV5V for <eat@ietfa.amsl.com>; Tue, 4 Sep 2018 03:43:45 -0700 (PDT)
Received: from mail-qt0-x231.google.com (mail-qt0-x231.google.com [IPv6:2607:f8b0:400d:c0d::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EE06130EA0 for <eat@ietf.org>; Tue, 4 Sep 2018 03:43:45 -0700 (PDT)
Received: by mail-qt0-x231.google.com with SMTP id r37-v6so3377977qtc.0 for <eat@ietf.org>; Tue, 04 Sep 2018 03:43:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhoundsoftware.com; s=google; h=user-agent:date:subject:from:to:message-id:thread-topic:references :in-reply-to:mime-version; bh=fRC3edYxwOmTRVj49WITC8CCYyoSBgKbRgFIJLr3oTo=; b=M7lI1DZfKVRiBE/pYnj/AW6fGVxbeiZP/DSZd35Zd2QuNv9TL8i8hhaL7Ga43ll6Rh vsAbbFSKt2A6dzQnUzjO3XyMMjtWZg6UPEDyhu7ONPHqC9A5RZWBpzkXQWXGUuqmeMQM mtOMioVZUm+1FI71CZBBlOJTPQO3i1U+Dc7sM=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:user-agent:date:subject:from:to:message-id :thread-topic:references:in-reply-to:mime-version; bh=fRC3edYxwOmTRVj49WITC8CCYyoSBgKbRgFIJLr3oTo=; b=OoHLHY/l1QcbgzDTSdsflMW/VbkZs7St0zFvNblJCDiO10XEcEisH+QNVMfI21RUO9 Lw2HiYS5i2eoSpRWj+gDRNMYWzFq9xNHS+vg86hzqZu1DM2Gm1OnvQsD30T40s5dEH7+ QrXAOrJNpdjdl+7obqAAfPldjJ10E7j+hg3tyHaVqb6ht9bGbUh84BcOAO8G3OWOQJCV O0EZL8cnhNqx4fYqZQlXGUuJxLBu1YNuVQXV6TunQiXPXh+8c0drHH2JWgezSN1USM5G EaYc21GyilY+cfnKEvKtoaJ7NPlSb3C6t0d76tRMk3bLxZ/0QcRSAtSpwE5CMseU3qV2 zLMg==
X-Gm-Message-State: APzg51DvJDGazay9MJuSDh7tRMW8G/epry3uMA7+ajowNxfnlDfXQBvT QN87kqjnEdDNefnge9ZS4ILFrHBTDMzsOg==
X-Google-Smtp-Source: ANB0VdY7x9/eYcUa8SebFRSQ2D1gVrbXppZJwLQ9sH94UaIiAbiT++FIVC2m4PH7iW/uVsfD05aRTw==
X-Received: by 2002:a0c:d5d3:: with SMTP id h19-v6mr28816901qvi.218.1536057824473; Tue, 04 Sep 2018 03:43:44 -0700 (PDT)
Received: from [192.168.2.27] (pool-108-28-91-61.washdc.fios.verizon.net. [108.28.91.61]) by smtp.googlemail.com with ESMTPSA id l23-v6sm13334212qta.30.2018.09.04.03.43.42 (version=TLS1 cipher=AES128-SHA bits=128/128); Tue, 04 Sep 2018 03:43:43 -0700 (PDT)
User-Agent: Microsoft-MacOutlook/14.7.6.170621
Date: Tue, 04 Sep 2018 06:43:46 -0400
From: Carl Wallace <carl@redhoundsoftware.com>
To: Laurence Lundblade <lgl@island-resort.com>, eat@ietf.org, rats@ietf.org
Message-ID: <D7B3D823.C023B%carl@redhoundsoftware.com>
Thread-Topic: [EAT] Organizing IETF attestation work
References: <F6917D3A-901F-474B-8E4C-A7F23C626045@island-resort.com>
In-Reply-To: <F6917D3A-901F-474B-8E4C-A7F23C626045@island-resort.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3618888230_6545064"
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/cnJnPmaN0eTI2Pju0FcNZtI0-mc>
Subject: Re: [EAT] Organizing IETF attestation work
X-BeenThere: eat@ietf.org
X-Mailman-Version: 2.1.27
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, 04 Sep 2018 10:43:49 -0000

I'd explicitly call out key attestation in the in-scope list. It's implied
by the references to TCG and the Attested TLS Token Binding but seems
important enough to call out:
-Key attestation schemes like Android P attestation, Yubikey attestation,
TPM/TCG key attestations.

The deliverables list would likely benefit from a document that describes
attestation verification in detail, including establishment of trust,
revocation of trust, etc.

From:  EAT <eat-bounces@ietf.org> on behalf of Laurence Lundblade
<lgl@island-resort.com>
Date:  Sunday, September 2, 2018 at 3:02 PM
To:  <eat@ietf.org>, <rats@ietf.org>
Subject:  [EAT] Organizing IETF attestation work

> Hi folks, here is a straw man proposal for organizing the IETF attestation
> work.
> 
> I proposed we combine eat and rats and call this the Remote Attestation or RA
> working group. 
> 
> Example in-scope use cases include:
> * TPM/TCG based attestations that are sent to remote entities, relying parties
> and such (non-local attestations)
> * Attestations used by protocols like FIDO that provide secured claims about a
> particular subsystem on a device to relying parties
> * Platform/system attestation schemes like Android O attestation
> * Reporting of device/system security characteristics by subsystems like TEEs
> and secure elements
> * Securing of risk signals (e.g., SW version, geographic location, device
> types) sent to relying parties
> * For IoT device on-boarding, proof of device provenance
> The documents produced would probably be:
> * An overall model and terminology document (we have a start with the RATS
> <https://tools.ietf.org/html/draft-birkholz-attestation-terminology-02>
> document)
> * A claims definition document (we have a start with the EAT
> <https://tools.ietf.org/html/draft-mandyam-eat-00>  document)
> * A protocol definition for transmitting attestations when they are not being
> carried in other protocols as extensions or such (not started)
> * Possibly the token binding attestation work (Giri has completed a lot of
> work on this <https://tools.ietf.org/html/draft-mandyam-tokbind-attest-04> )
> 
> We get to reference Ra, the Egyptian sun god and use hieroglyphics.
> 
> LL
> <snip>
> _______________________________________________ EAT mailing list EAT@ietf.org
> https://www.ietf.org/mailman/listinfo/eat