
From nobody Fri May 21 07:23:29 2021
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 383023A1210 for <dots@ietfa.amsl.com>; Fri, 21 May 2021 07:23:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level: 
X-Spam-Status: No, score=-2.095 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pmoOyCwE4d5h for <dots@ietfa.amsl.com>; Fri, 21 May 2021 07:23:17 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B6A43A120B for <dots@ietf.org>; Fri, 21 May 2021 07:23:16 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar24.francetelecom.fr (ESMTP service) with ESMTP id 4Fmpjs3TfGz5y0h for <dots@ietf.org>; Fri, 21 May 2021 16:23:13 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1621606993; bh=++pE023wZLW5C/kzmrhMY87AVZVzYK2sccjnevzL6Xw=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=PHJr4sMhHykXSL0dvEzHT5hRwTuqjciS7p+PIv9UzOx5k06cGuRpEppmIPlnds+wS SOtwvfDnwnPFG4gtqrOzemKQIJaNUPnbpVBPytzVyBP0E+RJ4di1qzr0IH6Y4Zc1nS gBvjzRa96IudPSwLtx+4k0cFgeDv36VCb8QBR51NpFz9h0eQ4ftdZ+LodVKTcxIyOf gV+mvNIoler+nLQMSRZoR3tOYEWHy1o7I5NUirdos7ysNzNzYjnPvpzOms0uN6DKw+ XnHbYZxLwpW1uIkr3Ui3nY83pF6D9Y33zYW6m5OUpb8GOTuWUjGWo8H+GKtfkSWUbp 8q4ZkrJyty+Bw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.86]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 4Fmpjs2ndqz1xns for <dots@ietf.org>; Fri, 21 May 2021 16:23:13 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: I-D Action: draft-ietf-dots-signal-call-home-13.txt
Thread-Index: AQHW6BpYbQnUMZGf1UadJthfbT143aruyDfg
Date: Fri, 21 May 2021 14:23:12 +0000
Message-ID: <7676_1621606993_60A7C251_7676_368_8_787AE7BB302AE849A7480A190F8B93303538C43B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <161037027105.15834.255075233056658139@ietfa.amsl.com>
In-Reply-To: <161037027105.15834.255075233056658139@ietfa.amsl.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/_jHYOXaCQkZdOrJfjiCMdmVLZpE>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-call-home-13.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: Fri, 21 May 2021 14:23:27 -0000

Hi all,=20

As we are blocked for more than 4 months, I suggest to remove the request f=
or assigning a new port number. We do still recommend the use of distinct p=
orts, but these are configured manually or discovered when such tools are s=
upported.=20=20

Unless there are objections, we are planning to submit this version: https:=
//tinyurl.com/dots-call-home-latest=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part
> de internet-drafts@ietf.org
> Envoy=E9=A0: lundi 11 janvier 2021 14:05
> =C0=A0: i-d-announce@ietf.org
> Cc=A0: dots@ietf.org
> Objet=A0: I-D Action: draft-ietf-dots-signal-call-home-13.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the DDoS Open Threat Signaling WG of the
> IETF.
>=20
>         Title           : Distributed Denial-of-Service Open Threat
> Signaling (DOTS) Signal Channel Call Home
>         Authors         : Tirumaleswar Reddy
>                           Mohamed Boucadair
>                           Jon Shallow
> 	Filename        : draft-ietf-dots-signal-call-home-13.txt
> 	Pages           : 44
> 	Date            : 2021-01-11
>=20
> Abstract:
>    This document specifies the DOTS signal channel Call Home, which
>    enables a Call Home DOTS server to initiate a secure connection to
> a
>    Call Home DOTS client, and to receive attack traffic information
> from
>    the Call Home DOTS client.  The Call Home DOTS server in turn uses
>    the attack traffic information to identify compromised devices
>    launching outgoing DDoS attacks and take appropriate mitigation
>    action(s).
>=20
>    The DOTS signal channel Call Home is not specific to home
> networks;
>    the solution targets any deployment in which it is required to
> block
>    DDoS attack traffic closer to the source(s) of a DDoS attack.
>=20
> Editorial Note (To be removed by RFC Editor)
>=20
>    Please update these statements within the document with the RFC
>    number to be assigned to this document:
>=20
>    o  "This version of this YANG module is part of RFC XXXX;"
>=20
>    o  "RFC XXXX: Distributed Denial-of-Service Open Threat Signaling
>       (DOTS) Signal Channel Call Home";
>=20
>    o  "| [RFCXXXX] |"
>=20
>    o  reference: RFC XXXX
>=20
>    Please update this statement with the RFC number to be assigned to
>    the following documents:
>=20
>    o  "RFC YYYY: Distributed Denial-of-Service Open Threat Signaling
>       (DOTS) Signal Channel Specification" (used to be I-D.ietf-dots-
>       rfc8782-bis)
>=20
>    Please update TBD/TBA statements with the assignments made by IANA
> to
>    DOTS Signal Channel Call Home.
>=20
>    Also, please update the "revision" date of the YANG module.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-signal-call-home/
>=20
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dots-signal-call-home-13
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-call-
> home-13
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-signal-call-home-13
>=20
>=20
> 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.
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
>=20
> _______________________________________________
> I-D-Announce mailing list
> I-D-Announce@ietf.org
> https://www.ietf.org/mailman/listinfo/i-d-announce
> Internet-Draft directories: http://www.ietf.org/shadow.html or
> ftp://ftp.ietf.org/ietf/1shadow-sites.txt

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Fri May 21 07:32:23 2021
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 CB8573A1256 for <dots@ietfa.amsl.com>; Fri, 21 May 2021 07:32:21 -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, SPF_HELO_NONE=0.001, 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 5Cn41p8Ex1Kz for <dots@ietfa.amsl.com>; Fri, 21 May 2021 07:32:17 -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 486393A121E for <dots@ietf.org>; Fri, 21 May 2021 07:32:16 -0700 (PDT)
Received: from mail2.jpshallow.com ([192.168.0.3] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1lk6CD-0006ve-2W; Fri, 21 May 2021 15:32:13 +0100
From: "Jon Shallow" <supjps-ietf@jpshallow.com>
To: <mohamed.boucadair@orange.com>, <dots@ietf.org>
References: <161037027105.15834.255075233056658139@ietfa.amsl.com> <7676_1621606993_60A7C251_7676_368_8_787AE7BB302AE849A7480A190F8B93303538C43B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <7676_1621606993_60A7C251_7676_368_8_787AE7BB302AE849A7480A190F8B93303538C43B@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Fri, 21 May 2021 15:32:14 +0100
Message-ID: <08e701d74e4e$181edb50$485c91f0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQKGuxqp0pON/2Atv1eqVCCf09evVQJ/LYnmqXssW/A=
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/K-9BthmhPj_EynbuL1SnWB9f2ro>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-call-home-13.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: Fri, 21 May 2021 14:32:22 -0000

Hi all,

I have no objection.

Regards

Jon

> -----Original Message-----
> From: mohamed.boucadair@orange.com =
[mailto:mohamed.boucadair@orange.com]
> Sent: 21 May 2021 15:23
> To: dots@ietf.org
> Subject: Re: [Dots] I-D Action: =
draft-ietf-dots-signal-call-home-13.txt
>=20
> Hi all,
>=20
> As we are blocked for more than 4 months, I suggest to remove the =
request
> for assigning a new port number. We do still recommend the use of =
distinct
> ports, but these are configured manually or discovered when such tools =
are
> supported.
>=20
> Unless there are objections, we are planning to submit this version:
> https://tinyurl.com/dots-call-home-latest
>=20
> Cheers,
> Med
>=20
> > -----Message d'origine-----
> > De=A0: I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la =
part
> > de internet-drafts@ietf.org
> > Envoy=E9=A0: lundi 11 janvier 2021 14:05
> > =C0=A0: i-d-announce@ietf.org
> > Cc=A0: dots@ietf.org
> > Objet=A0: I-D Action: draft-ietf-dots-signal-call-home-13.txt
> >
> >
> > A New Internet-Draft is available from the on-line Internet-Drafts
> > directories.
> > This draft is a work item of the DDoS Open Threat Signaling WG of =
the
> > IETF.
> >
> >         Title           : Distributed Denial-of-Service Open Threat
> > Signaling (DOTS) Signal Channel Call Home
> >         Authors         : Tirumaleswar Reddy
> >                           Mohamed Boucadair
> >                           Jon Shallow
> > 	Filename        : draft-ietf-dots-signal-call-home-13.txt
> > 	Pages           : 44
> > 	Date            : 2021-01-11
> >
> > Abstract:
> >    This document specifies the DOTS signal channel Call Home, which
> >    enables a Call Home DOTS server to initiate a secure connection =
to
> > a
> >    Call Home DOTS client, and to receive attack traffic information
> > from
> >    the Call Home DOTS client.  The Call Home DOTS server in turn =
uses
> >    the attack traffic information to identify compromised devices
> >    launching outgoing DDoS attacks and take appropriate mitigation
> >    action(s).
> >
> >    The DOTS signal channel Call Home is not specific to home
> > networks;
> >    the solution targets any deployment in which it is required to
> > block
> >    DDoS attack traffic closer to the source(s) of a DDoS attack.
> >
> > 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: Distributed Denial-of-Service Open Threat Signaling
> >       (DOTS) Signal Channel Call Home";
> >
> >    o  "| [RFCXXXX] |"
> >
> >    o  reference: RFC XXXX
> >
> >    Please update this statement with the RFC number to be assigned =
to
> >    the following documents:
> >
> >    o  "RFC YYYY: Distributed Denial-of-Service Open Threat Signaling
> >       (DOTS) Signal Channel Specification" (used to be =
I-D.ietf-dots-
> >       rfc8782-bis)
> >
> >    Please update TBD/TBA statements with the assignments made by =
IANA
> > to
> >    DOTS Signal Channel Call Home.
> >
> >    Also, please update the "revision" date of the YANG module.
> >
> >
> > The IETF datatracker status page for this draft is:
> > https://datatracker.ietf.org/doc/draft-ietf-dots-signal-call-home/
> >
> > There are also htmlized versions available at:
> > https://tools.ietf.org/html/draft-ietf-dots-signal-call-home-13
> > https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-call-
> > home-13
> >
> > A diff from the previous version is available at:
> > =
https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-signal-call-home-13
> >
> >
> > 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.
> >
> > Internet-Drafts are also available by anonymous FTP at:
> > ftp://ftp.ietf.org/internet-drafts/
> >
> >
> > _______________________________________________
> > I-D-Announce mailing list
> > I-D-Announce@ietf.org
> > https://www.ietf.org/mailman/listinfo/i-d-announce
> > Internet-Draft directories: http://www.ietf.org/shadow.html or
> > ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>=20
> ___________________________________________________________________
> ______________________________________________________
>=20
> 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.
>=20
> 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.
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots


From nobody Tue May 25 00:36:19 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BCCB3A192E; Tue, 25 May 2021 00:36:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <162192816459.1693.7785910495366474634@ietfa.amsl.com>
Date: Tue, 25 May 2021 00:36:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/fVnnI8WgfIU8o-jZORI8We-9Pgo>
Subject: [Dots] I-D Action: draft-ietf-dots-multihoming-06.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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, 25 May 2021 07:36:13 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Multi-homing Deployment Considerations for Distributed-Denial-of-Service Open Threat Signaling (DOTS)
        Authors         : Mohamed Boucadair
                          Tirumaleswar Reddy
                          Wei Pan
	Filename        : draft-ietf-dots-multihoming-06.txt
	Pages           : 15
	Date            : 2021-05-21

Abstract:
   This document discusses multi-homing considerations for Distributed-
   Denial-of-Service Open Threat Signaling (DOTS).  The goal is to
   provide some guidance for DOTS clients/gateways when multihomed.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-multihoming/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-multihoming-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-multihoming-06


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Tue May 25 05:20:07 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D34393A1116; Tue, 25 May 2021 05:20:00 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <162194520082.30674.12310409462219380422@ietfa.amsl.com>
Date: Tue, 25 May 2021 05:20:00 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/MtBlLSWp4MOH1v_z4O7NjOyKaVg>
Subject: [Dots] I-D Action: draft-ietf-dots-telemetry-16.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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, 25 May 2021 12:20:01 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Distributed Denial-of-Service Open Threat Signaling (DOTS) Telemetry
        Authors         : Mohamed Boucadair
                          Tirumaleswar Reddy
                          Ehud Doron
                          Meiling Chen
                          Jon Shallow
	Filename        : draft-ietf-dots-telemetry-16.txt
	Pages           : 113
	Date            : 2021-05-25

Abstract:
   This document aims to enrich DOTS signal channel protocol with
   various telemetry attributes allowing optimal Distributed Denial-of-
   Service attack mitigation.  It specifies the normal traffic baseline
   and attack traffic telemetry attributes a DOTS client can convey to
   its DOTS server in the mitigation request, the mitigation status
   telemetry attributes a DOTS server can communicate to a DOTS client,
   and the mitigation efficacy telemetry attributes a DOTS client can
   communicate to a DOTS server.  The telemetry attributes can assist
   the mitigator to choose the DDoS mitigation techniques and perform
   optimal DDoS attack mitigation.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-16

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-telemetry-16


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Tue May 25 05:21:41 2021
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 9AE773A1115 for <dots@ietfa.amsl.com>; Tue, 25 May 2021 05:21:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yLgWS77_rFFI for <dots@ietfa.amsl.com>; Tue, 25 May 2021 05:21:36 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41DAD3A1116 for <dots@ietf.org>; Tue, 25 May 2021 05:21:36 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 4FqCqc71wqz518K for <dots@ietf.org>; Tue, 25 May 2021 14:21:32 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1621945293; bh=U3mDK7SqGFjcGzCPsRSKTftB09zHORsvS5LN2rAMmBU=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=TqV6/40/QIFFQnGAw9pqxRgWzuhc6XiXWuiWX2K+tEptMf7cyk7xAEbNLi9BtIfRT iuYj+eUGSVF0vfOpDyReWV0ZRBzT9/Em3/nz+2B7aqsedInCJ02kWg4R4Nu+wPqa1t IwKy0y3yzu/SFl0UHMm2B6FfGYEM3apECGN3T4XgKMprJJlFDRdl1/hLlsFXwu+vUQ q1LEpMiNuUtUTRatj5dRF42IQHI7mKHIf+K95axC24NZ7GGMihr1Re7I5MphSHDySe OQRKpKf9WiT7lHWR6t+DpM7bkrOVRkctS5xhieyVK7FJCt43KWBxcBtRtBbkuSUuF2 wgvsrZRAhAXAg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.64]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 4FqCqc6HhBz1xpr for <dots@ietf.org>; Tue, 25 May 2021 14:21:32 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-telemetry-16.txt
Thread-Index: AQHXUWBOItoP/UNWYUWHuBl+/JjJ8ar0HfRQ
Date: Tue, 25 May 2021 12:21:32 +0000
Message-ID: <9570_1621945292_60ACEBCC_9570_93_2_787AE7BB302AE849A7480A190F8B93303538E7B3@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <162194520082.30674.12310409462219380422@ietfa.amsl.com>
In-Reply-To: <162194520082.30674.12310409462219380422@ietfa.amsl.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.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/fkcmEGv95dcsoIQHguaERB7N0-c>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-telemetry-16.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, 25 May 2021 12:21:41 -0000

