Re: [multipathtcp] Replacing SHA-1 with SHA-256

Alan Ford <alan.ford@gmail.com> Thu, 16 March 2017 07:57 UTC

Return-Path: <alan.ford@gmail.com>
X-Original-To: multipathtcp@ietfa.amsl.com
Delivered-To: multipathtcp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0865B126C23 for <multipathtcp@ietfa.amsl.com>; Thu, 16 Mar 2017 00:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 X8PQ4Tlr4YcI for <multipathtcp@ietfa.amsl.com>; Thu, 16 Mar 2017 00:57:56 -0700 (PDT)
Received: from mail-wm0-x241.google.com (mail-wm0-x241.google.com [IPv6:2a00:1450:400c:c09::241]) (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 61D6C1250B8 for <multipathtcp@ietf.org>; Thu, 16 Mar 2017 00:57:56 -0700 (PDT)
Received: by mail-wm0-x241.google.com with SMTP id z133so1420736wmb.2 for <multipathtcp@ietf.org>; Thu, 16 Mar 2017 00:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vnUm6VUEBS/k+qeFBNZT1EWJxemQU4Cvo8EW49Lo5rQ=; b=QZj1rwkHABLOcJxAFTx8f1Jv3Dg2E9sl0cWDcbq1Z0Dzp7biRX+mE/X1ohwq5qdSXw R+Cs+YxYhSHvcWDcoLFXS+tBRCn3VzNsaw8kG9iqGs6crKgV+LQd2fj34IQTZ5Dv2GdX MF69hIu74ctQ3TwctZA9tQr3YfRN8q3utOeyLE86Mg4wvjysooRwdhJoiaE+lPHmUPvx mp8CeLTtSy+lgYyaGkbqe29b/bvjwNR/l+cokqaNAcgly/sZdbtBiI2obEZB+W02HyO3 +T1v6upzWjmBvP+aTywhkAnVFxGeFJhYZsC+4p1udOTPJv5/fnjEzYNIfO1MWqS3ttr0 pc8g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=vnUm6VUEBS/k+qeFBNZT1EWJxemQU4Cvo8EW49Lo5rQ=; b=e+wOaX2xMy4SD1EOn1ZEyljHnEX1oUZLHR30sQc1jkw3UCRI1CZpTKL8M09MBOmSA2 emVmPPtBzjiVX2ur5Xgz598RQtwyBmb7hjQF6bcbFl9234JLo+lwPxVQrEYZ9tjDMv9N ACxzj8Uwq4gxQGY8Rolv5yf040VIc0i60FlMrseK4Th/y87J5FiCFAP9WvE0iILRgqax DdMAB0zxPzevzXWWaTA4/n2EaXpRHGlUkW2JQUZTAGin0rmG7yPt//D4LLQnukpUn7wm mg3QC7YAQBMtIJY1BOyNIV+punpJuY0fOyvvK0juHLzc6y7Qb6jyiqtl7LKN/LGU9V5e nCOA==
X-Gm-Message-State: AFeK/H0D7NBm61zWq3WVTLOsme5eqp/CmMRT3r9Oe5niBx5m5nCQNj5dZrjlxSL2VSdsKA==
X-Received: by 10.28.170.206 with SMTP id t197mr4241188wme.61.1489651074969; Thu, 16 Mar 2017 00:57:54 -0700 (PDT)
Received: from alans-mbp.lan (152.52.159.143.dyn.plus.net. [143.159.52.152]) by smtp.gmail.com with ESMTPSA id w207sm3258559wmw.29.2017.03.16.00.57.54 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 16 Mar 2017 00:57:54 -0700 (PDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alan Ford <alan.ford@gmail.com>
In-Reply-To: <662A6FEA-0514-412E-AFA3-B1F4754FB218@apple.com>
Date: Thu, 16 Mar 2017 07:57:53 +0000
Cc: Olivier.Bonaventure@uclouvain.be, multipathtcp@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <5819DE4E-545E-4E65-A2CF-08125DC322A8@gmail.com>
References: <5254457A-9922-4E02-8A60-18E712A3EE5D@gmail.com> <ED4CCFD3-35DB-4EE5-B4C0-6F80D590580C@apple.com> <d7923793-51de-a214-5cbc-b610ca79ac2f@uclouvain.be> <662A6FEA-0514-412E-AFA3-B1F4754FB218@apple.com>
To: Greg Greenway <ggreenway@apple.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/multipathtcp/d63Ot8r7zJOAoIOS-kMBfOIaszI>
Subject: Re: [multipathtcp] Replacing SHA-1 with SHA-256
X-BeenThere: multipathtcp@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-path extensions for TCP <multipathtcp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/multipathtcp/>
List-Post: <mailto:multipathtcp@ietf.org>
List-Help: <mailto:multipathtcp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multipathtcp>, <mailto:multipathtcp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Mar 2017 07:57:58 -0000

> On 15 Mar 2017, at 23:09, Greg Greenway <ggreenway@apple.com> wrote:
> 
> 
>> On Mar 15, 2017, at 3:17 PM, Olivier Bonaventure <olivier.bonaventure@uclouvain.be> wrote:
>> 
>> On 15/03/17 22:31, Greg Greenway wrote:
>>> Would this change also set a different bit in the MP_CAPABLE option for
>>> crypto algorithm negotiation (eg set bit G for SHA-256, instead of the
>>> current bit H for SHA-1)?
>> 
>> 
>> No, this idea is that SHA-256 would apply to RFC6824bis, i.e. the standard track version of MPTCP while SHA-1 applies to RFC6824
> 
> Ok, but this will use MPTCP protocol version 1, whereas anything using SHA-1 will use protocol version 0, correct?  If that's the case, I have no objections.

Thanks Greg, that’s exactly what we mean. The diff would literally be s/SHA-1/SHA-256/g (subject to any security area further recommendations).

Best regards,
Alan