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

"Roland Dobbins" <rdobbins@arbor.net> Fri, 19 February 2016 17:03 UTC

Return-Path: <rdobbins@arbor.net>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F7701B3269 for <dots@ietfa.amsl.com>; Fri, 19 Feb 2016 09:03:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham
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 LppnLA_rIpwA for <dots@ietfa.amsl.com>; Fri, 19 Feb 2016 09:03:21 -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 B9E6D1AC3F0 for <dots@ietf.org>; Fri, 19 Feb 2016 09:03:21 -0800 (PST)
Received: by mail-pa0-x22a.google.com with SMTP id fl4so53289131pad.0 for <dots@ietf.org>; Fri, 19 Feb 2016 09:03:21 -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 :content-type; bh=NCAx/8L811HRfAN7xYBTwAqv9bwePi6zLSB/TroG9lI=; b=aolKytjE+is9jDOWU2gp95MEz7t0rROIRaXNvUKf32XQXI/02dUFi8Q7uvCp8HJRLd yBwjN+sB+8YDUUTJw8w/hBKy+OsS88J/6y4oU9k9XuaC7fwbdZ7fHT1W003VyzI/yux8 2Wx6ex3pXS3gPdXoszNJ6S8GfBC2IiaBbLMY4=
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:content-type; bh=NCAx/8L811HRfAN7xYBTwAqv9bwePi6zLSB/TroG9lI=; b=kKj+8sBAohUVLKOgC/hCNdKjCgsVPhEZgOk6SpXFF9Y61PFl2btK1HxqKDux+sds7M oub0c19y4G5vJQJBnb8PdiccoR6QBT4Pc9lrvG+6utLGfvT96E6BWGZaKHVc2feeCHAT fqvXIoLBQbzZp27lAhAfcovB0P0Fz83xslD5bA5fZTUrTVyq3v2UvLba/Aid4vH7ceHn a8W+PfNVYoC8F0h3+qVacCpIb5x/AJtLn4Hx+oMcbtGz41UPsZYqlYWpffwo6gfcWhFL wX8/lUbBfoQww6ja+/J6LwiilBCfioZRsO38vLLqxykZSn6YeAzA/Df0zknMbRLDLgiK bPVg==
X-Gm-Message-State: AG10YOTWuULsZnGfnqOU/eLu2Ubb70LZn7A/v6G/6l7GsU/OHDH0ONJj5SpJ8zzlV0TVvlat
X-Received: by 10.66.248.168 with SMTP id yn8mr19635109pac.24.1455901401370; Fri, 19 Feb 2016 09:03:21 -0800 (PST)
Received: from [172.19.254.138] (202-176-81-112.static.asianet.co.th. [202.176.81.112]) by smtp.gmail.com with ESMTPSA id xa9sm19110919pab.44.2016.02.19.09.03.19 for <dots@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Fri, 19 Feb 2016 09:03:20 -0800 (PST)
From: Roland Dobbins <rdobbins@arbor.net>
To: dots@ietf.org
Date: Sat, 20 Feb 2016 00:03:17 +0700
Message-ID: <34F87D2A-9BFB-4C57-B25C-2501FEB654AE@arbor.net>
In-Reply-To: <56C729D0.2080707@nttv6.jp>
References: <20160219143213.18440.22155.idtracker@ietfa.amsl.com> <56C729D0.2080707@nttv6.jp>
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"
X-Mailer: MailMate (1.9.4r5213)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/3g2RPDGnOWO2cswskCOBDPbyRs0>
Subject: Re: [Dots] New Version Notification for draft-nishizuka-dots-inter-domain-mechanism-00.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.15
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, 19 Feb 2016 17:03:27 -0000

On 19 Feb 2016, at 21:42, kaname nishizuka wrote:

> Any comments and suggestions are welcome.

This draft is partially or wholly duplicative of 
draft-ietf-dots-use-cases-00, draft-ietf-dots-requirements-00, and 
draft-reddy-dots-transport-02; it is overly prescriptive (e.g., talk 
about flow telemetry); premature (e.g., talk about JSON, certs, message 
formats, and so forth); incomplete (doesn't mention relays at all); and 
contains factually incorrect statements (e.g., that provisioning must 
take place prior to an attack; in point of fact, one of the rationales 
for DOTS is that it allows for dynamic registration and 
auto-provisioning even during an attack).

Have the submitters been following the discussions around the three 
drafts mentioned above?

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