Re: [quicwg/base-drafts] TLS alert no_application_protocol is not always possible (#3580)
Lucas Pardue <notifications@github.com> Thu, 16 April 2020 15:31 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 F0B953A0BB8 for <quic-issues@ietfa.amsl.com>; Thu, 16 Apr 2020 08:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.175
X-Spam-Level:
X-Spam-Status: No, score=-2.175 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.168, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 92onw_iTz-6z for <quic-issues@ietfa.amsl.com>; Thu, 16 Apr 2020 08:31:35 -0700 (PDT)
Received: from out-23.smtp.github.com (out-23.smtp.github.com [192.30.252.206]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B64163A0BB7 for <quic-issues@ietf.org>; Thu, 16 Apr 2020 08:31:35 -0700 (PDT)
Received: from github-lowworker-f1f7af9.ash1-iad.github.net (github-lowworker-f1f7af9.ash1-iad.github.net [10.56.111.13]) by smtp.github.com (Postfix) with ESMTP id 3EF1B66084E for <quic-issues@ietf.org>; Thu, 16 Apr 2020 08:31:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1587051094; bh=j0VIeSq1La7FH4Vn+kiG3KQXePSo0Fk7kdzvyVxkIwM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RVS/RQrTEHpz65DqNQqWypHwLkp3jqUw9ubhU6yLhcL1SHiNo/WZQMdo7hRDZxSkQ HG/lxiumQ7xZxWFRV78nfB6z4z/NcCRH7T/9i3rVyxv3oaZUtgDKqToRXviMNa63E8 6vDqXPzb3f46V23AWvC+vJjJNgFo8l8g1Xa1gfUo=
Date: Thu, 16 Apr 2020 08:31:34 -0700
From: Lucas Pardue <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2VIBSNRFU7S32VKNF4URNVNEVBNHHCHP77D4@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3580/614725441@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3580@github.com>
References: <quicwg/base-drafts/issues/3580@github.com>
Subject: Re: [quicwg/base-drafts] TLS alert no_application_protocol is not always possible (#3580)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5e987a562e5c7_44933fca58acd96c1999f9"; 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/viMefZSI3UefutW8kyRJN_oCJBw>
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, 16 Apr 2020 15:31:37 -0000
To follow up with a way to resolve this. I don't believe we need to change any normative language and so this is not a design issue. I'll leave it to editors' discretion on whether there is any editorial work required to address the original concern. -- 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/3580#issuecomment-614725441
- [quicwg/base-drafts] TLS alert no_application_pro… Andrew Macedonia
- Re: [quicwg/base-drafts] TLS alert no_application… Martin Thomson
- Re: [quicwg/base-drafts] TLS alert no_application… Andrew Macedonia
- Re: [quicwg/base-drafts] TLS alert no_application… Martin Thomson
- Re: [quicwg/base-drafts] TLS alert no_application… Andrew Macedonia
- Re: [quicwg/base-drafts] TLS alert no_application… Lucas Pardue
- Re: [quicwg/base-drafts] TLS alert no_application… Lucas Pardue
- Re: [quicwg/base-drafts] TLS alert no_application… Martin Thomson
- Re: [quicwg/base-drafts] TLS alert no_application… Martin Thomson
- Re: [quicwg/base-drafts] TLS alert no_application… Kazuho Oku
- Re: [quicwg/base-drafts] TLS alert no_application… Lucas Pardue
- Re: [quicwg/base-drafts] TLS alert no_application… Kazuho Oku
- Re: [quicwg/base-drafts] TLS alert no_application… martinduke
- Re: [quicwg/base-drafts] TLS alert no_application… Lucas Pardue
- Re: [quicwg/base-drafts] TLS alert no_application… ekr
- Re: [quicwg/base-drafts] TLS alert no_application… Martin Thomson