[rtcweb] [Technical Errata Reported] RFC8832 (6411)
RFC Errata System <rfc-editor@rfc-editor.org> Mon, 25 January 2021 09:28 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 0BEA83A0D70
for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 01:28:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.979
X-Spam-Level:
X-Spam-Status: No, score=0.979 tagged_above=-999 required=5
tests=[CTE_8BIT_MISMATCH=0.999, RCVD_IN_MSPIKE_H4=-0.01,
RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, 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 ZFDVxFwXakGi for <rtcweb@ietfa.amsl.com>;
Mon, 25 Jan 2021 01:28:51 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49])
(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id E348B3A0D6F
for <rtcweb@ietf.org>; Mon, 25 Jan 2021 01:28:51 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30)
id 3AF95F40764; Mon, 25 Jan 2021 01:28:48 -0800 (PST)
To: randell-ietf@jesup.org, salvatore.loreto@ericsson.com,
tuexen@fh-muenster.de, superuser@gmail.com, barryleiba@computer.org,
sean+ietf@sn3rd.com, ted.ietf@gmail.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: boivie@google.com, rtcweb@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset=UTF-8
Message-Id: <20210125092848.3AF95F40764@rfc-editor.org>
Date: Mon, 25 Jan 2021 01:28:48 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/pAZE1afutz4wk97hdxiKhhJY-HA>
X-Mailman-Approved-At: Mon, 25 Jan 2021 09:36:59 -0800
Subject: [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 09:28:53 -0000
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] [Technical Errata Reported] RFC8832 (641… RFC Errata System
- Re: [rtcweb] [Technical Errata Reported] RFC8832 … Ted Hardie
- Re: [rtcweb] [Technical Errata Reported] RFC8832 … Barry Leiba
- Re: [rtcweb] [Technical Errata Reported] RFC8832 … Michael Tuexen
- Re: [rtcweb] [Technical Errata Reported] RFC8832 … Michael Tuexen
- Re: [rtcweb] [Technical Errata Reported] RFC8832 … Harald Alvestrand