IETF Logo Mail Archive

Re: [quicwg/base-drafts] Allow the Transport to Stop/Reset a Stream? (#3291)

Geoff Kizer <notifications@github.com> Thu, 12 December 2019 21:23 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 D07D2120121 for <quic-issues@ietfa.amsl.com>; Thu, 12 Dec 2019 13:23:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.382
X-Spam-Level:
X-Spam-Status: No, score=-6.382 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, 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
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 LRqxXc8MUWQh for <quic-issues@ietfa.amsl.com>; Thu, 12 Dec 2019 13:23:39 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41B7B120123 for <quic-issues@ietf.org>; Thu, 12 Dec 2019 13:23:39 -0800 (PST)
Received: from github-lowworker-9bcb4a1.ac4-iad.github.net (github-lowworker-9bcb4a1.ac4-iad.github.net [10.52.25.84]) by smtp.github.com (Postfix) with ESMTP id 5CC3FC60B3C for <quic-issues@ietf.org>; Thu, 12 Dec 2019 13:23:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1576185818; bh=8n144y8SKdxP2KSrpKh/NpP36pgNbrSXC3VuYCWDyek=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=wWNL/0y0hcJYOYl59AaGWmMRAfOdIYDazaDcqzOiYLWKXqNh84VSL06mSovslmV3+ uTdljBZAviMCduRkkvleSFQhh19dwEhO9xSdLEyqR9a6clo5qO5frZC8Nk8493PToD U1rC1NFcU9WgGk2Wy3MYPpRMWk0pZ0l3C0z/cFVs=
Date: Thu, 12 Dec 2019 13:23:38 -0800
From: Geoff Kizer <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5UD3NCO5FGKT2LHIF377RFVEVBNHHB7WKXVY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3291/565192856@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3291@github.com>
References: <quicwg/base-drafts/issues/3291@github.com>
Subject: Re: [quicwg/base-drafts] Allow the Transport to Stop/Reset a Stream? (#3291)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5df2afda4c2b6_8e83f9f676cd964100286"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: geoffkizer
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/J27Pc4GC5jt8-nHDLefa4m3AYsA>
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, 12 Dec 2019 21:23:41 -0000

> It is still outside the transport layer.

The point I'm trying to make here is that the transport layer can detect that a stream is no longer usable because the object that represents it has been garbage collected.

This is a *good thing*, because it helps detect and prevent leaks.

The problem is that the transport layer can't really do anything except kill the connection, which makes it more difficult to diagnose what caused the problem.

-- 
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/3291#issuecomment-565192856

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