Hi Eric, Thanks for the review and sharing your observations
Inline: GV> -----Original Message----- From: Éric Vyncke via Datatracker <[email protected]> Sent: Wednesday, July 9, 2025 2:46 PM To: The IESG <[email protected]> Cc: [email protected]; [email protected] Subject: Éric Vyncke's No Objection on charter-ietf-bess-01-08: (with COMMENT) CAUTION: This is an external email. Please be very careful when clicking links or opening attachments. See the URL nok.it/ext for additional information. Éric Vyncke has entered the following ballot position for charter-ietf-bess-01-08: 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.) The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/charter-ietf-bess/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- s/producing BGP specifications for services in its charter/producing *standard track* BGP specifications for services in its charter/ GV> Updated in charter-v10 s/protocols*'* specifications/protocols specifications/ GV> Updated in charter-v10. I also cleaned up the language used in that paragraph for clarity. A list of *deliverables* in the charter would allow for a well-defined scope of BESS WG. Notably, I see nowhere the `informational documents only related to operational and deployment aspects` in the `the WG is expected to work on`. GV> Thanks for catching this. I added the below line in the list of BESS "deliverables" to resolve this deliverable ambiguity in charter-v10: " h) Informational documents that describe operational practices, deployment considerations, and implementation experiences related to services for which the WG is also developing standard track protocol specifications. " G/ _______________________________________________ BESS mailing list -- [email protected] To unsubscribe send an email to [email protected]
