IETF Logo Mail Archive

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

Ted Hardie <ted.ietf@gmail.com> Mon, 25 January 2021 17:40 UTC

Return-Path: <ted.ietf@gmail.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 506FB3A1663 for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 09:40:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 H70sewukMea8 for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 09:40:52 -0800 (PST)
Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 267A43A162C for <rtcweb@ietf.org>; Mon, 25 Jan 2021 09:40:51 -0800 (PST)
Received: by mail-ot1-x32a.google.com with SMTP id e70so13510110ote.11 for <rtcweb@ietf.org>; Mon, 25 Jan 2021 09:40:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=A698PLPyK8Z9C5/qQPUSCUa5GbMlAW/6TTyCpJ7wR+8=; b=u7Z/z7367hx2/VQyHWnK3zyhT7CofO6ijCrfrKErwRrxa2nyTvy47LHkTxzRHJOl7U Yg31oawp7eMrvASRCfq2ggQx/pHlthvkiNLmeDlIIaFSIhQ4pE9xxH+FNZmtOaofqat9 uwuzPlv0qjg2YM8pGVidxxPN4UX1RqUOe+gfKsqAMo3GD0GIj6gGXq1DvqTSfLcTG3/N UIAKKd731pIku7gyqE1QLKWQuKTJ17SPMdFbZNTvospQW8WTuyqFlNSvxDuKTZ2vQAUH mGWaxHeRLhKV7TCN/e6TvbItug6E31bXmWd3AiUlyau60VrMdThx+Rd1Wvw1N5MdtWXc TQNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=A698PLPyK8Z9C5/qQPUSCUa5GbMlAW/6TTyCpJ7wR+8=; b=r5GVYSUu2LtS2rFEyKgbXMXBmbxDED+NCMa09IvqY5xHmuMq0fLBwVnw88KJw6uSmY iyl8huIgYjdIZDHxoTZ606eu4TuMPaxQxaKKQcyRDjqNtZd52goEim6bmKeWoy24WqUt uIsjInyqDpVX6tlqJ72QeyByFPxGIZV7BDJkKbqSTWR6eERCCZWZ7VWXlr557S+ohlrO BYnAaZngIgdfdalbHEt94Y1fz62+6p6uQpJoA1IEfOc1ielDg2Xmk+vDoN1r5T2+UWEk izzNb3uo3M2MVlyb+a9c8LQvaAudepeVp/1hFlxMUWwyFiAtSzVQ9YsqMG2HM7OT+WCa XymA==
X-Gm-Message-State: AOAM530G2hwzR9sGQKnd6HCcEtEHaHOWjQwhIr5pROyatLoJFLfYOyu6 ifbvIKJ+aYKEH/UFFu8AL9Cp+nSadXUsfuOwp6I=
X-Google-Smtp-Source: ABdhPJypA1KLaq/F4TrB+GVaWk69FnkZ/fZjQ+HoQwUtSvKG5vDXLYgPvV/cvVv4AMINgvba0Lp2xrXIg/IkfELBvyI=
X-Received: by 2002:a9d:4786:: with SMTP id b6mr1192800otf.269.1611596450467; Mon, 25 Jan 2021 09:40:50 -0800 (PST)
MIME-Version: 1.0
References: <20210125092848.3AF95F40764@rfc-editor.org>
In-Reply-To: <20210125092848.3AF95F40764@rfc-editor.org>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Mon, 25 Jan 2021 09:40:24 -0800
Message-ID: <CA+9kkMBJTN-U0WNdSRJ6PdOPBHwayfWxUGebThr+iHOM_QmYqQ@mail.gmail.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: Randell Jesup <randell-ietf@jesup.org>, Salvatore Loreto <salvatore.loreto@ericsson.com>, Michael Tuexen <tuexen@fh-muenster.de>, "Murray S. Kucherawy" <superuser@gmail.com>, Barry Leiba <barryleiba@computer.org>, sean+ietf@sn3rd.com, boivie@google.com, RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f392c405b9bd09c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/pv1Fy7onwjbhe8BrXdC7yMSGf_k>
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 17:41:00 -0000

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.

Just my personal opinion,

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