Re: [Dots] I-D Action: draft-ietf-dots-signal-filter-control-01.txt

<mohamed.boucadair@orange.com> Fri, 24 May 2019 12:51 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 471D3120092 for <dots@ietfa.amsl.com>; Fri, 24 May 2019 05:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 YGNpSLS70ikk for <dots@ietfa.amsl.com>; Fri, 24 May 2019 05:51:36 -0700 (PDT)
Received: from orange.com (mta240.mail.business.static.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 DCBA4120144 for <dots@ietf.org>; Fri, 24 May 2019 05:51:35 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 459R861y0WzBs7y for <dots@ietf.org>; Fri, 24 May 2019 14:51:34 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.95]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 459R861FQ8zCqkS for <dots@ietf.org>; Fri, 24 May 2019 14:51:34 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM24.corporate.adroot.infra.ftgroup ([fe80::b43f:9973:861e:42af%21]) with mapi id 14.03.0439.000; Fri, 24 May 2019 14:51:34 +0200
From: <mohamed.boucadair@orange.com>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-signal-filter-control-01.txt
Thread-Index: AQHVEi5O4V3tUmIpakWpZnvHvjLuUqZ6OI9g
Date: Fri, 24 May 2019 12:51:33 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA8EDCA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <155870180735.19858.13837460653147954541@ietfa.amsl.com>
In-Reply-To: <155870180735.19858.13837460653147954541@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/uA9hX5-vPkxXSbLsjKZmg3aChsM>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-filter-control-01.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, 24 May 2019 12:51:39 -0000

Hi all, 

This version takes into account the outcome of the issues discussed on the list: 
* recommend against including acl attributes in an initial mitigation request.
* a client can adjust the activation-type as an attack evolves.
* specify the behavior when the server fails to apply an acl change.
* clarify that the procedure does not assume the data and signal channels are not terminating on the same server.
* add a new example to illustrate that the client can deactivate back a filter it activated earlier. 

and many editorial changes to enhance the readability of the document. 

Comments and questions are welcome.

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de internet-
> drafts@ietf.org
> Envoyé : vendredi 24 mai 2019 14:43
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : [Dots] I-D Action: draft-ietf-dots-signal-filter-control-01.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           : Controlling Filtering Rules Using Distributed
> Denial-of-Service Open Threat Signaling (DOTS) Signal Channel
>         Authors         : Kaname Nishizuka
>                           Mohamed Boucadair
>                           Tirumaleswar Reddy
>                           Takahiko Nagata
> 	Filename        : draft-ietf-dots-signal-filter-control-01.txt
> 	Pages           : 25
> 	Date            : 2019-05-24
> 
> Abstract:
>    This document specifies an extension to the DOTS signal channel
>    protocol so that DOTS clients can control their filtering rules when
>    an attack mitigation is active.
> 
>    Particularly, this extension allows a DOTS client to activate or de-
>    activate existing filtering rules during a DDoS attack.  The
>    characterization of these filtering rules is supposed to be conveyed
>    by a DOTS client during an idle time by means of the DOTS data
>    channel protocol.
> 
> Editorial Note (To be removed by RFC Editor)
> 
>    Please update these statements within the document with the RFC
>    number to be assigned to this document:
> 
>    o  "This version of this YANG module is part of RFC XXXX;"
> 
>    o  "RFC XXXX: Controlling Filtering Rules Using Distributed Denial-
>       of-Service Open Threat Signaling (DOTS) Signal Channel";
> 
>    o  reference: RFC XXXX
> 
>    o  [RFCXXXX]
> 
>    Please update these statements with the RFC number to be assigned to
>    the following documents:
> 
>    o  "RFC SSSS: Distributed Denial-of-Service Open Threat Signaling
>       (DOTS) Signal Channel Specification" (used to be
>       [I-D.ietf-dots-signal-channel])
> 
>    o  "RFC DDDD: Distributed Denial-of-Service Open Threat Signaling
>       (DOTS) Data Channel Specification" (used to be
>       [I-D.ietf-dots-data-channel])
> 
>    Please update the "revision" date of the YANG module.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-signal-filter-control/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dots-signal-filter-control-01
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-filter-
> control-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-filter-control-01
> 
> 
> 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/
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots