Re: [Dots] Adoption call for draft-nishizuka-dots-signal-control-filtering-06

<mohamed.boucadair@orange.com> Tue, 16 April 2019 08:40 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 007D312037D; Tue, 16 Apr 2019 01:40:16 -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 DILuFl6fqc70; Tue, 16 Apr 2019 01:40:15 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBABA120372; Tue, 16 Apr 2019 01:40:14 -0700 (PDT)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar20.francetelecom.fr (ESMTP service) with ESMTP id 44jzMd3J5Jz8tP0; Tue, 16 Apr 2019 10:40:13 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.95]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 44jzMd22RjzCqjh; Tue, 16 Apr 2019 10:40:13 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM24.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Tue, 16 Apr 2019 10:40:13 +0200
From: mohamed.boucadair@orange.com
To: Dan Wing <danwing@gmail.com>, Valery Smyslov <valery@smyslov.net>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "dots@ietf.org" <dots@ietf.org>, "kaduk@mit.edu" <kaduk@mit.edu>
Thread-Topic: [Dots] Adoption call for draft-nishizuka-dots-signal-control-filtering-06
Thread-Index: AQHU87XBX60o/DOehEK5zkTcgdNlzaY+dpLw
Date: Tue, 16 Apr 2019 08:40:12 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA60D56@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <023e01d4ee1f$c3892950$4a9b7bf0$@smyslov.net> <D6EE3667-C4E6-4F68-A9A5-E8F0744C0972@gmail.com>
In-Reply-To: <D6EE3667-C4E6-4F68-A9A5-E8F0744C0972@gmail.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/vtSeuzhhDodRozgga6WK33kqmzc>
Subject: Re: [Dots] Adoption call for draft-nishizuka-dots-signal-control-filtering-06
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, 16 Apr 2019 08:40:17 -0000

Hi Dan, 

Thank you for the comment. 

Some of the text is provided as a reminder to ease the readability of the document, while some (new) text (e.g., "Note that both 'immediate' and 'activate-when-mitigating' have an immediate effect when a mitigation request is being processed by the DOTS server.") is specific to the signal channel. 

A first attempt to tweak the text and avoid the potential confusion you raised is available at: 

https://github.com/boucadair/filter-control/blob/master/wdiff%20draft-nishizuka-dots-signal-control-filtering-06.txt%20draft-nishizuka-dots-signal-control-filtering-06.pdf 

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de Dan Wing
> Envoyé : lundi 15 avril 2019 20:05
> À : Valery Smyslov
> Cc : dots-chairs@ietf.org; dots@ietf.org; kaduk@mit.edu
> Objet : Re: [Dots] Adoption call for draft-nishizuka-dots-signal-control-
> filtering-06
> 
> I support adoption of this draft.
> 
> Nit: I am nervous it is unnecessarily re-stating normative behavior in its
> Section 3.2.1 -- normative behavior of acl-name and activation-type which
> should only be located in draft-ietf-dots-data-channel.  It's difficult to
> tell if the subtle word differences are intended to change behavior or simply
> restate the behavior described in draft-ietf-dots-data-channel.  I would just
> remove the text that mimics draft-ietf-dots-data-channel and simply point off
> to draft-ietf-dots-data-channel.
> 
> -d
> 
> 
> > On Apr 8, 2019, at 8:28 AM, Valery Smyslov <valery@smyslov.net> wrote:
> >
> > Hi all,
> >
> > the chairs recently received an adoption request for draft-nishizuka-dots-
> signal-control-filtering-06.
> >
> > This message starts a two-week adoption call for draft-nishizuka-dots-
> signal-control-filtering-06.
> > The call ends up on Tuesday, April the 23rd.
> >
> > Please send your opinion regarding adoption of this document to the list
> before this date.
> > If you think the draft should be adopted, please indicate whether you're
> willing
> > to review it/to work on it. If you think the draft should not be adopted,
> please explain why.
> >
> > Regards,
> > Frank & Valery.
> >
> >
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org
> > https://www.ietf.org/mailman/listinfo/dots
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots