Re: [tcpinc] Making ECDHE-Curve25519 the only MTI for tcpcrypt

Kyle Rose <> Tue, 17 October 2017 14:13 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 51A85132D51 for <>; Tue, 17 Oct 2017 07:13:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Status: No, score=-2.7 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, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pSZii7HKbhgv for <>; Tue, 17 Oct 2017 07:13:40 -0700 (PDT)
Received: from ( [IPv6:2607:f8b0:400d:c09::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 0879A13214D for <>; Tue, 17 Oct 2017 07:13:40 -0700 (PDT)
Received: by with SMTP id m189so2175271qke.4 for <>; Tue, 17 Oct 2017 07:13:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=veHiJZj3q4OZuv6kyJx4uFniwjlPGIhinVfsmvOic6Q=; b=ZvLO77MDiXzvf6Yq962TuBxWFdOG6UpW5DlRfqxbH7Mmewnfy63ucKHm2Agew/NkTD 9O3tvz8pSoCG7CWCyRepMh2BrxrlecexX8e2y2FI2mGUl7SZZYFMauWQgNnm5l4cYCxL x4oOkygOTEbnIDxEtJwNWif3AxBOkdpQOCFm0=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=veHiJZj3q4OZuv6kyJx4uFniwjlPGIhinVfsmvOic6Q=; b=kDlz0p5AIfN0e8YUZKYQV2GzTFNDFt5Ydi3v5Yr+W2HLhwf6aELtezy/f2ZeDsCjRD RRcbHGZxhLXvPgkcmruJTknhbJDAHUCYXygFHiDTz/IVsDMIYn+w86/ozPBn3ANtaiCe rM1RU8FV2OLHIJ1occxZTxHZXd1nY7kSf9F4qJ/FgLMMFNuUlEyhMY8evykSdSUZIbP2 JyTKJdoa0WAUY89AruUbnS1FTcN0FprXq8SmhBDLV6E5HlFID7yP2KXeLDmfmpdep+0u WJi9nKg4GLA+UVe10ZiVBCeSKIpkERCLlF3B6OiK/4hOExJziCc/7lg8chCA4/0wU00e SEPg==
X-Gm-Message-State: AMCzsaVhjcCMas6B9jB6KdmZ/tHU4jC07yg/ud3YBkb8vXGkSodAs5Uv eS35flBQFvKEXoxmCnyyBJKmIz6G4dh6BplzJBsncc79
X-Google-Smtp-Source: ABhQp+R5t5HIVXLnIsL0MFW4sUVA09EZN1HtkdnYe7Pdw1nF0Xf75pNJ21Dyf8Kc7OZoMjuvHf8Er3mvTwtwxLpL4q4=
X-Received: by with SMTP id 23mr19531940qku.78.1508249619030; Tue, 17 Oct 2017 07:13:39 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Tue, 17 Oct 2017 07:13:38 -0700 (PDT)
X-Originating-IP: [2607:fb90:ed7:a692:c523:1758:ece9:6bd9]
Received: by with HTTP; Tue, 17 Oct 2017 07:13:38 -0700 (PDT)
In-Reply-To: <>
References: <> <> <> <> <> <> <> <> <> <> <>
From: Kyle Rose <>
Date: Tue, 17 Oct 2017 10:13:38 -0400
Message-ID: <>
To: David Mazieres expires 2018-01-14 PST <>, "Mirja Kuehlewind (IETF)" <>, "Black, David" <>
Cc: ianG <>, Gregorio Guidi <>, tcpinc <>
Content-Type: multipart/alternative; boundary="001a1144cc04c682a6055bbebaba"
Archived-At: <>
Subject: Re: [tcpinc] Making ECDHE-Curve25519 the only MTI for tcpcrypt
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Working group mailing list for TCP Increased Security \(tcpinc\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 17 Oct 2017 14:13:42 -0000

On Oct 16, 2017 9:40 PM, "David Mazieres" <>

Question one is whether there's anyone in the working group who thinks
it would be a bad idea to make this change--i.e., to have a single MTI
algorithm, namely ECDHE-Curve25519.  If so, please speak up.

Speaking as interested party rather than chair, I was in favor of this
change over a year ago and remain in favor of it.

Question two, if no one object to this change and some people want to
see it, is whether it is now too late to make this change without
jeopardizing the RFC.  Can we still make such a change in last call?
It's obviously not a lot of text to change, but a fairly big semantic
change.  We'd appreciate guidance on this question from people with more
IETF experience.

Mirja and David Black: can you provide guidance here?