Hi all,=20

This is a minor rev to avoid the doc to expire while waiting for the AD rev=
iew.=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots [mailto:dots-bounces@ietf.org] De la part de internet-
> drafts@ietf.org
> Envoy=E9=A0: mardi 25 mai 2021 14:20
> =C0=A0: i-d-announce@ietf.org
> Cc=A0: dots@ietf.org
> Objet=A0: [Dots] I-D Action: draft-ietf-dots-telemetry-16.txt
>=20
>=20
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> This draft is a work item of the DDoS Open Threat Signaling WG of the
> IETF.
>=20
>         Title           : Distributed Denial-of-Service Open Threat
> Signaling (DOTS) Telemetry
>         Authors         : Mohamed Boucadair
>                           Tirumaleswar Reddy
>                           Ehud Doron
>                           Meiling Chen
>                           Jon Shallow
> 	Filename        : draft-ietf-dots-telemetry-16.txt
> 	Pages           : 113
> 	Date            : 2021-05-25
>=20
> Abstract:
>    This document aims to enrich DOTS signal channel protocol with
>    various telemetry attributes allowing optimal Distributed Denial-
> of-
>    Service attack mitigation.  It specifies the normal traffic
> baseline
>    and attack traffic telemetry attributes a DOTS client can convey
> to
>    its DOTS server in the mitigation request, the mitigation status
>    telemetry attributes a DOTS server can communicate to a DOTS
> client,
>    and the mitigation efficacy telemetry attributes a DOTS client can
>    communicate to a DOTS server.  The telemetry attributes can assist
>    the mitigator to choose the DDoS mitigation techniques and perform
>    optimal DDoS attack mitigation.
>=20
>=20
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry/
>=20
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-16
>=20
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-dots-telemetry-16
>=20
>=20
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>=20
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Wed May 26 00:50:04 2021
Return-Path: <session-request@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E833A24EC; Wed, 26 May 2021 00:50:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IETF Meeting Session Request Tool <session-request@ietf.org>
To: <session-request@ietf.org>
Cc: dots-chairs@ietf.org, dots@ietf.org, kaduk@mit.edu, valery@smyslov.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <162201540184.11128.3400370814252289615@ietfa.amsl.com>
Date: Wed, 26 May 2021 00:50:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/CoJuGrqbmtdCVsrtgztAoGNEIzA>
Subject: [Dots] dots - New Meeting Session Request for IETF 111
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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, 26 May 2021 07:50:03 -0000

A new meeting session request has just been submitted by Valery Smyslov, a Chair of the dots working group.


---------------------------------------------------------
Working Group Name: DDoS Open Threat Signaling
Area Name: Security Area
Session Requester: Valery Smyslov


Number of Sessions: 1
Length of Session(s):  1 Hour
Number of Attendees: 50
Conflicts to Avoid: 
 Chair Conflict:  uta ipsecme
 Technology Overlap:  cfrg tls saag cbor secdispatch
 Key Participant Conflict:  drip





People who must be present:
  Valery Smyslov
  Liang Xia
  Benjamin Kaduk

Resources Requested:

Special Requests:
  Please avoid security related BoFs if possible.
---------------------------------------------------------



From nobody Wed May 26 06:07:44 2021
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 C90293A2E93 for <dots@ietfa.amsl.com>; Wed, 26 May 2021 06:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.095
X-Spam-Level: 
X-Spam-Status: No, score=-2.095 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_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lcecjWju6H8m for <dots@ietfa.amsl.com>; Wed, 26 May 2021 06:07:32 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 35BD23A117E for <dots@ietf.org>; Wed, 26 May 2021 06:07:26 -0700 (PDT)
Received: from opfedar02.francetelecom.fr (unknown [xx.xx.xx.4]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 4Fqrp41lz8z31JZ; Wed, 26 May 2021 15:07:24 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1622034444; bh=HBlU6KfRylJhoD3nfgTIzpRCtS8mGKyQcN9pwQnKQQE=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=aiOOFlDPmk8c2a2vK2iCIAYqCam5ubRK0j66U3cHx8H79TMnJotXXCBMjTrPANxvG 9Rll8A7KN1m+JoEKsh/AjyvZYB6bCad9uJN0o7WewT/4ygyrEKS+ng2+JWCLFIcAZW adqg20gp42x0qMQ063Fsf9AEuxNS+wxn8HvJs+GfV49dFV8ZJPUZ5h5KIuVDO+1TZj vvULisFFUKfmLPuOUbxT898blA4NWoz98OKA5svCRu/Yw70eMgCOOAyhnYLWx7le4C h8O1IunU2/9umkLtI4ZVuLCYqnUgo1yhfNrZo4+tZyAoyfERWp2l/aUAFgjRo9FarD jmE14o+1Lb0mg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.82]) by opfedar02.francetelecom.fr (ESMTP service) with ESMTP id 4Fqrp40t94zCqkV; Wed, 26 May 2021 15:07:24 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: "dots@ietf.org" <dots@ietf.org>
CC: Jon Shallow <supjps-ietf@jpshallow.com>
Thread-Topic: [Dots] draft-ietf-core-new-block for draft-ietf-dots-telemetry
Thread-Index: AdcXQzssePT/XT7jQo6Gsf+7fCfXOg640+Xg
Date: Wed, 26 May 2021 13:07:23 +0000
Message-ID: <24345_1622034444_60AE480C_24345_185_5_787AE7BB302AE849A7480A190F8B93303538F49A@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <06b801d71743$3ea976a0$bbfc63e0$@jpshallow.com>
In-Reply-To: <06b801d71743$3ea976a0$bbfc63e0$@jpshallow.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: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93303538F49AOPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/thdenufk5pDlbGghYdKTIpi4Viw>
Subject: Re: [Dots] draft-ietf-core-new-block for draft-ietf-dots-telemetry
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, 26 May 2021 13:07:43 -0000

--_000_787AE7BB302AE849A7480A190F8B93303538F49AOPEXCAUBMA2corp_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi all,

Now that draft-ietf-core-new-block is almost ready to be sent to the RFC ed=
itor, it would be good if we can consider adopting draft-bosh-dots-quick-bl=
ocks so that DOTS agents can negotiate Q-Block functionality and make use o=
f it instead of Block1/2.

Cheers,
Med

De : Dots [mailto:dots-bounces@ietf.org] De la part de Jon Shallow
Envoy=E9 : vendredi 12 mars 2021 14:26
=C0 : dots@ietf.org
Objet : [Dots] draft-ietf-core-new-block for draft-ietf-dots-telemetry

Hi All,

Following the Core meeting at IETF 110 today, https://datatracker.ietf.org/=
doc/draft-ietf-core-new-block/ which handles sending a CoAP non-confirmable=
 body split over multiple payloads, has passed WGLC, and is waiting for the=
 write-up to progress the document to the IESG.

This draft refers to https://datatracker.ietf.org/doc/html/draft-bosh-dots-=
quick-blocks-01 for an example mechanism to negotiate the additional conges=
tion control parameters  using the DOTS signal channel configuration mechan=
ism, defining some new YANG/CBOR mapping entries.

This draft has been implemented, available using libcoap and the specific c=
ode (not merged) can be found at https://github.com/obgm/libcoap/pull/611  =
and has been tested in lossy and DOTS environments.

This draft is of significance for the DOTS telemetry draft ( https://datatr=
acker.ietf.org/doc/html/draft-ietf-dots-telemetry-15#section-4.3 ), which n=
eeds to be able to continue to send (large) telemetry information under net=
work attack situations.

Regards

Jon

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


--_000_787AE7BB302AE849A7480A190F8B93303538F49AOPEXCAUBMA2corp_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D">Hi all,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D">Now that draft-ietf-core-new-block is almost ready to be sent=
 to the RFC editor, it would be good if we can consider adopting draft-bosh=
-dots-quick-blocks so that DOTS agents can negotiate
 Q-Block functionality and make use of it instead of Block1/2.<o:p></o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D">Cheers,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D">Med<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Courier New&quot;;c=
olor:#1F497D"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"FR">De&nbsp;:</span></b><span lang=
=3D"FR"> Dots [mailto:dots-bounces@ietf.org]
<b>De la part de</b> Jon Shallow<br>
<b>Envoy=E9&nbsp;:</b> vendredi 12 mars 2021 14:26<br>
<b>=C0&nbsp;:</b> dots@ietf.org<br>
<b>Objet&nbsp;:</b> [Dots] draft-ietf-core-new-block for draft-ietf-dots-te=
lemetry<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Hi All,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Following the Core meeting at I=
ETF 110 today,
<a href=3D"https://datatracker.ietf.org/doc/draft-ietf-core-new-block/">htt=
ps://datatracker.ietf.org/doc/draft-ietf-core-new-block/</a> which handles =
sending a CoAP non-confirmable body split over multiple payloads, has passe=
d WGLC, and is waiting for the write-up
 to progress the document to the IESG.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">This draft refers to <a href=3D=
"https://datatracker.ietf.org/doc/html/draft-bosh-dots-quick-blocks-01">
https://datatracker.ietf.org/doc/html/draft-bosh-dots-quick-blocks-01</a> f=
or an example mechanism to negotiate the additional congestion control para=
meters &nbsp;using the DOTS signal channel configuration mechanism, definin=
g some new YANG/CBOR mapping entries.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">This draft has been implemented=
, available using libcoap and the specific code (not merged) can be found at
<a href=3D"https://github.com/obgm/libcoap/pull/611">https://github.com/obg=
m/libcoap/pull/611</a>&nbsp; and has been tested in lossy and DOTS environm=
ents.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">This draft is of significance f=
or the DOTS telemetry draft (
<a href=3D"https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-=
15#section-4.3">
https://datatracker.ietf.org/doc/html/draft-ietf-dots-telemetry-15#section-=
4.3</a> ), which needs to be able to continue to send (large) telemetry inf=
ormation under network attack situations.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Regards<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-GB">Jon<o:p></o:p></span></p>
</div>
</div>
<PRE>______________________________________________________________________=
___________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.
</PRE></body>
</html>

--_000_787AE7BB302AE849A7480A190F8B93303538F49AOPEXCAUBMA2corp_--


From nobody Wed May 26 21:48:47 2021
Return-Path: <kaduk@mit.edu>
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 E19693A081D; Wed, 26 May 2021 21:48:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=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 KagPmoxGdlFo; Wed, 26 May 2021 21:48:35 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 F2D8F3A081B; Wed, 26 May 2021 21:48:34 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 14R4llaK021391 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 27 May 2021 00:47:51 -0400
Date: Wed, 26 May 2021 21:47:46 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: mohamed.boucadair@orange.com
Cc: Dale Worley <worley@ariadne.com>, "gen-art@ietf.org" <gen-art@ietf.org>, "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-rfc8782-bis.all@ietf.org" <draft-ietf-dots-rfc8782-bis.all@ietf.org>,  "last-call@ietf.org" <last-call@ietf.org>
Message-ID: <20210527044746.GU32395@kduck.mit.edu>
References: <161646013325.22110.15904279569991264804@ietfa.amsl.com> <14598_1616503101_6059E13C_14598_15_12_787AE7BB302AE849A7480A190F8B93303535A30C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <14598_1616503101_6059E13C_14598_15_12_787AE7BB302AE849A7480A190F8B93303535A30C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/j_ZPczaY7R06CRC7wWs4aOdHgpc>
Subject: Re: [Dots] Genart last call review of draft-ietf-dots-rfc8782-bis-05
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: Thu, 27 May 2021 04:48:40 -0000

Hi Dale,

A bit thanks for your careful (as always) review.
Med, thanks for responding and updating the document.

I think there's just one point left that I want to comment on:

On Tue, Mar 23, 2021 at 12:38:20PM +0000, mohamed.boucadair@orange.com wrote:
> Hi Dale, 
> 
> Thank you for the careful review. Much appreciated!
> 
> The changes to take into account your review can be tracked at: https://tinyurl.com/8782bis-latest. 
> 
> Please see inline. 
> 
> Cheers,
> Med
> 
> > -----Message d'origine-----
> > De : Dale Worley via Datatracker [mailto:noreply@ietf.org]
> > Envoyé : mardi 23 mars 2021 01:42
> > À : gen-art@ietf.org
> > Cc : dots@ietf.org; draft-ietf-dots-rfc8782-bis.all@ietf.org; last-
> > call@ietf.org
> > Objet : Genart last call review of draft-ietf-dots-rfc8782-bis-05
> > 
[...]
> >   Also, you need to specify whether
> > the connection to the alternate server is a new session (with
> > independent state) or whether it is expected to be a continuation of
> > the existing session (carrying the same state).
> 
> [Med] This is covered here:
> 
>    When the DOTS client receives a 5.03 response with an alternate
>    server included, it considers the current request to have failed, but
>    it SHOULD try resending the request to the alternate DOTS server.

This seems to imply that the session state indeed is preserved across the
change of server, since it is just "resending the request" without mention
of reestablishing aliases or other setup.  We probably should be more
explicit about what we expect to happen, here.

Thanks,

Ben


From nobody Wed May 26 21:58:32 2021
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 501403A08F9; Wed, 26 May 2021 21:58:30 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Kaduk via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dots-rfc8782-bis@ietf.org, dots-chairs@ietf.org, dots@ietf.org,  valery@smyslov.net, valery@smyslov.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Benjamin Kaduk <kaduk@mit.edu>
Message-ID: <162209150978.23407.5280863704183505347@ietfa.amsl.com>
Date: Wed, 26 May 2021 21:58:30 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/f6ctja36YHAiwMpVJKdbWvyrpnE>
Subject: [Dots] Benjamin Kaduk's Yes on draft-ietf-dots-rfc8782-bis-06: (with COMMENT)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 May 2021 04:58:31 -0000

Benjamin Kaduk has entered the following ballot position for
draft-ietf-dots-rfc8782-bis-06: Yes

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dots-rfc8782-bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

In Section 4.4.1.3, the description of 'conflict-scope' for the case of
conflicting requests from different clients has lost the "a list of
prefixes" item as a possible scope.  (The analogous text for the
"conflicting with a different 'mid' case does still list prefixes as
possible.)

I see that there was some discussion in the genart thread about whether
the "conflict-information" tree is really "optional" in certain cases.
However, in going from the -04 to the -06, we also lost the marking that
it "must only be used for responses", and I didn't quite follow why that
change was needed.  (I am not sure that we need to change the text, but
please help me understand whether the node can be present in requests as
well.)


The genart reviewer also remarked:

>   Also, you need to specify whether
> the connection to the alternate server is a new session (with
> independent state) or whether it is expected to be a continuation of
> the existing session (carrying the same state).

