Re: [rtcweb] [Technical Errata Reported] RFC8832 (6411)

I recommend this to be "accepted, held for update".

Just to have said this before the merge (which may be late or may be 
never) ... I see no reason for allowing "unless otherwise stated", and 
the new sentence should come before the existing paragraph, not after it.

On 1/25/21 10:28 AM, RFC Errata System wrote:
> The following errata report has been submitted for RFC8832,
> "WebRTC Data Channel Establishment Protocol".
>
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6411
>
> --------------------------------------
> Type: Technical
> Reported by: Victor Boivie <boivie@google.com>
>
> Section: 5
>
> Original Text
> -------------
> 5.  Message Formats
>
>     Every Data Channel Establishment Protocol message starts with a one
>     byte field called "Message Type" which indicates the type of the
>     message.  The corresponding values are managed by IANA (see
>     Section 8.2.1).
>
> Corrected Text
> --------------
> 5.  Message Formats
>
>     Every Data Channel Establishment Protocol message starts with a one
>     byte field called "Message Type" which indicates the type of the
>     message.  The corresponding values are managed by IANA (see
>     Section 8.2.1).
>
>     All integer fields in an Data Channel Establishment Protocol message
>     MUST be transmitted in network byte order, unless otherwise stated.
>
> Notes
> -----
> The byte order of integer fields in the protocol messages is not defined.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". If necessary, please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> can log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC8832 (draft-ietf-rtcweb-data-protocol-09)
> --------------------------------------
> Title               : WebRTC Data Channel Establishment Protocol
> Publication Date    : January 2021
> Author(s)           : R. Jesup, S. Loreto, M. Tüxen
> Category            : PROPOSED STANDARD
> Source              : Real-Time Communication in WEB-browsers
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb