Mahesh Jethanandani has entered the following ballot position for charter-ietf-quic-03-05: 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-quic/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Paragraph 3 > * Maintenance and evolution of the QUIC base specifications that > describe its invariants, core transport mechanisms, security and > privacy properties, loss detection and recovery, congestion control, > version and extension negotiation, etc. This includes the > specification of new versions of QUIC. > > * Maintenance and evolution of the existing QUIC extensions > specified by the WG. This area of work seems to conflate maintenance and specification of a new version of QUIC, when they are two different tasks with their own set of milestones. Ideally, they should be broken out as two separate areas of work. ------------------------------------------------------------------------------- NIT ------------------------------------------------------------------------------- All comments below are about very minor potential issues that you may choose to address in some way - or ignore - as you see fit. Some were flagged by automated tools (via https://github.com/larseggert/ietf-reviewtool), so there will likely be some false positives. There is no need to let me know what you did with these suggestions. Paragraph 5 > ations that have adopted QUIC as a transport. 2. The second area of work is > ^^^^^^^^^^^ Uncountable nouns are usually not used with an indefinite article. Use simply "transport". "QUIC", paragraph 1 > ion control schemes may fall under the the third area of work. The QUIC WG o > ^^^^^^^ Possible typo: you repeated a word.
