John Scudder has entered the following ballot position for charter-ietf-spring-02-01: 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-spring/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- This sentence makes my brain hurt, simply because the syntax requires way too much parsing: 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. (Also, the "-or extension to-" thing is just wrong, turn those dashes into commas, if that text is kept. There are some definite articles missing and stuff, too.) I don't have a fantastic rewrite to offer, but a first attempt might be to break it into several smaller sentences, as in, 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 same. The responsible WG should coordinate with the SPRING WG. Alternatively, the work may be done in the SPRING WG after agreement with all the relevant WG chairs and responsible Area Directors. I'll be interested in the response to Roman's BLOCK, and I want to echo his implicit "why aren't any milestones listed?" _______________________________________________ spring mailing list -- spring@ietf.org To unsubscribe send an email to spring-le...@ietf.org
