Re: [Dots] I-D Action: draft-ietf-dots-telemetry-06.txt

Hi all, 

The main changes in this version are as follows:
* add a reminder that cuid/cdid must not appear in the message body
* add a reminder about the use of YANG
* add a clarification about refresh of telemetry configuration
* Restructure the model to fix a problem raised by Jon about access to max/min data when no tsid is in place.
* Define unit-type 
* attack details are not modeled as an array
* add new containers ton convey protocol- and port-specific telemetry data. 
* add a clarification about partial requests
* add a clarification about the usage of per protocol and per-port metrics. 
* telemetry data can now be filtered using Uri-Query options
* add a note about handling baseline to accommodate non-attack overloads
* describe how to delete "tmids'
* update the cbor/mapping tables. 

The point about long responses is still PENDING.  

Please review and share your comments.

Cheers,
Med

> -----Message d'origine-----
> De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de
> internet-drafts@ietf.org
> Envoyé : mardi 7 avril 2020 09:53
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : I-D Action: draft-ietf-dots-telemetry-06.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the DDoS Open Threat Signaling WG of the
> IETF.
> 
>         Title           : Distributed Denial-of-Service Open Threat
> Signaling (DOTS) Telemetry
>         Authors         : Mohamed Boucadair
>                           Tirumaleswar Reddy
>                           Ehud Doron
>                           Meiling Chen
> 	Filename        : draft-ietf-dots-telemetry-06.txt
> 	Pages           : 93
> 	Date            : 2020-04-07
> 
> Abstract:
>    This document aims to enrich DOTS signal channel protocol with
>    various telemetry attributes allowing optimal DDoS attack
> mitigation.
>    It 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.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dots-telemetry-06
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-06
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-telemetry-06
> 
> 
> 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.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> 
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt