Hi Med,
Many thanks for your detailed review. Most of them are inserted.
I don't understand this one comment (and BMI35, BMI36)
For this one below, you are right. We propose to reuse the definitions
in draft-ietf-opsawg-oam-characterization
<https://datatracker.ietf.org/doc/draft-ietf-opsawg-oam-characterization/>,
instead of the IOAM specific terms.
Regards, Benoit.
On 7/12/2024 4:42 PM, mohamed.boucad...@orange.com wrote:
Hi all,
FWIW, please find below my review of this draft:
* pdf:
https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2024/draft-ietf-opsawg-ipfix-on-path-telemetry-08-rev%20Med.pdf
<https://github.com/boucadair/IETF-Drafts-Reviews/blob/master/2024/draft-ietf-opsawg-ipfix-on-path-telemetry-08-rev%20Med.pdf>
* doc:
https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/2024/draft-ietf-opsawg-ipfix-on-path-telemetry-08-rev%20Med.doc
Overall,
* I think that some motivation is needed to explain the need for the
IEs compared to an approach where intermediate nodes export the
timestamps observed in packets and local receiving timestamp and
let the collector to do the various math operations.
* The IEs do not need to be tightly linked with IOAM. The IEs are
applicable whenever a timestamp is present in packets. For
example, The IEs can be used in the context of
https://datatracker.ietf.org/doc/html/rfc9145#name-new-nsh-variable-length-cont
to help detect abnormal traffic steering policies for
time-optimized service function chains. I suggest the authors to
reconsider the current description and generalize the use.
* The security considerations are under specified: these IEs are
sensitive as they may (when blindly trusted) to network
reconfiguration. Appropriate guards should be in place to control
how abnormal delays trigger service/network optimization.
* The document includes citations to many individual drafts. Some of
the citations are obviously normative. I don’t think that’s
needed. I would cleanup the various citations and focus on a
subset for the sake of illustration. Please note that some of
these are expired, while they are the only cited reference for
aspects that are presented as key (ex. draft-song).
* I would insist more on time synchronization matter early in the
document.
* The exploitation of the various delay-related metric may be
problematic in the absence of reference measurement intervals, etc.
* The IE naming does not following 7012 rules
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.
_______________________________________________
OPSAWG mailing list -- opsawg@ietf.org
To unsubscribe send an email to opsawg-le...@ietf.org
