Re: [Dots] I-D Action: draft-ietf-dots-data-channel-26.txt
<mohamed.boucadair@orange.com> Tue, 19 February 2019 08:12 UTC
Return-Path: <mohamed.boucadair@orange.com>
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 4AD5E124B0C for <dots@ietfa.amsl.com>; Tue, 19 Feb 2019 00:12:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 haHF6Aswj0nn for <dots@ietfa.amsl.com>; Tue, 19 Feb 2019 00:12:06 -0800 (PST)
Received: from orange.com (mta134.mail.business.static.orange.com [80.12.70.34]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F67D130E77 for <dots@ietf.org>; Tue, 19 Feb 2019 00:12:06 -0800 (PST)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr27.francetelecom.fr (ESMTP service) with ESMTP id 443YP050tcz4wxJ; Tue, 19 Feb 2019 09:12:04 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.60]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 443YP04HgJzDq82; Tue, 19 Feb 2019 09:12:04 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM5D.corporate.adroot.infra.ftgroup ([fe80::8899:bbc3:9726:cd5e%22]) with mapi id 14.03.0435.000; Tue, 19 Feb 2019 09:12:04 +0100
From: mohamed.boucadair@orange.com
To: kaname nishizuka <kaname@nttv6.jp>, "Benjamin Kaduk (kaduk@mit.edu)" <kaduk@mit.edu>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-data-channel-26.txt
Thread-Index: AQHUyCkQ29sbJMsplkyd3xdE3asfnaXmxBNQ
Date: Tue, 19 Feb 2019 08:12:03 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA21AFA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <155049459642.5615.1531443959140669891@ietfa.amsl.com> <787AE7BB302AE849A7480A190F8B93302EA20FD1@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <0423e4f1-41be-a924-3c51-3d20977b7eae@nttv6.jp>
In-Reply-To: <0423e4f1-41be-a924-3c51-3d20977b7eae@nttv6.jp>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.114.13.247]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/yFa6RHOowRMAaRMNEREkuBLgMDQ>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-data-channel-26.txt
X-BeenThere: dots@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 19 Feb 2019 08:12:13 -0000
Hi Kaname, FWIW, the main changes are the following: * use error-app-tag instead of defining a new error-tag. * describe the behavior when multiple target-* scope types are included in the same request. The structure of the YANG module is the same; only some reordering of some nodes. Cheers, Med > -----Message d'origine----- > De : kaname nishizuka [mailto:kaname@nttv6.jp] > Envoyé : mardi 19 février 2019 09:00 > À : BOUCADAIR Mohamed TGI/OLN; Benjamin Kaduk (kaduk@mit.edu) dots@ietf.org > Objet : Re: [Dots] I-D Action: draft-ietf-dots-data-channel-26.txt > > Hi, > > The revised text is more precise. Thanks for your careful work. > I'll check if our implementation is compatible with the specified types and > behavior. > > thanks, > Kaname > > > On 2019/02/18 22:06, mohamed.boucadair@orange.com wrote: > > Hi Ben, all, > > > > This version addresses the comments from the AD review. > > > > A diff to track the changes is available at: > > https://www.ietf.org/rfcdiff?url1=draft-ietf-dots-data-channel- > 25&url2=draft-ietf-dots-data-channel-26&difftype=--hwdiff > > > > Cheers, > > Med > > > >> -----Message d'origine----- > >> De : I-D-Announce [mailto:i-d-announce-bounces@ietf.org] De la part de > >> internet-drafts@ietf.org > >> Envoyé : lundi 18 février 2019 13:57 > >> À : i-d-announce@ietf.org > >> Cc : dots@ietf.org > >> Objet : I-D Action: draft-ietf-dots-data-channel-26.txt > >> > >> > >> A New Internet-Draft is available from the on-line Internet-Drafts > >> directories. > >> This draft is a work item of the DDoS Open Threat Signaling WG of the > IETF. > >> > >> Title : Distributed Denial-of-Service Open Threat > Signaling > >> (DOTS) Data Channel Specification > >> Authors : Mohamed Boucadair > >> Tirumaleswar Reddy > >> Filename : draft-ietf-dots-data-channel-26.txt > >> Pages : 70 > >> Date : 2019-02-18 > >> > >> Abstract: > >> The document specifies a Distributed Denial-of-Service Open Threat > >> Signaling (DOTS) data channel used for bulk exchange of data that > >> cannot easily or appropriately communicated through the DOTS signal > >> channel under attack conditions. > >> > >> This is a companion document to the DOTS signal channel > >> specification. > >> > >> Editorial Note (To be removed by RFC Editor) > >> > >> Please update these statements within the document with the RFC > >> number to be assigned to this document: > >> > >> o "This version of this YANG module is part of RFC XXXX;" > >> > >> o "RFC XXXX: Distributed Denial-of-Service Open Threat Signaling > >> (DOTS) Data Channel Specification"; > >> > >> o reference: RFC XXXX > >> > >> Please update the "revision" date of the YANG module. > >> > >> > >> The IETF datatracker status page for this draft is: > >> https://datatracker.ietf.org/doc/draft-ietf-dots-data-channel/ > >> > >> There are also htmlized versions available at: > >> https://tools.ietf.org/html/draft-ietf-dots-data-channel-26 > >> https://datatracker.ietf.org/doc/html/draft-ietf-dots-data-channel-26 > >> > >> A diff from the previous version is available at: > >> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-data-channel-26 > >> > >> > >> Please note that it may take a couple of minutes from the time of > submission > >> until the htmlized version and diff are available at tools.ietf.org. > >> > >> Internet-Drafts are also available by anonymous FTP at: > >> ftp://ftp.ietf.org/internet-drafts/ > >> > >> _______________________________________________ > >> I-D-Announce mailing list > >> I-D-Announce@ietf.org > >> https://www.ietf.org/mailman/listinfo/i-d-announce > >> Internet-Draft directories: http://www.ietf.org/shadow.html > >> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt > > _______________________________________________ > > Dots mailing list > > Dots@ietf.org > > https://www.ietf.org/mailman/listinfo/dots
- [Dots] I-D Action: draft-ietf-dots-data-channel-2… internet-drafts
- Re: [Dots] I-D Action: draft-ietf-dots-data-chann… mohamed.boucadair
- Re: [Dots] I-D Action: draft-ietf-dots-data-chann… kaname nishizuka
- Re: [Dots] I-D Action: draft-ietf-dots-data-chann… mohamed.boucadair
- Re: [Dots] I-D Action: draft-ietf-dots-data-chann… kaname nishizuka