IETF Logo Mail Archive

Re: Last Call: <draft-ietf-quic-applicability-14.txt> (Applicability of the QUIC Transport Protocol) to Informational RFC

Christian Huitema <huitema@huitema.net> Mon, 24 January 2022 20:48 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 457FB3A0BFB for <quic@ietfa.amsl.com>; Mon, 24 Jan 2022 12:48:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.602
X-Spam-Level:
X-Spam-Status: No, score=-7.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.714, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=unavailable 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 uox4qNLfM4jD for <quic@ietfa.amsl.com>; Mon, 24 Jan 2022 12:48:55 -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 053883A0BED for <quic@ietf.org>; Mon, 24 Jan 2022 12:48:54 -0800 (PST)
Received: from xse212.mail2web.com ([66.113.196.212] helo=xse.mail2web.com) by mx135.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nC6Gf-0002oy-17 for quic@ietf.org; Mon, 24 Jan 2022 21:48:52 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4JjMXG4ktPzLJg for <quic@ietf.org>; Mon, 24 Jan 2022 12:48:46 -0800 (PST)
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1nC6Gc-0004VF-I3 for quic@ietf.org; Mon, 24 Jan 2022 12:48:46 -0800
Received: (qmail 7439 invoked from network); 24 Jan 2022 20:48:45 -0000
Received: from unknown (HELO [192.168.200.66]) (Authenticated-user:_huitema@huitema.net@[72.235.197.84]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <last-call@ietf.org>; 24 Jan 2022 20:48:45 -0000
Message-ID: <787736c3-e7fc-168a-db8e-8025cf21b5b4@huitema.net>
Date: Mon, 24 Jan 2022 10:48:43 -1000
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: last-call@ietf.org, IETF-Announce <ietf-announce@ietf.org>
Cc: quic@ietf.org, draft-ietf-quic-applicability@ietf.org, Zaheduzzaman.Sarker@ericsson.com, matt.joras@gmail.com, quic-chairs@ietf.org
References: <164303934925.4261.5777530168632194333@ietfa.amsl.com>
From: Christian Huitema <huitema@huitema.net>
Subject: Re: Last Call: <draft-ietf-quic-applicability-14.txt> (Applicability of the QUIC Transport Protocol) to Informational RFC
In-Reply-To: <164303934925.4261.5777530168632194333@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: 66.113.196.212
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.09)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT97i3UAKe3M5Q/idGJ2g2o6PUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5x6h2yQpzTslcOqazQkKtAFKj/EwzSHE5FGYwwjsNRPCCbm LxUnsy644u5Pqj1X6y3mD6wdmZPcItWbGe10hXJtXL4FsauCVkDjmcYJdU3yWp7KuHNaaKdg7iBE ZefdsNUFWKwa/wzJUjmazeC7ImcapiW8pZ2PmF36xFjfnZTYwBQ6V51u76v35b1wNe/MvdL/hXir I7jpLA3NtNK1rbkD2+J9PgaoF8SQHto3le4zsHTaeQtlKubP6iUTjj6yPARK6buALVaA782LKxg6 vRmng8N1aLhXqdc+jC1RcnVud53D5caUhbVtvqItBqoizkEt9O20UjkwI0v+LOlw05G4BS+iyyNq bT8dUMXMJ4tUCMj6G37ZfAMLceP5aNHPt26RBupu5v1nytoNnc138GfEJRQ2qC7jjynPIHPNqSn4 QTXUjLjYWQt1/5xnQymMoPsgr/U0flMcy2Vi/IcBgY4arPaiJ1W6hAyiRC61jekdwIcXNugoOEbH RyFULpSjm7jZ1h/HfDRQ5Ig8VhPsPE8NlkBmbR1LS6Kx8w5MHqDEEz4cuRlNZu3m3dTlBwK3/x1k TJUpwVTBkMuRiOkIwxGJDRojSVizNl0ce/s7u0P9b9Tml6eOMCV9kYYwkPx6ZsXvIUzTXkDAiiJi mGhLUFuS2lhaIetXfCg1JdAVrOwKfG2n2BoS2EZ0uMLqFd0EzkhUoFIvD3sIcP1fhJPM6B/8Ip0p nk+kXy8MVdyGFO3QlGBA8uIWBTaxiXLo2fDhOGCJ+dym1L8cD17Js0v4cp1M3DMnQUSjXMH40pca uRrcbzcKVNeVJ9BXyu9+ceCqThTYg2px1fSoqxQCCHnLMo/m9VKh99btUAanjnMCAH2co+fBoeG+ Hs0afhsY/5zhNYWRVYKU9W9tbmVXJBqdHHDmZEKhyNAv1N35kYWaEdgLurFV5oTvAcwA4rM3FkfW 8/1kE/e7sUnsVpINvARNxpFO
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/S08Z3Tam41hRhm1mqj-suozrF6w>
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, 24 Jan 2022 20:49:00 -0000

Reading the current draft, I find one small issue regarding packet 
types. The draft mentions in section 2.1 that packet types are defined 
in the Version1 specification. Section 3.1.2 correctly warns against 
using packet types for heuristics because they may changed in further 
version, and section 3.4.1 correctly conditions inspection of Initial 
packet to recognizing version 1. However, I am concerned that 
middle-boxes might ignore these caveats. Could we add a note somewhere, 
maybe in section 2.1, that different versions of QUIC might encode 
packet types differently? Indeed, the version 2 draft 
(https://datatracker.ietf.org/doc/draft-ietf-quic-v2/) uses different 
encodings for the packet types.

-- Christian Huitema

On 1/24/2022 5:49 AM, The IESG wrote:
> The IESG has received a request from the QUIC WG (quic) to consider the
> following document: - 'Applicability of the QUIC Transport Protocol'
>    <draft-ietf-quic-applicability-14.txt> as Informational RFC
>
> The IESG plans to make a decision in the next few weeks, and solicits final
> comments on this action. Please send substantive comments to the
> last-call@ietf.org mailing lists by 2022-02-07. Exceptionally, comments may
> be sent to iesg@ietf.org instead. In either case, please retain the beginning
> of the Subject line to allow automated sorting.
>
> Abstract
>
>
>     This document discusses the applicability of the QUIC transport
>     protocol, focusing on caveats impacting application protocol
>     development and deployment over QUIC.  Its intended audience is
>     designers of application protocol mappings to QUIC, and implementors
>     of these application protocols.
>
>
>
>
> The file can be obtained via
> https://datatracker.ietf.org/doc/draft-ietf-quic-applicability/
>
>
>
> No IPR declarations have been submitted directly on this I-D.
>
>
>
>
>
> _______________________________________________
> IETF-Announce mailing list
> IETF-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-announce

v2.23.0 | Report a Bug | By Email