IETF Logo Mail Archive

Re: [quicwg/base-drafts] CID change still required in response to migration? (#2778)

Tatsuhiro Tsujikawa <notifications@github.com> Mon, 10 June 2019 07:39 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 8A15B12014A for <quic-issues@ietfa.amsl.com>; Mon, 10 Jun 2019 00:39:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Level:
X-Spam-Status: No, score=-6.463 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 0WT8oHPKDVix for <quic-issues@ietfa.amsl.com>; Mon, 10 Jun 2019 00:39:51 -0700 (PDT)
Received: from out-3.smtp.github.com (out-3.smtp.github.com [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE348120088 for <quic-issues@ietf.org>; Mon, 10 Jun 2019 00:39:50 -0700 (PDT)
Date: Mon, 10 Jun 2019 00:39:49 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1560152389; bh=eIAWdxgLaRZObom9SrjdTUo4ly+MAwU3gEyTWaGrG1I=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=NJCtsGj/MxaNiREWS7NABYaghmIMY6E5jxPmgWQu7lmJdHvdYelgymk1BYgnOgeQM E6MulOC1M8uz2mqGLcC3otP69i+BFsL+yVMMoV46teZ8h2UoljnU4URxUW+OxytNVv apWCGkWGraOzyGhJsSD3kenjy3acj9Sm14rCJkpg=
From: Tatsuhiro Tsujikawa <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK5CDQQ7ENGECSDVG2N3BM54LEVBNHHBWDXNEU@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/500322748@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_5cfe09455d361_15f83fc5acccd95c1394043"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: tatsuhiro-t
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/0RC_VXkZUe8_5j2McitQZO6eX5U>
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: Mon, 10 Jun 2019 07:39:53 -0000

So what does implementation actually need to do in response to migrating peer?
Just keep using same CID or not?  Use same CID to do path validation?
I know that peer can change CID at anytime it likes.


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

v2.23.0 | Report a Bug | By Email