IETF Logo Mail Archive

Re: [rtcweb] [Errata Held for Document Update] RFC8832 (6411)

tuexen@fh-muenster.de Tue, 07 November 2023 12:31 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 3AB87C1D471D; Tue, 7 Nov 2023 04:31:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.907
X-Spam-Level:
X-Spam-Status: No, score=-6.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bSKy81M6WU-2; Tue, 7 Nov 2023 04:31:44 -0800 (PST)
Received: from mx-out-02.fh-muenster.de (mx-out-02.fh-muenster.de [212.201.120.206]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11DB3C0A856B; Tue, 7 Nov 2023 04:31:21 -0800 (PST)
Received: from mail-director-01.fh-muenster.de (mail-director-01.fh-muenster.de [185.149.215.227]) by mx-out-02.fh-muenster.de (Postfix) with ESMTPS id 404EEE02A8; Tue, 7 Nov 2023 13:30:48 +0100 (CET)
Received: from smtpclient.apple (dhcp-9201.meeting.ietf.org [31.133.146.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: tuexen) by mail-director-01.fh-muenster.de (Postfix) with ESMTPSA id 8A4251A0064; Tue, 7 Nov 2023 13:30:47 +0100 (CET)
Content-Type: multipart/signed; boundary="Apple-Mail=_DDA54EFE-461F-4AE5-BC39-C576A3900391"; protocol="application/pkcs7-signature"; micalg="sha-256"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
From: tuexen@fh-muenster.de
In-Reply-To: <20231107102600.F1CEB55E6C@rfcpa.amsl.com>
Date: Tue, 07 Nov 2023 13:30:46 +0100
Cc: Victor Boivie <boivie@google.com>, randell-ietf@jesup.org, salvatore.loreto@ericsson.com, francesca.palombini@ericsson.com, iesg@ietf.org, rtcweb@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3D37A14-3CB1-4183-A76C-433E807B262A@fh-muenster.de>
References: <20231107102600.F1CEB55E6C@rfcpa.amsl.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/Hsbhy0asrPRisJ6hkdatoeSVQxc>
Subject: Re: [rtcweb] [Errata Held for Document Update] RFC8832 (6411)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.39
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, 07 Nov 2023 12:31:48 -0000

> On Nov 7, 2023, at 11:26, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> The following errata report has been held for document update 
> for RFC8832, "WebRTC Data Channel Establishment Protocol". 
> 
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6411
> 
> --------------------------------------
> Status: Held for Document Update
> Type: Technical
> 
> Reported by: Victor Boivie <boivie@google.com>
> Date Reported: 2021-01-25
> Held by: Francesca Palombini (IESG)
> 
> 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
> -----
> Submitter's note: The byte order of integer fields in the protocol messages is not defined.
Correct, that statement is missing.

Thanks for reporting.

Best regards
Michael
> ---
> Verifier's note: the byte order in the protocol messages is defined, since Data Channel Establishment Protocol depends on SCTP, which requires Network Byte Order (RFC 4960, Section 3). However, since this could be considered an omission that might have been corrected if it had been caught at the time of publication, I am marking it "Hold for document update".
> 
> --------------------------------------
> 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