From nobody Thu Oct 4 00:33:49 2018 Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 16B60130DE9; Thu, 4 Oct 2018 00:33:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.901 X-Spam-Level: X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.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 umgJ2XxamDuG; Thu, 4 Oct 2018 00:33:37 -0700 (PDT) Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80045.outbound.protection.outlook.com [40.107.8.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 39D5F130DF0; Thu, 4 Oct 2018 00:33:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VPlKfdvx5UOExeeEKDR5CLyUcg7Z/3l/L51hJJxpiWw=; b=pPXU2zP3ay6Na/iWH+w/3DdYXsHwloeoIVZSebryRDGdV/tOykl4YhOiKEGz/FTFQJ7CTLxRHvy7YqRBFf300Kvjwpw/GW15yrGbd9Mw0w+eexRqgp7LWXTRm7RS5mnZDnx6dPY/ntPtP5f/+vZTJfyGeL5VRXF6sgGdbN3/EAY= Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com (10.173.75.16) by VI1PR0801MB2110.eurprd08.prod.outlook.com (10.173.75.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1185.24; Thu, 4 Oct 2018 07:33:33 +0000 Received: from VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::ed81:d01e:32bf:6116]) by VI1PR0801MB2112.eurprd08.prod.outlook.com ([fe80::ed81:d01e:32bf:6116%8]) with mapi id 15.20.1207.022; Thu, 4 Oct 2018 07:33:33 +0000 From: Hannes Tschofenig To: "teep@ietf.org" , "suit@ietf.org" Thread-Topic: Hackathon @ IETF #103 Thread-Index: AdRbszT1hWAJ74EgTDCdx/KZPK4MJA== Date: Thu, 4 Oct 2018 07:33:33 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=Hannes.Tschofenig@arm.com; x-originating-ip: [195.149.223.137] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; VI1PR0801MB2110; 6:eN77IQVQ3cFp5bCTQTVoup59adx7eqbXB0oKINorx/FZsz6I6ZzRBmbOHTnDQxqU7/ABDd0xfgGIGzgThsbyv62Yx3TCM54GfBDJPgtExQxjvzV91gZaCX76WkJQHkEe0DHjEAvVVK0pg1nNytQg2zUzushOd3NHJVvRoF1bHI1g3a5K3xkWmXb2zPxdScyvIlRSQWKW18JY0T6m9pHPrkC1FUoOuiI+KofsP96i0CSpwMbG8PH2Wt2kQpHX0MThss6gvM9Zo5QMv448QZqaRL/U2DivxDf/Lmg4LHswgDvHHZUBIjqB8rncnxZbQ0Eaza4BgVPODGBcPqY22+ZmHpWzxZ3Hpes2IvNtJFt/Nj08BMJxe+uAR9qaSZh0D4ci2sD7M08siYQD74CRbA+DsDlm4T9uo3uNQrGKf81kD2KJlVHbUQlg24QKlGmmwTqxmHHRBr2ug+SviU2GtD0MRg==; 5:kmcRhKYrV27uu2cxUGzF0tkJgh9OJPDSuRSfMeQq9B0Aa6rOMQt/DGBRklxtcRZLHmLG6dT1yvchjtdVqgYYuzcoOoiTdWGMGsUqcVV8mT2ouuyi+/EG9tBmvDL5Ekr9uQ2yWdXYGrdBMqWkGQq5I6blJzJ+uo+0wsEL2IGyJe0=; 7:TpApRCh5VP09kvCHltzpN1KMyb5Ens/ixORhDq38BO/AfPI4G3d2K44zAsyjgzcmJEz/TKYM3zPzioA4YTS9gG9Fs0S2P3Cyx4e56lkFWHXdwOD9+jqTo0qd4MLLsqduDHZEzF5hpvpHcvKAVOMHUBxtyHU8uc92JmmGQUSao/P0VmkRuwe7zsUArbqxjrfgMqt9v6KqnrZDerZGyhbIRhVce2WXMOcshYWITyzKNhzWpVghJxDY7bFFU3cB2+0f x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: f926938a-6e93-4cb2-2c21-08d629cbb09c x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:VI1PR0801MB2110; x-ms-traffictypediagnostic: VI1PR0801MB2110: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(3231355)(944501410)(52105095)(93006095)(93001095)(10201501046)(6055026)(149066)(150057)(6041310)(20161123560045)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(201708071742011)(7699051); SRVR:VI1PR0801MB2110; BCL:0; PCL:0; RULEID:; SRVR:VI1PR0801MB2110; x-forefront-prvs: 0815F8251E x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(39860400002)(396003)(346002)(376002)(366004)(40434004)(53754006)(189003)(199004)(105586002)(106356001)(74316002)(110136005)(476003)(7736002)(81156014)(81166006)(99286004)(186003)(8936002)(5660300001)(33656002)(8676002)(256004)(14444005)(5024004)(486006)(26005)(102836004)(6506007)(7696005)(5250100002)(790700001)(6116002)(3846002)(6436002)(68736007)(2501003)(9686003)(54896002)(55016002)(14454004)(86362001)(71200400001)(71190400001)(53936002)(2906002)(316002)(39060400002)(66066001)(478600001)(2900100001)(25786009)(72206003)(97736004); DIR:OUT; SFP:1101; SCL:1; SRVR:VI1PR0801MB2110; H:VI1PR0801MB2112.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: ofYNQVzyaT57geWXoe4heVg5rrOM6MLpBrQt8zxxSGQ4oQqo74dHnw5pj96SN7pFXNImpU5QqAXpk+SQCaJZSAuZeF+AO1eGtOXk4ftvu4H8pa6Xf6B71ejdVsI+ocuq4NUkb+RgNlCP79dOMjGd+9+MGXHPend4sVw9WgmApuwWBaivNFCvuUgPk8GoSC4DQAxeziS0trSzTy6ikGz6Oe/RtCu48kIfoacsMhBPghNUyZrZW3vJMUV8bzl+0lrIObr32IVW2RXlooFuNd0oz1wBctBTS0jCdLLsLdxhA7UKi/+s/G2C8qhnU1eKrqVdhZJHEbTusv2TMRXAG+xgz2SYfCq5FaX6Q9PiJDGouSE= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_VI1PR0801MB21124F5B688255A7310516ADFAEA0VI1PR0801MB2112_" MIME-Version: 1.0 X-OriginatorOrg: arm.com X-MS-Exchange-CrossTenant-Network-Message-Id: f926938a-6e93-4cb2-2c21-08d629cbb09c X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2018 07:33:33.6077 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0801MB2110 Archived-At: Subject: [Suit] Hackathon @ IETF #103 X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 07:33:40 -0000 --_000_VI1PR0801MB21124F5B688255A7310516ADFAEA0VI1PR0801MB2112_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi all, When we worked on firmware and software updates at the last Hackathon at th= e Montreal IETF meeting we agreed that it would be useful to also continue = the effort at the IETF#103 Hackathon. In order to prepare appropriately it = would be good to know who is planning to attend and what they are most inte= rested in. I looked at the attendee list but so far it looks pretty short. So, if you thinking about attending the Hackathon please let me know. It wo= uld be interesting to find out what we could accomplish during these 1 =BD = days and what hardware we need to carry along. Ciao Hannes IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease 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. --_000_VI1PR0801MB21124F5B688255A7310516ADFAEA0VI1PR0801MB2112_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi all,

 

When we worked on firmware and software updates at t= he last Hackathon at the Montreal IETF meeting we agreed that it would be u= seful to also continue the effort at the IETF#103 Hackathon. In order to pr= epare appropriately it would be good to know who is planning to attend and what they are most interested in. I = looked at the attendee list but so far it looks pretty short.

 

So, if you thinking about attending the Hackathon pl= ease let me know. It would be interesting to find out what we could accompl= ish during these 1 =BD days and what hardware we need to carry along.<= /o:p>

 

Ciao

Hannes

IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease 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. --_000_VI1PR0801MB21124F5B688255A7310516ADFAEA0VI1PR0801MB2112_-- From nobody Thu Oct 4 11:10:03 2018 Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 26322130EC0; Thu, 4 Oct 2018 11:09:54 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.456 X-Spam-Level: X-Spam-Status: No, score=-2.456 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.456, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 DlvEoD-Y8XeY; Thu, 4 Oct 2018 11:09:51 -0700 (PDT) Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-eopbgr690119.outbound.protection.outlook.com [40.107.69.119]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EEAA5130E99; Thu, 4 Oct 2018 11:09:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=vMwqs+zh/QFcz6xL5WFIHZ3aipvoGNmjG0JCprMLL9w=; b=ElYymvk75VQTcuwtRQuzpANuUUSIKjMfNl4MwEgeYRaglkn2TJqE1R2xrp7aO697zK5kE5lput7qd3V1U7qI3ELCrHUngt5XIPwenAQmyb04SuBHuSkhcH68lp9rgYfAzsRTRdASiMAZZnpB5lmcQyGdY1Aps0BhzHQcN6Y4kfs= Received: from CY4PR21MB0168.namprd21.prod.outlook.com (10.173.192.150) by CY4PR21MB0744.namprd21.prod.outlook.com (10.173.189.10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1228.5; Thu, 4 Oct 2018 18:09:48 +0000 Received: from CY4PR21MB0168.namprd21.prod.outlook.com ([fe80::3484:e2d0:b23:90af]) by CY4PR21MB0168.namprd21.prod.outlook.com ([fe80::3484:e2d0:b23:90af%5]) with mapi id 15.20.1228.011; Thu, 4 Oct 2018 18:09:48 +0000 From: Dave Thaler To: Hannes Tschofenig , "teep@ietf.org" , "suit@ietf.org" Thread-Topic: Hackathon @ IETF #103 Thread-Index: AdRbszT1hWAJ74EgTDCdx/KZPK4MJAAWhhCw Date: Thu, 4 Oct 2018 18:09:48 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=dthaler@ntdev.microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-10-04T18:09:50.3662708Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General x-originating-ip: [73.59.106.235] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; CY4PR21MB0744; 6:REH0NsmtQo46ubBi/Nm7lJwBZT78PsXFDfh+0Bvb+jGtkGlejs2mSHjq7VnfvPoUlWxQ5mkvlh82rXVLG5uLySEURcU0CINoNqdk/KiqZ7gmECFZkMnZXZr5tLLqYuSfEhVUvvM49m8D01sCepjZm0jf8bEalrF9Kgxbp9GhbotMeEQnA2fX/K05kYkjlpiVMjAFlxCIK6C2xjJ9k9ZwWZvSUsSorqFoLmHwHn0d67MVXvuL06UTx/KpxJNCom0xu2F6N5/xb4IunPUoNmgYc/pQXFTle7hdFt31m/Ck85YVIWKe2lgUIZyN9rkJ2XeQRQ5AtYdcElGOgztaRA+XirYqVcwXOVpCkst3/qmddVFmGB6o2gM4GrxWUTPVPCbcOf3V2Q3P4cCqiGzgYGjC7z5FixrBJfv6/yywVScPZ6szkpKw+d8ke0FlKyk+Ie2Bo17uXeUxtpEQHSQZqipSYQ==; 5:GzPg9VM1T4++rOP/lL2kYUzUn42R+O4cPjH3sRY6JTyM9aBPIzDmrRPNGuowBX2uQwgZAh7ofL4qJ63exaeOX1ILQkyJItrhTW+NYksvnxdJVHmmZuqj+eO4wMVYA38xMxWBuznDxe4zqoQ9pw8E+RQmAOp2t2uIph4FgrojzjU=; 7:NtnTOekqD0kL9ZWEihWo0viRPxymP5zOvc4oqBpH+dA+7w13LAsGylXd5/HwdDhBHUsjtnaQ8mdM1VINJxQI/eCh1LnAkwjhZUJVeoa2Gbn8Mgs+xUSNV1Mo7M6g+9gU520kS2p5yCnA/EwImzshJNnYMQ6b+C28LSU6sgCxzwnt6+9IP/fMCqCbqQwG6hfqEcYP5tYt31L5MnAZZGkgqqEbpBd0LBqVpgEdxJal92dSMm9vz7Oj5Dt/+l7mXrHT x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: e6804516-c69b-4d77-3e92-08d62a2492b6 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7193020); SRVR:CY4PR21MB0744; x-ms-traffictypediagnostic: CY4PR21MB0744: authentication-results: spf=none (sender IP is ) smtp.mailfrom=dthaler@microsoft.com; x-ld-processed: 72f988bf-86f1-41af-91ab-2d7cd011db47,ExtAddr x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(21748063052155)(28532068793085)(190501279198761)(227612066756510); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3231355)(944501410)(52105095)(2018427008)(3002001)(93006095)(93001095)(6055026)(149066)(150057)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(201708071742011)(7699051)(76991048); SRVR:CY4PR21MB0744; BCL:0; PCL:0; RULEID:; SRVR:CY4PR21MB0744; x-forefront-prvs: 0815F8251E x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(396003)(39860400002)(366004)(346002)(136003)(53754006)(189003)(199004)(40434004)(68736007)(11346002)(10290500003)(26005)(76176011)(256004)(105586002)(55016002)(186003)(7736002)(6506007)(74316002)(6306002)(54896002)(14444005)(2501003)(2900100001)(5024004)(9686003)(99286004)(2201001)(6246003)(8990500004)(25786009)(22452003)(86362001)(316002)(53936002)(6436002)(106356001)(446003)(86612001)(97736004)(486006)(53546011)(7696005)(790700001)(3846002)(5250100002)(476003)(6116002)(102836004)(478600001)(10090500001)(81156014)(229853002)(66066001)(81166006)(8676002)(71190400001)(2906002)(71200400001)(110136005)(33656002)(5660300001)(8936002)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR21MB0744; H:CY4PR21MB0168.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: Ov17Ka7fN1ierL3O5PSAoJUoDx6hNPTSMgOxLSYA779YjBaxR/UogRdcmr5CL6OIr5ACzieav0wes9kQ1mbJuWFGvJ0zciQAU/IUXIbxpiiRJdPfABJX1Oe9lqQ2aNfcJ7gAqlyjw090Uhp7SxnoTNL0Yk3JQtYPpTAJv6MqPO94s8RxUQHIfSN+MNBt0iaQia47sM2G24Bvsjro6+mxiqwbZ4wS40MaJYWu38a8BCR6Ig3qQzScEBlGaFGQBNML7HwkXqDJN3YWpzDt90LRu6cpWu8xevVkPArbJx9plObHzKe02bSzZloJaE6YfU/+CamgdqZiQ5EgUj1zyzs2JOwziPgxm5d5y08gdO03+yQ= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_CY4PR21MB016871C3FC5E284C7BD29511A3EA0CY4PR21MB0168namp_" MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-Network-Message-Id: e6804516-c69b-4d77-3e92-08d62a2492b6 X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Oct 2018 18:09:48.6618 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR21MB0744 Archived-At: Subject: Re: [Suit] Hackathon @ IETF #103 X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 04 Oct 2018 18:10:02 -0000 --_000_CY4PR21MB016871C3FC5E284C7BD29511A3EA0CY4PR21MB0168namp_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable I plan to be at the hackathon again, and work on an OTrP implementation to = look for any more spec issues. Dave From: TEEP On Behalf Of Hannes Tschofenig Sent: Thursday, October 4, 2018 12:34 AM To: teep@ietf.org; suit@ietf.org Subject: [Teep] Hackathon @ IETF #103 Hi all, When we worked on firmware and software updates at the last Hackathon at th= e Montreal IETF meeting we agreed that it would be useful to also continue = the effort at the IETF#103 Hackathon. In order to prepare appropriately it = would be good to know who is planning to attend and what they are most inte= rested in. I looked at the attendee list but so far it looks pretty short. So, if you thinking about attending the Hackathon please let me know. It wo= uld be interesting to find out what we could accomplish during these 1 =BD = days and what hardware we need to carry along. Ciao Hannes IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease 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. --_000_CY4PR21MB016871C3FC5E284C7BD29511A3EA0CY4PR21MB0168namp_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

I plan to be at the ha= ckathon again, and work on an OTrP implementation to look for any more spec= issues.

 

Dave=

 

From: TEEP <teep-bounces@ietf.org> O= n Behalf Of Hannes Tschofenig
Sent: Thursday, October 4, 2018 12:34 AM
To: teep@ietf.org; suit@ietf.org
Subject: [Teep] Hackathon @ IETF #103

 

Hi all,

 

When we worked on firmware and = software updates at the last Hackathon at the Montreal IETF meeting we agre= ed that it would be useful to also continue the effort at the IETF#103 Hack= athon. In order to prepare appropriately it would be good to know who is planning to attend and what they are most = interested in. I looked at the attendee list but so far it looks pretty sho= rt.

 

So, if you thinking about atten= ding the Hackathon please let me know. It would be interesting to find out = what we could accomplish during these 1 =BD days and what hardware we need = to carry along.

 

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 othe= r person, use it for any purpose, or store or copy the information in any m= edium. Thank you.

--_000_CY4PR21MB016871C3FC5E284C7BD29511A3EA0CY4PR21MB0168namp_-- From nobody Fri Oct 5 16:02:01 2018 Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59D42128CF2; Fri, 5 Oct 2018 16:01:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 RmxGxXE5Lt3X; Fri, 5 Oct 2018 16:01:47 -0700 (PDT) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 4059812872C; Fri, 5 Oct 2018 16:01:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost.informatik.uni-bremen.de [134.102.201.11]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w95N1h5K027980; Sat, 6 Oct 2018 01:01:43 +0200 (CEST) Received: from [192.168.217.102] (p54A6C3C7.dip0.t-ipconnect.de [84.166.195.199]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 42Rlcl3YPszDXqZ; Sat, 6 Oct 2018 01:01:43 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 X-Mao-Original-Outgoing-Id: 560473301.606288-c7fe6422b2715fe968046003cdd4f56d Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Sat, 6 Oct 2018 01:01:42 +0200 Message-Id: To: suit , teep@ietf.org, din@irtf.org, rats@ietf.org, eat@ietf.org X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [Suit] Constrained Node/Network Cluster @ IETF103: DRAFT AGENDA X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Oct 2018 23:01:51 -0000 Here is my usual eclectic condensed agenda based on the DRAFT AGENDA for IETF103. Remember that there is still quite some potential for changes. cbor/teep and 6tisch/suit are annoying but probably livable. No qirg for core goers... All times are ICT (Indochina Time) =3D=3D UTC +7 hours. There is no daylight saving time in effect in Thailand. DST will have ended in Europe by then (e.g., CET =3D UTC+0100) and will end in the US during the initial weekend (On Sun, Nov 4; e.g. EST =3D UTC-0500). (You can get pure UTC times on https://datatracker.ietf.org/meeting/agenda-utc, for those who want to listen from remote.) Please note that the Friday schedule is still evolving; plan to stick around until 13:20 or you may miss interesting conversations. Gr=C3=BC=C3=9Fe, Carsten SATURDAY/SUNDAY, November 3/4. 2018 -- Hackathon (including various interops) (Centre Ville) -- Sun 1700-1900 Welcome Reception - Garden at Queen's Park -- Sun 1800-2000 Hot RFC Lightning Talks - Thai Chitlada 3 MONDAY, November 5, 2018 0900-1100 Morning Session I Thai Chitlada 3 IRTF*** dinrg Decentralized Internet Infrastructure = Proposed RG Meeting 1 OPS v6ops IPv6 Operations WG Boromph. 1/2 RTG *** roll Routing Over Low power and Lossy = networks WG Thai Chitlada 1 SEC secdispatch Security Dispatch WG Thai Chitlada 2 TSV taps Transport Services WG 1120-1220 Morning Session II Thai Chitlada 1 IRTF cfrg Crypto Forum Thai Chitlada 2 TSV tsvarea Transport Area Open Meeting 1350-1550 Afternoon Session I Boromph. 1/2 ART *** core Constrained RESTful Environments WG Meeting 2 OPS anima Autonomic Networking Integrated Model = and Approach WG Thai Chitlada 2 SEC tls Transport Layer Security WG Thai Chitlada 3 TSV tsvwg Transport Area Working Group WG 1610-1810 Afternoon Session II Meeting 1 INT *** 6lo IPv6 over Networks of = Resource-constrained Nodes WG Thai Chitlada 1 IRTF irtfopen IRTF Open Meeting Thai Chitlada 2 SEC mls Messaging Layer Security WG TUESDAY, November 6, 2018 0900-1100 Morning Session I Thai Chitlada 2 ART httpbis Hypertext Transfer Protocol WG Meeting 1 INT *** lpwan IPv6 over Low Power Wide-Area Networks = WG Boromph. 1/2 SEC oauth Web Authorization Protocol WG 1120-1220 Morning Session II Thai Chitlada 3 INT ipwave IP Wireless Access in Vehicular = Environments WG Meeting 2 SEC oauth Web Authorization Protocol WG 1350-1550 Afternoon Session I Thai Chitlada 3 INT 6man IPv6 Maintenance WG Thai Chitlada 2 SEC rats Remote ATtestation ProcedureS BOF Thai Chitlada 1 TSV quic QUIC WG 1610-1810 Afternoon Session II Thai Chitlada 1 IRTF maprg Measurement and Analysis for Protocols Meeting 2 IRTF*** t2trg Thing-to-Thing WEDNESDAY, November 7, 2018 0900-1100 Morning Session ! Thai Chitlada 3 ART *** cbor Concise Binary Object Representation = Maintenance and Extensions WG Boromph. 3 RTG bier Bit Indexed Explicit Replication WG Meeting 1 SEC *** teep Trusted Execution Environment = Provisioning WG Boromph. 1/2 SEC tokbind Token Binding WG Thai Chitlada 1 TSV quic QUIC WG 1120-1220 Morning Session II Boromph. 1/2 INT *** lwig Light-Weight Implementation Guidance WG Thai Chitlada 1 SEC tls Transport Layer Security WG Thai Chitlada 2 TSV tsvwg Transport Area Working Group WG 1350-1520 Afternoon Session I Meeting 1 GEN wugh WGs Using GitHub BOF Thai Chitlada 3 INT homenet Home Networking WG Meeting 2 IRTF panrg Path Aware Networking RG 1540-1710 Afternoon Session II Meeting 1 ART dispatch Dispatch WG - Joint with ARTAREA Thai Chitlada 3 INT intarea Internet Area Working Group WG Meeting 2 IRTF pearg Privacy Enhancements and Assessments = Proposed Research Group Boromph. 3 RTG babel Babel routing protocol WG Boromph. 1/2 RTG rift Routing In Fat Trees WG THURSDAY, November 8, 2018 0900-1100 Morning Session I Thai Chitlada 1 ART httpbis Hypertext Transfer Protocol WG Boromph. 4 INT *** 6tisch IPv6 over the TSCH mode of IEEE = 802.15.4e WG Meeting 1 IRTF icnrg Information-Centric Networking Thai Chitlada 2 SEC *** suit Software Updates for Internet of Things = WG 1120-1220 Morning Session II Thai Chitlada 2 ART *** core Constrained RESTful Environments WG Thai Chitlada 3 IRTF qirg Quantum Internet Proposed Research Group Boromph. 4 RTG bier Bit Indexed Explicit Replication WG Thai Chitlada 1 SEC mls Messaging Layer Security WG Meeting 2 TSV rmcat RTP Media Congestion Avoidance = Techniques WG 1350-1550 Afternoon Session I Meeting 1 INT dnssd Extensions for Scalable DNS Service = Discovery WG Thai Chitlada 2 RTG detnet Deterministic Networking WG Thai Chitlada 1 SEC saag Security Area Open Meeting 1610-1810 Afternoon Session II Thai Chitlada 3 RTG rtgarea Routing Area Open Meeting Thai Chitlada 1 SEC *** ace Authentication and Authorization for = Constrained Environments WG Boromph. 1/2 SEC acme Automated Certificate Management = Environment WG FRIDAY, November 9, 2018 Various ad-hoc meetings, please see https://trac.ietf.org/trac/ietf/meeting/wiki/103sidemeetings#FRIDAY -- 0900..1320 T2TRG work meeting -- 1000..??? COIN (Computing in the Network) From nobody Tue Oct 16 06:48:23 2018 Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE783130DC9 for ; Tue, 16 Oct 2018 06:48:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.9 X-Spam-Level: X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] 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 vAiBvunoNxlb for ; Tue, 16 Oct 2018 06:48:19 -0700 (PDT) Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D50FD12D4EE for ; Tue, 16 Oct 2018 06:48:19 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id 6358A300A98 for ; Tue, 16 Oct 2018 09:48:17 -0400 (EDT) X-Virus-Scanned: amavisd-new at mail.smeinc.net Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id hxmsCx2pSDyW for ; Tue, 16 Oct 2018 09:48:16 -0400 (EDT) Received: from a860b60074bd.home (pool-71-127-50-4.washdc.fios.verizon.net [71.127.50.4]) by mail.smeinc.net (Postfix) with ESMTPSA id 7D38B300523 for ; Tue, 16 Oct 2018 09:48:16 -0400 (EDT) From: Russ Housley Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Message-Id: Date: Tue, 16 Oct 2018 09:48:17 -0400 To: suit X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [Suit] Draft agenda for SUIT WG at IETF 103 X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2018 13:48:22 -0000 https://datatracker.ietf.org/meeting/103/materials/agenda-103-suit-00 Please send comments to the list. Russ From nobody Tue Oct 16 08:19:10 2018 Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 274B8130DC5 for ; Tue, 16 Oct 2018 08:19:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.065 X-Spam-Level: X-Spam-Status: No, score=-2.065 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.064, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 LvwqUzVqJC3j for ; Tue, 16 Oct 2018 08:19:05 -0700 (PDT) Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0136.outbound.protection.outlook.com [104.47.41.136]) (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 8E2CA12D4EE for ; Tue, 16 Oct 2018 08:19:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=JGhFGwRDY9FLe0xqwYO5CiljeDTHIKbhtfHZhWNpdaU=; b=kBuEmNPxQhk8Bs/r6Axqf+mRVS+JmpZbFY1TtfnP7GlMmogi6SY0R+zRZh9DVimVq4GCqJeJS6btwOmzffmd6ZFoBjWCu+QDEy6Lx6kIg3cLZ2RMzl0cBmKhDF3eg3Ed6qFQSpkUQkQKjxc9Ar2tk9Jzn22IMR+tiWSXHhD+BlQ= Received: from SN4PR2101MB0814.namprd21.prod.outlook.com (10.167.151.156) by SN4PR2101MB0736.namprd21.prod.outlook.com (10.167.151.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.3; Tue, 16 Oct 2018 15:19:04 +0000 Received: from SN4PR2101MB0814.namprd21.prod.outlook.com ([fe80::5006:856e:45c3:ea97]) by SN4PR2101MB0814.namprd21.prod.outlook.com ([fe80::5006:856e:45c3:ea97%5]) with mapi id 15.20.1250.004; Tue, 16 Oct 2018 15:19:04 +0000 From: Martin Pagel To: Russ Housley , suit Thread-Topic: [Suit] Draft agenda for SUIT WG at IETF 103 Thread-Index: AQHUZVbvf6luJQvbV0CA2kSEOhXg4qUh+9ew Date: Tue, 16 Oct 2018 15:19:03 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=mapagel@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-10-16T15:19:03.3535768Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General x-originating-ip: [97.126.26.32] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; SN4PR2101MB0736; 6:mSuohiFN1AEEAy697B2aVo0o7jPYq8/+1CPIKSSytVtUW9QWYmUdVGWoluIXXDs29gZtr8OxiTtR2678MmMwDdjTlgX+cDEooGJGSqwCU1b3l5EfBAtiB+wSqF495J9ZEVtdJt/jvbvUSHKb1afMh7qmSUAC7xHCfrwFyTI8N3KiUtBNye0cFlPhN11fxjQRaXYK4PIJO7C0reIuKtAF3AJuMyqWKuqOPDOAzSOyfE2LlvoJT2q30763iDut8lSa+sFQEOpuFfJPz6PUkY1eVgUrBaLQMY7The9AAHrv+eeY7bwDWirrhRrdHcNu1RK9r0MPiRGV7/3yzeA7UCxAiqvPsW/JU//xqd4X0igHyhEPPltUXpEds1JvO+/d98+vRSsE/yXbV6OX8dHyNlk+FO0btiDqsEtsBXnLfVmVG/JySTVL+7qhsg73vhVMxVrGz/Mccq0MlWPpg3q1hj1B8w==; 5:NIVi4+r6iihZBZEYEDAikV/Ojfk8UYE1x2yVqUnqkGWRcJ9aXuSnyPIK81wNcNxup3N99pkw8ARq/IYaJND9kw1dCRFCosW+o2OOyFAKF+eZRCCCn84aSZkOb6MxLhUzNOu/4xRAEJctKD48UxPt33X3qhmHZTJ/XythReYDvPU=; 7:HpuswdP9XwMeLtsf4DqwOMYZQh+Y9UH/dVXuG8w14Qk2iGfJaHh7V9FAYnezCvAD24fTfcMPYie4hVs40J9RdkwKp3ZX9+YfcWCLAxMSSZqSOI8ZrjKiFmQautrDGawS46P/MJ2A25IUP15wWbOfZQ== x-ms-exchange-antispam-srfa-diagnostics: SOS; x-ms-office365-filtering-correlation-id: 4e00c984-f4a1-4ec6-528e-08d6337ab554 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(5600074)(711020)(4618075)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(2017052603328)(7193020); SRVR:SN4PR2101MB0736; x-ms-traffictypediagnostic: SN4PR2101MB0736: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(219752817060721)(189930954265078); x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231355)(944501410)(52105095)(2018427008)(93006095)(93001095)(10201501046)(3002001)(6055026)(149066)(150057)(6041310)(20161123564045)(20161123562045)(20161123558120)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991067); SRVR:SN4PR2101MB0736; BCL:0; PCL:0; RULEID:; SRVR:SN4PR2101MB0736; x-forefront-prvs: 0827D7ACB9 x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(136003)(39860400002)(346002)(376002)(13464003)(199004)(189003)(25786009)(11346002)(97736004)(446003)(476003)(486006)(10090500001)(102836004)(8990500004)(256004)(5250100002)(86612001)(186003)(2900100001)(53936002)(9686003)(6306002)(26005)(22452003)(2906002)(316002)(6246003)(5660300001)(55016002)(229853002)(575784001)(86362001)(106356001)(6436002)(74316002)(76176011)(105586002)(6346003)(71190400001)(66066001)(7696005)(33656002)(478600001)(10290500003)(8676002)(8936002)(6506007)(7736002)(53546011)(305945005)(81166006)(3846002)(68736007)(110136005)(14454004)(71200400001)(966005)(99286004)(6116002)(81156014)(72206003); DIR:OUT; SFP:1102; SCL:1; SRVR:SN4PR2101MB0736; H:SN4PR2101MB0814.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts) authentication-results: spf=none (sender IP is ) smtp.mailfrom=Martin.Pagel@microsoft.com; x-microsoft-antispam-message-info: J3ERoszaag5rjLLLpWQ2rQwVW6MLpRLrEd/IrbZAUrwpS28/+mf2XBCFaFPDB56pSOcYdoOQ2x4XDWIkOsbTCaYPdoY9rJNw68aeXt2JtmaV5A7K5Pui1j3LBIm+BYnDejy/4Brryg/jewUIlXSlkz/x6hhHsoyNBb/EnusRqmZlyUfcpb4Il3JBzd+9zVjXJKDmpD3WrBU2NZLDi0nQj98xn45NptoceldqB9rgq35gQ1q3vbp2MojlK48HeOYegYKl42J2Dl2t4gotFw61VGKwLIX//ACMsJAJFW6B/dNRzPorecQxBoG8KrOzHvNKnsJma/LS+J5eSzpkXapcPBHZvtu/15oD/uvY8r9igH0= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: microsoft.com X-MS-Exchange-CrossTenant-Network-Message-Id: 4e00c984-f4a1-4ec6-528e-08d6337ab554 X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Oct 2018 15:19:03.9111 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47 X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN4PR2101MB0736 Archived-At: Subject: Re: [Suit] Draft agenda for SUIT WG at IETF 103 X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Oct 2018 15:19:08 -0000 Thanks, Russ,=20 The MeetEcho link refers to location Vancouver and therefore the timing may= be off, can you check? Thanks Martin -----Original Message----- From: Suit On Behalf Of Russ Housley Sent: Tuesday, October 16, 2018 6:48 AM To: suit Subject: [Suit] Draft agenda for SUIT WG at IETF 103 https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fdatatrac= ker.ietf.org%2Fmeeting%2F103%2Fmaterials%2Fagenda-103-suit-00&data=3D02= %7C01%7Cmartin.pagel%40microsoft.com%7C0fac696a235043f1618e08d6336e105a%7C7= 2f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636752945163797623&sdata=3D6Z= CCl%2B5GECQeAbbEqrbnlKifc59f%2BHXELctXTq0CBJg%3D&reserved=3D0 Please send comments to the list. Russ _______________________________________________ Suit mailing list Suit@ietf.org https://na01.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.ietf= .org%2Fmailman%2Flistinfo%2Fsuit&data=3D02%7C01%7Cmartin.pagel%40micros= oft.com%7C0fac696a235043f1618e08d6336e105a%7C72f988bf86f141af91ab2d7cd011db= 47%7C1%7C0%7C636752945163797623&sdata=3DBKssUDUW88Qv1LPXJUcUAH3hjPqpYOl= JTszXXOdZVFg%3D&reserved=3D0 From nobody Wed Oct 17 07:40:42 2018 Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BBD36130DE3; Wed, 17 Oct 2018 07:40:33 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.199 X-Spam-Level: X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, URIBL_BLOCKED=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 l_mNTGujUmzq; Wed, 17 Oct 2018 07:40:31 -0700 (PDT) Received: from mailhost.informatik.uni-bremen.de (mailhost.informatik.uni-bremen.de [IPv6:2001:638:708:30c9::12]) (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 A7634130DDE; Wed, 17 Oct 2018 07:40:29 -0700 (PDT) X-Virus-Scanned: amavisd-new at informatik.uni-bremen.de Received: from submithost.informatik.uni-bremen.de (submithost2.informatik.uni-bremen.de [IPv6:2001:638:708:30c8:406a:91ff:fe74:f2b7]) by mailhost.informatik.uni-bremen.de (8.14.5/8.14.5) with ESMTP id w9HEeIrG029861; Wed, 17 Oct 2018 16:40:23 +0200 (CEST) Received: from [192.168.217.114] (p54A6CA9F.dip0.t-ipconnect.de [84.166.202.159]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by submithost.informatik.uni-bremen.de (Postfix) with ESMTPSA id 42Zvwf2Dxpz1Bqf; Wed, 17 Oct 2018 16:40:18 +0200 (CEST) From: Carsten Bormann Content-Type: text/plain; charset=utf-8 X-Mao-Original-Outgoing-Id: 561480016.121739-51f36c93b1d85dd445e675488f4c9abe Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Date: Wed, 17 Oct 2018 16:40:17 +0200 Message-Id: <6B9735FC-AD2D-4D8D-ABEA-D6D741233322@tzi.org> To: suit , teep@ietf.org, din@irtf.org, rats@ietf.org, eat@ietf.org X-Mailer: Apple Mail (2.3445.9.1) Archived-At: Subject: [Suit] Constrained Node/Network Cluster @ IETF103: "FINAL" AGENDA X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Oct 2018 14:40:34 -0000 Here is my usual eclectic condensed agenda based on the "FINAL" AGENDA for IETF103. A few changes from the DRAFT AGENDA. I waited a bit with sending this as a few more side meetings have become known, as well. Of course, "FINAL" doesn't mean final. cbor/teep and 6tisch/ace (was suit) are annoying but probably livable. qirg no longer conflicts with core :-). dinrg is now on top of lpwan. secdispatch on top of t2trg will all but make sure no security people attend t2trg. All times are ICT (Indochina Time) =3D=3D UTC +7 hours. There is no daylight saving time in effect in Thailand. DST will have ended in Europe by then (e.g., CET =3D UTC+0100) and will end in the US during the initial weekend (On Sun, Nov 4; e.g. EST =3D UTC-0500). (You can get pure UTC times on https://datatracker.ietf.org/meeting/agenda-utc, for those who want to listen from remote.) Please note that the Friday schedule is still evolving; plan to stick around until 13:20 or you may miss interesting conversations. Gr=C3=BC=C3=9Fe, Carsten SATURDAY/SUNDAY, November 3/4. 2018 -- Hackathon (including various interops) (Centre Ville), e.g.: T2TRG WISHI, possibly some CBOR, LPWAN, TLS 1.3, EST-COAPS, TEEP Please see https://trac.ietf.org/trac/ietf/meeting/wiki/103hackathon -- Sun 1700-1900 Welcome Reception - Garden at Queen's Park -- Sun 1800-2000 Hot RFC Lightning Talks - Chitlada 3 MONDAY, November 5, 2018 0900-1100 Morning Session I Chitlada 2 ART dispatch Dispatch WG - Joint with ARTAREA Meeting 1 OPS v6ops IPv6 Operations WG Boromph. 1/2 RTG *** roll Routing Over Low power and Lossy = networks WG Meeting 2 SEC oauth Web Authorization Protocol WG 1120-1220 Morning Session II Chitlada 1 IRTF cfrg Crypto Forum Chitlada 2 TSV tsvarea Transport Area Open Meeting 1350-1550 Afternoon Session I Boromph. 1/2 ART *** core Constrained RESTful Environments WG Meeting 1 OPS anima Autonomic Networking Integrated Model = and Approach WG Chitlada 2 SEC tls Transport Layer Security WG Chitlada 3 TSV tsvwg Transport Area Working Group WG 1610-1810 Afternoon Session II Meeting 2 INT *** 6lo IPv6 over Networks of = Resource-constrained Nodes WG Chitlada 1 IRTF irtfopen IRTF Open Meeting Chitlada 2 SEC mls Messaging Layer Security WG TUESDAY, November 6, 2018 0900-1100 Morning Session I Chitlada 1 ART httpbis Hypertext Transfer Protocol WG Meeting 1 INT *** lpwan IPv6 over Low Power Wide-Area Networks = WG Meeting 2 IRTF*** dinrg Decentralized Internet Infrastructure = Proposed RG Boromph. 4 SEC tokbind Token Binding WG 1120-1220 Morning Session II Chitlada 3 INT ipwave IP Wireless Access in Vehicular = Environments WG Chitlada 2 IRTF qirg Quantum Internet Proposed Research Group Meeting 1 SEC oauth Web Authorization Protocol WG 1350-1550 Afternoon Session I Chitlada 3 INT 6man IPv6 Maintenance WG Chitlada 2 SEC rats Remote ATtestation ProcedureS BOF Chitlada 1 TSV quic QUIC WG 1610-1810 Afternoon Session II Chitlada 1 IRTF maprg Measurement and Analysis for Protocols Meeting 1 IRTF*** t2trg Thing-to-Thing Meeting 2 SEC secdispatch Security Dispatch WG Pagoda -- 1700..1800 CACAO side meeting Apartment 3 -- 1800..2000 IoT Onboarding side meeting (lear/mcr) WEDNESDAY, November 7, 2018 0900-1100 Morning Session I Chitlada 3 ART *** cbor Concise Binary Object Representation = Maintenance and Extensions WG Boromph. 3 RTG bier Bit Indexed Explicit Replication WG Meeting 2 SEC *** teep Trusted Execution Environment = Provisioning WG Chitlada 1 TSV quic QUIC WG 1120-1220 Morning Session II Meeting 2 INT *** lwig Light-Weight Implementation Guidance WG Chitlada 1 SEC tls Transport Layer Security WG Chitlada 2 TSV tsvwg Transport Area Working Group WG 1350-1520 Afternoon Session I Meeting 2 GEN wugh WGs Using GitHub BOF Chitlada 3 INT homenet Home Networking WG Meeting 1 IRTF panrg Path Aware Networking RG -- 1400..1500 IoT Onboarding Mechanisms side meeting 1540-1710 Afternoon Session II Chitlada 3 INT intarea Internet Area Working Group WG Meeting 1 IRTF pearg Privacy Enhancements and Assessments = Proposed Research Group Boromph. 3 RTG babel Babel routing protocol WG Boromph. 1/2 RTG rift Routing In Fat Trees WG Meeting 2 TSV taps Transport Services WG THURSDAY, November 8, 2018 0900-1100 Morning Session I Chitlada 1 ART httpbis Hypertext Transfer Protocol WG Meeting 2 IRTF icnrg Information-Centric Networking Chitlada 2 SEC *** suit Software Updates for Internet of Things = WG 1120-1220 Morning Session II Chitlada 2 ART *** core Constrained RESTful Environments WG Boromph. 1/2 RTG bier Bit Indexed Explicit Replication WG Chitlada 1 SEC mls Messaging Layer Security WG Meeting 1 TSV rmcat RTP Media Congestion Avoidance = Techniques WG 1350-1550 Afternoon Session I Meeting 2 INT dnssd Extensions for Scalable DNS Service = Discovery WG Chitlada 2 RTG detnet Deterministic Networking WG Chitlada 1 SEC saag Security Area Open Meeting 1610-1810 Afternoon Session II Boromph. 3 INT *** 6tisch IPv6 over the TSCH mode of IEEE = 802.15.4e WG Chitlada 3 RTG rtgarea Routing Area Open Meeting Chitlada 1 SEC *** ace Authentication and Authorization for = Constrained Environments WG Boromph. 1/2 SEC acme Automated Certificate Management = Environment WG FRIDAY, November 9, 2018 Various ad-hoc meetings, please see https://trac.ietf.org/trac/ietf/meeting/wiki/103sidemeetings#FRIDAY Boromph. 4 -- 0900..1320 T2TRG work meeting Boromph. 3 -- 1000..1200 COIN (Computing in the Network) From nobody Fri Oct 19 11:59:54 2018 Return-Path: X-Original-To: suit@ietf.org Delivered-To: suit@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C0F6131060; Fri, 19 Oct 2018 11:56:31 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: "\"IETF Secretariat\"" To: , Cc: ekr@rtfm.com, suit@ietf.org X-Test-IDTracker: no X-IETF-IDTracker: 6.87.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <153997539130.6592.15888596805009183901.idtracker@ietfa.amsl.com> Date: Fri, 19 Oct 2018 11:56:31 -0700 Archived-At: Subject: [Suit] suit - Requested session has been scheduled for IETF 103 X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2018 18:56:39 -0000 Dear Russ Housley, The session(s) that you have requested have been scheduled. Below is the scheduled session information followed by the original request. suit Session 1 (2:00 requested) Thursday, 8 November 2018, Morning Session I 0900-1100 Room Name: Chitlada 2 size: 250 --------------------------------------------- iCalendar: https://datatracker.ietf.org/meeting/103/sessions/suit.ics Request Information: --------------------------------------------------------- Working Group Name: Software Updates for Internet of Things Area Name: Security Area Session Requester: Russ Housley Number of Sessions: 1 Length of Session(s): 2 Hours Number of Attendees: 100 Conflicts to Avoid: First Priority: ipwave lamps stir ipsecme tls sipbrandy curdle sacm mile teep core ace saag Second Priority: t2trg lwig 6lo cfrg acme perc cbor Third Priority: v6ops 6man intarea People who must be present: Russell Housley Eric Rescorla Dave Thaler Hannes Tschofenig David Waltermire Resources Requested: Special Requests: --------------------------------------------------------- From nobody Tue Oct 30 02:39:38 2018 Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0887912DD85 for ; Tue, 30 Oct 2018 02:39:37 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.902 X-Spam-Level: X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.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 VljxEOxdsp52 for ; Tue, 30 Oct 2018 02:39:34 -0700 (PDT) Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01on061f.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe1f::61f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F38D9128DFD for ; Tue, 30 Oct 2018 02:39:33 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector1-arm-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UvfriUuHYS5unTzivv6ZV9ve+fFcRY8JEYEY7z7s1C4=; b=gm8zbvZ30V//XRMDoMRBdXD0xHCLzsnW59rrwsCNoReLPvOyMThhCtDshSqnW3ojAEJ5tt7VzdE/T5kqQ7YkjhsYi7OxM1oap1lcnAFjWWraOecsdr537oMlw2fA7uOMLvR45/RfcbB0SG9w89LmXokLZY84dGXFdKRQIAOwt0k= Received: from DB6PR0801MB1879.eurprd08.prod.outlook.com (10.168.85.13) by DB6PR0801MB1877.eurprd08.prod.outlook.com (10.168.85.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1273.19; Tue, 30 Oct 2018 09:39:31 +0000 Received: from DB6PR0801MB1879.eurprd08.prod.outlook.com ([fe80::acf2:1e1b:193a:4971]) by DB6PR0801MB1879.eurprd08.prod.outlook.com ([fe80::acf2:1e1b:193a:4971%3]) with mapi id 15.20.1273.027; Tue, 30 Oct 2018 09:39:31 +0000 From: Brendan Moran To: suit CC: Hannes Tschofenig Thread-Topic: New draft-moran-suit-manifest-03 Thread-Index: AQHUcDR15fD1AvYt/0iI2fftlsy4fg== Date: Tue, 30 Oct 2018 09:39:31 +0000 Message-ID: <72B15CEC-9CB3-480D-A13D-0B8D6E106FDA@arm.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-mailer: Apple Mail (2.3445.9.1) authentication-results: spf=none (sender IP is ) smtp.mailfrom=Brendan.Moran@arm.com; x-originating-ip: [217.140.106.50] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1; DB6PR0801MB1877; 6:V3AKVxXfzysGANjO6/4eZ+5hd8Re79xkUQDqgl2+9vkgPBE6O6ig7L69R9KNJSK6DqjkQfvKbKVtSAKqtJCa5DS0iG4OHaKcleXsBgreMJVQaSRCllSbrJoDaZtzSFN6mIyfBoTCGEmN8RUlxYU+VE2AMXfnEDpEpAS9QAD2XlkrAbCAcy+tMRHuuyeTbltszF7qFiX3Pnz4Vmon8oyp4hGRhwObsfAGOScWGoVySHd8icChsxrKH34N0toS6SEnkhNzFXBjBy21BuKvOnshNOOz1KUCd+tQJrrw/6Xhnzun94y5I4NRSH0aVp8Zu6DxXzWqCCCEc7RpdL3df5ztkNNqqk/qtn6ERK6xGh9z3xRLRDSQfTXIKnaLSzwrk7G1NV8wZbCQfrp1qLx32CB9mIYg8YupZo8+2yDOo9BM/z86On9nmg/pypQ5cZkyPSv0wuC8nUAndems27hz4z1peQ==; 5:4JtARbq6GasXRWIsa7YMVe+sAT6aZ4661fIwN1DeOJsezP8Nx6NVPryB18lnxXa13UD6cA7iJebXDlxaeOzRjEGTa++k32Feq3sEL3gopNdHATg5B+0ewW9HGWes8xh/Y0T7L8e9G24sWdobCOOOUaNnTuHHGcP3AqFC9eXP0uY=; 7:tN+rOprcMU4am0bn4zXRvds/LdvvZEjzKScZYndk9Qdxkl6vn7pa1UYYe5HOAO3ZjYArA4z6u3ItsE0D7P4RHiz5WAuagYGmQBRDe1aVkOJKN0JX12kMWNmTiH/S/oMjzP1wQiSlFEe1PcPPzn8a4g== x-ms-exchange-antispam-srfa-diagnostics: SOS;SOR; x-ms-office365-filtering-correlation-id: 36df4192-f554-432a-727f-08d63e4b9840 x-ms-office365-filtering-ht: Tenant x-microsoft-antispam: BCL:0; PCL:0; RULEID:(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600074)(711020)(4618075)(2017052603328)(7153060)(7193020); SRVR:DB6PR0801MB1877; x-ms-traffictypediagnostic: DB6PR0801MB1877: x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:; x-ms-exchange-senderadcheck: 1 x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231382)(944501410)(52105095)(93006095)(93001095)(3002001)(10201501046)(6055026)(148016)(149066)(150057)(6041310)(20161123558120)(20161123560045)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(201708071742011)(7699051)(76991095); SRVR:DB6PR0801MB1877; BCL:0; PCL:0; RULEID:; SRVR:DB6PR0801MB1877; x-forefront-prvs: 08417837C5 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(39860400002)(366004)(346002)(136003)(376002)(396003)(40434004)(199004)(189003)(6116002)(57306001)(4326008)(478600001)(14454004)(72206003)(25786009)(14444005)(5024004)(966005)(82746002)(256004)(2900100001)(186003)(36756003)(2616005)(486006)(7736002)(305945005)(6506007)(6486002)(97736004)(476003)(8936002)(102836004)(99286004)(8676002)(81156014)(81166006)(6436002)(5660300001)(33656002)(26005)(53936002)(5250100002)(86362001)(66066001)(71200400001)(6306002)(106356001)(105586002)(6916009)(50226002)(83716004)(2906002)(6512007)(71190400001)(68736007)(3846002)(316002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:DB6PR0801MB1877; H:DB6PR0801MB1879.eurprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; received-spf: None (protection.outlook.com: arm.com does not designate permitted sender hosts) x-microsoft-antispam-message-info: x3ZEp5Dld85oYXOpLo5nI6Ro3q09lD9PNJtAf3I5/NsbIDw3LkETMiYRHOLanRYVgTLgYsjmyNr7CIFlPN9VCYKNs4ZAPM7sRvbxUMVY6+H+RvvrPH4uhxyyJ/DIhH5AC5gDXTk3JIfUwGcPh+cgqbde67zXZvHCWxb+/UEg/r8IXtAK4NJPC4ZuqObiXJdBvIztrGe+tkifGJogchNGkQSgm1C5hk9cmFQX8/JDFO9y4xsYfAIfr8Y6CJYvfRdJZjb47eh4DpbNW71wjUfygL8XeB9hjTbybWxfi1jiBZQ9R0Xtag2sJ32owmYLAGfwkAZhq6aQerFx9nywoXdyMU0HAVf2L1QkeYROKP9iIJo= spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: arm.com X-MS-Exchange-CrossTenant-Network-Message-Id: 36df4192-f554-432a-727f-08d63e4b9840 X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2018 09:39:31.6683 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: f34e5979-57d9-4aaa-ad4d-b122a662184d X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0801MB1877 Archived-At: Subject: [Suit] New draft-moran-suit-manifest-03 X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Oct 2018 09:39:37 -0000 My apologies for the delay in announcing this new draft, it was published M= onday last week. Summary of changes: * All sections are now fully described * Most structures are now CBOR Maps * New COSE_Digest structure is defined * Processors IDs are CBOR Lists * Processors are defined in a tree, not a graph. Encoding of the tree is fl= at, in a child-first order. * Examples are added IANA actions required: * New CBOR Tag for COSE_Digest_Tagged * New COSE Algorithm identifiers for digest algorithms Please see here for full details: https://tools.ietf.org/html/draft-moran-suit-manifest-03 Best Regards, Brendan IMPORTANT NOTICE: The contents of this email and any attachments are confid= ential and may also be privileged. If you are not the intended recipient, p= lease 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. From amyas.phillips@gmail.com Wed Oct 31 02:20:43 2018 Return-Path: X-Original-To: suit@ietfa.amsl.com Delivered-To: suit@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EEA9130E16 for ; Wed, 31 Oct 2018 02:20:43 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.4 X-Spam-Level: X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 i6_kzIEfFRjt for ; Wed, 31 Oct 2018 02:20:40 -0700 (PDT) Received: from mail-ed1-f48.google.com (mail-ed1-f48.google.com [209.85.208.48]) (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 EBB6312D4F1 for ; Wed, 31 Oct 2018 02:20:39 -0700 (PDT) Received: by mail-ed1-f48.google.com with SMTP id z12-v6so7194378edp.7 for ; Wed, 31 Oct 2018 02:20:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=6BXpLvRHEbmcF0PUXlqF+3H7RXnaDGbNLfzhVjwGqNA=; b=KaM4YgPRIBcqR84OJQ+UmUFi2WD3yCbIDxxPprMgYW897Fpv1lrscy3scDVQ9ockJw knSnPownTlraQXFaE7SpzBJEaLbq+y10HREO6Yw17xSG1kstCgfW/d2xq/6RYVpkgtvS GRzUaGASVPyPs+VRQPp30U/etnixlSmSMMWlkQh0yaumTBi6RoUvAltpQalIqm8jE5LW ZBFphQhDhoFmzGIFv7srn1EF9fBOZst9/r30Q3LkYqKspFeLx2IcFcSOHsuoKfOm15Yq BvU9Xz++S/K2kXRjlTPRwvtTlmkA+Rs1B9IHCU7IYGMYjpihM31FuiZLi/GWbmNrldef G8KA== X-Gm-Message-State: AGRZ1gLKVG5BSNdmbE7bI+KIriPxX44ISB6yAOv+9uAMKfp5U28tiVlc CDtmoniU3wz6eWPZ6rRzE5q6eU6KiLc= X-Google-Smtp-Source: AJdET5cGfwpOeKv0ZNJbaXLlJq/wHVlwUgdFlqh8VYt7ni00io6+attcnhbG2/jG7HkQ73ucD8xIpQ== X-Received: by 2002:a50:a7c1:: with SMTP id i59-v6mr1373413edc.296.1540977637998; Wed, 31 Oct 2018 02:20:37 -0700 (PDT) Received: from mail-wm1-f45.google.com (mail-wm1-f45.google.com. [209.85.128.45]) by smtp.gmail.com with ESMTPSA id b2-v6sm6739045edy.52.2018.10.31.02.20.37 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 31 Oct 2018 02:20:37 -0700 (PDT) Received: by mail-wm1-f45.google.com with SMTP id p2-v6so13763968wmc.2 for ; Wed, 31 Oct 2018 02:20:37 -0700 (PDT) X-Received: by 2002:a1c:1f8f:: with SMTP id f137-v6mr1667978wmf.64.1540977637132; Wed, 31 Oct 2018 02:20:37 -0700 (PDT) MIME-Version: 1.0 From: Amyas Phillips Date: Wed, 31 Oct 2018 09:20:27 +0000 X-Gmail-Original-Message-ID: Message-ID: To: suit@ietf.org Content-Type: multipart/alternative; boundary="000000000000ab1240057982d07b" Archived-At: Subject: [Suit] Devices with multiple updatable elements X-BeenThere: suit@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Software Updates for Internet of Things List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Oct 2018 09:23:09 -0000 --000000000000ab1240057982d07b Content-Type: text/plain; charset="UTF-8" Hi All I want to suggest modifications to draft-ietf-suit-information-model-01, sections: 3.3.1. Security Requirement MFSR1: Monotonic Sequence Numbers 4.10. Manifest Element: Storage Location , and 4.11. Manifest Element: Component Identifier Here are the current texts, to save you looking them up: 3.3.1. Security Requirement MFSR1: Monotonic Sequence Numbers Only an actor with firmware installation authority is permitted to decide when device firmware can be installed. To enforce this rule, manifests MUST contain monotonically increasing sequence numbers. Manifests MAY use UTC epoch timestamps to coordinate monotonically increasing sequence numbers across many actors in many locations. If UTC epoch timestamps are used, they MUST NOT be treated as times, they MUST be treated only as sequence numbers. Devices MUST reject manifests with sequence numbers smaller than any onboard sequence number. Note: This is not a firmware version. It is a manifest sequence number. A firmware version may be rolled back by creating a new manifest for the old firmware version with a later sequence number. Mitigates: Threat MFT1 Implemented by: Manifest Element: Monotonic Sequence Number 4.10. Manifest Element: Storage Location This element tells the device which component is being updated. The device can use this to establish which permissions are necessary and the physical location to use. This element is MANDATORY and MUST be present to enable devices to store payloads to the correct location. Implements: Security Requirement MFSR4b 4.10.1. Example 1: Two Storage Locations A device supports two components: an OS and an application. These components can be updated independently, expressing dependencies to ensure compatibility between the components. The firmware authority chooses two storage identifiers: - OS - APP 4.10.2. Example 2: File System A device supports a full filesystem. The firmware authority chooses to make the storage identifier the path at which to install the payload. The payload may be a tarball, in which case, it unpacks the tarball into the specified path. 4.10.3. Example 3: Flash Memory A device supports flash memory. The firmware authority chooses to make the storage identifier the offset where the image should be written. 4.11. Manifest Element: Component Identifier In a heterogeneous storage architecture, a storage identifier is insufficient to identify where and how to store a payload. To resolve this, a component identifier indicates which part of the storage architecture is targeted by the payload. In a homogeneous storage architecture, this element is unnecessary. This element is OPTIONAL and only necessary in heterogeneous storage architecture devices. Implements: MFUR3 Several examples are given in the documents of scenarios in which a single device has multiple updatable elements. draft-moran-suit-architecture discusses devices with multiple processors, and a device with an external updatable radio. draft-ietf-suit-information-model-01 in section 3.5.3. Usability Requirement MFUR3 discusses scenarios where peripheral devices need updating, and firmware modules are independently updatable. In section 4.10.1. Example 1: Two Storage Locations, the specific scenario of separately-maintained OS and APP is introduced. Other scenarios spring to mind, such as bootloaders and recovery images. Section 3.3.1 in draft-ietf-suit-information-model-01 introduces the idea that multiple uncoordinated actors may be creating manifests for the same device. This might happen if they are maintainers of firmware for different parts of the device's system. To prevent one actor's update of element A invalidating another's update of element B, unnecessarily and quite likely unpredictably, I propose that the requirement in section 3.3.1 for the manifest sequence number to increase monotonically be scoped to each updatable element. This is where I ought to sign off and request your consideration of my proposal. However, I have to request that you bear with me a little further, because draft-ietf-suit-information-model-01 is not completely clear about how to identify updatable elements. A device with multiple updatable elements will need to know what element is targeted by a manifest, so that it can invoke an appropriate handler. Section 4.10. Manifest Element: Storage Location says plainly "This element tells the device which component is being updated. The device can use this to establish which permissions are necessary and the physical location to use." This descends from security threat MFT5: The target device installs the payload to the wrong location. This parameter (aka storageIdentifier elsewhere in the document) would also serve very well in the three example scenarios in usability requirement MFUR3: multiple MCUs, separate code and configuration, and modular firmware. Instead of doing that the document in section 4.11 introduces a new parameter, Component Identifier. For the use cases and threats given, I suggest that Storage Location is sufficient. It can both identify a handler (e.g. file:) and if necessary provide a parameter to it (e.g. bin/fw/wifi). Component Identifier is redundant and should be removed. If Component Identifier is removed, then the concepts of HeSA and HoSA are also unnecessary to the specification and can also be removed. To recap then, I want to suggest two changes: 1. Scope the requirement in section 3.3.1 (for the manifest sequence number to increase monotonically) to each updatable element (i.e. to each Storage Location, if item 2 is also acceptable). This is to better support use cases involving multiple independent firmware maintainers. 2. Remove Component Identifier (4.11) from draft-ietf-suit-information-model-01. State instead that MFUR3 (3.5.3) is satisfied by manifest element Storage Location (4.10). Remove references to HeSA and HoSA from both documents. Generalise language and expand examples around use of Storage Location to clarify usage in use cases involving devices with multiple separately updatable components. Many thanks Amyas Phillips --000000000000ab1240057982d07b Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi All

I wa= nt to suggest modifications to draft-ietf-suit-information-model-01, sectio= ns:=C2=A0

3.3.1.=C2=A0 Security Requirement MFSR1:= Monotonic Sequence Numbers
4.10.=C2=A0 Manifest Element: Storage= Location , and=C2=A0
4.11. Manifest Element: Component Identifie= r

Here are the current texts, to save you looking = them up:



3.3.1.=C2= =A0 Security Requirement MFSR1: Monotonic Sequence Numbers

=C2=A0 =C2=A0Only an actor with firmware installation authority is= permitted to
=C2=A0 =C2=A0decide when device firmware can be ins= talled.=C2=A0 To enforce this rule,
=C2=A0 =C2=A0manifests MUST c= ontain monotonically increasing sequence numbers.
=C2=A0 =C2=A0Ma= nifests MAY use UTC epoch timestamps to coordinate monotonically
= =C2=A0 =C2=A0increasing sequence numbers across many actors in many locatio= ns.=C2=A0 If
=C2=A0 =C2=A0UTC epoch timestamps are used, they MUS= T NOT be treated as times,
=C2=A0 =C2=A0they MUST be treated only= as sequence numbers.=C2=A0 Devices MUST reject
=C2=A0 =C2=A0mani= fests with sequence numbers smaller than any onboard sequence
=C2= =A0 =C2=A0number.

=C2=A0 =C2=A0Note: This is not a= firmware version.=C2=A0 It is a manifest sequence
=C2=A0 =C2=A0n= umber.=C2=A0 A firmware version may be rolled back by creating a new
<= div>=C2=A0 =C2=A0manifest for the old firmware version with a later sequenc= e number.

=C2=A0 =C2=A0Mitigates: Threat MFT1

=C2=A0 =C2=A0Implemented by: Manifest Element: Monoton= ic Sequence Number



4= .10.=C2=A0 Manifest Element: Storage Location

=C2= =A0 =C2=A0This element tells the device which component is being updated.= =C2=A0 The
=C2=A0 =C2=A0device can use this to establish which pe= rmissions are necessary and
=C2=A0 =C2=A0the physical location to= use.

=C2=A0 =C2=A0This element is MANDATORY and M= UST be present to enable devices to
=C2=A0 =C2=A0store payloads t= o the correct location.

=C2=A0 =C2=A0Implements: S= ecurity Requirement MFSR4b

4.10.1.=C2=A0 Example 1= : Two Storage Locations

=C2=A0 =C2=A0A device supp= orts two components: an OS and an application.=C2=A0 These
=C2=A0= =C2=A0components can be updated independently, expressing dependencies to<= /div>
=C2=A0 =C2=A0ensure compatibility between the components.=C2=A0 T= he firmware authority
=C2=A0 =C2=A0chooses two storage identifier= s:
=C2=A0 =C2=A0-=C2=A0 OS
=C2=A0 =C2=A0-=C2=A0 APP

4.10.2.=C2=A0 Example 2: File System

=C2=A0 =C2=A0A device supports a full filesystem.=C2=A0 The firmwa= re authority chooses
=C2=A0 =C2=A0to make the storage identifier = the path at which to install the
=C2=A0 =C2=A0payload.=C2=A0 The = payload may be a tarball, in which case, it unpacks the
=C2=A0 = =C2=A0tarball into the specified path.

4.10.3.=C2= =A0 Example 3: Flash Memory

=C2=A0 =C2=A0A device = supports flash memory.=C2=A0 The firmware authority chooses to
= =C2=A0 =C2=A0make the storage identifier the offset where the image should = be
=C2=A0 =C2=A0written.


=
4.11.=C2=A0 Manifest Element: Component Identifier

=C2=A0 =C2=A0In a heterogeneous storage architecture, a sto= rage identifier is
=C2=A0 =C2=A0insufficient to identify where an= d how to store a payload.=C2=A0 To
=C2=A0 =C2=A0resolve this, a c= omponent identifier indicates which part of the
=C2=A0 =C2=A0stor= age architecture is targeted by the payload.=C2=A0 In a homogeneous
=C2=A0 =C2=A0storage architecture, this element is unnecessary.

=C2=A0 =C2=A0This element is OPTIONAL and only necessary i= n heterogeneous storage
=C2=A0 =C2=A0architecture devices.
<= div>
=C2=A0 =C2=A0Implements: MFUR3

=

Several examples are given in the documents o= f scenarios in which a single device has multiple updatable elements.=C2=A0= draft-moran-suit-architecture discusses devices with multiple processors, = and a device with an external updatable radio. draft-ietf-suit-information-= model-01 in section 3.5.3.=C2=A0 Usability Requirement MFUR3 discusses scen= arios where peripheral devices need updating, and firmware modules are inde= pendently updatable.=C2=A0 In section 4.10.1.=C2=A0 Example 1: Two Storage = Locations, the specific scenario of separately-maintained OS and APP is int= roduced.=C2=A0 Other scenarios spring to mind, such as bootloaders and reco= very images.=C2=A0=C2=A0

Section 3.3.1 in draft-ie= tf-suit-information-model-01 introduces the idea that multiple uncoordinate= d actors may be creating manifests for the same device. This might happen i= f they are maintainers of firmware for different parts of the device's = system.=C2=A0 =C2=A0=C2=A0

To prevent one actor= 9;s update of element A invalidating another's update of element B, unn= ecessarily and quite likely unpredictably, I propose that the requirement i= n section 3.3.1 for the manifest sequence number to increase monotonically = be scoped to each updatable element.



This is where I ought to sign off and request your conside= ration of my proposal.=C2=A0 However, I have to request that you bear with = me a little further, because draft-ietf-suit-information-model-01 is not co= mpletely clear about how to identify updatable elements.

A device with multiple updatable elements will need to know what ele= ment is targeted by a manifest, so that it can invoke an appropriate handle= r.=C2=A0 =C2=A0Section 4.10.=C2=A0 Manifest Element: Storage Location says = plainly "This element tells the device which component is being update= d.=C2=A0 The device can use this to establish which permissions are necessa= ry and the physical location to use."=C2=A0 This descends from securit= y threat MFT5: The target device installs the payload to the wrong location= .=C2=A0 This parameter (aka storageIdentifier elsewhere in the document) wo= uld also serve very well in the three example scenarios in usability requir= ement MFUR3: multiple MCUs, separate code and configuration, and modular fi= rmware.=C2=A0 Instead of doing that the document in section 4.11 introduces= a new parameter, Component Identifier.=C2=A0=C2=A0

For the use cases and threats given, I suggest that Storage Location is s= ufficient.=C2=A0 It can both identify a handler (e.g. file:) and if necessa= ry provide a parameter to it (e.g. bin/fw/wifi). Component Identifier is re= dundant and should be removed.=C2=A0 If Component Identifier is removed, th= en the concepts of HeSA and HoSA are also unnecessary to the specification = and can also be removed.=C2=A0=C2=A0



To recap then, I want to suggest two changes:
1. Scope the requirement in section 3.3.1 (for the manifest se= quence number to increase monotonically) to each updatable element (i.e. to= each Storage Location, if item 2 is also acceptable).=C2=A0 This is to bet= ter support use cases involving multiple independent firmware maintainers.<= /div>

2. Remove Component Identifier (4.11) from draft-i= etf-suit-information-model-01.=C2=A0 State instead that MFUR3 (3.5.3) is sa= tisfied by manifest element Storage Location (4.10).=C2=A0 =C2=A0Remove ref= erences to HeSA and HoSA from both documents.=C2=A0 Generalise language and= expand examples around use of Storage Location to clarify usage in use cas= es involving devices with multiple separately updatable components.=C2=A0



Many thanks

Amyas Phillips
--000000000000ab1240057982d07b--