Roman Danyliw has entered the following ballot position for draft-ietf-opsawg-yang-vpn-service-pm-13: 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-yang-vpn-service-pm/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Daniel Migault for the SECDIR. ** Section 4.4. s/Lists p <line break> erformance/Lists performance/ ** Section 4.4. s/Last updatd/Last updated/ ** Section 6. Recommend being more descriptive in the impact. OLD Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. NEW Write operations (e.g., edit-config) to these data nodes without proper protection can have a negative effect on network operations. These write operates can lead to inaccurate or incomplete network measurements which case impact the visibility and decisions this data would be used to inform. ** Section 6. Thanks for the detailed table describing the impact of write operations. Since there is space to add a bit more descriptive language on the page, consider: “impact reporting” --> “impacts reporting cadence” “impact monitoring” --> “impacts monitoring fidelity” I don’t understand “render invalid”? Does this combine the idea of “turning it all off” and “making the data unusable”? I’d recommend explaining the phrase or use something different. _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
