[Dots] was RE: Closing DOTS?

mohamed.boucadair@orange.com Tue, 04 April 2023 06:34 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 4595DC1516E0; Mon, 3 Apr 2023 23:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.796
X-Spam-Level:
X-Spam-Status: No, score=-2.796 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EgPApBAGT6lV; Mon, 3 Apr 2023 23:34:01 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06DE0C14F693; Mon, 3 Apr 2023 23:34:01 -0700 (PDT)
Received: from opfednr05.francetelecom.fr (unknown [xx.xx.xx.69]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr23.francetelecom.fr (ESMTP service) with ESMTPS id 4PrHzC0Bv9z5vtN; Tue, 4 Apr 2023 08:33:59 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1680590039; bh=boZtraLmiji31Baa5yGoUYOTQ9QJmDw0RLgSnGb0tqA=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=nCWALX6WDTUgoj+3P4TibU0RA1Ql1TqtyNIAB1o6xq0pfg7+Y34TfA4St7SLMTCE9 GfUBYsCScVybJhCOLYqtTJBpneebajA+j3OJNykoJpqbClXDEBUbqEz2g/QTBFWg4y Tuiex0cNTq4r8SyagHVNWvgjpUeZH+NysMZjsQ7CgjUILr9kNkajQHpSDyWwXYqIqe iM29+NwaVK+9JXRowykKwSCVmPeeJWh+z9yT1KgRsjiYgmxR3IRGxnn9SIceGmq5At 7EjqS7cqrmsXQ2kUeBYd27KqI7QRh+4ElVLfR40SDKLez8GP5eC3aDzvNzZKb4fCSx 42+HOoUhJwHZA==
From: mohamed.boucadair@orange.com
To: Valery Smyslov <valery@smyslov.net>, Kaname Nishizuka <kaname.nttv6.jp@gmail.com>, "supjps-ietf@jpshallow.com" <supjps-ietf@jpshallow.com>
CC: tirumal reddy <kondtir@gmail.com>, "dots@ietf.org" <dots@ietf.org>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>, Paul Wouters <paul.wouters@aiven.io>, Ehud Doron <EhudD@radware.com>
Thread-Topic: was RE: [Dots] Closing DOTS?
Thread-Index: Adlmv2zTa0SUrRjISpytV+ioyiiF1w==
Content-Class:
Date: Tue, 04 Apr 2023 06:33:58 +0000
Message-ID: <27073_1680590038_642BC4D6_27073_48_1_f3147cfccae74b8ba02b072e93a777e7@orange.com>
References: <054c01d960bc$255a8df0$700fa9d0$@smyslov.net> <012601d960c1$b6716660$23543320$@jpshallow.com> <20143_1679969194_64224BAA_20143_273_1_4547ab71739d41c5a900103532a75c5a@orange.com> <CAFpG3gehpWC_OMwkdTP2k7LZFqV+Z5e+3gSoF2PkKn4bVuksZg@mail.gmail.com> <PA4PR01MB9476782A5E9236E66461D727BB899@PA4PR01MB9476.eurprd01.prod.exchangelabs.com> <CAO2AGn9VKLcXpQuAepJ6rxf7KEB5YjgayO8rvnpRe8NN3PBPog@mail.gmail.com>
In-Reply-To: <CAO2AGn9VKLcXpQuAepJ6rxf7KEB5YjgayO8rvnpRe8NN3PBPog@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2023-04-04T06:22:19Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=2cf651b1-62df-4b37-a9fa-54c205c813ae; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.50]
Content-Type: multipart/alternative; boundary="_000_f3147cfccae74b8ba02b072e93a777e7orangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/yKhu5jNkzegcH4GPD6zyM7ycvc0>
Subject: [Dots] was RE: Closing DOTS?
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.39
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, 04 Apr 2023 06:34:05 -0000

Hi Kaname, all,

Thank you for all the hard work to keep the implem aligned with the spec.

In order to ease finding this implementation, I wonder whether the Chairs can update the “Additional Resources” of the WG Datatracker page with the following line:

related_implementations https://github.com/nttdots/go-dots (Go Implementation of DOTS)

A similar line can be added to the proprietary code from Jon.

Cheers,
Med

From: Kaname Nishizuka <kaname.nttv6.jp@gmail.com>
Sent: vendredi 31 mars 2023 05:33
To: Ehud Doron <EhudD@radware.com>
Cc: tirumal reddy <kondtir@gmail.com>; BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>; supjps-ietf@jpshallow.com; dots@ietf.org; Valery Smyslov <valery@smyslov.net>; dots-chairs@ietf.org; Paul Wouters <paul.wouters@aiven.io>
Subject: Re: [Dots] Closing DOTS?

Hi all,

