Re: [quicwg/base-drafts] CID change still required in response to migration? (#2778)
MikkelFJ <notifications@github.com> Thu, 15 August 2019 05: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 936A3120044 for <quic-issues@ietfa.amsl.com>; Wed, 14 Aug 2019 22:50:34 -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 6farc3FT_slF for <quic-issues@ietfa.amsl.com>; Wed, 14 Aug 2019 22:50:33 -0700 (PDT)
Received: from out-24.smtp.github.com (out-24.smtp.github.com [192.30.252.207]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 04769120019 for <quic-issues@ietf.org>; Wed, 14 Aug 2019 22:50:33 -0700 (PDT)
Date: Wed, 14 Aug 2019 22:50:32 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1565848232; bh=hpguU7m5DphxmFy3MdF+zjfzU7R63v/FimRDtgDW3z8=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=l5N4unDzgn2n8yhx4ssHEDx35VPNSHNlIPslkbIc4kkdgvaCjUiAJDzxlTHcARjrU /l3SORy+rhjW+s8j7gNpi2zfHc6n6Uq1ysdPNWLvdUCdqrS8T+v+/SN5BpNV5aYTWE r+drByKo+X+QYBARjZpW10BPYr24VObFRC8gGebg=
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJKZLXOB7CYPCUUETZGN3MISSREVBNHHBWDXNEU@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2778/521523040@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2778@github.com>
References: <quicwg/base-drafts/issues/2778@github.com>
Subject: Re: [quicwg/base-drafts] CID change still required in response to migration? (#2778)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d54f2a8176b9_42823fc7970cd96c448477"; 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/EsuFVUiSRW8IzxAPzbu1_8Wjt3g>
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: Thu, 15 Aug 2019 05:50:35 -0000
> In reviewing this, I think we've messed up badly. We currently only mandate the use of a new connection ID for the initiator of a migration. A peer that responds to a connection migration has to change a connection ID if the initiator changed their connection ID. This has been discussed at length and while I tend to agree that this is not a good design, I believe things ended up as they are due to concerns about endless CID change loops. I think that can be prevented without too much complexity, but that argument was one of the drivers, as I recall. -- 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/2778#issuecomment-521523040
- [quicwg/base-drafts] CID change still required in… Tatsuhiro Tsujikawa
- Re: [quicwg/base-drafts] CID change still require… MikkelFJ
- Re: [quicwg/base-drafts] CID change still require… Tatsuhiro Tsujikawa
- Re: [quicwg/base-drafts] CID change still require… MikkelFJ
- Re: [quicwg/base-drafts] CID change still require… Tatsuhiro Tsujikawa
- Re: [quicwg/base-drafts] CID change still require… Eric Kinnear
- Re: [quicwg/base-drafts] CID change still require… Martin Thomson
- Re: [quicwg/base-drafts] CID change still require… Eric Kinnear
- Re: [quicwg/base-drafts] CID change still require… MikkelFJ
- Re: [quicwg/base-drafts] CID change still require… Mark Nottingham
- Re: [quicwg/base-drafts] CID change still require… Tatsuhiro Tsujikawa
- Re: [quicwg/base-drafts] CID change still require… Tatsuhiro Tsujikawa
- Re: [quicwg/base-drafts] CID change still require… Lars Eggert
- Re: [quicwg/base-drafts] CID change still require… Kazuho Oku
- Re: [quicwg/base-drafts] CID change still require… Tatsuhiro Tsujikawa
- Re: [quicwg/base-drafts] CID change still require… MikkelFJ
- Re: [quicwg/base-drafts] CID change still require… MikkelFJ
- Re: [quicwg/base-drafts] CID change still require… Lars Eggert
- Re: [quicwg/base-drafts] CID change still require… Martin Thomson
- Re: [quicwg/base-drafts] CID change still require… MikkelFJ
- Re: [quicwg/base-drafts] CID change still require… Martin Thomson
- Re: [quicwg/base-drafts] CID change still require… Kazuho Oku
- Re: [quicwg/base-drafts] CID change still require… Eric Kinnear
- Re: [quicwg/base-drafts] CID change still require… Mike Bishop
- Re: [quicwg/base-drafts] CID change still require… Martin Thomson