[Dots] TR: New Version Notification for draft-nishizuka-dots-signal-control-filtering-05.txt

<mohamed.boucadair@orange.com> Fri, 08 March 2019 15:09 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 8B9AB1279B3 for <dots@ietfa.amsl.com>; Fri, 8 Mar 2019 07:09:39 -0800 (PST)
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 Du28Tl9CLVOy for <dots@ietfa.amsl.com>; Fri, 8 Mar 2019 07:09:37 -0800 (PST)
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 26F4812423B for <dots@ietf.org>; Fri, 8 Mar 2019 07:09:37 -0800 (PST)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar25.francetelecom.fr (ESMTP service) with ESMTP id 44G9rv4hPPz8tbv; Fri, 8 Mar 2019 16:09:35 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.60]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 44G9rv3l3VzCqkY; Fri, 8 Mar 2019 16:09:35 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM5D.corporate.adroot.infra.ftgroup ([fe80::8899:bbc3:9726:cd5e%22]) with mapi id 14.03.0439.000; Fri, 8 Mar 2019 16:09:35 +0100
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>, "Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com>
Thread-Topic: New Version Notification for draft-nishizuka-dots-signal-control-filtering-05.txt
Thread-Index: AQHU1cBKOPUCl/5Od0e84+mZKJHbo6YB1XVw
Date: Fri, 08 Mar 2019 15:09:34 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA364DE@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <155205749391.3291.6600013239588052877.idtracker@ietfa.amsl.com>
In-Reply-To: <155205749391.3291.6600013239588052877.idtracker@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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/LYXoZ8T2ViYG6eQcn60n1hFKZe8>
Subject: [Dots] TR: New Version Notification for draft-nishizuka-dots-signal-control-filtering-05.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, 08 Mar 2019 15:09:39 -0000

Hi Franck, all, 

We prepared an updated version to address your clarification comments. We added two additional examples to illustrate the behavior. 

A diff is provided below to track the changes. 

As usual, comments/questions/suggestions are more than welcome. 

Cheers,
Med

> -----Message d'origine-----
> De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Envoyé : vendredi 8 mars 2019 16:05
> À : Takahiko Nagata; Tirumaleswar Reddy; BOUCADAIR Mohamed TGI/OLN; Reddy K;
> Kaname Nishizuka
> Objet : New Version Notification for draft-nishizuka-dots-signal-control-
> filtering-05.txt
> 
> 
> A new version of I-D, draft-nishizuka-dots-signal-control-filtering-05.txt
> has been successfully submitted by Mohamed Boucadair and posted to the
> IETF repository.
> 
> Name:		draft-nishizuka-dots-signal-control-filtering
> Revision:	05
> Title:		Controlling Filtering Rules Using DOTS Signal Channel
> Document date:	2019-03-08
> Group:		Individual Submission
> Pages:		21
> URL:            https://www.ietf.org/internet-drafts/draft-nishizuka-dots-
> signal-control-filtering-05.txt
> Status:         https://datatracker.ietf.org/doc/draft-nishizuka-dots-signal-
> control-filtering/
> Htmlized:       https://tools.ietf.org/html/draft-nishizuka-dots-signal-
> control-filtering-05
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-nishizuka-dots-
> signal-control-filtering
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-nishizuka-dots-
> signal-control-filtering-05
> 
> Abstract:
>    This document specifies an extension to the DOTS signal channel to
>    control the 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 peace time by means of DOTS data channel.
> 
> 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 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.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat