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 06:41 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 2CDC612D51F for <dots@ietfa.amsl.com>; Thu, 10 Mar 2016 22:41:11 -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 mBQWlXeF1t7G for <dots@ietfa.amsl.com>; Thu, 10 Mar 2016 22:41:09 -0800 (PST)
Received: from mail-pa0-x233.google.com (mail-pa0-x233.google.com [IPv6:2607:f8b0:400e:c03::233]) (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 ADDD012D51A for <dots@ietf.org>; Thu, 10 Mar 2016 22:41:09 -0800 (PST)
Received: by mail-pa0-x233.google.com with SMTP id td3so60301840pab.2 for <dots@ietf.org>; Thu, 10 Mar 2016 22:41:09 -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=nUIFdFfBNH95ll/a+2LRpD6o7BR7T8BemWxRtwDtJbM=; b=eaD2Axp3jI691zJbb8xhObfyzX/a6y9vFvh+N+ghWieITHUcr/cG6OTsoW6fYdjLSW cdqPjpO0P4drOgr/qwz9GEuk9qAsQHvr62pmAb3AazPB4WpUHtNyDl59vBm1yYnF/X7H 5WY/zlmFOu8feEhFPyKLo7VRK5vSmfSqVdVWU=
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=nUIFdFfBNH95ll/a+2LRpD6o7BR7T8BemWxRtwDtJbM=; b=flUmf0h73g1aXlS65pW7Q393cLm51nn4si3g3IgXY8Ex+53lGWS+FPxWDbg36lCdj5 hCFzimPi/cR7u0OjYfUoO28b40/scfjipFYKx1p4CSI59rg+XMWYAsH/9/1tB6hRhx// dlkc1WkyVEb3HiqHpxnzN3FQmPzz07dKZEJ5LkWw5yq3fhNj0D44MAawreWop+6BMLQ6 gAvZ/Tvvknvx0hfr2GSZqdgbJqkXUPoASeLaoyd9TI8wKY7GP24DdSddgbWwK9hsXqQu 0NvFPIYU3r7RHxRSopLFGT6PdQU5xbbKAUgAEUTh5LWFirtnIT5BfwHkujkhxX/oUQZQ myNA==
X-Gm-Message-State: AD7BkJK+ZIZEfis2nybkExLTa5TWFhcZeoHZ5pKNVu4ZfEIjzA/NVdk0Iq1Uvhw3SlUxIClQ
X-Received: by 10.67.30.163 with SMTP id kf3mr11735148pad.45.1457678469292; Thu, 10 Mar 2016 22:41:09 -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 o7sm9970006pfa.37.2016.03.10.22.41.07 for <dots@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Thu, 10 Mar 2016 22:41:08 -0800 (PST)
From: Roland Dobbins <rdobbins@arbor.net>
To: "dots@ietf.org" <dots@ietf.org>
Date: Fri, 11 Mar 2016 13:41:05 +0700
Message-ID: <69193462-0AB3-448D-93DA-ABF31A869C59@arbor.net>
In-Reply-To: <C085D587-0959-45EF-8D60-C870A1A5AE13@arbor.net>
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> <C085D587-0959-45EF-8D60-C870A1A5AE13@arbor.net>
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/TdNbR-QjMNNXebHwTzyD74kU3d4>
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 06:41:11 -0000

On 11 Mar 2016, at 12:51, Roland Dobbins wrote:

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

To expand this point - an orchestrator can be a DOTS server, relay, 
client, or any combination thereof.

An orchestrator is not in and of itself a necessary or desirable element 
of DOTS.  DOTS must be usable in scenarios where orchestrators are 
present, as well as scenarios in which no orchestrators are involved.

This also applies to flow collectors/analyzers.  They can be DOTS 
servers, relays, clients, or any combination thereof.  They are not 
required elements of DOTS itself.

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

v2.23.0 | Report a Bug | By Email