Re: [quicwg/base-drafts] Does it make sense to try 0-RTT after Retry? (#2842)

Kazuho Oku <> Tue, 25 June 2019 00:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 01BE7120158 for <>; Mon, 24 Jun 2019 17:50:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.999
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_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id iQ4kdVQUTNpF for <>; Mon, 24 Jun 2019 17:50:33 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2CBEB12004D for <>; Mon, 24 Jun 2019 17:50:33 -0700 (PDT)
Date: Mon, 24 Jun 2019 17:50:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1561423832; bh=71i7UvTZzn21EUE8u5aLnQ8JCfBadu02D3OAcOKc0gY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ezrZRQ1FJu7iZg8QhVbcZ8lFKwS9ty5/8eF9D0Vr81KkybAtZEbSFJcRnBCa2g5Wq 4EZRnDRnh8VezJxSAoxDyXfliwwZHCDicV1fF0hy2ED1Qn17Xq8XWcaMXdpLsyr9r5 erQd3PRnci7YwWkN/saLt05ZbvD2TliYnxbDjs5o=
From: Kazuho Oku <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2842/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Does it make sense to try 0-RTT after Retry? (#2842)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d116fd8323a7_52d33fc2002cd95c23945"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 Jun 2019 00:50:35 -0000

> In #2831 (review), @MikeBishop points out that after a Retry, all 0-RTT packets sent in the first flight are still valid, although they will probably have been dropped by the server (unless there's significant reordering).

I am not sure if I agree with the observation. The transport draft states that _a server MAY send Retry packets in response to Initial and 0-RTT packets. A server can either discard or buffer 0-RTT packets that it receives ([section 17.2.5](

I am not sure if I like this ambiguity (because I think most if not all of us will be dropping 0-RTT packets that carry the original DCID when sending a Retry), but IMO the draft is clear.

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: