IETF Logo Mail Archive

Re: [quicwg/base-drafts] CONNECTION_CLOSE for unpadded Initial (#3269)

Marten Seemann <notifications@github.com> Wed, 20 November 2019 03:05 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 B84D9120AE6 for <quic-issues@ietfa.amsl.com>; Tue, 19 Nov 2019 19:05:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.454
X-Spam-Level:
X-Spam-Status: No, score=-6.454 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, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 uA4Y9I_QycY1 for <quic-issues@ietfa.amsl.com>; Tue, 19 Nov 2019 19:05:31 -0800 (PST)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1B9BC120AED for <quic-issues@ietf.org>; Tue, 19 Nov 2019 19:05:31 -0800 (PST)
Date: Tue, 19 Nov 2019 19:05:30 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1574219130; bh=5pul3M9gqYFE1K8TwOb/fj1gzgr2zCPlMQ5Fzh5e6Xk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ir0Jr9kPQXI3mDEMuIDl4AUAR3G7kzz7j1xtXE9/pnMQpxlRrFkfTdMEzSwbumpgu zWnZ+qd0g2b1iWQUhE2kLgBg198TAsBtX5TkGrPFmYNRE7o6EFakt1VD97rR6rWPQM t2JA1QmQHuWI1G7U3UZyFqgVNYv5L+bxnzK8fcaU=
From: Marten Seemann <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZCIKRH65C72TE6FBF34HP7VEVBNHHB6UGSKE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3269/555815799@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3269@github.com>
References: <quicwg/base-drafts/issues/3269@github.com>
Subject: Re: [quicwg/base-drafts] CONNECTION_CLOSE for unpadded Initial (#3269)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dd4ad7a2a866_3aa73f9bfc4cd95c116538"; 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/PTn_hkAlvXz3TN2LIrQWI011QcI>
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: Wed, 20 Nov 2019 03:05:35 -0000

> The draft requires that if an Initial packet is not padded, the server sends a CONNECTION_CLOSE.

Why would a server want to send a CONNECTION_CLOSE in the first place? I think dropping the packet is a perfectly valid thing to do, and in fact is preferable at such an early state in the connection.

-- 
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/3269#issuecomment-555815799

v2.26.15 | Report a Bug | By Email | System Status