Re: [Detnet] DetNet Security Team plan

"Grossman, Ethan A." <eagros@dolby.com> Fri, 31 March 2017 15:18 UTC

Return-Path: <prvs=726356c735=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 BBA271294EF for <detnet@ietfa.amsl.com>; Fri, 31 Mar 2017 08:18:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.619
X-Spam-Level:
X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, 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 qgYnNvXeoyr8 for <detnet@ietfa.amsl.com>; Fri, 31 Mar 2017 08:18:37 -0700 (PDT)
Received: from mx0a-000fd501.pphosted.com (mx0b-000fd501.pphosted.com [67.231.152.235]) (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 70C78129417 for <detnet@ietf.org>; Fri, 31 Mar 2017 08:18:37 -0700 (PDT)
Received: from pps.filterd (m0000695.ppops.net [127.0.0.1]) by mx0b-000fd501.pphosted.com (8.16.0.20/8.16.0.20) with SMTP id v2VFITUM021019 for <detnet@ietf.org>; Fri, 31 Mar 2017 08:18:34 -0700
Received: from dlb-xchpw04.dolby.net (dcd-outbound.dolby.com [67.216.187.124]) by mx0b-000fd501.pphosted.com with ESMTP id 29g5rmj06p-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <detnet@ietf.org>; Fri, 31 Mar 2017 08:18:34 -0700
Received: from DLB-XCHPW03.dolby.net (10.233.7.3) by DLB-XCHPW04.dolby.net (10.233.7.4) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 31 Mar 2017 08:18:32 -0700
Received: from DLB-XCHPW03.dolby.net ([10.103.9.186]) by DLB-XCHPW03.dolby.net ([10.103.9.186]) with mapi id 15.00.1210.000; Fri, 31 Mar 2017 08:18:33 -0700
From: "Grossman, Ethan A." <eagros@dolby.com>
To: "detnet@ietf.org" <detnet@ietf.org>
Thread-Topic: DetNet Security Team plan
Thread-Index: AQHSqXDgoJghTCId7EisDdvs2H3uVaGtzi4g
Date: Fri, 31 Mar 2017 15:18:33 +0000
Message-ID: <f27572490cb1445f8686a58757d23184@DLB-XCHPW03.dolby.net>
References: <D5029959.E8F5%ethan.grossman@dolby.com>
In-Reply-To: <D5029959.E8F5%ethan.grossman@dolby.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.207.133.62]
Content-Type: multipart/alternative; boundary="_000_f27572490cb1445f8686a58757d23184DLBXCHPW03dolbynet_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-31_13:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/detnet/P05jjk36lst9IWfw4XJo1AZp9g4>
Subject: Re: [Detnet] DetNet Security Team plan
X-BeenThere: detnet@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 31 Mar 2017 15:18:40 -0000

Update: I attended the SAAG meeting and spoke with Kathleen Moriarty who was directing the session, and had a few hallway conversations afterwards (Carsten, Subir, Tal, Deborah). The resulting plan for connecting with SAAG is to send an email to the SAAG group with a pointer to our draft, requesting their input on it, and preferably providing us a "security expert" or two who would be "assigned to our case". However, we concluded that the timing of that email, to get the best effect, should wait until our security draft is more mature, i.e.

1)      It is adopted by the workgroup

2)      It includes concrete mitigation statements for review

3)      It specifies the technologies in use, e.g. based on our approved data plane design

4)      It passes the "review for security" process that is expected by SAAG (Deborah to send Ethan the links to the required info on this)
This is the plan of record. We considered that it might be good to have expert eyes on it sooner rather than later, but decided in favor of the above approach. If anyone else has comments, please chime it.
Thanks,
Ethan.

From: Grossman, Ethan A.
Sent: Thursday, March 30, 2017 11:16 AM
To: detnet@ietf.org
Subject: DetNet Security Team plan

Hi Folks,
Given the positive reception to our DetNet Security draft at the DetNet session, we (the informal DetNet Security Design Team) plan to continue this work, the next steps being:

  1.  Get more IETF security experts involved
  2.  Continue the draft with the next proposed section on Threat Mitigation
Regarding item 1 above, Tal and I plan to attend the SAAG meeting this afternoon (room Zurich D, at 15:20) and see if we can raise awareness there. If anyone else wants to meet us there to discuss further, please join us.

Regarding item 2, If you are interested in contributing please let me know and I'll put you on our informal email cc list.

Thanks,
Ethan.