Re: [quicwg/base-drafts] How do I generate an RST? (#2228)

Martin Thomson <notifications@github.com> Mon, 24 December 2018 06:21 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 3CA95130EC2 for <quic-issues@ietfa.amsl.com>; Sun, 23 Dec 2018 22:21:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.661
X-Spam-Level:
X-Spam-Status: No, score=-6.661 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, 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 e3JI6SfmvZ_q for <quic-issues@ietfa.amsl.com>; Sun, 23 Dec 2018 22:21:40 -0800 (PST)
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 7D716130EC1 for <quic-issues@ietf.org>; Sun, 23 Dec 2018 22:21:40 -0800 (PST)
Date: Sun, 23 Dec 2018 22:21:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545632499; bh=fU9vK2HDu197Bqm5rfwYZnMSCBUpgmCOak/kEU6hKHU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hDlmFFSvx6fSYw4hpjOR1NkCcjr7dAisRfbb61KlqlIFwWQ3hYt1LScERSEDw8XY+ IRFyaeU9dZDUCRYsBfN0ttPwI1jApfRcvEOaRrfKrF2jCTjpE5tMutSBhPrYcfj5k+ Yaqnl5PBn+EY9/DOhPXoez+VN0jKzeV4Yfi3EdiM=
From: Martin Thomson <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab5943c221ea062b0d2ebe3a76b3c87763f9bd2bee92cf0000000118383cf392a169ce177071b8@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2228/449691617@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2228@github.com>
References: <quicwg/base-drafts/issues/2228@github.com>
Subject: Re: [quicwg/base-drafts] How do I generate an RST? (#2228)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c207af3a5b5e_75363fb5f44d45c41484de"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinthomson
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/UkKtteDvLglsWtgmFpn_km4_c1c>
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: Mon, 24 Dec 2018 06:21:42 -0000

This is not that.  We know that some implementations use TCP half-closed in HTTP.  Some even rely on it to the point that things break if you don't do it.  Not that things don't break for those people, but they have a narrow set of peers that they interact with.

Of course, whether that set of endpoints is ALSO the same set of endpoints using CONNECT is hard to know.

-- 
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/2228#issuecomment-449691617