[Dots] TR: New Version Notification for draft-reddy-dots-home-network-02.txt

<mohamed.boucadair@orange.com> Tue, 13 November 2018 14:37 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 577D412F1A6 for <dots@ietfa.amsl.com>; Tue, 13 Nov 2018 06:37:33 -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 wC0-aAl5lAgY for <dots@ietfa.amsl.com>; Tue, 13 Nov 2018 06:37:31 -0800 (PST)
Received: from orange.com (mta240.mail.business.static.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 82351127332 for <dots@ietf.org>; Tue, 13 Nov 2018 06:37:31 -0800 (PST)
Received: from opfedar07.francetelecom.fr (unknown [xx.xx.xx.9]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 42vVZx4sJFz7vP8; Tue, 13 Nov 2018 15:37:29 +0100 (CET)
Received: from Exchangemail-eme2.itn.ftgroup (unknown [xx.xx.31.17]) by opfedar07.francetelecom.fr (ESMTP service) with ESMTP id 42vVZx3l3lz5vN0; Tue, 13 Nov 2018 15:37:29 +0100 (CET)
Received: from OPEXCLILMA3.corporate.adroot.infra.ftgroup ([fe80::60a9:abc3:86e6:2541]) by OPEXCLILM24.corporate.adroot.infra.ftgroup ([fe80::a1e6:3e6a:1f68:5f7e%18]) with mapi id 14.03.0415.000; Tue, 13 Nov 2018 15:37:29 +0100
From: mohamed.boucadair@orange.com
To: Roman Danyliw <rdd@cert.org>, "Xialiang (Frank, Network Integration Technology Research Dept)" <frank.xialiang@huawei.com>, "Panwei (William) (william.panwei@huawei.com)" <william.panwei@huawei.com>
CC: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: New Version Notification for draft-reddy-dots-home-network-02.txt
Thread-Index: AQHUe10kJSRMb+D/lkigQOVa0XsC5KVNw5qw
Date: Tue, 13 Nov 2018 14:37:29 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302E045230@OPEXCLILMA3.corporate.adroot.infra.ftgroup>
References: <154211930418.26992.12586161888366921.idtracker@ietfa.amsl.com>
In-Reply-To: <154211930418.26992.12586161888366921.idtracker@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.4]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/9XFOsfzQRs4YPdkk_ulVNjXVljI>
Subject: [Dots] TR: New Version Notification for draft-reddy-dots-home-network-02.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, 13 Nov 2018 14:37:33 -0000

Hi Roman, Franck, Wei, 

FYI, we released an updated version of the draft which integrates the comments you raised. The main changes are as follows: 

* Add a new privacy considerations section as suggested by Roman.
* Add a discussion on issues/fixes when an address sharing function is present between the DOTS client and server (Wei)
* Add some text to clarify that the DOTS server on the CPE is simple compared to the one on the provider side. Only a single DOTS session will be maintained (Franck).
* Further highlight that the solution is suitable for blocking attacks near the sources (I failed to get the name of the gentleman who raised this issue in the meeting).
* Add some text to clarify that DOTS servers do not blindly accept requests and that the solution does not aim to track or censor users (the comment was made by same gentleman as above).  

Please let us know if the new text addresses your concern. 

As usual, comments, suggestions, and questions are more than welcome.

Cheers,
Med

> -----Message d'origine-----
> De : internet-drafts@ietf.org [mailto:internet-drafts@ietf.org]
> Envoyé : mardi 13 novembre 2018 15:28
> À : Tirumaleswar Reddy; Joshi Harsha; Jon Shallow; Reddy K; BOUCADAIR Mohamed
> TGI/OLN
> Objet : New Version Notification for draft-reddy-dots-home-network-02.txt
> 
> 
> A new version of I-D, draft-reddy-dots-home-network-02.txt
> has been successfully submitted by Mohamed Boucadair and posted to the
> IETF repository.
> 
> Name:		draft-reddy-dots-home-network
> Revision:	02
> Title:		Denial-of-Service Open Threat Signaling (DOTS) Signal
> Channel Call Home
> Document date:	2018-11-12
> Group:		Individual Submission
> Pages:		17
> URL:            https://www.ietf.org/internet-drafts/draft-reddy-dots-home-
> network-02.txt
> Status:         https://datatracker.ietf.org/doc/draft-reddy-dots-home-
> network/
> Htmlized:       https://tools.ietf.org/html/draft-reddy-dots-home-network-02
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-reddy-dots-home-
> network
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-reddy-dots-home-
> network-02
> 
> Abstract:
>    This document presents DOTS signal channel Call Home service, which
>    enables a DOTS server to initiate a secure connection to a DOTS
>    client, and to receive the attack traffic information from the DOTS
>    client.  The DOTS server in turn uses the attack traffic information
>    to identify the compromised devices launching the outgoing DDOS
>    attack and takes appropriate mitigation action.
> 
> 
> 
> 
> 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.
> 
> The IETF Secretariat