Re: [quicwg/base-drafts] Handling of Retire Prior To field (#3046)

Kazuho Oku <notifications@github.com> Tue, 17 September 2019 16:50 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 AB695120108 for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 09:50:45 -0700 (PDT)
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 eDs6j8Cs9hte for <quic-issues@ietfa.amsl.com>; Tue, 17 Sep 2019 09:50:44 -0700 (PDT)
Received: from out-18.smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C8E28120112 for <quic-issues@ietf.org>; Tue, 17 Sep 2019 09:50:21 -0700 (PDT)
Date: Tue, 17 Sep 2019 09:50:20 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1568739020; bh=GYOkcfU62s7RSZZFQZ01er0p8kH9in39BoW7pg1ui30=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RdaxfEVAmFRkcqDVRqSVuXE5ENxpMFH9pVM0RrjJegkDefRDBqsM4cWxe4g8NPS4k fAaXCxIavVGZk2H5OyqX97gSizS29aBG22jcmssNuLuFvHav4jXvpNjf6jo5T8HRoM fdcCYt1ATjI2do6ZVPT4pR3rrT3YS5Vvw/rH/bTo=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZUUDWTIMCW2GBGMRN3RZAUZEVBNHHB27HBVI@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3046/532305468@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3046@github.com>
References: <quicwg/base-drafts/issues/3046@github.com>
Subject: Re: [quicwg/base-drafts] Handling of Retire Prior To field (#3046)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d810ecce2b73_142e3fb52c8cd964210959"; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/_kZiNhxSvnJjAMjUMkFM0kbpXxk>
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, 17 Sep 2019 16:50:46 -0000

My personal take is that it would be nice if the processing of NEW_CONNECTION_ID frame and RETIRE_CONNECTION_ID frame can be an optional feature. QUIC is already very complex, and it would be beneficial to have some features being optional, in sense that endpoints can simply discard certain frames when not implementing certain features.

IIUC, at the moment, these two frames are optional for an endpoint that do not support migration.

OTOH, from the robustness viewpoint of the protocol, it does make sense to change the text to MUST. We might have already crossed the river by introducing the Retire Prior To field.

The third option is to add a TP that indicates if an endpoint supports retirement of connection IDs...

-- 
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/3046#issuecomment-532305468