[Dots] we can consider update current DOTS use cases draft to reflect your case://答复: Hi, authors, 3 questions on draft-hayashi-dots-dms-offload-usecase-01:

"Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com> Fri, 12 July 2019 06:15 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 0B088120052; Thu, 11 Jul 2019 23:15:36 -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 nhdbXhnkOQp3; Thu, 11 Jul 2019 23:15:33 -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 9F3A7120048; Thu, 11 Jul 2019 23:15:32 -0700 (PDT)
Received: from lhreml705-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 3205183978519F59D907; Fri, 12 Jul 2019 07:15:30 +0100 (IST)
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by lhreml705-cah.china.huawei.com (10.201.108.46) with Microsoft SMTP Server (TLS) id 14.3.408.0; Fri, 12 Jul 2019 07:15:29 +0100
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1713.5; Fri, 12 Jul 2019 07:15:29 +0100
Received: from DGGEMM403-HUB.china.huawei.com (10.3.20.211) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1713.5 via Frontend Transport; Fri, 12 Jul 2019 07:15:29 +0100
Received: from DGGEMM511-MBX.china.huawei.com ([169.254.1.140]) by DGGEMM403-HUB.china.huawei.com ([10.3.20.211]) with mapi id 14.03.0439.000; Fri, 12 Jul 2019 14:12:44 +0800
From: "Xialiang (Frank, Network Standard & Patent Dept)" <frank.xialiang@huawei.com>
To: H Y <yuuhei.hayashi@gmail.com>
CC: "draft-hayashi-dots-dms-offload-usecase.authors@ietf.org" <draft-hayashi-dots-dms-offload-usecase.authors@ietf.org>, Valery Smyslov <valery@smyslov.net>, "dots@ietf.org" <dots@ietf.org>, "neshi-nwsec-p-ml@hco.ntt.co.jp" <neshi-nwsec-p-ml@hco.ntt.co.jp>
Thread-Topic: =?utf-8?B?d2UgY2FuIGNvbnNpZGVyIHVwZGF0ZSBjdXJyZW50IERPVFMgdXNlIGNhc2Vz?= =?utf-8?B?IGRyYWZ0IHRvIHJlZmxlY3QgeW91ciBjYXNlOi8v562U5aSNOiBbRG90c10g?= =?utf-8?B?SGksIGF1dGhvcnMsIDMgcXVlc3Rpb25zIG9uIGRyYWZ0LWhheWFzaGktZG90?= =?utf-8?Q?s-dms-offload-usecase-01:?=
Thread-Index: AdU4drc3kJSvluH1S52+pXatmcOeWA==
Date: Fri, 12 Jul 2019 06:12:44 +0000
Message-ID: <C02846B1344F344EB4FAA6FA7AF481F13E7C88B2@dggemm511-mbx.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.134.159.76]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/HprYLyWUw9U5fUyLg-Ox3ei-5yk>
Subject: [Dots] =?utf-8?q?we_can_consider_update_current_DOTS_use_cases_d?= =?utf-8?b?cmFmdCB0byByZWZsZWN0IHlvdXIgY2FzZTovL+etlOWkjTogIEhpLCBhdXRo?= =?utf-8?q?ors=2C_3_questions_on_draft-hayashi-dots-dms-offload-usecase-01?= =?utf-8?q?=3A?=
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, 12 Jul 2019 06:15:36 -0000

Hi Yuhei,
Thanks for quick and clear clarification.

See inline:

And in summary from my side, the only thing we may need to do according to your proposal is to update the DOTS use cases draft to reflect your new case: " It's effective that DMS have DOTS client function in DOTS orchestration use case ".
But we welcome more discussions.

B.R.
Frank

-----邮件原件-----
发件人: H Y [mailto:yuuhei.hayashi@gmail.com] 
发送时间: 2019年7月12日 13:00
收件人: Xialiang (Frank, Network Standard & Patent Dept) <frank.xialiang@huawei.com>;
抄送: draft-hayashi-dots-dms-offload-usecase.authors@ietf.org; Valery Smyslov <valery@smyslov.net>;; dots@ietf.org; neshi-nwsec-p-ml@hco.ntt.co.jp
主题: Re: [Dots] Hi, authors, 3 questions on draft-hayashi-dots-dms-offload-usecase-01:

Hi Frank,

Thank you for reviewing my draft :-)
Please see inline.

> 1.  I see your proposed offload use case as an variant of DOTS Orchestration use case (section 3.3 of draft-ietf-dots-use-cases-18).
[hayashi]Yes, that's right.

