Re: [quicwg/base-drafts] TLS alert no_application_protocol is not always possible (#3580)

Lucas Pardue <> Thu, 16 April 2020 15:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F0B953A0BB8 for <>; Thu, 16 Apr 2020 08:31:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.175
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 92onw_iTz-6z for <>; Thu, 16 Apr 2020 08:31:35 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B64163A0BB7 for <>; Thu, 16 Apr 2020 08:31:35 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3EF1B66084E for <>; Thu, 16 Apr 2020 08:31:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; 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 <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3580/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-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: