Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles

<> Fri, 26 July 2019 11:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6DD9F1202E5 for <>; Fri, 26 Jul 2019 04:33:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Status: No, score=-2.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 st_kd5Kcw7Bx for <>; Fri, 26 Jul 2019 04:33:22 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 48AD112024F for <>; Fri, 26 Jul 2019 04:33:22 -0700 (PDT)
Received: from (unknown [xx.xx.xx.70]) by (ESMTP service) with ESMTP id 45w6Qm2kpmz1y6Z; Fri, 26 Jul 2019 13:33:20 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.76]) by (ESMTP service) with ESMTP id 45w6Ql6dpHzDq93; Fri, 26 Jul 2019 13:33:19 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM7E.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Fri, 26 Jul 2019 13:33:20 +0200
From: <>
To: "Panwei (William)" <>, "Konda, Tirumaleswar Reddy" <>, Valery Smyslov <>, "" <>
Thread-Topic: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles
Thread-Index: AdVC85i4bFch/Zy8RxyBqvTQ1hxRMP//l+iAgAD+xQCAABi9gIAAAsKAgACskTT///rvIA==
Date: Fri, 26 Jul 2019 11:33:19 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330312E9518@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B9330312E88FA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <01db01d54302$9bef3b40$d3cdb1c0$> <787AE7BB302AE849A7480A190F8B9330312E9380@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <>, <787AE7BB302AE849A7480A190F8B9330312E9427@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> 2426C851-FB5E-4031-B64B-1C8166491C2A
In-Reply-To: 2426C851-FB5E-4031-B64B-1C8166491C2A
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330312E9518OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles
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: Fri, 26 Jul 2019 11:33:25 -0000


What about adding the following to the terminology section?

   'DOTS signal channel Call Home' refers to a DOTS signal channel
   established at the initiative of a DOTS server.  That is, the DOTS
   server (a.k.a., Call Home DOTS server) initiates a secure connection
   to a DOTS client (a.k.a., Call Home DOTS client), and uses that
   connection to receive the attack traffic information from the Call
   Home DOTS client.  More details are provided in Section 3.


De : Panwei (William) []
Envoyé : vendredi 26 juillet 2019 13:12
À : BOUCADAIR Mohamed TGI/OLN; Konda, Tirumaleswar Reddy; Valery Smyslov;
Objet : RE: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles


I agree with Med. This maybe confused for people who are not familiar with this spec.
The confusing part can be at the situation where base siganl channel and call home channel are used at the same time. In this case there are two kinds of DOTS client/server, we must emphasize DOTS client used in base signal channel and DOTS client used in call home signal channel to separate them. I think the new terms will make this difference better for both understanding and expressing.
BTW, I suggest giving 'Call Home Signal Channel' a term definition at the same time.

潘伟 William
Mobile: +86-18551640326<tel:+86-18551640326>
发件人 <>;
收件人:Konda, Tirumaleswar Reddy <>;Valery Smyslov <>; <>;
时间:2019-07-26 04:54:48
主 题:Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles


Please see inline.


De : Dots [] De la part de Konda, Tirumaleswar Reddy
Envoyé : vendredi 26 juillet 2019 10:45
À : BOUCADAIR Mohamed TGI/OLN; Valery Smyslov;
Objet : Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles

I don’t see any such terminology used in other specifications like Why do we need “Call Home” prefix even after the text clarifies the roles clearly ?
[Med] For us who are familiar with the text, there is no confusion. But I hear the comment from Valery as this may be confusing in some places. It is worth to clarify at this stage rather than spending extra cycles when the document advances in the process.

If we go with this change all the figures needs to modified, and these terms need to be defined before being used.
[Med] No all of the figures, but only when there is a confusion.


From: Dots <>; On Behalf Of
Sent: Friday, July 26, 2019 12:46 PM
To: Valery Smyslov <>;;
Subject: Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles

CAUTION: External email. Do not click links or open attachments unless you recognize the sender and know the content is safe.

Hi Valery,

We didn’t consider the use of new terms because we thought this may be interpreted as if we are defining new DOTS roles (which we don’t).

The text uses “in the call home scenario” to make that distinction in some places, but I understand this may not be sufficient.

I’m OK to go with “Call Home DOTS *”. I updated the terminology section with the following:

   DOTS agents involved in the DOTS Call Home adhere to the DOTS roles

   as defined in [RFC8612].  For clarity, this document uses "Call Home

   DOTS client" (or "Call Home DOTS server") to refer to a DOTS client

   (or DOTS server) deployed in a Call Home scenario.

and changed the text when it makes sense. The full diff is available at:

candidate -05:

Please let us know if this is better.

Thank you.



De : Valery Smyslov []
Envoyé : jeudi 25 juillet 2019 18:04
Objet : RE: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles

Hi Med,

thank you for adding this section, it really helps.
However, I was asking for more - did you consider
changing the terminology in such a way, that
Call Home use case is not mixed with basic DOTS use case?

For example, calling entities not just DOTS Client and DOTS
Server, but say Call Home DOTS Client and Call Home DOTS Server?
(actually I don't like these ad hoc names, probably you can invent better term)..


From: Dots <<>> On Behalf Of<>
Sent: Thursday, July 25, 2019 5:17 PM
Subject: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles


There was a comment raised during the meeting asking to further clarify the role of the various DOTS agent in the call home. We added an new section to address this comment: