Re: [quicwg/base-drafts] Do we still need Retry packets? (#1233)

ianswett <notifications@github.com> Mon, 19 March 2018 00:27 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 2E808126BFD for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 17:27:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.392
X-Spam-Level:
X-Spam-Status: No, score=-5.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 UAFde1fhV7ln for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 17:27:41 -0700 (PDT)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92566126579 for <quic-issues@ietf.org>; Sun, 18 Mar 2018 17:27:41 -0700 (PDT)
Date: Sun, 18 Mar 2018 17:27:40 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1521419260; bh=GsEOEftF9cjQHlAKDbIOhKnAAwlymMM/UmKLMSZ5FmI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=rX54uSLTNkY4m7sDoq2LqwSY3tfSPE27BlPmWcrIDgFvnzAunDOnCi5bDW8IPQh1E 1Bgx4jNI+WvEVfiRwKplkEsU3Ah6OkGiZLLl0sOENvzWkDtpQNrhimH/kcs+EmAvMq aVBiyuPLWRyml6+HPYd1YK0tv46yCycXmY3pduTo=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab93b51a927d329e2c472e3a39e4860702b8ea81d892cf0000000116c6c5fc92a169ce1241ad3b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1233/374070626@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1233@github.com>
References: <quicwg/base-drafts/issues/1233@github.com>
Subject: Re: [quicwg/base-drafts] Do we still need Retry packets? (#1233)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aaf03fc73ebd_47253fb5e6eb6f2811576e"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/moH7bP_h6qN3LtEgxNZI4btJalM>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 19 Mar 2018 00:27:43 -0000

I can't come up with a clear reason for them.  The crypto handshake is going to have to indicate that the reset is stateful or stateless, and the transport is going to have to respond accordingly, so I haven't been able to determine what value the extra packet type provides.

-- 
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/1233#issuecomment-374070626