Andrew Alston has entered the following ballot position for draft-ietf-quic-bit-grease-04: Discuss
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.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-quic-bit-grease/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Thanks for the work on this document, Hopefully this discuss will be relatively easy to resolve - and may result from a lack of understanding - but - Endpoints that receive the grease_quic_bit transport parameter from a peer SHOULD set the QUIC Bit to an unpredictable value unless another extension assigns specific meaning to the value of the bit. Now, this is in reference to a bit - which can only be 0 or 1 - and the document further goes on to clarify certain situations where this bit should be set or unset - so I am not at all sure what this paragraph really means and hoping this can be clarified because I'm not sure how this will be interpreted on implementation.
