Re: [quicwg/base-drafts] Clarify initial UDP datagram padding (#2519)
Kazuho Oku <notifications@github.com> Wed, 13 March 2019 22:36 UTC
Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 E34761310B5 for <quic-issues@ietfa.amsl.com>; Wed, 13 Mar 2019 15:36:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.001
X-Spam-Level:
X-Spam-Status: No, score=-3.001 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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, 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 KcweC7Djx0BX for <quic-issues@ietfa.amsl.com>; Wed, 13 Mar 2019 15:36:18 -0700 (PDT)
Received: from o1.sgmail.github.com (o1.sgmail.github.com [192.254.114.176]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BEC81310E2 for <quic-issues@ietf.org>; Wed, 13 Mar 2019 15:36:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=Aoj7AcvW5FKNM+ZVcTiiyoEriHc=; b=ZdN+OEqGprbMM188 afO3F0r9NNCvdvxZ0gwNEkIVlU08d7pQJQ6n5SSdh1RNVqcHm7nAUdeDSUBV4MPK 9fwdgs3zqHuYJqEQvPZfmCGmNY0hHAkMSPNbpczFusQmJWl82zzQZeMoNfxs8MMg sWJzUVx1zBLlShMRo7iYUl11IBQ=
Received: by filter0849p1las1.sendgrid.net with SMTP id filter0849p1las1-26642-5C8985E0-27 2019-03-13 22:36:17.020244857 +0000 UTC m=+107836.707634751
Received: from github-lowworker-dcc078e.cp1-iad.github.net (unknown [192.30.252.44]) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id 63WC4SFtRZq7sSTKbVR3gg for <quic-issues@ietf.org>; Wed, 13 Mar 2019 22:36:16.837 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-dcc078e.cp1-iad.github.net (Postfix) with ESMTP id CA96C2C036F for <quic-issues@ietf.org>; Wed, 13 Mar 2019 15:36:16 -0700 (PDT)
Date: Wed, 13 Mar 2019 22:36:17 +0000
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abe63d1de23a778d0b665c9596729f0b957077091592cf0000000118a147e092a169ce1910f335@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2519/472633202@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2519@github.com>
References: <quicwg/base-drafts/issues/2519@github.com>
Subject: Re: [quicwg/base-drafts] Clarify initial UDP datagram padding (#2519)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c8985e0c8f68_7cb83f99a72d45bc4273bf"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3g0DaTtLe+N80D+XALtobql9rP3/RzzHOTn8 DK3kcPIYOFxPvWAjB56u3VF2zzAfsFNsB6RVobkKOSsFPGAweWJw4gB0sK+ZJQTlXUvlaRHiScmBqb nJBbsYhI0RP6xy8ethg5H/w9AlasOCOcUwmGaXepiHKOJxdc01D7ViU5QAHg8O6IHgSHFE88m81HvI 4=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/iwg-WifL7lPZSp1gBzi2YdgLGDo>
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, 13 Mar 2019 22:36:21 -0000
As stated in https://github.com/quicwg/base-drafts/pull/2520#discussion_r265213467, I prefer to stop requiring the use of full-sized packets once the client observes a response from server. Reasons: * QUIC stacks would have the logic to change rules based on if the peer's address has been validated due to the 3-packet rule on the server side. It's just about using the same logic for padding on the client side. * Implementations that prefer to pad all the Initial packets it sends can do so anyways. * Regardless of what we decide, the server side logic would be indifferent; i.e. create new connection context only when observing a full-sized Initial packet. -- 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/2519#issuecomment-472633202
- [quicwg/base-drafts] Clarify initial UDP datagram… Dmitri Tikhonov
- Re: [quicwg/base-drafts] Clarify initial UDP data… ianswett
- Re: [quicwg/base-drafts] Clarify initial UDP data… Martin Thomson
- Re: [quicwg/base-drafts] Clarify initial UDP data… ianswett
- Re: [quicwg/base-drafts] Clarify initial UDP data… Kazuho Oku
- Re: [quicwg/base-drafts] Clarify initial UDP data… Martin Thomson
- Re: [quicwg/base-drafts] Clarify initial UDP data… ianswett
- Re: [quicwg/base-drafts] Clarify initial UDP data… Kazuho Oku
- Re: [quicwg/base-drafts] Clarify initial UDP data… Jana Iyengar