Re: [quicwg/base-drafts] Define the use of generic TLS alerts (#3601)

David Schinazi <> Tue, 28 April 2020 19:07 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id EEDBF3A10B6 for <>; Tue, 28 Apr 2020 12:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.554
X-Spam-Status: No, score=-1.554 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_20=1.546, 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 7T65vfxLLNyJ for <>; Tue, 28 Apr 2020 12:07: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 F32253A09E1 for <>; Tue, 28 Apr 2020 12:06:42 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 3925F282CB6 for <>; Tue, 28 Apr 2020 12:06:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1588100802; bh=q2Zo/7VgTaQw8ZPqCV2pVn/rXI+4O6/KnOIsqNT29bE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u6cWATXGmNxaq93QGahS7qyn6iJ2oHro6I2JEFDuYqdOOMdmDkSr0yFEhXaq0qOrl PtymokcsgmMFRFsAsPRlstA14i41thz858VUfPg+kE3kFVk2fJOSgctcsQ67P2arU2 pk/KOZXjebu3IJffFcIEs+wk7ESLSrk2IvG+Xn6Y=
Date: Tue, 28 Apr 2020 12:06:42 -0700
From: David Schinazi <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3601/review/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] Define the use of generic TLS alerts (#3601)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ea87ec229b4a_1e333fdf1d0cd960879a2"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: DavidSchinazi
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: Tue, 28 Apr 2020 19:07:42 -0000

@DavidSchinazi commented on this pull request.

 The alert level of all TLS alerts is "fatal"; a TLS stack MUST NOT generate
 alerts at the "warning" level.
+QUIC permits the use of a generic code in place of a specific error code; see
+Section 11 of {{QUIC-TRANSPORT}}. For TLS alerts, this includes replacing any
+alert with a generic alert, such as handshake_failure (0x128 in QUIC).
+Endpoints might use a generic error code to avoid possibly exposing

should this might be a MAY?

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: