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

[kaname nishizuka <[e-mail]>]

Hi Med, Jon,

Thanks for describing the issue, Jon.

One way is separating the URI-path for "the client's PUT/GET" and "GET for the values seen by the DOTS server".

The other way is treating Total Traffic/Attack Details telemetry data by the DOTS client PUT as a hint which will not be stored in the DOTS server.
However, in that situation, the DOTS client DELETE will mean nothing.

regards,
Kaname

On 2020/06/26 21:10, Jon Shallow wrote:
>
> 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: [e-mail]] *On Behalf Of *[e-mail]
> *Sent:* 25 June 2020 20:29
> *To:* kaname nishizuka
> *Cc:* [e-mail]
> *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.