Re: [Dots] WGLC for draft-ietf-dots-telemetry-use-cases-04

[[e-mail]]

Hi Yuhei, all,

Thank you very much for taking care of the comments in a timely manner. 

I think that we are almost there, but I'm afraid that one further revision may be needed. 

For convenience, I added the proposed changes directly to the xml file that can find at: 
* xml: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-dots-telemetry-use-cases-08-rev%20Med.xml
* txt: https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/draft-ietf-dots-telemetry-use-cases-08-rev%20Med.txt

A diff to track the proposed changes can be seen at: https://raw.githubusercontent.com/boucadair/IETF-Drafts-Reviews/master/wdiff%20draft-ietf-dots-telemetry-use-cases-08.txt%20draft-ietf-dots-telemetry-use-cases-08-revMed.txt.pdf

The main proposed changes are as follows:

* Updated the security section as the draft includes aspects that were not covered in the telemetry draft (controllers, orchestrators, etc.)
* Added the folding as per RFC8792

Also, 
(1) Can you please clarify in the text what is meant by "teacher labels". 
(2) Most of the use cases include a statement where DOTS client/server are implemented. However, some of the use cases do not include such statement. I would add a similar text for these use cases for consistency. Also, please check that all instances that implement DOTS elements are cited in the examples.  

Some text (e.g., about IPFIX and BGP flow spec) is repeated several times in the draft. I'm OK with that but expect that some reviewers will ask to factorize that text. 

Thank you.

Cheers,
Med

> -----Message d'origine-----
> De : H Y <[e-mail]>
> Envoyé : vendredi 18 février 2022 04:51
> À : BOUCADAIR Mohamed INNOV/NET <[e-mail]>; dots
> <[e-mail]>
> Cc : dots-chairs <[e-mail]>; Valery Smyslov
> <[e-mail]>; [e-mail];
> Meiling Chen <[e-mail]>
> Objet : Re: RE: [Dots] WGLC for draft-ietf-dots-telemetry-use-cases-04
> 
> Hi Med, All
> 
> I submitted the latest version 08. I think all Med's comments were
> addressed.
> 
> Comments are welcome.
> 
> Thanks,
> Yuhei

_________________________________________________________________________________________________________________________

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.