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

ekr <notifications@github.com> Mon, 24 December 2018 14:18 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 E44C8130F00 for <quic-issues@ietfa.amsl.com>; Mon, 24 Dec 2018 06:18:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.065
X-Spam-Level:
X-Spam-Status: No, score=-8.065 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_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 fmS7As5pF5LH for <quic-issues@ietfa.amsl.com>; Mon, 24 Dec 2018 06:18:43 -0800 (PST)
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 446F41271FF for <quic-issues@ietf.org>; Mon, 24 Dec 2018 06:18:43 -0800 (PST)
Date: Mon, 24 Dec 2018 06:18:42 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545661122; bh=VfG7syAh+RZGpUDW5ETwFVmRXz4mMNE4OUPglOjbI2c=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=KOtPw+ahxJuS/jRJl2UmqqNSUG/jixygxMzh+59pnlpgU+EQC14Rj70Y4W/lkPBIW gcWPN18pfulzxKFgYX+4GVNSVefmQn407X+Yk1USSOaqJvZZG+1lneIbyXrgHODShT unm6wfDVNRb+60Uarf0Yy5NalTLpEXGXf6I3lLa0=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abb47ed588fbf8cd60b4b75c216502ecb4eb3cf9d892cf000000011838acc292a169ce177071b8@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/449739438@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_5c20eac236be6_42f13f894a8d45c42084bc"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/8QeY8JXQ4BHJukd_pNvblt6LWIA>
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 14:18:45 -0000

Note that this particular issue is not about half-closed. In half-closed,
you generate a FIN and then keep receiving data. This is about sending an
RST.

On Sun, Dec 23, 2018 at 10:21 PM Martin Thomson <notifications@github.com>
wrote:

> 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 authored the thread.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/2228#issuecomment-449691617>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/ABD1oWZ-xOHvA2hcEMiW0hrPR7Hq2xiBks5u8HJxgaJpZM4ZdD1t>
> .
>


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