IETF Logo Mail Archive

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

<mohamed.boucadair@orange.com> Wed, 24 April 2019 05:20 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 0F241120150; Tue, 23 Apr 2019 22:20:46 -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 mtipE6VkYaca; Tue, 23 Apr 2019 22:20:43 -0700 (PDT)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 62EF5120021; Tue, 23 Apr 2019 22:20:43 -0700 (PDT)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr23.francetelecom.fr (ESMTP service) with ESMTP id 44ppYj2tQsz5vvc; Wed, 24 Apr 2019 07:20:41 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.92]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 44ppYj1tsxzDq78; Wed, 24 Apr 2019 07:20:41 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM34.corporate.adroot.infra.ftgroup ([fe80::7873:1668:636f:52c%21]) with mapi id 14.03.0439.000; Wed, 24 Apr 2019 07:20:40 +0200
From: mohamed.boucadair@orange.com
To: Valery Smyslov <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>
CC: "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "kaduk@mit.edu" <kaduk@mit.edu>
Thread-Topic: [Dots] Adoption call for draft-nishizuka-dots-signal-control-filtering-06
Thread-Index: AQFofcDll063hnoOZ5xJUu1PCD2lGacjui6ggAAEW3A=
Date: Wed, 24 Apr 2019 05:20:40 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA6487C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <023e01d4ee1f$c3892950$4a9b7bf0$@smyslov.net> <019101d4fa5b$2702cd50$750867f0$@smyslov.net>
In-Reply-To: <019101d4fa5b$2702cd50$750867f0$@smyslov.net>
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/A4DFhZy7JRSCD5IH2L6n4guNw_k>
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: Wed, 24 Apr 2019 05:20:46 -0000

Hi Valery, 

Will do. Thanks. 

I fail to see where "MAY NOT" is used in the draft. 

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de Valery Smyslov
> Envoyé : mercredi 24 avril 2019 07:04
> À : dots@ietf.org
> Cc : dots-chairs@ietf.org; kaduk@mit.edu
> Objet : Re: [Dots] Adoption call for draft-nishizuka-dots-signal-control-
> filtering-06
> 
> Hi,
> 
> we received a lot of replies supporting adoption of the document.
> So, the document is adopted. Authors, please re-submit it as WG draft.
> 
> One comment.
> The draft uses few times a keyword "MAY NOT". This combination is not
> among the list of RFC requirement keywords (it is not listed neither
> in RFC2119, nor in RFC8174). If the intent was to use RFC requirement
> language, then I'd suggest replacing it with one of MUST NOT, SHALL NOT,
> SHOULD NOT. Otherwise please make it lowcase.
> 
> Regards,
> Valery.
> 
> > 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

v2.23.0 | Report a Bug | By Email