[quicwg/base-drafts] Can Server Require Connection ID to be Included in Packets Sent by Clients? (#789)

Nick Banks <notifications@github.com> Fri, 22 September 2017 14:15 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 C314013446E for <quic-issues@ietfa.amsl.com>; Fri, 22 Sep 2017 07:15:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.616
X-Spam-Level:
X-Spam-Status: No, score=-5.616 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_28=1.404, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 YysIryIfxuFi for <quic-issues@ietfa.amsl.com>; Fri, 22 Sep 2017 07:15:18 -0700 (PDT)
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2-ext8.iad.github.net [192.30.252.199]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4877134478 for <quic-issues@ietf.org>; Fri, 22 Sep 2017 07:15:02 -0700 (PDT)
Date: Fri, 22 Sep 2017 07:15:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1506089702; bh=uHnXqu+WUCRmLbdjO9RLni0hU97DIrTrzhH+2c3eS1s=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=QMGn/cSQe7rNGnp6Mnt5IvzcOL94WdqbO25g2nfhI4D23Ft2G84/0IrvweId1ER3k RdBXdKZ6/HNs+vzVsFdldeExPgY6WGmYmpiQp/+hRHk7iFNBxjmrr4yBM2nNbxB6wn AAFg3aP/UglF2NAypuvjQ6jRTv7kGQPFcN+unObA=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab2139ea960c6dbc4a49a4c9511b1e7e2cef1a971a92cf0000000115dcdce592a169ce0f7cacf0@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/789@github.com>
Subject: [quicwg/base-drafts] Can Server Require Connection ID to be Included in Packets Sent by Clients? (#789)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_59c51ae63ba1_78ed3f84d5e14f801246b"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/yrDpBascQCRrSgQe4l6JerkBI6I>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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, 22 Sep 2017 14:15:20 -0000

This is slightly related to #659.

Is it reasonable/acceptable for a server implementation to require that a client always include the connection ID? If so, what exactly should it do if it receives a new connection where the client specified `omit_connection_id` in its transport parameters? Should it drop the connection? Send an error back (if so, what error)?

It seems to me that if we want to allow servers to restrict the usage of `omit_connection_id` by the client, we should probably have some mechanism to indicate the client the connection must include the connection ID. One possibility is a new transport parameters that is server specific that indicates connection id is required.

-- 
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/789