Re: Fwd: Quic: the Elephant in the Room

Michael Thomas <mike@mtcc.com> Wed, 21 April 2021 19:38 UTC

Return-Path: <mike@fresheez.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92C8A3A340E for <ietf@ietfa.amsl.com>; Wed, 21 Apr 2021 12:38:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mtcc.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 ZyrPyI7rRTVL for <ietf@ietfa.amsl.com>; Wed, 21 Apr 2021 12:38:17 -0700 (PDT)
Received: from mail-pg1-x52b.google.com (mail-pg1-x52b.google.com [IPv6:2607:f8b0:4864:20::52b]) (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 970AD3A340D for <ietf@ietf.org>; Wed, 21 Apr 2021 12:38:17 -0700 (PDT)
Received: by mail-pg1-x52b.google.com with SMTP id j7so21492740pgi.3 for <ietf@ietf.org>; Wed, 21 Apr 2021 12:38:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mtcc.com; s=fluffulence; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=n8+u+su90Z+pz0rGQHI2vtqhExPMW1YupR08NvMXn58=; b=MkCDgUtGVNGiQrvweNa7LQtntWTE4DedbS6qer08z01xcFJML3ZCQmxa+JvtnYz6Je iC6A39FJbo9NcySEefqx8dmwikgtttxgiw47YnOzpF5cYbNlpTHu1S0cOvYVHisXhsq3 UszrtcVbQOEAh3P16u8AcdH7cI6i35GdGgJb4sgx2uMOeawrOKalKlHqzQrabTeGXRwX TPsNYUMgwUhYzhExvFSY8o0EIQLQjTg4LQzIPA4vaCTSKWrLSMgkG72SfDaAJvlQ5ja5 wsqdc5LShoF1nRfMlGasYV0kdjVcTbc4+Lb777nG2iJ50s8Tl4HnodKwlHy/H/xFifBU j2hg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=n8+u+su90Z+pz0rGQHI2vtqhExPMW1YupR08NvMXn58=; b=iTjzVZGr56+GrYeEyUI1nOlXHHbuAQjCNMgEKL2hO+xFpb7ARvwjpqcEXZtC6EjCME b2BifTm2yy83HHoE4b3G1S1+W+vKfIhSTMue8q9iLgZtdN8DxeQGyp5IbgENCoqGcCzD pIIdyOa8munJfl+KB91LtF7NrOvGHRrBkk1H5uM+Kf60++SbPgTc/0Rc9oKZ1xcEQy/C Hokz4n0dwLybCffvyjmdTcfEA4sDkVWXMcIAB9l5VHRKkm4pG4ukYpdezDVcj3k5I2t8 QexoMpb6ccSuwCqgrodAz6bxEJw0+maulKqu95oPo0F2Q23uwKVY8o7QUHubrOe1GzdM 2C+g==
X-Gm-Message-State: AOAM532TrxudwFapPjKysTjY4nQQ8Md1fcoggUuEjsPoxSb5HPCFt21U ZXmP6Rd5WOqb9wzGEryBbwJcRHV+mJjrRQ==
X-Google-Smtp-Source: ABdhPJwptVucqLWDunvsrwqupiWB6PNtLBAl84Ek2JIrkAU7aGNRGGCYyioq+y+mQCjVqdICzP53HA==
X-Received: by 2002:a63:5458:: with SMTP id e24mr22991810pgm.170.1619033896037; Wed, 21 Apr 2021 12:38:16 -0700 (PDT)
Received: from mike-mac.lan (107-182-43-245.volcanocom.com. [107.182.43.245]) by smtp.gmail.com with ESMTPSA id v10sm188099pgi.6.2021.04.21.12.38.14 for <ietf@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 21 Apr 2021 12:38:15 -0700 (PDT)
Subject: Re: Fwd: Quic: the Elephant in the Room
To: ietf@ietf.org
References: <8BA5A095-268D-494B-A272-D43B5CA5F7F4@eggert.org> <E15E2665-09AB-4EB3-B65B-BAF54618133E@eggert.org>
From: Michael Thomas <mike@mtcc.com>
Message-ID: <ec187d3e-4372-5978-c011-4abbae5fc6ae@mtcc.com>
Date: Wed, 21 Apr 2021 12:38:14 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.9.0
MIME-Version: 1.0
In-Reply-To: <E15E2665-09AB-4EB3-B65B-BAF54618133E@eggert.org>
Content-Type: multipart/alternative; boundary="------------C94F1393B77A5C829E410E86"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/LNRcXZNT6u5TQd7_8W_NmHcDgK0>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Apr 2021 19:38:22 -0000

On 4/21/21 12:00 PM, Lars Eggert wrote:
> Hi,
>
> for context, and to correct some misrepresentations, here is my reply 
> to Michael from the QUIC list.

I counted the number of messages from the rest of the working group 
before one of the chairs called it off topic and for me to go way and it 
was 4 or maybe 5. And "as chair" is not a suggestion, it is a command. 
It sure seems to me that the number of messages a transport protocol 
needs to start a session is pretty on topic, or at least of interest.

Getting told to go elsewhere *is* dramatic, if not predictable.

Mike

>
> Thanks,
> Lars
>
>
> Begin forwarded message:
>>
>> *From: *Lars Eggert <lars@eggert.org <mailto:lars@eggert.org>>
>> *Subject: **Re: Quic: the Elephant in the Room*
>> *Date: *April 21, 2021 at 19:46:57 GMT+3
>> *To: *Michael Thomas <mike@mtcc.com <mailto:mike@mtcc.com>>
>> *Cc: *Eric Rescorla <ekr@rtfm.com <mailto:ekr@rtfm.com>>, Phillip 
>> Hallam-Baker <phill@hallambaker.com <mailto:phill@hallambaker.com>>, 
>> Matt Joras <matt.joras@gmail.com <mailto:matt.joras@gmail.com>>, 
>> Lucas Pardue <lucaspardue.24.7@gmail.com 
>> <mailto:lucaspardue.24.7@gmail.com>>, David Schinazi 
>> <dschinazi.ietf@gmail.com <mailto:dschinazi.ietf@gmail.com>>, IETF 
>> QUIC WG <quic@ietf.org <mailto:quic@ietf.org>>
>>
>> Hi,
>>
>> On 2021-4-21, at 19:11, Michael Thomas <mike@mtcc.com 
>> <mailto:mike@mtcc.com>> wrote:
>>> I am a newcomer. I came here against my better judgement as I stated 
>>> on the IETF list.
>>
>> I have emails from you in my IETF mail archive at least as far back 
>> as 2006. But I assume you mean that you are a newcomer to the QUIC WG.
>>
>>> I immediately had my head chopped off and told to go away by a 
>>> working group chair in less than 24 hours.
>>
>> I don't think you're helping your case by using dramatic phrases.
>>
>> To recap: You brought a proposal that had been discussed elsewhere to 
>> the QUIC WG list. You got feedback from a number of different 
>> participants on your proposal. The discussion veered away from QUIC 
>> to other protocols that this WG is not working on. A chair suggested 
>> you continue the discussion on a mailing list better suited to your 
>> topic.
>>
>>> If the number of packets exchanged in the initial handshake of a 
>>> transport protocol is off topic, I am speechless. My better 
>>> judgement wasn't that it was off topic, it was that this outcome is 
>>> the ordinary behavior of insular IETF working groups.
>>
>> A number of participants have commented on this already, for example, 
>> pointing out that the number of round trips matter much more than the 
>> number of packets, and that in their opinion your suggestion would 
>> not lead to further substantial enough gains. You then moved the 
>> topic of the discussion to why Google (and I assume other companies) 
>> are not signing their zones and offered theories as to why that is, 
>> which is not a topic of relevance to this WG. Hence the request to 
>> discuss it elsewhere.
>>
>>> I also got told that signing a zone is tantamount to "boiling the 
>>> ocean".
>>
>> You're misquoting David. He said:
>>
>> On 2021-4-20, at 20:20, David Schinazi <dschinazi.ietf@gmail.com 
>> <mailto:dschinazi.ietf@gmail.com>> wrote:
>>> I'm not saying that a 3-packet handshake would be bad, I'm saying
>>> that it's not worth boiling the ocean to remove 2 packets.
>>
>> Nowhere in that sentence or the rest of David's email do I see any 
>> mention of signing zones.
>>
>>> As IETF chair, do you agree with that? Because if it's true then 
>>> there are serious issues with DNSSec and we should do something 
>>> about it. I think it's nonsense, fwiw.
>>
>> Again, not a topic for *this* mailing list.
>>
>>> Mike, and what exactly are those venues? tia.
>>
>> I'd start at DNSOP and ask if there is a more appropriate list.
>>
>> Thanks,
>> Lars
>>
>>
>