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

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 07 November 2023 10:26 UTC

Return-Path: <wwwrun@rfcpa.amsl.com>
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 240E5C17DC11; Tue, 7 Nov 2023 02:26:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.534
X-Spam-Level:
X-Spam-Status: No, score=0.534 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_HELO_SOFTFAIL=0.732, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 I9mFp9Zxu1dL; Tue, 7 Nov 2023 02:26:06 -0800 (PST)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (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 57D8BC1705E2; Tue, 7 Nov 2023 02:26:01 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id F1CEB55E6C; Tue, 7 Nov 2023 02:26:00 -0800 (PST)
To: boivie@google.com, randell-ietf@jesup.org, salvatore.loreto@ericsson.com, tuexen@fh-muenster.de
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: francesca.palombini@ericsson.com, iesg@ietf.org, rtcweb@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20231107102600.F1CEB55E6C@rfcpa.amsl.com>
Date: Tue, 07 Nov 2023 02:26:00 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/HD9cS6Xc4NgZWkE4cn5BNzyMnEQ>
Subject: [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 10:26:11 -0000

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.
---
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