Re: [quicwg/base-drafts] Make ALPN mandatory in QUIC-via-TLS (#2263)
Kazuho Oku <notifications@github.com> Thu, 27 December 2018 18:26 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 546EE12DD85 for <quic-issues@ietfa.amsl.com>; Thu, 27 Dec 2018 10:26:35 -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 YkiC8r7d9Dkh for <quic-issues@ietfa.amsl.com>; Thu, 27 Dec 2018 10:26:33 -0800 (PST)
Received: from out-7.smtp.github.com (out-7.smtp.github.com [192.30.252.198]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A031A126F72 for <quic-issues@ietf.org>; Thu, 27 Dec 2018 10:26:33 -0800 (PST)
Date: Thu, 27 Dec 2018 10:26:32 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1545935192; bh=igF09CLUssO0vmK/XoyN0W/15t+oagpBmqJNRWpakp4=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=MqTMwkGZKl/u7qsbYuHon97vWdGcW3Du6sZKFO5i6m+Jhs60g0+UwFIlkpEN3Fy7f P6cDSEw95taMPxMpgL2V5o3mbY9DHXKMKqQ1sF4ETsrxVM0oLH9DQt1FctYCVAOwLS 60i9tkwwjiMao6UjhuEv3TIJvywMOaLH9WcHauJU=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab332cd36cff7e20736f27ee92a93ea6d9af94ea7e92cf00000001183cdb5892a169ce1781f912@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/450205280@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_5c251958a213f_385a3fd23c4d45c4641155"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
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/APhb3KuHaq9LwtcB50uLYz_NxeU>
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 18:26:36 -0000
@vasilvv > The root issue in TCP or regular UDP is that the application protocol is multiplexed by the port, but the port is never a certain indicator of the protocol. ALPN, on other hand, is exactly that. Since there are no b/c concerns in our case, can we make ALPN mandatory in QUIC? This could save us a lot of security issues down the road. I would be concerned of the side-effects that we might have. RFC 7301 (ALPN) requires Expert Review for registering new application protocols. My concern is that mandating the "use" of ALPN might forbid QUIC being used in in-house protocols. @LPardue My interpretation would be the same as @marten-seemann, that the intent of the text is to state that the handshake protocol must protect the protocol negotiation _when_ it is negotiated. -- 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-450205280
- [quicwg/base-drafts] Make ALPN mandatory in QUIC-… Victor Vasiliev
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Lucas Pardue
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Marten Seemann
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Lucas Pardue
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Kazuho Oku
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Lucas Pardue
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Martin Thomson
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Lucas Pardue
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… MikkelFJ
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Victor Vasiliev
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… erickinnear
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Kazuho Oku
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Martin Thomson
- Re: [quicwg/base-drafts] Make ALPN mandatory in Q… Martin Thomson