[Dots] DOTS telemetry Issues picked up in Interop Testing

[Jon Shallow <[e-mail]>]

Hi All,

 

1)

   DOTS agents MUST NOT send pre-or-ongoing-mitigation telemetry

   messages to the same peer more frequently than once every 'telemetry-

   notify-interval' (Section 6.1).

 

If I do a PUT /tm-setup, followed immediately by a GET /tm-setup, should the
GET fail based on the telemetry-notify-interval, or should
telemetry-notify-interval apply individually to PUT. GET and DELETE?

[I may want to do a DELETE (no tsid) followed by a GET to get suitable
max/min information and telemetry-notify-interval can easily be more than 1
second. ]

 

2)

Use of multiple Uri-Query:

 

Uri-Query: target_prefix=[1.2.3.4]

Uri-Query: target_prefix=[2.3.4.5]

I think this should be OR

 

Uri-Query: target_prefix=[1.2.3.4]

Uri-Query: target_port=[80]

I think this should be an AND.

 

Perhaps we should have operator queries

Uri-Query: target_prefix=[1.2.3.4]

Uri-Query: op=OR

Uri-Query: target_prefix=[2.3.4.5]

 

Uri-Query: target_prefix=[1.2.3.4]

Uri-Query: op=AND

Uri-Query: target_port=[80]

 

Thoughts?

 

3)

What happens if a Query cannot be supported.

 

E.g. Uri-Query: target_port=[80] and statistics on the server by a port
basis  is not supported.  Do we want to either error out with a 4.0X
responses, or should we include a (new additional) YANG body response
indicating which Uri-Query is not supported?

 

 

Regards

 

Jon