
From nobody Fri Apr  1 18:08:31 2022
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 1E9C93A1C15; Fri,  1 Apr 2022 18:08:29 -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.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: dots@ietf.org
Message-ID: <164886170906.20199.11185267345443734787@ietfa.amsl.com>
Date: Fri, 01 Apr 2022 18:08:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/fvFlhKc5KaWybthoVYrgtpm1lSw>
Subject: [Dots] I-D Action: draft-ietf-dots-telemetry-use-cases-10.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: Sat, 02 Apr 2022 01:08:30 -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           : Use Cases for DDoS Open Threat Signaling (DOTS) Telemetry
        Authors         : Yuhei Hayashi
                          Meiling Chen
                          Li Su
	Filename        : draft-ietf-dots-telemetry-use-cases-10.txt
	Pages           : 28
	Date            : 2022-04-01

Abstract:
   DDoS Open Threat Signaling (DOTS) Telemetry enriches the base DOTS
   protocols to assist the mitigator in using efficient DDoS attack
   mitigation techniques in a network.  This document presents sample
   use cases for DOTS Telemetry.  It discusses in particular what
   components are deployed in the network, how they cooperate, and what
   information is exchanged to effectively use these techniques.


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

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

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


Internet-Drafts are also available by rsync at rsync.ietf.org::internet-drafts



