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

Harald Alvestrand <harald@alvestrand.no> Tue, 26 January 2021 09:28 UTC

Return-Path: <harald@alvestrand.no>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F68B3A086E for <rtcweb@ietfa.amsl.com>; Tue, 26 Jan 2021 01:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level:
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rmDxS7we4xtu for <rtcweb@ietfa.amsl.com>; Tue, 26 Jan 2021 01:28:03 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F6223A017E for <rtcweb@ietf.org>; Tue, 26 Jan 2021 01:28:03 -0800 (PST)
Received: from [192.168.3.157] (unknown [188.113.93.42]) by mork.alvestrand.no (Postfix) with ESMTPSA id BA9F87C64F6 for <rtcweb@ietf.org>; Tue, 26 Jan 2021 10:28:01 +0100 (CET)
To: rtcweb@ietf.org
References: <20210125092848.3AF95F40764@rfc-editor.org>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <e3c7aa2c-c3c6-f44f-fbd8-c017eae0f4d2@alvestrand.no>
Date: Tue, 26 Jan 2021 10:28:01 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <20210125092848.3AF95F40764@rfc-editor.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/M1IB6a8UxuBK3Dxj3PKgEbTpOBk>
Subject: Re: [rtcweb] [Technical Errata Reported] RFC8832 (6411)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 26 Jan 2021 09:28:05 -0000

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