[secdir] Secdir review of draft-ietf-6lo-deadline-time-04

Charlie Kaufman <charliekaufman@outlook.com> Sat, 04 May 2019 01:18 UTC

Return-Path: <charliekaufman@outlook.com>
X-Original-To: secdir@ietfa.amsl.com
Delivered-To: secdir@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D3DE1202F7; Fri, 3 May 2019 18:18:33 -0700 (PDT)
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, FREEMAIL_FROM=0.001, 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 (2048-bit key) header.d=outlook.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 XKjjcWEuNGWT; Fri, 3 May 2019 18:18:31 -0700 (PDT)
Received: from NAM04-CO1-obe.outbound.protection.outlook.com (mail-oln040092010032.outbound.protection.outlook.com [40.92.10.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D6EF4120116; Fri, 3 May 2019 18:18:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Xrss5aYs9ENmkZJyrCKxnqqC53zAIA5bSoaXbKDnnjs=; b=K46RlXYAXxxTLHvVuWQHUyx7T59wkuaALANaMK3tSig9tQJTIUe34EL5ThqLlpBtR+xGQLXjXSk1i2Qe7nYzsCB0L2qw3jcE0uQdKCKuaGqTK/kvZ3biTnxrKlFQQBe6AfHgmgSf7Y/+gvDXMuX+XziPFtMOYZ+U5EPpfLdRJTPd+QKetYC8zdhy3VmRlC+YbhYWc0xkE9/yY0zCVn61mX/war5bcIcsbRaFX4NKh7dr+MUfnfs6phCf+H7CAUZK41P5H0/kD8qQ4C9i4NC3xf3NvT+3lrm+TljsHu0+2M93VzDumqbR+XXx1MuXJiGsVV+pgAzz939dutMfZIqpfA==
Received: from SN1NAM04FT037.eop-NAM04.prod.protection.outlook.com (10.152.88.51) by SN1NAM04HT048.eop-NAM04.prod.protection.outlook.com (10.152.89.42) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1835.13; Sat, 4 May 2019 01:18:29 +0000
Received: from MWHPR04MB0367.namprd04.prod.outlook.com (10.152.88.60) by SN1NAM04FT037.mail.protection.outlook.com (10.152.88.202) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.1835.13 via Frontend Transport; Sat, 4 May 2019 01:18:29 +0000
Received: from MWHPR04MB0367.namprd04.prod.outlook.com ([fe80::30f9:fd17:40d1:98f9]) by MWHPR04MB0367.namprd04.prod.outlook.com ([fe80::30f9:fd17:40d1:98f9%9]) with mapi id 15.20.1856.008; Sat, 4 May 2019 01:18:29 +0000
From: Charlie Kaufman <charliekaufman@outlook.com>
To: "secdir@ietf.org" <secdir@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "draft-ietf-6lo-deadline-time.all@ietf.org" <draft-ietf-6lo-deadline-time.all@ietf.org>
Thread-Topic: Secdir review of draft-ietf-6lo-deadline-time-04
Thread-Index: AQHVAhcw5kia49XGcEu0uXmSnWTn2g==
Date: Sat, 4 May 2019 01:18:29 +0000
Message-ID: <MWHPR04MB0367E2E63CE45D19F9215119DF360@MWHPR04MB0367.namprd04.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-incomingtopheadermarker: OriginalChecksum:EB25E3C71EA31E4D2021CC96FBC5F4BF0316F29E5F52A31194FE3A6CC1677713; UpperCasedChecksum:B5FDEA39E31CC2403413D834756A82CE075366D9B509D5788E2D5AB754222822; SizeAsReceived:6798; Count:40
x-tmn: [QnhHKsakoWxzVH3UnkTWztt4d9nl0zHtx/DYFBgfVkZwPoby3XLnRKRfW1FMVGtO]
x-ms-publictraffictype: Email
x-incomingheadercount: 40
x-eopattributedmessage: 0
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(5050001)(7020095)(20181119110)(201702061078)(5061506573)(5061507331)(1603103135)(2017031320274)(2017031323274)(2017031324274)(2017031322404)(1601125500)(1603101475)(1701031045); SRVR:SN1NAM04HT048;
x-ms-traffictypediagnostic: SN1NAM04HT048:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-message-info: oY+s7NUclezQK2ryXevdFw/xIyBYm6oNOi3rAEmCqXw64M9rNl+vDIlF6OYNI7GkYQpnIeGyVsjTNO7MqN0WejkP1n5FW6+r6IOeA4KyFdqaG0Xsc7JyXT+ETd/FK9jCGVSBvcCsS17EiwNnNhBcZgXO5uBHHUh1I+XSYqSHUOrPvdoThhC77p3fWXM8Pe0j
Content-Type: multipart/alternative; boundary="_000_MWHPR04MB0367E2E63CE45D19F9215119DF360MWHPR04MB0367namp_"
MIME-Version: 1.0
X-OriginatorOrg: outlook.com
X-MS-Exchange-CrossTenant-RMS-PersistedConsumerOrg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-Network-Message-Id: 0db42b88-ef73-41dd-f50e-08d6d02e6ac9
X-MS-Exchange-CrossTenant-rms-persistedconsumerorg: 00000000-0000-0000-0000-000000000000
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 May 2019 01:18:29.6996 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Internet
X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1NAM04HT048
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/c5c4LUNYucngnocw-VtuxmvVAI4>
Subject: [secdir] Secdir review of draft-ietf-6lo-deadline-time-04
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 04 May 2019 01:18:33 -0000

I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.

This document specifies a new optional header in the routing header of packets carried over LLNs (Low Power and Lossy Networks). This new header specifies a delivery deadline for packets, and the spec describes how a router is supposed to modify the field when the packet crosses between synchronized time domains.

There really aren't any security implications to a feature like this, though depending on how routers adjust their scheduling based on the values in this field, there might be opportunities for network nodes to mount more effective denial of service attacks or to get themselves better service than they might be entitled to. Since this document does not specify the scheduling algorithms, it's probably not appropriate for it to worry about possible weaknesses in those algorithms.

 --Charlie



Sent from Outlook<http://aka.ms/weboutlook>