Re:Re: Fast Address Validation - about
"Qing An" <anqing.aq@alibaba-inc.com> Fri, 01 November 2019 14:47 UTC
Return-Path: <anqing.aq@alibaba-inc.com>
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 98FAA1201A3 for <quic@ietfa.amsl.com>; Fri, 1 Nov 2019 07:47:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level:
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=alibaba-inc.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 IWTqlsE1ztle for <quic@ietfa.amsl.com>; Fri, 1 Nov 2019 07:47:22 -0700 (PDT)
Received: from out0-138.mail.aliyun.com (out0-138.mail.aliyun.com [140.205.0.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0200A120044 for <quic@ietf.org>; Fri, 1 Nov 2019 07:47:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572619635; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=X/xJDM8JxMT/qkuklk7fORPN9LakNzxKM6UAAbR88Qg=; b=WJcoyhXJoPetAKj7kGQW3iepm1UfNdU9BYwPAQD0PPKmeCgoYStlW9uvfD8oozl9fpZtdDmUdnvD2zidssFEv0dW0Ukh7WUzfD6IQF7h1oKipdtPxOLxWnOr5O4gPJPdz3deAerr49PLXY+5FyrrDuzLqXfTLM8jV52clYaoXP8=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R161e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03300; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=5; SR=0; TI=alimail_ios_2.COREAPIb4dc312a0dbd47fcbfcc9c12d14e889e;
Received: from WS-web (anqing.aq@alibaba-inc.com[alimail_ios_2.COREAPIb4dc312a0dbd47fcbfcc9c12d14e889e]) by e01l07449.eu6 at Fri, 01 Nov 2019 22:47:13 +0800
Date: Fri, 01 Nov 2019 22:47:13 +0800
From: Qing An <anqing.aq@alibaba-inc.com>
To: Töma Gavrichenkov <ximaera@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, mt <mt@lowentropy.net>, Max <max.ldp@alibaba-inc.com>
Message-ID: <cee17fee-fed3-497b-82fc-5deda3d0f565.anqing.aq@alibaba-inc.com>
Subject: Re:Re: Fast Address Validation - about
X-Priority: 3
X-Mailer: [Alimail-Mailagent revision 2765257]
MIME-Version: 1.0
In-Reply-To: <CALZ3u+ZaHzbNEzUsUa2bYXy2eB+fgkyzSDQir_mtTyLrrcAm7A@mail.gmail.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <CALZ3u+YyOQxA5zBxkhDj9-wObfqjxPxPyXH9PumaW79DNkKjsg@mail.gmail.com> <6ab3b6d6-7638-4b96-b2a3-4212f747a7af.anqing.aq@alibaba-inc.com>, <CALZ3u+ZaHzbNEzUsUa2bYXy2eB+fgkyzSDQir_mtTyLrrcAm7A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_24763_55ce3940_5dbc4571_356399"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jpdefLzQZsurJhIM4ztmJYUJZ6c>
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: Fri, 01 Nov 2019 14:47:25 -0000
For initial flood, there are approaches like source address statistics and speed limitation. ------------------Original Mail ------------------ Sender:Töma Gavrichenkov <ximaera@gmail.com> Send Date:Fri Nov 1 22:01:08 2019 Recipients:Qing An <anqing.aq@alibaba-inc.com> CC:IETF QUIC WG <quic@ietf.org>, jri.ietf <jri.ietf@gmail.com>, mt <mt@lowentropy.net>, 刘大鹏(鹏成) <max.ldp@alibaba-inc.com> Subject:Re: Fast Address Validation - about On Fri, Nov 1, 2019, 4:26 PM Qing An <anqing.aq@alibaba-inc.com> wrote: Right, client address validation can provide protection against floods, but today's server often has other approaches to handle floods. Speaking of Hello flood (and SYN flood), what particular approaches do you have in mind? -- Töma
- Fast Address Validation - about Qing An
- Re: Fast Address Validation - about Mikkel Fahnøe Jørgensen
- RE: Fast Address Validation - about Mike Bishop
- Re: Fast Address Validation - about Martin Thomson
- Re: Fast Address Validation - about Qing An
- RE: Fast Address Validation - about Mike Bishop
- Re: Fast Address Validation - about Qing An
- Re: Fast Address Validation - about Marten Seemann
- Re: Fast Address Validation - about Töma Gavrichenkov
- Re: Fast Address Validation - about Qing An
- Re: Fast Address Validation - about Qing An
- Re: Fast Address Validation - about Mikkel Fahnøe Jørgensen
- Re: Fast Address Validation - about Töma Gavrichenkov
- Re:Re: Fast Address Validation - about Qing An
- Re:Re: Fast Address Validation - about Qing An
- Re:Re: Fast Address Validation - about Mikkel Fahnøe Jørgensen
- Re: Re: Fast Address Validation - about Töma Gavrichenkov
- Re: Fast Address Validation - about Töma Gavrichenkov
- Re: Fast Address Validation - about Jana Iyengar
- Re:Re: Fast Address Validation - about Qing An
- Re:Re:Re: Fast Address Validation - about Qing An
- Re: Fast Address Validation - about Christian Huitema
- Re:Re: Fast Address Validation - about Qing An
- Re: Fast Address Validation - about Christian Huitema
- Re:Re:Re: Fast Address Validation - about Mikkel Fahnøe Jørgensen
- Re: Fast Address Validation - about Christian Huitema