to which Med responds "This is covered here:

   When the DOTS client receives a 5.03 response with an alternate
   server included, it considers the current request to have failed, but
   it SHOULD try resending the request to the alternate DOTS server."

This wording seems to imply that the session state is preserved, but I
think it would be beneficial to be explicit about it.


>From the secdir thread, in Section 7.3, we may not need a new normative
requirement that essentially duplicates what's already stated in RFC
6347.  Since RFC 6347 already has a "MUST fit"
requirement, we could just rely on that and avoid using new normative
language, perhaps as:

  To avoid DOTS signal message fragmentation and the subsequent
  decreased probability of message delivery, the DLTS records need to
  fit within a single datagram [RFC6347].




From nobody Thu May 27 00:05:23 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id A5AEB3A0ED9; Thu, 27 May 2021 00:05:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <162209911060.31874.14053452830202176284@ietfa.amsl.com>
Date: Thu, 27 May 2021 00:05:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/GTJqv7aE3ZFmKj9uWVsVkCRsgco>
Subject: [Dots] I-D Action: draft-ietf-dots-signal-call-home-14.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 May 2021 07:05:11 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Call Home
        Authors         : Tirumaleswar Reddy
                          Mohamed Boucadair
                          Jon Shallow
	Filename        : draft-ietf-dots-signal-call-home-14.txt
	Pages           : 43
	Date            : 2021-05-27

Abstract:
   This document specifies the DOTS signal channel Call Home, which
   enables a Call Home DOTS server to initiate a secure connection to a
   Call Home DOTS client, and to receive attack traffic information from
   the Call Home DOTS client.  The Call Home DOTS server in turn uses
   the attack traffic information to identify compromised devices
   launching outgoing DDoS attacks and take appropriate mitigation
   action(s).

   The DOTS signal channel Call Home is not specific to home networks;
   the solution targets any deployment in which it is required to block
   DDoS attack traffic closer to the source(s) of a DDoS attack.

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: Distributed Denial-of-Service Open Threat Signaling
      (DOTS) Signal Channel Call Home";

   o  "| [RFCXXXX] |"

   o  reference: RFC XXXX

   Please update this statement with the RFC number to be assigned to
   the following documents:

   o  "RFC YYYY: Distributed Denial-of-Service Open Threat Signaling
      (DOTS) Signal Channel Specification" (used to be I-D.ietf-dots-
      rfc8782-bis)

   Please update TBD/TBA statements with the assignments made by IANA to
   DOTS Signal Channel Call Home.

   Also, please update the "revision" date of the YANG module.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-signal-call-home/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-call-home-14

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-call-home-14


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Thu May 27 05:43:43 2021
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E7643A0688; Thu, 27 May 2021 05:43:37 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: dots@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <162211941701.26623.6410865804803479167@ietfa.amsl.com>
Date: Thu, 27 May 2021 05:43:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/8YdbahiiSKrUhzetVOI46NZzk9o>
Subject: [Dots] I-D Action: draft-ietf-dots-rfc8782-bis-07.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 27 May 2021 12:43:37 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the DDoS Open Threat Signaling WG of the IETF.

        Title           : Distributed Denial-of-Service Open Threat Signaling (DOTS) Signal Channel Specification
        Authors         : Mohamed Boucadair
                          Jon Shallow
                          Tirumaleswar Reddy.K
	Filename        : draft-ietf-dots-rfc8782-bis-07.txt
	Pages           : 117
	Date            : 2021-05-27

Abstract:
   This document specifies the Distributed Denial-of-Service Open Threat
   Signaling (DOTS) signal channel, a protocol for signaling the need
   for protection against Distributed Denial-of-Service (DDoS) attacks
   to a server capable of enabling network traffic mitigation on behalf
   of the requesting client.

   A companion document defines the DOTS data channel, a separate
   reliable communication layer for DOTS management and configuration
   purposes.

   This document obsoletes RFC 8782.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dots-rfc8782-bis/

There is also an htmlized version available at:
https://datatracker.ietf.org/doc/html/draft-ietf-dots-rfc8782-bis-07

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-rfc8782-bis-07


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/



From nobody Thu May 27 05:47:06 2021
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 957A43A0474; Thu, 27 May 2021 05:47:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zjofZzu9YH5d; Thu, 27 May 2021 05:46:55 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B159A3A0524; Thu, 27 May 2021 05:46:54 -0700 (PDT)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 4FrSHv5t0XzBtZT; Thu, 27 May 2021 14:46:51 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1622119611; bh=e0kzb81SbQGdwD4+LQZAeGHmkfhCWgbc4tdylkc5n4o=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=noqCNqzgU4/sBiDAHBk0nMF+hr7DDS3tX20VYaaa56RJigdpb2hQqO5lD2efX7XNv +Qe+pX38EytCqkI6D12KJJrpiFaPyDOu+5X6AXduIYXSkj1Z3DZjDPO3cr+B6c+cgR i5TYspOMXZ0MR5MHrEC0K2671lqz+4UH+zbmKcC04cbNMT4S1h/ClF6hkSmD0/lGaq 1kq0IPpAGLcvA4JJ2+jdh2ZkW2o89yVNOpwLvPGXSjr9Z9UxcsQMVOzqcvUuFXtx41 z1CiqoHi2oRhID1F5e9y0yHhOMrNVvxb0sdQ1yKcK3z8enF5YDw75DEUuJUshtLFkJ cO1omMg3kTbcw==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.51]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 4FrSHv4Mqcz3wbh; Thu, 27 May 2021 14:46:51 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: Benjamin Kaduk <kaduk@mit.edu>, Dale Worley <worley@ariadne.com>
CC: "draft-ietf-dots-rfc8782-bis.all@ietf.org" <draft-ietf-dots-rfc8782-bis.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>, "gen-art@ietf.org" <gen-art@ietf.org>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] Genart last call review of draft-ietf-dots-rfc8782-bis-05
Thread-Index: AQHXUrOXh1FMpIgGwUqtj08LIZW/cKr3RrEw
Date: Thu, 27 May 2021 12:46:50 +0000
Message-ID: <5503_1622119611_60AF94BB_5503_219_16_787AE7BB302AE849A7480A190F8B93303538FF03@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <161646013325.22110.15904279569991264804@ietfa.amsl.com> <14598_1616503101_6059E13C_14598_15_12_787AE7BB302AE849A7480A190F8B93303535A30C@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <20210527044746.GU32395@kduck.mit.edu>
In-Reply-To: <20210527044746.GU32395@kduck.mit.edu>
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/r9gy-aN2WwZNkKbtf5GRrNRZjYc>
Subject: Re: [Dots] Genart last call review of draft-ietf-dots-rfc8782-bis-05
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: Thu, 27 May 2021 12:47:01 -0000

Hi Ben, Dale, all,=20

> > >   Also, you need to specify whether
> > > the connection to the alternate server is a new session (with
> > > independent state) or whether it is expected to be a continuation
> of
> > > the existing session (carrying the same state).
> >
> > [Med] This is covered here:
> >
> >    When the DOTS client receives a 5.03 response with an alternate
> >    server included, it considers the current request to have
> failed, but
> >    it SHOULD try resending the request to the alternate DOTS
> server.
>=20
> This seems to imply that the session state indeed is preserved across
> the change of server, since it is just "resending the request"
> without mention of reestablishing aliases or other setup.  We
> probably should be more explicit about what we expect to happen,
> here.

Sure. Added a note to explicit the expected behavior:
https://www.ietf.org/rfcdiff?url1=3Ddraft-ietf-dots-rfc8782-bis-06&url2=3Dd=
raft-ietf-dots-rfc8782-bis-07=20

Cheers,
Med

> -----Message d'origine-----
> De=A0: Dots [mailto:dots-bounces@ietf.org] De la part de Benjamin Kaduk
> Envoy=E9=A0: jeudi 27 mai 2021 06:48
> =C0=A0: BOUCADAIR Mohamed TGI/OLN <mohamed.boucadair@orange.com>
> Cc=A0: draft-ietf-dots-rfc8782-bis.all@ietf.org; last-call@ietf.org;
> gen-art@ietf.org; Dale Worley <worley@ariadne.com>; dots@ietf.org
> Objet=A0: Re: [Dots] Genart last call review of draft-ietf-dots-
> rfc8782-bis-05
>=20
> Hi Dale,
>=20
> A bit thanks for your careful (as always) review.
> Med, thanks for responding and updating the document.
>=20
> I think there's just one point left that I want to comment on:
>=20
> On Tue, Mar 23, 2021 at 12:38:20PM +0000,
> mohamed.boucadair@orange.com wrote:
> > Hi Dale,
> >
> > Thank you for the careful review. Much appreciated!
> >
> > The changes to take into account your review can be tracked at:
> https://tinyurl.com/8782bis-latest.
> >
> > Please see inline.
> >
> > Cheers,
> > Med
> >
> > > -----Message d'origine-----
> > > De=A0: Dale Worley via Datatracker [mailto:noreply@ietf.org]
> Envoy=E9=A0:
> > > mardi 23 mars 2021 01:42 =C0=A0: gen-art@ietf.org Cc=A0: dots@ietf.or=
g;
> > > draft-ietf-dots-rfc8782-bis.all@ietf.org; last- call@ietf.org
> Objet
> > > : Genart last call review of draft-ietf-dots-rfc8782-bis-05
> > >
> [...]
> > >   Also, you need to specify whether
> > > the connection to the alternate server is a new session (with
> > > independent state) or whether it is expected to be a continuation
> of
> > > the existing session (carrying the same state).
> >
> > [Med] This is covered here:
> >
> >    When the DOTS client receives a 5.03 response with an alternate
> >    server included, it considers the current request to have
> failed, but
> >    it SHOULD try resending the request to the alternate DOTS
> server.
>=20
> This seems to imply that the session state indeed is preserved across
> the change of server, since it is just "resending the request"
> without mention of reestablishing aliases or other setup.  We
> probably should be more explicit about what we expect to happen,
> here.
>=20
> Thanks,
>=20
> Ben=20

___________________________________________________________________________=
______________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confiden=
tielles 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 el=
ectroniques 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 inf=
ormation 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 dele=
te 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.


From nobody Thu May 27 14:34:52 2021
Return-Path: <wwwrun@rfc-editor.org>
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 2B1773A13D0; Thu, 27 May 2021 14:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 d6ecnq337npd; Thu, 27 May 2021 14:34:45 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6959B3A13D5; Thu, 27 May 2021 14:34:45 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 69ABCF40719; Thu, 27 May 2021 14:34:31 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, dots@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210527213431.69ABCF40719@rfc-editor.org>
Date: Thu, 27 May 2021 14:34:31 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/Bc-oFZX3bxFjHOHuayi8qV8UvGU>
Subject: [Dots] =?utf-8?q?RFC_8903_on_Use_Cases_for_DDoS_Open_Threat_Sign?= =?utf-8?q?aling?=
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: Thu, 27 May 2021 21:34:50 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8903

        Title:      Use Cases for DDoS Open 
                    Threat Signaling 
        Author:     R. Dobbins,
                    D. Migault,
                    R. Moskowitz,
                    N. Teague,
                    L. Xia,
                    K. Nishizuka
        Status:     Informational
        Stream:     IETF
        Date:       May 2021
        Mailbox:    roland.dobbins@netscout.com,
                    daniel.migault@ericsson.com,
                    rgm@labs.htt-consult.com,
                    nteague@ironmountain.co.uk,
                    frank.xialiang@huawei.com,
                    kaname@nttv6.jp
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dots-use-cases-25.txt

        URL:        https://www.rfc-editor.org/info/rfc8903

        DOI:        10.17487/RFC8903

The DDoS Open Threat Signaling (DOTS) effort is intended to provide
protocols to facilitate interoperability across disparate DDoS
Mitigation solutions. This document presents sample use cases that
describe the interactions expected between the DOTS components as
well as DOTS messaging exchanges. These use cases are meant to
identify the interacting DOTS components, how they collaborate, and
what the typical information to be exchanged is.

This document is a product of the DDoS Open Threat Signaling Working Group of the IETF.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon May 31 02:32:09 2021
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7CBE53A0CCE; Mon, 31 May 2021 02:31:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Lars Eggert via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dots-rfc8782-bis@ietf.org, dots-chairs@ietf.org, dots@ietf.org,  valery@smyslov.net, valery@smyslov.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Lars Eggert <lars@eggert.org>
Message-ID: <162245351898.5006.16218698122336319008@ietfa.amsl.com>
Date: Mon, 31 May 2021 02:31:59 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/Kh1-yFbPMtmy6Jq04kqXEC44d_g>
Subject: [Dots] Lars Eggert's No Objection on draft-ietf-dots-rfc8782-bis-07: (with COMMENT)
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 31 May 2021 09:32:00 -0000

Lars Eggert has entered the following ballot position for
draft-ietf-dots-rfc8782-bis-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dots-rfc8782-bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

