IETF Logo Mail Archive

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

ianswett <notifications@github.com> Sat, 16 February 2019 21:24 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 3F44E13104E for <quic-issues@ietfa.amsl.com>; Sat, 16 Feb 2019 13:24:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 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_32=0.001, 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 NRcLhWAuQZqd for <quic-issues@ietfa.amsl.com>; Sat, 16 Feb 2019 13:24:45 -0800 (PST)
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 32914131006 for <quic-issues@ietf.org>; Sat, 16 Feb 2019 13:24:45 -0800 (PST)
Date: Sat, 16 Feb 2019 13:24:43 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1550352283; bh=jketyFZASuEN5Djak25Oe3Nsci+y8IJhEdLcjjBC/Es=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=jUm7HG99CG+Vylh6pnNZgBLOVkLFT3/fhGKu0NgrySxWzV7xziZLKrqOjiJ/eXCW4 D7g2kztzQy4Jlb/kkuldYc/rwWTjeyNNROtuJqH79BQDvbFlr7ylPcEIvnmbkH8INw +cDfdYTHnCtaqiPQYnxeJy6s2pSm9fh9Z89ZJdq0=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abc6c022d10f270fc10622b1290d93c828c8edc5d792cf000000011880419b92a169ce187d68e1@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/464387118@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_5c687f9ba53b2_19b63fc8484d45b8324310"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/3AUMUOjWg6A2Jjboe92sKYg8i9I>
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 21:24:51 -0000

@kazuho The server can also statelessly reset the connection if it has no state by 5-tuple, as you mention above.

I don't have a very strong feeling on this, but it seems like another thing we forbid that has some potentially valid uses with drawbacks we don't like.  Unless we think this is actively harmful, I'd prefer to allow this.

If a server never wants to transition to/from a 0-len CID, it's easy for it to do that.

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

v2.23.0 | Report a Bug | By Email