IETF Logo Mail Archive

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

<mohamed.boucadair@orange.com> Fri, 26 July 2019 07:16 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 E85551202BD for <dots@ietfa.amsl.com>; Fri, 26 Jul 2019 00:16:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.597
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GDvwJMVkq7Ak for <dots@ietfa.amsl.com>; Fri, 26 Jul 2019 00:16:09 -0700 (PDT)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA6BF120281 for <dots@ietf.org>; Fri, 26 Jul 2019 00:16:08 -0700 (PDT)
Received: from opfedar01.francetelecom.fr (unknown [xx.xx.xx.2]) by opfedar20.francetelecom.fr (ESMTP service) with ESMTP id 45w0jy66Bmz8sqm; Fri, 26 Jul 2019 09:16:06 +0200 (CEST)
Received: from Exchangemail-eme6.itn.ftgroup (unknown [xx.xx.13.104]) by opfedar01.francetelecom.fr (ESMTP service) with ESMTP id 45w0jy54pBzBrLv; Fri, 26 Jul 2019 09:16:06 +0200 (CEST)
Received: from OPEXCAUBMA2.corporate.adroot.infra.ftgroup ([fe80::e878:bd0:c89e:5b42]) by OPEXCAUBM5F.corporate.adroot.infra.ftgroup ([::1]) with mapi id 14.03.0439.000; Fri, 26 Jul 2019 09:16:06 +0200
From: mohamed.boucadair@orange.com
To: Valery Smyslov <smyslov.ietf@gmail.com>, "dots@ietf.org" <dots@ietf.org>
Thread-Topic: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles
Thread-Index: AdVC85i4bFch/Zy8RxyBqvTQ1hxRMP///H2A//7iU5A=
Date: Fri, 26 Jul 2019 07:16:06 +0000
Message-ID: <787AE7BB302AE849A7480A190F8B9330312E9380@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
References: <787AE7BB302AE849A7480A190F8B9330312E88FA@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <01db01d54302$9bef3b40$d3cdb1c0$@gmail.com>
In-Reply-To: <01db01d54302$9bef3b40$d3cdb1c0$@gmail.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.247]
Content-Type: multipart/alternative; boundary="_000_787AE7BB302AE849A7480A190F8B9330312E9380OPEXCAUBMA2corp_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/bOBTmYoHKicPr8T_MWhKqddAfag>
Subject: Re: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles
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: Fri, 26 Jul 2019 07:16:11 -0000

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:



https://github.com/boucadair/dots-call-home/blob/master/wdiff%20draft-ietf-dots-signal-call-home-04.txt%20draft-ietf-dots-signal-call-home-05.pdf



candidate -05: https://github.com/boucadair/dots-call-home/blob/master/draft-ietf-dots-signal-call-home-05.txt



Please let us know if this is better.



Thank you.



Cheers,

Med

De : Valery Smyslov [mailto:smyslov.ietf@gmail.com]
Envoyé : jeudi 25 juillet 2019 18:04
À : BOUCADAIR Mohamed TGI/OLN; dots@ietf.org
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).

Regards,
Valery.


From: Dots <dots-bounces@ietf.org> On Behalf Of mohamed.boucadair@orange.com
Sent: Thursday, July 25, 2019 5:17 PM
To: dots@ietf.org
Subject: [Dots] draft-ietf-dots-call-home: Clarify DOTS Agent Roles

Re-,

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: https://tools.ietf.org/html/draft-ietf-dots-signal-call-home-04#section-1.4

Cheers,
Med

v2.23.0 | Report a Bug | By Email