From nobody Fri Apr  1 18:13:44 2022
Return-Path: <yuuhei.hayashi@gmail.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 19F593A1C19; Fri,  1 Apr 2022 18:13:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.108
X-Spam-Level: 
X-Spam-Status: No, score=-7.108 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, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 HHslYdPnYRxo; Fri,  1 Apr 2022 18:13:37 -0700 (PDT)
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com [IPv6:2a00:1450:4864:20::530]) (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 0F3B23A1C1C; Fri,  1 Apr 2022 18:12:35 -0700 (PDT)
Received: by mail-ed1-x530.google.com with SMTP id c62so4879182edf.5; Fri, 01 Apr 2022 18:12:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=KhgGHHMiS6VP3LJBelawiLAuPqFZdIGNmJ7CV5t/iw0=; b=M2ybZ7zYs8yQ/lo2vrJMffFBcP1wgXjNBmcSV5k+e18My5nSu3Dg1SX8rT0ACPcW1/ nPvyuthiNZagrPETlVfahnvN/jnp4pJngPOIl3FKXRXxK1G5cs5TBVe3SvoO1VGh3FGW UIrHbwfJ2p24IMdGGKm2qeloy7+HcuiLAn7TNubM4lmx838e1jT+gtlikiwPvqZd8PCu YtbdppnZ2FCJVxGys4Uw4fzRmci0ETQvQvJm+QLwTwTVk4Qf6WeWXc3ZS78SKfR8XPe8 qX3DPvn7YEdb4P9lWlk3hzMRdpWX41TuCD5g51r7Uhxpq/DOFgMsCv2aEH/Z1PFUpiH2 2+3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=KhgGHHMiS6VP3LJBelawiLAuPqFZdIGNmJ7CV5t/iw0=; b=snyk/S3hQvU66D2WBfWrwCqTAYy+IHQ/tD5cP5n9LpiqEt7oYVirYpG63awrVLyxO6 tX6SPLEDowDuLIWNS/eIkVWWKSaG9xw1qdKLKOfC7LAeZNAXOU7T7iKYOl/d/rVawaIH +/+9Z/onzr4wwBaDVfyTMjvdFshyfjX47UbKhr76uQx11jGQoVend9G/5gqMSd9DQs7m 5+gnksDEufbdk0zywd0iFY1wstV9pdqbZU7jQk3H3jQg/LO0j76HMftCn9N/AfU/53Ut 8RJaaf7RCSo8pzfXohrrgj7LiHDZV5yaYS73hZp+2bpimoO8I0EjEk/ybVs3FynoIZsb okrg==
X-Gm-Message-State: AOAM533z7687M/frrLMPTovfDbE0ALV/eQi8DPSqoi4C0DRHnvnh49ed +I7DVzFJayN1aKXKPYgzQ94fGj14J20FMlXV6dpwNxFmlbw=
X-Google-Smtp-Source: ABdhPJz1qolp7rwvHB7FBJQiIV0qIp1cDOdbvp0jlbEzI7fY9N/bwpiHbkjsSfDKvSXlxmqlfyfSsvrca91s95psns0=
X-Received: by 2002:a50:bb08:0:b0:41b:6bb6:3be6 with SMTP id y8-20020a50bb08000000b0041b6bb63be6mr14708701ede.106.1648861953028; Fri, 01 Apr 2022 18:12:33 -0700 (PDT)
MIME-Version: 1.0
References: <19f101d84506$df98e810$9ecab830$@smyslov.net>
In-Reply-To: <19f101d84506$df98e810$9ecab830$@smyslov.net>
From: H Y <yuuhei.hayashi@gmail.com>
Date: Sat, 2 Apr 2022 10:12:24 +0900
Message-ID: <CAA8pjUN_aq7zJGxb9ErWCpVwpBgxa-E6UOuD9rWSf5wi9HSD5A@mail.gmail.com>
To: Valery Smyslov <valery@smyslov.net>
Cc: draft-ietf-dots-telemetry-use-cases@ietf.org, dots <dots@ietf.org>,  dots-chairs <dots-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/DpS81o0SESjW4Qv3fI7LrUAgc6I>
Subject: Re: [Dots] Shepherd review of draft-ietf-dots-telemetry-use-cases
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: Sat, 02 Apr 2022 01:13:43 -0000

Hi Valery,

Thank you for your careful review.

We fixed the nits and posted it as draft-ietf-dots-telemetry-use-cases-10.

>4. Section 3.1.1.
>   After that, the orchestrator
>   orders the forwarding nodes to redirect as much of the top talker's tra=
ffic...
> Shouldn't it be top-talkers' ?
>7. Section 3.1.5.
> s/The forwarding nodes  send traffic statistics ... to the orchestrator t=
he using "vendor-id" and "attack-id" telemetry attributes/
> The forwarding nodes  send traffic statistics ... to the orchestrator by =
using "vendor-id" and "attack-id" telemetry attributes

We found the same nits in draft-ietf-dots-telemetry-use-cases-9, so we
fixed them all.

Thanks,
Yuhei

2022=E5=B9=B43=E6=9C=8831=E6=97=A5(=E6=9C=A8) 22:54 Valery Smyslov <valery@=
smyslov.net>:
>
> Hi,
>
> I reviewed the document and found some nits (mostly grammar and typos).
>
> 1. Abstract.
>
> The expansion of DOTS is "DDoS Open Threat Signaling". In the abstract it=
 is expanded as "Denial-of-service Open Threat Signaling".
>
> 2. Figure 1, Figure 3, Figure 5, Figure 7, Figure 16, Figure 18.
>
> All contain the same typo:
>
> s/S is for DOTS client functionality/S is for DOTS server functionality
>
> 3. Section 3.1.1.
>
> IPFIX, BGP, SNMP aren't expanded on first use.
>
> 4. Section 3.1.1.
>
>    After that, the orchestrator
>    orders the forwarding nodes to redirect as much of the top talker's tr=
affic...
>
> Shouldn't it be top-talkers' ?
>
> 5. Figure 7.
>
> s/BGP Flow spec/BGP Flowspec
>
> 6. Section 3.1.5.
>
> s/It may also necessary/It may also be necessary
>
> 7. Section 3.1.5.
>
> s/The forwarding nodes  send traffic statistics ... to the orchestrator t=
he using "vendor-id" and "attack-id" telemetry attributes/
> The forwarding nodes  send traffic statistics ... to the orchestrator by =
using "vendor-id" and "attack-id" telemetry attributes
>
> 8. Section 3.2.
>
> s/Figure 15 provides ...  from the orchestrator to the network ./Figure 1=
5 provides ...  from the orchestrator to the network.
>
> 9. Section 3.2.
>
> s/Then, the DDoS mitigation systems reports the status of DDoS countermea=
sures to the orchestrator sending "attack-detail" telemetry
> attributes./
> Then, the DDoS mitigation systems reports the status of DDoS countermeasu=
res to the orchestrator by sending "attack-detail"
> telemetry attributes.
>
> 10. Section 3.2.
>
> s/After  that, the orchestrator integrates the reports ... and send it to=
 a network administrator .../
> After  that, the orchestrator integrates the reports ... and sends them t=
o a network administrator ...
>
> (two places)
>
> 11. Section 3.3.1.
>
>    On the other hand, DDoS detection based on the
>    DMSes is a more accurate method for detecting attack traffic better
>    than flow monitoring.
>
> I have trouble parsing this text. Probably:
>
>   On the other hand, DDoS detection based on the
>    DMSes is a more accurate method for detecting attack traffic
>    than flow monitoring.
>
> 12. Section 3.3.1.
>
> s/The aim of this use case is to increases flow collector's detection ...=
/The aim of this use case is to increase flow collector's
> detection ...
>
> 13. Section 3.3.1.
>
> s/statisticsto/statistics to
>
> 14. Section 4.
>
> s/a DDoS attacks/DDoS attacks
>
> Regards,
> Valery.
>


--=20
----------------------------------
Yuuhei HAYASHI
08065300884
yuuhei.hayashi@gmail.com
iehuuy_0220@docomo.ne.jp
----------------------------------


From nobody Mon Apr  4 00:26:50 2022
Return-Path: <valery@smyslov.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51BCE3A1F5F; Mon,  4 Apr 2022 00:26:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 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, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=smyslov.net
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 EEqyGpsvwaoV; Mon,  4 Apr 2022 00:26:23 -0700 (PDT)
Received: from direct.host-care.com (direct.host-care.com [198.136.54.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D033F3A1F61; Mon,  4 Apr 2022 00:26:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=smyslov.net ; s=default; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID :Date:Subject:In-Reply-To:References:Cc:To:From:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=Tm9onqDHgjh+K/CFGZQuV5e2naPg8RKgoatFE9aonrg=; b=vD88QIZms+FGjdPqyBu0r4IiJD w3npbCWIFAb2OdBWTFMKxL8JZWlZv2PQ37bkoNbRo4m6JBgGF2vPTHbhzUvxdPdQ+fZtAqK2vk66w 5969l2ppIQa1q7QBf2/Js+FA1sh7vu5cK8mdS9+DXEAdgGX59ybr8oaJudqmYeGgKAY08xcJBMtKp vBmlg5KLoEve1nmvU5bb6vLCBuXt3YNZhkdEa72vqqxiUlajTHGlaktfMLDdzYcZczj080Pd+GmMU A6W6Ot6e79bvo+ACiYLNTOlId4BAzjMwRT7zqYph/pByf0AmDMgml1/lO0108Z3Lx5j/3nWMQINvH j3D5Eolg==;
Received: from [93.188.44.204] (port=53664 helo=buildpc) by direct.host-care.com with esmtpsa (TLS1.2) tls TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.93) (envelope-from <valery@smyslov.net>) id 1nbH6R-0000Is-3J; Mon, 04 Apr 2022 03:26:19 -0400
From: "Valery Smyslov" <valery@smyslov.net>
To: "'H Y'" <yuuhei.hayashi@gmail.com>
Cc: <draft-ietf-dots-telemetry-use-cases@ietf.org>, "'dots'" <dots@ietf.org>,  "'dots-chairs'" <dots-chairs@ietf.org>
References: <19f101d84506$df98e810$9ecab830$@smyslov.net> <CAA8pjUN_aq7zJGxb9ErWCpVwpBgxa-E6UOuD9rWSf5wi9HSD5A@mail.gmail.com>
In-Reply-To: <CAA8pjUN_aq7zJGxb9ErWCpVwpBgxa-E6UOuD9rWSf5wi9HSD5A@mail.gmail.com>
Date: Mon, 4 Apr 2022 10:26:16 +0300
Message-ID: <1bec01d847f5$47685890$d63909b0$@smyslov.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJVlQNLgeASXdSWg3oo1N+vMEhaoAHfpd/4q9XCq6A=
Content-Language: ru
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - direct.host-care.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - smyslov.net
X-Get-Message-Sender-Via: direct.host-care.com: authenticated_id: valery@smyslov.net
X-Authenticated-Sender: direct.host-care.com: valery@smyslov.net
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/qjCJ7njjaIYMFxZUKNV34ZColV4>
Subject: Re: [Dots] Shepherd review of draft-ietf-dots-telemetry-use-cases
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, 04 Apr 2022 07:26:39 -0000

Hi Yuhei,

thank you for updating the document. I've been waiting for the=20
remaining author to provide IPR confirmation. Once I receive it,
I'll send the document to IESG.

Regards,
Valery.

> Hi Valery,
>=20
> Thank you for your careful review.
>=20
> We fixed the nits and posted it as =
draft-ietf-dots-telemetry-use-cases-10.
>=20
> >4. Section 3.1.1.
> >   After that, the orchestrator
> >   orders the forwarding nodes to redirect as much of the top =
talker's traffic...
> > Shouldn't it be top-talkers' ?
> >7. Section 3.1.5.
> > s/The forwarding nodes  send traffic statistics ... to the =
orchestrator the using "vendor-id" and "attack-id"
> telemetry attributes/
> > The forwarding nodes  send traffic statistics ... to the =
orchestrator by using "vendor-id" and "attack-id"
> telemetry attributes
>=20
> We found the same nits in draft-ietf-dots-telemetry-use-cases-9, so we
> fixed them all.
>=20
> Thanks,
> Yuhei
>=20
> 2022=E5=B9=B43=E6=9C=8831=E6=97=A5(=E6=9C=A8) 22:54 Valery Smyslov =
<valery@smyslov.net>:
> >
> > Hi,
> >
> > I reviewed the document and found some nits (mostly grammar and =
typos).
> >
> > 1. Abstract.
> >
> > The expansion of DOTS is "DDoS Open Threat Signaling". In the =
abstract it is expanded as "Denial-of-service
> Open Threat Signaling".
> >
> > 2. Figure 1, Figure 3, Figure 5, Figure 7, Figure 16, Figure 18.
> >
> > All contain the same typo:
> >
> > s/S is for DOTS client functionality/S is for DOTS server =
functionality
> >
> > 3. Section 3.1.1.
> >
> > IPFIX, BGP, SNMP aren't expanded on first use.
> >
> > 4. Section 3.1.1.
> >
> >    After that, the orchestrator
> >    orders the forwarding nodes to redirect as much of the top =
talker's traffic...
> >
> > Shouldn't it be top-talkers' ?
> >
> > 5. Figure 7.
> >
> > s/BGP Flow spec/BGP Flowspec
> >
> > 6. Section 3.1.5.
> >
> > s/It may also necessary/It may also be necessary
> >
> > 7. Section 3.1.5.
> >
> > s/The forwarding nodes  send traffic statistics ... to the =
orchestrator the using "vendor-id" and "attack-id"
> telemetry attributes/
> > The forwarding nodes  send traffic statistics ... to the =
orchestrator by using "vendor-id" and "attack-id"
> telemetry attributes
> >
> > 8. Section 3.2.
> >
> > s/Figure 15 provides ...  from the orchestrator to the network =
./Figure 15 provides ...  from the orchestrator
> to the network.
> >
> > 9. Section 3.2.
> >
> > s/Then, the DDoS mitigation systems reports the status of DDoS =
countermeasures to the orchestrator
> sending "attack-detail" telemetry
> > attributes./
> > Then, the DDoS mitigation systems reports the status of DDoS =
countermeasures to the orchestrator by
> sending "attack-detail"
> > telemetry attributes.
> >
> > 10. Section 3.2.
> >
> > s/After  that, the orchestrator integrates the reports ... and send =
it to a network administrator .../
> > After  that, the orchestrator integrates the reports ... and sends =
them to a network administrator ...
> >
> > (two places)
> >
> > 11. Section 3.3.1.
> >
> >    On the other hand, DDoS detection based on the
> >    DMSes is a more accurate method for detecting attack traffic =
better
> >    than flow monitoring.
> >
> > I have trouble parsing this text. Probably:
> >
> >   On the other hand, DDoS detection based on the
> >    DMSes is a more accurate method for detecting attack traffic
> >    than flow monitoring.
> >
> > 12. Section 3.3.1.
> >
> > s/The aim of this use case is to increases flow collector's =
detection .../The aim of this use case is to increase
> flow collector's
> > detection ...
> >
> > 13. Section 3.3.1.
> >
> > s/statisticsto/statistics to
> >
> > 14. Section 4.
> >
> > s/a DDoS attacks/DDoS attacks
> >
> > Regards,
> > Valery.
> >
>=20
>=20
> --
> ----------------------------------
> Yuuhei HAYASHI
> 08065300884
> yuuhei.hayashi@gmail.com
> iehuuy_0220@docomo.ne.jp
> ----------------------------------


From nobody Mon Apr  4 03:12:11 2022
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 B91A93A201D; Mon,  4 Apr 2022 03:12:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: =?utf-8?q?Mirja_K=C3=BChlewind_via_Datatracker?= <noreply@ietf.org>
To: <tsv-art@ietf.org>
Cc: dots@ietf.org, draft-ietf-dots-multihoming.all@ietf.org, last-call@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <164906712466.21199.15632970933973718487@ietfa.amsl.com>
Reply-To: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>
Date: Mon, 04 Apr 2022 03:12:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/cg52t1p7vsCazw4Ow55WBUig2u4>
Subject: [Dots] Tsvart last call review of draft-ietf-dots-multihoming-11
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, 04 Apr 2022 10:12:05 -0000

Reviewer: Mirja Kühlewind
Review result: Ready

This document has been reviewed as part of the transport area review team's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the document's
authors and WG to allow them to address any issues raised and also to the IETF
discussion list for information.

When done at the time of IETF Last Call, the authors should consider this
review as part of the last-call comments they receive. Please always CC
tsv-art@ietf.org if you reply to or forward this review.

The document is well-written and clear. This review did not identify any
transport issues or actually any issues at all.



From nobody Mon Apr  4 03:22:20 2022
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 97B6F3A2016; Mon,  4 Apr 2022 03:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level: 
X-Spam-Status: No, score=-2.107 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 Kz8v8tsTtryr; Mon,  4 Apr 2022 03:22:00 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (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 45D793A2011; Mon,  4 Apr 2022 03:21:57 -0700 (PDT)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr26.francetelecom.fr (ESMTP service) with ESMTPS id 4KX6Jg6T08z10Rl;  Mon,  4 Apr 2022 12:21:55 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1649067715; bh=QiICW+1VtPTjWZXUUYlWNSd6brPYSTOwSuILsX5aJ4o=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=NZPppoBX568lNVllwZcNC+kR0QtRexBrlj5GwmvfIIoqL7JTAYQ9c1FSN8Hg3XZYf AdMg+CU/iTbUv4aQwxzXSJ+6D+O1ry7eQE05C8V5NQb+7BjsJI5ZbymCbYm8e89NLW 3zsq/XlwMPWnYO2xcKGYMRLr6iiqvQd7yOGzLyv/C32JLZ3ZNC5GKzgooeJs/VkvRs A3Yibc+rTBNjvE++N2OMj7UR9NMeH87+YNpnxXDbWRZSSC5kVLDYrVzqrCgP9njCgP TLJLUxRjmObwOBEPGupJtyLfAs9dBuiyl8uM/zB47Qi9hNUFqdubLg+acbZ+uhAdpm LJ6PxZdpGX7lA==
From: <mohamed.boucadair@orange.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <ietf@kuehlewind.net>, "tsv-art@ietf.org" <tsv-art@ietf.org>
CC: "dots@ietf.org" <dots@ietf.org>, "draft-ietf-dots-multihoming.all@ietf.org" <draft-ietf-dots-multihoming.all@ietf.org>, "last-call@ietf.org" <last-call@ietf.org>
Thread-Topic: Tsvart last call review of draft-ietf-dots-multihoming-11
Thread-Index: AQHYSAx22+RDBePAqkmoPT6d3D/4AqzfiVGA
Content-Class: 
Date: Mon, 4 Apr 2022 10:21:55 +0000
Message-ID: <589_1649067715_624AC6C3_589_154_1_5949b222fd4445a6b6536f83e56f58f8@orange.com>
References: <164906712466.21199.15632970933973718487@ietfa.amsl.com>
In-Reply-To: <164906712466.21199.15632970933973718487@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-04-04T10:16:56Z;  MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=a10c77d5-a1d9-49d5-a8e2-9409b0dd2b3a; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.26.52]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/YLD3vrHx8mFrKHJ-KGbDQxPWq-w>
Subject: Re: [Dots] Tsvart last call review of draft-ietf-dots-multihoming-11
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, 04 Apr 2022 10:22:06 -0000

SGkgTWlyamEsIA0KDQpUaGFuayB5b3UgZm9yIHRoZSByZXZpZXcuIE11Y2ggYXBwcmVjaWF0ZWQs
IGFzIHVzdWFsLg0KDQpZb3VyIHJldmlldyB3aWxsIGJlIEFDS2VkIGluIHRoZSBuZXh0IGl0ZXJh
dGlvbiBhcyB5b3UgY2FuIHNlZSBpbjogaHR0cHM6Ly90aW55dXJsLmNvbS9kb3RzLW11bHRpaG9t
aW5nLWxhdGVzdC4NCg0KQ2hlZXJzLA0KTWVkDQoNCj4gLS0tLS1NZXNzYWdlIGQnb3JpZ2luZS0t
LS0tDQo+IERlwqA6IE1pcmphIEvDvGhsZXdpbmQgdmlhIERhdGF0cmFja2VyIDxub3JlcGx5QGll
dGYub3JnPg0KPiBFbnZvecOpwqA6IGx1bmRpIDQgYXZyaWwgMjAyMiAxMjoxMg0KPiDDgMKgOiB0
c3YtYXJ0QGlldGYub3JnDQo+IENjwqA6IGRvdHNAaWV0Zi5vcmc7IGRyYWZ0LWlldGYtZG90cy1t
dWx0aWhvbWluZy5hbGxAaWV0Zi5vcmc7IGxhc3QtDQo+IGNhbGxAaWV0Zi5vcmcNCj4gT2JqZXTC
oDogVHN2YXJ0IGxhc3QgY2FsbCByZXZpZXcgb2YgZHJhZnQtaWV0Zi1kb3RzLW11bHRpaG9taW5n
LTExDQo+IA0KPiBSZXZpZXdlcjogTWlyamEgS8O8aGxld2luZA0KPiBSZXZpZXcgcmVzdWx0OiBS
ZWFkeQ0KPiANCj4gVGhpcyBkb2N1bWVudCBoYXMgYmVlbiByZXZpZXdlZCBhcyBwYXJ0IG9mIHRo
ZSB0cmFuc3BvcnQgYXJlYSByZXZpZXcNCj4gdGVhbSdzIG9uZ29pbmcgZWZmb3J0IHRvIHJldmll
dyBrZXkgSUVURiBkb2N1bWVudHMuIFRoZXNlIGNvbW1lbnRzIHdlcmUNCj4gd3JpdHRlbiBwcmlt
YXJpbHkgZm9yIHRoZSB0cmFuc3BvcnQgYXJlYSBkaXJlY3RvcnMsIGJ1dCBhcmUgY29waWVkIHRv
DQo+IHRoZSBkb2N1bWVudCdzIGF1dGhvcnMgYW5kIFdHIHRvIGFsbG93IHRoZW0gdG8gYWRkcmVz
cyBhbnkgaXNzdWVzIHJhaXNlZA0KPiBhbmQgYWxzbyB0byB0aGUgSUVURiBkaXNjdXNzaW9uIGxp
c3QgZm9yIGluZm9ybWF0aW9uLg0KPiANCj4gV2hlbiBkb25lIGF0IHRoZSB0aW1lIG9mIElFVEYg
TGFzdCBDYWxsLCB0aGUgYXV0aG9ycyBzaG91bGQgY29uc2lkZXINCj4gdGhpcyByZXZpZXcgYXMg
cGFydCBvZiB0aGUgbGFzdC1jYWxsIGNvbW1lbnRzIHRoZXkgcmVjZWl2ZS4gUGxlYXNlDQo+IGFs
d2F5cyBDQyB0c3YtYXJ0QGlldGYub3JnIGlmIHlvdSByZXBseSB0byBvciBmb3J3YXJkIHRoaXMg
cmV2aWV3Lg0KPiANCj4gVGhlIGRvY3VtZW50IGlzIHdlbGwtd3JpdHRlbiBhbmQgY2xlYXIuIFRo
aXMgcmV2aWV3IGRpZCBub3QgaWRlbnRpZnkgYW55DQo+IHRyYW5zcG9ydCBpc3N1ZXMgb3IgYWN0
dWFsbHkgYW55IGlzc3VlcyBhdCBhbGwuDQo+IA0KDQoKX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwoKQ2UgbWVzc2FnZSBldCBz
ZXMgcGllY2VzIGpvaW50ZXMgcGV1dmVudCBjb250ZW5pciBkZXMgaW5mb3JtYXRpb25zIGNvbmZp
ZGVudGllbGxlcyBvdSBwcml2aWxlZ2llZXMgZXQgbmUgZG9pdmVudCBkb25jCnBhcyBldHJlIGRp
ZmZ1c2VzLCBleHBsb2l0ZXMgb3UgY29waWVzIHNhbnMgYXV0b3Jpc2F0aW9uLiBTaSB2b3VzIGF2
ZXogcmVjdSBjZSBtZXNzYWdlIHBhciBlcnJldXIsIHZldWlsbGV6IGxlIHNpZ25hbGVyCmEgbCdl
eHBlZGl0ZXVyIGV0IGxlIGRldHJ1aXJlIGFpbnNpIHF1ZSBsZXMgcGllY2VzIGpvaW50ZXMuIExl
cyBtZXNzYWdlcyBlbGVjdHJvbmlxdWVzIGV0YW50IHN1c2NlcHRpYmxlcyBkJ2FsdGVyYXRpb24s
Ck9yYW5nZSBkZWNsaW5lIHRvdXRlIHJlc3BvbnNhYmlsaXRlIHNpIGNlIG1lc3NhZ2UgYSBldGUg
YWx0ZXJlLCBkZWZvcm1lIG91IGZhbHNpZmllLiBNZXJjaS4KClRoaXMgbWVzc2FnZSBhbmQgaXRz
IGF0dGFjaG1lbnRzIG1heSBjb250YWluIGNvbmZpZGVudGlhbCBvciBwcml2aWxlZ2VkIGluZm9y
bWF0aW9uIHRoYXQgbWF5IGJlIHByb3RlY3RlZCBieSBsYXc7CnRoZXkgc2hvdWxkIG5vdCBiZSBk
aXN0cmlidXRlZCwgdXNlZCBvciBjb3BpZWQgd2l0aG91dCBhdXRob3Jpc2F0aW9uLgpJZiB5b3Ug
aGF2ZSByZWNlaXZlZCB0aGlzIGVtYWlsIGluIGVycm9yLCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5k
ZXIgYW5kIGRlbGV0ZSB0aGlzIG1lc3NhZ2UgYW5kIGl0cyBhdHRhY2htZW50cy4KQXMgZW1haWxz
IG1heSBiZSBhbHRlcmVkLCBPcmFuZ2UgaXMgbm90IGxpYWJsZSBmb3IgbWVzc2FnZXMgdGhhdCBo
YXZlIGJlZW4gbW9kaWZpZWQsIGNoYW5nZWQgb3IgZmFsc2lmaWVkLgpUaGFuayB5b3UuCgo=


From nobody Tue Apr  5 01:31:24 2022
Return-Path: <suli@chinamobile.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 52D713A2248; Tue,  5 Apr 2022 01:31:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 AynQGLxRqb36; Tue,  5 Apr 2022 01:31:17 -0700 (PDT)
Received: from cmccmta3.chinamobile.com (cmccmta3.chinamobile.com [221.176.66.81]) by ietfa.amsl.com (Postfix) with ESMTP id 7DE493A2236; Tue,  5 Apr 2022 01:31:15 -0700 (PDT)
X-RM-TagInfo: emlType=0                                       
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.3]) by rmmx-syy-dmz-app10-12010 (RichMail) with SMTP id 2eea624bfe51951-1170a; Tue, 05 Apr 2022 16:31:14 +0800 (CST)
X-RM-TRANSID: 2eea624bfe51951-1170a
X-RM-TagInfo: emlType=0                                       
X-RM-SPAM-FLAG: 00000000
Received: from cmccPC (unknown[120.245.130.140]) by rmsmtp-syy-appsvr02-12002 (RichMail) with SMTP id 2ee2624bfe50541-4e6e4; Tue, 05 Apr 2022 16:31:14 +0800 (CST)
X-RM-TRANSID: 2ee2624bfe50541-4e6e4
From: "SuLi" <suli@chinamobile.com>
To: "'Valery Smyslov'" <valery@smyslov.net>, "'H Y'" <yuuhei.hayashi@gmail.com>
Cc: <draft-ietf-dots-telemetry-use-cases@ietf.org>, "'dots'" <dots@ietf.org>,  "'dots-chairs'" <dots-chairs@ietf.org>
References: <19f101d84506$df98e810$9ecab830$@smyslov.net> <CAA8pjUN_aq7zJGxb9ErWCpVwpBgxa-E6UOuD9rWSf5wi9HSD5A@mail.gmail.com> <1bec01d847f5$47685890$d63909b0$@smyslov.net>
In-Reply-To: <1bec01d847f5$47685890$d63909b0$@smyslov.net>
Date: Tue, 5 Apr 2022 16:31:16 +0800
Message-ID: <002b01d848c7$858cd240$90a676c0$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQJVlQNLgeASXdSWg3oo1N+vMEhaoAHfpd/4q9XCq6CAAaTwgA==
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/azDxMrp7GQJSxDDPVFP-3Cb7Gdk>
Subject: [Dots] =?utf-8?b?562U5aSNOiBTaGVwaGVyZCByZXZpZXcgb2YgZHJhZnQt?= =?utf-8?q?ietf-dots-telemetry-use-cases?=
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, 05 Apr 2022 08:31:23 -0000

