This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
"body": "Is \"to the encoder\" intended? Should this be \"within the encoder\" or might \"contain\" be made \"limit\" or something else?\n\nOriginal:\n\n QPACK is designed to contain the more complex state tracking to the\n encoder, while the decoder is relatively simple.\n",
"createdAt": "2022-03-25T17:40:08Z",
"updatedAt": "2022-04-26T17:48:17Z",
"updatedAt": "2022-05-09T19:04:01Z",
"closedAt": null,
"comments": [
{
@@ -139766,6 +139766,13 @@
"body": "\"Limit\" is probably the closest if we want to keep the phrase as-is. Writing something *de novo* might be better, but I'm having trouble coming up with anything pithy.",
"createdAt": "2022-04-26T17:48:17Z",
"updatedAt": "2022-04-26T17:48:17Z"
},
{
"author": "LPardue",
"authorAssociation": "MEMBER",
"body": "Some alternatives (aka throwing mud at the wall)\r\n\r\n1. \"The design of QPACK requires an encoder to implement relatively more-complex state tracking than a decoder.\"\r\n2. \"QPACK's design requires state tracking in various degrees of complexity. In relative terms, encoders have complex requirements, while decoders are more simple.\r\n3. \"QPACK is designed to put the state tracking complexity onus on encoders, resulting in relatively simple decoders.\"\r\n",
"createdAt": "2022-05-09T19:03:42Z",
"updatedAt": "2022-05-09T19:04:01Z"
}
]
},
@@ -139840,7 +139847,7 @@
"id": "I_kwDOBGXJj85GZZ46",
"title": "Auth48: Huffman-coded versus Huffman encoded",
"body": "May we update \"Huffman-coded\" with \"Huffman encoded\" in this text to match other uses?\n\nOriginal:\nThey begin with a single bit flag, denoted as 'H' in this document\n(indicating whether the string is Huffman-coded), followed by the\nLength encoded as a 7-bit prefix integer, and finally Length bytes of\ndata.\n",
"createdAt": "2022-03-25T17:40:09Z",
"updatedAt": "2022-04-01T19:18:48Z",
"closedAt": null,
"comments": []
"updatedAt": "2022-05-09T18:04:16Z",
"closedAt": "2022-05-09T18:04:16Z",
"comments": [
{
"author": "MikeBishop",
"authorAssociation": "CONTRIBUTOR",
"body": "Fixed in #4986.",
"createdAt": "2022-05-09T18:04:16Z",
"updatedAt": "2022-05-09T18:04:16Z"
}
]
},
{
"number": 4972,
@@ -139891,7 +139906,7 @@
"id": "I_kwDOBGXJj85GZZ5L",
"title": "Should the following text be formatted using <aside>? (comment 7)",
"body": "Should the following text be formatted using <aside>? See the definition at <https://authors.ietf.org/rfcxml-vocabulary#aside>.\n\nOriginal:\n\n Note: Padding schemes only provide limited protection against an\n attacker with these capabilities, potentially only forcing an\n increased number of guesses to learn the length associated with a\n given guess. Padding schemes also work directly against\n compression by increasing the number of bits that are transmitted.\n\nOriginal:\n\n Note: Simply removing entries corresponding to the field from the\n dynamic table can be ineffectual if the attacker has a reliable\n way of causing values to be reinstalled. For example, a request\n to load an image in a web browser typically includes the Cookie\n header field (a potentially highly valued target for this sort of\n attack), and websites can easily force an image to be loaded,\n thereby refreshing the entry in the dynamic table.\n\n",
"body": "This is a change in the RFC Editor diff that I don't think works; pulling out for separate discussion.\r\n\r\nOriginal:\r\n> For HTTP/3 servers and HTTP/3 clients when 0-RTT is not attempted or is rejected, the maximum table capacity is 0 until the encoder processes a SETTINGS frame with a non-zero value of SETTINGS_QPACK_MAX_TABLE_CAPACITY.\r\n\r\nProposed but incorrect:\r\n> When 0-RTT is not attempted or is rejected, for HTTP/3 servers and clients, the maximum table capacity is 0 until the encoder processes a SETTINGS frame with a non-zero value of SETTINGS_QPACK_MAX_TABLE_CAPACITY.\r\n\r\nThe intended reading is: For...\r\n\r\n- HTTP/3 servers (always, regardless of 0-RTT) and\r\n- HTTP/3 clients when 0-RTT is not attempted or is rejected\r\n\r\n...the maximum table capacity is 0.",