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

mohamed.boucadair@orange.com Fri, 10 July 2020 08:07 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 5C1403A0E9D; Fri, 10 Jul 2020 01:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, 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 tUyyVshvbZ0l; Fri, 10 Jul 2020 01:07:02 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 995603A0E9C; Fri, 10 Jul 2020 01:07:02 -0700 (PDT)
Received: from opfednr06.francetelecom.fr (unknown [xx.xx.xx.70]) by opfednr24.francetelecom.fr (ESMTP service) with ESMTP id 4B35H86Y9rz1yjy; Fri, 10 Jul 2020 10:07:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1594368420; bh=68JNsAjH65ZPXniK3wHfWf5BGO4s7cqA8D9ofSTqtqI=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=JM7+2nSyoVV5SyFLIDp7EMAB07grbjEIV+33YY+1ssiAhSlTJbNDdyNP5jg5S3UR2 jSijK3Zx6jt00ckOjsQu9T/JNtKGo0jKhd+svmFq1t+K94S8h/cpG3cCCOuBvhR02Z tPhzFHrQXy2o6RPRqp2gR4JHeVbLtr0KPTolk6VB2fPCZApme9hnW39jTr05uI920K 6mX2rbatci5aawNM9tCByutAuVr5dlUHNysANl9UkbUZFZgkcjFdhwP6S9ElqqB+6N aO0KaVwWB9XgZzcAp/4UE2o3+UkmmDwB6O7u4Gac0IqbRLCJFwnZ1fBddXfwdzAsSd C5wrAekJMEMGA==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.35]) by opfednr06.francetelecom.fr (ESMTP service) with ESMTP id 4B35H85Lb5zDq8L; Fri, 10 Jul 2020 10:07:00 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: I-D Action: draft-ietf-dots-telemetry-10.txt
Thread-Index: AQHWVo+F/qC2bC2tOU+Ah+rgJOcdzqkAcfsw
Date: Fri, 10 Jul 2020 08:07:00 +0000
Message-ID: <23390_1594368420_5F0821A4_23390_276_4_787AE7BB302AE849A7480A190F8B9330314F4EB4@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <159436772889.4578.9157973873492692210@ietfa.amsl.com>
In-Reply-To: <159436772889.4578.9157973873492692210@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.245]
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/pHV2iHeFhs0FS9dlQQjudvulc04>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-10.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: Fri, 10 Jul 2020 08:07:04 -0000

Hi all, 

This version integrates the inputs received in the interim and the three issues raised in the interop and then discussed on the list. Note that the document updates 8782 as we are changing some of the IANA assignment policies: 128-255 range for comprehension-optional attribute. 

Also, this version addresses the yangdoctors review. That is mainly use "sx:structure" rather than containers. The internal structure of the telemetry message is not modified. The new design requires a ** normative dependency ** on the 8782-yang-update draft. That issue is currently worked out with the chairs/Ben. 

We also added a NEW section called 'Error Handling" which is basically summarizing what we do already have in the specs. This section is meant to provide more visibility on error handling. 

Some other edits are made to enhance the readability of the document and fix nits. 

This version is ready for the WGLC.

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é : vendredi 10 juillet 2020 09:55
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : I-D Action: draft-ietf-dots-telemetry-10.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
>                           Jon Shallow
> 	Filename        : draft-ietf-dots-telemetry-10.txt
> 	Pages           : 109
> 	Date            : 2020-07-10
> 
> Abstract:
>    This document aims to enrich DOTS signal channel protocol with
>    various telemetry attributes allowing optimal Distributed
> Denial-of-
>    Service 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-10
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-10
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-telemetry-10
> 
> 
> 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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.