Dear all:
	I don't have any IPR in this draft.

Best Regards!
Su Li(=E7=B2=9F=E6=A0=97)

-----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
=E5=8F=91=E4=BB=B6=E4=BA=BA: Valery Smyslov [mailto:valery@smyslov.net]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2022=E5=B9=B44=E6=9C=884=E6=97=A5 =
15:26
=E6=94=B6=E4=BB=B6=E4=BA=BA: 'H Y'
=E6=8A=84=E9=80=81: draft-ietf-dots-telemetry-use-cases@ietf.org; =
'dots'; 'dots-chairs'
=E4=B8=BB=E9=A2=98: RE: Shepherd review of =
draft-ietf-dots-telemetry-use-cases

Hi Yuhei,

thank you for updating the document. I've been waiting for the=20
remaining author to provide IPR confirmation. Once I receive it,
I'll send the document to IESG.

Regards,
Valery.

> Hi Valery,
>=20
> Thank you for your careful review.
>=20
> We fixed the nits and posted it as =
draft-ietf-dots-telemetry-use-cases-10.
>=20
> >4. Section 3.1.1.
> >   After that, the orchestrator
> >   orders the forwarding nodes to redirect as much of the top =
talker's traffic...
> > Shouldn't it be top-talkers' ?
> >7. Section 3.1.5.
> > s/The forwarding nodes  send traffic statistics ... to the =
orchestrator the using "vendor-id" and "attack-id"
> telemetry attributes/
> > The forwarding nodes  send traffic statistics ... to the =
orchestrator by using "vendor-id" and "attack-id"
> telemetry attributes
>=20
> We found the same nits in draft-ietf-dots-telemetry-use-cases-9, so we
> fixed them all.
>=20
> Thanks,
> Yuhei
>=20
> 2022=E5=B9=B43=E6=9C=8831=E6=97=A5(=E6=9C=A8) 22:54 Valery Smyslov =
<valery@smyslov.net>:
> >
> > Hi,
> >
> > I reviewed the document and found some nits (mostly grammar and =
typos).
> >
> > 1. Abstract.
> >
> > The expansion of DOTS is "DDoS Open Threat Signaling". In the =
abstract it is expanded as "Denial-of-service
> Open Threat Signaling".
> >
> > 2. Figure 1, Figure 3, Figure 5, Figure 7, Figure 16, Figure 18.
> >
> > All contain the same typo:
> >
> > s/S is for DOTS client functionality/S is for DOTS server =
functionality
> >
> > 3. Section 3.1.1.
> >
> > IPFIX, BGP, SNMP aren't expanded on first use.
> >
> > 4. Section 3.1.1.
> >
> >    After that, the orchestrator
> >    orders the forwarding nodes to redirect as much of the top =
talker's traffic...
> >
> > Shouldn't it be top-talkers' ?
> >
> > 5. Figure 7.
> >
> > s/BGP Flow spec/BGP Flowspec
> >
> > 6. Section 3.1.5.
> >
> > s/It may also necessary/It may also be necessary
> >
> > 7. Section 3.1.5.
> >
> > s/The forwarding nodes  send traffic statistics ... to the =
orchestrator the using "vendor-id" and "attack-id"
> telemetry attributes/
> > The forwarding nodes  send traffic statistics ... to the =
orchestrator by using "vendor-id" and "attack-id"
> telemetry attributes
> >
> > 8. Section 3.2.
> >
> > s/Figure 15 provides ...  from the orchestrator to the network =
./Figure 15 provides ...  from the orchestrator
> to the network.
> >
> > 9. Section 3.2.
> >
> > s/Then, the DDoS mitigation systems reports the status of DDoS =
countermeasures to the orchestrator
> sending "attack-detail" telemetry
> > attributes./
> > Then, the DDoS mitigation systems reports the status of DDoS =
countermeasures to the orchestrator by
> sending "attack-detail"
> > telemetry attributes.
> >
> > 10. Section 3.2.
> >
> > s/After  that, the orchestrator integrates the reports ... and send =
it to a network administrator .../
> > After  that, the orchestrator integrates the reports ... and sends =
them to a network administrator ...
> >
> > (two places)
> >
> > 11. Section 3.3.1.
> >
> >    On the other hand, DDoS detection based on the
> >    DMSes is a more accurate method for detecting attack traffic =
better
> >    than flow monitoring.
> >
> > I have trouble parsing this text. Probably:
> >
> >   On the other hand, DDoS detection based on the
> >    DMSes is a more accurate method for detecting attack traffic
> >    than flow monitoring.
> >
> > 12. Section 3.3.1.
> >
> > s/The aim of this use case is to increases flow collector's =
detection .../The aim of this use case is to increase
> flow collector's
> > detection ...
> >
> > 13. Section 3.3.1.
> >
> > s/statisticsto/statistics to
> >
> > 14. Section 4.
> >
> > s/a DDoS attacks/DDoS attacks
> >
> > Regards,
> > Valery.
> >
>=20
>=20
> --
> ----------------------------------
> Yuuhei HAYASHI
> 08065300884
> yuuhei.hayashi@gmail.com
> iehuuy_0220@docomo.ne.jp
> ----------------------------------





