[Dots] Call Home: use cases

<mohamed.boucadair@orange.com> Thu, 28 March 2019 10:50 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dots@ietfa.amsl.com
Delivered-To: dots@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 2A5E3120251 for <dots@ietfa.amsl.com>; Thu, 28 Mar 2019 03:50:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id f4cm9S7_vAbW for <dots@ietfa.amsl.com>; Thu, 28 Mar 2019 03:50:38 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.orange.com []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A3DAC12027F for <dots@ietf.org>; Thu, 28 Mar 2019 03:50:37 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar27.francetelecom.fr (ESMTP service) with ESMTP id 44VM8r0LrCz2xbQ for <dots@ietf.org>; Thu, 28 Mar 2019 11:50:36 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.82]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 44VM8q5xGtzBrLf for <dots@ietf.org>; Thu, 28 Mar 2019 11:50:35 +0100 (CET)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM5E.corporate.adroot.infra.ftgroup ([fe80::849f:f804:b713:d99a%21]) with mapi id 14.03.0439.000; Thu, 28 Mar 2019 11:50:35 +0100
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>
Thread-Topic: Call Home: use cases
Thread-Index: AdTlVBC2f+Kq2pp7T/ew+qPWxoRG/g==
Date: Thu, 28 Mar 2019 10:50:34 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA4EACA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B93302EA4EACAOPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/mlzmj7x-_YRwwZAwHLJMKU7Glig>
Subject: [Dots] Call Home: use cases
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: Thu, 28 Mar 2019 10:50:41 -0000


FWIW, to the comment about the applicability of the solution, I'd like to clarify that the I-D states the following:


1.3. Scope

   The aforementioned problems may be encountered in other deployments

   than those discussed Section 1.1<https://tools.ietf.org/html/draft-reddy-dots-home-network-03#section-1.1>.  The solution proposed in this

   document can be used for those deployments to block DDoS attack

   traffic closer to the source(s) of the attack.