IETF Logo Mail Archive

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

<mohamed.boucadair@orange.com> Mon, 18 November 2019 06:49 UTC

Return-Path: <mohamed.boucadair@orange.com>
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 9527712089E for <dots@ietfa.amsl.com>; Sun, 17 Nov 2019 22:49:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 YB5Lr6GYfBmV for <dots@ietfa.amsl.com>; Sun, 17 Nov 2019 22:49:01 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B555A1200B3 for <dots@ietf.org>; Sun, 17 Nov 2019 22:49:00 -0800 (PST)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 47Gfgb1g4Lz7tLP; Mon, 18 Nov 2019 07:48:59 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.26]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 47Gfgb0qwGzCqkN; Mon, 18 Nov 2019 07:48:59 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM31.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0468.000; Mon, 18 Nov 2019 07:48:59 +0100
From: mohamed.boucadair@orange.com
To: kaname nishizuka <kaname@nttv6.jp>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] TR: New Version Notification for draft-reddy-dots-telemetry-04.txt
Thread-Index: AQHVhZcTqLIZd9IRTUy9z3OirX19/adgIwpAgC0KHYCAA390IA==
Date: Mon, 18 Nov 2019 06:48:58 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330313D89E1@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <157139119677.3853.16590465405127507911.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B9330313410DA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <1726faa7-f319-58a4-2940-1703587c2c3b@nttv6.jp>
In-Reply-To: <1726faa7-f319-58a4-2940-1703587c2c3b@nttv6.jp>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.245]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/9wvbyAZZVxN0eBWEwdrjcSzXN_k>
Subject: Re: [Dots] TR: New Version Notification for draft-reddy-dots-telemetry-04.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, 18 Nov 2019 06:49:02 -0000

Hi Kaname, 

Yes. If we assume that a filter exists, it can be controlled via the signal channel. 

Will update accordingly. Thank you.

Cheers,
Med

> -----Message d'origine-----
> De : kaname nishizuka [mailto:kaname@nttv6.jp]
> Envoyé : samedi 16 novembre 2019 03:21
> À : BOUCADAIR Mohamed TGI/OLN; dots@ietf.org
> Objet : Re: [Dots] TR: New Version Notification for draft-reddy-dots-
> telemetry-04.txt
> 
> Hi Med,
> 
> One quick suggestion.
> 
> It would be worth to refer to [draft-ietf-dots-signal-filter-control] after
> this sentence
> https://github.com/boucadair/draft-dots-
> telemetry/blob/7b8d2bce108ae45d677e97143fcb985b9a9aa74b/draft-reddy-dots-
> telemetry-04.txt#L414-L418
> 
> like:
> The rate-limit action can be controlled by signal-channel [draft-ietf-dots-
> signal-filter-control] with more possibility than data-channel even when
> the pipe is overwhelmed
> 
> thanks,
> Kaname
> 
> On 2019/10/18 18:38, mohamed.boucadair@orange.com wrote:
> > Hi all,
> >
> > Although we are waiting for a call for adoption for this draft, we made
> some changes which you can track with the diff provided below.
> >
> > Cheers,
> > Med
> >
> >> -----Message d'origine-----
> >> De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> >> Envoyé : vendredi 18 octobre 2019 11:33
> >> À : chenmeiling; BOUCADAIR Mohamed TGI/OLN; Meiling Chen; Tirumaleswar
> >> Reddy; Ehud Doron; Reddy K
> >> Objet : New Version Notification for draft-reddy-dots-telemetry-04.txt
> >>
> >>
> >> A new version of I-D, draft-reddy-dots-telemetry-04.txt
> >> has been successfully submitted by Mohamed Boucadair and posted to the
> >> IETF repository.
> >>
> >> Name:		draft-reddy-dots-telemetry
> >> Revision:	04
> >> Title:		Distributed Denial-of-Service Open Threat Signaling (DOTS)
> >> Telemetry
> >> Document date:	2019-10-18
> >> Group:		Individual Submission
> >> Pages:		41
> >> URL:            https://www.ietf.org/internet-drafts/draft-reddy-dots-
> >> telemetry-04.txt
> >> Status:         https://datatracker.ietf.org/doc/draft-reddy-dots-
> >> telemetry/
> >> Htmlized:       https://tools.ietf.org/html/draft-reddy-dots-telemetry-
> 04
> >> Htmlized:       https://datatracker.ietf.org/doc/html/draft-reddy-dots-
> >> telemetry
> >> Diff:           https://www.ietf.org/rfcdiff?url2=draft-reddy-dots-
> >> telemetry-04
> >>
> >> 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.
> >>
> >> The IETF Secretariat
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots

v2.23.0 | Report a Bug | By Email