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

"Jon Shallow" <> Thu, 12 September 2019 08:12 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AAF04120864 for <>; Thu, 12 Sep 2019 01:12:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id pgK8nGgXKbxR for <>; Thu, 12 Sep 2019 01:12:32 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6CDB11208BF for <>; Thu, 12 Sep 2019 01:12:32 -0700 (PDT)
Received: from ([] helo=N01332) by with esmtp (Exim 4.92.2) (envelope-from <>) id 1i8KDM-0005hQ-OH; Thu, 12 Sep 2019 09:12:29 +0100
From: "Jon Shallow" <>
To: "'Konda, Tirumaleswar Reddy'" <>, <>
References: <> <> <>
In-Reply-To: <>
Date: Thu, 12 Sep 2019 09:12:28 +0100
Message-ID: <002301d56941$d1616770$74243650$>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0024_01D5694A.33272F00"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQFyArTqdojItGd5cuRsKSZmUVtvIgKgr6ghAHfCq9Cn1bedwA==
Content-Language: en-gb
Archived-At: <>
Subject: Re: [Dots] FW: New Version Notification for draft-reddy-dots-telemetry-02.txt
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 12 Sep 2019 08:12:35 -0000

Hi Tiru,


It is looking good.


However, we are not consistent in the usage of “mitigation-start” in the signal draft and “start-time” where time is represented differently in the usage of uint64 which may cause some downstream confusion.


I actually prefer (the granularity of) the “start-time” format, but am unsure as to how you would define  this in YANG.






From: Dots [mailto:] On Behalf Of Konda, Tirumaleswar Reddy
Sent: 12 September 2019 05:55
Subject: [Dots] FW: New Version Notification for draft-reddy-dots-telemetry-02.txt


This revision addresses comments from Kaname, Jon, Wei Pan and Yuuhei Hayashi.  


Major changes are listed below:


a.  Added path-suffix ‘telemetry’ to from the URI to signal DOTS telemetry

b.  Added attributes useful to detect resource-based DDoS attacks

c.  Attack details can be signaled from the DOTS client to server and vice-versa. 

d.  Added several new attributes for attack details including top talkers.


Comments and suggestions are welcome.




---------- Forwarded message ---------
From: <>
Date: Thu, 12 Sep 2019 at 09:58
Subject: New Version Notification for draft-reddy-dots-telemetry-02.txt
To: Tirumaleswar Reddy <>om>, Ehud Doron <>om>, Mohamed Boucadair <>

A new version of I-D, draft-reddy-dots-telemetry-02.txt
has been successfully submitted by Tirumaleswar Reddy and posted to the
IETF repository.

Name:           draft-reddy-dots-telemetry
Revision:       02
Title:          Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
Document date:  2019-09-12
Group:          Individual Submission
Pages:          16

   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

The IETF Secretariat