Re: A non-TLS standard is needed

Paul Vixie <paul@redbarn.org> Mon, 27 April 2020 22:46 UTC

Return-Path: <paul@redbarn.org>
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 C7FE13A0CE8 for <quic@ietfa.amsl.com>; Mon, 27 Apr 2020 15:46:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, 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 xXaX-JHlkBvt for <quic@ietfa.amsl.com>; Mon, 27 Apr 2020 15:46:56 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97C5F3A0CE7 for <quic@ietf.org>; Mon, 27 Apr 2020 15:46:56 -0700 (PDT)
Received: from linux-9daj.localnet (vixp1.redbarn.org [24.104.150.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 5C4EAB074A; Mon, 27 Apr 2020 22:46:56 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: Lars Eggert <lars@eggert.org>
Cc: quic <quic@ietf.org>
Subject: Re: A non-TLS standard is needed
Date: Mon, 27 Apr 2020 22:46:55 +0000
Message-ID: <2010266.tehQBtF6zN@linux-9daj>
Organization: none
In-Reply-To: <72518FA2-4D02-4498-BFED-C6F694C5687A@eggert.org>
References: <tencent_458BB4AFD3E32DBAAEA3F09FAEF063800605@qq.com> <2208100.KEu4SK8F6j@linux-9daj> <72518FA2-4D02-4498-BFED-C6F694C5687A@eggert.org>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aH3aoM49TXxk8lpMcDqVVFMGEvc>
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: Mon, 27 Apr 2020 22:46:58 -0000

On Monday, 27 April 2020 11:56:20 UTC Lars Eggert wrote:
> Hi Paul,
> 
> this is definitely a broader discussion - it's popping up in other places as
> well.
> 
> The IETF can certainly have this discussion somewhere, but the QUIC list is
> probably not the right home for it, esp. not as we've entered the home
> stretch with regards to closing the final open issues that will let us WGLC
> the current specs.

lars, et al, thank you for such recognition. if mirjam's draft isn't a WG 
item, i hope that those in charge will find a place for it. i do not expect to 
relitigate the mandate for TLS, but i do hope we can recommend some signal 
beyond destination UDP port number, which is arbitrary given ALT-SVC and the 
HTTPSSVC mechanisms, as the way a hardened private network can recognize some 
UDP flows as likely to be HTTP-related and thus permitted to form outbound 
flows. without this the applicability of QUIC will be less than it could be.

in other words i am requesting advice, a redirect, beyond the source quench.

-- 
Paul