Re: [Detnet] DetNet Security Considerations Meetup at IETF 106 - Wed 15:20-16:50
"Grossman, Ethan A." <eagros@dolby.com> Wed, 20 November 2019 05:08 UTC
Return-Path: <eagros@dolby.com>
X-Original-To: detnet@ietfa.amsl.com
Delivered-To: detnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A37C12004F for <detnet@ietfa.amsl.com>; Tue, 19 Nov 2019 21:08:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dolby.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 9tTSnhOiZuYD for <detnet@ietfa.amsl.com>; Tue, 19 Nov 2019 21:08:01 -0800 (PST)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-eopbgr740138.outbound.protection.outlook.com [40.107.74.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D02C9120033 for <detnet@ietf.org>; Tue, 19 Nov 2019 21:08:00 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gWO2mdxkXXildUxRa72iqDhig1i4/Vd9GwZzIDTwR+HgULwIET9UhxfDu57A9SGSHI/sUjuUhUJuZ2+DcuU+cqO9NqEBr1s2BRCJiWqOelWWwo4IthBZ6J02f9hE5YWemG8FlY35MItKhZUyPKfYGc2o+JEPB/djVeEn7scy0qVCGFa2MFOX6FKNf6FSZbNk1yXJ4DWNbPF6rCTbNPcZ5U1NLJlZSpkwslHJBefJRG/06jNIy2vUqSy0paWm65eONeU8L0xeGhR07j9WH409K1Wv//LNVLkk6kyoIuAbnPqGXEzog2wumKDhN3MmnGPadNYtWEKLqzoDlVXiixSvVQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oho5H019EzKLhPkP3A4oGlhDqfdXp+CdMKBEp8FC5Kk=; b=hews1Pustn4b27dnbS494219lCZdWCMHQQtH6UpS8yEV9XfzNmU0PRqKTkaFPJvMZWxMmHDsERTlfbKf7xzJn3WneBVDUBARsDW/WVqKROKIGwxPI+Cj8Sgvz6JCgqN6pQZ9wOVbvS7XcHTXnqPFa6rSSvtGPKO0MOQIG602cDxlUs1l67LksUi08v3o0/Md84IlLagMfVDu/pg5ABw2HojalEOhoYJZ/wv3CoOysiUBiAs4OWJpfjsro+xAJ8dmJcBqvSQhit6RPoREvC2az77tkaqvLHQy6yO8+PKa1n1+Q5Y+4fWVbgeO1/pX6AmKeIXAUAx7JldZ0uxJG4UGNg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=dolby.com; dmarc=pass action=none header.from=dolby.com; dkim=pass header.d=dolby.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dolby.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oho5H019EzKLhPkP3A4oGlhDqfdXp+CdMKBEp8FC5Kk=; b=gDr/XUiCjyeBHJrZJNt6Yv7ROoAqteR2rdO67ecwzQye+krjy+iJHB8JcHdJ+DXkdjjhRTN7K/SRNgZlt4I0PxL5A6yh5mgPmcNqeC9Hd7W6YpGdojj+L3X/O3GqqhFVYZridcgr7z3LG/dZKb4LgNE+SuCLEYVT4A/DyWBiVdk=
Received: from BYAPR06MB4325.namprd06.prod.outlook.com (52.135.240.140) by BYAPR06MB4358.namprd06.prod.outlook.com (52.135.239.81) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.26; Wed, 20 Nov 2019 05:07:58 +0000
Received: from BYAPR06MB4325.namprd06.prod.outlook.com ([fe80::9089:e77d:8842:b8f0]) by BYAPR06MB4325.namprd06.prod.outlook.com ([fe80::9089:e77d:8842:b8f0%4]) with mapi id 15.20.2451.031; Wed, 20 Nov 2019 05:07:58 +0000
From: "Grossman, Ethan A." <eagros@dolby.com>
To: Tal Mizrahi <tal.mizrahi.phd@gmail.com>, "Black, David" <David.Black@dell.com>, Stewart Bryant <stewart.bryant@gmail.com>
CC: "detnet@ietf.org" <detnet@ietf.org>
Thread-Topic: DetNet Security Considerations Meetup at IETF 106 - Wed 15:20-16:50
Thread-Index: AdWY0mme7At/pOlFRtOAMBGnmRryAAE38KRgAGt+GsA=
Date: Wed, 20 Nov 2019 05:07:58 +0000
Message-ID: <BYAPR06MB4325A3A3446D841DA0E992E7C44F0@BYAPR06MB4325.namprd06.prod.outlook.com>
References: <BYAPR06MB432543E18E062A0B4B51179FC4740@BYAPR06MB4325.namprd06.prod.outlook.com> <BYAPR06MB432592D952920B8EAD3C58DFC44D0@BYAPR06MB4325.namprd06.prod.outlook.com>
In-Reply-To: <BYAPR06MB432592D952920B8EAD3C58DFC44D0@BYAPR06MB4325.namprd06.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5Lmh0bWwiIHA9ImM6XHVzZXJzXGVhZ3Jvc1xhcHBkYXRhXHJvYW1pbmdcMDlkODQ5YjYtMzJkMy00YTQwLTg1ZWUtNmI4NGJhMjllMzViXG1zZ3NcbXNnLWIyOWYyMGNjLTBiNTMtMTFlYS1iOTEwLTg0ZmRkMTNjZDRjZlxhbWUtdGVzdFxiMjlmMjBjZS0wYjUzLTExZWEtYjkxMC04NGZkZDEzY2Q0Y2Zib2R5Lmh0bWwiIHN6PSI2ODg1IiB0PSIxMzIxODcwMDA3NzMxODg2NTIiIGg9Imh4ZU05amMwWURqUks3TkxobjFxYnlWUjZwQT0iIGlkPSIiIGJsPSIwIiBibz0iMSIvPjwvbWV0YT4=
x-dg-rorf:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=eagros@dolby.com;
x-originating-ip: [203.127.152.4]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: eec22fbf-9dd5-417a-7d93-08d76d779c3d
x-ms-traffictypediagnostic: BYAPR06MB4358:
x-microsoft-antispam-prvs: <BYAPR06MB43582B350F3752B53942639DC44F0@BYAPR06MB4358.namprd06.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 02272225C5
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(136003)(366004)(396003)(39850400004)(199004)(189003)(86362001)(76176011)(6246003)(7696005)(236005)(4326008)(66946007)(2906002)(2420400007)(6116002)(486006)(71200400001)(11346002)(186003)(3846002)(790700001)(71190400001)(66476007)(66556008)(5660300002)(6306002)(316002)(54896002)(478600001)(74316002)(7110500001)(6506007)(53546011)(7736002)(66066001)(9686003)(55016002)(110136005)(6436002)(15650500001)(102836004)(66446008)(64756008)(8676002)(81156014)(81166006)(26005)(229853002)(476003)(446003)(33656002)(25786009)(66574012)(14454004)(99286004)(52536014)(8936002)(256004)(14444005)(76116006); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR06MB4358; H:BYAPR06MB4325.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: dolby.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: HA32h7Y0U03FnsIAu4BFyRzL9ACPiljTVvW7ryx4/WQh889kInIEnH32WaSY4mcxZbWPqd3Bwl0Eke7qYXvkQrqXNYqnIaAzL1dtMpSPRjRT1+G1ftGS1m/VFIhzZaXnLnTKjsvFWL7qDRwwMsNuETskSVzCKgg1/YP6I1qge5RKXtyNTCw25/aqOTli04oB0GZRDC8ZNIZZ0K2Y2VhO5uoeMv7zwEPD71zBUnekYumDqrhFRVfhIxo4hTUcevkr8T/wh9CR4YtULzOIbXRh/mvwthiPzpnfcPiAhZE3/KvS02imoGqN9QTrggrgp9qebBhz4t0BBggO/+vM0lnJEPeBot5Nfx59s8JDKYQgcnRB97aURyhHahupfnbYJHOeEaaWlQpezATnNvQWEYz2X3IUoHFw+Uz9ZoC4oRvSaYiy77bJNg1rEUFqflvKIjrq
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BYAPR06MB4325A3A3446D841DA0E992E7C44F0BYAPR06MB4325namp_"
MIME-Version: 1.0
X-OriginatorOrg: dolby.com
X-MS-Exchange-CrossTenant-Network-Message-Id: eec22fbf-9dd5-417a-7d93-08d76d779c3d
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Nov 2019 05:07:58.4056 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 05408d25-cd0d-40c8-8962-5462de64a318
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: OcRLalix0Z7e3mE0t2+wAbsa7tpF2ZipFC6aO0lMu+WK8TqhpTD4PIFV+OfGOcIlZFrYocf1YkfiRR2H4KaPpQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR06MB4358
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/tp_AoAB8nNlJZaIF4s18PvZcgFk>
Subject: Re: [Detnet] DetNet Security Considerations Meetup at IETF 106 - Wed 15:20-16:50
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Discussions on Deterministic Networking BoF and Proposed WG <detnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/detnet>, <mailto:detnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/detnet/>
List-Post: <mailto:detnet@ietf.org>
List-Help: <mailto:detnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/detnet>, <mailto:detnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Nov 2019 05:08:03 -0000
Reminder, we are meeting today at 3:20pm at IETF Reception desk... Thanks, Ethan. From: detnet <detnet-bounces@ietf.org> On Behalf Of Grossman, Ethan A. Sent: Monday, November 18, 2019 9:51 AM To: Tal Mizrahi <tal.mizrahi.phd@gmail.com>; Black, David <David.Black@dell.com>; Stewart Bryant <stewart.bryant@gmail.com> Cc: detnet@ietf.org Subject: Re: [Detnet] DetNet Security Considerations Meetup at IETF 106 - Wed 15:20-16:50 As of today there are four of us, so the plan is to meet at the IETF Registration desk Wed at 15:20 and find a place to sit, ad hoc. If anyone else cares to join us, please do. Thanks, Ethan. From: Grossman, Ethan A. <eagros@dolby.com<mailto:eagros@dolby.com>> Sent: Tuesday, November 12, 2019 5:25 AM To: detnet@ietf.org<mailto:detnet@ietf.org>; draft-ietf-detnet-security@ietf.org<mailto:draft-ietf-detnet-security@ietf.org> Cc: Alissa Cooper <alissa@cooperw.in<mailto:alissa@cooperw.in>>; kaduk@mit.edu<mailto:kaduk@mit.edu>; Alvaro Retana <aretana.ietf@gmail.com<mailto:aretana.ietf@gmail.com>>; Mirja Kühlewind <ietf@kuehlewind..net<mailto:ietf@kuehlewind..net>>; rt-dt-security@ietf.org<mailto:rt-dt-security@ietf.org>; Tero Kivinen <kivinen@iki.fi<mailto:kivinen@iki.fi>>; Kathleen Moriarty <kathleen.moriarty.ietf@gmail.com<mailto:kathleen.moriarty.ietf@gmail.com>>; Tal Mizrahi <tal.mizrahi.phd@gmail.com<mailto:tal.mizrahi.phd@gmail.com>>; Black, David <David.Black@dell.com<mailto:David.Black@dell.com>>; Deborah Brungard <db3546@att.com<mailto:db3546@att.com>> Subject: DetNet Security Considerations Meetup at IETF 106 - Wed 15:20-16:50 To: "DetNet Security Considerations" potentially interested parties From: Ethan (as DetNet Security Considerations draft editor) We are now driving towards completion of the DetNet Security Considerations draft, particularly since the DetNet data plane drafts refer to it, and we have now completed WG LC on 5 of those data plane drafts. Towards this end we will have a slot for a DetNet Security discussion at the DetNet session, and also in advance of the session a side meeting to bring together ideas from any interested parties, such as yourself. >From my point of view, the key DetNet Security question currently is "Are there any considerations that are both DetNet-specific (i.e. specific to time-sensitive networks) and DetNet-technology-specific (IP, MPLS, TSN)?". At this point the draft has "placeholder" sections to address that question, which basically say "there are none". Are we comfortable publishing the draft with that stance? We have established a time for the discussion, which is to overlap Wednesday Afternoon session II: 15:20-16:50 Wednesday Afternoon (in other words Session II --> Overlapped by DetNet Security Considerations Side Meeting). The location has not been established - if you have even the slightest inkling that you may want to attend this side meeting, please send me an email to that effect, and once we have the location set, I will let y'all know. And of course if you have comments you are encouraged to send them to the list. Thanks, Ethan.
- [Detnet] DetNet Security Considerations Meetup at… Grossman, Ethan A.
- Re: [Detnet] DetNet Security Considerations Meetu… Grossman, Ethan A.
- Re: [Detnet] DetNet Security Considerations Meetu… Grossman, Ethan A.