Re: [EAT] [Rats] Rats and EAT

Henk Birkholz <henk.birkholz@sit.fraunhofer.de> Mon, 09 July 2018 09:53 UTC

Return-Path: <henk.birkholz@sit.fraunhofer.de>
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 8F375130F4D; Mon, 9 Jul 2018 02:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 Ckl6FEJmdkPT; Mon, 9 Jul 2018 02:53:40 -0700 (PDT)
Received: from mailext.sit.fraunhofer.de (mailext.sit.fraunhofer.de [141.12.72.89]) (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 5E131130E33; Mon, 9 Jul 2018 02:53:39 -0700 (PDT)
Received: from mail.sit.fraunhofer.de (mail.sit.fraunhofer.de [141.12.84.171]) by mailext.sit.fraunhofer.de (8.14.4/8.14.4/Debian-4.1ubuntu1) with ESMTP id w699rY3l012529 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 9 Jul 2018 11:53:35 +0200
Received: from [134.102.163.216] (134.102.163.216) by mail.sit.fraunhofer.de (141.12.84.171) with Microsoft SMTP Server (TLS) id 14.3.399.0; Mon, 9 Jul 2018 11:53:28 +0200
To: Yaron Sheffer <yaronf.ietf@gmail.com>, Laurence Lundblade <lgl@island-resort.com>, rats@ietf.org, eat@ietf.org
References: <0236DCF5-8B9D-4721-B169-8DCBC6B4CFBC@island-resort.com> <f81f30bd-28c4-f915-18d7-028f0e3cb2da@gmail.com>
From: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Message-ID: <e8cad7be-49fb-f95d-fad5-4e0830060caf@sit.fraunhofer.de>
Date: Mon, 09 Jul 2018 11:47:46 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <f81f30bd-28c4-f915-18d7-028f0e3cb2da@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [134.102.163.216]
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/rSDy2zkaRKING7ZEVXVMV7QLf0s>
Subject: Re: [EAT] [Rats] Rats and EAT
X-BeenThere: eat@ietf.org
X-Mailman-Version: 2.1.26
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: Mon, 09 Jul 2018 09:53:44 -0000

Hello Yaron,

the TNC architecture was revised and update to 2.0 last year. You can 
find the current detailed architecture diagram in this document on page 
20 (Figure 5).

> https://trustedcomputinggroup.org/wp-content/uploads/TCG-TNC-Architecture-for-Interoperability-Version-2.0-Raevision-13-.pdf

There is also this freshly minted RFC that makes use of the architecture 
(RFC 5792, called IF-M in TCG lingo):

> https://datatracker.ietf.org/doc/rfc8412/


Viele Grüße,

Henk

On 07/07/2018 11:51 PM, Yaron Sheffer wrote:
> I'm a bit surprised that nobody's mentioning the work done by the IETF 
> NEA working group <https://datatracker.ietf.org/wg/nea/about/>. Yes, 
> it's been some time ago, but the people involved were (to the best of my 
> knowledge) involved with the TCG community.
> 
> NEA was about desktop machines and NAC rather than mobile devices, but 
> hey, by now we should be looking for solutions that encompass both 
> technologies!
> 
> See this diagram 
> <https://wiki.strongswan.org/projects/1/wiki/trustednetworkconnect> on 
> how the complex NEA/TNC architecture fits together, including the TPM.
> 
> Thanks,
> 
>      Yaron
> 
> 
> On 06/07/18 22:20, Laurence Lundblade wrote:
>> Hey EAT and Rats folks, just became aware of IETF attestation work 
>> running in parallel. Seems like EAT is focused more on an independent 
>> signed, self-secured data structure with a lot of clams. Rats, seems 
>> more TPM and full protocol centric, but I’m still reading.
>>
>> Here’s a list of attestation work that Diego and Henk made:
>> https://datatracker.ietf.org/doc/draft-pastor-i2nsf-nsf-remote-attestation/
>> https://datatracker.ietf.org/doc/draft-birkholz-i2nsf-tuda/
>> https://datatracker.ietf.org/doc/draft-mandyam-eat/
>> https://datatracker.ietf.org/doc/draft-mandyam-tokbind-attest/
>> https://datatracker.ietf.org/doc/draft-birkholz-reference-ra-interaction-model/
>> https://datatracker.ietf.org/doc/draft-birkholz-yang-basic-remote-attestation/
>> https://datatracker.ietf.org/doc/draft-birkholz-attestation-terminology/
>>
>> A couple of other interesting non-TPM “attestation" technologies:
>> - FIDO 
>> <https://www.w3.org/Submission/2015/SUBM-fido-key-attestation-20151120/> does 
>> attestation of FIDO authenticators
>> - Android KeyStore 
>> <https://developer.android.com/training/articles/security-key-attestation> uses 
>> the term to mean proving the provenance of a stored key
>> - IEEE 802.1AR is kind of an attestation too
>>
>> FYI, the IETF attestation events I know of so far are:
>>  - I’ll present EAT at HotRFC Sunday around 18:00
>>  - Secdispatch discussion of EAT (and Rats?) Monday at 15:30 (At least 
>> I hope; no confirmation yet)
>>  - EAT BarBof Monday at 18:00
>>  - Rats BarBof Thursday after dinner
>>
>> I will attend them all :-)
>>
>> LL
> 
> 
> 
> _______________________________________________
> Rats mailing list
> Rats@ietf.org
> https://www.ietf.org/mailman/listinfo/rats
>