Re: [Dots] Unique use cases

kaname nishizuka <kaname@nttv6.jp> Fri, 01 April 2016 04:56 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 F16C512D0E6 for <dots@ietfa.amsl.com>; Thu, 31 Mar 2016 21:56:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.912
X-Spam-Level:
X-Spam-Status: No, score=-1.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 CZaDwkELhF2g for <dots@ietfa.amsl.com>; Thu, 31 Mar 2016 21:55:58 -0700 (PDT)
Received: from guri.nttv6.jp (guri.nttv6.jp [IPv6:2402:c800:ff06:a::4]) by ietfa.amsl.com (Postfix) with ESMTP id 7F4EC12D0CE for <dots@ietf.org>; Thu, 31 Mar 2016 21:55:58 -0700 (PDT)
Received: from z.nttv6.jp (z.nttv6.jp [192.168.8.15]) by guri.nttv6.jp (NTTv6MTA) with ESMTP id 800854E971; Fri, 1 Apr 2016 13:55:57 +0900 (JST)
Received: from SR2-nishizuka.local (fujiko.nttv6.jp [IPv6:2402:c800:ff06:136::141]) by z.nttv6.jp (NTTv6MTA) with ESMTP id 3EEFD3ACA8; Fri, 1 Apr 2016 13:55:57 +0900 (JST)
To: "Roman D. Danyliw" <rdd@cert.org>, Roland Dobbins <rdobbins@arbor.net>, "dots@ietf.org" <dots@ietf.org>
References: <359EC4B99E040048A7131E0F4E113AFCD96F75B8@marathon> <794C446F-DDB2-4583-A9A9-7ACE67C0192A@arbor.net> <359EC4B99E040048A7131E0F4E113AFCD96F992C@marathon>
From: kaname nishizuka <kaname@nttv6.jp>
Message-ID: <56FDFF5D.8080808@nttv6.jp>
Date: Fri, 01 Apr 2016 13:55:57 +0900
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.7.0
MIME-Version: 1.0
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD96F992C@marathon>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/8U_cLI98jw6V2ALhMl1EUTg19OM>
Subject: Re: [Dots] Unique use cases
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.17
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, 01 Apr 2016 04:56:01 -0000

Hi Roman,

The questions are related to my draft.
Sorry for my late reply, I added comments inline.

On 2016/04/01 4:25, Roman D. Danyliw wrote:
> Hi Roland!
>
> (chair hat off)
>> -----Original Message-----
>> From: Dots [mailto:dots-bounces@ietf.org] On Behalf Of Roland Dobbins
>> Sent: Wednesday, March 30, 2016 8:05 AM
>> To: dots@ietf.org
>> Subject: Re: [Dots] Unique use cases
>>
>> On 30 Mar 2016, at 5:30, Roman D. Danyliw wrote:
> [snip]
>
>>> (1) What's the difference between [WG-UC]'s [WG-UC]-2, 3, 4, 5 and 6
>>> beyond the kind of device acting as the DOTS client?  The write-ups
>>> are nearly identical.
>> That's the point - to illustrate that different types of devices/applications can
>> participate in DOTS, and that all the other differences are largely irrelevant to
>> the actual requirements of DOTS, and that DOTS has universal applicability.
> I agree on the intent.  IMHO, by repeating the text so many times, this universal applicability and common behavior regardless of device got lost.
>
> [snip]
>>> (2) What's the difference between [ID-UC]'s [UD-UC]-1 (Section 4.1.1)
>>> and 2 (Section 4.1.2); and [WG-UC]-1, 2, 3, 4, 5 and 6?
>> There is no Section 4.1.1 nor Section 4.1.2 in draft-ietf-dots-use-cases-01,
>> IIRC?
> The cited section numbers were for draft-nishizuka-dots-inter-domain-usecases-01 [aka, ID-UC].  I didn't cite the section numbers for draft-ietf-dots-use-cases-01 [aka, WG-UC].
>
>>> (3) What's the difference between [ID-UC]'s [ID-UC]-3 (Section 4.2.1)
>>> and [ID-UC]-4 (Section 4.2.2); and [IDC-UC]-1 (Section 3.1)?
>> Are you asking about the delta between the specific use cases in the two
>> draft versions?
> Ignoring, draft-ietf-dots-use-cases-01, I was trying to understand the difference between use cases #3 and 4 in Section 4.2.1/4.2.2 in draft-nishizuka-dots-inter-domain-usecases-01 [aka, ID-UC]; relative to use case #1 in Section 3.1 of draft-nishizuka-dots-inter-domain-mechanism-00 [aka, IDC-UC].  Are the former two use cases the same as the latter?
>
First, [ID-UC]-4,5 is intended to be identical with [IDC-UC]-1,2. (related to (4)): [ID-UC]-4 == [IDC-UC]-1, [ID-UC]-5 == [IDC-UC]-2.

[ID-UC]-4 (Mutual delegation) is a combination of [ID-UC]-3(delegation model), however, they have a slight difference.
The uniqueness of [ID-UC]-4 is that they utilize the DDoS protection system each other. Hence, it causes a coordination problem like how to determine the range of the protection they cover.



>>> (4) [ID-UC]-5 and [IDC-UC]-2 appear to be acknowledged as the same use
>>> case in Section 4.2.3 of [ID-UC].  Is that correct?
>> Unfortunately, I'm very confused by all the new acronyms and reliance on
>> numbers which don't actually appear in the documents - there is no Section
>> 4.2.3 in draft-ietf-dots-use-cases-01.  Can you provide more context?
>> Apologies for my confusion!
> Sorry for the confusion.  Let me expand my notation for clarity ...
>
> Use case #5 in Section 4.2.3 of draft-nishizuka-dots-inter-domain-usecases-01 [aka, ID-UC] appears to state that it is identical to use case #2 in Section 3.2 of draft-nishizuka-dots-inter-domain-mechanism-00 [aka, IDC-UC].  Is that correct?
yes, it's correct.

thank you,
kaname
> Roman
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots