IETF Logo Mail Archive

Re: [quicwg/base-drafts] What to do if address of client changes while in draining state (#946)

Subodh Iyengar <notifications@github.com> Sun, 19 November 2017 22:33 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 12DA11205D3 for <quic-issues@ietfa.amsl.com>; Sun, 19 Nov 2017 14:33:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.396
X-Spam-Level:
X-Spam-Status: No, score=-3.396 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-2.8, 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 4AMxqYSnnFtF for <quic-issues@ietfa.amsl.com>; Sun, 19 Nov 2017 14:33:39 -0800 (PST)
Received: from o6.sgmail.github.com (o6.sgmail.github.com [192.254.113.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6BA3512009C for <quic-issues@ietf.org>; Sun, 19 Nov 2017 14:33:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=jmIWHDStRGdZeHIecfi/dAmisdg=; b=xJpgbHRNc5kVzI81 6tXXNCyMuTNuI+ZgihcT/4il9EoYqc+5BMFwDWiZkhrG0ok9f7w74b1NXBJY14rt QaKSYNcoIKlmTm3SU+jnSvfcQPKKc8O5+mhIyP+qb074f1a7KEwVkE/OROGEdbOv PXS0AIj8EC0hbyueztjSyBp61n0=
Received: by filter0831p1mdw1.sendgrid.net with SMTP id filter0831p1mdw1-1240-5A1206C2-3 2017-11-19 22:33:38.037102602 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id sgmnyRsXQUC-I7BfoNjFDQ for <quic-issues@ietf.org>; Sun, 19 Nov 2017 22:33:37.935 +0000 (UTC)
Date: Sun, 19 Nov 2017 22:33:38 +0000
From: Subodh Iyengar <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf9dea15eb922934ded32ad2e765a84219e457b2592cf000000011629c8c192a169ce10662b3b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/946/345555762@github.com>
In-Reply-To: <quicwg/base-drafts/issues/946@github.com>
References: <quicwg/base-drafts/issues/946@github.com>
Subject: Re: [quicwg/base-drafts] What to do if address of client changes while in draining state (#946)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a1206c1d2094_22d123fc0b269cf281884e0"; 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
tracking:
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak2c3t/mg55LsHIYdqyAPcGJE8/lg494/wZWX5 OWAI9IfvoSu2MQDyS9G1TJoP+pzknxs3o4wlFi/WyV5jmJoCxIPTkWMY00267ai3lB97ficaKfpol0 BUvGItL3g5GnAUqd9icF5YTVELzwHau3mnDzLIpcHPZbVKAyLoFTp8heeu/Au53Bov1LMTo4k1RN7P s=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/EPbRMl6rwj4oj_AfxiQJfnDslzY>
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, 19 Nov 2017 22:33:41 -0000

the connection close could be 1MSS big because of the close reason, and it seemed kind of icky to send a connection close to a random unauthenticated source address someone could send us a small packet and we would send them a larger connection close while the connection is draining. The client may have legitimately transition to a new address due to nat rebinding, however there would be no way to tell. That's the reason just exiting draining might be 1 legitimate option.

-- 
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/946#issuecomment-345555762

v2.23.0 | Report a Bug | By Email