IETF Logo Mail Archive

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

Subodh Iyengar <notifications@github.com> Sun, 18 March 2018 23: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 AD6E112D810 for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 16:27:21 -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 utxtvjLlLeeu for <quic-issues@ietfa.amsl.com>; Sun, 18 Mar 2018 16:27:20 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D84E11241F8 for <quic-issues@ietf.org>; Sun, 18 Mar 2018 16:27:19 -0700 (PDT)
Date: Sun, 18 Mar 2018 16:27:19 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1521415639; bh=rP2SQohHRpuSm6SxGQ4hHzewg+Q3RLg3QuCgPRUdg18=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=0I6Z48CcJQX80fm725ejItgzTEO6O3Dp1Irk2WjIyte1+U2VxWkUsIIBWcUopI34J DF7Kuv8xIRSuQ4cUTNLN9ZgbqHUYgAMhTzvhkL2mXLnDYeShp5xbDVoB4cPf09SldD JI0x2+iKu1q17STHgnSNNyr89zYvg8w4lGeEWA1Q=
From: Subodh Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab489619d794e525e4b01af543c08f1e3ced12c0c592cf0000000116c6b7d792a169ce1241ad3b@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/374066166@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_5aaef5d79fef_38dc2aad0ac58ec414403c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: siyengar
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/5IgCdDoKeQ67wbyntWYJx6JTEMo>
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: Sun, 18 Mar 2018 23:27:22 -0000

ya i agree with this. The TLS stack on the client already knows whether it is a stateful or a stateless retry, and can act accordingly. Serializing the information the client already knows into a frame type is redundant and error prone.

cc @mcmanus 

-- 
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-374066166

v2.46.0 | Report a Bug | By Email | System Status