Zaheduzzaman Sarker has entered the following ballot position for charter-ietf-spring-02-01: Block
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-spring/ ---------------------------------------------------------------------- BLOCK: ---------------------------------------------------------------------- I support Roman's and Gunter's block, I think those are good points that needs clarifiction. I have blocking comment as I am trying to understand the part I copied here, what it says, but I am getting confused on what should be done in spring and what should be done in other working groups and how that should be decided --Any modification of -or extension to- existing architectures, data planes, or control or management plane protocols should be carried out in the WGs responsible for the architecture, data plane, or control or management plane protocol being modified and in coordination with the SPRING WG, but may be done in SPRING WG after agreement with all the relevant WG chairs and responsible Area Directors. -- If the responsible working group should carry out the work, then why do they need to bring that work in spring? This should be explicitly mentioned otherwise it would create confusions in future to decide what should be done where. And rephrasing the mentioned text could help here a lot. _______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
