IETF Logo Mail Archive

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 22:16 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 BB65A3A1581 for <quic-issues@ietfa.amsl.com>; Wed, 20 Jan 2021 14:16:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.804
X-Spam-Level:
X-Spam-Status: No, score=-1.804 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_20=1.546, 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 PRPKWytp2EoD for <quic-issues@ietfa.amsl.com>; Wed, 20 Jan 2021 14:16:19 -0800 (PST)
Received: from smtp.github.com (out-21.smtp.github.com [192.30.252.204]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B3EE3A1513 for <quic-issues@ietf.org>; Wed, 20 Jan 2021 14:16:19 -0800 (PST)
Received: from github.com (hubbernetes-node-c0cb15c.ac4-iad.github.net [10.52.102.51]) by smtp.github.com (Postfix) with ESMTPA id AC343520478 for <quic-issues@ietf.org>; Wed, 20 Jan 2021 14:16:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1611180978; bh=ugSh1Z2xLt3IhZcBlY/+eBGzJOBywnwEoyM1aFIJ5F8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=HWCFinFGuIGiuslrxfuNdVA+F/1hvyKGeV4SFgJjDjb1qXJSFR2uDbcI++Y8ucgrh I0bAoW7+8ZJLlqlPRD6GkIIjoFlWYsf87rStFxbbdZj/CqfbrfVPMBvn39Kx+EC8K3 oDi3bUBcudsSXR0df4l9feUA9hkUR0Hyp49M7Lao=
Date: Wed, 20 Jan 2021 14:16:18 -0800
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZNR4S5SHGIKYSMF5N6CSGLFEVBNHHC6HBMWU@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/763985965@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_6008abb2a88f3_5b1a04162035"; 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/2ocL7EvueyEC6m00quo_f9WoWHw>
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 22:16:21 -0000

Later in 9.5, there's also this text that is relevant, but I don't think it clarifies how to resolve the MUSTs.

"   An endpoint that exhausts available connection IDs cannot probe new
   paths or initiate migration, nor can it respond to probes or attempts
   by its peer to migrate.  To ensure that migration is possible and
   packets sent on different paths cannot be correlated, endpoints
   SHOULD provide new connection IDs before peers migrate; see
   Section 5.1.1.  If a peer might have exhausted available connection
   IDs, a migrating endpoint could include a NEW_CONNECTION_ID frame in
   all packets sent on a new network path."

-- 
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-763985965

v2.23.0 | Report a Bug | By Email