Re: [Teep] Tutorial and Hackathon

<Faibish.Sorin@dell.com> Wed, 14 August 2019 14:05 UTC

Return-Path: <Faibish.Sorin@dell.com>
X-Original-To: teep@ietfa.amsl.com
Delivered-To: teep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C9F91200F8; Wed, 14 Aug 2019 07:05:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dell.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 4OFCSe6lrbcT; Wed, 14 Aug 2019 07:05:51 -0700 (PDT)
Received: from mx0a-00154904.pphosted.com (mx0a-00154904.pphosted.com [148.163.133.20]) (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 A492D12081F; Wed, 14 Aug 2019 07:05:51 -0700 (PDT)
Received: from pps.filterd (m0170389.ppops.net [127.0.0.1]) by mx0a-00154904.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x7EE5p9E011772; Wed, 14 Aug 2019 10:05:51 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dell.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=smtpout1; bh=wk1EUYZEBbhmGI8bStDIO65TJIiM8nvNGpx7NRbOI1g=; b=hPngz+DfbbWdiz+nqfl9GS2/BQuQH183ZvITMdkpiCTFKlSoohrV7kKHZE/2S//hfitS PUeDwwD9IMu2OIZr+KNO9yx0wJf4AbHnbYhyZlHpZIUSeFKH68pF7AdhxXGG33BW60XK EUP8Yjpz7Q1nff0fLaK7wQFD6fIoZFnNTPi5+RbFBlZn3Wsa7XqUJnhFUl3DPKAFvj0O YUlZHg4bIa+jrSQBQpbvgGBgFmuGYeronGHYErsu4SYTWQHuhxNFO1pgIuzoCM7Wppbg khSZEweV0DQpjlYvViKlQZBwQOk/g1HgOFxKeg7PT0xe+yqFW1QMUx1L+XfnFATiED6c HA==
Received: from mx0b-00154901.pphosted.com (mx0b-00154901.pphosted.com [67.231.157.37]) by mx0a-00154904.pphosted.com with ESMTP id 2ucg1jrxat-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 14 Aug 2019 10:05:51 -0400
Received: from pps.filterd (m0134318.ppops.net [127.0.0.1]) by mx0a-00154901.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x7EE3Zfc079229; Wed, 14 Aug 2019 10:05:46 -0400
Received: from ausxippc101.us.dell.com (ausxippc101.us.dell.com [143.166.85.207]) by mx0a-00154901.pphosted.com with ESMTP id 2u9rjdt57f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 14 Aug 2019 10:05:45 -0400
X-LoopCount0: from 10.166.136.211
X-PREM-Routing: D-Outbound
X-IronPort-AV: E=Sophos;i="5.60,346,1549951200"; d="scan'208,217";a="1285339106"
From: Faibish.Sorin@dell.com
To: Hannes.Tschofenig@arm.com, teep@ietf.org, suit@ietf.org
CC: t.schmidt@haw-hamburg.de
Thread-Topic: Tutorial and Hackathon
Thread-Index: AdVRrAY8GW/tiLKVTpGnbCyx/qWFKwAKyNqQACiVWBAAC3UlYA==
Date: Wed, 14 Aug 2019 14:05:40 +0000
Message-ID: <000e10b7f4864e65b9c18fb506103ac9@x13pwdurdag1001.AMER.DELL.COM>
References: <VI1PR08MB53603E5BF61EF8757B303591FAD20@VI1PR08MB5360.eurprd08.prod.outlook.com> <fdb7894657df408dab5621c5a473624f@x13pwdurdag1001.AMER.DELL.COM> <VI1PR08MB53605E8DCCDF20612715D09CFAAD0@VI1PR08MB5360.eurprd08.prod.outlook.com>
In-Reply-To: <VI1PR08MB53605E8DCCDF20612715D09CFAAD0@VI1PR08MB5360.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Enabled=True; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_SiteId=945c199a-83a2-4e80-9f8c-5a91be5752dd; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Owner=faibish_sorin@emc.com; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_SetDate=2019-08-13T13:07:37.5708205Z; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Name=External Public; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Application=Microsoft Azure Information Protection; MSIP_Label_17cb76b2-10b8-4fe1-93d4-2202842406cd_Extended_MSFT_Method=Manual; aiplabel=External Public
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.146.130.80]
Content-Type: multipart/alternative; boundary="_000_000e10b7f4864e65b9c18fb506103ac9x13pwdurdag1001AMERDELL_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-14_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908140146
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908140146
Archived-At: <https://mailarchive.ietf.org/arch/msg/teep/g72hQpDfgSA0_HRwpBZZci6c-Rw>
Subject: Re: [Teep] Tutorial and Hackathon
X-BeenThere: teep@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A Protocol for Dynamic Trusted Execution Environment Enablement <teep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teep>, <mailto:teep-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teep/>
List-Post: <mailto:teep@ietf.org>
List-Help: <mailto:teep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teep>, <mailto:teep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2019 14:05:54 -0000

Hannes,

