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

kaname nishizuka <kaname@nttv6.jp> Sat, 16 November 2019 02:21 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 CED27120096 for <dots@ietfa.amsl.com>; Fri, 15 Nov 2019 18:21:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-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 pxQ5dZ3cd5x6 for <dots@ietfa.amsl.com>; Fri, 15 Nov 2019 18:21:32 -0800 (PST)
Received: from guri.nttv6.jp (guri.nttv6.jp [115.69.228.140]) by ietfa.amsl.com (Postfix) with ESMTP id B1EAA120046 for <dots@ietf.org>; Fri, 15 Nov 2019 18:21:32 -0800 (PST)
Received: from z.nttv6.jp (z.nttv6.jp [IPv6:2402:c800:ff06:6::f]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id C170925F6B8; Sat, 16 Nov 2019 11:21:28 +0900 (JST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nttv6.jp; s=20180820; t=1573870889; 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:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=7J+vY/zKEA04NMB5KGKU+7lAUrv04QylpT2NJ08dkVI=; b=J5jtcGYr2KqWq08qZ+1IoRi7NZQrUIv/buYITpE6iKv0a3/FVUn2goD6wjtUlgPVw5m27+ AI2ZEjENpa6eRbI67Rc3X97PvdqlPBYbWnAy038j5xj4tktmKB8GfgNlKcIAIuPyj1HRey 9arsXQA5oq8jHVPV6LFoECnE4APHdTI=
Received: from dhcp-868e.meeting.ietf.org (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 49AC8759062; Sat, 16 Nov 2019 11:21:28 +0900 (JST)
To: mohamed.boucadair@orange.com, "dots@ietf.org" <dots@ietf.org>
References: <157139119677.3853.16590465405127507911.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B9330313410DA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
From: kaname nishizuka <kaname@nttv6.jp>
Message-ID: <1726faa7-f319-58a4-2940-1703587c2c3b@nttv6.jp>
Date: Sat, 16 Nov 2019 11:21:27 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <787AE7BB302AE849A7480A190F8B9330313410DA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Authentication-Results: guri.nttv6.jp; spf=pass smtp.mailfrom=kaname@nttv6.jp
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/MVmf_EbSEDgoAWcZLf9kJ6d_FhY>
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: Sat, 16 Nov 2019 02:21:36 -0000

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