Re: [quicwg/base-drafts] Clarify initial UDP datagram padding (#2519)
ianswett <notifications@github.com> Wed, 13 March 2019 22:25 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 69F11126CFF for <quic-issues@ietfa.amsl.com>; Wed, 13 Mar 2019 15:25:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.383
X-Spam-Level:
X-Spam-Status: No, score=-1.383 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 f0TzO3_IX7ON for <quic-issues@ietfa.amsl.com>; Wed, 13 Mar 2019 15:25:41 -0700 (PDT)
Received: from o8.sgmail.github.com (o8.sgmail.github.com [167.89.101.199]) (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 09A9B124BF6 for <quic-issues@ietf.org>; Wed, 13 Mar 2019 15:25:40 -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=SXh/7k6F76VwoYQO6Oa9TF+eylk=; b=fTC99eqfimaqLwXO CvikgYEJwFw8+q+Jwd6biamD0+CE+KhYfAcmGnYy4wlX/I2sfwgTaUN7TKQnwB2T Zp+rYBRqHD5Oe2tRbfPHYCkWcMik79evzS3VMytO9RaNeboHBVCqUniGgExmjvTG 57psrevYiQuuqvQ5sctm9TjZIl8=
Received: by filter1492p1mdw1.sendgrid.net with SMTP id filter1492p1mdw1-9271-5C898363-2F 2019-03-13 22:25:39.812524963 +0000 UTC m=+166460.735352301
Received: from github-lowworker-dcc078e.cp1-iad.github.net (unknown [192.30.252.44]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id uYtDj5VgTrSW6Fu8xygVhw for <quic-issues@ietf.org>; Wed, 13 Mar 2019 22:25:39.784 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-dcc078e.cp1-iad.github.net (Postfix) with ESMTP id BD17A2C0045 for <quic-issues@ietf.org>; Wed, 13 Mar 2019 15:25:39 -0700 (PDT)
Date: Wed, 13 Mar 2019 22:25:39 +0000
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2afad940290c61fc4aa9a00ab4d05cd6966bd50092cf0000000118a1456392a169ce1910f335@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/472630210@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_5c898363bbbb8_7ca43f99a72d45bc2067c3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0RGqYiGYmeXZhi+wZUX5ASuKuG9HCmGx7NxH ERGGNo3FVIVqICL348/7uhu8gGC4gTH5nf/0V8OvqNGyxjJNfTdxPTRTn1jMe/MtVCrgHWWAVgtwK7 LXyDMwsaxEZJGTSPttS238McrSgU8EY6lutHE6fta7CER9zQCSDRLUgLSw==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/mIH0oJ1eZk6Q0Z-kjN0_1GwFMAA>
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:25:42 -0000
Given PADDING is supposed to count towards bytes in flight, but it's not ack-eliciting, a special case for ACK-only packets makes sense. I'd be inclined to specify ACK-only packets as the exception, opposed to basing it on receiving an ACK of handshake or some other mechanism. -- 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-472630210
- [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