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

Kristian Larsson <kristian@spritelink.net> Wed, 09 March 2016 14:21 UTC

Return-Path: <kristian@spritelink.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 6F07F12D6B2 for <dots@ietfa.amsl.com>; Wed, 9 Mar 2016 06:21:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 31IodKzveQJg for <dots@ietfa.amsl.com>; Wed, 9 Mar 2016 06:21:41 -0800 (PST)
Received: from Mail2.SpriteLink.NET (Mail2.SpriteLink.NET [195.182.5.83]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C22FD12DEB3 for <dots@ietf.org>; Wed, 9 Mar 2016 06:21:29 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by Mail2.SpriteLink.NET (Postfix) with ESMTP id 52B68261848 for <dots@ietf.org>; Wed, 9 Mar 2016 15:21:28 +0100 (CET)
X-Virus-Scanned: amavisd-new at SpriteLink.NET
Received: from Mail2.SpriteLink.NET ([195.182.5.83]) by localhost (Mail2.SpriteLink.NET [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sQx5jFGBztkU for <dots@ietf.org>; Wed, 9 Mar 2016 15:21:25 +0100 (CET)
Received: from 195-20-206-74.serverhotell.net (unknown [195.20.206.74]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: kristian@spritelink.net) by Mail2.SpriteLink.NET (Postfix) with ESMTPSA id E74A4261846 for <dots@ietf.org>; Wed, 9 Mar 2016 15:21:24 +0100 (CET)
To: dots@ietf.org
References: <20160219143213.18440.22155.idtracker@ietfa.amsl.com> <56C729D0.2080707@nttv6.jp> <CALgsdbdZ1pFZHwMXj3hMBAv+zchkcCjBJHrf-P4FXu7ORu148Q@mail.gmail.com>
From: Kristian Larsson <kristian@spritelink.net>
Message-ID: <56E03164.3030702@spritelink.net>
Date: Wed, 09 Mar 2016 15:21:24 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
In-Reply-To: <CALgsdbdZ1pFZHwMXj3hMBAv+zchkcCjBJHrf-P4FXu7ORu148Q@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dots/Ycat_AHOoQ-MY5PIZhd8KAAzyjY>
Subject: Re: [Dots] 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: Wed, 09 Mar 2016 14:21:44 -0000

I wonder, have we discussed using YANG to model the messages/RPCs? I'm 
not sure why I haven't brought this up earlier, but it sure would be 
nice to reuse the most popular modelling language IETF has at its disposal.

And just to be clear, I'm not implying a particular transport like 
NETCONF or RESTCONF. Obviously we have very specific requirements in 
there so one might have to invent something new but I don't think this 
prevents using YANG to describe the message content.

Kind regards,
    Kristian.



On 09/03/16 15:04, Pavel Odintsov wrote:
> Hello!
>
> You have done nice work! I really love json from developer point of
> view. We definitely will integrate this draft protocol as proof of
> concept into our DDoS mitigation solution.
>
> Do you have reference implementations or some code?
>
> On Fri, Feb 19, 2016 at 5:42 PM, kaname nishizuka <kaname@nttv6.jp
> <mailto:kaname@nttv6.jp>> wrote:
>
>     Hi all,
>
>     We submitted a new draft regarding to a cooperative DDoS protection.
>
>     Summary of the draft:
>         As DDoS attack evolves rapidly in the aspect of volume and
>         sophistication, cooperation among operators for sharing the capacity
>         of the protection system to cope with it becomes very necessary.
>         This document describes some possible solutions to the cooperative
>         DDoS protection problems.
>         The inter-domain protocol (or signaling mechanism) for the goal of
>         DDoS protection coordination is the main focus of this document.
>
>     We're all happy to have discussions. Any comments and suggestions
>     are welcome.
>
>     thanks in advance,
>     kaname
>
>
>     -------- Forwarded Message --------
>     Subject: 	New Version Notification for
>     draft-nishizuka-dots-inter-domain-mechanism-00.txt
>     Date: 	Fri, 19 Feb 2016 06:32:13 -0800
>     From: 	internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>     To: 	Luyuan Fang <lufang@microsoft.com>
>     <mailto:lufang@microsoft.com>, Kaname Nishizuka <kaname@nttv6.jp>
>     <mailto:kaname@nttv6.jp>, Jinwei Xia <xiajinwei@huawei.com>
>     <mailto:xiajinwei@huawei.com>, Dacheng Zhang
>     <dacheng.zdc@aliabab-inc.com> <mailto:dacheng.zdc@aliabab-inc.com>,
>     Liang Xia <frank.xialiang@huawei.com>
>     <mailto:frank.xialiang@huawei.com>
>
>
>
>     A new version of I-D, draft-nishizuka-dots-inter-domain-mechanism-00.txt
>     has been successfully submitted by Kaname Nishizuka and posted to the
>     IETF repository.
>
>     Name:		draft-nishizuka-dots-inter-domain-mechanism
>     Revision:	00
>     Title:		Inter-domain cooperative DDoS protection problems and mechanism
>     Document date:	2016-02-19
>     Group:		Individual Submission
>     Pages:		22
>     URL:https://www.ietf.org/internet-drafts/draft-nishizuka-dots-inter-domain-mechanism-00.txt
>     Status:https://datatracker.ietf.org/doc/draft-nishizuka-dots-inter-domain-mechanism/
>     Htmlized:https://tools.ietf.org/html/draft-nishizuka-dots-inter-domain-mechanism-00
>
>
>     Abstract:
>         As DDoS attack evolves rapidly in the aspect of volume and
>         sophistication, cooperation among operators for sharing the capacity
>         of the protection system to cope with it becomes very necessary.
>         This document describes some possible solutions to the cooperative
>         inter-domain DOTS problems.
>
>
>
>
>     Please note that it may take a couple of minutes from the time of submission
>     until the htmlized version and diff are available attools.ietf.org <http://tools.ietf.org>.
>
>     The IETF Secretariat
>
>
>
>
>     _______________________________________________
>     Dots mailing list
>     Dots@ietf.org <mailto:Dots@ietf.org>
>     https://www.ietf.org/mailman/listinfo/dots
>
>
>
>
> --
> Sincerely yours, Pavel Odintsov
>
>
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots
>