Three ECN NiTS #3734
Labels
-transport
editorial
An issue that does not affect the design of the protocol; does not require consensus.
Projects
(1) NiT:
/The ECN counter for the ECN codepoint received in the associated IP header are incremented once for each QUIC packet, not per enclosing IP packet or UDP datagram./
(2) I like this phrase in the security considerations also from the point of view of how to generate transport feedback for ECT(?). Can we call this out here:
/QUIC endpoints ignore the ECN codepoint field on an IP packet unless at least one QUIC packet in that IP packet is successfully processed/
(3) General experiments are not permitted in RFC8311, only using experimental RFCs. I think therefore, we should be clear in the detail here:
/Implementations MAY experiment with and use other strategies for use of ECN. Other methods of probing paths for ECN support are possible, as are different marking strategies. Implementations can also use the ECT(1) codepoint, as specified in {{?RFC8311}}./
I’d propose something more like this:
/Other methods of probing paths for ECN support are possible, as are different marking strategies. Implementations MAY use other methods defined in RFCs, as specified in {{?RFC8311}}. Implementations that use the ECT(1) codepoint, need to perform ECN validation using this code point./
The text was updated successfully, but these errors were encountered: