[quicwg/base-drafts] Don't levy requirements on non-QUIC TLS endpoints (#2174)
ekr <notifications@github.com> Fri, 14 December 2018 00: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 8005112E036 for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 16:24:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.056
X-Spam-Level:
X-Spam-Status: No, score=-8.056 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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 EV7UJxCAN4dh for <quic-issues@ietfa.amsl.com>; Thu, 13 Dec 2018 16:24:06 -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 B08E51286E7 for <quic-issues@ietf.org>; Thu, 13 Dec 2018 16:24:06 -0800 (PST)
Date: Thu, 13 Dec 2018 16:24:05 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1544747045; bh=/ojx/20/39JuHfMNINl6rM6JIYNRvtCaDcaKCsQApoQ=; h=Date:From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=xgA5CM7RhmbGTNrSLS0cucnFfgJjqMTCWoIPeI5J1YaDzwa/E1GaocfDdfI0VdHw3 yPugLPiaeDzLqRh7yJgNX3wVOFNkXx+YhWsJRB0BdGPTxxDRrCCcR983tifvaZjm8O DxhhXZ2jy8dDYYmDkQVGXbD9dAe7PWPeaV9bGNnA=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab36c405394cad0f9eff6b902c3c6f9cc30573389e92cf00000001182aba2592a169ce174cea1a@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2174@github.com>
Subject: [quicwg/base-drafts] Don't levy requirements on non-QUIC TLS endpoints (#2174)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c12f825caa09_4eaf3ff02f6d45c01653c8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/Jz0hOwvXw9aPRZcZHOZaEKouhP0>
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, 14 Dec 2018 00:24:09 -0000
Section 8.2 says:
```
Endpoints MUST NOT send this extension in a TLS connection that does not use
QUIC (such as the use of TLS with TCP defined in {{!TLS13}}). A fatal
unsupported_extension alert MUST be sent if this extension is received when the
transport is not QUIC.
```
However, this directly contradicts TLS 1.3 https://tools.ietf.org/rfcmarkup?doc=8446#section-4.1.2, which says:
```
Servers MUST ignore unrecognized extensions.
```
In order to say this, this document would need to Update 8446, and even then it doesn't make sense because the presumptive point of this rule is to detect attempts to negotiate QUIC with non-QUIC TLS endpoints, which don't need to conform to this RFC (and may predate it).
--
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/2174
- [quicwg/base-drafts] Don't levy requirements on n… ekr
- Re: [quicwg/base-drafts] Don't levy requirements … MikkelFJ
- Re: [quicwg/base-drafts] Don't levy requirements … Kazuho Oku
- Re: [quicwg/base-drafts] Don't levy requirements … ekr
- Re: [quicwg/base-drafts] Don't levy requirements … Martin Thomson
- Re: [quicwg/base-drafts] Don't levy requirements … Kazuho Oku
- Re: [quicwg/base-drafts] Don't levy requirements … ekr
- Re: [quicwg/base-drafts] Don't levy requirements … Martin Thomson
- Re: [quicwg/base-drafts] Don't levy requirements … Martin Thomson