Hi Juan-Carlos, Happy New Year! Thanks a lot for your review - and sorry for the delay. We've just posted a new revision https://www.ietf.org/archive/id/draft-ietf-ippm-ioam-deployment-04.txt which is to address your comments. Please see inline. > -----Original Message----- > From: Juan-Carlos Zúñiga via Datatracker <noreply@xxxxxxxx> > Sent: Sunday, 11 December 2022 16:28 > To: int-dir@xxxxxxxx > Cc: draft-ietf-ippm-ioam-deployment.all@xxxxxxxx; ippm@xxxxxxxx; last- > call@xxxxxxxx > Subject: Intdir telechat review of draft-ietf-ippm-ioam-deployment-02 > > Reviewer: Juan-Carlos Zúñiga > Review result: Ready with Nits > > This document is almost ready for publication as an Informational RFC, with > some nits. > > Comments: > > The document is well written, clear, and helpful to understand the IOAM > framework. Sections 1-6 explain the different concepts and aspects of IOAM, > section 7 provides some important considerations to be taken into account > when deploying IOAM (perhaps the main section), section 8 provides some > IOAM management recommendations, and finally section 10 provides an > analysis of possible security threats and mitigations. > > Nits: > > - The draft's intended status is Informational. However, the Abstract mentions > that the document provides a framework and discusses best current practices. > Since the intended status is not BCP, I would suggest changing the sentence to > something like "provides a framework and describes important IOAM > deployment considerations," ...FB: The fact that the abstract should not sounds like a BCP has been mentioned by several reviewers. The abstract now reads: " This document provides a framework for IOAM deployment and provides IOAM deployment considerations and guidance." > > - Section 7 is introduced as "discussing aspects of IOAM." Although the section's > scope is indeed very wide, I would suggest changing the text to something more > descriptive and representative of the importance of this section, like "describes > several concepts of IOAM, and provides considerations that need to be taken to > account when implementing IOAM in a network domain." ...FB: Good point. The intro to Section 7 got expanded accordingly: This section describes several concepts of IOAM, and provides considerations that need to be taken to account when implementing IOAM in a network domain. This includes concepts like IOAM Namespaces, IOAM Layering, traffic-sets that IOAM is applied to and IOAM loopback mode. For a definition of IOAM Namespaces and IOAM layering, please refer to [RFC9197]. IOAM loopback mode is defined in [RFC9322] Thanks again for your review. Cheers, Frank > > -- last-call mailing list last-call@xxxxxxxx https://www.ietf.org/mailman/listinfo/last-call
