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 C43B7120043
 for <quic-issues@ietfa.amsl.com>; Sat, 14 Sep 2019 12:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level: 
X-Spam-Status: No, score=-7.999 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_32=0.001,
 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 WBjxNq2jUfZN for <quic-issues@ietfa.amsl.com>;
 Sat, 14 Sep 2019 12:19:11 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by ietfa.amsl.com (Postfix) with ESMTPS id 767F912001E
 for <quic-issues@ietf.org>; Sat, 14 Sep 2019 12:19:11 -0700 (PDT)
Date: Sat, 14 Sep 2019 12:19:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
 s=pf2014; t=1568488750;
 bh=S4JZyaYcFfKqXLXkEcIaEfkRjuA0XHVIhMtQ3AyjxTM=;
 h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post:
 List-Unsubscribe:From;
 b=zzZZpT9tbu7o0ZEpNXuos7pOTg5OkRqjaLfmcyB1p8c1TjUgFIusycJzozGnz1Pjg
 IR758AiYGNbuenib9tWfkWrgpd5Oy8B/Hmobk5TBVTp+km4tO+UEPui7CJL43tiRRa
 hQ25UNC5TiVAU2ss0+SA4aUASFzF+Wcqzw2vkwuI=
From: Alessandro Ghedini <notifications@github.com>
Reply-To: quicwg/base-drafts
 <reply+AFTOJK5TSHVNWX6R2NO7R7F3RJ635EVBNHHB23E46Q@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3033@github.com>
Subject: [quicwg/base-drafts] Suggest sending empty CRYPTO frames in
 Initial/Handshake packets (#3033)
Mime-Version: 1.0
Content-Type: multipart/alternative;
 boundary="--==_mimepart_5d7d3d2e6ce34_40293ff15c0cd964209760";
 charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ghedo
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/Cw_cWT-AzYi24iV0TbXdIiU1f7c>
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: Sat, 14 Sep 2019 19:19:13 -0000


----==_mimepart_5d7d3d2e6ce34_40293ff15c0cd964209760
Content-Type: text/plain;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

As per @tatsuhiro-t, since PING frames are not allowed in
Initial/Handshake packets, one can use an empty CRYPTO frame when
sending a probe when there is no other ack-eliciting frame to send.

It seems to me like this is something that is fairly easy to miss, so
worth expanding the existing suggestion I think.

The alternative would be to allow PING frames in Initial/Handshake, but
I figured we are maybe too late in the process for that kind of design
change.
You can view, comment on, or merge this pull request online at:

  https://github.com/quicwg/base-drafts/pull/3033

-- Commit Summary --

  * Suggest sending empty CRYPTO frames in Initial/Handshake packets

-- File Changes --

    M draft-ietf-quic-recovery.md (6)

-- Patch Links --

https://github.com/quicwg/base-drafts/pull/3033.patch
https://github.com/quicwg/base-drafts/pull/3033.diff

-- 
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/3033

----==_mimepart_5d7d3d2e6ce34_40293ff15c0cd964209760
Content-Type: text/html;
 charset=UTF-8
Content-Transfer-Encoding: 7bit

<p>As per <a class="user-mention" data-hovercard-type="user" data-hovercard-url="/hovercards?user_id=404610" data-octo-click="hovercard-link-click" data-octo-dimensions="link_type:self" href="https://github.com/tatsuhiro-t">@tatsuhiro-t</a>, since PING frames are not allowed in<br>
Initial/Handshake packets, one can use an empty CRYPTO frame when<br>
sending a probe when there is no other ack-eliciting frame to send.</p>
<p>It seems to me like this is something that is fairly easy to miss, so<br>
worth expanding the existing suggestion I think.</p>
<p>The alternative would be to allow PING frames in Initial/Handshake, but<br>
I figured we are maybe too late in the process for that kind of design<br>
change.</p>

<hr>

<h4>You can view, comment on, or merge this pull request online at:</h4>
<p>&nbsp;&nbsp;<a href='https://github.com/quicwg/base-drafts/pull/3033'>https://github.com/quicwg/base-drafts/pull/3033</a></p>

<h4>Commit Summary</h4>
<ul>
  <li>Suggest sending empty CRYPTO frames in Initial/Handshake packets</li>
</ul>

<h4>File Changes</h4>
<ul>
  <li>
    <strong>M</strong>
    <a href="https://github.com/quicwg/base-drafts/pull/3033/files#diff-0">draft-ietf-quic-recovery.md</a>
    (6)
  </li>
</ul>

<h4>Patch Links:</h4>
<ul>
  <li><a href='https://github.com/quicwg/base-drafts/pull/3033.patch'>https://github.com/quicwg/base-drafts/pull/3033.patch</a></li>
  <li><a href='https://github.com/quicwg/base-drafts/pull/3033.diff'>https://github.com/quicwg/base-drafts/pull/3033.diff</a></li>
</ul>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/quicwg/base-drafts/pull/3033?email_source=notifications&amp;email_token=AFTOJK6TE5MQTRLDSQLRYPDQJU2K5A5CNFSM4IWYAGQ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLMTT2A">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/AFTOJK7DA5GQIYMUJ4AERPDQJU2K5ANCNFSM4IWYAGQQ">mute the thread</a>.<img src="https://github.com/notifications/beacon/AFTOJK5AUAM7FDVDWHI3JY3QJU2K5A5CNFSM4IWYAGQ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLMTT2A.gif" height="1" width="1" alt="" /></p>
<script type="application/ld+json">[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/quicwg/base-drafts/pull/3033?email_source=notifications\u0026email_token=AFTOJK6TE5MQTRLDSQLRYPDQJU2K5A5CNFSM4IWYAGQ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLMTT2A",
"url": "https://github.com/quicwg/base-drafts/pull/3033?email_source=notifications\u0026email_token=AFTOJK6TE5MQTRLDSQLRYPDQJU2K5A5CNFSM4IWYAGQ2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HLMTT2A",
"name": "View Pull Request"
},
"description": "View this Pull Request on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]</script>

----==_mimepart_5d7d3d2e6ce34_40293ff15c0cd964209760--

