Re: [quicwg/base-drafts] Clarify response to a non-probing migration when no CIDs are available (#4788)

ianswett <notifications@github.com> Wed, 20 January 2021 23:58 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 8E6643A160E for <quic-issues@ietfa.amsl.com>; Wed, 20 Jan 2021 15:58:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.258
X-Spam-Level:
X-Spam-Status: No, score=-2.258 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, 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 RQIW8NSFzfvr for <quic-issues@ietfa.amsl.com>; Wed, 20 Jan 2021 15:58:38 -0800 (PST)
Received: from smtp.github.com (out-18.smtp.github.com [192.30.252.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 634C43A160B for <quic-issues@ietf.org>; Wed, 20 Jan 2021 15:58:38 -0800 (PST)
Received: from github.com (hubbernetes-node-f25a51f.va3-iad.github.net [10.48.110.15]) by smtp.github.com (Postfix) with ESMTPA id B61B6340629 for <quic-issues@ietf.org>; Wed, 20 Jan 2021 15:58:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1611187117; bh=3vuRLj5f0V8rWBBxWfdr4KD/FWONxIXc2I26xEIBZEw=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=EJPBdg8E1c5WD9RVQwhz9uV6h7VIBHt/aXAKWeguZrh3wkhbF9TrIk0+HBBWdr8ob ePNZykTGb0PmUdBE60uILvdsLVgmUQyHrqqNWy0KlzNKOYoVNKUdwiUTrSL8GXau8s 3p/rDzjo6bQhraFOr5cEocIu9Un2AhXVsrEdq9g8=
Date: Wed, 20 Jan 2021 15:58:37 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK7XFBHNLJT6ANE3CXF6CSSK3EVBNHHC6HBMWU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/4788/764044065@github.com>
In-Reply-To: <quicwg/base-drafts/issues/4788@github.com>
References: <quicwg/base-drafts/issues/4788@github.com>
Subject: Re: [quicwg/base-drafts] Clarify response to a non-probing migration when no CIDs are available (#4788)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_6008c3adb397a_5a1a049117"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/XOa8JnhOH117mBzWQm8YK_xWk2M>
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, 20 Jan 2021 23:58:40 -0000

Yes, that clarifies the issue when the CID does not change.  But that does not clarify the case when the CID does change and the responder has no more CIDs.

-- 
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/4788#issuecomment-764044065