From nobody Mon Apr 11 04:20:24 2022
Return-Path: <smyslov.ietf@gmail.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 1C5F63A17E8; Mon, 11 Apr 2022 04:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level: 
X-Spam-Status: No, score=-2.108 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, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 tDuIaqN8FkTt; Mon, 11 Apr 2022 04:20:17 -0700 (PDT)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 EE89E3A17E1; Mon, 11 Apr 2022 04:20:16 -0700 (PDT)
Received: by mail-lf1-x12e.google.com with SMTP id t25so25988883lfg.7; Mon, 11 Apr 2022 04:20:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112;  h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=svAcXY5gdDTh8dpT1JPYhiyNJ5wNH+s/pNPqom+VbWs=; b=h4utLbylCRk1Y9w2BUjv5xiexswXfPInRLLEczhN8ktLzL+w/eaRnyc1QVJj0PAFCf 2SETREvRf7VsSERB3qArRfYJ/hOTMZOLlH4hQwdgkvA27+56zmyX5trgXuXKdNoxEsjU vsyj1PJp6659QUjrPIlZFxmAoErY3wcfZq6WQ/2PBhsoNv6ErcPPHrtGONw9JSr8WHkn wepmHmOrV8NXsG5knLSw4uh6ohHTaTQcvVSSBiBtA+MJUadSTcBmS15vwRP6i7cBg10v VD6Bqtaocr7kD7D/0LDamjiQJqdwM9oknV2hIZxP92Q0jfsZg8rccHtQq1CaKMQ6nQX8 kpvw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=svAcXY5gdDTh8dpT1JPYhiyNJ5wNH+s/pNPqom+VbWs=; b=FkxAHwLrA8Xsa6HKQCTzbLiWxuO4xFxm7WvNu6iSe2g2rt2/coPFcjNZ5vW40x0N2u YQnmddaBewHFhJTdl6thvrMXtcKck7hPEerQTvkkJUnl6zA1ZCrsum6D53c0ZhrA+KRP NmiBntMnFtwqQKL+mL22blJ0XqXyFqXI61rkDHBCQF30B5zQS9ptK7W2G8S/E4iZGBnC 3kMqjRLKB6dP3A91m8I1UznWaQNcqK9kNEI2yZtVILCOIZM+oK3d9DJp9ICmDcp3nRV3 2g+tDczXCeC3j55YowUSu71GQ2hW4ouAEc0TK7iHuxCD4ZLUEmJgBY99QypBGdwMoIw5 GOMQ==
X-Gm-Message-State: AOAM5321XuMysVDXAZGu/pfapUJCaqlMY3hhhz1mtoL4UlTCqQ1tvD6s UjI488GKv27V4Q8kIJbimYW1Jb71lSw=
X-Google-Smtp-Source: ABdhPJxZAM5UwyMA+UBEgcdVaLK/JkMOOcLPV4tOp8TyNwTI4QbWiYY1K4MpsgZtaBmCW0wdU3I/6g==
X-Received: by 2002:a05:6512:3a83:b0:46a:38a2:d7e with SMTP id q3-20020a0565123a8300b0046a38a20d7emr11649880lfu.61.1649676014212;  Mon, 11 Apr 2022 04:20:14 -0700 (PDT)
Received: from buildpc ([93.188.44.204]) by smtp.gmail.com with ESMTPSA id u19-20020a197913000000b00448a1f20261sm3295854lfc.34.2022.04.11.04.20.12 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 11 Apr 2022 04:20:13 -0700 (PDT)
From: "Valery Smyslov" <smyslov.ietf@gmail.com>
To: "'SuLi'" <suli@chinamobile.com>
Cc: <draft-ietf-dots-telemetry-use-cases@ietf.org>, "'dots'" <dots@ietf.org>,  "'dots-chairs'" <dots-chairs@ietf.org>
References: <19f101d84506$df98e810$9ecab830$@smyslov.net> <CAA8pjUN_aq7zJGxb9ErWCpVwpBgxa-E6UOuD9rWSf5wi9HSD5A@mail.gmail.com> <1bec01d847f5$47685890$d63909b0$@smyslov.net> <002b01d848c7$858cd240$90a676c0$@com>
In-Reply-To: <002b01d848c7$858cd240$90a676c0$@com>
Date: Mon, 11 Apr 2022 14:20:12 +0300
Message-ID: <1fb701d84d96$1d4f5080$57edf180$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQJVlQNLgeASXdSWg3oo1N+vMEhaoAHfpd/4AmLtYWYCcZdk/6u6YESQ
Content-Language: ru
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/-J7SHDHbrQHK6aoqZmjpTc8D0_s>
Subject: Re: [Dots] =?utf-8?b?562U5aSNOiBTaGVwaGVyZCByZXZpZXcgb2YgZHJhZnQt?= =?utf-8?q?ietf-dots-telemetry-use-cases?=
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, 11 Apr 2022 11:20:22 -0000

