Re: [Dots] DOTS Telemetry: Interop Clarification #1

Jon Shallow <supjps-ietf@jpshallow.com> Mon, 29 June 2020 09:13 UTC

Return-Path: <supjps-ietf@jpshallow.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 CD0B13A0CBE for <dots@ietfa.amsl.com>; Mon, 29 Jun 2020 02:13:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 KywWK7sdjkNi for <dots@ietfa.amsl.com>; Mon, 29 Jun 2020 02:13:03 -0700 (PDT)
Received: from mail.jpshallow.com (mail.jpshallow.com [217.40.240.153]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 324B23A0CBC for <dots@ietf.org>; Mon, 29 Jun 2020 02:12:59 -0700 (PDT)
Received: from mail2.jpshallow.com ([192.168.0.3] helo=N01332) by mail.jpshallow.com with esmtp (Exim 4.92.3) (envelope-from <jon.shallow@jpshallow.com>) id 1jppqQ-00041V-Kq; Mon, 29 Jun 2020 10:12:54 +0100
From: Jon Shallow <supjps-ietf@jpshallow.com>
To: mohamed.boucadair@orange.com, kaname nishizuka <kaname@nttv6.jp>, dots@ietf.org
References: <25679_1593113350_5EF4FB06_25679_457_1_787AE7BB302AE849A7480A190F8B9330314E762D@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <084a01d64bb2$d63a86b0$82af9410$@jpshallow.com> <9226_1593412702_5EF98C5E_9226_29_1_787AE7BB302AE849A7480A190F8B9330314E8989@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
In-Reply-To: <9226_1593412702_5EF98C5E_9226_29_1_787AE7BB302AE849A7480A190F8B9330314E8989@OPEXCAUBMA2.corporate.adroot.infra.ftgroup>
Date: Mon, 29 Jun 2020 10:12:47 +0100
Message-ID: <0ad501d64df5$74b89b30$5e29d190$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0AD6_01D64DFD.D67E89D0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQH0NBewyz0cz3gVN6O99zZ2D4scewEFmq9oAkUV0A6omSuj4A==
Content-Language: en-gb
Archived-At: <https://mailarchive.ietf.org/arch/msg/dots/4fF1IjHMPwZb-1k-ZZHu7hmsFJo>
Subject: Re: [Dots] DOTS Telemetry: Interop Clarification #1
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: Mon, 29 Jun 2020 09:13:06 -0000

Hi Med,

 

So for absolute clarity, the DOTS server will return the values it has
internally determined (from DOTS mitigator etc.), not those provided by the
DOTS client using a PUT, as modified by the GET Query filters.

 

Regards

 

Jon

 

From: Dots [mailto: dots-bounces@ietf.org] On Behalf Of
mohamed.boucadair@orange.com
Sent: 29 June 2020 07:38
To: Jon Shallow; kaname nishizuka; dots@ietf.org
Subject: Re: [Dots] DOTS Telemetry: Interop Clarification #1

 

Hi Jon, all,

 

The server will return the data that match the filters included in the GET
that triggered the response. 

 

Cheers,

Med

 

De : Jon Shallow [mailto:supjps-ietf@jpshallow.com] 
Envoyé : vendredi 26 juin 2020 14:11
À : BOUCADAIR Mohamed TGI/OLN; kaname nishizuka; dots@ietf.org
Objet : RE: [Dots] DOTS Telemetry: Interop Clarification #1

 

Hi Med,

 

I think that this refers several places.

 

1.       Efficacy updates.  E.g.  Figure 45: An Example of Mitigation
Efficacy Update with Telemetry  Attributes. Here we do an efficacy update of
what the client is seeing happen to a specific resource.  If the client now
does a GET against the same resource – what is returned – the last efficacy
update or the current state of mitigation as seen by the DOTS server?

 

2.       Also, Figure 36: PUT to Send Pre-or-Ongoing-Mitigation Telemetry
allows the client to update the tmid with some information.  This includes
an attack-detail.  When the client wants to see what is happening with this
“tmid”, it does a Figure 40: GET to Subscribe to Telemetry Asynchronous
Notifications for a Specific 'tmid'.  Which attack-detail is returned – the
one from the PUT or the ongoing situation?

 

Regards

 

Jon

 

From: Dots [mailto: dots-bounces@ietf.org] On Behalf Of
mohamed.boucadair@orange.com
Sent: 25 June 2020 20:29
To: kaname nishizuka
Cc: dots@ietf.org
Subject: [Dots] DOTS Telemetry: Interop Clarification #1

 

Hi Kaname, 

 

We discussed this issue in the interim:

 

==

Current Uri-Path can't distinguish telemetry resources posted by the client
or created by the server.

–Those are totally different resources. 

For example, Uri-Query won't be applicable to the telemetry resources posted
by the client.

==

 

Can you please identify precisely which parts of the text need to be
updated?

 

Thank you 

 

Cheers,

Med

 

____________________________________________________________________________
_____________________________________________
 
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.
____________________________________________________________________________
_____________________________________________
 
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.