IETF Logo Mail Archive

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

"Valery Smyslov" <valery@smyslov.net> Wed, 24 April 2019 05:40 UTC

Return-Path: <valery@smyslov.net>
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 A00161200CD; Tue, 23 Apr 2019 22:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 MD-lUT7-LN0f; Tue, 23 Apr 2019 22:40:29 -0700 (PDT)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (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 1D5CB12002E; Tue, 23 Apr 2019 22:40:29 -0700 (PDT)
Received: from [185.48.36.5] (port=61205 helo=svannotebook) by direct.host-care.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.91) (envelope-from <valery@smyslov.net>) id 1hJAdu-00076Z-Vg; Wed, 24 Apr 2019 01:40:27 -0400
From: Valery Smyslov <valery@smyslov.net>
To: mohamed.boucadair@orange.com, dots@ietf.org
Cc: dots-chairs@ietf.org, kaduk@mit.edu
References: <023e01d4ee1f$c3892950$4a9b7bf0$@smyslov.net> <019101d4fa5b$2702cd50$750867f0$@smyslov.net> <787AE7BB302AE849A7480A190F8B93302EA6487C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <787AE7BB302AE849A7480A190F8B93302EA6487C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Wed, 24 Apr 2019 08:40:23 +0300
Message-ID: <019201d4fa60$38096050$a81c20f0$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQFofcDll063hnoOZ5xJUu1PCD2lGQIVZhnTAlvcHUunADl0EA==
Content-Language: ru
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/3xXhk7r-IlWH_uQLSr7nFMsX584>
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:40:31 -0000

Hi Med,

> Hi Valery,
> 
> Will do. Thanks.
> 
> I fail to see where "MAY NOT" is used in the draft.

You are right, it is used uppercase only in home-network draft.
I read both the drafts a while ago and probably mixed up 
the references when checking this.

Thank you,
Valery.

> 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.15.0 | Report a Bug | By Email