IETF Logo Mail Archive

Re: [quicwg/base-drafts] Connection ID Garbage Collection (#1729)

erickinnear <notifications@github.com> Wed, 12 September 2018 00:42 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 C4E24130F7B for <quic-issues@ietfa.amsl.com>; Tue, 11 Sep 2018 17:42:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.01
X-Spam-Level:
X-Spam-Status: No, score=-8.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, T_DKIMWL_WL_HIGH=-0.01] 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 H53zzMcmsquG for <quic-issues@ietfa.amsl.com>; Tue, 11 Sep 2018 17:42:23 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B624130F7F for <quic-issues@ietf.org>; Tue, 11 Sep 2018 17:42:17 -0700 (PDT)
Date: Tue, 11 Sep 2018 17:42:16 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1536712936; bh=wiNS8OHn+AIg8ihOpTG2/HF5ikBxWDWlYDPftFgd5YY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=hEJv7+Et5Bqs6+sFp6bSBFDkRF+uQ3tA/klS+1BUax5P+hREJvQjKfDz9sS7h4uo6 rwzJ35MEpvKg6rGREG/icYWyjWtp1bw53dbpRo9YPzcxyQp3tO41eym4ptZeXWgH6f bgE/tweOCi8g4a/Yn+elujkS8dsmmabBTQyWTMnU=
From: erickinnear <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6b54057a9e53e5932d5798859f80eb10fb31147d92cf0000000117b022e892a169ce155ca63e@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1729/420472907@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1729@github.com>
References: <quicwg/base-drafts/issues/1729@github.com>
Subject: Re: [quicwg/base-drafts] Connection ID Garbage Collection (#1729)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b9860e859608_18693fe8792d45b4122731"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: erickinnear
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/WimkDFcFhWbibzTtT32a0QRm8bU>
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: Wed, 12 Sep 2018 00:42:26 -0000

I don't believe the repo has any access control applied to it, so I'm not sure what's happening there? Should be open to everyone. Also shouldn't matter at this point, but I don't think there's any ACLs applied. 

There've been quite a few roundtrips on getting everything ironed out, and it's taken longer than I think any of us would have liked. A lot of that can be attributed to my being slow about updating the actual text in the PR. 

@huitema, it seems like you may be referring to the Stream 0 design team, which wrapped up in June and has output included in -13. That is a completely different thing from the CID DT that started after Montreal in late July/early August and should hopefully be wrapping up about now. 

It seems like a lot of the claims and discussion are around that assumption, so perhaps we should re-evaluate and move onwards in light of (potentially) new information. 

-- 
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/1729#issuecomment-420472907

v2.23.0 | Report a Bug | By Email