Re: [Dots] I-D Action: draft-ietf-dots-signal-channel-36.txt

<mohamed.boucadair@orange.com> Wed, 24 July 2019 09:07 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 1673D120124 for <dots@ietfa.amsl.com>; Wed, 24 Jul 2019 02:07:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 LyFE4dQWy3OP for <dots@ietfa.amsl.com>; Wed, 24 Jul 2019 02:07:51 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.41]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 40BA6120114 for <dots@ietf.org>; Wed, 24 Jul 2019 02:07:51 -0700 (PDT)
Received: from opfedar04.francetelecom.fr (unknown [xx.xx.xx.6]) by opfedar22.francetelecom.fr (ESMTP service) with ESMTP id 45tqHn5NRjz2xQ1 for <dots@ietf.org>; Wed, 24 Jul 2019 11:07:49 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.101]) by opfedar04.francetelecom.fr (ESMTP service) with ESMTP id 45tqHn4Ygzz1xnn for <dots@ietf.org>; Wed, 24 Jul 2019 11:07:49 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM6F.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Wed, 24 Jul 2019 11:07:49 +0200
From: <mohamed.boucadair@orange.com>
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] I-D Action: draft-ietf-dots-signal-channel-36.txt
Thread-Index: AQHVQf3vMnDEssovZUSWprMYlNzF7qbZeQ3w
Date: Wed, 24 Jul 2019 09:07:49 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330312E718E@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <156395868830.14494.2780998194145188435@ietfa.amsl.com>
In-Reply-To: <156395868830.14494.2780998194145188435@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.114.13.245]
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/5dGru-hdqGW6ObqqAtaOXscLy5Y>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-channel-36.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: Wed, 24 Jul 2019 09:07:54 -0000

Hi all, 

This version includes changes to clarify some points raised in recent threads, mainly:

(1) Add text to recall that the retransmission parameters do not apply for TCP. This addresses a comment from Valery.
(2) Add examples to illustrate the flexibility of the retry configuration offered by the protocol. This is intended to clarify a comment raised by Ben. 

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de internet-
> drafts@ietf.org
> Envoyé : mercredi 24 juillet 2019 10:58
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : [Dots] I-D Action: draft-ietf-dots-signal-channel-36.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-36.txt
> 	Pages           : 106
> 	Date            : 2019-07-24
> 
> 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/TBD1/TBD2 statements with the assignments made by
>    IANA 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-36
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-channel-36
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-channel-36
> 
> 
> 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