IETF Logo Mail Archive

Re: New Version Notification for draft-huitema-quic-mpath-req-00.txt

Christian Huitema <huitema@huitema.net> Tue, 02 January 2018 04:32 UTC

Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E40DD126C89 for <quic@ietfa.amsl.com>; Mon, 1 Jan 2018 20:32:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 Wd7MMxAxNsX4 for <quic@ietfa.amsl.com>; Mon, 1 Jan 2018 20:32:15 -0800 (PST)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 4B8BD12025C for <quic@ietf.org>; Mon, 1 Jan 2018 20:32:15 -0800 (PST)
Received: from xsmtp05.mail2web.com ([168.144.250.245]) by mx43.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1eWEFJ-0002oS-9g for quic@ietf.org; Tue, 02 Jan 2018 05:32:13 +0100
Received: from [10.5.2.13] (helo=xmail03.myhosting.com) by xsmtp05.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1eWEFG-0004jl-ED for quic@ietf.org; Mon, 01 Jan 2018 23:32:11 -0500
Received: (qmail 4790 invoked from network); 2 Jan 2018 04:32:09 -0000
Received: from unknown (HELO [192.168.1.105]) (Authenticated-user:_huitema@huitema.net@[172.56.42.40]) (envelope-sender <huitema@huitema.net>) by xmail03.myhosting.com (qmail-ldap-1.03) with ESMTPA for <martin.thomson@gmail.com>; 2 Jan 2018 04:32:09 -0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (15C153)
In-Reply-To: <CABkgnnXRfNG25U-wF4L16t7pfxsxoJknPa9zjKv03hNv7YLcdA@mail.gmail.com>
Date: Mon, 01 Jan 2018 20:32:07 -0800
Cc: "quic@ietf.org" <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BC82026-2A30-4A31-87F1-6FBB694C9FAE@huitema.net>
References: <151440883747.29897.3176327891691875461.idtracker@ietfa.amsl.com> <1728cfeb-e2ce-61cd-9a4e-770d76816fff@huitema.net> <CABkgnnXRfNG25U-wF4L16t7pfxsxoJknPa9zjKv03hNv7YLcdA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Subject: Re: New Version Notification for draft-huitema-quic-mpath-req-00.txt
X-Originating-IP: 168.144.250.245
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.13)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5sjEOoY7Jr9ODtX/46hJh38Xv9krsgRhBn0ayn6qsUc7A2kcKDr1fzRm ksYYe0sWHrgNzB/4Jkrw1eDLcif59fsLVxTk0IBx13yeFhiYOi5NB98yDTitFWvbHwz9vKZpmxBf ggn8Frespz1KxArpwUw8uEFOG92DI83j3LMNDNEdZsQEbaxxISMHgJxrdMdSS4B6hVJPXxgisa+g wkHvC+PVG1YjIrFRKhESMT/tU1Dx+IHaAZrg1ulFniksjLYqZxdG5bOwa1rOgT+89+/XFrGt2tce crpXRY6fm8RXptyzavERpop5LF7RavHozgbn9XzprFRbpFQTOcEGeQOY3IcDlgJpEbxunV7tCPNi PQvHQpVRoYcix47lJTuKsG8TgnDHFRDF834rtLc6Wv9Yj+vBPX9bzGJi0ycLbiOUDEySIK/1NH5T HMtlYvyHAYGOGheVSH7cGoIH3Vd41lbD31XsxRC3Cl5agFgis4e3pTrPzFy2BMVafZkKGCe45ASM DbvPZ2MU0aggZCbOzDKduscHmFDqewO9xyOqCYO8P1aHuJ+q0VAdWduuFNAGSPDW/D0UF36LWvas gj4e2T8BuA1dHghQC//pO9KiygTP+bGFirtlAtdsrBTAcAoY5WeLmsibYT4C2qF2lnc18bVJn65v jRxjDQ3TvE7lS2eoKehjsGSPZLRpX8VZnBFOnZ4xjTwJWw42swm4bO6gacpMpzLdQBUMkAI/PGrN 0+wWmMSTvLpZVaBCgo9IFgw1OrNwYFjI1dRH6f16eQCtvwPkeoxzBkc1CTpvaEJjkrbHF6v+l1Fr MVSE/J/ewUnTj7YP55q9INbyRwqQyVkoHpS/jX2RVYKU9W9tbmVXJBqdHHDm8ZIH36IzEI956ubs TR4WHrFV5oTvAcwA4rM3FkfW8/2B3o0d/ygg1mkxyifBss2L
X-Report-Abuse-To: spam@quarantine5.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lkZnhMP2euRpV7Ek8RzZUH5ITv8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Jan 2018 04:32:17 -0000

 
> On Jan 1, 2018, at 2:33 PM, Martin Thomson <martin.thomson@gmail.com> wrote:
> 
> ...
> 
> I don't think that the section on flow control makes any sense, since flow control operates at your stream layer.

Actually, flow control in TCP is used both as an application layer tool, e.g. don't send faster than the printer can print, and as a transport level tool to limit the speed at which the peer can send. If we just look at the application level, then of course this is purely a stream layer issue. But if we consider the transport function, then it makes sense to tie it to a path. 


> 
> I'm going to have to think on it some more, but your suggestion in 4.7 might be a good idea.  We don't have to do that now, though we might choose to do so if we can work through the design and implications.

Either separate encryption keys for separate connection ID, or mix IV with connection ID and sequence number for the nonce. The latter might work better, because it does not require keeping the master secret around. But it leaks one bit for correlation if the phase bit changes at the same time on all paths after a key rotation.

-- Christian Huitema

v2.23.0 | Report a Bug | By Email