Dear Mike, On behalf of the authors. We received feedback from Deb, Gunter, Med and Greg and decided to publish revision -21.
https://author-tools.ietf.org/diff?doc_1=draft-ietf-opsawg-ipfix-on-path-telemetry-21 We are looking forward to your feedback wherever the changes addressing your concerns. Best wishes Thomas -----Original Message----- From: Graf Thomas, SCS-INI-NET-VNC-E2E Sent: Friday, September 5, 2025 7:17 AM To: 'Mike Bishop' <[email protected]>; 'The IESG' <[email protected]> Cc: '[email protected]' <[email protected]>; '[email protected]' <[email protected]>; '[email protected]' <[email protected]> Subject: RE: [OPSAWG]Mike Bishop's No Objection on draft-ietf-opsawg-ipfix-on-path-telemetry-20: (with COMMENT) Dear Mike, We addressed your feedback together with Tim's, Med's, Deb's, Éric's, Gunter's, Greg's and Gorry's as following https://author-tools.ietf.org/diff?doc_1=draft-ietf-opsawg-ipfix-on-path-telemetry-20&url_2=https://raw.githubusercontent.com/network-analytics/draft-ietf-opsawg-ipfix-on-path-telemetry/refs/heads/main/draft-ietf-opsawg-ipfix-on-path-telemetry-21.txt I hope this addresses your comments. Looking forward to your review. Best wishes Thomas -----Original Message----- From: Mike Bishop via Datatracker <[email protected]> Sent: Tuesday, August 5, 2025 4:37 PM To: The IESG <[email protected]> Cc: [email protected]; [email protected]; [email protected] Subject: [OPSAWG]Mike Bishop's No Objection on draft-ietf-opsawg-ipfix-on-path-telemetry-20: (with COMMENT) Mike Bishop has entered the following ballot position for draft-ietf-opsawg-ipfix-on-path-telemetry-20: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-opsawg-ipfix-on-path-telemetry/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- https://www.ietf.org/archive/id/draft-ietf-opsawg-ipfix-on-path-telemetry-20.html#section-1-5 feels like an argument for why the metrics are registered and why they're named what they are. Does the document need this, or should it just specify and register them? "Hybrid Type I Passive" is used as a single term in this document, saying it's imported from RFC7799. However, https://www.rfc-editor.org/rfc/rfc7799#section-3.8 appears to use "Hybrid Type I" and "Passive" as two separate terms, and RFC 7799 does not appear to contain the string "Hybrid Type I Passive". ===NITS FOLLOW=== - In 3.3.2, "Section 4.4.2.3 and 4.4.2.4" => "Sections 4.4.2.3 and 4.4.2.4", and these should probably be links to the sections in question. - In 3.3.5, should "hybrid type I" be capitalized as it is elsewhere in the document? - In the Acknowledgements, "Rest in Peace Al" => "Rest in Peace, Al" or simply "Rest in Peace" to avoid misreading this as a nickname. _______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
