IETF Logo Mail Archive

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

Michael Tuexen <tuexen@fh-muenster.de> Mon, 25 January 2021 18:37 UTC

Return-Path: <tuexen@fh-muenster.de>
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 8F1373A172D for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 10:37:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.42
X-Spam-Level:
X-Spam-Status: No, score=0.42 tagged_above=-999 required=5 tests=[KHOP_HELO_FCRDNS=0.399, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no 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 CjY6lR6PI0pK for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 10:37:14 -0800 (PST)
Received: from drew.franken.de (drew.ipv6.franken.de [IPv6:2001:638:a02:a001:20e:cff:fe4a:feaa]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D05863A172C for <rtcweb@ietf.org>; Mon, 25 Jan 2021 10:37:12 -0800 (PST)
Received: from [IPv6:2a02:8109:1140:c3d:8cdb:3c2b:1f77:6217] (unknown [IPv6:2a02:8109:1140:c3d:8cdb:3c2b:1f77:6217]) (Authenticated sender: macmic) by mail-n.franken.de (Postfix) with ESMTPSA id CE86B7220C6D1; Mon, 25 Jan 2021 19:37:08 +0100 (CET)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <65E4DC3A-8FC9-48D3-9D2D-9EF62117A8D7@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_A7EA20FE-A82F-4774-B4C5-2189DEE9BD61"; protocol="application/pkcs7-signature"; micalg="sha-256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.40.0.2.32\))
Date: Mon, 25 Jan 2021 19:37:08 +0100
In-Reply-To: <CA+9kkMBJTN-U0WNdSRJ6PdOPBHwayfWxUGebThr+iHOM_QmYqQ@mail.gmail.com>
Cc: RFC Errata System <rfc-editor@rfc-editor.org>, Randell Jesup <randell-ietf@jesup.org>, Salvatore Loreto <salvatore.loreto@ericsson.com>, "Murray S. Kucherawy" <superuser@gmail.com>, Barry Leiba <barryleiba@computer.org>, sean+ietf@sn3rd.com, boivie@google.com, RTCWeb IETF <rtcweb@ietf.org>
To: Ted Hardie <ted.ietf@gmail.com>
References: <20210125092848.3AF95F40764@rfc-editor.org> <CA+9kkMBJTN-U0WNdSRJ6PdOPBHwayfWxUGebThr+iHOM_QmYqQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/oq3MW3R_EUJtUqgukv91kbtS_QY>
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: Mon, 25 Jan 2021 18:37:18 -0000

> On 25. Jan 2021, at 18:40, Ted Hardie <ted.ietf@gmail.com> wrote:
> 
> Since the Data Channel Establishment Protocol depends on SCTP, which requires Network Byte Order (RFC 4960, Section 3), I do not believe that this erratum is needed.  I recommend it be rejected.
The text in RFC 4960 Section 3 covers the fields of the SCTP protocol, it does not cover
the payload, which is DCEP.
> 
> Just my personal opinion,
In my opinion we just forgot to state that all fields should be in network byte order.
The fields are definitely intended to be in network byte order.
Therefore, I think the report is valid.

Best regards
Michael
> 
> regards,
> 
> Ted
> 
> On Mon, Jan 25, 2021 at 1:28 AM RFC Errata System <rfc-editor@rfc-editor.org> 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

v2.23.0 | Report a Bug | By Email