Re: [EAT] [Rats] Rats and EAT

Diego Lopez <dr2lopez@icloud.com> Sun, 08 July 2018 19:47 UTC

Return-Path: <dr2lopez@icloud.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 478EE12872C; Sun, 8 Jul 2018 12:47:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.687
X-Spam-Level:
X-Spam-Status: No, score=-2.687 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=icloud.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 hXuzzl4TAO0i; Sun, 8 Jul 2018 12:47:02 -0700 (PDT)
Received: from pv35p12im-ztdg05041101.me.com (pv35p12im-ztdg05041101.me.com [17.133.186.214]) (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 82AC6127332; Sun, 8 Jul 2018 12:47:02 -0700 (PDT)
Received: from process-dkim-sign-daemon.pv35p12im-ztdg05041101.me.com by pv35p12im-ztdg05041101.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) id <0PBK00H00C50UZ00@pv35p12im-ztdg05041101.me.com>; Sun, 08 Jul 2018 19:47:01 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=icloud.com; s=04042017; t=1531079221; bh=LIZrLPxkORfLFD3gPHa7ErYC8alr5U7Hja9BD3Njev0=; h=To:From:Subject:Date:Message-id:Content-type:MIME-version; b=mR9GL15c7Yh9oYHdU2YO/DNfZ5gjQwVUjbxhBO2agEmu2EDpdguARc5tTEn+tlOM5 OzL0ENbwIfRb+r6nMpaV0iJKE4+qNMGZc4gkjPxsDRsGMzw2Gx4OPwVqL7UpLbpgF7 alpu/InwvpYhZR+hHgn7EDQiudR9WRy7ETj6EJ5B18SAfpKE3EluarY30C8VSueEG2 oO0xF9Gg6QqrYnGK0ifL9Mi1961Ms18Rsh7tsFH2yfK9s3sEWUx9TBdfuso3T8wAyy FwpZz/Anhuf8VvCmS5XGDC7sFzJs+f6LjJYilaoLvuCWDGTImWfcKUudM/LinnV24E gG70PBJUfgTtg==
Received: from localhost (pv38p12im-ztdg02103501.me.com [17.133.131.166]) by pv35p12im-ztdg05041101.me.com (Oracle Communications Messaging Server 8.0.1.2.20170607 64bit (built Jun 7 2017)) with ESMTP id <0PBK009QQCABMF00@pv35p12im-ztdg05041101.me.com>; Sun, 08 Jul 2018 19:47:00 +0000 (GMT)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:,, definitions=2018-07-08_12:,, signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 clxscore=1015 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1707230000 definitions=main-1807080239
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: Yaron Sheffer <yaronf.ietf@gmail.com>, "eat@ietf.org" <eat@ietf.org>, Laurence Lundblade <lgl@island-resort.com>, "rats@ietf.org" <rats@ietf.org>
From: Diego Lopez <dr2lopez@icloud.com>
Date: Sun, 08 Jul 2018 19:46:58 +0000
X-Mailer: iCloud MailClient1812Project34 MailServer1812B11.27417-16A-3271-df2820d40485
Message-id: <eb1d952b-1e73-4c41-bf12-82299b44ff3d@me.com>
Content-type: multipart/alternative; boundary="Apple-Webmail-42--9b0c6991-62df-48d4-afbc-af9ee6856b34"
MIME-version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/VOMoFwref8a4hwnFEw1P7fCXdNI>
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: Sun, 08 Jul 2018 19:47:06 -0000

Hi Hannes,

I was not deeply involved in the work, but NEA seemed to be focused on a particular use case (that of user devices attaching to a network) and not to the more general problem of mutual attestation in more P2P relationships, that I think are the most relevant right now. And it seems to me that at the moment NEA produced its work, user devices were not that much able of performing the procedures defined by the WG...

Anyway, I think there are several of these procedures that are applicable to P2P environments, once adequately adapted.

Be goode,

--
Eih bennek eih blavek!

Dr Diego R. Lopez
dr2lopez@icloud.com
https://es.linkedin.com/in/dr2lopez

On Jul 08, 2018, at 06:54 PM, Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:

Hi Diego,
 
what do you think are the lessons we can learn from NEA?
It clearly wasn’t as successful as hoped. I am sure there are reasons for that.
 
Ciao
Hannes
 
 
From: Diego Lopez [mailto:dr2lopez@icloud.com] 
Sent: 09 July 2018 01:45
To: Hannes Tschofenig
Cc: Yaron Sheffer; Laurence Lundblade; rats@ietf.org; eat@ietf.org
Subject: Re: [EAT] [Rats] Rats and EAT
 
And the use of NEA results is mentioned at least in one of the drafts on remote attestation referred in a previous message. Using NEA’s findings is certainly in our aim.
 
Be goode,

--
Likely to be brief and not very
elaborate as sent from my mobile
Diego R. Lopez

On 8 Jul 2018, at 15:39, Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:

Hi Yaron,
 
Eliot mentioned NEA on the mailing list. It would be interesting to hear what lessons can be learned from NEA.
 
Ciao
Hannes
 
From: EAT [mailto:eat-bounces@ietf.org] On Behalf Of Yaron Sheffer
Sent: 08 July 2018 06:51
To: Laurence Lundblade; rats@ietf.org; eat@ietf.org
Subject: Re: [EAT] [Rats] Rats and EAT
 
I'm a bit surprised that nobody's mentioning the work done by the IETF NEA working group. 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 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 does attestation of FIDO authenticators
- Android KeyStore 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
 
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
EAT mailing list
EAT@ietf.org
https://www.ietf.org/mailman/listinfo/eat
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
_______________________________________________
EAT mailing list
EAT@ietf.org
https://www.ietf.org/mailman/listinfo/eat