All comments below are about very minor potential issues that you may choose to
address in some way - or ignore - as you see fit. Some were flagged by
automated tools (via https://github.com/larseggert/ietf-reviewtool), so there
will likely be some false positives. There is no need to let me know what you
did with these suggestions.

Section 4.3, paragraph 2, nit:
-    connectionless and connection-oriented protocols.  As such, the DOTS
+    connection-less and connection-oriented protocols.  As such, the DOTS
+              +

Section 4.4.1.1, paragraph 39, nit:
-       The use of FQDNs may be suboptimal because:
+       The use of FQDNs may be suboptimal, because:
+                                         +

Section 5.3, paragraph 26, nit:
-                 Ths is is a mandatory attribute when a client
-                   --
+                 This is a mandatory attribute when a client

Section 10.1, paragraph 3, nit:
-    assigned to this docuement:
-                         -
+    assigned to this document:

Section 1, paragraph 5, nit:
> lient. The DOTS server may or may not not be co-located with the DOTS mitiga
>                                   ^^^^^^^
Double negatives are discouraged in standard English. Can you reformulate this
phrase or is a comma missing?

Section 4.4.1.1, paragraph 3, nit:
> ys MUST handle 'cuid' collision directly and it is RECOMMENDED that 'cuid' c
>                                 ^^^^^^^^^^^^
Use a comma before 'and' if it connects two independent clauses (unless they
are closely connected and short).

Section 4.4.3, paragraph 6, nit:
> DOTS client will send a Reset | message so it does not receive any more retra
>                                 ^^^^^^^^^^
Use a comma before 'so' if it connects two independent clauses (unless they are
closely connected and short).

Section 4.5.1, paragraph 22, nit:
> rtbeat frequency. It is NOT RECOMMENDED to return a Max-Age Option set to 0.
>                             ^^^^^^^^^^^^^^^^^^^^^
The verb 'RECOMMENDED' is used with the gerund form: "RECOMMENDED returning".

Section 6, paragraph 5, nit:
> S server when the Content-Format is used but the request is not formatted as
>                                     ^^^^
Use a comma before 'but' if it connects two independent clauses (unless they
are closely connected and short).

Section 6, paragraph 5, nit:
> ' URI IANA is requested to update the the 'dots' well-known URI (Table 6) en
>                                   ^^^^^^^
Possible typo: you repeated a word

Obsolete reference to RFC5246, obsoleted by RFC8446.

Document references draft-ietf-dots-multihoming-05, but -06 is the latest
available revision.

Document references draft-ietf-dots-telemetry-15, but -16 is the latest
available revision.

Document references draft-ietf-dots-use-cases, but that has been published as
RFC8903.

These URLs in the document can probably be converted to HTTPS:
 * http://www.iana.org/assignments/cbor-tags/cbor-tags.xhtml
 * http://www.iana.org/assignments/media-types
 * http://www.iana.org/assignments/core-parameters/core-parameters.xhtml#content-formats
 * http://www.iana.org/assignments/protocol-numbers




From nobody Mon May 31 02:33:29 2021
Return-Path: <lars@eggert.org>
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 875B23A0CDF; Mon, 31 May 2021 02:33:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=eggert.org
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 3gF-Y1ZenFHT; Mon, 31 May 2021 02:33:21 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:4000:400:211:32ff:fe22:186f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0460C3A0CDA; Mon, 31 May 2021 02:33:20 -0700 (PDT)
Received: from smtpclient.apple (unknown [212.68.24.84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 91900600315; Mon, 31 May 2021 12:33:09 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1622453589; bh=rQjOnHcUeZZYgksMPfKC+RF74N6UGlVxxPhb+sfRJ9Y=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=JeDZLR0KtuNPXjefY5ZCKQYNcqPjBNaaEoTXmIByHh9BMBj/hTcAs739wuqoUwHb4 UyRYkdOye2BwHIAqDNRX8JhRSk4tv/cxMLzjQklxN7PmnZ4PPhg/rKfgbPbDDfy64A 6Qi1zJnMsBBQW2xS1IzO9BRayVLgSgw/CYh8k3BQ=
From: Lars Eggert <lars@eggert.org>
Message-Id: <8BA869CB-8411-488C-B653-B253E66AD71B@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_1C487B8C-3822-4400-97A2-C7A3A2B6E044"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Date: Mon, 31 May 2021 12:33:08 +0300
In-Reply-To: <161646013325.22110.15904279569991264804@ietfa.amsl.com>
Cc: General Area Review Team <gen-art@ietf.org>, draft-ietf-dots-rfc8782-bis.all@ietf.org, last-call@ietf.org, dots@ietf.org
To: Dale Worley <worley@ariadne.com>
References: <161646013325.22110.15904279569991264804@ietfa.amsl.com>
X-MailScanner-ID: 91900600315.A1294
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/9VEH9w9PxqnKGoqrMy1fcSlDMC4>
Subject: Re: [Dots] [Last-Call] Genart last call review of draft-ietf-dots-rfc8782-bis-05
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: Mon, 31 May 2021 09:33:27 -0000

--Apple-Mail=_1C487B8C-3822-4400-97A2-C7A3A2B6E044
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Dale, thank you for your extensive review. I have entered a No Objection =
ballot for this document based on the follow-up discussion.

Lars


> On 2021-3-23, at 2:42, Dale Worley via Datatracker <noreply@ietf.org> =
wrote:
>=20
> Reviewer: Dale Worley
> Review result: Ready with Issues
>=20
> I am the assigned Gen-ART reviewer for this draft. The General Area
> Review Team (Gen-ART) reviews all IETF documents being processed
> by the IESG for the IETF Chair.  Please treat these comments just
> like any other last call comments.
>=20
> For more information, please see the FAQ at
>=20
> <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.
>=20
> Document:  draft-ietf-dots-rfc8782-bis-05
> Reviewer:  Dale R. Worley
> Review Date:  2021-03-22
> IETF LC End Date:  2021-03-22
> IESG Telechat date:  unknown
>=20
> Summary:
>=20
>    This draft is on the right track but has open issues, described in
>    the review.
>=20
> I've provided a long list of minor editorial issues, and a short list
> of technical issues.  I suspect that the technical issues have been
> resolved in the practices of the community and that their apparent
> status as problems stems from not getting the wording properly
> aligned with practice.
>=20
> Major issues:
>=20
> The condition of two DOTS mitigation requests overlapping depends on
> addresses (and alternatives to them) but as defined in section 4.4.1,
> does NOT depend on port numbers.  However, other parts of the text
> seem to presume that port numbers are involved in testing for
> overlapping.  The correct choice needs to be established and the text
> made consistent.
>=20
> Does the requesting of a mitigation only withdraw overlapping
> mitigations that were requested using the same signal channel, or is
> the effect global?  If a mitigation request with trigger-mitigation =3D
> false is activated by ending of a signal channel, does reestablishing
> the channel withdraw it?  (Naively I thought it would, but that isn't
> stated.)  If so, how are the former and the current signal channels
> correlated, given that cuid collisions can prevent them from using the
> same common identifiers?  Indeed, the text does not make it clear how
> a mitigation that is triggered by the ending of a signal channel can
> be withdrawn, other than by the expiration of its timer.
>=20
> Minor issues:
>=20
> The 4.09 response is used to report cuid conflicts, but also various
> other conflicts.  Given that cuid conflicts require specific
> processing, and can happen when other conflicts could also be
> reported, it seems to me that for cuid conflicts, you want that the
> response MUST include conflict-information.
>=20
> In section 4.4.1 there is a discussion of a configuration where a
> client communicates through two different gateways to one same server
> using a different certificate to communicate with each gateway.  The
> text discusses a configuration where we want the two transaction
> streams to be treated as one by the client and server.  It seems to me
> that this is an unusual situation which can only succeed if both the
> client and server have specific configuration for it.  As a
> consequence, the situation doesn't need to be discussed in this
> document.  Conversely, the default result of this topology is that the
> client and server treat both transactions streams separately (and
> perhaps neither of them is aware of the overall topology).  It seems
> like this case should work correctly without any special
> considerations, and so does not need to be documented specifically,
> either.
>=20
> The overall framework for signal channel configuration is not clear.
> By default, I assume that the client sets the channel configuration,
> constrained by the limits on parameter values imposed by the server,
> and that these values apply to communication in both directions (when
> applicable).  The text in 4.5 and 4.5.1 is consistent with this model.
> However text in 4.5.2 talks about "agents" changing configuration
> values, which implies it's possible for the server to set channel
> configuration.  There is discussion in section 4.5.3 of a server
> sending "a validity time with a configuration it sends", which makes
> no sense if only the client can change the configuration -- the
> configuration won't change until the client changes it.  Also "the
> update of the configuration data if a change occurs at the DOTS server
> side".  The model needs to be established, and the text aligned with
> it.
>=20
> Nits/editorial comments:
>=20
> Global editorial issues:
>=20
> There is a lot of special terminology, and it would help if
> definitions were gathered in section 2.  Additionally, this would help
> reveal where the text uses undefined synonyms of defined terms,
> several cases of which I have spotted.
>=20
> There are issues involving "Observe".  One is at the start of section
> 4.4, where the text refers to "subscribe", but that is not the term
> used in CoAP, indeed CoAP deliberately avoids that term.  Also, unless
> one is familiar with CoAP, one thinks GET has no side-effects, and
> thus cannot possibly establish a subscription.  There are related
> issues in sections 4.4.2.1 and 4.4.2.2 that left me wondering for
> which GET requests Observe was mandatory and/or permitted and what
> values (0 and/or 1) were permitted.  I think it would help to start
> 4.4.2.1 with an overview discussion of the permitted/required uses of
> Observe in DOTS GET requests.
>=20
> It would help to have adjectives for a mitigation request with
> trigger-mitigation =3D false, and for a mitigation request with
> trigger-mitigation =3D true.
>=20
> It seems that "deactivating" a mitigation request is used as an
> undefined synonym of "withdrawing" it, but (on my first two reads), I
> thought it meant "delete".  At this point, I suspect that the words
> hide complexity which has not been made explicit:  the client
> "requests" a mitigation with trigger-mitigation =3D false, but the =
loss
> of the channel "activates" it.  Worse, "activation" causes the actions
> that are described as being caused by "requesting" a mitigation with
> trigger-mitigation =3D true.  A description of the states, the
> transitions between them, and the verbs to describe them should be
> given, perhaps in section 2.
>=20
> Section 4.4.1 is 16 pages long and really should be cut into a number
> of subsections.
>=20
> Section 4.4.1 contains two parallel but different
> definitions/discussions of conflict-information.  Not being in a
> position to print the document, I can't quite make out what is going
> on, but I suspect some reorganization of the section is in order to
> replace the two partial definitions with one complete one.  (This
> might be connected with the entries in section 9 and/or section 10.3.)
> The two parallel definitions are partially excerpted below, and both
> have the problem that the contextual text says that the response will
> include "enough information for a DOTS client to recognize ...", but
> the definition of conflict-information states that it is optional:
>=20
> -----
>=20
>   The response includes enough information for a DOTS client to
>   recognize the source of the conflict as described below in the
>   'conflict-information' subtree with only the relevant nodes listed:
>=20
>   conflict-information:  Indicates that a mitigation request is
>      conflicting with another mitigation request.  This optional
>      attribute has the following structure:
>=20
> -----
>=20
>   For both 2.01
>   (Created) and 4.09 (Conflict) responses, the response includes =
enough
>   information for a DOTS client to recognize the source of the =
conflict
>   as described below:
>=20
>   conflict-information:  Indicates that a mitigation request is
>      conflicting with another mitigation request(s) from other DOTS
>      client(s).  This optional attribute has the following structure:
>=20
> -----
>=20
> Detailed editorial issues:
>=20
> (Note that some of these are summarized in a clearer way above.)
>=20
> 1.  Introduction
>=20
> The example of Figure 1 is introduced by this paragraph:
>=20
>   An example of a network diagram that illustrates a deployment of =
DOTS
>   agents is shown in Figure 1.  In this example, a DOTS server is
>   operating on the access network.  A DOTS client is located on the =
LAN
>   (Local Area Network), while a DOTS gateway is embedded in the CPE
>   (Customer Premises Equipment).
>=20
> But the example also includes a DOTS gateway, and would have been
> clearer to me if the statement introducing DOTS gateways was made
> before the start of the example rather than after it:
>=20
>   The DOTS client can
>   communicate directly with a DOTS server or indirectly via a DOTS
>   gateway.
>=20
> 3.  Design Overview
>=20
>   support for asynchronous Non-confirmable messaging
>=20
> It might be worth noting here or in section 2 that "Non-confirmable"
> (and "Confirmable") are CoAP technical terms.
>=20
>   Absent such mutual agreement, the DOTS
>   signal channel MUST run over port number 4646 as defined in
>   Section 10.1, for both UDP and TCP.
>=20
> It might be worth stating this port number is for both the client and
> the server to use (or that 4646 is just the listening port for
> servers).
>=20
>   Also, the DOTS server may rely on the signal
>   channel session loss to trigger mitigation for preconfigured
>   mitigation requests (if any).
>=20
> This doesn't carry quite the right idea.  What is really going on is
> that the DOTS client may configure mitigation requests that will be
> automatically acted upon by the server if the signal channel session
> is lost.  This is a required facility of the server, but it may be
> relied upon by the client.
>=20
>   DOTS signaling can happen with DTLS over UDP and TLS over TCP.
>=20
> s/can happen/can use/ or perhaps "can happen over".
>=20
>   In deployments where multiple DOTS clients are enabled in a network
>   (owned and operated by the same entity) ...
>=20
> I think you want something like "In deployments with multiple DOTS
> clients in a single network and administrative domain ...".
>=20
>   o  Port Control Protocol (PCP) [RFC6887] or Session Traversal
>      Utilities for NAT (STUN) [RFC8489] may be used to retrieve the
>      external addresses/prefixes and/or port numbers.
>=20
> Would be clearer if it is "may be used by the client to retrieve ...",
> as the preceding paragraph is about the translator and here we are
> talking about the client without explicitly mentioning it.
>=20
> 4.4.  DOTS Mitigation Methods
>=20
>   GET:    DOTS clients may use the GET method to subscribe to DOTS
>           server status messages or to retrieve the list of its
>           mitigations maintained by a DOTS server (Section 4.4.2).
>=20
> Unless one is aware of the "Observe" option of CoAP, using GET to
> establish a subscription seems impossible, as it is a side-effect.
> The reader could be warned by wording like:
>=20
>   GET:    DOTS clients may use the GET method to retrieve the list
>           of its mitigations maintained by a DOTS server (Section
>           4.4.2), or (using the CoAP Observe option [RFC7641]) to
>           subscribe to DOTS server status messages.
>=20
> --
>=20
>   Mitigation requests MUST NOT be delayed
>   because of checks on probing rate (Section 4.7 of [RFC7252]).
>=20
> How does this sentence connect with the preceding sentences of the
> paragraph?  Also, what does "probing" refer to?  I suspect you mean
> that mitigation requests can be Non-confirmable and would by default
> fall under the rules of the preceding sentences, but you don't want
> that.  So the sentence could be clarified as "However, mitigation
> requests MUST NOT be delayed by these limitations."
>=20
> 4.4.1.  Request Mitigation
>=20
>         with the trailing "=3D" removed from the encoding
>=20
> Should be 'the trailing two "=3D"', 'the trailing "=3D"s', or similar,
> since the base64 encoding of a string of 16 bytes will always end in
> two "=3D".
>=20
>         DOTS servers MUST return 4.09 (Conflict) error code to a DOTS
>         peer to notify that the 'cuid' is already in use by another
>         DOTS client.
>=20
> The error code 4.09 has other defined uses in the signal channel.
> Given the special and "global" action needed based on this error code,
> there must be an unambiguous way for the client to identify cuid
> collision.  Unfortunately, there is no "session initiation handshake"
> message for which a 4.09 response would be unambiguous.  It seems like
> the best choice is to look for conflict-information in the response,
> since it has a conflict-cause value "CUID Collision".  But
> conflict-information is optional.  I recommend making
> conflict-information mandatory in this situation.  However, see my
> comments at the end of the section regarding the lack of clarity
> whether conflict-information is mandatory or optional.
>=20
>         If the 'mid' value has reached 3/4 of (2^(32) - 1) (i.e.,
>         3221225471) and no attack is detected, the DOTS client MUST
>         reset 'mid' to 0 to handle 'mid' rollover.
>=20
> It sounds like, but does not say explicitly, that mid rollover =
automatically
> invalidates any active high-mid mitigation request, and thus, if the
> client wants to maintain any existing request, it must recreate them
> (necessarily with small mid values).  This needs to be clarified.
>=20
>      The default value of the parameter is 'true' (that is, the
>      mitigation starts immediately).  If 'trigger-mitigation' is not
>      present in a request, this is equivalent to receiving a request
>      with 'trigger-mitigation' set to 'true'.
>=20
> The second sentence is completely redundant, but I suspect that a
> practical need for it has been discovered.
>=20
>         ... or the 'cuid' was generated from a rogue DOTS client.
>=20
> Probably s/from/by/.
>=20
> But it seems that there is a valid situation where duplicate cuids are
> plausible, when two DOTS clients are using the same certificate to
> peer with a server because that certificate is what the server
> administrator provided to peer with the server.  I don't know if that
> is worth mentioning here, though.
>=20
>         If a DOTS client is provisioned, for example, with distinct
>         certificates as a function of the peer server-domain DOTS
>         gateway, distinct 'cdid' values may be supplied by a server-
>         domain DOTS gateway.  The ultimate DOTS server MUST treat =
those
>         'cdid' values as equivalent.
>=20
> I'm having a hard time following this, probably because I am not
> familiar with the language used to describe these situations.  I think
> it means
>=20
>         If a DOTS client is provisioned, for example, with distinct
>         certificates to use to peer with distinct server-domain DOTS
>         gateways that peer to the same DOTS server, distinct 'cdid'
>         values may be supplied by the gateways to the server.  The
>         ultimate DOTS server MUST treat those 'cdid' values as
>         equivalent.
>=20
> The final normative statement is clear, but it isn't clear to me how
> the server can implement that, unless it is provisioned with the
> knowledge that the two certificates are used by the same client.
>=20
> More subtly, if the server must treat them as equivalent, dependencies
> between transactions in one transaction stream apply to the union of
> the transaction streams through the two servers.  E.g. the rule that
> mid is nearly-monotonic and the consequences thereof.  Handling this
> correctly requires that the client knows that transactions through the
> two gateways will be handled equivalently by one same server, and that
> seems to require that the client also be configured with particular
> knowledge.
>=20
> It seems to me that there are actually two cases (1) a "dumb" case
> where the client happens to access the same server through two
> gateways, but neither the client nor the server knows that.  In that
> case, the signal channel protocol "just works" normally. (2) a "smart"
> case where both the client and serve must know that access through the
> two gateways is considered equivalent (but the gateways do not need to
> know).  In that case, as long as both the client and server agree on
> this equivalence, the signal channel protocol also "just works".
>=20
> It's not clear that it is necessary to document here the "smart" case,
> as the needed adjustments are logically determined by the intended use
> case.  If it is not needed, the quoted paragraph is probably best
> omitted, because trying to implement it generally would tend to cause
> the "dumb" case to fail.
>=20
>   If the mitigation request
>   contains the 'alias-name' and other parameters identifying the =
target
>   resources (such as 'target-prefix', 'target-port-range', 'target-
>   fqdn', or 'target-uri'), the DOTS server appends the parameter =
values
>   in 'alias-name' with the corresponding parameter values in 'target-
>   prefix', 'target-port-range', 'target-fqdn', or 'target-uri'.
>=20
> This sentence is not connected with any other processing -- what use
> is the concatenated value put to?  Also, the processing described will
> NOT be done if alias-name is not present, suggesting that in some way
> it is optional.  Also, the phrase "the parameter values in
> 'alias-name'" is undefined, as alias-name is an opaque string value.
> I suspect that some aspect of the processing has not been described.
>=20
> Perhaps the meaning is that an alias is always configured as a set of
> values for the other parameters, and that if a request contains both
> an alias name and other parameters, the effective request is formed by
> merging the two sets of parameter values.  Though if that is meant,
> some provision must be made for the situation where the alias gives a
> value for a parameter that is contradicted by an explicit parameter in
> the request.
>=20
>   If the DOTS server does not find the 'mid' parameter value conveyed
>   in the PUT request in its configuration data [it may interpret it
>   in a certain way]
>=20
> It's not clear what is going on here, as "mid=3D..." is a mandatory =
part
> of the Uri-Path, and any such request must be rejected.
>=20
>   A DOTS server could reject mitigation requests when it is
>   near capacity or needs to rate-limit a particular client, for
>   example.
>=20
> This should be a separate paragraph, as it applies more broadly than
> the conditions of the first sentence of the paragraph.  Also, it
> probably merits s/could/MAY/.
>=20
>   Two mitigation requests from a DOTS
>   client have overlapping scopes if there is a common IP address, IP
>   prefix, FQDN, URI, or alias.
>=20
> Probably worth stating explicitly that a common port number is NOT a
> factor in determining overlapping scopes.
>=20
>   If the DOTS server receives a mitigation request that overlaps with
>   an active mitigation request, but both have distinct 'trigger-
>   mitigation' types, the DOTS server SHOULD deactivate (absent =
explicit
>   policy/configuration otherwise) the mitigation request with =
'trigger-
>   mitigation' set to 'false'.
>=20
> I'm pretty sure I don't know what this means.  What does "deactivate"
> mean?  The first time I read it, I thought it meant "delete", The
> second time, I suspected it meant the opposite action of "activate",
> which is what happens to a trigger-mitigation =3D false mitigation =
when
> the signal channel is lost.  The third time, I was wondering why
> the reestablishment of the signal channel didn't automatically
> cause the trigger-mitigation =3D false mitigation to be deactivated.
>=20
>      conflict-scope:  Characterizes the exact conflict scope.  It may
>         include a list of IP addresses, a list of prefixes, a list of
>         port numbers, a list of target protocols, a list of FQDNs, a
>         list of URIs, a list of aliases, or references to conflicting
>         ACLs (by an 'acl-name', typically [RFC8783]).
>=20
> Note this text includes a "list of port numbers", but port numbers are
> not a factor in conflicts.
>=20
> Also, is it really intended that this parameter is, effectively, only
> human-readable, since there is no particular way to specify what type
> of datum the value contains?
>=20
> 4.4.2.  Retrieve Information Related to a Mitigation
>=20
>    +-----------+----------------------------------------------------+
>    |         4 | Attack has exceeded the mitigation provider        |
>    |           | capability.                                        |
>    +-----------+----------------------------------------------------+
>=20
> "mitigation provider" is used in a few places but it appears that the
> intended term is "mitigator".
>=20
>    +-----------+----------------------------------------------------+
>    |         6 | Attack mitigation is now terminated.               |
>    +-----------+----------------------------------------------------+
>=20
> It seems like code 6 includes codes 5 and 7.  Is this ambiguity
> intended?  I suspect the text that is actually wanted is "DOTS client
> has withdrawn the mitigation request and the attack mitigation is now
> terminated."  There is a parallel issue in section 10.6.2.
>=20
> 4.4.2.1.  DOTS Servers Sending Mitigation Status
>=20
>   DOTS
>   implementations MUST use the Observe Option for both 'mitigate' and
>   'config' (Section 4.2).
>=20
> It's not clear what "MUST use the Observe Option" means.  Does it mean
> that clients MUST use it in GET requests for 'mitigate' and 'config'?
> If so, is the client allowed to use "Observe: 1", despite that this
> section only discusses the "Observe: 0" case?  Or does it just mean
> that servers must implement it, and thus respond correctly if a client
> sends it?
>=20
> 4.4.2.2.  DOTS Clients Polling for Mitigation Status
>=20
>   In such case, the DOTS client recalls the mitigation request by
>   issuing a DELETE request for this mitigation request (Section =
4.4.4).
>=20
> The term "recall" is used in a few places but it seems like the
> correct term is "withdraw" (section 4.4.4).
>=20
> 4.4.3.  Efficacy Update from DOTS Clients
>=20
> In what way is an "efficacy update" different from an "update"?  Can
> "efficacy" be removed without loss, or is it a term of art for updates
> to mitigation requests sent during attacks?
>=20
> It appears that an update is an "efficacy update" if and only if
> "attack-status" is present.  This should be stated at the beginning of
> the section, as otherwise it's a mystery what distinguishes "efficacy
> updates".
>=20
> 4.4.4.  Withdraw a Mitigation
>=20
>   Once the request is validated, the DOTS server immediately
>   acknowledges a DOTS client's request to withdraw the DOTS signal
>   using 2.02 (Deleted) Response Code with no response payload.
>=20
> s/DOTS signal/DOTS mitigation request/
>=20
> 4.5.  DOTS Signal Channel Session Configuration
>=20
>   d.  Acceptable signal loss ratio: Maximum retransmissions,
>       retransmission timeout value, and other message transmission
>       parameters for Confirmable messages over the DOTS signal =
channel.
>=20
> What are the names of these parameters in the signal-config structure?
>=20
>   As such, the transmission-related
>   parameters ('missing-hb-allowed' and acceptable signal loss ratio)
>   are negotiated only for DOTS over unreliable transports.
>=20
> It seems this could be said more clearly by listing the permitted
> fields:  "only the 'heartbeat-interval' parameter [or whatever] is
> negotiated for DOTS over reliable transports".
>=20
> 4.5.1.  Discover Configuration Parameters
>=20
>   At least one of the attributes 'heartbeat-interval', 'missing-hb-
>   allowed', 'probing-rate', 'max-retransmit', 'ack-timeout', and 'ack-
>   random-factor' MUST be present in the PUT request.  Note that
>   'heartbeat-interval', 'missing-hb-allowed', 'probing-rate', 'max-
>   retransmit', 'ack-timeout', and 'ack-random-factor', if present, do
>   not need to be provided for both 'mitigating-config', and 'idle-
>   config' in a PUT request.
>=20
> Must both the mitigating and idle configuration sections be present in
> the PUT?  Does the requirement "At least one..." apply to both
> sections together or each section alone?  If e.g. missing-hb-allowed
> is present in one section but not the other, the wording gives a vague
> suggestion that the same value is implicitly provided for the other
> section.  Is this true?
>=20
>   The PUT request with a higher numeric 'sid' value overrides the DOTS
>   signal channel session configuration data installed by a PUT request
>   with a lower numeric 'sid' value.  To avoid maintaining a long list
>   of 'sid' requests from a DOTS client, the lower numeric 'sid' MUST =
be
>   automatically deleted and no longer available at the DOTS server.
>=20
> Does this mean that the PUT with the higher sid installs what values
> it provides on top of the current configuration, or does it mean that
> the previous PUT's effect is entirely removed, that is, parameters not
> given in the higher-sid PUT take their default values?  Note that the
> latter is resistant to problems from lost PUT requests but the former
> is not.
>=20
>   o  If the DOTS server finds the 'sid' parameter value conveyed in =
the
>      PUT request in its configuration data and if the DOTS server has
>      accepted the updated configuration parameters, 2.04 (Changed) =
MUST
>      be returned in the response.
>=20
> Given the earlier statement "'sid' values MUST increase monotonically
> (when a new PUT is generated by a DOTS client to convey the
> configuration parameters for the signal channel).", if a server
> receives a PUT with the same sid as a previous PUT then the client is
> misbehaving and the server should send an error response.
>=20
>   A DOTS client may issue a GET message with a 'sid' Uri-Path =
parameter
>   to retrieve the negotiated configuration.
>=20
> Does this sid value matter, or is only its presence important?  Also,
> you probably want to expand this to "a GET message for 'config' with a
> 'sid' Uri-Path parameter ...".
>=20
> 4.5.3.  Configuration Freshness and Notifications
>=20
> The underlying processing is not made clear.  Roughly, it seems that
> the idea is the server has the right to change the configuration
> unilaterally at any time, but if the client does a GET of the
> configuration, the server is required to commit that it won't change
> the configuration given in the response within Max-Age Option seconds.
>=20
> Or is this talking about a mechanism where the server can, at its
> initiative, tell the client how the client should behave?  Which is
> completely different from section 4.5.2 where the client tells the
> server how to behave.
>=20
> 4.5.4.  Delete DOTS Signal Channel Session Configuration
>=20
>   Upon bootstrapping or reboot, a DOTS client MAY send a DELETE =
request
>   to set the configuration parameters to default values.  Such a
>   request does not include any 'sid'.
>=20
> I would take it as assumed that when the (D)TLS connection is
> established, that is, when the DOTS signal channel session is
> initiated, it has the default configuration parameters.  Thus the
> DELETE described here is guaranteed to have no effect.  But perhaps
> the intention is that the signal channel is conceptualized as
> persisting longer than the (D)TLS connection, and (perhaps) associated
> with the cuid/cdid value.  If so, that should be stated clearly.
>=20
> 4.6.  Redirected Signaling
>=20
>   If a DOTS server wants to redirect a DOTS client to an alternative
>   DOTS server for a signal session, then the Response Code 5.03
>   (Service Unavailable) will be returned in the response to the DOTS
>   client.
>=20
> What is "the response"?  It seems that this is only sensible if the
> session is just being established, but there doesn't seem to be a
> specific session-initiation message.  If you really mean that the
> server can redirect the session in response to any request, it would
> be helpful to state that directly.  Also, you need to specify whether
> the connection to the alternate server is a new session (with
> independent state) or whether it is expected to be a continuation of
> the existing session (carrying the same state).
>=20
> 4.7.  Heartbeat Mechanism
>=20
>   For
>   example, if a DOTS client receives a 2.04 response for its heartbeat
>   messages but no server-initiated heartbeat messages, the DOTS client
>   sets 'peer-hb-status' to 'false'.  The DOTS server then will ...
>=20
> There is a lot of detail left out here, as there are messages and
> events involved that are not mentioned explicitly.  I think what is
> meant is "For example, if a DOTS client receives a 2.04 response for
> its heartbeat messages but no server-initiated heartbeat messages, the
> DOTS client sets 'peer-hb-status' to 'false' in its next heartbeat
> message.  Upon receiving that message, the DOTS server then will ..."
>=20
> It might be useful to explicitly state that the bodies of responses to
> heartbeat requests are empty.
>=20
> 6.  YANG/JSON Mapping Parameters to CBOR
>=20
> It might help the implementors to tell whether this is the same as
> section 6 of RFC 8782 or not.
>=20
> 10.1.  DOTS Signal Channel UDP and TCP Port Number
>=20
>   IANA has assigned the port number 4646 (the ASCII decimal value for
>   ".." (DOTS)) ...
>=20
> Ow!
>=20
> [END]
>=20
>=20
>=20
> --
> last-call mailing list
> last-call@ietf.org
> https://www.ietf.org/mailman/listinfo/last-call


--Apple-Mail=_1C487B8C-3822-4400-97A2-C7A3A2B6E044
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAmC0rVQACgkQVLXDCb9w
wVdAzxAAh9B93Emkt4eUEAFxIJU+IeNThqWXhrj/w2i4Re0/1Pog9K5KVlKZP6ss
2qvMuDPmh97XyYG0XQmpikPXbQbmI8BV7JXh5a2RE3pGSeQw8r3JLXntEzHyLb2x
y1LCd0LL/0X03bA/e2mJWgnhgHQHNtH6JCuwCJcpSI0+/xHpslar/dbUcfT4mqyS
FnyrKhg9PoqmVbqs7uPRZuLdpOf/Xx0qLtMR9U/5Qpkm0ry8A4ymsJN/8zbdunjQ
cmBHWoPy9/TCsPqWej2i30fYn5L/GYnmPcpvTKoG4QT6iwJF6LFcdHY2yUt0KFHS
EhOOFWtIM46uzArs+IGuUeSvbtj+6hkicnaTDwtAyrRdDfE6v5NWcOn2gGCEUXn/
66TnVVaAi5owx2yNTw6b7d2fJmYcvbjd4BjnUFbt5vBpstdZn7Ejp/3kYcPdv3X6
/WFaI9bYPAOl/5ov6KFuwPEVz1/A/NPHMSqP01A0ieToBvenNTQljv1kHX9yBfYT
Som/WR6La/4Tl9+3CPPVZTzaJRD4P1+HYnO66t16BLAkZnqbdmaVIfjwiK1o+kH9
YWZGDoIAXYkFpEWtUCtf9J6WfLLP0f9cmlUoBGz8hx726kOo+6T9UvO3IcpxFDd5
nfOfSLczs+r/yWea6t84nxgVf5kKgqk+ZvUJP/2eVf6hCCsBOS8=
=bDiE
-----END PGP SIGNATURE-----

--Apple-Mail=_1C487B8C-3822-4400-97A2-C7A3A2B6E044--


From nobody Mon May 31 02:51:21 2021
Return-Path: <noreply@ietf.org>
X-Original-To: dots@ietf.org
Delivered-To: dots@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C23D43A0F49; Mon, 31 May 2021 02:51:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?=C3=89ric_Vyncke_via_Datatracker?= <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dots-rfc8782-bis@ietf.org, dots-chairs@ietf.org, dots@ietf.org,  valery@smyslov.net, valery@smyslov.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.30.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: =?utf-8?q?=C3=89ric_Vyncke?= <evyncke@cisco.com>
Message-ID: <162245467875.25457.5499708730835623241@ietfa.amsl.com>
Date: Mon, 31 May 2021 02:51:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/PELizk6GrVgUxI9-WlE6HuhW72I>
Subject: [Dots] =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf?= =?utf-8?q?-dots-rfc8782-bis-07=3A_=28with_COMMENT=29?=
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 31 May 2021 09:51:19 -0000

Ã‰ric Vyncke has entered the following ballot position for
draft-ietf-dots-rfc8782-bis-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dots-rfc8782-bis/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you for the work put into this document.

As I already reviewed the original RFC 8782, I have only review the diffs
(thanks to RFCDIFF!).

Please find below some non-blocking COMMENT points (but replies would be
appreciated).

I hope that this helps to improve the document,

Regards,

-Ã©ric

== COMMENTS ==

-- Section 3.1 --
In "that follow the present specification", the use of "present" is ambiguous:
does it mean current implementations of RFC 8782? or this specification (i.e.,
this I-D) ?

-- Section 4.4.1.3 --
I wonder why a port number can be used if the case of common/shared URI ? In "A
list of port numbers may also be included if there is a common IP address, IP
prefix, FQDN, URI, or alias."

-- Section 5.3 --
I am not a YANG module expert but using a union for 'lifetime' just to allow a
-1 value to signal infinity looks a little weird to me. Could the value
0x7fffffff be used for 'infinity' and keeping a uint32 ?

In probing-rate.current-value, there is a default value of 5 byte/second. Is it
useful to recommend such a default value ?

More generically, I wonder whether measuring in octets/second is more suitable
than in bits/second.

The 'alt-server' is now better typed as 'inet:domain-name' but I now wonder
whether relying solely on DNS in a case of DoS is sensible.




From nobody Mon May 31 02:56:16 2021
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 A934D3A0FE4; Mon, 31 May 2021 02:56:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJH5_4xRrfvi; Mon, 31 May 2021 02:56:09 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 468C23A0FE2; Mon, 31 May 2021 02:56:09 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 4FtrK31M1Cz2ycX; Mon, 31 May 2021 11:56:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1622454967; bh=GBkJeK6QM7NsBdbTC3yZgMlS7dWvgz8mIZi5N9DW8ZU=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=FWUz0qBKJJN/gTnYjgSqAQTg90AbxFyTtFLJuw7B1Q5h6gRP12iMI2zZYBEw40UlN XodYRkgZA+xCTvZ5PwF3fk0Q3l87cCf7CnobCX6XcWJx7BSiduxbA1l37N4+849Goo H0RX5rpF67fK0T27uZWo7ZGibBnizT7ZUnmqC2ZgXDj8FOkQVq1wWOPDwrCw8bq0N7 k4USDXVLzoKaHIT3XXEZrrCxGEZHQLebneg/+MjT1h70kiSc/GF2l/lWyMMzScpHgx btHxtZpBehLi33KKa88uoaT7SNJVNEi8QPjryxVngWYJf4eHkzc5AfJjc0mCJapjS2 22SXCQEID4OPg==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.89]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 4FtrK271mRzBrLR; Mon, 31 May 2021 11:56:06 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: Lars Eggert <lars@eggert.org>, The IESG <iesg@ietf.org>
CC: "draft-ietf-dots-rfc8782-bis@ietf.org" <draft-ietf-dots-rfc8782-bis@ietf.org>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "dots@ietf.org" <dots@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>
Thread-Topic: Lars Eggert's No Objection on draft-ietf-dots-rfc8782-bis-07: (with COMMENT)
Thread-Index: AQHXVf/YkFRfLoSqlU+4YWmZfNJ6Gar9WX7g
Date: Mon, 31 May 2021 09:56:06 +0000
Message-ID: <28845_1622454967_60B4B2B7_28845_190_1_787AE7BB302AE849A7480A190F8B933035394F2F@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <162245351898.5006.16218698122336319008@ietfa.amsl.com>
In-Reply-To: <162245351898.5006.16218698122336319008@ietfa.amsl.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.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/57W-TzWdzr_F9eFjfBXN7purMMs>
Subject: Re: [Dots] Lars Eggert's No Objection on draft-ietf-dots-rfc8782-bis-07: (with COMMENT)
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: Mon, 31 May 2021 09:56:15 -0000

SGkgTGFycywgDQoNClRoYW5rcyBmb3IgdGhlIHJldmlldy4gDQoNCkZpeGVkIHRoZSBuaXRzIHdo
ZW4gSSB0aGluayBpcyBuZWVkZWQ6IGh0dHBzOi8vdGlueXVybC5jb20vODc4MmJpcy1sYXRlc3Qu
IA0KDQpGb3IgdGhpcyBvbmU6IA0KDQo+IE9ic29sZXRlIHJlZmVyZW5jZSB0byBSRkM1MjQ2LCBv
YnNvbGV0ZWQgYnkgUkZDODQ0Ni4NCg0KVGhpcyBpcyBvbiBwdXJwb3NlIGFzIHlvdSBjYW4gc2Vl
IGluOiBodHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL2RvdHMvLVZhZlNqa1N1
eExEVmJ5d1hCa3kwcXIyZVdvLyANCg0KQ2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1NZXNzYWdlIGQn
b3JpZ2luZS0tLS0tDQo+IERlwqA6IExhcnMgRWdnZXJ0IHZpYSBEYXRhdHJhY2tlciBbbWFpbHRv
Om5vcmVwbHlAaWV0Zi5vcmddDQo+IEVudm95w6nCoDogbHVuZGkgMzEgbWFpIDIwMjEgMTE6MzIN
Cj4gw4DCoDogVGhlIElFU0cgPGllc2dAaWV0Zi5vcmc+DQo+IENjwqA6IGRyYWZ0LWlldGYtZG90
cy1yZmM4NzgyLWJpc0BpZXRmLm9yZzsgZG90cy1jaGFpcnNAaWV0Zi5vcmc7DQo+IGRvdHNAaWV0
Zi5vcmc7IHZhbGVyeUBzbXlzbG92Lm5ldDsgdmFsZXJ5QHNteXNsb3YubmV0DQo+IE9iamV0wqA6
IExhcnMgRWdnZXJ0J3MgTm8gT2JqZWN0aW9uIG9uIGRyYWZ0LWlldGYtZG90cy1yZmM4NzgyLWJp
cy0wNzoNCj4gKHdpdGggQ09NTUVOVCkNCj4gDQo+IExhcnMgRWdnZXJ0IGhhcyBlbnRlcmVkIHRo
ZSBmb2xsb3dpbmcgYmFsbG90IHBvc2l0aW9uIGZvcg0KPiBkcmFmdC1pZXRmLWRvdHMtcmZjODc4
Mi1iaXMtMDc6IE5vIE9iamVjdGlvbg0KPiANCj4gV2hlbiByZXNwb25kaW5nLCBwbGVhc2Uga2Vl
cCB0aGUgc3ViamVjdCBsaW5lIGludGFjdCBhbmQgcmVwbHkgdG8gYWxsDQo+IGVtYWlsIGFkZHJl
c3NlcyBpbmNsdWRlZCBpbiB0aGUgVG8gYW5kIENDIGxpbmVzLiAoRmVlbCBmcmVlIHRvIGN1dA0K
PiB0aGlzIGludHJvZHVjdG9yeSBwYXJhZ3JhcGgsIGhvd2V2ZXIuKQ0KPiANCj4gDQo+IFBsZWFz
ZSByZWZlciB0byBodHRwczovL3d3dy5pZXRmLm9yZy9pZXNnL3N0YXRlbWVudC9kaXNjdXNzLQ0K
PiBjcml0ZXJpYS5odG1sDQo+IGZvciBtb3JlIGluZm9ybWF0aW9uIGFib3V0IERJU0NVU1MgYW5k
IENPTU1FTlQgcG9zaXRpb25zLg0KPiANCj4gDQo+IFRoZSBkb2N1bWVudCwgYWxvbmcgd2l0aCBv
dGhlciBiYWxsb3QgcG9zaXRpb25zLCBjYW4gYmUgZm91bmQgaGVyZToNCj4gaHR0cHM6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtaWV0Zi1kb3RzLXJmYzg3ODItYmlzLw0KPiANCj4g
DQo+IA0KPiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4gLQ0KPiBDT01NRU5UOg0KPiAtLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCj4g
LQ0KPiANCj4gQWxsIGNvbW1lbnRzIGJlbG93IGFyZSBhYm91dCB2ZXJ5IG1pbm9yIHBvdGVudGlh
bCBpc3N1ZXMgdGhhdCB5b3UgbWF5DQo+IGNob29zZSB0byBhZGRyZXNzIGluIHNvbWUgd2F5IC0g
b3IgaWdub3JlIC0gYXMgeW91IHNlZSBmaXQuIFNvbWUgd2VyZQ0KPiBmbGFnZ2VkIGJ5IGF1dG9t
YXRlZCB0b29scyAodmlhIGh0dHBzOi8vZ2l0aHViLmNvbS9sYXJzZWdnZXJ0L2lldGYtDQo+IHJl
dmlld3Rvb2wpLCBzbyB0aGVyZSB3aWxsIGxpa2VseSBiZSBzb21lIGZhbHNlIHBvc2l0aXZlcy4g
VGhlcmUgaXMNCj4gbm8gbmVlZCB0byBsZXQgbWUga25vdyB3aGF0IHlvdSBkaWQgd2l0aCB0aGVz
ZSBzdWdnZXN0aW9ucy4NCj4gDQo+IFNlY3Rpb24gNC4zLCBwYXJhZ3JhcGggMiwgbml0Og0KPiAt
ICAgIGNvbm5lY3Rpb25sZXNzIGFuZCBjb25uZWN0aW9uLW9yaWVudGVkIHByb3RvY29scy4gIEFz
IHN1Y2gsIHRoZQ0KPiBET1RTDQo+ICsgICAgY29ubmVjdGlvbi1sZXNzIGFuZCBjb25uZWN0aW9u
LW9yaWVudGVkIHByb3RvY29scy4gIEFzIHN1Y2gsIHRoZQ0KPiBET1RTDQo+ICsgICAgICAgICAg
ICAgICsNCj4gDQo+IFNlY3Rpb24gNC40LjEuMSwgcGFyYWdyYXBoIDM5LCBuaXQ6DQo+IC0gICAg
ICAgVGhlIHVzZSBvZiBGUUROcyBtYXkgYmUgc3Vib3B0aW1hbCBiZWNhdXNlOg0KPiArICAgICAg
IFRoZSB1c2Ugb2YgRlFETnMgbWF5IGJlIHN1Ym9wdGltYWwsIGJlY2F1c2U6DQo+ICsgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICsNCj4gDQo+IFNlY3Rpb24gNS4zLCBw
YXJhZ3JhcGggMjYsIG5pdDoNCj4gLSAgICAgICAgICAgICAgICAgVGhzIGlzIGlzIGEgbWFuZGF0
b3J5IGF0dHJpYnV0ZSB3aGVuIGEgY2xpZW50DQo+IC0gICAgICAgICAgICAgICAgICAgLS0NCj4g
KyAgICAgICAgICAgICAgICAgVGhpcyBpcyBhIG1hbmRhdG9yeSBhdHRyaWJ1dGUgd2hlbiBhIGNs
aWVudA0KPiANCj4gU2VjdGlvbiAxMC4xLCBwYXJhZ3JhcGggMywgbml0Og0KPiAtICAgIGFzc2ln
bmVkIHRvIHRoaXMgZG9jdWVtZW50Og0KPiAtICAgICAgICAgICAgICAgICAgICAgICAgIC0NCj4g
KyAgICBhc3NpZ25lZCB0byB0aGlzIGRvY3VtZW50Og0KPiANCj4gU2VjdGlvbiAxLCBwYXJhZ3Jh
cGggNSwgbml0Og0KPiA+IGxpZW50LiBUaGUgRE9UUyBzZXJ2ZXIgbWF5IG9yIG1heSBub3Qgbm90
IGJlIGNvLWxvY2F0ZWQgd2l0aCB0aGUNCj4gRE9UUyBtaXRpZ2ENCj4gPiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgXl5eXl5eXg0KPiBEb3VibGUgbmVnYXRpdmVzIGFyZSBkaXNj
b3VyYWdlZCBpbiBzdGFuZGFyZCBFbmdsaXNoLiBDYW4geW91DQo+IHJlZm9ybXVsYXRlIHRoaXMg
cGhyYXNlIG9yIGlzIGEgY29tbWEgbWlzc2luZz8NCj4gDQo+IFNlY3Rpb24gNC40LjEuMSwgcGFy
YWdyYXBoIDMsIG5pdDoNCj4gPiB5cyBNVVNUIGhhbmRsZSAnY3VpZCcgY29sbGlzaW9uIGRpcmVj
dGx5IGFuZCBpdCBpcyBSRUNPTU1FTkRFRCB0aGF0DQo+ICdjdWlkJyBjDQo+ID4gICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICBeXl5eXl5eXl5eXl4NCj4gVXNlIGEgY29tbWEgYmVmb3Jl
ICdhbmQnIGlmIGl0IGNvbm5lY3RzIHR3byBpbmRlcGVuZGVudCBjbGF1c2VzDQo+ICh1bmxlc3Mg
dGhleSBhcmUgY2xvc2VseSBjb25uZWN0ZWQgYW5kIHNob3J0KS4NCj4gDQo+IFNlY3Rpb24gNC40
LjMsIHBhcmFncmFwaCA2LCBuaXQ6DQo+ID4gRE9UUyBjbGllbnQgd2lsbCBzZW5kIGEgUmVzZXQg
fCBtZXNzYWdlIHNvIGl0IGRvZXMgbm90IHJlY2VpdmUgYW55DQo+IG1vcmUgcmV0cmENCj4gPiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIF5eXl5eXl5eXl4NCj4gVXNlIGEgY29tbWEg
YmVmb3JlICdzbycgaWYgaXQgY29ubmVjdHMgdHdvIGluZGVwZW5kZW50IGNsYXVzZXMNCj4gKHVu
bGVzcyB0aGV5IGFyZSBjbG9zZWx5IGNvbm5lY3RlZCBhbmQgc2hvcnQpLg0KPiANCj4gU2VjdGlv
biA0LjUuMSwgcGFyYWdyYXBoIDIyLCBuaXQ6DQo+ID4gcnRiZWF0IGZyZXF1ZW5jeS4gSXQgaXMg
Tk9UIFJFQ09NTUVOREVEIHRvIHJldHVybiBhIE1heC1BZ2UgT3B0aW9uDQo+IHNldCB0byAwLg0K
PiA+ICAgICAgICAgICAgICAgICAgICAgICAgICAgICBeXl5eXl5eXl5eXl5eXl5eXl5eXl4NCj4g
VGhlIHZlcmIgJ1JFQ09NTUVOREVEJyBpcyB1c2VkIHdpdGggdGhlIGdlcnVuZCBmb3JtOiAiUkVD
T01NRU5ERUQNCj4gcmV0dXJuaW5nIi4NCj4gDQo+IFNlY3Rpb24gNiwgcGFyYWdyYXBoIDUsIG5p
dDoNCj4gPiBTIHNlcnZlciB3aGVuIHRoZSBDb250ZW50LUZvcm1hdCBpcyB1c2VkIGJ1dCB0aGUg
cmVxdWVzdCBpcyBub3QNCj4gZm9ybWF0dGVkIGFzDQo+ID4gICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgXl5eXg0KPiBVc2UgYSBjb21tYSBiZWZvcmUgJ2J1dCcgaWYgaXQgY29u
bmVjdHMgdHdvIGluZGVwZW5kZW50IGNsYXVzZXMNCj4gKHVubGVzcyB0aGV5IGFyZSBjbG9zZWx5
IGNvbm5lY3RlZCBhbmQgc2hvcnQpLg0KPiANCj4gU2VjdGlvbiA2LCBwYXJhZ3JhcGggNSwgbml0
Og0KPiA+ICcgVVJJIElBTkEgaXMgcmVxdWVzdGVkIHRvIHVwZGF0ZSB0aGUgdGhlICdkb3RzJyB3
ZWxsLWtub3duIFVSSQ0KPiAoVGFibGUgNikgZW4NCj4gPiAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgXl5eXl5eXg0KPiBQb3NzaWJsZSB0eXBvOiB5b3UgcmVwZWF0ZWQgYSB3b3Jk
DQo+IA0KPiBPYnNvbGV0ZSByZWZlcmVuY2UgdG8gUkZDNTI0Niwgb2Jzb2xldGVkIGJ5IFJGQzg0
NDYuDQo+IA0KPiBEb2N1bWVudCByZWZlcmVuY2VzIGRyYWZ0LWlldGYtZG90cy1tdWx0aWhvbWlu
Zy0wNSwgYnV0IC0wNiBpcyB0aGUNCj4gbGF0ZXN0IGF2YWlsYWJsZSByZXZpc2lvbi4NCj4gDQo+
IERvY3VtZW50IHJlZmVyZW5jZXMgZHJhZnQtaWV0Zi1kb3RzLXRlbGVtZXRyeS0xNSwgYnV0IC0x
NiBpcyB0aGUNCj4gbGF0ZXN0IGF2YWlsYWJsZSByZXZpc2lvbi4NCj4gDQo+IERvY3VtZW50IHJl
ZmVyZW5jZXMgZHJhZnQtaWV0Zi1kb3RzLXVzZS1jYXNlcywgYnV0IHRoYXQgaGFzIGJlZW4NCj4g
cHVibGlzaGVkIGFzIFJGQzg5MDMuDQo+IA0KPiBUaGVzZSBVUkxzIGluIHRoZSBkb2N1bWVudCBj
YW4gcHJvYmFibHkgYmUgY29udmVydGVkIHRvIEhUVFBTOg0KPiAgKiBodHRwOi8vd3d3LmlhbmEu
b3JnL2Fzc2lnbm1lbnRzL2Nib3ItdGFncy9jYm9yLXRhZ3MueGh0bWwNCj4gICogaHR0cDovL3d3
dy5pYW5hLm9yZy9hc3NpZ25tZW50cy9tZWRpYS10eXBlcw0KPiAgKiBodHRwOi8vd3d3LmlhbmEu
b3JnL2Fzc2lnbm1lbnRzL2NvcmUtcGFyYW1ldGVycy9jb3JlLQ0KPiBwYXJhbWV0ZXJzLnhodG1s
I2NvbnRlbnQtZm9ybWF0cw0KPiAgKiBodHRwOi8vd3d3LmlhbmEub3JnL2Fzc2lnbm1lbnRzL3By
b3RvY29sLW51bWJlcnMNCj4gDQo+IA0KDQoKX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBzZXMgcGll
Y2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZpZGVudGll
bGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRpZmZ1c2Vz
LCBleHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2ZXogcmVj
dSBjZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdleHBlZGl0
ZXVyIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExlcyBtZXNz
YWdlcyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24sCk9yYW5n
ZSBkZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUgYWx0ZXJl
LCBkZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRzIGF0dGFj
aG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9ybWF0aW9u
IHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBkaXN0cmli
dXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3UgaGF2ZSBy
ZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgYW5k
IGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxzIG1heSBi
ZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBoYXZlIGJl
ZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=


From nobody Mon May 31 06:18:22 2021
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 56A563A17E4; Mon, 31 May 2021 06:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KHkdHCVCqA3e; Mon, 31 May 2021 06:18:13 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 866A93A17E9; Mon, 31 May 2021 06:18:12 -0700 (PDT)
Received: from opfednr03.francetelecom.fr (unknown [xx.xx.xx.67]) by opfednr26.francetelecom.fr (ESMTP service) with ESMTP id 4FtwpB2LD4z11Zb; Mon, 31 May 2021 15:18:10 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1622467090; bh=/fAwckE4D/ql8+64dh3k/h68vxFsjPNYCmOWn9O4Qng=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=pqjQMMc7fUbrmeq/2rU7fVcpWaf/fZNmSvkEuNf6cGppyrnTruh4mxjkq9tP5IP1a UCw3G/ax+BdjCDHawMP/O7K2mOCIhEugMR8dxeNvBs5d3o5lMmu8vJvSiJa6atxILu i0MXJtCsiWgAXmEYlps67xmpjRjDKsy6SBa5WwJugK/EKRanN4n24kuGO7kc4YYgLP fSJT7TGAZLDWpvshQM4bzxvRY02jF+/W15xQQteudq47Ui76/ubGAigj7cAeao5dFj ng1T8AoQwkcWoLbcpkyVBulnEly+9tBZ7eV8ChI14JcUIdo6tBh7bK4TMyNp7/rlPD 35uGZdAyZULTQ==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.20]) by opfednr03.francetelecom.fr (ESMTP service) with ESMTP id 4FtwpB1TszzDq7V; Mon, 31 May 2021 15:18:10 +0200 (CEST)
From: <mohamed.boucadair@orange.com>
To: =?utf-8?B?w4lyaWMgVnluY2tl?= <evyncke@cisco.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-dots-rfc8782-bis@ietf.org" <draft-ietf-dots-rfc8782-bis@ietf.org>, "dots-chairs@ietf.org" <dots-chairs@ietf.org>, "dots@ietf.org" <dots@ietf.org>, "valery@smyslov.net" <valery@smyslov.net>
Thread-Topic: =?utf-8?B?w4lyaWMgVnluY2tlJ3MgTm8gT2JqZWN0aW9uIG9uIGRyYWZ0LWlldGYtZG90?= =?utf-8?Q?s-rfc8782-bis-07:_(with_COMMENT)?=
Thread-Index: AQHXVgKDZMUSoy5baU2RNHdzwcMNs6r9bQSg
Date: Mon, 31 May 2021 13:18:09 +0000
Message-ID: <5586_1622467090_60B4E212_5586_472_1_787AE7BB302AE849A7480A190F8B93303539504D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <162245467875.25457.5499708730835623241@ietfa.amsl.com>
In-Reply-To: <162245467875.25457.5499708730835623241@ietfa.amsl.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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/DW1DF8gEN-CkustHW2rV37ZR-zw>
Subject: Re: [Dots]  =?utf-8?q?=C3=89ric_Vyncke=27s_No_Objection_on_draft-ietf?= =?utf-8?q?-dots-rfc8782-bis-07=3A_=28with_COMMENT=29?=
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: Mon, 31 May 2021 13:18:18 -0000

