IETF Logo Mail Archive

Re: [quicwg/base-drafts] Detectable Stateless Resets (#3032)

MikkelFJ <notifications@github.com> Thu, 19 September 2019 17:33 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 EC670120236 for <quic-issues@ietfa.amsl.com>; Thu, 19 Sep 2019 10:33:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.353
X-Spam-Level:
X-Spam-Status: No, score=-6.353 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_20=1.546, 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
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 uEm1_dxlV7By for <quic-issues@ietfa.amsl.com>; Thu, 19 Sep 2019 10:33:15 -0700 (PDT)
Received: from out-19.smtp.github.com (out-19.smtp.github.com [192.30.252.202]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 20DEA120241 for <quic-issues@ietf.org>; Thu, 19 Sep 2019 10:33:14 -0700 (PDT)
Received: from github-lowworker-f144ac1.va3-iad.github.net (github-lowworker-f144ac1.va3-iad.github.net [10.48.16.59]) by smtp.github.com (Postfix) with ESMTP id 901A0520145 for <quic-issues@ietf.org>; Thu, 19 Sep 2019 10:33:13 -0700 (PDT)
Date: Thu, 19 Sep 2019 10:33:13 -0700
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7DXP4WURWS3HT3WDV3SD6GTEVBNHHB22URPQ@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3032/533232513@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3032@github.com>
References: <quicwg/base-drafts/issues/3032@github.com>
Subject: Re: [quicwg/base-drafts] Detectable Stateless Resets (#3032)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d83bbd982362_6c523fa8ba6cd96c879c"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/XMGpJXbTvJtmU-MjM6ekflgmM-U>
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: Thu, 19 Sep 2019 17:33:19 -0000

That is not a good assumption.

I have redundant servers that respawn should one go down either due to an error, or more likely, a software upgrade. While these are behind load balancers that hide their address, this is not always the case.

Therefore, server migration could be a very real thing. Now, it is not necessarily trivial to pass state to fail-over servers, but it does happen.


-- 
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/3032#issuecomment-533232513

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