Hi,

BCP78 and BCP79 requires that all authors and contributors confirm that =
they are=20
not _aware_ of any IPR (or disclose them). So, it is not sufficient to =
confirm=20
that you don't _have_ any IPR, you must confirm that you are not _aware_
of any IPR (for example, your employer may have one). Note, that you are =
not
required to search through all IPRs, you only required to confirm that =
you
are not aware of any.

So, please you re-confirm that you are not aware of any IPR related to =
the draft.

Regards,
Valery.

> Dear all:
> 	I don't have any IPR in this draft.
>=20
> Best Regards!
> Su Li(=E7=B2=9F=E6=A0=97)
>=20
> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: Valery Smyslov =
[mailto:valery@smyslov.net]
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2022=E5=B9=B44=E6=9C=884=E6=97=A5 15:26
> =E6=94=B6=E4=BB=B6=E4=BA=BA: 'H Y'
> =E6=8A=84=E9=80=81: draft-ietf-dots-telemetry-use-cases@ietf.org; =
'dots'; 'dots-chairs'
> =E4=B8=BB=E9=A2=98: RE: Shepherd review of =
draft-ietf-dots-telemetry-use-cases
>=20
> Hi Yuhei,
>=20
> thank you for updating the document. I've been waiting for the
> remaining author to provide IPR confirmation. Once I receive it,
> I'll send the document to IESG.
>=20
> Regards,
> Valery.
>=20
> > Hi Valery,
> >
> > Thank you for your careful review.
> >
> > We fixed the nits and posted it as =
draft-ietf-dots-telemetry-use-cases-10.
> >
> > >4. Section 3.1.1.
> > >   After that, the orchestrator
> > >   orders the forwarding nodes to redirect as much of the top =
talker's traffic...
> > > Shouldn't it be top-talkers' ?
> > >7. Section 3.1.5.
> > > s/The forwarding nodes  send traffic statistics ... to the =
orchestrator the using "vendor-id" and "attack-id"
> > telemetry attributes/
> > > The forwarding nodes  send traffic statistics ... to the =
orchestrator by using "vendor-id" and "attack-id"
> > telemetry attributes
> >
> > We found the same nits in draft-ietf-dots-telemetry-use-cases-9, so =
we
> > fixed them all.
> >
> > Thanks,
> > Yuhei
> >
> > 2022=E5=B9=B43=E6=9C=8831=E6=97=A5(=E6=9C=A8) 22:54 Valery Smyslov =
<valery@smyslov.net>:
> > >
> > > Hi,
> > >
> > > I reviewed the document and found some nits (mostly grammar and =
typos).
> > >
> > > 1. Abstract.
> > >
> > > The expansion of DOTS is "DDoS Open Threat Signaling". In the =
abstract it is expanded as "Denial-of-
> service
> > Open Threat Signaling".
> > >
> > > 2. Figure 1, Figure 3, Figure 5, Figure 7, Figure 16, Figure 18.
> > >
> > > All contain the same typo:
> > >
> > > s/S is for DOTS client functionality/S is for DOTS server =
functionality
> > >
> > > 3. Section 3.1.1.
> > >
> > > IPFIX, BGP, SNMP aren't expanded on first use.
> > >
> > > 4. Section 3.1.1.
> > >
> > >    After that, the orchestrator
> > >    orders the forwarding nodes to redirect as much of the top =
talker's traffic...
> > >
> > > Shouldn't it be top-talkers' ?
> > >
> > > 5. Figure 7.
> > >
> > > s/BGP Flow spec/BGP Flowspec
> > >
> > > 6. Section 3.1.5.
> > >
> > > s/It may also necessary/It may also be necessary
> > >
> > > 7. Section 3.1.5.
> > >
> > > s/The forwarding nodes  send traffic statistics ... to the =
orchestrator the using "vendor-id" and "attack-id"
> > telemetry attributes/
> > > The forwarding nodes  send traffic statistics ... to the =
orchestrator by using "vendor-id" and "attack-id"
> > telemetry attributes
> > >
> > > 8. Section 3.2.
> > >
> > > s/Figure 15 provides ...  from the orchestrator to the network =
./Figure 15 provides ...  from the
> orchestrator
> > to the network.
> > >
> > > 9. Section 3.2.
> > >
> > > s/Then, the DDoS mitigation systems reports the status of DDoS =
countermeasures to the orchestrator
> > sending "attack-detail" telemetry
> > > attributes./
> > > Then, the DDoS mitigation systems reports the status of DDoS =
countermeasures to the orchestrator by
> > sending "attack-detail"
> > > telemetry attributes.
> > >
> > > 10. Section 3.2.
> > >
> > > s/After  that, the orchestrator integrates the reports ... and =
send it to a network administrator .../
> > > After  that, the orchestrator integrates the reports ... and sends =
them to a network administrator ...
> > >
> > > (two places)
> > >
> > > 11. Section 3.3.1.
> > >
> > >    On the other hand, DDoS detection based on the
> > >    DMSes is a more accurate method for detecting attack traffic =
better
> > >    than flow monitoring.
> > >
> > > I have trouble parsing this text. Probably:
> > >
> > >   On the other hand, DDoS detection based on the
> > >    DMSes is a more accurate method for detecting attack traffic
> > >    than flow monitoring.
> > >
> > > 12. Section 3.3.1.
> > >
> > > s/The aim of this use case is to increases flow collector's =
detection .../The aim of this use case is to increase
> > flow collector's
> > > detection ...
> > >
> > > 13. Section 3.3.1.
> > >
> > > s/statisticsto/statistics to
> > >
> > > 14. Section 4.
> > >
> > > s/a DDoS attacks/DDoS attacks
> > >
> > > Regards,
> > > Valery.
> > >
> >
> >
> > --
> > ----------------------------------
> > Yuuhei HAYASHI
> > 08065300884
> > yuuhei.hayashi@gmail.com
> > iehuuy_0220@docomo.ne.jp
> > ----------------------------------
>=20
>=20
>=20
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots


