Note: opsawg, nmop, teas, and ccamp in Bcc Hello, ONIONS WG (and other related WGs). Dhruv and I are holding the pen on the ONIONS WG charter, and we need your help to refine it.
We have taken Med’s initial, raw text (see https://github.com/boucadair/WG-Charters/blob/main/onions-raw.md) and produced a draft charter at https://github.com/boucadair/WG-Charters/blob/main/onions.md. Please use the onions@ mailer to discuss any issues, concerns, or suggested text. We want to make sure the scope and framing of the charter are clear and appropriate, and we address any gaps as soon as possible. Our goal is to have a stable charter by the IETF 123 document cut-off (July 7). Once new text has some consensus, please create a pull request at https://github.com/boucadair/WG-Charters/pulls, and we can merge the work. Also, see https://github.com/boucadair/WG-Charters/labels/onions for a list of issues that have already been raised as these are good to carry over discussion here. Some specific things to consider is to what extent does ONIONS focus on tooling? Is this just developing requirements, or is tool development also in scope? There are existing drafts in the IETF (see https://github.com/boucadair/WG-Charters/blob/main/onions-impact.md) that could move to the ONIONS WG. Is the intended action (stay or move) appropriate for these documents? What other documents should be considered and why? Thanks for your time and input! Joe and Dhruv
_______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
