Re: [quicwg/base-drafts] Mandate using a new connection ID on migration (#2413)
MikkelFJ <notifications@github.com> Tue, 05 February 2019 04:59 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 B5D62130DFA for <quic-issues@ietfa.amsl.com>; Mon, 4 Feb 2019 20:59:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Level:
X-Spam-Status: No, score=-11.149 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, 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 eRIv7e73EkMx for <quic-issues@ietfa.amsl.com>; Mon, 4 Feb 2019 20:59:25 -0800 (PST)
Received: from out-6.smtp.github.com (out-6.smtp.github.com [192.30.252.197]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6EC1C130DEF for <quic-issues@ietf.org>; Mon, 4 Feb 2019 20:59:25 -0800 (PST)
Date: Mon, 04 Feb 2019 20:59:24 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549342764; bh=CjSnS9oRljaUnXmfE16lOfm6LgByw12R69XWmdu/K7g=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=YySRpYDbqW3jKFI37+AyUNI+sgYP4dMbNfkmXJA41lzWBIrQpfGNE5B/iDlLK+ShM gkcrBKuZAk9bYXw9N06DrUxwW6aHtVRp6ufx+XqLJe7r4qJJOsQ3CyHKtQ6xbUVphR CLlwpfT80ARjvHQ6WGsMH9dwj0jCgiTXOqICky2k=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab8979add27b264002b1327190bdb4d4cc62c46af292cf000000011870da2c92a169ce183ba2c6@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2413/460513453@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2413@github.com>
References: <quicwg/base-drafts/issues/2413@github.com>
Subject: Re: [quicwg/base-drafts] Mandate using a new connection ID on migration (#2413)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c59182c1c2a0_1dad3fbbf50d45bc1623ee"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
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/sT_xCYzfoTfEKfCdkwIu1OFpyRI>
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, 05 Feb 2019 04:59:28 -0000
> As for the perceived conflict, yeah, the text is not ideal. I'll find some way to reword it. Perhaps by observing that you can never run out of zero-length connection IDs. The intent is clearly to disallow avoidable migration on empty CIDs. Not running out would suggest keep using it, which is wrong. Otoh: if it is not required to use a new CID, it makes no sense to forbid empty CID, on migration. -- 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/2413#issuecomment-460513453
- [quicwg/base-drafts] Mandate using a new connecti… Martin Thomson
- Re: [quicwg/base-drafts] Mandate using a new conn… Igor Lubashev
- Re: [quicwg/base-drafts] Mandate using a new conn… erickinnear
- Re: [quicwg/base-drafts] Mandate using a new conn… Martin Thomson
- Re: [quicwg/base-drafts] Mandate using a new conn… Igor Lubashev
- Re: [quicwg/base-drafts] Mandate using a new conn… David Schinazi
- Re: [quicwg/base-drafts] Mandate using a new conn… MikkelFJ
- Re: [quicwg/base-drafts] Mandate using a new conn… Mike Bishop
- Re: [quicwg/base-drafts] Mandate using a new conn… MikkelFJ
- Re: [quicwg/base-drafts] Mandate using a new conn… Martin Thomson
- Re: [quicwg/base-drafts] Mandate using a new conn… Martin Thomson
- Re: [quicwg/base-drafts] Mandate using a new conn… Martin Thomson
- Re: [quicwg/base-drafts] Mandate using a new conn… Jana Iyengar
- Re: [quicwg/base-drafts] Mandate using a new conn… Jana Iyengar
- Re: [quicwg/base-drafts] Mandate using a new conn… Martin Thomson