Re: [Dots] WGLC for draft-ietf-dots-telemetry-13

Hi there,

Issues found during Interop testing 30 Oct 2020.

1)
ietf-dots-telemetry:telemetry is not in the CBOR mapping and needs to be
added.

2)
Clarity needed.  We have

   A DOTS client uses a GET request to retrieve its vendor attack
   mapping details as maintained by the DOTS server (Figure 35).

   GET /restconf/data/ietf-dots-data-channel:dots-data\
       /dots-client=dz6pHjaADkaFTbjr0JGBpw\
       /ietf-dots-mapping:vendor-mapping?\
       content=all HTTP/1.1
   Host: example.com
   Accept: application/yang-data+json

    Figure 35: GET to Retrieve Installed Vendor Attack Mapping Details

If there has not been any POST/PUT vendor-mapping for dots-client=XX, what
is the response for the GET?
4.04 or generic mappings that the server knows about?
- my preference is for the HTTP 4.04 as there (currently) are no mapping
details maintained for the dots-client=

Regards

Jon

> -----Original Message-----
> From: Dots [mailto: dots-bounces@ietf.org] On Behalf Of Valery
> Smyslov
> Sent: 27 October 2020 07:09
> To: dots@ietf.org
> Cc: dots-chairs@ietf.org; draft-ietf-dots-telemetry@ietf.org
> Subject: [Dots] WGLC for draft-ietf-dots-telemetry-13
> 
> Hi,
> 
> this message starts a two-week working group last call for
draft-ietf-dots-
> telemetry-13,
> which will end on Wednesday, November 11. Please, review the draft
> carefully and
> send your comments to the mailing list.
> 
> Regards,
> Frank & Valery.
> 
> _______________________________________________
> Dots mailing list
> Dots@ietf.org
> https://www.ietf.org/mailman/listinfo/dots