Re: [Last-Call] Opsdir last call review of draft-ietf-quic-bit-grease-03

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On May 20, 2022, at 1:46 AM, Martin Thomson <mt@xxxxxxxxxxxxxx> wrote:


Section 3

Current:
“The grease_quic_bit transport parameter (0x2ab2) can be sent by both
  client and server.  The transport parameter is sent with an empty
  value; an endpoint that understands this transport parameter MUST
  treat receipt of a non-empty value as a connection error of type
  TRANSPORT_PARAMETER_ERROR.”

I find the above wording confusing – “ receipt of a non-empty value” of what?
(the “grease_quic_bit” or something else?

I don't see an issue here.  Is it that this is missing the context that transport parameters have values?  That's pretty elementary stuff that I don't think needs to be contextualized.

maybe
The grease_quic_bit transport parameter (0x2ab2) can be sent by both
  client and server.  The transport parameter is sent with an empty
  value; an endpoint that understands this transport parameter MUST
  treat receipt of a non-empty value of the transport parameter as a connection error of type
  TRANSPORT_PARAMETER_ERROR.”
-- 
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call

[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux