Re: [Dots] I-D Action: draft-ietf-dots-signal-channel-26.txt
<mohamed.boucadair@orange.com> Fri, 21 December 2018 15:25 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 D50CC128AFB for <dots@ietfa.amsl.com>; Fri, 21 Dec 2018 07:25:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 jcexe0KYi7GU for <dots@ietfa.amsl.com>; Fri, 21 Dec 2018 07:25:07 -0800 (PST)
Received: from orange.com (mta136.mail.business.static.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 062AC1274D0 for <dots@ietf.org>; Fri, 21 Dec 2018 07:25:07 -0800 (PST)
Received: from opfednr07.francetelecom.fr (unknown [xx.xx.xx.71]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 43LsrK4GPKz21ST for <dots@ietf.org>; Fri, 21 Dec 2018 16:25:05 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.32]) by opfednr07.francetelecom.fr (ESMTP service) with ESMTP id 43LsrK3XMjzFpWb for <dots@ietf.org>; Fri, 21 Dec 2018 16:25:05 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM32.corporate.adroot.infra.ftgroup ([fe80::8924:188:2124:a046%19]) with mapi id 14.03.0415.000; Fri, 21 Dec 2018 16:25:05 +0100
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-signal-channel-26.txt
Thread-Index: AQHUmT9GVGHhf+IlTkmyyKtxZX5dUqWJTCPA
Date: Fri, 21 Dec 2018 15:25:05 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302E05F1A5@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <154540499981.20288.7115619272692249566@ietfa.amsl.com>
In-Reply-To: <154540499981.20288.7115619272692249566@ietfa.amsl.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.168.234.6]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/kRcUO7rnfTeNWEm4u-s03I8asAw>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-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: Fri, 21 Dec 2018 15:25:09 -0000
Re-, This version reflects some of the outcomes of the discussion related to the requirements and architecture I-Ds: * Abandon white/black-* terms * Remove the use of versions Also, this version integrates some early comments received from Ben: * DOTS session is not replaced with DOTS signal channel session for consistency. The definition of DOTS signal channel session is added to the architecture I-D. * Clarify that the examples are using JSON notation As discussed in the context of draft-reddy-dots-home-network, we updated the IANA section with sub-registries to maintain codes/parameters that are used by the protocol. Ben, the source files are available at: https://github.com/boucadair/draft-ietf-dots-signal-channel Cheers, Med > -----Message d'origine----- > De : Dots [mailto:dots-bounces@ietf.org] De la part de internet- > drafts@ietf.org > Envoyé : vendredi 21 décembre 2018 16:10 > À : i-d-announce@ietf.org > Cc : dots@ietf.org > Objet : [Dots] I-D Action: draft-ietf-dots-signal-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) Signal Channel Specification > Authors : Tirumaleswar Reddy > Mohamed Boucadair > Prashanth Patil > Andrew Mortensen > Nik Teague > Filename : draft-ietf-dots-signal-channel-26.txt > Pages : 97 > Date : 2018-12-21 > > Abstract: > This document specifies the DOTS signal channel, a protocol for > signaling the need for protection against Distributed Denial-of- > Service (DDoS) attacks to a server capable of enabling network > traffic mitigation on behalf of the requesting client. > > A companion document defines the DOTS data channel, a separate > reliable communication layer for DOTS management and configuration > purposes. > > 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) Signal Channel Specification"; > > o "| [RFCXXXX] |" > > o reference: RFC XXXX > > Please update this statement with the RFC number to be assigned to > the following documents: > > o "RFC YYYY: Distributed Denial-of-Service Open Threat Signaling > (DOTS) Data Channel Specification (used to be > [I-D.ietf-dots-data-channel]) > > Please update TBD statements with the port number to be assigned to > DOTS Signal Channel Protocol. > > Also, please update the "revision" date of the YANG modules. > > > The IETF datatracker status page for this draft is: > https://datatracker.ietf.org/doc/draft-ietf-dots-signal-channel/ > > There are also htmlized versions available at: > https://tools.ietf.org/html/draft-ietf-dots-signal-channel-26 > https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-channel-26 > > A diff from the previous version is available at: > https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-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/ > > _______________________________________________ > Dots mailing list > Dots@ietf.org > https://www.ietf.org/mailman/listinfo/dots
- [Dots] I-D Action: draft-ietf-dots-signal-channel… internet-drafts
- Re: [Dots] I-D Action: draft-ietf-dots-signal-cha… mohamed.boucadair