Re: [Dots] clarification questions from the hackathon

<> Thu, 28 March 2019 13:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 91F13120466 for <>; Thu, 28 Mar 2019 06:56:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.599
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id F3B_QyHHysoK for <>; Thu, 28 Mar 2019 06:56:44 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 92DA31204BD for <>; Thu, 28 Mar 2019 06:56:44 -0700 (PDT)
Received: from (unknown [xx.xx.xx.66]) by (ESMTP service) with ESMTP id 44VRHb1Lg8zCrgH; Thu, 28 Mar 2019 14:56:43 +0100 (CET)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.64]) by (ESMTP service) with ESMTP id 44VRHb0Rmnz8sYR; Thu, 28 Mar 2019 14:56:43 +0100 (CET)
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; Thu, 28 Mar 2019 14:56:42 +0100
To: Olli Vanhoja <>, kaname nishizuka <>
CC: "" <>
Thread-Topic: [Dots] clarification questions from the hackathon
Thread-Index: AQHU5VO3CfVXhciSq0+ZqKxGOtsoYqYhDJ7w
Date: Thu, 28 Mar 2019 13:56:42 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B93302EA4EDD0@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <> <>
In-Reply-To: <>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Dots] clarification questions from the hackathon
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "List for discussion of DDoS Open Threat Signaling \(DOTS\) technology and directions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 28 Mar 2019 13:56:59 -0000

Hi Olli,

Please see inline. 


> -----Message d'origine-----
> De : Dots [] De la part de Olli Vanhoja
> Envoyé : jeudi 28 mars 2019 11:48
> À : kaname nishizuka
> Cc :
> Objet : Re: [Dots] clarification questions from the hackathon
> Some additional questions.
> I saw somewhere a probably outdated spec with a version ned URL
> /.well-known/dots/v1/mitigate
> This was however dropped from the draft:
> /.well-known/dots/mitigate
> Why is this? Wouldn't it be a good idea to allow versioning somewhere,
> either in the request path or the request body?

[Med] That change was made to reflect a change in the requirements I-D with regards to versioning. The spec relies on two sets of attributes (comprehension-required, comprehension-optional) to extend the protocol by adding new features instead of bumping the version number. 

> Was there any consideration about PKI and/or key distribution? Or
> should implementors and users solve this?

[Med] This is left to deployments. Existing specs do only say the following:

   A key challenge to deploying DOTS is the provisioning of DOTS
   clients, including the distribution of keying material to DOTS
   clients to enable the required mutual authentication of DOTS agents.
   Enrollment over Secure Transport (EST) [RFC7030] defines a method of
   certificate enrollment by which domains operating DOTS servers may
   provide DOTS clients with all the necessary cryptographic keying
   material, including a private key and a certificate to authenticate
   themselves.  One deployment option is DOTS clients behave as EST
   clients for certificate enrollment from an EST server provisioned by
   the mitigation provider.  This document does not specify which EST or
   other mechanism the DOTS client uses to achieve initial enrollment.

Having deployment guidelines would be helpful, though. 

> _______________________________________________
> Dots mailing list