IETF Logo Mail Archive

[dhcwg] Review Request: draft-ietf-dots-server-discovery-01

<mohamed.boucadair@orange.com> Wed, 17 April 2019 09:28 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C4321200B9; Wed, 17 Apr 2019 02:28:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lx7uFfYrsAk5; Wed, 17 Apr 2019 02:28:33 -0700 (PDT)
Received: from orange.com (mta241.mail.business.static.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 5A79A12003E; Wed, 17 Apr 2019 02:28:30 -0700 (PDT)
Received: from opfedar03.francetelecom.fr (unknown [xx.xx.xx.5]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 44kcNr3nHJzFqKk; Wed, 17 Apr 2019 11:28:28 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.64]) by opfedar03.francetelecom.fr (ESMTP service) with ESMTP id 44kcNr31qHzCqkt; Wed, 17 Apr 2019 11:28:28 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBMA3.corporate.adroot.infra.ftgroup ([fe80::90fe:7dc1:fb15:a02b%21]) with mapi id 14.03.0439.000; Wed, 17 Apr 2019 11:28:28 +0200
From: mohamed.boucadair@orange.com
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
CC: "draft-ietf-dots-server-discovery@ietf.org" <draft-ietf-dots-server-discovery@ietf.org>
Thread-Topic: Review Request: draft-ietf-dots-server-discovery-01
Thread-Index: AdT0/+RXbZFR81OQRAKUqN0ZNUh3Lg==
Date: Wed, 17 Apr 2019 09:28:27 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA61A48@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
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/dhcwg/0wLnhFYtnpIKe9-uXK6_0OxZSxk>
Subject: [dhcwg] Review Request: draft-ietf-dots-server-discovery-01
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Apr 2019 09:28:35 -0000

Dear all, 

FWIW, we are currently developing this specification in DOTS WG.

We would appreciate your feedback/review of the DHCP part of this spec. Thank you. 

Cheers,
Med

> -----Message d'origine-----
> De : Dots [mailto:dots-bounces@ietf.org] De la part de internet-
> drafts@ietf.org
> Envoyé : mercredi 17 avril 2019 11:13
> À : i-d-announce@ietf.org
> Cc : dots@ietf.org
> Objet : [Dots] I-D Action: draft-ietf-dots-server-discovery-01.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) Server Discovery
>         Authors         : Mohamed Boucadair
>                           Tirumaleswar Reddy
>                           Prashanth Patil
> 	Filename        : draft-ietf-dots-server-discovery-01.txt
> 	Pages           : 20
> 	Date            : 2019-04-17
> 
> Abstract:
>    It may not be possible for a network to determine the cause for an
>    attack, but instead just realize that some resources seem to be under
>    attack.  To fill that gap, Distributed-Denial-of-Service Open Threat
>    Signaling (DOTS) allows a network to inform a DOTS server that it is
>    under a potential attack so that appropriate mitigation actions are
>    undertaken.
> 
>    This document specifies mechanisms to configure DOTS clients with
>    DOTS servers.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-dots-server-discovery/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-dots-server-discovery-01
> https://datatracker.ietf.org/doc/html/draft-ietf-dots-server-discovery-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dots-server-discovery-01
> 
> 
> 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

v2.23.0 | Report a Bug | By Email