IETF Logo Mail Archive

Re: A non-TLS standard is needed

Paul Vixie <paul@redbarn.org> Sun, 26 April 2020 19:27 UTC

Return-Path: <paul@redbarn.org>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CA043A0F1A for <quic@ietfa.amsl.com>; Sun, 26 Apr 2020 12:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 tgwoc8Bvv7R5 for <quic@ietfa.amsl.com>; Sun, 26 Apr 2020 12:27:18 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08C503A0F16 for <quic@ietf.org>; Sun, 26 Apr 2020 12:27:17 -0700 (PDT)
Received: from linux-9daj.localnet (vixp1.redbarn.org [24.104.150.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id BCAFBB074A; Sun, 26 Apr 2020 19:27:15 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: Töma Gavrichenkov <ximaera@gmail.com>
Cc: quic <quic@ietf.org>
Subject: Re: A non-TLS standard is needed
Date: Sun, 26 Apr 2020 19:27:15 +0000
Message-ID: <3122349.QDWD7Ophk7@linux-9daj>
Organization: none
In-Reply-To: <CALZ3u+ZGd=YWJFxLEivow9vXKU=5aAXJhcDYp4MPjpswuWWjKg@mail.gmail.com>
References: <tencent_458BB4AFD3E32DBAAEA3F09FAEF063800605@qq.com> <2208100.KEu4SK8F6j@linux-9daj> <CALZ3u+ZGd=YWJFxLEivow9vXKU=5aAXJhcDYp4MPjpswuWWjKg@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/M20p0H6ZZEJcpXs7Fp5_wcNEmLs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 26 Apr 2020 19:27:20 -0000

On Sunday, 26 April 2020 19:13:37 UTC Töma Gavrichenkov wrote:
> Peace,

and to you.

> On Sun, Apr 26, 2020, 9:57 PM Paul Vixie <paul@redbarn.org> wrote:
> > i was directed to the following i-d when i asked about QUIC manageability:
> > 
> > https://tools.ietf.org/html/draft-ietf-quic-manageability-06#section-3
> 
> To be honest, and with all due respect to everyone involved, the
> manageability draft wasn't properly updated for years (and the authors do
> not seem to respond to emails, though this could be possibly attributed to
> some sort of email filtering which is common those days).
> 
> To be specific, e.g. the section 4.4, as of today, still states that, to
> quote, "current practices in detection and mitigation of Distributed Denial
> of Service (DDoS) attacks generally involve passive measurement using
> network flow data", which is clearly not how it works, as everyone who has
> seen reCaptcha interruptions during application layer DDoS could witness.

yikes. i had no idea this was already an open issue.

> There's certain amount of hard work required to update this document before
> referencing it properly (I volunteer).

i'd review.

-- 
Paul

v2.23.0 | Report a Bug | By Email