Re: [Dots] TR: New Version Notification for draft-nishizuka-dots-signal-control-filtering-06.txt
"Jon Shallow" <supjps-ietf@jpshallow.com> Tue, 02 April 2019 14:21 UTC
Return-Path: <supjps-ietf@jpshallow.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 A999B1201EB for <dots@ietfa.amsl.com>; Tue, 2 Apr 2019 07:21:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 LmZyY1o_NWaJ for <dots@ietfa.amsl.com>; Tue, 2 Apr 2019 07:21:32 -0700 (PDT)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 180A612016F for <dots@ietf.org>; Tue, 2 Apr 2019 07:21:31 -0700 (PDT)
Received: from [127.0.0.1] (helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.91) (envelope-from <jon.shallow@jpshallow.com>) id 1hBKI4-000337-KB; Tue, 02 Apr 2019 15:21:28 +0100
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: mohamed.boucadair@orange.com, dots@ietf.org
References: <155421064292.6387.16657228529546449549.idtracker@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93302EA512C0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EA512C0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Tue, 02 Apr 2019 15:21:27 +0100
Message-ID: <151801d4e95f$5d98ffe0$18caffa0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Content-Language: en-gb
Thread-Index: AQIodJsxuhDA6GheWme44Hg+M5GD1QNE9aJJpWek9gA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/Nilus08uOlLzIKd3IeRXxPoNLCU>
Subject: Re: [Dots] TR: New Version Notification for draft-nishizuka-dots-signal-control-filtering-06.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: Tue, 02 Apr 2019 14:21:37 -0000
Hi Med, Thanks for this. Clarification / comment 3.2.1 Parameters & Behaviors ... acl-name: A name of an access list defined using the DOTS data channel (Section 7.2 of [I-D.ietf-dots-data-channel]). The acl-name is unique per cuid, but the name can be duplicated, so perhaps Updated acl-name: A name of an access list defined using the DOTS data channel (Section 7.2 of [I-D.ietf-dots-data-channel]) that is associated with the DOTS client's 'cuid'. Old Figure 5: GET to Retrieve the Filtering (After Mitigation) New Figure 5: DOTS Data Channel GET response after Mitigation Old Figure 6: DOTS Data Channel Request to Create an Accep-List Filter New Figure 6: DOTS Data Channel Request to Create an Accept-List Filter Regards Jon > -----Original Message----- > From: Dots [mailto: dots-bounces@ietf.org] On Behalf Of > mohamed.boucadair@orange.com > Sent: 02 April 2019 14:13 > To: dots@ietf.org > Subject: [Dots] TR: New Version Notification for draft-nishizuka-dots-signal- > control-filtering-06.txt > > Hi all, > > This version takes into account the comments received in Prague. > > The text was also restructured for a better readability. > > Questions, comments, and suggestions are more than welcome. > > Cheers, > Med > > > -----Message d'origine----- > > De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > > Envoyé : mardi 2 avril 2019 15:11 > > À : Takahiko Nagata; Tirumaleswar Reddy; BOUCADAIR Mohamed TGI/OLN; > Reddy K; > > Kaname Nishizuka > > Objet : New Version Notification for draft-nishizuka-dots-signal-control- > > filtering-06.txt > > > > > > A new version of I-D, draft-nishizuka-dots-signal-control-filtering-06.txt > > has been successfully submitted by Mohamed Boucadair and posted to the > > IETF repository. > > > > Name: draft-nishizuka-dots-signal-control-filtering > > Revision: 06 > > Title: Controlling Filtering Rules Using Distributed Denial-of- > > Service Open Threat Signaling (DOTS) Signal Channel > > Document date: 2019-04-02 > > Group: Individual Submission > > Pages: 23 > > URL: https://www.ietf.org/internet-drafts/draft-nishizuka-dots- > > signal-control-filtering-06.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-06 > > 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-06 > > > > Abstract: > > This document specifies an extension to the DOTS signal channel 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. > > > > > > > > > > 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 > > _______________________________________________ > Dots mailing list > Dots@ietf.org > https://www.ietf.org/mailman/listinfo/dots
- [Dots] TR: New Version Notification for draft-nis… mohamed.boucadair
- Re: [Dots] TR: New Version Notification for draft… Jon Shallow
- Re: [Dots] TR: New Version Notification for draft… mohamed.boucadair