[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)

[Sandy Ginoza <[e-mail]>]

Hi Martin and Sean,

Please see the discussion with IANA below and let us know if any updates needed here.

Thanks,
Sandy 


> On Apr 29, 2021, at 3:56 PM, Amanda Baber via RT <[e-mail]> wrote:
> 
> Hi Sandy,
> 
> On Thu Apr 29 21:46:15 2021, [e-mail] wrote:
>> Hi Amanda,
>> 
>> Regarding the "QUIC Transport Error Codes“ registry:
>> https://www.iana.org/assignments/quic/quic.xhtml#quic-transport-error-
>> codes <https://www.iana.org/assignments/quic/quic.xhtml#quic-
>> transport-error-codes>
>> 
>> 
>> For section 20.1 <https://www.ietf.org/archive/id/draft-ietf-quic-
>> transport-34.html#section-20.1>, does anything need to be marked on
>> the IANA page regarding this range?  It’s not listed in the IANA
>> Considerations section — it’s only mentioned in section 20.1.  Should
>> anything appear in the IANA Considerations section or is this just
>> guidance in the doc for IANA?
>> 
>> CRYPTO_ERROR (0x1XX):
>> The cryptographic handshake failed. A range of 256 values is reserved
>> for carrying error codes specific to the cryptographic handshake that
>> is used. Codes for errors occurring when TLS is used for the crypto
>> handshake are described in Section 4.8 of [QUIC-TLS
>> <https://www.ietf.org/archive/id/draft-ietf-quic-transport-
>> 34.html#QUIC-TLS>].
> 
> It does look like 0x100-0x1FF (or possibly 0x0100-0x01FF, or 0x01xx; I think that for the HTTP/3 document they wanted padding to the byte?) does need to be recorded in the registry in some form. How would they want this entry filled in? 
> 
>> Also, would you please update the capitalization of the description to
>> match what appears in the I-D and the other items in the registry:
>> 
>> https://www.ietf.org/archive/id/draft-ietf-quic-transport-
>> 34.html#iana-error-table <https://www.ietf.org/archive/id/draft-ietf-
>> quic-transport-34.html#iana-error-table>
>> 
>> 
>> IANA:
>> 0x00    NO_ERROR        no error
>> 
>> 
>> Current doc (caps was used in the original I-D):
>> 0x00    NO_ERROR        No error
> 
> Done:
> 
> https://www.iana.org/assignments/quic/quic.xhtml#quic-transport-error-codes
> 
> thanks,
> Amanda
> 
> 
>> Thanks!
>> Sandy
>> 
>> 
>> 
>> 
>>> On Feb 11, 2021, at 8:32 PM, Amanda Baber via RT <drafts-
>>> [e-mail]> wrote:
>>> 
>>> RFC Editor:
>>> 
>>> NOTE: with the authors' permission, we've added padding to the values
>>> in Table 7 to match other QUIC registries (e.g. 0x00 instead of 0x0)
>>> and changed "Received" in that table to "received."
>>> 
>>> We've completed the registry actions for the following RFC-to-be:
>>> 
>>> draft-ietf-quic-transport-34
>>> 
>>> IANA has created the QUIC Versions, QUIC Transport Parameters, QUIC
>>> Frame Types, and QUIC Transport Error Codes under the "QUIC" heading
>>> at
>>> 
>>> Please see
>>> https://www.iana.org/assignments/quic
>>> 
>>> Please reply to this message to acknowledge receipt of these actions.
>>> 
>>> Please let us know when an RFC number has been assigned and the date
>>> of publication by sending a new message to <drafts-update-
>>> [e-mail]>.
>>> 
>>> Thanks,
>>> 
>>> Amanda Baber
>>> Lead IANA Services Specialist
>>> 
>