Re: Consensus Calls for Transport/TLS issues, post-Cupertino

Jana Iyengar <jri.ietf@gmail.com> Tue, 22 October 2019 07:51 UTC

Return-Path: <jri.ietf@gmail.com>
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 C39AB1200B5 for <quic@ietfa.amsl.com>; Tue, 22 Oct 2019 00:51:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 XvIE2pl_Yy4p for <quic@ietfa.amsl.com>; Tue, 22 Oct 2019 00:51:06 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 34A0312002F for <quic@ietf.org>; Tue, 22 Oct 2019 00:51:06 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id 21so3306346lft.10 for <quic@ietf.org>; Tue, 22 Oct 2019 00:51:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=8qQU6OlfWNtjADIZomuL0Tn/A19rwZrrb6jxn3oL1HE=; b=XEDklC6ZyzGUjO27f2z2ie9GEbReZoxX/gFjubfv+2Wl5Sfj0IVOYopuTlY3zbJ9jl wBIbwnW2ziTfKpL9IhcBbU2nwysw1pVCUnjllIjBCXd602jLknDiglsCQ70Ooh2H3JN6 YZGAQV/fsN/8b2vVnpB84BqBq3CNRS2L++6E2aOA743rNYGwNkQhsgef0cUwyyWLEOVw HZr9H3zn9GuAm1ZoQQX4JWbbpdw6a1UpsBVRuX984kZ3YT315Y3GWpO9dfBucdbxWHtL N3nsXuCPOybb5t1AjnhXH6fAMylp0kujp3hcpYHvEVT2NFpWp6MaNwxlhP5ypDBMs2aE suPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=8qQU6OlfWNtjADIZomuL0Tn/A19rwZrrb6jxn3oL1HE=; b=uI29f9Bri6gAtX9E1yFWIHCUb3RTdMOhT6J+RPQcquOyhObDyiaqvVC5V5TUW9pWFS WHiHh/CdTcI28OK57Kvt+n/7+lOhznsHPRMRjlwRtgBPTgVxQnOuf7t3K3o/JUs2Z8z3 rKKTRmYzVjVm/IJjE5Gb2aDQdvOOrys0XzIipB705PlVtKF2ryXOAGarQjBASJXLUr1o nSHbZPzkvVEVe1POJlcRaFMy0W4khyJWfkduQ2BebD0U9oibTY1A1+A4EZQNvcSeSHMP lpKfPWJPOR9o0yU5fKu3iEGX+KQLtwQrnn2bk66bJrCPYufOxoaw85TSyVkexzKxx2zS 2StQ==
X-Gm-Message-State: APjAAAX4hqDFUe86pxOg/ZVuQrit6roqtyhLePdwh8QUKZCGNoNQgVQR eQW+6DUziT66FjfCXTliKdcWCZ3dCkPxJoItojI=
X-Google-Smtp-Source: APXvYqzMd/+6NK7aqt3mD65IJPonRPZRxQPLxYo8ldnIBThm+YXAXLGx9xqjRlWcSTiG2ajVCqv40FhjJBX0XQC1MWY=
X-Received: by 2002:ac2:4142:: with SMTP id c2mr17663483lfi.47.1571730664140; Tue, 22 Oct 2019 00:51:04 -0700 (PDT)
MIME-Version: 1.0
References: <4D6397AF-B411-4E67-AFD2-76E8F2AD462C@mnot.net> <CANatvzwYA-NN+p5jLu4vpgKY_G-ZoUM03CacZWS2FAPyPqgiiw@mail.gmail.com> <BN3PR00MB0083E9A10A58F4CCC7B8A5C6B3680@BN3PR00MB0083.namprd00.prod.outlook.com> <22517ab5-9a6c-4486-b7ea-03badc064cbe@www.fastmail.com> <CANatvzx=RWB1Bio7tqX7nN_Vn1SfSaE69LZbuiU5pWeXP=BwNQ@mail.gmail.com> <DB6PR10MB176678E88FF226C2EB8FF78EAC680@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
In-Reply-To: <DB6PR10MB176678E88FF226C2EB8FF78EAC680@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 22 Oct 2019 16:50:53 +0900
Message-ID: <CACpbDccOe01VBjwwy=mdSi5nync8bXa506OMTbLPpBH-hoj4Sw@mail.gmail.com>
Subject: Re: Consensus Calls for Transport/TLS issues, post-Cupertino
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
Cc: Kazuho Oku <kazuhooku@gmail.com>, Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000eb35b505957b0fd7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ztR2PP7lvcps1IUCk3g4rFgeq28>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Oct 2019 07:51:09 -0000

I agree with Kazuho here. The issue of migration was not one we had
considered. I was going through this with Kazuho, and we may have
identified yet another issue with handshake retransmissions and migration,
which is present in the current spec.

Sadly, I don't think we can call this issue done.

On Tue, Oct 22, 2019 at 2:14 PM Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>
wrote:

> Without a way to move to a single PN space I find this a deal breaker. I
> might do a custom version of the protocol.
>
>
> ------------------------------
> *Fra:* QUIC <quic-bounces@ietf.org> på vegne af Kazuho Oku <
> kazuhooku@gmail.com>
> *Sendt:* tirsdag, oktober 22, 2019 6:58 AM
> *Til:* Martin Thomson
> *Cc:* IETF QUIC WG
> *Emne:* Re: Consensus Calls for Transport/TLS issues, post-Cupertino
>
>
>
> 2019年10月22日(火) 11:38 Martin Thomson <mt@lowentropy.net>:
>
>> On Tue, Oct 22, 2019, at 12:39, Nick Banks wrote:
>> >  I'd also prefer to fix the problem, even if it means bringing back
>> > something like RETIRE_KEY.
>>
>> I would prefer to think of this proposed resolution as a temporary one.
>> I don't think that we agreed to keep the handshake keys indefinitely, only
>> that we would use that option as a fallback position until we found a
>> better solution.
>>
>
> I might point out that #3121 is not proposal-ready as a way to resolve
> #2863. That is because it does not define how to send and receive Handshake
> packets until or after migration happens. There would be a deadlock unless
> both endpoints agree on how that should be done (e.g., how to select SCID,
> whether the path used for Handshake packets migrates too).
>
> Without that being clarified, can we say that we are ready for a
> consensus call?
>
>
>>
>> On that basis, I think that it would be best if we open a new issue that
>> says "Handshake keys can't ever be dropped".
>>
>> We might still conclude not to address that issue, but the important
>> thing is to ensure that any solution works properly.
>>
>>
>
> --
> Kazuho Oku
>