IETF Logo Mail Archive

Re: [Dots] Re Fwd: New Version Notification for draft-nishizuka-dots-inter-domain-mechanism-00.txt

"Roland Dobbins" <rdobbins@arbor.net> Fri, 11 March 2016 03:48 UTC

Return-Path: <rdobbins@arbor.net>
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 5C78C12DFD5 for <dots@ietfa.amsl.com>; Thu, 10 Mar 2016 19:48:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=arbor.net
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 GLnYUr7h5Bhc for <dots@ietfa.amsl.com>; Thu, 10 Mar 2016 19:48:46 -0800 (PST)
Received: from mail-pf0-x232.google.com (mail-pf0-x232.google.com [IPv6:2607:f8b0:400e:c00::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 661D812DFD4 for <dots@ietf.org>; Thu, 10 Mar 2016 19:48:44 -0800 (PST)
Received: by mail-pf0-x232.google.com with SMTP id n5so46387029pfn.2 for <dots@ietf.org>; Thu, 10 Mar 2016 19:48:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=arbor.net; s=m0; h=from:to:subject:date:message-id:in-reply-to:references:mime-version; bh=rzNyoPUqc9n9ryS6WvqZGbGj1Hi4MjRYoZHo9PFCifM=; b=hEWjUPmCzrq9SW1mc4kHsKrV3OKjzrXM6S+4uQhGLdMk9rZxRNOodJSJP7tsoM/InS qJKcyjfx/L/8+ZWFu27+IvgYh2zv9QS6qmmllh5ktr796Ngvueu8M7h623zyAhOw0sT2 DYBEAummHRDcDH7KdKGu1EA05yuXpPtjwXKg8=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:date:message-id:in-reply-to :references:mime-version; bh=rzNyoPUqc9n9ryS6WvqZGbGj1Hi4MjRYoZHo9PFCifM=; b=GVsW6G2GhAi6ZjJmeEcteI3YBUN90FemSkabMVdcU+xN3rEehV7nlEefqBJqgKYEen O3ppFpxanpFnR2oJ+8wv03gZB6XQPdPVEjmt/f6A5Ki2W6uOtfYmuXSLRZ7ciwCiJY8Q tZrQ2+WbgUSeHml6IBj7oOmEOwPgRUUAGtAi/f83gBx71VUU9q1OeyQmZF3u834yr/YQ d5O+pxQah+pLA+504ERP+gzLeGxEpLIS9Aveu9gXmuI2Jk+tyANjjdXDasAkavqz4ez4 LRucfJopYLJrXAovsB7haNMeDMEIRXxNGXwhsUgduNvrl3ijv7R1V1+8qvZMq+QPMlEe ARrw==
X-Gm-Message-State: AD7BkJKhRBnR991qHq0JsjhqNkBVVi5wuB/y621tDBwLpeXdeKbqAfp0URCLa9Kl2vR3thH2
X-Received: by 10.98.14.68 with SMTP id w65mr10324745pfi.144.1457668123427; Thu, 10 Mar 2016 19:48:43 -0800 (PST)
Received: from [172.19.254.115] (202-176-81-112.static.asianet.co.th. [202.176.81.112]) by smtp.gmail.com with ESMTPSA id qy7sm8713371pab.34.2016.03.10.19.48.41 for <dots@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 10 Mar 2016 19:48:42 -0800 (PST)
From: Roland Dobbins <rdobbins@arbor.net>
To: "dots@ietf.org" <dots@ietf.org>
Date: Fri, 11 Mar 2016 10:48:38 +0700
Message-ID: <63E5D6FA-A71A-403E-8FAD-5E45A98C21B4@arbor.net>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFCD96E3836@marathon>
References: <20160219143213.18440.22155.idtracker@ietfa.amsl.com> <56C729D0.2080707@nttv6.jp> <359EC4B99E040048A7131E0F4E113AFCD96E1534@marathon> <C02846B1344F344EB4FAA6FA7AF481F12AEF923E@SZXEMA502-MBS.china.huawei.com> <359EC4B99E040048A7131E0F4E113AFCD96E3836@marathon>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.4r5226)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/kfkGAK2pISxz-DHySKRn453zJ2k>
Subject: Re: [Dots] Re Fwd: New Version Notification for draft-nishizuka-dots-inter-domain-mechanism-00.txt
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, 11 Mar 2016 03:48:49 -0000

On 11 Mar 2016, at 5:17, Roman D. Danyliw wrote:

> or that there is an additional element (flow analyzer?) in the DOTS 
> architecture (per the requirements draft) that needs to be described 
> (beyond a client, server, relay and mitigator).

No - this is just one particular detection/classification/traceback 
mechanism.  As we've discussed previously on this list and in WG 
meetings, the actual mechanisms utilized for 
detection/classification/traceback/mitigation are beyond the scope of 
this WG.

> Thanks for the clarification. In figure 1, why are there multiple DOTS 
> clients/servers in ISP 1?

There certainly could and most likely should be multiple DOTS clients, 
relays, and servers within any organization.

> Like noted above with the flow analyzer, in the view of the draft, is 
> the orchestrator is an additional element of the DOTS architecture?

Per the above, no - that is outside our remit.

-----------------------------------
Roland Dobbins <rdobbins@arbor.net>

v2.23.0 | Report a Bug | By Email