Re: [secdir] secdir review of draft-ietf-tictoc-multi-path-synchronization-05

Ben Laurie <benl@google.com> Mon, 19 September 2016 11:00 UTC

Return-Path: <benl@google.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 2E08012B328 for <secdir@ietfa.amsl.com>; Mon, 19 Sep 2016 04:00:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.016
X-Spam-Level:
X-Spam-Status: No, score=-5.016 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_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 XtOV41KJPoaU for <secdir@ietfa.amsl.com>; Mon, 19 Sep 2016 04:00:43 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (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 E152112B13D for <secdir@ietf.org>; Mon, 19 Sep 2016 04:00:42 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id g192so141759517ywh.1 for <secdir@ietf.org>; Mon, 19 Sep 2016 04:00:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/sOzTenyBUw9euQjj9h7tAZr2PXO0z7w/EnAe7yXjsM=; b=bZ4eo9YaxS/u/ftDjfC4VRb9Tv2aUb5uQXeOrwD8TxlPyEMDqZLbaV8bcuVQbxJs27 Kz3XP2Yqe4XlRdlPELIzH1H6hpkcrxF6BtaCCgkAQJrk3ZkNm0q/QdJMV0t3TrXaZjbS ovM3gTKXhAhcSXzZ4JAK7kPyM2OKVyUGq7C8mTnnOzyGX7nJpD1BqEv9TDJfJH5kNsyU tg/zPHO3obf2lI64MQwzwrxVjT5bIucgRyWxJcuB4/ckXrV7QkpDa15uQ1mPS392Rjau Q3X85BvhrdXjFh+WJ0Ufxr4vs7/4pNwS1yIbPF8APngKfstXIcGuG0BKkIn7u4TNro// srkw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/sOzTenyBUw9euQjj9h7tAZr2PXO0z7w/EnAe7yXjsM=; b=OnvPRD+AqycGdMXFyhpOh9GVn9VbE0+FZbIj+jAzdM8R35XvWMMPfx9bCSrI99l8uX /sV28pZNdapdsfJ+5/CvgALOJ465x4/cNXmormQ3UzFfuVEsADsKaRoqx4MgR/lvbig6 v1VRJhCiR1qmxjFA+mWSaGCvGfY82LCzi1SjMUlZvYAlcxos1oqtjKz0SpWC/Xfa+3be ZOgpyHL8wg22+2ORx5Y6JCl2uNYxrAkL4i13IfpPsctubp+e2Ld322KkW3DMERwjZXwa RnNjHotBkSVhLgq8YcFKXaeeRXvDSiSvlB2T4whI1sRUudvVzRKI9STppSer7VeK6alE ZjOg==
X-Gm-Message-State: AE9vXwMLhmW915VFfqdRjqX9jELbBTAcKJ+XZ5mrcktLZKXosvBEop9IirtJyyKqRIgu2KfcpLuG9w5fFRO2OVkb
X-Received: by 10.13.231.199 with SMTP id q190mr26012626ywe.26.1474282841931; Mon, 19 Sep 2016 04:00:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.148.11 with HTTP; Mon, 19 Sep 2016 04:00:41 -0700 (PDT)
In-Reply-To: <3993e58a01f4472992ae6fcdfaa8e0f7@IL-EXCH01.marvell.com>
References: <CACsn0cmCGrpaHtiLNEpnN52_+FqM4XiCtUHhZm9XQD1qfbFH3w@mail.gmail.com> <2c34b139112a45ac9a68ff000aa7d934@IL-EXCH01.marvell.com> <CACsn0ckk0egkREuvfhwU6FJV5LBV4BPs5HsNoRk63yWjVdBB_g@mail.gmail.com> <3993e58a01f4472992ae6fcdfaa8e0f7@IL-EXCH01.marvell.com>
From: Ben Laurie <benl@google.com>
Date: Mon, 19 Sep 2016 12:00:41 +0100
Message-ID: <CABrd9STp-VgHoczmQfBoL-MKWFkJARt2Wj6JNpBWaanHf99mdA@mail.gmail.com>
To: Tal Mizrahi <talmi@marvell.com>
Content-Type: multipart/alternative; boundary="94eb2c08155217f89f053cda3903"
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/4xjlpSrRK-QmAYHlEBrQQXHi8B4>
Cc: "Karen ODonoghue (odonoghue@isoc.org)" <odonoghue@isoc.org>, "secdir@ietf.org" <secdir@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>, "draft-ietf-tictoc-multi-path-synchronization.all@tools.ietf.org" <draft-ietf-tictoc-multi-path-synchronization.all@tools.ietf.org>, "<iesg@ietf.org>" <iesg@ietf.org>
Subject: Re: [secdir] secdir review of draft-ietf-tictoc-multi-path-synchronization-05
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.17
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: Mon, 19 Sep 2016 11:00:47 -0000

On 19 September 2016 at 01:34, Tal Mizrahi <talmi@marvell.com> wrote:

> Time protocols have a pretty unique property: even if you use the
> strongest cryptographic mechanisms, the protocol can still easily be
> attacked by a man-in-the-middle who simply adds a constant delay to some of
> the packets, and thereby easily manipulates the protocol. The only way to
> mitigate delay attacks is by redundancy: multiple time sources and/or
> multiple network paths.


Surely not - challenge/response, for example, would also reveal a delay.