From: TEEP <teep-bounces@ietf.org> On Behalf Of Hannes Tschofenig
Sent: Wednesday, August 14, 2019 4:28 AM
To: faibish, sorin; teep@ietf.org; suit@ietf.org
Cc: t.schmidt@haw-hamburg.de
Subject: Re: [Teep] Tutorial and Hackathon


[EXTERNAL EMAIL]
Hi Sorin,

[sf] Just as a disclaimer: I am only focused on DDoS usecases but not sure TEEP or SUIT intention is to prevent DDoS attacks. I want to build tools that will test both protocols.

Thanks for your feedback. I believe your tools would be helpful in the context of the TEEP work but less so for the SUIT work (but maybe I am wrong).
[sf] My plan is to implement a set of tools that will allow to test IoT devices to be exploited for DDoS attacks; packet reflection or random network traffic generation. I am open to ideas as I intent to offer this as a student project. My intention is to test both protocols TEEP and SUIT and I am opened for proposals how to test resistance to DDoS traffic generation.

It is certainly something to think about as we are preparing the virtual machine image.
[sf] I can actually offer the image I already used in Montreal as the base and I will bring to Singapore hackathon.

Regarding the date: the thinking was that we should try it as early as possible but still leaving us enough time. The challenge with attaching the event to the IETF meeting is simply that there are so many other activities attached to it. While the hackathon at the IETF meeting is great (and I always enjoy attending it) it turns out getting so busy that it is difficult to get the actual coding done because there are so many distractions.
[sf] Actually I observed this in Montreal when I was not able to test anything, using my VM and tools, as most of the time we discussed the drafts and slides (no offense to anybody).

With a complex topic as embedded development and TEEs I believe having a much, much smaller group would actually be beneficial for folks. The SUIT hackathon in Berlin was we did last year was such an example. It was very focused and we accomplished a lot.
[sf] I completely agree but if it will only be F2F and I cannot travel I will have to ask somebody to run the tests using the tools that will be open sourced. Thanks

./Sorin

Ciao
Hannes


From: Faibish.Sorin@dell.com<mailto:Faibish.Sorin@dell.com> <Faibish.Sorin@dell.com<mailto:Faibish.Sorin@dell.com>>
Sent: Dienstag, 13. August 2019 15:08
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com<mailto:Hannes.Tschofenig@arm.com>>; teep@ietf.org<mailto:teep@ietf.org>; suit@ietf.org<mailto:suit@ietf.org>
Cc: t.schmidt@haw-hamburg.de<mailto:t.schmidt@haw-hamburg.de>
Subject: RE: Tutorial and Hackathon

Hannes,

As you know I already made the first step at Hackathon in Montreal when I brought a VM that I used to run the DDoS based on IoT devices. So, if there will be a VM with development tools I can add to it my python tools so all can check their devices. I can provide to Thomas all my tools to be also included in the VM. I have a problem though; it will require an additional travel to Berlin outside of the IETF formal meetings and it might create a problem for some people under the current travel restrictions. As it has to be F2F maybe we can do it a day before IETF 107 in Vancouver? Thoughts? Thank you

./Sorin

From: TEEP <teep-bounces@ietf.org<mailto:teep-bounces@ietf.org>> On Behalf Of Hannes Tschofenig
Sent: Tuesday, August 13, 2019 4:24 AM
To: teep@ietf.org<mailto:teep@ietf.org>; suit@ietf.org<mailto:suit@ietf.org>
Cc: Thomas C. Schmidt
Subject: [Teep] Tutorial and Hackathon


[EXTERNAL EMAIL]
Hi all,

at the Montreal meeting we briefly talked about the idea of organizing a tutorial followed by a hackathon for SUIT and TEEP.
A few discussions later we came up with the following story.

Thomas Schmidt (HAW Hamburg) offered to host the event in Berlin. As a date around Jan/Feb 2020 looks more realistic to prepare all the necessary material. The idea was to create a virtual machine with the development environment pre-installed and to make it available to the interested participants well in advance so that we don't have to waste time with tool/IDE problems. This virtual machine image would primarily be used for embedded development. For the TEEP story a separate setup will be needed to support TrustZone/SGX-based devices (since the development environments are different). The virtual machine setup for embedded development would be tailored to a specific embedded hardware and we haven't decided yet what hardware to use. The SUIT hackathon demo boards used in earlier IETF Hackathons may be an reasonable choice. Thoughts are nevertheless welcome. At the tutorial we would get participants up to speed on the most recent protocol/manifest format and the already written tools (e.g., the Python tool to create a manifest) so that time at the hackathon is spent as productive as possible.

We thought it makes sense to cover both SUIT and TEEP in a single event because both groups plan to the manifest format and some of the use cases overlap.

Russ suggested to conclude the event with a virtual interim meeting (maybe an hour long) to discuss the lessons learned.

As you can see, the event is focused on hands-on work and hence we will not offer remote participation possibilities. If you are not interested in writing code this event is likely not very useful for you.

We need your feedback:


  *   Would you like to participate in such an event?
  *   In case you know already, what topic would you like to explore at the event?
  *   Is the Jan/Feb 2020 timeframe good for you?
  *   Is your interest in TEEP, SUIT, or both?
  *   Do you have additional suggestions for getting most out of this event?

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.
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.