Re: [Dots] Fwd: New Version Notification for draft-reddy-dots-telemetry-00.txt

kaname nishizuka <kaname@nttv6.jp> Mon, 22 July 2019 14:55 UTC

Return-Path: <kaname@nttv6.jp>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B94241202BB for <dots@ietfa.amsl.com>; Mon, 22 Jul 2019 07:55:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level:
X-Spam-Status: No, score=-1.989 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, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nttv6.jp
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 RbWqEeK5aWAa for <dots@ietfa.amsl.com>; Mon, 22 Jul 2019 07:55:38 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [115.69.228.140]) by ietfa.amsl.com (Postfix) with ESMTP id 2FBAF120353 for <dots@ietf.org>; Mon, 22 Jul 2019 07:55:38 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [192.168.8.15]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 64BF625F6BD; Mon, 22 Jul 2019 23:55:37 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nttv6.jp; s=20180820; t=1563807337; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=+Co0nWBdpYwYUpIKOVzaF1E46XVVXXooxmwGqtPlvas=; b=ogd4GwcNd0FYAnxAru3F7t9sUu5UAs3JPPECECNkyq9ri+PmgN2kFPi8VmpYwkFVxnVzM5 tNCAFzmduAz7M5daugwfv/XdQ1Gr+qTK9eubrg5VCvbs1pX+j62cxCvUKeT8qCIgbva/nY xthkadL2iD3Y5kxGj/uwOCzOM9qZehc=
Received: from MacBook-Pro-17.local (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 7B2FA75907D; Mon, 22 Jul 2019 23:55:36 +0900 (JST)
To: "Konda, Tirumaleswar Reddy" <TirumaleswarReddy_Konda@McAfee.com>, tirumal reddy <kondtir@gmail.com>, "dots@ietf.org" <dots@ietf.org>
References: <156233245922.21720.2303446065970922340.idtracker@ietfa.amsl.com> <CAFpG3gcgpJRyLSoLkOMuUWY8pZrBPDCCz6-sc8A=1KW3GMpm+g@mail.gmail.com> <9401a258-5a32-b612-450b-10d3452777ac@nttv6.jp> <DM5PR16MB17054921F8CC3C2C90CB6A4BEAC40@DM5PR16MB1705.namprd16.prod.outlook.com>
From: kaname nishizuka <kaname@nttv6.jp>
Message-ID: <a70c3aad-8b41-3d3c-7cd9-88d681e888b6@nttv6.jp>
Date: Mon, 22 Jul 2019 23:55:35 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <DM5PR16MB17054921F8CC3C2C90CB6A4BEAC40@DM5PR16MB1705.namprd16.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------260C9F720E753AEB47FB6DA6"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/D7z-E1FW-044gnS45RHkNzRWEVs>
Subject: Re: [Dots] Fwd: New Version Notification for draft-reddy-dots-telemetry-00.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <dots.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dots>, <mailto:dots-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dots/>
List-Post: <mailto:dots@ietf.org>
List-Help: <mailto:dots-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dots>, <mailto:dots-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jul 2019 14:55:47 -0000

Hi Tiru,

Let me explain it.
There is a service by several transit providers such as detection capabilities to notify clients of potential attacks.
It is assumed that they have a DDoS mitigation system and a DDoS detection system (for example, a flow collector) separately.
It is a realistic deployment that the DOTS server is integrated with the flow collector.

When an attack occur, the DDoS detection system will notice that the customer is under attack, then the pre-mitigation DOTS telemetry(= attack details) can be signaled from the DOTS server to the (associated) DOTS client.

Here is one of the traffic anomaly detection notification example (threshold basis) quoted from some actual service.
Organization:       XXX
Attack ID:          13227
Start Time:         2019/06/05 22:52:30 JST+0900
Level:              1
Traffic Amount:     4.02k pps
Threshold:          4.00k pps
Direction:          incoming
Victim IP Address:  x.x.x.x/32
Attack Type:        TCP SYN

It says like "it seems you're under attack, what will you do? (We can offer some protection)"

regards,
Kaname


On 2019/07/22 23:11, Konda, Tirumaleswar Reddy wrote:
>
> Thanks Kaname for the support. I did not get the comment. what type of pre-mitigation DOTS telemetry attributes can be signaled from the DOTS server to the DOTS client ?
>
> And How will the DOTS server know the pre-mitigation DOTS telemetry attributes relevant or associated with a DOTS client ?
>
> Cheers,
>
> -Tiru
>
> *From:*Dots <dots-bounces@ietf.org>; *On Behalf Of *kaname nishizuka
> *Sent:* Monday, July 22, 2019 6:44 PM
> *To:* tirumal reddy <kondtir@gmail.com>;; dots@ietf.org
> *Subject:* Re: [Dots] Fwd: New Version Notification for draft-reddy-dots-telemetry-00.txt
>
> *CAUTION*:External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.
>
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> I support this draft.
>
> I'd like to mention about the telemetry attributes from a DOTS server to a DOTS client.
> Currently, several transit ISPs are providing DDoS detection and protection services.
> In such a service, they send a DDoS detection notification via e-mail when they noticed that their customer is under attack.
> The mail includes the telemetry information such as 4.1.5. Attack Details.
> This info can be used for further decision of protection strategy by the customer's security operators.
> I think it should be covered by the DOTS telemetry specification.
>
> One suggestion to the draft:
> Pre-mitigation DOTS Telemetry Attributes can also be signaled from the DOTS server to the DOTS client.
>
> thanks,
> Kaname
>
>
> On 2019/07/05 22:20, tirumal reddy wrote:
>
>     Hi all,
>
>     https://tools.ietf.org/html/draft-reddy-dots-telemetry-00 aims to enrich DOTS protocols with various telemetry attributes allowing optimal DDoS attack mitigation. This document specifies the normal traffic baseline and attack traffic telemetry attributes a DOTS client can convey to its DOTS server in the mitigation request, the mitigation status telemetry attributes a DOTS server can communicate to a DOTS client, and the mitigation efficacy telemetry attributes a DOTS client can communicate to a DOTS server.  The telemetry attributes can assist the mitigator to choose the DDoS mitigation techniques and perform optimal DDoS attack mitigation.
>
>     Comments, suggestions, and questions are more than welcome.
>
>
>     Cheers,
>
>     -Tiru
>
>     ---------- Forwarded message ---------
>     From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
>     Date: Fri, 5 Jul 2019 at 18:44
>     Subject: New Version Notification for draft-reddy-dots-telemetry-00.txt
>     To: Tirumaleswar Reddy <kondtir@gmail.com <mailto:kondtir@gmail.com>>, Ehud Doron <ehudd@radware.com <mailto:ehudd@radware.com>>, Mohamed Boucadair <mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com>>
>
>
>
>
>     A new version of I-D, draft-reddy-dots-telemetry-00.txt
>     has been successfully submitted by Tirumaleswar Reddy and posted to the
>     IETF repository.
>
>     Name:           draft-reddy-dots-telemetry
>     Revision:       00
>     Title:          Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
>     Document date:  2019-07-05
>     Group:          Individual Submission
>     Pages:          13
>     URL: https://www.ietf.org/internet-drafts/draft-reddy-dots-telemetry-00.txt
>     Status: https://datatracker.ietf.org/doc/draft-reddy-dots-telemetry/
>     Htmlized: https://tools.ietf.org/html/draft-reddy-dots-telemetry-00
>     Htmlized: https://datatracker.ietf.org/doc/html/draft-reddy-dots-telemetry
>
>
>     Abstract:
>        This document aims to enrich DOTS signal channel protocol with
>        various telemetry attributes allowing optimal DDoS attack mitigation.
>        This document specifies the normal traffic baseline and attack
>        traffic telemetry attributes a DOTS client can convey to its DOTS
>        server in the mitigation request, the mitigation status telemetry
>        attributes a DOTS server can communicate to a DOTS client, and the
>        mitigation efficacy telemetry attributes a DOTS client can
>        communicate to a DOTS server.  The telemetry attributes can assist
>        the mitigator to choose the DDoS mitigation techniques and perform
>        optimal DDoS attack mitigation.
>
>
>
>
>     Please note that it may take a couple of minutes from the time of submission
>     until the htmlized version and diff are available at tools.ietf.org <http://tools.ietf.org>;.
>
>     The IETF Secretariat
>
>
>
>     _______________________________________________
>
>     Dots mailing list
>
>     Dots@ietf.org  <mailto:Dots@ietf.org>
>
>     https://www.ietf.org/mailman/listinfo/dots
>
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots