IETF Logo Mail Archive

Re: [quicwg/base-drafts] receivers cannot enforce datagram padding (though they may drop) (#4254)

Marten Seemann <notifications@github.com> Tue, 20 October 2020 04:11 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 EABF13A0A3B for <quic-issues@ietfa.amsl.com>; Mon, 19 Oct 2020 21:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.555
X-Spam-Level:
X-Spam-Status: No, score=-1.555 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 GCsrgqChTbl3 for <quic-issues@ietfa.amsl.com>; Mon, 19 Oct 2020 21:11:50 -0700 (PDT)
Received: from out-28.smtp.github.com (out-28.smtp.github.com [192.30.252.211]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AB79D3A0A2E for <quic-issues@ietf.org>; Mon, 19 Oct 2020 21:11:50 -0700 (PDT)
Received: from github.com (hubbernetes-node-517ff24.ash1-iad.github.net [10.56.102.61]) by smtp.github.com (Postfix) with ESMTPA id E37069001F6 for <quic-issues@ietf.org>; Mon, 19 Oct 2020 21:11:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1603167109; bh=YrEbsX9l98ER5Me84W6HyCLknEqOzfFhHD0XfFCvsI8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=w3GRESmSHjtxhX9ANhRUr+HjzGR3P9f8lZgUo8ZV+czhBIhvWaN2hxLUBCUsUrGAW jbjLt8kQ7kJPEQQYdCWNiEaRzVZdg9z4Fj0TCBhI0QCW1ksjMyXO42cayc4eQmo5MB 1fkIde+0izHWo01thgJGNUhHWpFfhPJd/e1prqdY=
Date: Mon, 19 Oct 2020 21:11:49 -0700
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK45HSQLLX5DUTH2XEN5TJCILEVBNHHCWODDNU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/4254/review/512317468@github.com>
In-Reply-To: <quicwg/base-drafts/pull/4254@github.com>
References: <quicwg/base-drafts/pull/4254@github.com>
Subject: Re: [quicwg/base-drafts] receivers cannot enforce datagram padding (though they may drop) (#4254)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f8e6385e03a2_4619b41740d1"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: marten-seemann
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/4isBtUvA6mm6c6g7FCky47GDyYQ>
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 04:11:52 -0000

@marten-seemann requested changes on this pull request.



> @@ -4085,6 +4085,13 @@ UDP datagrams MUST NOT be fragmented at the IP layer.  In IPv4
 ({{!IPv4=RFC0791}}), the DF bit MUST be set if possible, to prevent
 fragmentation on the path.
 
+Even though datagrams with certain properties are required to be padded, the
+size of the datagram is not authenticated, and endpoints might send coalesced
+packets after the handshake is confirmed (see {{packet-coalesce}}).  Therefore,

Once the handshake is confirmed, Handshake keys are dropped. From that point on, it's not possible to send coalesced packets any more.

-- 
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/pull/4254#pullrequestreview-512317468

v2.23.0 | Report a Bug | By Email