Re: [EAT] [Rats] BOF Preparation

"Shwetha Bhandari (shwethab)" <shwethab@cisco.com> Tue, 09 October 2018 02:00 UTC

Return-Path: <shwethab@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 8DB361310F4; Mon, 8 Oct 2018 19:00:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.49
X-Spam-Level:
X-Spam-Status: No, score=-14.49 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_FILL_THIS_FORM_SHORT=0.01, 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 IKa3ADXmORkA; Mon, 8 Oct 2018 19:00:46 -0700 (PDT)
Received: from rcdn-iport-1.cisco.com (rcdn-iport-1.cisco.com [173.37.86.72]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0BFF01310E2; Mon, 8 Oct 2018 19:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=43408; q=dns/txt; s=iport; t=1539050446; x=1540260046; h=from:to:cc:subject:date:message-id:mime-version; bh=Rrt0g+R0lnFGzcl4Iq2YxITlh+WMEcZX+Lugv/F23nE=; b=ds0wATwjxrOQXblgAxOnOimS+2n1DhTWlwMAaCJT6IItUuwpHYhFIgP8 kvAkqoGkPYJFdySZ2FrIod8svGFt8dNv6qJpQE55Pa00rsWqAWo1QcFF1 S56gHYEj4clMByzYy9IY4QB7uskSdokIxhogfY3S4Rb2AJU4WU0tEk4fh A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADAABEC7xb/5xdJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ5NKmZ/KAqDa4gVjC+BaCWWaRSBZgs?= =?us-ascii?q?BASCBV4J1AheEJiE0DQ0BAwEBAgEBAm0cDIU5AQEDAiMKQQIJEgEGAhEDAQE?= =?us-ascii?q?BIQEGAwIEJwkUCQoEAQ0FH4MCAYEdZA+IZJtNgS4fhAwBBweFVAWKHIEdF4F?= =?us-ascii?q?BPyZsJwwTgkyDGwEBAYEkCQESARwKBwkIAQcFCgKCSTGCJgKIPRyFN49fCQK?= =?us-ascii?q?McVGDBheBTiKEQ4MOhjiHNI4ZAhEUgSUdOCc9cXAVOyoBgkGDOAECgkiKUm8?= =?us-ascii?q?BihGBH4EfAQE?=
X-IronPort-AV: E=Sophos;i="5.54,358,1534809600"; d="scan'208,217";a="463577720"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2018 02:00:44 +0000
Received: from XCH-ALN-011.cisco.com (xch-aln-011.cisco.com [173.36.7.21]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id w9920imd006812 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 9 Oct 2018 02:00:44 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-ALN-011.cisco.com (173.36.7.21) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 8 Oct 2018 21:00:43 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1395.000; Mon, 8 Oct 2018 21:00:43 -0500
From: "Shwetha Bhandari (shwethab)" <shwethab@cisco.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "Diego R. Lopez" <diego.r.lopez@telefonica.com>, "eat@ietf.org" <eat@ietf.org>, "rats@ietf.org" <rats@ietf.org>
CC: "'Benjamin Kaduk'" <kaduk@mit.edu>, "Eric Voit (evoit)" <evoit@cisco.com>
Thread-Topic: [Rats] [EAT] BOF Preparation
Thread-Index: AQHUX3PiyQmT6CocLke6OfpTrN0yTA==
Date: Tue, 9 Oct 2018 02:00:43 +0000
Message-ID: <1AE74D0A-DB9A-4847-A3C9-F25A29CA1C5B@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.1a.0.160910
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.61.60]
Content-Type: multipart/alternative; boundary="_000_1AE74D0ADB9A4847A3C9F25A29CA1C5Bciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.21, xch-aln-011.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/eat/csw39_4iDiUVpm2I1ZM-P1m9PeY>
Subject: Re: [EAT] [Rats] BOF Preparation
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, 09 Oct 2018 02:00:51 -0000

Hi Hannes, All,

A number of networking vendors have expressed interest in contributing to and implementing the models on the network devices to provide challenge-response as well as unidirectional attestation.  “draft-birkholz-yang-basic-remote-attestation” shows some of this support.

Also commercial implementations of applications exposing the boot integrity of devices exist.  E.g., see:
https://www.cisco.com/c/dam/en/us/td/docs/cloud-systems-management/application-policy-infrastructure-controller-enterprise-module/1-5-x/integrity_verification/release-notes_ver_275/Cisco_IV_App_RN_1_5_0_275.pdf

A standard data model and any protocol extension(s) for interoperability that fits in the existing network operations will be of key value in exposing proof of network device integrity. At Cisco, we are geared up to progress this work.


Thanks,
Shwetha
From: RATS <rats-bounces@ietf.org> on behalf of Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Date: Tuesday, October 9, 2018 at 1:13 AM
To: "Diego R. Lopez" <diego.r.lopez@telefonica.com>om>, "eat@ietf.org" <eat@ietf.org>rg>, "rats@ietf.org" <rats@ietf.org>
Cc: 'Benjamin Kaduk' <kaduk@mit.edu>
Subject: Re: [Rats] [EAT] BOF Preparation

Thanks, Diego. That’s useful input on the scenarios you are looking into.


From: Diego R. Lopez <diego.r.lopez@telefonica.com>
Sent: Sunday, October 7, 2018 6:53 PM
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>om>; eat@ietf.org; rats@ietf.org
Cc: 'Benjamin Kaduk' <kaduk@mit.edu>
Subject: Re: [EAT] BOF Preparation

Hi Hannes,

We are interested in using the base technology (whatever is supported in low level software or operating systems) to support attestation of NFV deployments, especially those related with the collaboration of third parties: with universal EPC, and edge computing as the main use cases. And, while is true we are not developing the base software, we are collaborating with academic teams working at the hypervisor and container platform level.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
https://www.linkedin.com/in/dr2lopez/

e-mail: diego.r.lopez@telefonica.com<mailto:diego.r.lopez@telefonica.com>
Tel:         +34 913 129 041
Mobile:  +34 682 051 091
----------------------------------

On 06/10/2018, 11:08, "Hannes Tschofenig" <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>> wrote:

Hi Diego,

I guess Telefonica is a user of the technology*. How would leverage the results?

Ciao
Hannes

*: You are not manufacturing chips, developing operating systems, or writing low level software (like firmware) that integrates the discussed attestation technology. Is that correct?

From: Diego R. Lopez <diego.r.lopez@telefonica.com<mailto:diego.r.lopez@telefonica.com>>
Sent: Saturday, October 6, 2018 12:27 AM
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>>; eat@ietf.org<mailto:eat@ietf.org>; rats@ietf.org<mailto:rats@ietf.org>
Cc: 'Benjamin Kaduk' <kaduk@mit.edu<mailto:kaduk@mit.edu>>
Subject: Re: [EAT] BOF Preparation

Hi,

We are interested in fostering attestation technologies able to support and leverage network virtualization techniques (yes, NFV strikes back…), and are in contact with other companies that share the same interest.

I won’t make it to Bangkok, but will be happy to help in anything I can through remote participation.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
https://www.linkedin.com/in/dr2lopez/

e-mail: diego.r.lopez@telefonica.com<mailto:diego.r.lopez@telefonica.com>
Tel:         +34 913 129 041
Mobile:  +34 682 051 091
----------------------------------

On 05/10/2018, 14:30, "EAT on behalf of Hannes Tschofenig" <eat-bounces@ietf.org<mailto:eat-bounces@ietf.org> on behalf of Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>> wrote:

Hi Ben, Hi BOF chairs, Hi all,

I have been thinking about how to turn this BoF into a success. I see a few challenges:

There are different items in scope of the work and we (Arm) are interested in contributing to those that relate to the EAT/attestation token work. We are happy to give a presentation about those but I haven’t seen any agenda for the BoF yet. Who is in charge of preparing an agenda? I have seen BoFs fail where the presentations weren’t well aligned or not clearly demonstrating a real-world problem.

At the BoF we will have to demonstrate that there are companies involved who are actually willing to do the heavy lifting to turn this effort into a success. Since there are very different items listed on the proposed charter text I am curious whether there is reasonable support for all of them. I can only speak for our interest in the EAT items and we are working with companies to state their support on the mailing list. But the BoF is likely going to fail if there is only support for a subset of the items. Where are we with the rest and who is reaching out to which part of the industry?

Ciao
Hannes

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.

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
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.

________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição
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.