Re: [Dots] My review of draft-ietf-dots-use-cases

kaname nishizuka <kaname@nttv6.jp> Fri, 28 April 2017 07:49 UTC

Return-Path: <kaname@nttv6.jp>
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 DA498128CD5; Fri, 28 Apr 2017 00:49:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.892
X-Spam-Level:
X-Spam-Status: No, score=-1.892 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=unavailable 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 kVQwqDn1dlgo; Fri, 28 Apr 2017 00:49:21 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [IPv6:2402:c800:ff06:136::140]) by ietfa.amsl.com (Postfix) with ESMTP id 51FBF12EA76; Fri, 28 Apr 2017 00:46:07 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [192.168.8.15]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 5013825F69B; Fri, 28 Apr 2017 16:45:36 +0900 (JST)
Received: from DHCP-161.nttv6.jp (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 3C6A9759047; Fri, 28 Apr 2017 16:45:36 +0900 (JST)
To: Daniel Migault <daniel.migault@ericsson.com>, "Teague, Nik" <nteague@verisign.com>
Cc: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "draft-ietf-dots-use-cases@ietf.org" <draft-ietf-dots-use-cases@ietf.org>, "dots-chairs@tools.ietf.org" <dots-chairs@tools.ietf.org>, "dots@ietf.org" <dots@ietf.org>
References: <787AE7BB302AE849A7480A190F8B933009E48936@OPEXCLILMA3.corporate.adroot.infra.ftgroup> <439EDA6D-6550-4010-9EF6-F8C06A15C4D0@verisign.com> <CADZyTknDXs9c+Q-GNS_49e039AsDNrO0ssV5fho=5XGa=9eFkQ@mail.gmail.com> <b7c4faae-cfbb-2d91-757e-6541c4db14d8@nttv6.jp> <2DD56D786E600F45AC6BDE7DA4E8A8C118BD7071@eusaamb107.ericsson.se>
From: kaname nishizuka <kaname@nttv6.jp>
Message-ID: <f78cd29e-2587-f4dd-c253-5b526a3524cb@nttv6.jp>
Date: Fri, 28 Apr 2017 16:45:39 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:52.0) Gecko/20100101 Thunderbird/52.0
MIME-Version: 1.0
In-Reply-To: <2DD56D786E600F45AC6BDE7DA4E8A8C118BD7071@eusaamb107.ericsson.se>
Content-Type: multipart/alternative; boundary="------------667D467562A44A4FD9AB7642"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/gva1EsosLm6WDMJjjnqTfY1ArA8>
Subject: Re: [Dots] My review of draft-ietf-dots-use-cases
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.22
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, 28 Apr 2017 07:49:24 -0000

Thank you for correcting the target repository :)

thank you,
Kaname

On 2017/04/27 22:40, Daniel Migault wrote:
>
> Hi,
>
> Please see the figure added by Kaname to the current repo [1].
>
> Please note that the repo to consider is the one associated to the WG, that is dotswg/dots-use-cases [1]
>
> Yours,
> Daniel
>
> https://github.com/dotswg/dots-use-cases/pull/1/commits/e8e75ff1940b136afeb81d47e0a7d6aea20028ad
>
> *From:*kaname nishizuka [mailto:kaname@nttv6.jp]
> *Sent:* Wednesday, April 26, 2017 11:32 PM
> *To:* Daniel Migault <daniel.migault@ericsson.com>; Teague, Nik <nteague@verisign.com>
> *Cc:* mohamed.boucadair@orange.com; draft-ietf-dots-use-cases@ietf.org; dots-chairs@tools.ietf.org
> *Subject:* Re: My review of draft-ietf-dots-use-cases
>
> Hi Daniel,
>
> I made a pull request of "adding a figure for the orchetsrator use case."
> https://github.com/mglt/draft-ietf-dots-use-cases/pull/4/files
>
> The proposed figure is like this (I hope your editor aligns the figure properly)
>            +----------+
>            | network  |C
>            | adminis  |<-+
>            | trator   |  |
>            +----------+  |
>                          |                       (internal)
>            +----------+  | S+--------------+     +-----------+
>            |telemetry/|  +->|              |C   S| DDoS      |+
>            |monitoring|<--->| Orchestrator |<--->| mitigation||
>            |systems   |C   S|              |<-+  | systems   ||
>            +----------+     +--------------+C | +-----------+|
>                                               | +----------+
>                                               |
>                                               |  (external)
>                                               |  +-----------+
>                                               | S| DDoS      |
>                                               +->| mitigation|
>                                                  | systems   |
>                                                  +-----------+
>            * C is for DOTS client functionality
>            * S is for DOTS server functionality
>
>    Figure 1: DDoS Orchestration
>
> Please see if the figure is fitting to the text of the dots relation in DDoS Orchstration section.
> If you are OK with this change, please merge it.
> By the way, this figure is truly abstraction of our DDoS mitigation service, although it is not using dots protocols yet.
>
> regards,
> Kaname
>
> On 2017/04/25 4:55, Daniel Migault wrote:
>
>     Hi Med,
>
>     Thanks for your comments. I have updated the document [1] with your comment. Feel free to let me know if you I have not addressed them appropriately.
>
>     We committed in Chicago to have the document ready before next meeting. I believe we are close to finalizing the document. I suggest the following planning: collecting comments by Friday April 28 so we make the document ready for WGLC next week.
>
>     Things we need to clarify before publishing version05:
>
>      - 1) Is the Home network use case described in the document better fit a inter-domain use case or an intra-domain use case. The reason I considered it rather a intra-domain is that I am considering that the ISP has an advantage of having the detection within a CPE, and in the use case we considered that the CPE is partly administrated by the ISP. The reason it might also be considered as an inter-domain use case is that the Home network may also ask the ISP to perform the DDoS mitigation.
>
>     I think it worth being discussed, I am fine having the use case in the inter-domain as well.
>
>     - 2 ) add a figure for the orchetsrator use case.
>
>     [1] https://github.com/dotswg/dots-use-cases/pull/1/commits/e7926b46640fb673e992d51598400caea22eb1e1
>
>     On Thu, Apr 6, 2017 at 8:17 AM, Teague, Nik <nteague@verisign.com <mailto:nteague@verisign.com>> wrote:
>
>
>         On 06/04/2017, 09:52, "mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com>" <mohamed.boucadair@orange.com <mailto:mohamed.boucadair@orange.com>> wrote:
>
>         Hi Daniel, all,
>
>         Attached my review of this version of the use case draft, fwiw.
>
>         Cheers,
>         Med
>
>         Thanks! – your review is much appreciated.
>
>         -Nik
>
>
>
>
>
>
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots