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 05:51 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 6AB7612DFC8 for <dots@ietfa.amsl.com>; Thu, 10 Mar 2016 21:51:37 -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 jQpedv5_yxjT for <dots@ietfa.amsl.com>; Thu, 10 Mar 2016 21:51:36 -0800 (PST)
Received: from mail-pa0-x22a.google.com (mail-pa0-x22a.google.com [IPv6:2607:f8b0:400e:c03::22a]) (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 184EE12D508 for <dots@ietf.org>; Thu, 10 Mar 2016 21:51:36 -0800 (PST)
Received: by mail-pa0-x22a.google.com with SMTP id fe3so69619805pab.1 for <dots@ietf.org>; Thu, 10 Mar 2016 21:51:36 -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=vDlcdfwDRaIuGeFEbcC3OmV4EOcjdtjiU+sK9ZMuqrc=; b=GD2xa3lZMPwZ2hG97TIkrbayc9sxr5sC8op+4MQQhBwY+81e1GFXkPmiQ7a/XKlsLS SYQlMj7i7wU6ZLdvBy4yId70qHKuftA/fd5ek2P2bhf1SpaOeh/P/konWymX0tnJR1ng OQeZemcxq9WOA4J5OaQzuAm152BeJE7GqPQ8M=
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=vDlcdfwDRaIuGeFEbcC3OmV4EOcjdtjiU+sK9ZMuqrc=; b=YtwE/txHcxUcGiIA5Zsk9/jy2GXZiF9pDvCyVgxM9inPED4iqMo8p2RUytMV2Iqfje G2jO/f8Wu5XIyF2dvdcCZfqx+ebRYf/gHN3fYVX91Q2NaBKYOFGOP9j41lYFvTqIXcUR zS8SX/OEevTXJtLK976bnx9S47ejnGfisbNgXhebSN7eNmOMnuZ9NsFQZl1iOdcNfQQy R2dV9bi1ufpwdCjn0EN8H8bCBeY0m7XDd/JdgFKzebfCw8Y5LQum69qgMy0FWihh0Gce u0drjq9twQ6g/8EffT/VdIHOVgwtp0zuOIQG4hL2YweTmUXrsSD2UFKeKwOkR4icabZg /C0Q==
X-Gm-Message-State: AD7BkJLS8HHqZwCVN1gRXmExcshE+n3VtUi4UPyKmBIJASxD66cgsRtBnXav2GKgVBd/ndhS
X-Received: by 10.66.140.14 with SMTP id rc14mr11184507pab.65.1457675495674; Thu, 10 Mar 2016 21:51:35 -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 17sm9523895pfp.96.2016.03.10.21.51.33 for <dots@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 10 Mar 2016 21:51:34 -0800 (PST)
From: Roland Dobbins <rdobbins@arbor.net>
To: "dots@ietf.org" <dots@ietf.org>
Date: Fri, 11 Mar 2016 12:51:28 +0700
Message-ID: <C085D587-0959-45EF-8D60-C870A1A5AE13@arbor.net>
In-Reply-To: <C02846B1344F344EB4FAA6FA7AF481F12AEF99C0@SZXEMA502-MBS.china.huawei.com>
References: <20160219143213.18440.22155.idtracker@ietfa.amsl.com> <56C729D0.2080707@nttv6.jp> <359EC4B99E040048A7131E0F4E113AFCD96E1534@marathon> <C02846B1344F344EB4FAA6FA7AF481F12AEF923E@SZXEMA502-MBS.china.huawei.com> <359EC4B99E040048A7131E0F4E113AFCD96E3836@marathon> <C02846B1344F344EB4FAA6FA7AF481F12AEF99C0@SZXEMA502-MBS.china.huawei.com>
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/BBI4l86z0kFKeDt0K3_94-4ckow>
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 05:51:37 -0000

On 11 Mar 2016, at 12:41, Xialiang (Frank) wrote:

> [Frank]: I mean both. I hope we can include this part of work in DOTS 
> WG.

We can refer to it in deployment examples, but not prescribe it.

> [Frank]: Good question. In general, one ISP can have multiple DOTS 
> systems to be responsible for its multiple domains respectively. It 
> can relieve the traffic pressure to one DOTS system in the ISP 
> network, and provide the optimized near-source mitigation in certain 
> level. I also think different deployment ways as you mentioned above 
> can work in various occasions. 1:1 coupling of server/client in the 
> orchestrator is now a simple model but is enough for most occasions. I 
> think the orchestrator should be an additional element for the DOTS 
> architecture.

Once again, this is something to which we can refer in deployment 
models, but not prescribe.

The purpose of this WG is to design a communications protocol that will 
be useful in most any DDoS mitigation scenario, not to prescribe 
elements beyond those required for the communications protocol itself to 
function (e.g., client, relay, server).

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