+1 and I can't express enough how grateful I am to all of you.
I learned a lot from the discussions I had with all of you and I am proud that we were able to improve the DOTS protocol as a result.
Especially, conducting hackathon sessions and dots interoperability testing with Jon and other members was fascinating every time.
I'll keep our dots implementation (https://github.com/nttdots/go-dots) open on github and hope it be adapted or referred by others in near future.

Special thanks to all the past and current chairs who have supported us. Without their kind help, we couldn't have accomplished such a great work in IETF.

Best regards,
Kaname Nishizuka

2023年3月29日(水) 13:23 Ehud Doron <EhudD@radware.com<mailto:EhudD@radware.com>>:
Hi
+1 from my side.
Thanks a lot to all participants, chairs and ADs!

Special thanks from my side to Tiru and Med for their phenomenal work and true collaboration starting from the early days of this WG and throughout the entire active period of the WG.

Best wishes, Ehud


From: Dots <dots-bounces@ietf.org<mailto:dots-bounces@ietf.org>> On Behalf Of tirumal reddy
Sent: Tuesday, March 28, 2023 8:04 AM
To: mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>
Cc: supjps-ietf@jpshallow.com<mailto:supjps-ietf@jpshallow.com>; dots@ietf.org<mailto:dots@ietf.org>; Valery Smyslov <valery@smyslov.net<mailto:valery@smyslov.net>>; dots-chairs@ietf.org<mailto:dots-chairs@ietf.org>; Paul Wouters <paul.wouters@aiven.io<mailto:paul.wouters@aiven.io>>
Subject: Re: [Dots] Closing DOTS?



CAUTION: EXTERNAL EMAIL.

+1, Awesome collaboration among the WG participants and the several hackathon sessions that led to hardened specifications. Many thanks to the DOTS WG chairs and Security ADs.

On Tue, 28 Mar 2023 at 11:06, <mohamed.boucadair@orange.com<mailto:mohamed.boucadair@orange.com>> wrote:
Hi all,

I also think that it is time to close.

Many thanks to the WG participants and Chairs, especially for the good and positive collaboration spirit. I personally enjoyed working in this WG.

Cheers,
Med

> -----Message d'origine-----
> De : Dots <dots-bounces@ietf.org<mailto:dots-bounces@ietf.org>> De la part de supjps-
> ietf@jpshallow.com<mailto:ietf@jpshallow.com>
> Envoyé : mardi 28 mars 2023 00:35
> À : dots@ietf.org<mailto:dots@ietf.org>; Valery Smyslov <valery@smyslov.net<mailto:valery@smyslov.net>>
> Cc : dots-chairs@ietf.org<mailto:dots-chairs@ietf.org>; 'Paul Wouters' <paul.wouters@aiven.io<mailto:paul.wouters@aiven.io>>
> Objet : Re: [Dots] Closing DOTS?
>
> Hi all,
>
> I think the DOTS WG has run its natural course and can come to an
> end.
>
> Many thanks to all that have worked on DOTS - good to work with
> people who are clear thinkers, have good ideas and were prepared to
> check out the practical usability in the real (but aggressive!)
> world.
>
> I also will never stop being amazed at those for whom English was not
> their first language being able to sort out (as someone who is
> British and should know better) my incompressible grammar into
> something that made even better sense.  Well done!
>
> Regards
>
> Jon
>
> > -----Original Message-----
> > From: Valery Smyslov [mailto: valery@smyslov.net<mailto:valery@smyslov.net>]
> > Sent: 27 March 2023 15:55
> > To: dots@ietf.org<mailto:dots@ietf.org>
> > Cc: dots-chairs@ietf.org<mailto:dots-chairs@ietf.org>; 'Paul Wouters'
> > Subject: [Dots] Closing DOTS?
> >
> > Hi,
> >
> > the DOTS WG has completed all its tasks according to the current
> > charter (the last WG draft - telemetry use cases is in the RFC
> Editor
> > queue and will hopefully be published soon).
> >
> > Additionally, we don't have any new discussion on the list for
> quite a
> long time
> > and we skipped 3 IETF meetings for this reason.
> >
> > The chairs discussed this with the responsible AD and we came to a
> conclusion
> > that it's time to close the group or recharter it if there is an
> > interest in more work items related to DOTS.
> >
> > So, our question to the WG - should the group be closed?
> > And if the answer is no, then what are new items the WG can work on
> > after its recharter?
> >
> > Regards,
> > Valery (for chairs)
> >
> > _______________________________________________
> > Dots mailing list
> > Dots@ietf.org<mailto:Dots@ietf.org>
> > https://www.ietf.org/mailman/listinfo/dots
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org<mailto:Dots@ietf.org>
> https://www.ietf.org/mailman/listinfo/dots

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

_______________________________________________
Dots mailing list
Dots@ietf.org<mailto:Dots@ietf.org>
https://www.ietf.org/mailman/listinfo/dots
_______________________________________________
Dots mailing list
Dots@ietf.org<mailto:Dots@ietf.org>
https://www.ietf.org/mailman/listinfo/dots

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.