Re: [quicwg/base-drafts] Specify DCID of 0-RTT packets (#2398)

Mike Bishop <notifications@github.com> Fri, 08 February 2019 21:10 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 20F99131012 for <quic-issues@ietfa.amsl.com>; Fri, 8 Feb 2019 13:10:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.597
X-Spam-Level:
X-Spam-Status: No, score=-6.597 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_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 Ki13dGYzb0Ko for <quic-issues@ietfa.amsl.com>; Fri, 8 Feb 2019 13:10:39 -0800 (PST)
Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 65704130FFA for <quic-issues@ietf.org>; Fri, 8 Feb 2019 13:10:39 -0800 (PST)
Date: Fri, 08 Feb 2019 13:10:38 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1549660238; bh=UI3VbDP52glfqOs7VJUIZeAAMvenHghaiZ82CVzfpFs=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=M7/A8djS8pN71DMcQFDeT+94+WCjQu5YT4r8aNXpBBuBcmPLTZXaDwKa7lgtKdp20 yJl5cfSMrbivkKuYE8tkPnf+quWA/0J2qPTmiAyRt8EXq9NpV5+lTKhGI+9zAcY3Y7 FeL+Z6XC3VnMeVRdIHB/HpIpnjjDyXUUIYCqg52k=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6ee5d76189cf662e539d4f323309e037213b6ada92cf000000011875b24e92a169ce182664e3@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2398/461947986@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2398@github.com>
References: <quicwg/base-drafts/issues/2398@github.com>
Subject: Re: [quicwg/base-drafts] Specify DCID of 0-RTT packets (#2398)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5df04e31aa4_430f3f8e03ed45c4109445"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/JeMZ5qBoaOm2DDc_zeNn_kpIXjs>
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: Fri, 08 Feb 2019 21:10:41 -0000

Are you proposing that the client should get a CID along with the NewSessionTicket (or the NEW_TOKEN)?  That's been discussed before, and while it makes sense to me, it means that load balancers need to be able to differentiate the two types (and potentially sizes) of CID.

On the whole, I think this is a promising direction, but perhaps not needed for v1.

-- 
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/2398#issuecomment-461947986