> If so, what is your propose for this part of content? Do you want to improve the existing DOTS use cases WG draft with your addition?
[hayashi]Yes, I want to add our use case to improve the DOTS orchestration use cases.
About the DOTS orchestration use case in current use cases WG draft, DMS doesn't have DOTS client function.
IMO, it's effective that DMSs send blocked information to an orchestrator via standardized IF and the orchestrator carries out some action in the network.

At IETF 104, I proposed to add our use case to improve the DOTS orchestration use cases, however, I could not do it because the use case WG draft now is in Publication Requested status.
Some people gave me the advice to include DOTS deployment consideration to my draft, so I update my draft based on the comments.

Please see IETF104 minute https://datatracker.ietf.org/doc/minutes-104-dots/

[Frank]: So, I suggest you to contact with DOTS use cases draft authors about this proposal asap, since it's in the AD Evaluation status and I think your improvement is just a minor part.

> 2.      Right now, DOTS protocol defines sending DOTS request via signal channel, do you propose to send it via data channel in some situation? If so, I personally disagree with it, since we originally define signal channel and data channel for different functionalities & messages, we can not send any DOTS messages over wrong channel, like: DOTS request via data channel.
[hayashi] After I submitted
draft-h-dots-mitigation-offload-expansion-00,  some people gave me comments not to use signal channel but to use data channel via out-of band because link b/w the DMS and Orchestrator won't be congested under attack time.

Please see the mail thread [Dots]
draft-h-dots-mitigation-offload-expansion-00: Reasons why we want to standardize between DMS and orchestrator using DOTS

Current data channel has the capability to send filtering rules immediately, so I think it can be used to send blocked information from DMS to Orchestrator.
If the signal channel has the capability to convey the attacker's information, the signal channel can be also used to send it to form DMS to Orchestrator.

[Frank]: sending acl filtering rules via DOTS data channel is ok.

> 3.      In addition to extended offload use case content, I do not see any new protocol, message or attribute extension comparing to the existing defined DOTS protocols, the left content are just some examples about how you use the existing DOTS protocol for your offload use case. So, what do you want DOTS WG to do for this draft, since there are no new thing here?
[hayashi] This draft requires that ...
- It's effective that DMS have DOTS client function in DOTS orchestration use case.

[Frank]: this is not excluded in current DOTS architecture, just lack of clear text of this point. You can discuss this point with use cases draft authors.

- It's effective that signal channel has the capability to send src information.
For example, it's useful and feasible to send src port information via the DOTS signal channel to request mitigation against reflection attack.

[Frank]: DOTS signal channel call home draft has already specified it. No more needs to be done.

> And be careful using signal channel call home for your use case, since it is a special mechanism for near source attack mitigation with DOTS server create TLS connection with DOTS client, which I don’t think it’s very suitable for your case.
Thank you for giving me comments. Could I define another signal channel expansion to send src information via signal channel?

[Frank]: I think it's not necessary. You can see my discussion with Med about the same thing just now in: https://mailarchive.ietf.org/arch/msg/dots/hRd3BRTUjXx5roIS2jJ6UXzTny4

Thanks,
Yuhei

2019年7月12日(金) 12:10 Xialiang (Frank, Network Standard & Patent Dept)
<frank.xialiang@huawei.com>;:
>
> Hi authors,
>
> I have reviewed this new version and have 3 questions as below:
>
> 1.      I see your proposed offload use case as an variant of DOTS Orchestration use case (section 3.3 of draft-ietf-dots-use-cases-18). If so, what is your propose for this part of content? Do you want to improve the existing DOTS use cases WG draft with your addition?
>
> 2.      Right now, DOTS protocol defines sending DOTS request via signal channel, do you propose to send it via data channel in some situation? If so, I personally disagree with it, since we originally define signal channel and data channel for different functionalities & messages, we can not send any DOTS messages over wrong channel, like: DOTS request via data channel.
>
> 3.      In addition to extended offload use case content, I do not see any new protocol, message or attribute extension comparing to the existing defined DOTS protocols, the left content are just some examples about how you use the existing DOTS protocol for your offload use case. So, what do you want DOTS WG to do for this draft, since there are no new thing here? And be careful using signal channel call home for your use case, since it is a special mechanism for near source attack mitigation with DOTS server create TLS connection with DOTS client, which I don’t think it’s very suitable for your case.
>
>
>
> Thanks!
>
>
>
> B.R.
>
> Frank
>
>
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots



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