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

mohamed.boucadair@orange.com Thu, 16 April 2020 05:39 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 C76453A0E7E for <dots@ietfa.amsl.com>; Wed, 15 Apr 2020 22:39:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 BB5BZtyw8j4x for <dots@ietfa.amsl.com>; Wed, 15 Apr 2020 22:39:51 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BB553A0E80 for <dots@ietf.org>; Wed, 15 Apr 2020 22:39:48 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 492p2V0gRlz8t9g for <dots@ietf.org>; Thu, 16 Apr 2020 07:39:46 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1587015586; bh=IcllbUObrQJO2JJqq4vEtyku3z1rjar0XUgXRWwsMSM=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=QDiE+fWLSDDrjIdd/EbcsFNZqtkuq5ogqdzLiseQVnATD0P/NtcuOwt+fBr4pvFl4 c3HG4kBloafaFNWSa9qQu3437kuu6w1jzInujPJHMY5KZJ6S9lDdkQSvA30KUeW57E vdgFdHPkJpXa6chy9fNM8i2nU31wH+NCZCK33l9tujGZotqFzs2468KIkhD7vg/xJ1 AwYvzBgOtw37zIbw1c1rLXPN2VmEjzdrF50V7dxgtmnp4ZHcji6j6MAOFRcsAqqg0s 5h2ZIkcW+oEggaC2VWtUDJNwuAqhcp0o8RVOHoH0176Q0cOa0U5oPUhtgmuEoy2aEq xLxXSSEsDNI6A==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.32]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 492p2T73KvzCqkV for <dots@ietf.org>; Thu, 16 Apr 2020 07:39:45 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: I-D Action: draft-ietf-dots-telemetry-07.txt
Thread-Index: AQHWE1usaQTObtnTc0myKtzOmEe+E6h7OWxg
Date: Thu, 16 Apr 2020 05:39:45 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93303149616A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <158697873353.29013.4148200236781320443@ietfa.amsl.com>
In-Reply-To: <158697873353.29013.4148200236781320443@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/044UH4cpzV2bLqlj8EWDKRR_wsI>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-07.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: Thu, 16 Apr 2020 05:39:54 -0000

Hi all, 

This is a minor revision with the following changes: 

* add a NEW text and pointer to Block3/Block4 options but without any normative language. 
* add a clarification that attack level is implementation-specific (to address a comment from Meiling)
* clarify that telemetry setup is not deleted when a DOTS session is lost. Its validity depends on the association with a dots client domain, not a transport session. 
* unit-status is mandatory when configuring units.
* add a clarification about overlapping targets to cover resolving IP addresses of fqdns/uri/aliases. 
* clarify that telemetry-notify-interval does not consider each "fragmented" notification as a single notification (if blocks are used to send a notification).
* clarify that data included in some attributes assumes that any uri-query filters are applied. 

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é : mercredi 15 avril 2020 21:26
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : I-D Action: draft-ietf-dots-telemetry-07.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-07.txt
> 	Pages           : 95
> 	Date            : 2020-04-15
> 
> 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-07
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-07
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-telemetry-07
> 
> 
> 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