Re: [C430] RFC 9000 - Re: [IANA #1196209] Protocol Action: 'QUIC: A UDP-Based Multiplexed and Secure Transport' to Proposed Standard (draft-ietf-quic-transport-34.txt)

Hi, Martin.

Apologies for the oversight previously -- we think that in line with updates to Table 3 and the entry in Section 20.1 for CRYPTO_ERROR, the spaces around the "-" in the CRYPTO_ERROR row in Table 7 should be removed.

However, we found that when the spaces around the hyphen in the number range 0x0100 - 0x01ff are removed, the table length is readjusted, and it extends beyond the margins; this results in "line too long" warnings for the text output.

In order to get the text output for Table 7 without any line-length warnings, inserting "&#8203;" (zero-width space) in this CRYPTO_ERROR entry works.  Another option is <br/>.  Do you have a preference between these options?  Please see the following files for an example of using "&#8203;":

   https://www.rfc-editor.org/v3test/rfc9000-Table-7-zero-width-space.xml
   https://www.rfc-editor.org/v3test/rfc9000-Table-7-zero-width-space.txt
   https://www.rfc-editor.org/v3test/rfc9000-Table-7-zero-width-space.html
   https://www.rfc-editor.org/v3test/rfc9000-Table-7-zero-width-space.pdf

Thank you!

RFC Editor/lb

> On May 18, 2021, at 3:29 PM, Martin Thomson via C430 <c430@rfc-editor.org> wrote:
> 
> Hi Sandy,  Thanks for going through this so thoroughly.
> 
> On Wed, May 19, 2021, at 05:37, Sandy Ginoza via C430 wrote:
>> Hi Amanda, Martin,
>> 
>>> On May 18, 2021, at 8:56 AM, Amanda Baber via RT <iana-matrix@iana.org> wrote:
>>> 
>>> Hi Sandy,
>>> 
>>> Do the authors prefer to not include 0x1XX in the registry? I believe we would at least need a note, if not an entry. It's not clear to me whether this is a kind of reservation or a description of what can be registered.
>> 
>> Sorry for not closing this out; thanks for the followup.  I’m including 
>> Martin (via the c430 list) on the thread.
>> 
>> Martin, please verify that the XXX in Section 19.8 is intentional. 
>> 
>>   STREAM frames implicitly create a stream and carry stream data. The 
>>   Type field in the STREAM frame takes the form 0b00001XXX (or the 
>>   set of values from 0x08 to 0x0f).
> 
> Yeah, I don't *like* this, but in this case it is important that we mark out the individual bits.  (The registry can use 0x08-0x0f as described.)
> 
> One thing here; in the registry this is 0x08-0x0F (uppercase), which is not consistent with the other entries.
> 
> (As for the other actions, item (2) was done.  Item (3) (CRYPTO_ERROR) needs to be added.)
> -- 
> C430 mailing list
> C430@rfc-editor.org
> https://www.rfc-editor.org/mailman/listinfo/c430