[Dots] 答复: Several comments on draft-ietf-dots-use-cases-13:

"Xialiang (Frank, Network Integration Technology Research Dept)" <frank.xialiang@huawei.com> Wed, 18 July 2018 15:43 UTC

Return-Path: <frank.xialiang@huawei.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 BFEDD1311AD for <dots@ietfa.amsl.com>; Wed, 18 Jul 2018 08:43:29 -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, HTML_MESSAGE=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 fhOQ69KD21vu for <dots@ietfa.amsl.com>; Wed, 18 Jul 2018 08:43:24 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 EDECD1311CD for <dots@ietf.org>; Wed, 18 Jul 2018 08:43:23 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 256E57E9D679; Wed, 18 Jul 2018 16:43:17 +0100 (IST)
Received: from DGGEML406-HUB.china.huawei.com (10.3.17.50) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.399.0; Wed, 18 Jul 2018 16:43:18 +0100
Received: from DGGEML522-MBX.china.huawei.com ([169.254.7.38]) by dggeml406-hub.china.huawei.com ([10.3.17.50]) with mapi id 14.03.0382.000; Wed, 18 Jul 2018 23:43:13 +0800
From: "Xialiang (Frank, Network Integration Technology Research Dept)" <frank.xialiang@huawei.com>
To: Daniel Migault <daniel.migault@ericsson.com>, "'Teague, Nik'" <nteague@verisign.com>, 'kaname nishizuka' <kaname@nttv6.jp>, 'Roland Dobbins' <rdobbins@arbor.net>, 'Robert Moskowitz' <rgm@htt-consult.com>, "dots@ietf.org" <dots@ietf.org>
CC: 'Roman Danyliw' <rdd@cert.org>, 'Tobias Gondrom' <tobias.gondrom@gondrom.org>
Thread-Topic: Several comments on draft-ietf-dots-use-cases-13:
Thread-Index: AdQY77lNzr+bolzDRtSLZf/vgfxz5wFJhb+QAAq3zLAAGoRFwAAAzlzQ
Date: Wed, 18 Jul 2018 15:43:14 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F12BE6CEE1@DGGEML522-MBX.china.huawei.com>
References: <C02846B1344F344EB4FAA6FA7AF481F12BE33C87@DGGEML522-MBX.china.huawei.com> <C02846B1344F344EB4FAA6FA7AF481F12BE6BFF1@DGGEML522-MBX.china.huawei.com> <af15eef3686e46a09e71379d33cb5903@ericsson.com> <2eb582e02b924333a43b64f87b6757a0@ericsson.com>
In-Reply-To: <2eb582e02b924333a43b64f87b6757a0@ericsson.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.124.182.76]
Content-Type: multipart/alternative; boundary="_000_C02846B1344F344EB4FAA6FA7AF481F12BE6CEE1DGGEML522MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/t5p2G_UtoE6Mc7iFIk0IYojyNyQ>
Subject: [Dots] 答复: Several comments on draft-ietf-dots-use-cases-13:
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.27
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, 18 Jul 2018 15:43:35 -0000

Hi Daniel,
Thanks for response and addressing this comments.
I am fine with all of them.

B.R.
Frank

发件人: Daniel Migault [mailto:daniel.migault@ericsson.com]
发送时间: 2018年7月18日 23:40
收件人: Xialiang (Frank, Network Integration Technology Research Dept) <frank.xialiang@huawei.com>; 'Teague, Nik' <nteague@verisign.com>; 'kaname nishizuka' <kaname@nttv6.jp>; 'Roland Dobbins' <rdobbins@arbor.net>; 'Robert Moskowitz' <rgm@htt-consult.com>; dots@ietf.org
抄送: 'Roman Danyliw' <rdd@cert.org>; 'Tobias Gondrom' <tobias.gondrom@gondrom.org>
主题: RE: Several comments on draft-ietf-dots-use-cases-13:

Hi Frank,

Thanks you for the comments, please fine my responses inline.

Yours,
Daniel
发件人: Xialiang (Frank, Network Integration Technology Research Dept)
发送时间: 2018年7月11日 16:42
收件人: Daniel Migault <daniel.migault@ericsson.com<mailto:daniel.migault@ericsson.com>>; Teague, Nik <nteague@verisign.com<mailto:nteague@verisign.com>>; kaname nishizuka <kaname@nttv6.jp<mailto:kaname@nttv6.jp>>; Roland Dobbins <rdobbins@arbor.net<mailto:rdobbins@arbor.net>>; Robert Moskowitz <rgm@htt-consult.com<mailto:rgm@htt-consult.com>>
抄送: Roman Danyliw <rdd@cert.org<mailto:rdd@cert.org>>; Tobias Gondrom <tobias.gondrom@gondrom.org<mailto:tobias.gondrom@gondrom.org>>
主题: Several comments on draft-ietf-dots-use-cases-13:

Hi Daniel and all co-authors,
I have made some updates to the latest draft directly in Github, which mainly relates with the editorial nits or some more clarification texts. Please double check my update!

<mglt>
These have been considered I guess. If you have more comments, please provide them on the mkd version to avoid lost in translation.
</mglt>

In addition, I still have some comments as below for your consideration:

1.       Section 1: “and attack characterization patterns”. From my side, these terms are vague and tend to mislead readers. Why now delete it and replace it with the sentence like: “, mitigation status/efficacy and other complimentary information”?
<mglt>
Adding “and attack characteristics such as ….

</mglt>


2.       Section 2: suggest to re-order the terms as: DDoS Mitigation; DDoS Mitigation Service; DMS; DDoS Mitigation Service Provider; ITP;

<mglt>
DDoS Mitigation needs to be after DMS.
DDoS Mitigation Service needs to be after DMS DDoS Service Provider
Other wise I believe I changed the order as close as what you proposed – without changing the definition 😉
</mglt>


3.       Section 3.1, suggest to add one sentence at last about: “Note that this use cases also applies to the situation that the downstream ISP network as the target network and requests the coordinated mitigation response to the upstream ITP”;

<mglt>
I think we have removed this sentence.
</mglt>


4.       Section 3.3, / the network administrator triggers the DDoS mitigation request using the web interface of a DOTS client/ the network administrator triggers the DDoS mitigation request using the web interface of the orchestrator
<mglt>
I believe the text below clarifies the concern:
the web interface of a DOTS client connected to the
orchestrator
</mglt>
Thanks!

B.R.
Frank