Re: [quicwg/base-drafts] Retire My Own CID (#2645)

Nick Banks <notifications@github.com> Tue, 23 April 2019 20:32 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 209B01202E4 for <quic-issues@ietfa.amsl.com>; Tue, 23 Apr 2019 13:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.001 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_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 6cfIN33R8sSc for <quic-issues@ietfa.amsl.com>; Tue, 23 Apr 2019 13:32:15 -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 B2E74120157 for <quic-issues@ietf.org>; Tue, 23 Apr 2019 13:32:15 -0700 (PDT)
Date: Tue, 23 Apr 2019 13:32:14 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1556051534; bh=aKg6jhVmfuWjsVepG8YSeabR+RxOgyPwTY3rszMlYso=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RwnT310WBvGvC/93sAyy9aCZAE/A+JuesuLfgxmoVuRaC2klHJyAxRCx4mtGKKvx8 mr2iuKOtQa/w2olL93XqVwhRUGd7KPlGomKrcIwt4ilQNvDfkTsCY9kiYaOQRnU+5E mzAB8Nb9kMvCsGaiF7OwYsqahPT5lcXdTlpzU2KE=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2TM4HQYVLR5NMU3T52ZSUM5EVBNHHBUAUCHA@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2645/485962999@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2645@github.com>
References: <quicwg/base-drafts/issues/2645@github.com>
Subject: Re: [quicwg/base-drafts] Retire My Own CID (#2645)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5cbf764eafc21_28dd3fa45c2cd96438106d"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/NLDv90d9rZtJIwzFPsMm_Ls5FCw>
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: Tue, 23 Apr 2019 20:32:17 -0000

@MikeBishop it might but I don't like the idea that it's a request. If the peer doesn't do this, it is causing two partitions to have cross-partition access for an extended period of time. I don't want the peer to have that type of control. With the extension, even if it claims support, what's stopping it from not actually implementing it?

If the act of acknowledging the packet allows me to drop the CID, then they have a great incentive to do it properly. Otherwise the connection dies.

And finally, yes, I want it in the spec. Not optional. Back to the whole problem of I don't want the peer to control my perf.

-- 
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/2645#issuecomment-485962999