Re: [quicwg/base-drafts] Connection ID Length changes (#2473)

martinduke <notifications@github.com> Sat, 16 February 2019 18:09 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 54920130F1C for <quic-issues@ietfa.amsl.com>; Sat, 16 Feb 2019 10:09:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.001
X-Spam-Level:
X-Spam-Status: No, score=-8.001 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_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 a4Gx-LzO5uss for <quic-issues@ietfa.amsl.com>; Sat, 16 Feb 2019 10:09:23 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3B1E130F06 for <quic-issues@ietf.org>; Sat, 16 Feb 2019 10:09:23 -0800 (PST)
Date: Sat, 16 Feb 2019 10:09:22 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1550340562; bh=MPZyTnP+Itz8R2gGLKH0ksk4/BBTWsXO6x6g38d4viA=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=OpqttR9VEhsA24YgW+HaQCGQqmxvhqkXlnqxd0AbWDuuQPNicLASlerVKXstDdCd1 1wGBgDGcr8IjwuQkS0/i2ykuAQ3XddCroa6skryAq+2pI0kZyLv6kIM+Ve5v09Skmf Ccbos+9uRUO52g7dtdxG+CBgIOzbR7YejxeCIsiA=
From: martinduke <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9303c54ee0534fc53ccea596e55d932700f1597092cf00000001188013d292a169ce187d68e1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2473/464368407@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2473@github.com>
References: <quicwg/base-drafts/issues/2473@github.com>
Subject: Re: [quicwg/base-drafts] Connection ID Length changes (#2473)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c6851d2574ab_700c3ff4608d45c04407eb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: martinduke
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/dHaSBu8CxlUo8bD1BQ8rTLURGtM>
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: Sat, 16 Feb 2019 18:09:25 -0000

Either I have been very unclear, or I am proposing something that makes a simple error so that it is confusing everybody. Here is what I am proposing to allow (CIDs are letters)

Client                                                                                                    Server
[ Connection already setup; client has no CID ]
IP: 1.1.1.1 to 2.2.2.2 (DCID A) ----->
           (contains NEW_CONN_ID B)
                                                                              <--- IP: 2.2.2.2 to 1.1.1.1 (no DCID)
                                                                                       (contains NEW_CONN_ID C)
(exchange continues with IP addresses above, with no CID to client and CID A to server)
(then there's an address change)
IP: 3.3.3.3 to 2.2.2.2 (DCID C) -------->
                                                                               <---- IP: 2.2.2.2 to 3.3.3.3 (DCID B)

This is the case I am concerned about. I do not see, at the moment, any reason why switching "client" and "server" above should make a difference.

What I am definitely NOT proposing is that an endpoint migrate while never accepting a non-ZL CID.

-- 
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/2473#issuecomment-464368407