From nobody Mon Apr 11 18:09:22 2022
Return-Path: <suli@chinamobile.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 40E183A0D27; Mon, 11 Apr 2022 18:09:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level: 
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 QLjx-PXrDhjS; Mon, 11 Apr 2022 18:09:15 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id 3C96C3A0D1B; Mon, 11 Apr 2022 18:09:13 -0700 (PDT)
X-RM-TagInfo: emlType=0                                       
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.7]) by rmmx-syy-dmz-app01-12001 (RichMail) with SMTP id 2ee16254d137cc3-73127; Tue, 12 Apr 2022 09:09:12 +0800 (CST)
X-RM-TRANSID: 2ee16254d137cc3-73127
X-RM-TagInfo: emlType=0                                       
X-RM-SPAM-FLAG: 00000000
Received: from cmccPC (unknown[10.2.53.192]) by rmsmtp-syy-appsvr04-12004 (RichMail) with SMTP id 2ee46254d136403-12af0; Tue, 12 Apr 2022 09:09:11 +0800 (CST)
X-RM-TRANSID: 2ee46254d136403-12af0
From: "SuLi" <suli@chinamobile.com>
To: "'Valery Smyslov'" <smyslov.ietf@gmail.com>
Cc: <draft-ietf-dots-telemetry-use-cases@ietf.org>, "'dots'" <dots@ietf.org>,  "'dots-chairs'" <dots-chairs@ietf.org>
References: <19f101d84506$df98e810$9ecab830$@smyslov.net> <CAA8pjUN_aq7zJGxb9ErWCpVwpBgxa-E6UOuD9rWSf5wi9HSD5A@mail.gmail.com> <1bec01d847f5$47685890$d63909b0$@smyslov.net> <002b01d848c7$858cd240$90a676c0$@com> <1fb701d84d96$1d4f5080$57edf180$@gmail.com>
In-Reply-To: <1fb701d84d96$1d4f5080$57edf180$@gmail.com>
Date: Tue, 12 Apr 2022 09:09:11 +0800
Message-ID: <000501d84e09$ebc5a360$c350ea20$@com>
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQJVlQNLgeASXdSWg3oo1N+vMEhaoAHfpd/4AmLtYWYCcZdk/6u6YESQgADoDJA=
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/2wLUOaoLGXOmLqmwnAo2AREgwuU>
Subject: [Dots] =?utf-8?b?562U5aSNOiAg562U5aSNOiBTaGVwaGVyZCByZXZpZXcg?= =?utf-8?q?of_draft-ietf-dots-telemetry-use-cases?=
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, 12 Apr 2022 01:09:20 -0000

