Re: [quicwg/base-drafts] Endpoints cannot verify padding (#4253)

Kazuho Oku <notifications@github.com> Tue, 20 October 2020 01:28 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8882E3A0962 for <quic-issues@ietfa.amsl.com>; Mon, 19 Oct 2020 18:28:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.482
X-Spam-Level:
X-Spam-Status: No, score=-1.482 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 (1024-bit key) header.d=github.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 xEIV28TAuOa6 for <quic-issues@ietfa.amsl.com>; Mon, 19 Oct 2020 18:28:54 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46CAB3A0948 for <quic-issues@ietf.org>; Mon, 19 Oct 2020 18:28:54 -0700 (PDT)
Received: from github.com (hubbernetes-node-b4817f2.ac4-iad.github.net [10.52.19.50]) by smtp.github.com (Postfix) with ESMTPA id 6E81F600376 for <quic-issues@ietf.org>; Mon, 19 Oct 2020 18:28:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1603157333; bh=d5DIKv2CkAI3q/P4q9Bmm2HRLjne/CUJMPvg8oGNN7s=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=lct5z9hMErKYJz7WCkGkgPj+xRC7ywweoFv5UJklPcHF9/Sz4io0YqaQWxeIeiOrg y5AG46hYMKggKBhPq3eRwZLsXkmTHfCKfio5K/fAFDBzOUik0i4gs3+SgJ53HmdfF4 HvNa5q/fimWjrjPTp7nLAccSAH24HEmkXcksuk2U=
Date: Mon, 19 Oct 2020 18:28:53 -0700
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK6EH5IO4OWIIVDZYZV5TIPFLEVBNHHCWOBQMQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4253/712531288@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4253@github.com>
References: <quicwg/base-drafts/issues/4253@github.com>
Subject: Re: [quicwg/base-drafts] Endpoints cannot verify padding (#4253)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f8e3d556b6e3_5719b4531637"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/_ZoeNCV8O_0LMYi5XaX3r-YyIgU>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 20 Oct 2020 01:28:55 -0000

As a step forward, I think we should do the following:
* Regarding the sentence we added in #4183, we should either a) change the rule to "MAY discard UDP datagrams less than 1200 bytes that carry ACK-eliciting Initial apckets", or b) delete the sentence, and
* Considering the fact that there could be other occasions in which we might want to require padding, either within the base drafts, or in some of the extensions, add a note to [section 14](https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#name-datagram-size) or somewhere that datagram size is not authenticated and cannot be enforced by the peer.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/4253#issuecomment-712531288