Re: [Dots] I-D Action: draft-ietf-dots-signal-call-home-09.txt

mohamed.boucadair@orange.com Tue, 15 September 2020 06:05 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 988D73A0EAC for <dots@ietfa.amsl.com>; Mon, 14 Sep 2020 23:05:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.118
X-Spam-Level:
X-Spam-Status: No, score=-2.118 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 t5UGnn1u9Cic for <dots@ietfa.amsl.com>; Mon, 14 Sep 2020 23:05:09 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 886373A0EA9 for <dots@ietf.org>; Mon, 14 Sep 2020 23:05:09 -0700 (PDT)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 4BrCPb6M6WzCrk8; Tue, 15 Sep 2020 08:05:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1600149907; bh=w8teIm+iRKfPdZnPwz7lXObRUsFEM2GvIcqKyp7mOnA=; h=From:To:Subject:Date:Message-ID:Content-Type: Content-Transfer-Encoding:MIME-Version; b=uZZKjzY+u3QmtnPsBmH6Ogr1RmNLrGPpwygBiDc/lVK/v0fXexa+mDz2sOiDM5T56 8jmkSjZgVq4Kiprn4D5Rnhworj3OeWlhhD12OZA0ag7O2+GfXu6spo9eJt28iYF2BA 8fQnkY6DRiiEr8jXiR0phr7EJ7IB6bcnFgaPXLDaiEZkwsyuVKqWiB1NGvfyPSkqlN 3nNk5CuWNNN2yDICqOXld+WR0l3F5qrsZ6DGWze72MVM1NgSNOEWorLu0HIu+IkPmS Le1cTLwfX7JrmGMaFtb8XlcglDFs6q3v+eMlZGZ0CexjLQfYlu0Xr1H2v+JkOt7Vgg gMN4rEYILLa4Q==
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.98]) by opfednr04.francetelecom.fr (ESMTP service) with ESMTP id 4BrCPb5Vmrz1xpF; Tue, 15 Sep 2020 08:05:07 +0200 (CEST)
From: mohamed.boucadair@orange.com
To: "dots@ietf.org" <dots@ietf.org>, "Benjamin Kaduk (kaduk@mit.edu)" <kaduk@mit.edu>
Thread-Topic: I-D Action: draft-ietf-dots-signal-call-home-09.txt
Thread-Index: AQHWiyWfM4vObSwKRUSLdMrRmTMiLKlpNXvQ
Date: Tue, 15 Sep 2020 06:05:07 +0000
Message-ID: <28148_1600149907_5F605993_28148_13_1_787AE7BB302AE849A7480A190F8B933031540A47@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <160014965486.4877.18032043993093344590@ietfa.amsl.com>
In-Reply-To: <160014965486.4877.18032043993093344590@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/5_E149zUUFksCil52ccL7z2X3pY>
Subject: Re: [Dots] I-D Action: draft-ietf-dots-signal-call-home-09.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, 15 Sep 2020 06:05:12 -0000

Hi Ben, all, 

The main update is to refer to 8782bis instead of 8782 and tweak the yang module accordingly. 

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é : mardi 15 septembre 2020 08:01
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : I-D Action: draft-ietf-dots-signal-call-home-09.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 Call Home
>         Authors         : Tirumaleswar Reddy
>                           Mohamed Boucadair
>                           Jon Shallow
> 	Filename        : draft-ietf-dots-signal-call-home-09.txt
> 	Pages           : 37
> 	Date            : 2020-09-14
> 
> Abstract:
>    This document specifies the DOTS signal channel Call Home, 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(s).
> 
>    The DOTS signal channel Call Home is not specific to the home
>    networks; the solution targets any deployment which requires to
> block
>    DDoS attack traffic closer to the source(s) of a DDoS attack.
> 
> 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 Call Home";
> 
>    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) Signal Channel Specification" (used to be I-D.ietf-
> dots-
>       rfc8782-bis)
> 
>    Please update TBD statements with the assignment made by IANA to
> DOTS
>    Signal Channel Call Home.
> 
>    Also, 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-signal-call-home/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dots-signal-call-home-09
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-signal-call-
> home-09
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-signal-call-home-
> 09
> 
> 
> 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

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.