Dear all,
	As one of the authors, I'm not aware of any IPR for this draft.=20
	Thank you.

Best Regards!
Su Li(=E7=B2=9F=E6=A0=97)

-----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
=E5=8F=91=E4=BB=B6=E4=BA=BA: Valery Smyslov =
[mailto:smyslov.ietf@gmail.com]=20
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2022=E5=B9=B44=E6=9C=8811=E6=97=A5 =
19:20
=E6=94=B6=E4=BB=B6=E4=BA=BA: 'SuLi'
=E6=8A=84=E9=80=81: draft-ietf-dots-telemetry-use-cases@ietf.org; =
'dots'; 'dots-chairs'
=E4=B8=BB=E9=A2=98: RE: [Dots] =E7=AD=94=E5=A4=8D: Shepherd review of =
draft-ietf-dots-telemetry-use-cases

Hi,

BCP78 and BCP79 requires that all authors and contributors confirm that =
they are=20
not _aware_ of any IPR (or disclose them). So, it is not sufficient to =
confirm=20
that you don't _have_ any IPR, you must confirm that you are not _aware_
of any IPR (for example, your employer may have one). Note, that you are =
not
required to search through all IPRs, you only required to confirm that =
you
are not aware of any.

So, please you re-confirm that you are not aware of any IPR related to =
the draft.

Regards,
Valery.

