IETF Logo Mail Archive

Re: [quicwg/base-drafts] Make ALPN mandatory in QUIC-via-TLS (#2263)

Lucas Pardue <notifications@github.com> Thu, 27 December 2018 19:16 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 55EF0130E6A for <quic-issues@ietfa.amsl.com>; Thu, 27 Dec 2018 11:16:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.065
X-Spam-Level:
X-Spam-Status: No, score=-8.065 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.065, 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 ZfcFJqT5yhjX for <quic-issues@ietfa.amsl.com>; Thu, 27 Dec 2018 11:16:46 -0800 (PST)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8D060130E5F for <quic-issues@ietf.org>; Thu, 27 Dec 2018 11:16:46 -0800 (PST)
Date: Thu, 27 Dec 2018 11:16:45 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545938205; bh=RPcp5N+GJUFOOcLJPUc9WKTPq86H1XayWYy1dxjnwgg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=FB6ZPFl/0SqwrC1ZJNk6YQwq+uuPP8wQirX+QB7C08DfmRBI5etUNyEA6Vzmq/B0h 6iVoHmu6S4bu19pKa+E+EGDw5UpZml8IAlw7ZXms4gfsKhRw4FOy0NZiq1y+l7FsxE ddt7cA0sRS48y8zPScdwY8c3yuiY4v0ftqmwyo80=
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4e73c0866b6533bddc69068711a42f72caad64f492cf00000001183ce71d92a169ce1781f912@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2263/450213244@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2263@github.com>
References: <quicwg/base-drafts/issues/2263@github.com>
Subject: Re: [quicwg/base-drafts] Make ALPN mandatory in QUIC-via-TLS (#2263)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c25251d37822_66413fe6bb2d45c41540a7"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
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/BkGuDh7uDUKERkFNY3kT3L012H8>
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: Thu, 27 Dec 2018 19:16:49 -0000

@kazuho I don't see read any optionality, so perhaps this is the ambiguity in the spec. (FWIW optionality of client authentication is explicitly highlighted in that section).

I also share your concerns about mandating ALPN. There still seem to be a few open questions about de-multiplexing different UDP-based protocols when a server listens on the same port - how does ALPN for QUIC mitigate that?

We also have WIP like DATAGRAM frame that are proposing use of TP for enabling the transport-layer feature that could be used by an application to talk arbitrary protocols. 

It seems like ALPN is too rigid a model to support multiple application layers within a single QUIC connection.

-- 
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/2263#issuecomment-450213244

v2.30.2 | Report a Bug | By Email | System Status