[Dots] 答复: Shepherd review of draft-ietf-dots-telemetry-use-cases

SuLi <suli@chinamobile.com> Tue, 05 April 2022 08:31 UTC

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, 05 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] 答复: 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: Tue, 05 Apr 2022 08:31:23 -0000

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

Best Regards!
Su Li(粟栗)

-----邮件原件-----
发件人: Valery Smyslov [mailto:valery@smyslov.net] 
发送时间: 2022年4月4日 15:26
收件人: 'H Y'
抄送: draft-ietf-dots-telemetry-use-cases@ietf.org; 'dots'; 'dots-chairs'
主题: RE: Shepherd review of draft-ietf-dots-telemetry-use-cases

Hi Yuhei,

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.

Regards,
Valery.

> 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年3月31日(木) 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
> ----------------------------------