> Dear all:
> 	I don't have any IPR in this draft.
>=20
> Best Regards!
> Su Li(=E7=B2=9F=E6=A0=97)
>=20
> -----=E9=82=AE=E4=BB=B6=E5=8E=9F=E4=BB=B6-----
> =E5=8F=91=E4=BB=B6=E4=BA=BA: Valery Smyslov =
[mailto:valery@smyslov.net]
> =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: =
2022=E5=B9=B44=E6=9C=884=E6=97=A5 15:26
> =E6=94=B6=E4=BB=B6=E4=BA=BA: 'H Y'
> =E6=8A=84=E9=80=81: draft-ietf-dots-telemetry-use-cases@ietf.org; =
'dots'; 'dots-chairs'
> =E4=B8=BB=E9=A2=98: RE: Shepherd review of =
draft-ietf-dots-telemetry-use-cases
>=20
> Hi Yuhei,
>=20
> thank you for updating the document. I've been waiting for the
> remaining author to provide IPR confirmation. Once I receive it,
> I'll send the document to IESG.
>=20
> Regards,
> Valery.
>=20
> > Hi Valery,
> >
> > Thank you for your careful review.
> >
> > We fixed the nits and posted it as =
draft-ietf-dots-telemetry-use-cases-10.
> >
> > >4. Section 3.1.1.
> > >   After that, the orchestrator
> > >   orders the forwarding nodes to redirect as much of the top =
talker's traffic...
> > > Shouldn't it be top-talkers' ?
> > >7. Section 3.1.5.
> > > s/The forwarding nodes  send traffic statistics ... to the =
orchestrator the using "vendor-id" and "attack-id"
> > telemetry attributes/
> > > The forwarding nodes  send traffic statistics ... to the =
orchestrator by using "vendor-id" and "attack-id"
> > telemetry attributes
> >
> > We found the same nits in draft-ietf-dots-telemetry-use-cases-9, so =
we
> > fixed them all.
> >
> > Thanks,
> > Yuhei
> >
> > 2022=E5=B9=B43=E6=9C=8831=E6=97=A5(=E6=9C=A8) 22:54 Valery Smyslov =
<valery@smyslov.net>:
> > >
> > > Hi,
> > >
> > > I reviewed the document and found some nits (mostly grammar and =
typos).
> > >
> > > 1. Abstract.
> > >
> > > The expansion of DOTS is "DDoS Open Threat Signaling". In the =
abstract it is expanded as "Denial-of-
> service
> > Open Threat Signaling".
> > >
> > > 2. Figure 1, Figure 3, Figure 5, Figure 7, Figure 16, Figure 18.
> > >
> > > All contain the same typo:
> > >
> > > s/S is for DOTS client functionality/S is for DOTS server =
functionality
> > >
> > > 3. Section 3.1.1.
> > >
> > > IPFIX, BGP, SNMP aren't expanded on first use.
> > >
> > > 4. Section 3.1.1.
> > >
> > >    After that, the orchestrator
> > >    orders the forwarding nodes to redirect as much of the top =
talker's traffic...
> > >
> > > Shouldn't it be top-talkers' ?
> > >
> > > 5. Figure 7.
> > >
> > > s/BGP Flow spec/BGP Flowspec
> > >
> > > 6. Section 3.1.5.
> > >
> > > s/It may also necessary/It may also be necessary
> > >
> > > 7. Section 3.1.5.
> > >
> > > s/The forwarding nodes  send traffic statistics ... to the =
orchestrator the using "vendor-id" and "attack-id"
> > telemetry attributes/
> > > The forwarding nodes  send traffic statistics ... to the =
orchestrator by using "vendor-id" and "attack-id"
> > telemetry attributes
> > >
> > > 8. Section 3.2.
> > >
> > > s/Figure 15 provides ...  from the orchestrator to the network =
./Figure 15 provides ...  from the
> orchestrator
> > to the network.
> > >
> > > 9. Section 3.2.
> > >
> > > s/Then, the DDoS mitigation systems reports the status of DDoS =
countermeasures to the orchestrator
> > sending "attack-detail" telemetry
> > > attributes./
> > > Then, the DDoS mitigation systems reports the status of DDoS =
countermeasures to the orchestrator by
> > sending "attack-detail"
> > > telemetry attributes.
> > >
> > > 10. Section 3.2.
> > >
> > > s/After  that, the orchestrator integrates the reports ... and =
send it to a network administrator .../
> > > After  that, the orchestrator integrates the reports ... and sends =
them to a network administrator ...
> > >
> > > (two places)
> > >
> > > 11. Section 3.3.1.
> > >
> > >    On the other hand, DDoS detection based on the
> > >    DMSes is a more accurate method for detecting attack traffic =
better
> > >    than flow monitoring.
> > >
> > > I have trouble parsing this text. Probably:
> > >
> > >   On the other hand, DDoS detection based on the
> > >    DMSes is a more accurate method for detecting attack traffic
> > >    than flow monitoring.
> > >
> > > 12. Section 3.3.1.
> > >
> > > s/The aim of this use case is to increases flow collector's =
detection .../The aim of this use case is to increase
> > flow collector's
> > > detection ...
> > >
> > > 13. Section 3.3.1.
> > >
> > > s/statisticsto/statistics to
> > >
> > > 14. Section 4.
> > >
> > > s/a DDoS attacks/DDoS attacks
> > >
> > > Regards,
> > > Valery.
> > >
> >
> >
> > --
> > ----------------------------------
> > Yuuhei HAYASHI
> > 08065300884
> > yuuhei.hayashi@gmail.com
> > iehuuy_0220@docomo.ne.jp
> > ----------------------------------
>=20
>=20
>=20
>=20
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots





From nobody Mon Apr 11 22:50:58 2022
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 3719D3A0658; Mon, 11 Apr 2022 22:50:54 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Valery Smyslov via Datatracker <noreply@ietf.org>
To: <paul.wouters@aiven.io>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Cc: dots-chairs@ietf.org, dots@ietf.org, iesg-secretary@ietf.org, valery@smyslov.net
Message-ID: <164974265414.22301.4095444885393292996@ietfa.amsl.com>
Date: Mon, 11 Apr 2022 22:50:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/AdJdCeYSe1lwv7AJtT87zsQiyZY>
Subject: [Dots] Publication has been requested for draft-ietf-dots-telemetry-use-cases-10
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, 12 Apr 2022 05:50:55 -0000

Valery Smyslov has requested publication of draft-ietf-dots-telemetry-use-cases-10 as Informational on behalf of the DOTS working group.

Please verify the document's state at https://datatracker.ietf.org/doc/draft-ietf-dots-telemetry-use-cases/



From nobody Thu Apr 14 16:28:06 2022
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 22F6D3A0B90; Thu, 14 Apr 2022 16:27:55 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Martin Duke via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-dots-multihoming@ietf.org, dots-chairs@ietf.org, dots@ietf.org,  valery@smyslov.net, valery@smyslov.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.46.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Martin Duke <martin.h.duke@gmail.com>
Message-ID: <164997887512.2774.16348083045059376497@ietfa.amsl.com>
Date: Thu, 14 Apr 2022 16:27:55 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/so1-VH95iwo3i16KCR8ljqQaln8>
Subject: [Dots] Martin Duke's No Objection on draft-ietf-dots-multihoming-11: (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, 14 Apr 2022 23:27:56 -0000

Martin Duke has entered the following ballot position for
draft-ietf-dots-multihoming-11: 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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


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



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

Thanks to Mirja Kuhlewind for the TSVART review.

There is nothing at all wrong with this document, but it is not what I
expected. IIUC DOTS will often have different interfaces for its DOTS channel
and the "data plane" where DoS attacks come in. I had thought the multihoming
reference would refer to that, but it does not.



