Re: [Dots] I-D Action: draft-ietf-dots-signal-filter-control-03.txt
mohamed.boucadair@orange.com Mon, 02 March 2020 08:48 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 314D43A1010 for <dots@ietfa.amsl.com>; Mon, 2 Mar 2020 00:48:05 -0800 (PST)
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 1CjffNFK1THl for <dots@ietfa.amsl.com>; Mon, 2 Mar 2020 00:48:03 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 46AB73A100F for <dots@ietf.org>; Mon, 2 Mar 2020 00:48:03 -0800 (PST)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 48WDLT61c5zFq3J; Mon, 2 Mar 2020 09:48:01 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1583138881; bh=F2zZag5qQo0Gsv7vwyKBsKJ9CWFPHMJcYFxjh6+D0bg=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=gxQY5tTqRUgLz5NQ9ajzgVQsQyGX/H8gSQQYZnraqnXzPQOigEHwYnwHm8A+dNV66 v+D41WFlKZfY4Lgh88xQ6Kkz+5+HzpH8lh+Z7YBkCGb6BCF8p96Ovdrc6yDmGy1yQM C6Wl1y+3MbcCrF2kQzmyQegBWrTuB/ng+5RXAWi/0U1FzNHyk/9jcroFEXT+zwi3Sb o8gfgyKdzPip2BN2r0rCwe1F8waKtK0nXhx9xGO47/avDbAkF+U6YHP2MBM71dD5bR OzjFHXULPF31W+lIa8STrFwsTZxYPhaGAuLso0lmQcCkltAdp5xp8etZKKbo0oR+6I cFsOzL1XIp69A==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.35]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 48WDLT59JLz1xpr; Mon, 2 Mar 2020 09:48:01 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM6C.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0487.000; Mon, 2 Mar 2020 09:48:01 +0100
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>
CC: "Benjamin Kaduk (kaduk@mit.edu)" <kaduk@mit.edu>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-signal-filter-control-03.txt
Thread-Index: AQHV8G0D+V9uLllelUmwgEF929JY06g0+wiA
Date: Mon, 02 Mar 2020 08:48:01 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93303145B38E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <158313789545.21225.8584305619220219100@ietfa.amsl.com>
In-Reply-To: <158313789545.21225.8584305619220219100@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/wjLLzW8lWmSFUgiQLEMoLtJNp2c>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-filter-control-03.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: Mon, 02 Mar 2020 08:48:05 -0000
Hi all, As discussed in the DOTS telemetry thread, this version registers "ietf-dots-signal-control:acl-list" and " ietf-dots-signal-control:acl-name" rather than using the key values already assigned to "acl-list" and "acl-name". I prefer to fix this now so that Ben can use this version for his review. Cheers, Med > -----Message d'origine----- > De : Dots [mailto:dots-bounces@ietf.org] De la part de internet- > drafts@ietf.org > Envoyé : lundi 2 mars 2020 09:32 > À : i-d-announce@ietf.org > Cc : dots@ietf.org > Objet : [Dots] I-D Action: draft-ietf-dots-signal-filter-control- > 03.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-03.txt > Pages : 26 > Date : 2020-03-02 > > 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-03 > https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-filter- > control-03 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-filter- > control-03 > > > 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
- [Dots] I-D Action: draft-ietf-dots-signal-filter-… internet-drafts
- Re: [Dots] I-D Action: draft-ietf-dots-signal-fil… mohamed.boucadair