SGkgw4lyaWMsIA0KDQpUaGFuayBmb3IgdGhlIGNvbW1lbnRzLiBNdWNoIGFwcHJlY2lhdGVkLiAN
Cg0KUGxlYXNlIHNlZSBpbmxpbmUuDQoNCkNoZWVycywNCk1lZA0KDQo+IC0tLS0tTWVzc2FnZSBk
J29yaWdpbmUtLS0tLQ0KPiBEZcKgOiDDiXJpYyBWeW5ja2UgdmlhIERhdGF0cmFja2VyIFttYWls
dG86bm9yZXBseUBpZXRmLm9yZ10NCj4gRW52b3nDqcKgOiBsdW5kaSAzMSBtYWkgMjAyMSAxMTo1
MQ0KPiDDgMKgOiBUaGUgSUVTRyA8aWVzZ0BpZXRmLm9yZz4NCj4gQ2PCoDogZHJhZnQtaWV0Zi1k
b3RzLXJmYzg3ODItYmlzQGlldGYub3JnOyBkb3RzLWNoYWlyc0BpZXRmLm9yZzsNCj4gZG90c0Bp
ZXRmLm9yZzsgdmFsZXJ5QHNteXNsb3YubmV0OyB2YWxlcnlAc215c2xvdi5uZXQNCj4gT2JqZXTC
oDogw4lyaWMgVnluY2tlJ3MgTm8gT2JqZWN0aW9uIG9uIGRyYWZ0LWlldGYtZG90cy1yZmM4Nzgy
LWJpcy0wNzoNCj4gKHdpdGggQ09NTUVOVCkNCj4gDQo+IMOJcmljIFZ5bmNrZSBoYXMgZW50ZXJl
ZCB0aGUgZm9sbG93aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCj4gZHJhZnQtaWV0Zi1kb3RzLXJm
Yzg3ODItYmlzLTA3OiBObyBPYmplY3Rpb24NCj4gDQo+IFdoZW4gcmVzcG9uZGluZywgcGxlYXNl
IGtlZXAgdGhlIHN1YmplY3QgbGluZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbA0KPiBlbWFpbCBh
ZGRyZXNzZXMgaW5jbHVkZWQgaW4gdGhlIFRvIGFuZCBDQyBsaW5lcy4gKEZlZWwgZnJlZSB0byBj
dXQNCj4gdGhpcyBpbnRyb2R1Y3RvcnkgcGFyYWdyYXBoLCBob3dldmVyLikNCj4gDQo+IA0KPiBQ
bGVhc2UgcmVmZXIgdG8gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaWVzZy9zdGF0ZW1lbnQvZGlzY3Vz
cy0NCj4gY3JpdGVyaWEuaHRtbA0KPiBmb3IgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCBESVNDVVNT
IGFuZCBDT01NRU5UIHBvc2l0aW9ucy4NCj4gDQo+IA0KPiBUaGUgZG9jdW1lbnQsIGFsb25nIHdp
dGggb3RoZXIgYmFsbG90IHBvc2l0aW9ucywgY2FuIGJlIGZvdW5kIGhlcmU6DQo+IGh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtZG90cy1yZmM4NzgyLWJpcy8NCj4g
DQo+IA0KPiANCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo+IC0NCj4gQ09NTUVOVDoNCj4gLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
DQo+IC0NCj4gDQo+IFRoYW5rIHlvdSBmb3IgdGhlIHdvcmsgcHV0IGludG8gdGhpcyBkb2N1bWVu
dC4NCj4gDQo+IEFzIEkgYWxyZWFkeSByZXZpZXdlZCB0aGUgb3JpZ2luYWwgUkZDIDg3ODIsIEkg
aGF2ZSBvbmx5IHJldmlldyB0aGUNCj4gZGlmZnMgKHRoYW5rcyB0byBSRkNESUZGISkuDQo+IA0K
PiBQbGVhc2UgZmluZCBiZWxvdyBzb21lIG5vbi1ibG9ja2luZyBDT01NRU5UIHBvaW50cyAoYnV0
IHJlcGxpZXMgd291bGQNCj4gYmUgYXBwcmVjaWF0ZWQpLg0KPiANCj4gSSBob3BlIHRoYXQgdGhp
cyBoZWxwcyB0byBpbXByb3ZlIHRoZSBkb2N1bWVudCwNCj4gDQo+IFJlZ2FyZHMsDQo+IA0KPiAt
w6lyaWMNCj4gDQo+ID09IENPTU1FTlRTID09DQo+IA0KPiAtLSBTZWN0aW9uIDMuMSAtLQ0KPiBJ
biAidGhhdCBmb2xsb3cgdGhlIHByZXNlbnQgc3BlY2lmaWNhdGlvbiIsIHRoZSB1c2Ugb2YgInBy
ZXNlbnQiIGlzDQo+IGFtYmlndW91czoNCj4gZG9lcyBpdCBtZWFuIGN1cnJlbnQgaW1wbGVtZW50
YXRpb25zIG9mIFJGQyA4NzgyPyBvciB0aGlzDQo+IHNwZWNpZmljYXRpb24gKGkuZS4sIHRoaXMg
SS1EKSA/DQoNCltNZWRdIFRoZSBmdWxsIHRleHQgaXM6IA0KDQogICBGb3IgYm90aCBsZWdhY3kg
YW5kIGltcGxlbWVudGF0aW9ucyB0aGF0IGZvbGxvdyB0aGUgcHJlc2VudA0KICAgc3BlY2lmaWNh
dGlvbg0KDQoicHJlc2VudCBzcGVjIiBtZWFucyAidGhpcyBkb2N1bWVudCIgd2hpbGUgImxlZ2Fj
eSIgcmVmZXJzIHRvIDg3ODIuIA0KDQpXZSBjYW4gY2hhbmdlIGl0IHRvIHRoZSBmb2xsb3dpbmcg
aWYgdGhpcyB3b3VsZCBoZWxwOiANCg0KICAgRm9yIGJvdGggbGVnYWN5IFtSRkM4NDgyXSBhbmQg
aW1wbGVtZW50YXRpb25zIHRoYXQgZm9sbG93IHRoZSBwcmVzZW50DQogICBzcGVjaWZpY2F0aW9u
DQoNCj4gDQo+IC0tIFNlY3Rpb24gNC40LjEuMyAtLQ0KPiBJIHdvbmRlciB3aHkgYSBwb3J0IG51
bWJlciBjYW4gYmUgdXNlZCBpZiB0aGUgY2FzZSBvZiBjb21tb24vc2hhcmVkDQo+IFVSSSA/IElu
ICJBIGxpc3Qgb2YgcG9ydCBudW1iZXJzIG1heSBhbHNvIGJlIGluY2x1ZGVkIGlmIHRoZXJlIGlz
IGENCj4gY29tbW9uIElQIGFkZHJlc3MsIElQIHByZWZpeCwgRlFETiwgVVJJLCBvciBhbGlhcy4i
DQoNCltNZWRdIFRoaXMgY2FuIGJlIHJldHVybmVkLCBmb3IgZXhhbXBsZSwgd2hlbiBhIG5ldyBy
ZXF1ZXN0IHNwZWNpZnlpbmcgYW4gSVAgYWRkcmVzcyArIHBvcnQgb3ZlcmxhcHMgd2l0aCBhbiBl
eGlzdGluZyByZXF1ZXN0IHdpdGggYSB0YXJnZXQtdXJpLiANCg0KPiANCj4gLS0gU2VjdGlvbiA1
LjMgLS0NCj4gSSBhbSBub3QgYSBZQU5HIG1vZHVsZSBleHBlcnQgYnV0IHVzaW5nIGEgdW5pb24g
Zm9yICdsaWZldGltZScganVzdA0KPiB0byBhbGxvdyBhDQo+IC0xIHZhbHVlIHRvIHNpZ25hbCBp
bmZpbml0eSBsb29rcyBhIGxpdHRsZSB3ZWlyZCB0byBtZS4gQ291bGQgdGhlDQo+IHZhbHVlIDB4
N2ZmZmZmZmYgYmUgdXNlZCBmb3IgJ2luZmluaXR5JyBhbmQga2VlcGluZyBhIHVpbnQzMiA/DQoN
CltNZWRdIFdlIGNvbnNpZGVyZWQgc2V2ZXJhbCBvcHRpb25zIGF0IHRoYXQgdGltZTogMCwgbGFy
Z2UgbnVtYmVyLCBvciAtMS4gV2Ugd2VudCBmb3IgLTEgYXMgMCBjYW4gbWVhbiAnZW5kcyBub3cn
IHdoaWxlICdsYXJnZSBudW1iZXInIGlzIHN0aWxsIGZpbml0ZSBmb3IgInB1cmlzdHMiLiAgDQoN
ClRoZSB1c2Ugb2YgInVuaW9uIiBpcyBPSyB0byBtYWtlIG1hdGNoIHRoZSB5YW5nIHNwZWMgd2l0
aCB0aGUgaW50ZW5kZWQgdXNhZ2U6IGEgdmFsaWQgdmFsdWUgY2FuIGJlICItMSIgb3IgYW55IHVp
bnQzMi4NCg0KUGxlYXNlIG5vdGUgdGhhdCB1c2luZyBhIGxhcmdlIG51bWJlciB3b3VsZCBpbXBh
Y3QgdGhlIGZvbGxvd2luZyBDQk9SIG1hcHBpbmcgZW50cnkuLi4NCg0KICAgfCBsaWZldGltZSAg
ICAgICAgICAgIHwgdW5pb24gICAgICAgIHwgMTQgICB8IDAgdW5zaWduZWQgIHwgTnVtYmVyIHwN
CiAgIHwgICAgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICB8ICAgICAgKy0tLS0tLS0t
LS0tLS0rLS0tLS0tLS0rDQogICB8ICAgICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAg
fCAgICAgIHwgMSBuZWdhdGl2ZSAgfCBOdW1iZXIgfA0KDQouLi4gd2hpY2ggd291bGQgdGhlbiBi
cmVhayB0aGUgY29uc3RyYWludCB3ZSBzZXQgZm9yIHRoZSBiaXM6DQoNCiAgIlRoZXNlDQogICBt
b2RpZmljYXRpb25zIGFyZSBtYWRlIHdpdGggdGhlIGNvbnN0cmFpbnQgdG8gYXZvaWQgY2hhbmdl
cyB0byB0aGUNCiAgIG1hcHBpbmcgdGFibGUgZGVmaW5lZCBpbiBUYWJsZSA1IG9mIFtSRkM4Nzgy
XSAoc2VlIGFsc28gU2VjdGlvbiA2KS4iDQoNCj4gDQo+IEluIHByb2JpbmctcmF0ZS5jdXJyZW50
LXZhbHVlLCB0aGVyZSBpcyBhIGRlZmF1bHQgdmFsdWUgb2YgNQ0KPiBieXRlL3NlY29uZC4gSXMg
aXQgdXNlZnVsIHRvIHJlY29tbWVuZCBzdWNoIGEgZGVmYXVsdCB2YWx1ZSA/DQoNCltNZWRdIFRo
aXMgaXMgdG8gYWxpZ24gdGhlIFlBTkcgbW9kdWxlIHdpdGggdGhpcyBwYXJ0IGluIFNlY3Rpb24g
NC41LjI6DQoNCiAgICAgIHwgIEFic2VudCBhbnkgZXhwbGljaXQgY29uZmlndXJhdGlvbiBvciBp
bmFiaWxpdHkgdG8NCiAgICAgIHwgIGR5bmFtaWNhbGx5IGFkanVzdCAncHJvYmluZy1yYXRlJyB2
YWx1ZXMgKFNlY3Rpb24gNC44LjEgb2YNCiAgICAgIHwgIFtSRkM3MjUyXSksIERPVFMgYWdlbnRz
IHVzZSA1IGJ5dGVzL3NlY29uZCBhcyBhIGRlZmF1bHQNCiAgICAgIHwgICdwcm9iaW5nLXJhdGUn
IHZhbHVlLiANCg0KPiANCj4gTW9yZSBnZW5lcmljYWxseSwgSSB3b25kZXIgd2hldGhlciBtZWFz
dXJpbmcgaW4gb2N0ZXRzL3NlY29uZCBpcyBtb3JlDQo+IHN1aXRhYmxlIHRoYW4gaW4gYml0cy9z
ZWNvbmQuDQoNCltNZWRdIEkgdGhpbmsgeW91IGFyZSByZWZlcnJpbmcgdG8gImJwcy1kcm9wcGVk
IiBhdHRyaWJ1dGUuIEl0IGlzIGFjdHVhbGx5IGluIGJ5dGVzIHBlciBzZWNvbmQgYXMgc3RhdGVt
ZW50IGluIFNlY3Rpb24gNC40LjI6IA0KDQogICBicHMtZHJvcHBlZDogIFRoZSBhdmVyYWdlIG51
bWJlciBvZiBkcm9wcGVkIGJ5dGVzIHBlciBzZWNvbmQgZm9yIHRoZQ0KICAgICAgbWl0aWdhdGlv
biByZXF1ZXN0IHNpbmNlIHRoZSBhdHRhY2sgbWl0aWdhdGlvbiB3YXMgdHJpZ2dlcmVkLg0KDQpI
b3dldmVyIHdoZW4gY2hlY2tpbmcgdGhlIFlBTkcgZGVzY3JpcHRpb24sIEkgZ3Vlc3MgdGhhdCB5
b3Ugd2VyZSBjb25mdXNlZCB3aXRoIHRoZSBmb2xsb3dpbmc6ICANCg0KICJUaGUgYXZlcmFnZSBu
dW1iZXIgb2YgZHJvcHBlZCBiaXRzIHBlciBzZWNvbmQgZm9yDQogICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIF5eXl4NCiAgdGhlIG1pdGlnYXRpb24gcmVxdWVzdCBzaW5jZSB0aGUgYXR0
YWNrDQogIG1pdGlnYXRpb24gd2FzIHRyaWdnZXJlZC4gIFRoaXMgc2hvdWxkIGJlIG92ZXINCiAg
Zml2ZS1taW51dGUgaW50ZXJ2YWxzICh0aGF0IGlzLCBtZWFzdXJpbmcgYnl0ZXMNCiAgICAgICAg
ICAgICAgICAgICAgICAgICBeXl5eXl5eXl5eXl5eXl5eXl5eXl5eXl4NCiAgaW50byBmaXZlLW1p
bnV0ZSBidWNrZXRzIGFuZCB0aGVuIGF2ZXJhZ2luZyB0aGVzZQ0KICBidWNrZXRzIG92ZXIgdGhl
IHRpbWUgc2luY2UgdGhlIG1pdGlnYXRpb24gd2FzDQogIHRyaWdnZXJlZCkuIjsNCg0KVGhlIHRl
eHQgaXMgdXBkYXRlZCBhcyBmb2xsb3dzOiANCg0KTkVXOg0KICJUaGUgYXZlcmFnZSBudW1iZXIg
b2YgZHJvcHBlZCBieXRlcyBwZXIgc2Vjb25kIGZvcg0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICBeXl5eXg0KICB0aGUgbWl0aWdhdGlvbiByZXF1ZXN0IHNpbmNlIHRoZSBhdHRhY2sN
CiAgbWl0aWdhdGlvbiB3YXMgdHJpZ2dlcmVkLiAgVGhpcyBzaG91bGQgYmUgb3Zlcg0KICBmaXZl
LW1pbnV0ZSBpbnRlcnZhbHMgKHRoYXQgaXMsIG1lYXN1cmluZyBieXRlcw0KICBpbnRvIGZpdmUt
bWludXRlIGJ1Y2tldHMgYW5kIHRoZW4gYXZlcmFnaW5nIHRoZXNlDQogIGJ1Y2tldHMgb3ZlciB0
aGUgdGltZSBzaW5jZSB0aGUgbWl0aWdhdGlvbiB3YXMNCiAgdHJpZ2dlcmVkKS4iOw0KDQpUaGFu
ayB5b3UgZm9yIGNhdGNoaW5nIHRoaXMuDQoNCj4gDQo+IFRoZSAnYWx0LXNlcnZlcicgaXMgbm93
IGJldHRlciB0eXBlZCBhcyAnaW5ldDpkb21haW4tbmFtZScNCg0KW01lZF0gVGhpcyBpcyB0byBi
ZXR0ZXIgcmVmbGVjdCB0aGUgZGVzY3JpcHRpb24gaW4gdGhlIGNvcmUgdGV4dDogDQoNCiAgIGFs
dC1zZXJ2ZXI6ICBGUUROIG9mIGFuIGFsdGVybmF0ZSBET1RTIHNlcnZlci4NCiAgICAgICAgICAg
ICAgICBeXl5eDQoNCiBidXQgSSBub3cNCj4gd29uZGVyIHdoZXRoZXIgcmVseWluZyBzb2xlbHkg
b24gRE5TIGluIGEgY2FzZSBvZiBEb1MgaXMgc2Vuc2libGUuDQoNCltNZWRdIFRoZSBuYW1lIGNh
biBiZSBzdXBwbGllZCB0byBhbnkgYXZhaWxhYmxlIG5hbWUgcmVzb2x1dGlvbiBsaWJyYXJ5LiBG
b3IgdGhlIHBhcnRpY3VsYXIgY2FzZSBvZiBETlMsIHdlIHNheSB0aGUgZm9sbG93aW5nOg0KDQog
ICBEdXJpbmcgYSBERG9TIGF0dGFjaywgdGhlIEROUyBzZXJ2ZXIgbWF5IGJlIHRoZSB0YXJnZXQg
b2YgYW5vdGhlcg0KICAgRERvUyBhdHRhY2ssIHRoZSBhbHRlcm5hdGUgRE9UUyBzZXJ2ZXIncyBJ
UCBhZGRyZXNzZXMgY29udmV5ZWQgaW4gdGhlDQogICA1LjAzIHJlc3BvbnNlIGhlbHAgdGhlIERP
VFMgY2xpZW50IHNraXAgdGhlIEROUyBsb29rdXAgb2YgdGhlDQogICBhbHRlcm5hdGUgRE9UUyBz
ZXJ2ZXIsIGF0IHRoZSBjb3N0IG9mIHRydXN0aW5nIHRoZSBmaXJzdCBET1RTIHNlcnZlcg0KICAg
dG8gcHJvdmlkZSBhY2N1cmF0ZSBpbmZvcm1hdGlvbi4gDQoNCkFzIGEgc2lkZSBub3RlLCB0aGUg
bmFtZSB3aWxsIGFsc28gYmUgdXNlZCBmb3IgYXV0aGVudGljYXRpb24gcHVycG9zZXMuIA0KCl9f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX18KCkNlIG1lc3NhZ2UgZXQgc2VzIHBpZWNlcyBqb2ludGVzIHBldXZlbnQgY29udGVuaXIg
ZGVzIGluZm9ybWF0aW9ucyBjb25maWRlbnRpZWxsZXMgb3UgcHJpdmlsZWdpZWVzIGV0IG5lIGRv
aXZlbnQgZG9uYwpwYXMgZXRyZSBkaWZmdXNlcywgZXhwbG9pdGVzIG91IGNvcGllcyBzYW5zIGF1
dG9yaXNhdGlvbi4gU2kgdm91cyBhdmV6IHJlY3UgY2UgbWVzc2FnZSBwYXIgZXJyZXVyLCB2ZXVp
bGxleiBsZSBzaWduYWxlcgphIGwnZXhwZWRpdGV1ciBldCBsZSBkZXRydWlyZSBhaW5zaSBxdWUg
bGVzIHBpZWNlcyBqb2ludGVzLiBMZXMgbWVzc2FnZXMgZWxlY3Ryb25pcXVlcyBldGFudCBzdXNj
ZXB0aWJsZXMgZCdhbHRlcmF0aW9uLApPcmFuZ2UgZGVjbGluZSB0b3V0ZSByZXNwb25zYWJpbGl0
ZSBzaSBjZSBtZXNzYWdlIGEgZXRlIGFsdGVyZSwgZGVmb3JtZSBvdSBmYWxzaWZpZS4gTWVyY2ku
CgpUaGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cyBtYXkgY29udGFpbiBjb25maWRlbnRp
YWwgb3IgcHJpdmlsZWdlZCBpbmZvcm1hdGlvbiB0aGF0IG1heSBiZSBwcm90ZWN0ZWQgYnkgbGF3
Owp0aGV5IHNob3VsZCBub3QgYmUgZGlzdHJpYnV0ZWQsIHVzZWQgb3IgY29waWVkIHdpdGhvdXQg
YXV0aG9yaXNhdGlvbi4KSWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhpcyBlbWFpbCBpbiBlcnJvciwg
cGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGFuZCBkZWxldGUgdGhpcyBtZXNzYWdlIGFuZCBpdHMg
YXR0YWNobWVudHMuCkFzIGVtYWlscyBtYXkgYmUgYWx0ZXJlZCwgT3JhbmdlIGlzIG5vdCBsaWFi
bGUgZm9yIG1lc3NhZ2VzIHRoYXQgaGF2ZSBiZWVuIG1vZGlmaWVkLCBjaGFuZ2VkIG9yIGZhbHNp
ZmllZC4KVGhhbmsgeW91LgoK

