Re: Proposal: Run QUIC over DTLS

Ted Hardie <ted.ietf@gmail.com> Tue, 13 March 2018 23:03 UTC

Return-Path: <ted.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 2CD6512D86C for <quic@ietfa.amsl.com>; Tue, 13 Mar 2018 16:03:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_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 rOTGu8KuzWur for <quic@ietfa.amsl.com>; Tue, 13 Mar 2018 16:03:43 -0700 (PDT)
Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::236]) (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 869D9126DFB for <quic@ietf.org>; Tue, 13 Mar 2018 16:03:43 -0700 (PDT)
Received: by mail-ot0-x236.google.com with SMTP id l5-v6so1381318otf.9 for <quic@ietf.org>; Tue, 13 Mar 2018 16:03:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=t3sjMhzgKd7PeHPUZPvbvQqJO5Y50GKSwn5QAOeQZ1Q=; b=RDwBu65MKWDiwaudWBuEGBjxFFMfObkox0dod5XV4ZOiiyPZAymzs0oRxMy+RpNFnf pV3EhuxU1tvdxi6+fRuRbkwrdNME+OnSK+/nnvJ/dLGRQSQyjsSTM0TSlEmGQ03HOlWD 3GnLTzhtPdkk6M2lhKjTWNINAMn6h/U86sXOZnsP/g/7pLhmqG0FkaW96iM+8bmJF2TP 10XTyrIpefnLvqQyNZmJISbtQvd6OA9iBksCneR1JdYVYXhlHSItnskcFfZp6VLKeHXZ ZhXOmmEIOm445LaBaB4ZY59q/mMO6oBKbpayleHONFOD5iVBq0NQr65Y3e97/SjuPPl+ uIbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=t3sjMhzgKd7PeHPUZPvbvQqJO5Y50GKSwn5QAOeQZ1Q=; b=H1TgUdc56m8LPczyzlf3R2jbLnq3OFxCrdM+E7lcXe9AdQPoYnlTq9BIVa2DuIQBBC FNv1RWAibu5eKfF/ZdKelqCETbA0xFTK5dhZkq+oSqJcSeIJbKLweaCl0SJ6lAXhENe1 msx7Zsawl1gjq3jfsYpMIL/3qjLtkPodIR9Nha6VN5Ex9YWeCPA30l20oj9KJ2MrD7tc VDwG+/nAUjKVtqmfQs7geZ9AHRD6ZGGpOXPuyMWM1m0+I9UVwm9KxO+eXKkBRDKXkmyp 6UCSM24IQeACQ0G6VE60LTdx4ouag0KUQgwKGFpWCt8WV1RH2aLuUyhfzoeXlv2izZmO lYUQ==
X-Gm-Message-State: AElRT7F+4vFqzpgUtDJUkRvm0q4nmFiGa7+3VSXBGe2D+lAPD+j+vhAb ef0/UfkVMQDOQdh0M6J7BkBnNKx0CGzr6rDsg5o=
X-Google-Smtp-Source: AG47ELvkZ3d8h6eFX+h//+rAXo7ujo87too9CQgSTJbJuqUx5qCo88G9nPViRCNQ/TtEjKexCif99CrQKKWeAIH7gwA=
X-Received: by 10.157.12.132 with SMTP id b4mr1705439otb.393.1520982221446; Tue, 13 Mar 2018 16:03:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.7.27 with HTTP; Tue, 13 Mar 2018 16:03:11 -0700 (PDT)
In-Reply-To: <CABcZeBOgqcL=GiFAAoKMidQa8=whpdDk5jk9zHgSRMz1g5tUag@mail.gmail.com>
References: <CABcZeBO9g5vnPK2aGYEUOYOkT-898Gc0-d4T=kDvxuE2Yg6kMQ@mail.gmail.com> <CABcZeBNAYiTzdyE+UcqvThgnKhDthuq2-UyjEBoJkpep8-t5vg@mail.gmail.com> <CA+9kkMBtWodBt7HR9SZmb4KhuOaaTLJ+CnwjhGO3Td5dL6xxmQ@mail.gmail.com> <CABcZeBOgqcL=GiFAAoKMidQa8=whpdDk5jk9zHgSRMz1g5tUag@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 13 Mar 2018 16:03:11 -0700
Message-ID: <CA+9kkMDA37auroT2XDPZPG372baxEZXp=-kpAtUXyirAMQ52vQ@mail.gmail.com>
Subject: Re: Proposal: Run QUIC over DTLS
To: Eric Rescorla <ekr@rtfm.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="001a1140e41e04e1aa0567534519"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jiq1cfdNQU1mbV48-_AW0BJwlHo>
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, 13 Mar 2018 23:03:45 -0000

On Tue, Mar 13, 2018 at 3:50 PM, Eric Rescorla <ekr@rtfm.com>; wrote:

>
> On Tue, Mar 13, 2018 at 12:20 PM, Ted Hardie <ted.ietf@gmail.com>; wrote:
>
>> On Tue, Mar 13, 2018 at 9:52 AM, Eric Rescorla <ekr@rtfm.com>; wrote:
>>
>>>
>>> I'd like to focus on the architectural question for the moment. I
>>> think there's broad -- though not universal -- agreement that the
>>> stream 0 thing is not great, but a fair amount of debate about
>>> what the right architecture and architectural principles are.
>>> It's not really productive to talk about schedule impact until
>>> we understand what the right thing is.
>>>
>>>
>> Hi Eric,
>>
>> As it stands, you've identified a pain point, and you've made a proposal
>> to  rebase a key part of the architecture on the basis of that pain.
>>
>> Folks agree with you that it is a pain point, but all of the feedback
>> you're getting that this isn't worth the schedule slip is, fundamentally,
>> also feedback on how bad the pain is.  The message I read (and, to be fair,
>> participated in sending) from this thread is "not bad enough for this".
>> It's clearly bad enough that Christian, I, and I'm sure others would like
>> you to create a PR to incorporate what improvements from your proposal can
>> fit into the current structure.   If that's the conversation you want to
>> have, I'm happy to jump in.
>>
>
> Hi Ted,
>
> I appreciate your concern with the schedule, and I do recognize that
> there are people who think that this is too late to discuss, but I
> also heard people who thought it was worth exploring, which is what
> I'm asking for at the moment.
>
> Even if I were to concede that that were not the case -- which I don't
> -- it's not possible to have a discussion about what we can do to
> address these issues without understanding the architectural
> principles we are trying to follow, which requires actually discussing
> the points I raised above.
>
> Hi Ekr,

It appears that I wasn't clear; sorry.  I am fine with continuing to
discuss the architectural points, but I don't want to do so by putting
aside discussion of the schedule.  Your note said that you felt it wasn't
productive to discuss the schedule impact while discussing the
architectural issues, and it was that point I disagree with it.

As I said earlier on, I don't want QUIC to be the last turn of the crank
for producing new transport protocols, and determining what lessons we
ought to learn for the next turn is always valuable, even if we choose to
make more modest changes in this effort.

I hope this clarifies my intent,

regards,

Ted



> -Ekr
>
>
>
>> But I don't think we can ignore the signal that the current state of
>> affairs actually works and that changing away from it so completely isn't
>> worth the (new) pain.  I think we will lose both momentum and expertise if
>> we start over to this extent at this juncture, and I'd rather we did not.
>> I'm particularly worried that the uncertainty around this could kill the
>> productivity of the hackathon and London meeting, and that we won't recover
>> until the next interim, if then.
>>
>> Not talking about that as we analyze this seems to me to be the wrong
>> choice.
>>
>> regards,
>>
>> Ted
>> /no hats
>>
>>
>>
>