
From nobody Mon Jan 18 13:40:35 2021
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 B16F53A160C; Mon, 18 Jan 2021 13:40:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 9q6GmjRiYwu7; Mon, 18 Jan 2021 13:40:22 -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 418AB3A160E; Mon, 18 Jan 2021 13:39:01 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 0DD41F4074E; Mon, 18 Jan 2021 13:38:46 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118213846.0DD41F4074E@rfc-editor.org>
Date: Mon, 18 Jan 2021 13:38:46 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/YUGKc5Fh4e-cn1nOZp1npupKQWM>
Subject: [rtcweb] =?utf-8?q?RFC_8825_on_Overview=3A_Real-Time_Protocols_f?= =?utf-8?q?or_Browser-Based_Applications?=
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, 18 Jan 2021 21:40:30 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8825

        Title:      Overview: Real-Time Protocols for Browser-Based 
                    Applications 
        Author:     H. Alvestrand
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    harald@alvestrand.no
        Pages:      17
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-overview-19.txt

        URL:        https://www.rfc-editor.org/info/rfc8825

        DOI:        10.17487/RFC8825

This document gives an overview and context of a protocol suite
intended for use with real-time applications that can be deployed in
browsers -- "real-time communication on the Web".

It intends to serve as a starting and coordination point to make sure
that (1) all the parts that are needed to achieve this goal are
findable and (2) the parts that belong in the Internet protocol suite
are fully specified and on the right publication track.

This document is an applicability statement -- it does not itself
specify any protocol, but it specifies which other specifications
implementations are supposed to follow to be compliant with Web
Real-Time Communication (WebRTC).

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Jan 18 13:40:52 2021
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 618773A11A1; Mon, 18 Jan 2021 13:40:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 XXIJFVs84HMx; Mon, 18 Jan 2021 13:40:38 -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 BC97A3A10E0; Mon, 18 Jan 2021 13:39:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 8E835F407A7; Mon, 18 Jan 2021 13:39:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118213900.8E835F407A7@rfc-editor.org>
Date: Mon, 18 Jan 2021 13:39:00 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/YmbvIIVLqScWJ8O8W79U9DoSH-E>
Subject: [rtcweb] =?utf-8?q?RFC_8826_on_Security_Considerations_for_WebRT?= =?utf-8?q?C?=
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, 18 Jan 2021 21:40:47 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8826

        Title:      Security Considerations for WebRTC 
        Author:     E. Rescorla
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    ekr@rtfm.com
        Pages:      21
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-security-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8826

        DOI:        10.17487/RFC8826

WebRTC is a protocol suite for use with real-time applications that
can be deployed in browsers -- "real-time communication on the Web". 
This document defines the WebRTC threat model and analyzes the
security threats of WebRTC in that model.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Jan 18 15:28:06 2021
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 456633A0CD4; Mon, 18 Jan 2021 15:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 snbG9iwnIZJd; Mon, 18 Jan 2021 15:28:04 -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 DDA423A0A1D; Mon, 18 Jan 2021 15:28:03 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9133CF40779; Mon, 18 Jan 2021 15:27:48 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118232748.9133CF40779@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:27:48 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/sVkrm7u2vsEUlN9NaZE6lohqvsg>
Subject: [rtcweb] =?utf-8?q?RFC_8828_on_WebRTC_IP_Address_Handling_Requir?= =?utf-8?q?ements?=
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, 18 Jan 2021 23:28:05 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8828

        Title:      WebRTC IP Address Handling Requirements 
        Author:     J. Uberti,
                    G. Shieh
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    justin@uberti.name,
                    guoweis@gmail.com
        Pages:      9
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-ip-handling-12.txt

        URL:        https://www.rfc-editor.org/info/rfc8828

        DOI:        10.17487/RFC8828

This document provides information and requirements for how IP
addresses should be handled by Web Real-Time Communication (WebRTC)
implementations.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Jan 18 15:29:19 2021
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 B515C3A1154; Mon, 18 Jan 2021 15:29:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level: 
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, 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 Ia-mlcV-9AWI; Mon, 18 Jan 2021 15:29:09 -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 F33DA3A10C7; Mon, 18 Jan 2021 15:28:53 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id A3C23F4077C; Mon, 18 Jan 2021 15:28:38 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118232838.A3C23F4077C@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:28:38 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/ZpGyq74NTjyJp7eUC4zYtcyYnlQ>
Subject: [rtcweb] =?utf-8?q?RFC_8831_on_WebRTC_Data_Channels?=
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, 18 Jan 2021 23:29:17 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8831

        Title:      WebRTC Data Channels 
        Author:     R. Jesup,
                    S. Loreto,
                    M. Tüxen
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    randell-ietf@jesup.org,
                    salvatore.loreto@ericsson.com,
                    tuexen@fh-muenster.de
        Pages:      14
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-data-channel-13.txt

        URL:        https://www.rfc-editor.org/info/rfc8831

        DOI:        10.17487/RFC8831

The WebRTC framework specifies protocol support for direct,
interactive, rich communication using audio, video, and data between
two peers' web browsers. This document specifies the non-media data
transport aspects of the WebRTC framework. It provides an
architectural overview of how the Stream Control Transmission
Protocol (SCTP) is used in the WebRTC context as a generic transport
service that allows web browsers to exchange generic data from peer
to peer.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Jan 18 15:29:47 2021
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 B08523A1022; Mon, 18 Jan 2021 15:29:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.902
X-Spam-Level: 
X-Spam-Status: No, score=-0.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, 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 mGJP36czjxdI; Mon, 18 Jan 2021 15:29:38 -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 E2D613A0FC7; Mon, 18 Jan 2021 15:29:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 99F6BF4079D; Mon, 18 Jan 2021 15:29:00 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118232900.99F6BF4079D@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:29:00 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/vVAP4Ulq2MhauTPnzm33OG-_WDw>
Subject: [rtcweb] =?utf-8?q?RFC_8832_on_WebRTC_Data_Channel_Establishment?= =?utf-8?q?_Protocol?=
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, 18 Jan 2021 23:29:45 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8832

        Title:      WebRTC Data Channel Establishment Protocol 
        Author:     R. Jesup,
                    S. Loreto,
                    M. Tüxen
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    randell-ietf@jesup.org,
                    salvatore.loreto@ericsson.com,
                    tuexen@fh-muenster.de
        Pages:      12
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-data-protocol-09.txt

        URL:        https://www.rfc-editor.org/info/rfc8832

        DOI:        10.17487/RFC8832

The WebRTC framework specifies protocol support for direct
interactive rich communication using audio, video, and data between
two peers' web browsers. This document specifies a simple protocol
for establishing symmetric data channels between the peers. It uses a
two-way handshake and allows sending of user data without waiting for
the handshake to complete.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Jan 18 15:30:37 2021
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 2FF103A126C; Mon, 18 Jan 2021 15:30:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 DSs55YvlxcYz; Mon, 18 Jan 2021 15:30:28 -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 9138A3A1164; Mon, 18 Jan 2021 15:29:45 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 48583F4078E; Mon, 18 Jan 2021 15:29:30 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118232930.48583F4078E@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:29:30 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/En7f9MHQlhWqbuahg_y_6VJbCjo>
Subject: [rtcweb] =?utf-8?q?RFC_8833_on_Application-Layer_Protocol_Negoti?= =?utf-8?q?ation_=28ALPN=29_for_WebRTC?=
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, 18 Jan 2021 23:30:36 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8833

        Title:      Application-Layer Protocol Negotiation (ALPN) for 
                    WebRTC 
        Author:     M. Thomson
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    martin.thomson@gmail.com
        Pages:      6
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-alpn-04.txt

        URL:        https://www.rfc-editor.org/info/rfc8833

        DOI:        10.17487/RFC8833

This document specifies two Application-Layer Protocol Negotiation
(ALPN) labels for use with Web Real-Time Communication (WebRTC).  The
"webrtc" label identifies regular WebRTC: a DTLS session that is used
to establish keys for the Secure Real-time Transport Protocol (SRTP)
or to establish data channels using the Stream Control Transmission
Protocol (SCTP) over DTLS.  The "c-webrtc" label describes the same
protocol, but the peers also agree to maintain the confidentiality of
the media by not sharing it with other applications.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Jan 18 15:31:22 2021
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 5483C3A14FC; Mon, 18 Jan 2021 15:31:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 svMaqpMLXpmw; Mon, 18 Jan 2021 15:31:09 -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 C32123A113A; Mon, 18 Jan 2021 15:30:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 83008F4079C; Mon, 18 Jan 2021 15:29:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118232958.83008F4079C@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:29:58 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/yO4FQdozNYc3QAMfphqnP8hQyc0>
Subject: [rtcweb] =?utf-8?q?RFC_8834_on_Media_Transport_and_Use_of_RTP_in?= =?utf-8?q?_WebRTC?=
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, 18 Jan 2021 23:31:17 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8834

        Title:      Media Transport and Use of RTP in WebRTC 
        Author:     C. Perkins,
                    M. Westerlund,
                    J. Ott
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    csp@csperkins.org,
                    magnus.westerlund@ericsson.com,
                    ott@in.tum.de
        Pages:      39
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-rtp-usage-26.txt

        URL:        https://www.rfc-editor.org/info/rfc8834

        DOI:        10.17487/RFC8834

The framework for Web Real-Time Communication (WebRTC) provides
support for direct interactive rich communication using audio, video,
text, collaboration, games, etc. between two peers' web browsers.
This memo describes the media transport aspects of the WebRTC
framework. It specifies how the Real-time Transport Protocol (RTP) is
used in the WebRTC context and gives requirements for which RTP
features, profiles, and extensions need to be supported.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Jan 18 15:31:51 2021
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 975D23A12D5; Mon, 18 Jan 2021 15:31:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 zOauLQCIY5i6; Mon, 18 Jan 2021 15:31:40 -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 20ED43A1180; Mon, 18 Jan 2021 15:30:37 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id CEA3AF40790; Mon, 18 Jan 2021 15:30:21 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118233021.CEA3AF40790@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:30:21 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/E7rl3W6GLN5Xo_lTOpPEJe1yRsw>
Subject: [rtcweb] =?utf-8?q?RFC_8835_on_Transports_for_WebRTC?=
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, 18 Jan 2021 23:31:48 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8835

        Title:      Transports for WebRTC 
        Author:     H. Alvestrand
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    harald@alvestrand.no
        Pages:      13
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-transports-17.txt

        URL:        https://www.rfc-editor.org/info/rfc8835

        DOI:        10.17487/RFC8835

This document describes the data transport protocols used by Web
Real-Time Communication (WebRTC), including the protocols used for
interaction with intermediate boxes such as firewalls, relays, and
NAT boxes.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Mon Jan 18 15:56:55 2021
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 610043A0CE1; Mon, 18 Jan 2021 15:56:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 SPavllkwQ0F2; Mon, 18 Jan 2021 15:56:48 -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 B75633A0CDF; Mon, 18 Jan 2021 15:56:48 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6A64FF4076B; Mon, 18 Jan 2021 15:56:33 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210118235633.6A64FF4076B@rfc-editor.org>
Date: Mon, 18 Jan 2021 15:56:33 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/FawDK0GhYPNSbz5cxoKc6TGZAhY>
Subject: [rtcweb] =?utf-8?q?RFC_8827_on_WebRTC_Security_Architecture?=
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, 18 Jan 2021 23:56:50 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8827

        Title:      WebRTC Security Architecture 
        Author:     E. Rescorla
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    ekr@rtfm.com
        Pages:      35
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-security-arch-20.txt

        URL:        https://www.rfc-editor.org/info/rfc8827

        DOI:        10.17487/RFC8827

This document defines the security architecture for WebRTC, a
protocol suite intended for use with real-time applications that can
be deployed in browsers -- "real-time communication on the Web".

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Tue Jan 19 14:55:24 2021
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 462143A1A4E; Tue, 19 Jan 2021 14:55:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 X0d0QbqfXR5O; Tue, 19 Jan 2021 14:55:09 -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 CE1753A18EA; Tue, 19 Jan 2021 14:54:45 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9BE75F40761; Tue, 19 Jan 2021 14:54:29 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210119225429.9BE75F40761@rfc-editor.org>
Date: Tue, 19 Jan 2021 14:54:29 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/Zr7HiSuvVBxgD6CZD0kvWfwrN8I>
Subject: [rtcweb] =?utf-8?q?RFC_8854_on_WebRTC_Forward_Error_Correction_R?= =?utf-8?q?equirements?=
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: Tue, 19 Jan 2021 22:55:17 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8854

        Title:      WebRTC Forward Error Correction Requirements 
        Author:     J. Uberti
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    justin@uberti.name
        Pages:      10
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-fec-10.txt

        URL:        https://www.rfc-editor.org/info/rfc8854

        DOI:        10.17487/RFC8854

This document provides information and requirements for the use of
Forward Error Correction (FEC) by WebRTC implementations.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Wed Jan 20 16:30:31 2021
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 606D13A1640; Wed, 20 Jan 2021 16:30:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.92
X-Spam-Level: 
X-Spam-Status: No, score=-1.92 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 oNmAYh7FUNDk; Wed, 20 Jan 2021 16:30:23 -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 C5FA43A163E; Wed, 20 Jan 2021 16:30:23 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 7ABF3F4071D; Wed, 20 Jan 2021 16:30:06 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, rtcweb@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20210121003006.7ABF3F4071D@rfc-editor.org>
Date: Wed, 20 Jan 2021 16:30:06 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/PMX70NOvlJM0dYz5sIL38u7Ju_Q>
Subject: [rtcweb] =?utf-8?q?RFC_8829_on_JavaScript_Session_Establishment_?= =?utf-8?q?Protocol_=28JSEP=29?=
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: Thu, 21 Jan 2021 00:30:26 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8829

        Title:      JavaScript Session Establishment Protocol (JSEP) 
        Author:     J. Uberti,
                    C. Jennings,
                    E. Rescorla, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2021
        Mailbox:    justin@uberti.name,
                    fluffy@iii.ca,
                    ekr@rtfm.com
        Pages:      95
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rtcweb-jsep-26.txt

        URL:        https://www.rfc-editor.org/info/rfc8829

        DOI:        10.17487/RFC8829

This document describes the mechanisms for allowing a JavaScript
application to control the signaling plane of a multimedia session
via the interface specified in the W3C RTCPeerConnection API and
discusses how this relates to existing signaling protocols.

This document is a product of the Real-Time Communication in WEB-browsers Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Thu Jan 21 06:59:22 2021
Return-Path: <sean@sn3rd.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 21B093A0F61 for <rtcweb@ietfa.amsl.com>; Thu, 21 Jan 2021 06:59:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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 (1024-bit key) header.d=sn3rd.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 75YQlHJKg8zh for <rtcweb@ietfa.amsl.com>; Thu, 21 Jan 2021 06:59:19 -0800 (PST)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 1429C3A0F5E for <rtcweb@ietf.org>; Thu, 21 Jan 2021 06:59:19 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id r9so1667786qtp.11 for <rtcweb@ietf.org>; Thu, 21 Jan 2021 06:59:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=ZhHBpUjBTuvWbj20vvQIPQi/LysBQbqf+2KclJswpY4=; b=AlFPPfN3HQ0YcQvUpBBX+VPFWfX32XnOX/6qd38WoGAPO6b25YWZBugb9lL7n2DYIY HcGFMVwEFDUa3gDRTkrWM5m7AreoQjti2Gfa4OklQxq+KSy8VuuvP6pmS9gcl0MQV2// ELtVqSv3ORut73UEq0LML7LPHei9JIZ6xcTfA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=ZhHBpUjBTuvWbj20vvQIPQi/LysBQbqf+2KclJswpY4=; b=t4S8gBAeQsgUmwSxca8BIB4baK1RkiUlnQpA9CMVvK+XLHKCdwzl2zyVJtk/ghcIoK ykPiX962CTPd2FdB9V0flVvvn+BX+bdHehuTh60Mx5DnGw/UDq7gQAvP2c5Bj1yPrTxy K1jsYgeKL7nX5HR8MeLxdBvTkZ8DB8MHc4jLJjcNzLHfnqjHfYvGR5PSOILP6bJk8E3a PWjVnxAoXUSJEKeFzMfcrxZO60AmLnwvAOEQ1X9hub4GXoAhcBPIKo6HQO9bXqygTxTY QGJTaXO3b1aN3ckHfuvWoGDP+38WUeh8oydkPLGzPQC3HqVPFp4e2qO/OTAjwdyjqKUi uFMw==
X-Gm-Message-State: AOAM531UpPPhsBczL2ntKa1d4paXUJQOIHuoexFv/MgcCXWYaHmPqQbd oUOZj60I/0vI/RAj2MvzgECeFI7AygFr8g==
X-Google-Smtp-Source: ABdhPJw5CDisumM8qBKktRfGoyCc7hReroBIBxlyQ/MbM8tfTdcGHxD6kFWyDzEWVqkZTOAGh6/qBA==
X-Received: by 2002:ac8:725a:: with SMTP id l26mr25895qtp.56.1611241157845; Thu, 21 Jan 2021 06:59:17 -0800 (PST)
Received: from [192.168.1.152] (pool-108-31-39-252.washdc.fios.verizon.net. [108.31.39.252]) by smtp.gmail.com with ESMTPSA id z30sm3557331qtd.21.2021.01.21.06.59.16 for <rtcweb@ietf.org> (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Jan 2021 06:59:16 -0800 (PST)
From: Sean Turner <sean@sn3rd.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Message-Id: <9331E58E-23EB-40B9-A70E-3586E0B4B467@sn3rd.com>
Date: Thu, 21 Jan 2021 09:59:15 -0500
To: rtcweb@ietf.org
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/gb_AS4g0n-kmqtPG3f2A_7TPntE>
Subject: [rtcweb] RTCWEB RFCs Published (aka draining cluster 238)
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: Thu, 21 Jan 2021 14:59:20 -0000

As you may have noticed over the last couple of days, all of RTCWEB=E2=80=99=
s I-D have now be published as RFCs. Congratulations to all those who =
participated.

The SDP examples draft, which was a WG draft but ended up being =
AD-sponsored after the WG closed down, is still making its way through =
the process.

Cheers,
spt=


From nobody Thu Jan 21 08:05:56 2021
Return-Path: <bernard.aboba@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 DF3D93A1250 for <rtcweb@ietfa.amsl.com>; Thu, 21 Jan 2021 08:05:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 fg6zIJrBr06J for <rtcweb@ietfa.amsl.com>; Thu, 21 Jan 2021 08:05:53 -0800 (PST)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 413343A124D for <rtcweb@ietf.org>; Thu, 21 Jan 2021 08:05:53 -0800 (PST)
Received: by mail-lf1-x12b.google.com with SMTP id b26so3229327lff.9 for <rtcweb@ietf.org>; Thu, 21 Jan 2021 08:05:53 -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=jFpBMHakHGj6TdLpo1bx+x0cN3uYqdZRCCdUmRDoVOg=; b=I07zcBdSMLyw0J9s2DY9hu8MPBGAvQU4mP7vIqnxw5LWJMz82yUl8booSxTC/xoMHw jVQn1XPOLLideipUw3gCcuRKbRcqkPySJwACy0Zs45HgMb7IHDq35KwiYcn2kBWAD8Af OICJSJN81wgXSco7hL8BDfD9ndYTsNvW6wujBeIq3OiDRTdHu3QzEoliPwAqGQ2w1/V9 spJgg8GJ9539yRQByN2LxcRuS8ZeRHwdfufcH/jFzlYSS/CGibHoWNdh3t311C4DtDyX 3D68DYt00RnMpmgEn+D5zM8FwEfNbUpRwLKWxgTx3uuWx0GRfATv7xlrM66m28erCbkT PZ2w==
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=jFpBMHakHGj6TdLpo1bx+x0cN3uYqdZRCCdUmRDoVOg=; b=j0KEleuyiJjVSn9x9rKmKlzlVeX/2Mmzi0REfR3UxpwokIVRqSnEhpMtJCRqn9ooRY OJoxPtgN6KV3PQGf3udVYY1z2QPMOe/RZes8FsC7EokoGHFS1460v2K6kg+mZVVODxd0 DpuPu2vCvyEUVubAK2NTgqHXbi5b/rVEsb6n/O0PNcAeFs7Hc6L7ECa1T7cESCE1lbDW UJxLanNr7UQs2/kwzZUKoPfL2X/NcReyr0Fwi7S0elcTn/gC4SRQU6WsPdshO2/BX5Br ouwIjFqkD82mivWM4Wm3jC1/xwG5PMUdGuKbr4vT7x60Vv7WupHy8Y5m4N6OPxrGkZzh c6EA==
X-Gm-Message-State: AOAM530oD7v4k2F4bCnVQ/B86V1dxch9kKcK1SYFvmzqbvbiTxi9wrXn 8c0ZrxhISkPnTwyJCV9WTrooYY1CHuoLcd9AwMA=
X-Google-Smtp-Source: ABdhPJxRIi2lcAra7RNptcwtt2MERoC9ySW6LETRo6i5rUOy2ahlppdsUhA2NExnKUVCNGBooatcIz8j/E68iQZVtKU=
X-Received: by 2002:a19:e30b:: with SMTP id a11mr6201611lfh.48.1611245151150;  Thu, 21 Jan 2021 08:05:51 -0800 (PST)
MIME-Version: 1.0
References: <9331E58E-23EB-40B9-A70E-3586E0B4B467@sn3rd.com>
In-Reply-To: <9331E58E-23EB-40B9-A70E-3586E0B4B467@sn3rd.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Thu, 21 Jan 2021 08:05:41 -0800
Message-ID: <CAOW+2duyhSp5bBzZScSsiVv5o1oh_vStjFKff-zKjWcuGNT6Pw@mail.gmail.com>
To: Sean Turner <sean@sn3rd.com>
Cc: RTCWeb IETF <rtcweb@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e1669b05b96b3ec1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/p6BZUAlWBPi2S61_jPkTEJ2xVsg>
Subject: Re: [rtcweb] RTCWEB RFCs Published (aka draining cluster 238)
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: Thu, 21 Jan 2021 16:05:56 -0000

--000000000000e1669b05b96b3ec1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Many thanks on the heroic efforts to unblock cluster 238.  This will also
unblock publication of the WebRTC PeerConnection API as a W3C
Recommendation.

Blocked Drain 238 - YouTube <https://www.youtube.com/watch?v=3D1A3iJnL2Das>

On Thu, Jan 21, 2021 at 6:59 AM Sean Turner <sean@sn3rd.com> wrote:

> As you may have noticed over the last couple of days, all of RTCWEB=E2=80=
=99s I-D
> have now be published as RFCs. Congratulations to all those who
> participated.
>
> The SDP examples draft, which was a WG draft but ended up being
> AD-sponsored after the WG closed down, is still making its way through th=
e
> process.
>
> Cheers,
> spt
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
>

--000000000000e1669b05b96b3ec1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">Many thanks on the heroic efforts to unbl=
ock cluster 238.=C2=A0 This will also unblock publication of the WebRTC Pee=
rConnection API as a W3C Recommendation.<div><br></div><div><a href=3D"http=
s://www.youtube.com/watch?v=3D1A3iJnL2Das">Blocked Drain 238 - YouTube</a><=
/div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Thu, Jan 21, 2021 at 6:59 AM Sean Turner &lt;<a href=3D"mailt=
o:sean@sn3rd.com">sean@sn3rd.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">As you may have noticed over the last coup=
le of days, all of RTCWEB=E2=80=99s I-D have now be published as RFCs. Cong=
ratulations to all those who participated.<br>
<br>
The SDP examples draft, which was a WG draft but ended up being AD-sponsore=
d after the WG closed down, is still making its way through the process.<br=
>
<br>
Cheers,<br>
spt<br>
_______________________________________________<br>
rtcweb mailing list<br>
<a href=3D"mailto:rtcweb@ietf.org" target=3D"_blank">rtcweb@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/rtcweb" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/rtcweb</a><br>
</blockquote></div>

--000000000000e1669b05b96b3ec1--


From nobody Fri Jan 22 17:35:36 2021
Return-Path: <superuser@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 98C7D3A1623 for <rtcweb@ietfa.amsl.com>; Fri, 22 Jan 2021 17:35:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.086
X-Spam-Level: 
X-Spam-Status: No, score=-2.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 EreZdePHhilB for <rtcweb@ietfa.amsl.com>; Fri, 22 Jan 2021 17:35:33 -0800 (PST)
Received: from mail-vs1-xe2d.google.com (mail-vs1-xe2d.google.com [IPv6:2607:f8b0:4864:20::e2d]) (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 9D3BA3A1624 for <rtcweb@ietf.org>; Fri, 22 Jan 2021 17:35:33 -0800 (PST)
Received: by mail-vs1-xe2d.google.com with SMTP id o19so4097185vsn.3 for <rtcweb@ietf.org>; Fri, 22 Jan 2021 17:35:33 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=2yEUsZvKMllHb/BxUuX8ZV6wPpcReNqNjn/t6PzN33Q=; b=deB2J8wu2ur7KfPJziiJ2uXqP6O5pxR6BY7sL5Kf/gokLMyLmWmluASQFMVgdxxD72 MWrlqcKob0jsygen8gg20zYjmYhD5MiKeNZ9HKlfA7BvxS21zlcStrelW2KiKnNLmNK2 hTMg3uOE6d+rk3Qf3rqn0dIircoG1sslKzWfG5JjS4eL8GToI6B/4g7vgY8ACtmGRJ57 c/sT/OzkAePqGp8MQHGfK9/CiS1+PiClJ5usKv3t/qKUy76WqTq3FNtBRA3Wn6vWYdkF DLsfnMrS+uCmgpFJmeVxtWwbMLGEr3wCda6uuCLfRLZ+93m+aBVlKYVpifzQtI6fPeZW RcVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=2yEUsZvKMllHb/BxUuX8ZV6wPpcReNqNjn/t6PzN33Q=; b=JnAhYlVdTjAg0rhOjIbZEmQbBKGJ1HRyJGwfECU8zlerKjtGlHJJ3V1f1tkUOx6dd8 iAuS1pWhdINSLjxe9nbiDXvoW7JeUQLLmf5DfO8yKWpyqGdwNGcJAQbHx6Kil9ynbbH4 4Jmr6tf1wUJMcyg7YG85zV/mb+eTwpl5BC7syrELWaRosHj25GYqf6AD0gqhPzUGTSHi XbteQz1yhmNG+iG+gT8jGYJXg5Ot60C1i4RZ6B4mHx9ihLNFOyG7C/E819NSJl3qBpu1 ywO56iuZJQoqZqW+wXciToq6ZdVB7NGqwUL/jpfMeXB9aBHE6uwfRf2MB6PwgmyH23pC 5unw==
X-Gm-Message-State: AOAM530IQeeACx9CDyXXynbTTgth4dXdTSZ9Ff0xBpj372+PAHwSEZsx +MISOPITQMKt5zMMY6WkbZyM1hDKJmRIDciPSvsINEjN24aC7A==
X-Google-Smtp-Source: ABdhPJyf9WuHXexGxPxIzqwGIuSIqv+rdF5CRvRssZjLoHowAyYelk5RDcDXCq553siip+rSH9KXoCoVVPxvY2PVpnk=
X-Received: by 2002:a67:eecc:: with SMTP id o12mr4259381vsp.40.1611365732413;  Fri, 22 Jan 2021 17:35:32 -0800 (PST)
MIME-Version: 1.0
From: "Murray S. Kucherawy" <superuser@gmail.com>
Date: Fri, 22 Jan 2021 17:35:21 -0800
Message-ID: <CAL0qLwYeg6_HdjVuLCdhPxtaNH4_vnE_r4Lr1p=s8uiTAu+hdQ@mail.gmail.com>
To: rtcweb@ietf.org
Content-Type: multipart/alternative; boundary="00000000000015740905b9875229"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/4N7GT-33L4neHKGBiAKCaCAmE40>
Subject: [rtcweb] Updating JSEP and BUNDLE
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: Sat, 23 Jan 2021 01:35:36 -0000

--00000000000015740905b9875229
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Colleagues,

In the final run-up to publication of C238, it was observed that the JSEP
and BUNDLE documents contradict each other in a significant way.

Rather than send them back to the working group to resolve, delaying
publication further for an unknown duration, the authors and Area Directors
involved reached consensus to publish the entire cluster as it was
originally approved, with a note added that acknowledges the contradiction
(without proposing solutions), and stating that the IETF will quickly take
up the work to publish updates.  The specific text is visible as Section
1.3 of RFC 8829 and 1.4 of RFC 8843.

The IESG intends to reconstitute the RTCWEB working group to resolve this
contradiction, with a scope to resolve only that specific issue and publish
a couple of document updates.  The plan is to have this rechartering in
place in time for a meeting at IETF 110 in March.

Below is the proposed re-chartering for the RTCWEB working group.  Feedback
on this is welcome, either on the rtcweb@ietf.org list, to me privately, or
to the IESG.  We will start the formal process of review and approval on
the next IESG telechat, and have already requested a session during IETF
110 to get the work going.


-MSK, ART AD


--


The RTCWEB working group was originally chartered to standardize mechanisms
that provide direct interactive rich communication using audio, video,
collaboration, games, etc. between two peers' web-browsers, without
requiring non-standard extensions or proprietary plug-ins.  The result was
a set of RFCs from RTCWEB, in addition to many other RFCs from other
working groups, all of which are interrelated and had to be published
together in what the RFC Editor refers to as a =E2=80=9Ccluster=E2=80=9D.  =
In the end, that
cluster comprised more than 40 RFCs and was finally published in January
2021.

During the run-up to publication of the cluster, a contradiction was
identified between what became RFCs 8829 and 8843.  A description of this
contradiction was added to both documents to highlight the problem, and
state our intention to proceed with publication but quickly initiate an
effort to publish updates to the affected documents.

The key part of the added text was as follows:

=E2=80=9CThe specific issue involves the handling of "m=3D" sections that a=
re
designated as bundle-only, as discussed in Section 4.1.1
<https://tools.ietf.org/html/rfc8829#section-4.1.1> of [RFC 8829].
Currently, there is divergence between JSEP and BUNDLE, as well as between
these specifications and existing browser implementations =E2=80=A6=E2=80=
=9D

The working group is being reconstituted to take up this contradiction,
come to consensus on a resolution, and issue Standards Track updates for
those two documents.  Updating any other document, or taking up any other
issue, is out of scope and will require IESG approval via rechartering.

--00000000000015740905b9875229
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;ma=
rgin-bottom:0pt" id=3D"gmail-docs-internal-guid-8d1b7cfb-7fff-5eae-039c-f37=
d60b46343"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0)=
;background-color:transparent;font-weight:400;font-style:normal;font-varian=
t:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"=
>Colleagues,</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-=
top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;=
color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:no=
rmal;font-variant:normal;text-decoration:none;vertical-align:baseline;white=
-space:pre-wrap">In the final run-up to publication of C238, it was observe=
d that the JSEP and BUNDLE documents contradict each other in a significant=
 way.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fo=
nt-variant:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">Rather than send them back to the working group to resolve, delay=
ing publication further for an unknown duration, the authors and Area Direc=
tors involved reached consensus to publish the entire cluster as it was ori=
ginally approved, with a note added that acknowledges the contradiction (wi=
thout proposing solutions), and stating that the IETF will quickly take up =
the work to publish updates.=C2=A0 The specific text is visible as Section =
1.3 of RFC 8829 and 1.4 of RFC 8843.</span></p><br><p dir=3D"ltr" style=3D"=
line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size=
:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-=
weight:400;font-style:normal;font-variant:normal;text-decoration:none;verti=
cal-align:baseline;white-space:pre-wrap">The IESG intends to reconstitute t=
he RTCWEB working group to resolve this contradiction, with a scope to reso=
lve only that specific issue and publish a couple of document updates.=C2=
=A0 The plan is to have this rechartering in place in time for a meeting at=
 IETF 110 in March.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;=
margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family=
:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-s=
tyle:normal;font-variant:normal;text-decoration:none;vertical-align:baselin=
e;white-space:pre-wrap">Below is the proposed re-chartering for the RTCWEB =
working group.=C2=A0 Feedback on this is welcome, either on the <a href=3D"=
mailto:rtcweb@ietf.org">rtcweb@ietf.org</a> list, to me privately, or to th=
e IESG.=C2=A0 We will start the formal process of review and approval on th=
e next IESG telechat, and have already requested a session during IETF 110 =
to get the work going.</span></p><p style=3D"line-height:1.38;margin-top:0p=
t;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:=
rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;f=
ont-variant:normal;text-decoration:none;vertical-align:baseline;white-space=
:pre-wrap"><br></span></p><p style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0=
,0);background-color:transparent;font-weight:400;font-style:normal;font-var=
iant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wr=
ap">-MSK, ART AD </span></p><p style=3D"line-height:1.38;margin-top:0pt;mar=
gin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0=
,0,0);background-color:transparent;font-weight:400;font-style:normal;font-v=
ariant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-=
wrap"><br></span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bot=
tom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);b=
ackground-color:transparent;font-weight:400;font-style:normal;font-variant:=
normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">-=
-</span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt">=
<span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background=
-color:transparent;font-weight:400;font-style:normal;font-variant:normal;te=
xt-decoration:none;vertical-align:baseline;white-space:pre-wrap"><br></span=
></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:=
0pt" id=3D"gmail-docs-internal-guid-041426c8-7fff-c814-2589-cf28fd0bd6dc"><=
span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-=
color:transparent;font-weight:400;font-style:normal;font-variant:normal;tex=
t-decoration:none;vertical-align:baseline;white-space:pre-wrap">The RTCWEB =
working group was originally chartered to standardize mechanisms that provi=
de direct interactive rich communication using audio, video, collaboration,=
 games, etc. between two peers&#39; web-browsers, without requiring non-sta=
ndard extensions or proprietary plug-ins.=C2=A0 The result was a set of RFC=
s from RTCWEB, in addition to many other RFCs from other working groups, al=
l of which are interrelated and had to be published together in what the RF=
C Editor refers to as a =E2=80=9Ccluster=E2=80=9D.=C2=A0 In the end, that c=
luster comprised more than 40 RFCs and was finally published in January 202=
1.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;ma=
rgin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(=
0,0,0);background-color:transparent;font-weight:400;font-style:normal;font-=
variant:normal;text-decoration:none;vertical-align:baseline;white-space:pre=
-wrap">During the run-up to publication of the cluster, a contradiction was=
 identified between what became RFCs 8829 and 8843.=C2=A0 A description of =
this contradiction was added to both documents to highlight the problem, an=
d state our intention to proceed with publication but quickly initiate an e=
ffort to publish updates to the affected documents.</span></p><br><p dir=3D=
"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;font-weight:400;font-style:normal;font-variant:normal;text-decora=
tion:none;vertical-align:baseline;white-space:pre-wrap">The key part of the=
 added text was as follows:</span><span style=3D"font-size:11pt;font-family=
:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-s=
tyle:normal;font-variant:normal;text-decoration:none;vertical-align:baselin=
e;white-space:pre-wrap"><br><br></span></p><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap">=E2=80=9CThe specific issue involves the h=
andling of &quot;m=3D&quot; sections that are designated as bundle-only, as=
 discussed in</span><a href=3D"https://tools.ietf.org/html/rfc8829#section-=
4.1.1" style=3D"text-decoration:none"><span style=3D"font-size:11pt;font-fa=
mily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;fo=
nt-style:normal;font-variant:normal;text-decoration:none;vertical-align:bas=
eline;white-space:pre-wrap"> </span><span style=3D"font-size:11pt;font-fami=
ly:Arial;color:rgb(17,85,204);background-color:transparent;font-weight:400;=
font-style:normal;font-variant:normal;text-decoration:underline;vertical-al=
ign:baseline;white-space:pre-wrap">Section 4.1.1</span></a><span style=3D"f=
ont-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transpare=
nt;font-weight:400;font-style:normal;font-variant:normal;text-decoration:no=
ne;vertical-align:baseline;white-space:pre-wrap"> of [RFC 8829].=C2=A0 Curr=
ently, there is divergence between JSEP and BUNDLE, as well as between thes=
e specifications and existing browser implementations =E2=80=A6=E2=80=9D</s=
pan></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-=
bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
">The working group is being reconstituted to take up this contradiction, c=
ome to consensus on a resolution, and issue Standards Track updates for tho=
se two documents.=C2=A0 Updating any other document, or taking up any other=
 issue, is out of scope and will require IESG approval via rechartering.</s=
pan></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><spa=
n style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap"></span></p></d=
iv>

--00000000000015740905b9875229--


From nobody Mon Jan 25 08:51:11 2021
Return-Path: <magnus.westerlund@ericsson.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 6B9573A1501; Mon, 25 Jan 2021 08:51:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.451
X-Spam-Level: 
X-Spam-Status: No, score=-0.451 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 0uT3yRVuOXCJ; Mon, 25 Jan 2021 08:51:00 -0800 (PST)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80079.outbound.protection.outlook.com [40.107.8.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E615A3A1500; Mon, 25 Jan 2021 08:50:59 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GfVWiLL/3VYayMj9nRmQLkPwu3/ynxTTZNYtwPaOIsiMZ8ueymCb4TUrLjbSaq7A+vBha2dXIJCdZCl3en2VLVE4KW2ZtiFg1Vq1Cl7QkG1IqutMxcMQ7lhSmOzDyaAqHpRFSrm7E9naDAwG31+O/MciUsGKRuJnlOScTxjYVaI9G5xF72K3Kd8epWlaeaLduD8r8paFfICGuOiylYBoV6h0pAE0BFbRPGG7QavBmQtsni46JyJMnskGYFe6miD3BzVZd6hVpQlR2Io0WCgAw6AHhC35DosQhLvICx6LhLuPyl282hXpXMpRcHfOye2myDP5xkxLNw5GwQZFwGHRYg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Eu/Wx51Q/PSM4/97rVO+Mr98C9KKnnexYDWM73QkosE=; b=i8b/4hWTA6jdBU/RoPFmbjZuaBb54IcGB5wSlZQx5P7PnNi944mGUCZG3cofGOpZJsNQQx4OSOqIQwOpU0nBk3zZAcQuDCoomE+U/qMSQeydlvIm2OqIUv6IjYU3GK7pXnJ6DqpRZwoeymrhPuzgvtm0WuxeGjGaymIKuGRRFVtUDF1vkXhneIR2fP2k0lEfhXt4+OG77atvcQHCvFOZoOx3M7iVCJNQqWl3N3e/gnsWZad9ajtbGxZRmOhveMZtTyq/Ys25ENU01jLrBam4Sk6Wnp9n/vJtWKLVg7NiBaXTxhoZBjUNj3XK/+aFUkTP3DyTsMMQjUUxE2BbijKaRA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Eu/Wx51Q/PSM4/97rVO+Mr98C9KKnnexYDWM73QkosE=; b=PQnHA0G4ZeVMdnFar4OsWwzc2kMshLVLrWMshAeiOm7BZEpjaCRwvKqgr5H1o51P1zL26nms05dLxvkYj4Mq5lXvjjwJ7vvuVI0WzI4rgl12W3uQNC9/24PuvGMBRzSQcRyk9RjtF8m7hZmklVBVUbhZvOTh/yI9qwuTG8vx0To=
Received: from (2603:10a6:7:8e::14) by HE1PR07MB4217.eurprd07.prod.outlook.com (2603:10a6:7:96::33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3805.14; Mon, 25 Jan 2021 16:50:56 +0000
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::8cd:496:65de:4ace]) by HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::8cd:496:65de:4ace%6]) with mapi id 15.20.3784.010; Mon, 25 Jan 2021 16:50:56 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "superuser@gmail.com" <superuser@gmail.com>, "mmusic@ietf.org" <mmusic@ietf.org>, "rtcweb@ietf.org" <rtcweb@ietf.org>
Thread-Topic: [rtcweb] Updating JSEP and BUNDLE
Thread-Index: AQHW8SgYoItmCXXdh0mU6Dw9WOklEao4ki0A
Date: Mon, 25 Jan 2021 16:50:56 +0000
Message-ID: <3259d26b0df271445895d17c73fdf60d94209c52.camel@ericsson.com>
References: <CAL0qLwYeg6_HdjVuLCdhPxtaNH4_vnE_r4Lr1p=s8uiTAu+hdQ@mail.gmail.com>
In-Reply-To: <CAL0qLwYeg6_HdjVuLCdhPxtaNH4_vnE_r4Lr1p=s8uiTAu+hdQ@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Evolution 3.28.5-0ubuntu0.18.04.2 
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [158.174.130.243]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6f61d0d8-466c-4366-9ff7-08d8c1516276
x-ms-traffictypediagnostic: HE1PR07MB4217:
x-microsoft-antispam-prvs: <HE1PR07MB421756CD54CCAFAC64DCA7ED95BD0@HE1PR07MB4217.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: cbi9HIFFTme8hNO8NDyySVslvDApfGYe0k/GUFJM3+d2nEXU5KxXCmQ5w+rJFf8M9Sn64LrUwiV8Ph6qTt7ckpDNcznGLIEG5/sf7GzqGQcPYRQQT4PW12C9i437UPsA86lH/kJiwx9rum4ND26Ba0ZbXq0/cy4FP4IbAxlQgh0UqO/yj6lI6YnYEp/c3onfsab1rfyOAeOazpX3INQiOxSa65XsBy8w4EaRvRhob/0dpJIAOQ239xE/ZH7M9OaHlS9GXzyQxtiGIPQ0Q9WE/Kk5Q+1sE+Z9q6OC0CiaCFfR/G4upnGNXscBMZbW9em+TPMJS5J3rVEyk+Dn+WJ26rjnHuP/cz506qACmvmOeANhBJUwpvKAJ0AwqzdfDXoDiB9dDNDR+I6V+vd0kX4iYXwWMK6sYwNgQHEoGyzUR7B6pfn363ZKyOfFh7swjVdytAtaB3BAe/p86yLImDlf97f8wy8HD2XS23NiF1w9A+cDG2wP38hL9ZbXLfWzyASZGp++O2wZjzSg/xc2wFNZ3IZN5j0j3EmxtfUvy0pY+OeQ6rfAl/Nnvbt41qcV+nb8pE/Me4+d+oJ2jL/+z/GhnF3VVxv0Uz0DgZrzhXHDeyvVvMAuumLBeHlqe07Fl2alykg1e9yUZ4h7QdckIieyjw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR0702MB3772.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(396003)(366004)(136003)(39860400002)(376002)(966005)(5660300002)(76116006)(64756008)(66476007)(66556008)(66946007)(86362001)(6512007)(8676002)(83380400001)(26005)(44832011)(2906002)(36756003)(66616009)(66446008)(66574015)(110136005)(478600001)(316002)(8936002)(186003)(71200400001)(2616005)(6486002)(6506007)(99936003)(99106002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: =?utf-8?B?N2x3QTlsait3NThoMnpKRGxPVmowTFJlckRlYUZyc0VjaDI5a0JrZHRuVEdV?= =?utf-8?B?bHhUdWxBdGExZXF3YmFFWmx5OVM2ZnlmZjBkdklNbXNqbGdpUklFQlBzUXdx?= =?utf-8?B?S3RrWFV3Zk1pUCs2WmZIbTBGVDdnRktkUkVJMGN5cnYyRHZGeWJaQzVrZ1pR?= =?utf-8?B?bUpod0FEcXBoQmpEa1RMQ2xHT2ZRMkdzZFl0djU1d3orS0FHdVVuaDQ1aTJS?= =?utf-8?B?U3A4WG9LMXVGRzRMVFU4a1ZkVEVuMXFRZnFQbDVGczVKa3o5bDhDZ2R0bkRa?= =?utf-8?B?NVJlakhQQmRJYVliZzZkYlhORTZKS0l2ODhYTS9KbG9xSjk0cWZUTGdtTU51?= =?utf-8?B?U3RkRi8rLzFPTEFKSnB6enZDSG1XT2RUa3NZLzNyU2o5RzNoQTkxcUJEVWJn?= =?utf-8?B?MjlpY3NYR2QvZ0FXY1E1T1Y3blJPdEw1cjE0T043aGhCTER2VHVhdUNhQTg4?= =?utf-8?B?M1VWUDhuUFVQOFozaEUvQlFhR2JWZmNQTFRpdG9ScFl5WFArUFcxRXUyNEJT?= =?utf-8?B?VXVzSmJiUlZ1ck1HOHQvM1pjWmZyMjdBcGZKQzNURlcwbVNjZG9HQTY5eFNB?= =?utf-8?B?eS9BYW9rbHEySUYrYWlQTnhNbWZzRzl4eTE2Vk04QTRIZVdYamsxUjlKWHZh?= =?utf-8?B?S3cxODRod1lBZ1FGUVV3SWJwR0w1a1pudnZpT2xDOGM5cHoyejMxOUZPNmor?= =?utf-8?B?OTB6TGlwb0YrYm5nNFJVMHEzNzcxdzAwRHlMWk9meHo0SVNSS245cUFhM3pE?= =?utf-8?B?akt3QTVUNDB1MUFkQ1lHZVlyWjVwMUxsSXFUT21jRHoyWWRWVy9mTE1PNVR3?= =?utf-8?B?SDc0RXhjRlpwNEduUlczM0ZEcW51UDFpZ2N4NFZITlZxbVNBNS9UUFg3bXY2?= =?utf-8?B?UklUMnJ1MXdRTmJZY0NSSnVRaHBJc0hSeFkxYmNSc055RzBaOGtZWi9hc0lB?= =?utf-8?B?aFNyQ1BmTHYvU0hobGxqTmFwb0ZPbjJrbTRtNkw5RjBxbE81NzBueHZ1UDg5?= =?utf-8?B?RDJnelpYQ2Jja3lKQ3RPc1Njb2NUa0VHS2dkOEY5Y0tFeFRYZndNd3o3UGlM?= =?utf-8?B?czRaMHhENWN0dFZjYkFabXd4dGhZbktqNm41TWJ4MVR6OW0razh1bjdjU2Uw?= =?utf-8?B?aXhSTFRyY0orTDdaZ0ZYRHlxMDF4eThaM2dFNEJDcUtrbW4zc1pqMEN3WGV6?= =?utf-8?B?MTNqcUIvaDFVK1ZhWU1hSCtSQlQvaXZlM05yMHlLWHF6Q21rNWJ1c0Nlci9E?= =?utf-8?B?Q3YxUWFIWDB6KzdTc3NPWmx2cjhmV2dXWHYxc1lncDRjM0p1d3JDOEpzVktU?= =?utf-8?B?bmZQQWNYdmtDZkwzS25xTXczZVk4YXZLNWhSMDdVbVdFUGNoOHJWUVR1UFY5?= =?utf-8?B?ckhCOWNnL3pqcGpWaTFYVmJXNm9tTngzNEt1c1BBYXR6VVdkWU50ZUhkVFJ3?= =?utf-8?B?NjRTbWFLVjU4MDhqc3krcE9CU0k1YWp3ZloyeXBRPT0=?=
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; micalg="sha-256"; protocol="application/x-pkcs7-signature"; boundary="=-A87+fg8l/93L25Vt4dS3"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR0702MB3772.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6f61d0d8-466c-4366-9ff7-08d8c1516276
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jan 2021 16:50:56.0638 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: VPcgYxXTkxANmKSIYj5u6BHKKv3TaazSXq9BUPcFiLnK+xGujUNJg/d1pj3Ql36sJnxFriCsyfIAqZGHOUpmEiWRptJfqAHbx1hIHe8TL8A=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4217
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/UDPXaHKryD4s7gl9pz6BKxHdJGU>
Subject: Re: [rtcweb] Updating JSEP and BUNDLE
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 16:51:02 -0000

--=-A87+fg8l/93L25Vt4dS3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi,

I am cross posting this to MMUSIC as BUNDLE was a MMUSIC document, and this
issue has to my understanding still not been conveyed to the MMUSIC WG
partipants.=20

First, I am a bit concerned that this is done in a RTCWeb WG without any
requirement on interaction with MMUSIC. BUNDLE is a general SDP O/A mechani=
sm
and not specific to RTCWebs usage in JSEP. Thus, I am worried about that ch=
anges
are applied to BUNDLE that works fine for JSEP, but affect the interoperabi=
lity
with general case SDP O/A usages.=20

Secondly, the citiation below includes the following: "... and existing bro=
wser
implementations." I think that gives an impression that RTCWeb browser=20
implementations can be used trump over general SDP O/A interoperability and=
 also other implementation, even of WebRTC, that this alignment fix could p=
otentially impact.=20

Thus, I would prefer a different wording than referring to a statement that=
 was
intended to be informative that there exists an issue. I would notet that t=
he
statement was quickly written, that a limited set of people had any chance =
to
see prior to its publication.=20

In addition I think the scope can be narrowed even further than to just the
Bundle-only part of BUNDLE and JSEP, to only the aspect that is missaligned=
.

Cheers

Magnus Westerlund




On Fri, 2021-01-22 at 17:35 -0800, Murray S. Kucherawy wrote:
> Colleagues,
>=20
> In the final run-up to publication of C238, it was observed that the JSEP=
 and
> BUNDLE documents contradict each other in a significant way.
>=20
> Rather than send them back to the working group to resolve, delaying
> publication further for an unknown duration, the authors and Area Directo=
rs
> involved reached consensus to publish the entire cluster as it was origin=
ally
> approved, with a note added that acknowledges the contradiction (without
> proposing solutions), and stating that the IETF will quickly take up the =
work
> to publish updates.  The specific text is visible as Section 1.3 of RFC 8=
829
> and 1.4 of RFC 8843.
>=20
> The IESG intends to reconstitute the RTCWEB working group to resolve this
> contradiction, with a scope to resolve only that specific issue and publi=
sh a
> couple of document updates.  The plan is to have this rechartering in pla=
ce in
> time for a meeting at IETF 110 in March.
>=20
> Below is the proposed re-chartering for the RTCWEB working group.  Feedba=
ck on
> this is welcome, either on the rtcweb@ietf.org list, to me privately, or =
to
> the IESG.  We will start the formal process of review and approval on the=
 next
> IESG telechat, and have already requested a session during IETF 110 to ge=
t the
> work going.
>=20
> -MSK, ART AD=20
>=20
> --
>=20
> The RTCWEB working group was originally chartered to standardize mechanis=
ms
> that provide direct interactive rich communication using audio, video,
> collaboration, games, etc. between two peers' web-browsers, without requi=
ring
> non-standard extensions or proprietary plug-ins.  The result was a set of=
 RFCs
> from RTCWEB, in addition to many other RFCs from other working groups, al=
l of
> which are interrelated and had to be published together in what the RFC E=
ditor
> refers to as a =E2=80=9Ccluster=E2=80=9D.  In the end, that cluster compr=
ised more than 40
> RFCs and was finally published in January 2021.
>=20
> During the run-up to publication of the cluster, a contradiction was
> identified between what became RFCs 8829 and 8843.  A description of this
> contradiction was added to both documents to highlight the problem, and s=
tate
> our intention to proceed with publication but quickly initiate an effort =
to
> publish updates to the affected documents.
>=20
> The key part of the added text was as follows:
>=20
> =E2=80=9CThe specific issue involves the handling of "m=3D" sections that=
 are designated
> as bundle-only, as discussed in Section 4.1.1 of [RFC 8829].  Currently, =
there
> is divergence between JSEP and BUNDLE, as well as between these specifica=
tions
> and existing browser implementations =E2=80=A6=E2=80=9D
>=20
> The working group is being reconstituted to take up this contradiction, c=
ome
> to consensus on a resolution, and issue Standards Track updates for those=
 two
> documents.  Updating any other document, or taking up any other issue, is=
 out
> of scope and will require IESG approval via rechartering.
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

--=-A87+fg8l/93L25Vt4dS3
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Disposition: attachment; filename="smime.p7s"
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCErYw
ggX0MIID3KADAgECAg8BdlE9InYZOYLl1zGep4IwDQYJKoZIhvcNAQELBQAwRzELMAkGA1UEBhMC
U0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENB
IHYzMB4XDTIwMTIxMTA5NTg0OVoXDTIzMTIxMjA5NTg0OVowXjERMA8GA1UECgwIRXJpY3Nzb24x
GjAYBgNVBAMMEU1hZ251cyBXZXN0ZXJsdW5kMS0wKwYJKoZIhvcNAQkBFh5tYWdudXMud2VzdGVy
bHVuZEBlcmljc3Nvbi5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCIT6U9ddUp
UCEryIA27xtF8WsRAIfc5jBavfu0OGDmwITYYRD2PaMEdEK+I4dqz0f6xcCrDnBk2Xj+JxjhaRkq
TAifJZima9WE2JoI/uq8UsS2HJWlhspAwKx1osARgtRiMjRZZyyfiRZLbgXHWYpnTt3i9QsuX/uo
9oZFWpDCbZee4Il9uldsUcuBLZx2PyZvBvC8KCUaBXsZX6bwV7hssRVn+BgFCuEievJMx0khTRVh
i9goObxu5Jl44RtwbZNYB1UE1IzRWEZw+b3cEvXiQjPl2e3ytMZSmhy+IaKmjxES6ODiuh51KAcm
PZfZIaX2djmD76YGi+ETmnb8Xm3dAgMBAAGjggHEMIIBwDAfBgNVHSMEGDAWgBQcexmel5x2rCA9
2NzjkWrj2y2mUzAdBgNVHQ4EFgQUICO/88T0EQvEUm5+HVt/d9Mm+Z8wDgYDVR0PAQH/BAQDAgWg
MFUGA1UdIAROMEwwSgYMKwYBBAGCDwIDAQESMDowOAYIKwYBBQUHAgEWLGh0dHBzOi8vcmVwb3Np
dG9yeS50cnVzdC50ZWxpYXNvbmVyYS5jb20vQ1BTMCkGA1UdEQQiMCCBHm1hZ251cy53ZXN0ZXJs
dW5kQGVyaWNzc29uLmNvbTBIBgNVHR8EQTA/MD2gO6A5hjdodHRwOi8vY3JsLnRydXN0LnRlbGlh
LmNvbS9lcmljc3Nvbm5saW5kaXZpZHVhbGNhdjMuY3JsMB0GA1UdJQQWMBQGCCsGAQUFBwMEBggr
BgEFBQcDAjCBggYIKwYBBQUHAQEEdjB0MCgGCCsGAQUFBzABhhxodHRwOi8vb2NzcDIudHJ1c3Qu
dGVsaWEuY29tMEgGCCsGAQUFBzAChjxodHRwOi8vY2EudHJ1c3QudGVsaWFzb25lcmEuY29tL2Vy
aWNzc29ubmxpbmRpdmlkdWFsY2F2My5jZXIwDQYJKoZIhvcNAQELBQADggIBANRZXQy+lUW97uaL
uApOixnDKLpUoz+N/5Owd/9illmbxQDEY1/pPs4KJSvw88p+F3bmOzb+fLUNa6Mi/2Tw83FzEVmO
3RqzKtca+I9GDpRQ8oWL7hrUPJoNacidSZLmAP4L4kwHIhvGNX4f1c/oB4fAkP/xZsAAxYi7nKxd
XA2n/KMWNkezyB9BSsD8ZOS4pWU8UaZjd5r0fzqM5zQbU4EPqHa8jFMSMz1UrYXPKKxl6E4WA3TE
w1oLjcli0NWGQHyQ+3Kh7fe6zPoXfLd/2EQjr2o76ssgoqd2V1Mx5TRHdUyxjIMPEOVYpvcerNUB
hEBkaOQ9FugYcMhMc8BF7nQZq+hsL/T7idg4gE2sEfNdK9RBf/EVH10GMrmbadqTycztD1gUL3dV
Qxik4TCMxIctt9XqtTGHaMewZLQAXp/sHWlU/vmz9brcuzYQ9YVd5hTendGMUyGhWPV/KvxouKPK
zdrGeEqUQCeBwWgQASQNOrpTzMJwZAV/Ww3ExQCjHvflvUQzVuU0sC6AEVkgqMATIXS6h6rjLL31
pjt2JV84XRjF5afYkcRIHTsrtcoWeFtOu/GpZNhtq+tde0QvnkSsjczMWU0gKk0hXBmXwEGUimuD
Vq/Wvr0mr18d9mKA6xPNQOfn/VL5CWXa11OtOjj8WsTy3XUpyJ6dc9Z72TmKMIIF9DCCA9ygAwIB
AgIPAXZRPSJ2GTmC5dcxnqeCMA0GCSqGSIb3DQEBCwUAMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQK
DAhFcmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MzAeFw0yMDEy
MTEwOTU4NDlaFw0yMzEyMTIwOTU4NDlaMF4xETAPBgNVBAoMCEVyaWNzc29uMRowGAYDVQQDDBFN
YWdudXMgV2VzdGVybHVuZDEtMCsGCSqGSIb3DQEJARYebWFnbnVzLndlc3Rlcmx1bmRAZXJpY3Nz
b24uY29tMIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAiE+lPXXVKVAhK8iANu8bRfFr
EQCH3OYwWr37tDhg5sCE2GEQ9j2jBHRCviOHas9H+sXAqw5wZNl4/icY4WkZKkwInyWYpmvVhNia
CP7qvFLEthyVpYbKQMCsdaLAEYLUYjI0WWcsn4kWS24Fx1mKZ07d4vULLl/7qPaGRVqQwm2XnuCJ
fbpXbFHLgS2cdj8mbwbwvCglGgV7GV+m8Fe4bLEVZ/gYBQrhInryTMdJIU0VYYvYKDm8buSZeOEb
cG2TWAdVBNSM0VhGcPm93BL14kIz5dnt8rTGUpocviGipo8REujg4roedSgHJj2X2SGl9nY5g++m
BovhE5p2/F5t3QIDAQABo4IBxDCCAcAwHwYDVR0jBBgwFoAUHHsZnpecdqwgPdjc45Fq49stplMw
HQYDVR0OBBYEFCAjv/PE9BELxFJufh1bf3fTJvmfMA4GA1UdDwEB/wQEAwIFoDBVBgNVHSAETjBM
MEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1c3Qu
dGVsaWFzb25lcmEuY29tL0NQUzApBgNVHREEIjAggR5tYWdudXMud2VzdGVybHVuZEBlcmljc3Nv
bi5jb20wSAYDVR0fBEEwPzA9oDugOYY3aHR0cDovL2NybC50cnVzdC50ZWxpYS5jb20vZXJpY3Nz
b25ubGluZGl2aWR1YWxjYXYzLmNybDAdBgNVHSUEFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwgYIG
CCsGAQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNvbTBI
BggrBgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5saW5k
aXZpZHVhbGNhdjMuY2VyMA0GCSqGSIb3DQEBCwUAA4ICAQDUWV0MvpVFve7mi7gKTosZwyi6VKM/
jf+TsHf/YpZZm8UAxGNf6T7OCiUr8PPKfhd25js2/ny1DWujIv9k8PNxcxFZjt0asyrXGviPRg6U
UPKFi+4a1DyaDWnInUmS5gD+C+JMByIbxjV+H9XP6AeHwJD/8WbAAMWIu5ysXVwNp/yjFjZHs8gf
QUrA/GTkuKVlPFGmY3ea9H86jOc0G1OBD6h2vIxTEjM9VK2FzyisZehOFgN0xMNaC43JYtDVhkB8
kPtyoe33usz6F3y3f9hEI69qO+rLIKKndldTMeU0R3VMsYyDDxDlWKb3HqzVAYRAZGjkPRboGHDI
THPARe50GavobC/0+4nYOIBNrBHzXSvUQX/xFR9dBjK5m2nak8nM7Q9YFC93VUMYpOEwjMSHLbfV
6rUxh2jHsGS0AF6f7B1pVP75s/W63Ls2EPWFXeYU3p3RjFMhoVj1fyr8aLijys3axnhKlEAngcFo
EAEkDTq6U8zCcGQFf1sNxMUAox735b1EM1blNLAugBFZIKjAEyF0uoeq4yy99aY7diVfOF0YxeWn
2JHESB07K7XKFnhbTrvxqWTYbavrXXtEL55ErI3MzFlNICpNIVwZl8BBlIprg1av1r69Jq9fHfZi
gOsTzUDn5/1S+Qll2tdTrTo4/FrE8t11KcienXPWe9k5ijCCBsIwggSqoAMCAQICEFO4foPhnJko
k7CbSRzsuOswDQYJKoZIhvcNAQELBQAwNzEUMBIGA1UECgwLVGVsaWFTb25lcmExHzAdBgNVBAMM
FlRlbGlhU29uZXJhIFJvb3QgQ0EgdjEwHhcNMTUxMDI3MTIxNjQ2WhcNMjUxMDI3MTIxNjQ2WjBH
MQswCQYDVQQGEwJTRTERMA8GA1UECgwIRXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIElu
ZGl2aWR1YWwgQ0EgdjMwggIiMA0GCSqGSIb3DQEBAQUAA4ICDwAwggIKAoICAQDs8t8AALhQ8qe7
2FS3xpP348GqO9TDRjS0s85eQ7Y0LTLZdmSz2cl+lYqs0zfSTm+7meisbhkqUXkL7fFzoe4iIZCh
/VuYUaW407CZlDCXes4n4TqTSuoklN6uOPhY7EC9ZVbXILlLhRummTdDdxhVW4Leo0awEhfLf98M
vWxzwCHzMj8m6YOmNjx+f9TcJE3qaA0piuvSxlfpVdiCulPTlmsmV2RSBSAwqBshZYRcQBIDfqmd
vkaoP9EzNKAh7yjthC0hpgHZyZMIs0eNo4v2PUmE0rhu+Zs0nujnwhljPA2/8b8v9tGixD1zbtT7
zoM2Ot1menJpFp4zJVSfdKVgtoWqg5t2H/E0XY1LwJez89W07nscEocyBmpC+zJAmKxKhzEWqIyP
1UrZaEIFu+hO+s0Nm8sOUMa4TlG4rAUikc5U5TmUIGBRQGxulYhfAzqSYf8oLUMLky1DOa9eRu3s
p0FdQDEzQlnF/h1L4AK1MOkX1vS+fLgOvBo5LRU1fLPUZQ7FKrDXC6nl2ldvEtljHWstGBmqv25a
EvAA+yrrplCh/kYvSBjvZibz9Obbwx4yqS77/NHN1iyZyVP2s52B2BLdvo4yhzk6nRk8S/8zHaUU
kBUrrvijPDaGK5FNVSaioGvkC7IKioITKffYLtT9XuirKrHlh3VzkazG46pAVwIDAQABo4IBuDCC
AbQwgYoGCCsGAQUFBwEBBH4wfDAtBggrBgEFBQcwAYYhaHR0cDovL29jc3AudHJ1c3QudGVsaWFz
b25lcmEuY29tMEsGCCsGAQUFBzAChj9odHRwOi8vcmVwb3NpdG9yeS50cnVzdC50ZWxpYXNvbmVy
YS5jb20vdGVsaWFzb25lcmFyb290Y2F2MS5jZXIwEgYDVR0TAQH/BAgwBgEB/wIBADBVBgNVHSAE
TjBMMEoGDCsGAQQBgg8CAwEBAjA6MDgGCCsGAQUFBwIBFixodHRwczovL3JlcG9zaXRvcnkudHJ1
c3QudGVsaWFzb25lcmEuY29tL0NQUzBLBgNVHR8ERDBCMECgPqA8hjpodHRwOi8vY3JsLTMudHJ1
c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY3JsMB0GA1UdJQQWMBQGCCsG
AQUFBwMCBggrBgEFBQcDBDAOBgNVHQ8BAf8EBAMCAQYwHQYDVR0OBBYEFBx7GZ6XnHasID3Y3OOR
auPbLaZTMB8GA1UdIwQYMBaAFPCPWTgAs/WPmpYM1ev6e6oX6BMSMA0GCSqGSIb3DQEBCwUAA4IC
AQBQWGvx1Yw7tC6rV0PIjKfDyxaanIX+NZLEGOkdQLKGW2gVLtDUJQEPRs5QtaZiObNHCZ7mmSNM
Vek4lkt/0dqfVIFutVw/QkyFGwC99ZmNwXSX9z+OoMyoEBHGvw5RY6vRlZrj0uKvdASzYL4KMaB7
m3NwurNDmmNbG52suRIZ76wBOEOddRZcZiTy50ZkBqYnnl2t3D3oBX2NZCQysshUcqRdUbkS13HT
CIChMuTV9W0tzPXUOJoJlJlU9nd91IikhGEOrPwfixWms+C8sF0r9qN1uJGx6ELPOiFrLfNtcMNM
MbAqRHwpSLxe3wcNkJGxv9T8LswLi1UrRIQ85AKjqzBnLSsjRGgbMgJ+xKtngmvEA155JmoKfUD7
DRbP6Kp14/Y9XFbR/WuDj84bYNKXe4HdDc1P+UMYm16m2L6LkIIoRlx0A5mi+K7jewuGqzFKkaPN
mJ0RLCi+4d4/47Zs3DC3PUNOxdOEEHf4kkdWOaSIuj3TQYhNv+LsgF0uijiBmaz2zUFDa2bcIkKa
kDZfAFM4HoHz8K2BZRaHKWhd3dZua/tlSiqokUFX2DxmHmZ1n5HM9OiaAIXP/Zo2x10j/Yb1mM3i
0bqGahxlHYzl/QyEG/dujp3lewuVjCI0mPDkZGphvxyqp4Jo8qS94EnOqBvxOgftYug7OY9EKY+W
kDGCAsowggLGAgEBMFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdlE9InYZOYLl1zGep4IwDQYJYIZIAWUD
BAIBBQCgggFBMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTIxMDEy
NTE2NTA1NFowLwYJKoZIhvcNAQkEMSIEIN/XmgBClVSLCsKUo3wEfAQHBQZC7koobq0U4/izcA9P
MGkGCSsGAQQBgjcQBDFcMFowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYD
VQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAg8BdlE9InYZOYLl1zGep4IwawYLKoZI
hvcNAQkQAgsxXKBaMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhFcmljc3NvbjElMCMGA1UEAwwc
RXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIPAXZRPSJ2GTmC5dcxnqeCMA0GCSqGSIb3DQEB
AQUABIIBAGxgNWD3gRUuTClnZ2AXLXGaIxgz9az0Uvgnl/R8gmgUw/bEHieCzNw+ce73zvRJXjjG
qxUlFuY8Byhe8yZFPOllwVPxf+UcZJ5GKuEEo2JZSOXS7M5Rfh26Dypf4ynJDiSxIshYBqhso99d
w/rqLpRxWWEISpMZpD8MG18YMmotaCmEkWMlJN6H14LZlRnCJJiN2phhKjiDbe6QXPS3zPHz15Ev
98JVm2BUeXWdLg1ktD5jLt80RR3FjJFDnYwReECDbXx4HykZuh7SNHXxjidgITvVYYR5lv9IZrGo
PGF81Y0+oHri+dgpVFE+4nqKtaA/P72J4j1y6xFtgFQAyVoAAAAAAAA=


--=-A87+fg8l/93L25Vt4dS3--


From nobody Mon Jan 25 09:37:00 2021
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


From nobody Mon Jan 25 09:41:03 2021
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

--000000000000f392c405b9bd09c1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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.or=
g>
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=C3=BCxen
> Category            : PROPOSED STANDARD
> Source              : Real-Time Communication in WEB-browsers
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG
>

--000000000000f392c405b9bd09c1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>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.=C2=A0 I recommend it be rejected.<br>=
</div><div><br></div><div>Just my personal opinion,</div><div><br></div><di=
v>regards,</div><div><br></div><div>Ted<br></div></div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jan 25, 2021 at 1:=
28 AM RFC Errata System &lt;<a href=3D"mailto:rfc-editor@rfc-editor.org">rf=
c-editor@rfc-editor.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">The following errata report has been submitted for R=
FC8832,<br>
&quot;WebRTC Data Channel Establishment Protocol&quot;.<br>
<br>
--------------------------------------<br>
You may review the report below and at:<br>
<a href=3D"https://www.rfc-editor.org/errata/eid6411" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.rfc-editor.org/errata/eid6411</a><br>
<br>
--------------------------------------<br>
Type: Technical<br>
Reported by: Victor Boivie &lt;<a href=3D"mailto:boivie@google.com" target=
=3D"_blank">boivie@google.com</a>&gt;<br>
<br>
Section: 5<br>
<br>
Original Text<br>
-------------<br>
5.=C2=A0 Message Formats<br>
<br>
=C2=A0 =C2=A0Every Data Channel Establishment Protocol message starts with =
a one<br>
=C2=A0 =C2=A0byte field called &quot;Message Type&quot; which indicates the=
 type of the<br>
=C2=A0 =C2=A0message.=C2=A0 The corresponding values are managed by IANA (s=
ee<br>
=C2=A0 =C2=A0Section 8.2.1).<br>
<br>
Corrected Text<br>
--------------<br>
5.=C2=A0 Message Formats<br>
<br>
=C2=A0 =C2=A0Every Data Channel Establishment Protocol message starts with =
a one<br>
=C2=A0 =C2=A0byte field called &quot;Message Type&quot; which indicates the=
 type of the<br>
=C2=A0 =C2=A0message.=C2=A0 The corresponding values are managed by IANA (s=
ee<br>
=C2=A0 =C2=A0Section 8.2.1).<br>
<br>
=C2=A0 =C2=A0All integer fields in an Data Channel Establishment Protocol m=
essage<br>
=C2=A0 =C2=A0MUST be transmitted in network byte order, unless otherwise st=
ated.<br>
<br>
Notes<br>
-----<br>
The byte order of integer fields in the protocol messages is not defined.<b=
r>
<br>
Instructions:<br>
-------------<br>
This erratum is currently posted as &quot;Reported&quot;. If necessary, ple=
ase<br>
use &quot;Reply All&quot; to discuss whether it should be verified or<br>
rejected. When a decision is reached, the verifying party=C2=A0 <br>
can log in to change the status and edit the report, if necessary. <br>
<br>
--------------------------------------<br>
RFC8832 (draft-ietf-rtcweb-data-protocol-09)<br>
--------------------------------------<br>
Title=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: WebRTC Data C=
hannel Establishment Protocol<br>
Publication Date=C2=A0 =C2=A0 : January 2021<br>
Author(s)=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0: R. Jesup, S. Loreto, M.=
 T=C3=BCxen<br>
Category=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : PROPOSED STANDARD<br>
Source=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Real-Time Communic=
ation in WEB-browsers<br>
Area=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : Applications =
and Real-Time<br>
Stream=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 : IETF<br>
Verifying Party=C2=A0 =C2=A0 =C2=A0: IESG<br>
</blockquote></div>

--000000000000f392c405b9bd09c1--


From nobody Mon Jan 25 10:34:08 2021
Return-Path: <barryleiba@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 58B173A1727 for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 10:34:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.499
X-Spam-Level: 
X-Spam-Status: No, score=0.499 tagged_above=-999 required=5 tests=[FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 3tf1WaNTrhz7 for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 10:34:02 -0800 (PST)
Received: from mail-lf1-f41.google.com (mail-lf1-f41.google.com [209.85.167.41]) (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 8FC0C3A172C for <rtcweb@ietf.org>; Mon, 25 Jan 2021 10:34:02 -0800 (PST)
Received: by mail-lf1-f41.google.com with SMTP id a8so19249268lfi.8 for <rtcweb@ietf.org>; Mon, 25 Jan 2021 10:34:02 -0800 (PST)
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:content-transfer-encoding; bh=uUZi+KkQZxGM2AHfbCAwcqw8E2oyiz8dqThZmF5sThY=; b=EoU4iic6t488wwW01GvNKqxRzSz1B7LSgACxHeq4G057JdMYlVrMfDENGr9FyQFX7g 8K2bpXhc9f7D4u/q0BvTUSAO23hodoa5muUjgCq2GjB90MqcKN7WpfeENNJ7mjSq5Gez WnNEYUmfXhceA8TZEbmYg7Y/U1/SqH79ePmwuo8HK7PRQAvp4+x9IDkfom7yOznZ5QbC qxILmWwmm+UK6HUtAZlxxjajcBrVgEoa4gexAOBOekz7FTEL40PeanJBj1qcOlF8UXFJ tkLzwRFaBzjh/Jv26XFcgrXHR5J7etcSIEcWQ2ebN5Z1VSwnbdxk0KBOaEAFv+sEZpyb gcbw==
X-Gm-Message-State: AOAM530wqgd/nxT+YPrNc5SLIzBHe2wJ826XvePZGOj2T+u9sLwCTX9X LMkF0i3LZ+BSH1Vp6fioZIvgwgrQOsVuAeUiMv0=
X-Google-Smtp-Source: ABdhPJxJxx9eW1l1sU4KgLS9cqVz+wmyaJSPslj9OC3XAnKEIjebgY9UrAgUP/1WqydjozKtjhDJ8iqT/bmIdiXakjY=
X-Received: by 2002:ac2:592a:: with SMTP id v10mr830241lfi.123.1611599640076;  Mon, 25 Jan 2021 10:34:00 -0800 (PST)
MIME-Version: 1.0
References: <20210125092848.3AF95F40764@rfc-editor.org> <CA+9kkMBJTN-U0WNdSRJ6PdOPBHwayfWxUGebThr+iHOM_QmYqQ@mail.gmail.com> <CAFaRDoL1nCwVE=3g-O-CV-ZjVT6Ggb9rP8JX3rmMcnaLN62jPw@mail.gmail.com>
In-Reply-To: <CAFaRDoL1nCwVE=3g-O-CV-ZjVT6Ggb9rP8JX3rmMcnaLN62jPw@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Mon, 25 Jan 2021 13:33:48 -0500
Message-ID: <CALaySJLX2eHrNogJ_f7FFRjyHLEasJa02-dbtgOwSmON_s2H9g@mail.gmail.com>
To: Victor Boivie <boivie@google.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, RFC Errata System <rfc-editor@rfc-editor.org>,  Randell Jesup <randell-ietf@jesup.org>, Salvatore Loreto <salvatore.loreto@ericsson.com>,  Michael Tuexen <tuexen@fh-muenster.de>, "Murray S. Kucherawy" <superuser@gmail.com>, sean+ietf@sn3rd.com,  RTCWeb IETF <rtcweb@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/lJEhq_KVGLVZEdJAQ9c-jBXJPrw>
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:34:06 -0000

>From the point of view of "errata", though, the question is whether
this was an omission that would have been fixed if it had been caught
at the time of publication... or something that was not put in because
it was considered to be covered elsewhere, so not an "error" in the
RFC.

It seems the latter, not the former.

Barry

On Mon, Jan 25, 2021 at 1:21 PM Victor Boivie <boivie@google.com> wrote:
>
> While I absolutely accept that rationale, Data Channel Establishment Prot=
ocol is layered on top of SCTP, and is not an SCTP extension (where I would=
 definitely agree with what you're saying).
>
> While I can't see what the future brings, I could envision an evolution o=
f RFC8832 being layered on top of e.g. QUIC or SRT, would the WebRTC projec=
t decide to change the underlying protocol from SCTP to something else in t=
he future. That would be a separate RFC, though.
>
> Thanks and best regards,
> Victor
>
> On Mon, Jan 25, 2021 at 6:40 PM Ted Hardie <ted.ietf@gmail.com> wrote:
>>
>> Since the Data Channel Establishment Protocol depends on SCTP, which req=
uires 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 define=
d.
>>>
>>> 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=C3=BCxen
>>> Category            : PROPOSED STANDARD
>>> Source              : Real-Time Communication in WEB-browsers
>>> Area                : Applications and Real-Time
>>> Stream              : IETF
>>> Verifying Party     : IESG


From nobody Mon Jan 25 10:37:19 2021
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

--Apple-Mail=_A7EA20FE-A82F-4774-B4C5-2189DEE9BD61
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 25. Jan 2021, at 18:40, Ted Hardie <ted.ietf@gmail.com> wrote:
>=20
> 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.
>=20
> 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
>=20
> regards,
>=20
> Ted
>=20
> 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".
>=20
> --------------------------------------
> You may review the report below and at:
> https://www.rfc-editor.org/errata/eid6411
>=20
> --------------------------------------
> Type: Technical
> Reported by: Victor Boivie <boivie@google.com>
>=20
> Section: 5
>=20
> Original Text
> -------------
> 5.  Message Formats
>=20
>    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).
>=20
> Corrected Text
> --------------
> 5.  Message Formats
>=20
>    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).
>=20
>    All integer fields in an Data Channel Establishment Protocol =
message
>    MUST be transmitted in network byte order, unless otherwise stated.
>=20
> Notes
> -----
> The byte order of integer fields in the protocol messages is not =
defined.
>=20
> 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 =20
> can log in to change the status and edit the report, if necessary.=20
>=20
> --------------------------------------
> 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=C3=BCxen
> Category            : PROPOSED STANDARD
> Source              : Real-Time Communication in WEB-browsers
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG


--Apple-Mail=_A7EA20FE-A82F-4774-B4C5-2189DEE9BD61
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEKow
ggUSMIID+qADAgECAgkA4wvV+K8l2YEwDQYJKoZIhvcNAQELBQAwgYIxCzAJBgNVBAYTAkRFMSsw
KQYDVQQKDCJULVN5c3RlbXMgRW50ZXJwcmlzZSBTZXJ2aWNlcyBHbWJIMR8wHQYDVQQLDBZULVN5
c3RlbXMgVHJ1c3QgQ2VudGVyMSUwIwYDVQQDDBxULVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAy
MB4XDTE2MDIyMjEzMzgyMloXDTMxMDIyMjIzNTk1OVowgZUxCzAJBgNVBAYTAkRFMUUwQwYDVQQK
EzxWZXJlaW4genVyIEZvZXJkZXJ1bmcgZWluZXMgRGV1dHNjaGVuIEZvcnNjaHVuZ3NuZXR6ZXMg
ZS4gVi4xEDAOBgNVBAsTB0RGTi1QS0kxLTArBgNVBAMTJERGTi1WZXJlaW4gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMtg1/9moUHN0vqH
l4pzq5lN6mc5WqFggEcVToyVsuXPztNXS43O+FZsFVV2B+pG/cgDRWM+cNSrVICxI5y+NyipCf8F
XRgPxJiZN7Mg9mZ4F4fCnQ7MSjLnFp2uDo0peQcAIFTcFV9Kltd4tjTTwXS1nem/wHdN6r1ZB+Ba
L2w8pQDcNb1lDY9/Mm3yWmpLYgHurDg0WUU2SQXaeMpqbVvAgWsRzNI8qIv4cRrKO+KA3Ra0Z3qL
NupOkSk9s1FcragMvp0049ENF4N1xDkesJQLEvHVaY4l9Lg9K7/AjsMeO6W/VRCrKq4Xl14zzsjz
9AkH4wKGMUZrAcUQDBHHWekCAwEAAaOCAXQwggFwMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQU
k+PYMiba1fFKpZFK4OpL4qIMz+EwHwYDVR0jBBgwFoAUv1kgNgB5oKAia4zV8mHSuCzLgkowEgYD
VR0TAQH/BAgwBgEB/wIBAjAzBgNVHSAELDAqMA8GDSsGAQQBga0hgiwBAQQwDQYLKwYBBAGBrSGC
LB4wCAYGZ4EMAQICMEwGA1UdHwRFMEMwQaA/oD2GO2h0dHA6Ly9wa2kwMzM2LnRlbGVzZWMuZGUv
cmwvVGVsZVNlY19HbG9iYWxSb290X0NsYXNzXzIuY3JsMIGGBggrBgEFBQcBAQR6MHgwLAYIKwYB
BQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMEgGCCsGAQUFBzAChjxodHRw
Oi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9UZWxlU2VjX0dsb2JhbFJvb3RfQ2xhc3NfMi5jZXIw
DQYJKoZIhvcNAQELBQADggEBAIcL/z4Cm2XIVi3WO5qYi3FP2ropqiH5Ri71sqQPrhE4eTizDnS6
dl2e6BiClmLbTDPo3flq3zK9LExHYFV/53RrtCyD2HlrtrdNUAtmB7Xts5et6u5/MOaZ/SLick0+
hFvu+c+Z6n/XUjkurJgARH5pO7917tALOxrN5fcPImxHhPalR6D90Bo0fa3SPXez7vTXTf/D6OWS
T1k+kEcQSrCFWMBvf/iu7QhCnh7U3xQuTY+8npTD5+32GPg8SecmqKc22CzeIs2LgtjZeOJVEqM7
h0S2EQvVDFKvaYwPBt/QolOLV5h7z/0HJPT8vcP9SpIClxvyt7bPZYoaorVyGTkwggWsMIIElKAD
AgECAgcbY7rQHiw9MA0GCSqGSIb3DQEBCwUAMIGVMQswCQYDVQQGEwJERTFFMEMGA1UEChM8VmVy
ZWluIHp1ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYu
MRAwDgYDVQQLEwdERk4tUEtJMS0wKwYDVQQDEyRERk4tVmVyZWluIENlcnRpZmljYXRpb24gQXV0
aG9yaXR5IDIwHhcNMTYwNTI0MTEzODQwWhcNMzEwMjIyMjM1OTU5WjCBjTELMAkGA1UEBhMCREUx
RTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9lcmRlcnVuZyBlaW5lcyBEZXV0c2NoZW4gRm9yc2NodW5n
c25ldHplcyBlLiBWLjEQMA4GA1UECwwHREZOLVBLSTElMCMGA1UEAwwcREZOLVZlcmVpbiBHbG9i
YWwgSXNzdWluZyBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJ07eRxH3h+Gy8Zp
1xCeOdfZojDbchwFfylfS2jxrRnWTOFrG7ELf6Gr4HuLi9gtzm6IOhDuV+UefwRRNuu6cG1joL6W
LkDh0YNMZj0cZGnlm6Stcq5oOVGHecwX064vXWNxSzl660Knl5BpBb+Q/6RAcL0D57+eGIgfn5mI
TQ5HjUhfZZkQ0tkqSe3BuS0dnxLLFdM/fx5ULzquk1enfnjK1UriGuXtQX1TX8izKvWKMKztFwUk
P7agCwf9TRqaA1KgNpzeJIdl5Of6x5ZzJBTN0OgbaJ4YWa52fvfRCng8h0uwN89Tyjo4EPPLR22M
ZD08WkVKusqAfLjz56dMTM0CAwEAAaOCAgUwggIBMBIGA1UdEwEB/wQIMAYBAf8CAQEwDgYDVR0P
AQH/BAQDAgEGMCkGA1UdIAQiMCAwDQYLKwYBBAGBrSGCLB4wDwYNKwYBBAGBrSGCLAEBBDAdBgNV
HQ4EFgQUazqYi/nyU4na4K2yMh4JH+iqO3QwHwYDVR0jBBgwFoAUk+PYMiba1fFKpZFK4OpL4qIM
z+EwgY8GA1UdHwSBhzCBhDBAoD6gPIY6aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1nMi1jYS9wdWIvY3JsL2NhY3JsLmNybDBAoD6gPIY6aHR0cDovL2NkcDIucGNhLmRmbi5kZS9n
bG9iYWwtcm9vdC1nMi1jYS9wdWIvY3JsL2NhY3JsLmNybDCB3QYIKwYBBQUHAQEEgdAwgc0wMwYI
KwYBBQUHMAGGJ2h0dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBKBggrBgEF
BQcwAoY+aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1nMi1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwSgYIKwYBBQUHMAKGPmh0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJv
b3QtZzItY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQCBeEWkTqR/
DlXwCbFqPnjMaDWpHPOVnj/z+N9rOHeJLI21rT7H8pTNoAauusyosa0zCLYkhmI2THhuUPDVbmCN
T1IxQ5dGdfBi5G5mUcFCMWdQ5UnnOR7Ln8qGSN4IFP8VSytmm6A4nwDO/afr0X9XLchMX9wQEZc+
lgQCXISoKTlslPwQkgZ7nu7YRrQbtQMMONncsKk/cQYLsgMHM8KNSGMlJTx6e1du94oFOO+4oK4v
9NsH1VuEGMGpuEvObJAaguS5Pfp38dIfMwK/U+d2+dwmJUFvL6Yb+qQTkPp8ftkLYF3sv8pBoGH7
EUkp2KgtdRXYShjqFu9VNCIaE40GMIIF4DCCBMigAwIBAgIMIRX9tDE2QqO3mVLXMA0GCSqGSIb3
DQEBCwUAMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8VmVyZWluIHp1ciBGb2VyZGVydW5nIGVp
bmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYuMRAwDgYDVQQLDAdERk4tUEtJMSUw
IwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5nIENBMB4XDTE5MDYwNDE0MjkxMFoXDTIy
MDYwMzE0MjkxMFowfDELMAkGA1UEBhMCREUxIDAeBgNVBAoMF0ZhY2hob2Noc2NodWxlIE11ZW5z
dGVyMTIwMAYDVQQLDClGYWNoYmVyZWljaCBFbGVrdHJvdGVjaG5payB1bmQgSW5mb3JtYXRpazEX
MBUGA1UEAwwOTWljaGFlbCBUdWV4ZW4wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDM
r8qQcPxLFCxzPtXvRyM9KeQaxyMA8gwUNc7IIiATs6mRQFe5ib/mvwT9nc0bAa+94go6HJDiD3FJ
NkTo4u8aBsIcTt5pJtdBQLm88PLakbe3+fp/00//n7xxbTh7mAtFVCf25LxDCKkrdGk/+jglRq/R
VdwhZZ3VpYCrx8YfI/hIzdRL3+4I4z/mnQ8K0X8d2MVVPG+9nBEngdnYGez5f/8wIVOgEYYBc21k
yvMnVXLu2Ing+LwBd0gDG9Vasv87MNHCOZfJTNBlLhI2UDei/uNg9Zd4ynlMpPWZ7v0oiDWvmv8E
OuD4oric8heyD0OYK2FL4qcVC4dn4pnyulfHAgMBAAGjggJOMIICSjA+BgNVHSAENzA1MA8GDSsG
AQQBga0hgiwBAQQwEAYOKwYBBAGBrSGCLAEBBAQwEAYOKwYBBAGBrSGCLAIBBAQwCQYDVR0TBAIw
ADAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQW
BBTxiodBVL/lA4p5iNesIsJRhhgd6zAfBgNVHSMEGDAWgBRrOpiL+fJTidrgrbIyHgkf6Ko7dDAg
BgNVHREEGTAXgRV0dWV4ZW5AZmgtbXVlbnN0ZXIuZGUwgY0GA1UdHwSBhTCBgjA/oD2gO4Y5aHR0
cDovL2NkcDEucGNhLmRmbi5kZS9kZm4tY2EtZ2xvYmFsLWcyL3B1Yi9jcmwvY2FjcmwuY3JsMD+g
PaA7hjlodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2Rmbi1jYS1nbG9iYWwtZzIvcHViL2NybC9jYWNy
bC5jcmwwgdsGCCsGAQUFBwEBBIHOMIHLMDMGCCsGAQUFBzABhidodHRwOi8vb2NzcC5wY2EuZGZu
LmRlL09DU1AtU2VydmVyL09DU1AwSQYIKwYBBQUHMAKGPWh0dHA6Ly9jZHAxLnBjYS5kZm4uZGUv
ZGZuLWNhLWdsb2JhbC1nMi9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwSQYIKwYBBQUHMAKGPWh0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvZGZuLWNhLWdsb2JhbC1nMi9wdWIvY2FjZXJ0L2NhY2VydC5jcnQw
DQYJKoZIhvcNAQELBQADggEBABs3VlmIZ1VF3HkaQdjInZYmamRabbdgJ7cz6m6o/agKL7+Vhwx7
1BaaYs2gMa5Nu/GJ3YfdqIsUlYtKdl58Yhp/89E6xBfJkItS+rE8RFdf2XgklGlx7GmsvdA3tId5
b6K6r9a5wpVN0epxY6K8wwpzEib6fJLcHylybQXZ7JSOaLRLp6WU3QPoyTT7FpvAe/0b2MSCbPX4
fc53PCn2aGgXuRFVQeCn1SP1BF3QW1ppkFhcF6G+0JcUxYFAXE6r/71WZBvUHqoG/th2hAwQnS+Y
KhUYh4SZQH3/ursXXJYXQ5vyIhkN1FZlmtWA8+ofdCnoqSTbiSX2Aa/kKbTapwgxggOdMIIDmQIB
ATCBnjCBjTELMAkGA1UEBhMCREUxRTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9lcmRlcnVuZyBlaW5l
cyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBWLjEQMA4GA1UECwwHREZOLVBLSTElMCMG
A1UEAwwcREZOLVZlcmVpbiBHbG9iYWwgSXNzdWluZyBDQQIMIRX9tDE2QqO3mVLXMA0GCWCGSAFl
AwQCAQUAoIIBzzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0yMTAx
MjUxODM3MDhaMC8GCSqGSIb3DQEJBDEiBCA0AeEpTMk0ek6+FBVxtZ2hXBf9KZIGKJl8b/GfHCKf
UTCBrwYJKwYBBAGCNxAEMYGhMIGeMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8VmVyZWluIHp1
ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYuMRAwDgYD
VQQLDAdERk4tUEtJMSUwIwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5nIENBAgwhFf20
MTZCo7eZUtcwgbEGCyqGSIb3DQEJEAILMYGhoIGeMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8
VmVyZWluIHp1ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUu
IFYuMRAwDgYDVQQLDAdERk4tUEtJMSUwIwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5n
IENBAgwhFf20MTZCo7eZUtcwDQYJKoZIhvcNAQELBQAEggEAlFTyTZYlDxQCcdizA2QWn44DBpiG
kDBzBJOo2Bv96C/5b+mACnNuYJ81d07gHn7JCBB8s/9HbQUz7BSqJmDiUobmZ1rn23G16SGLwi8V
9XHj1NQUaCz12B/6a5ji2ikKgu5ITYqyKDb0wjofPray6u+NV1xyr/KO3ZrJrW/Drw9pDpX+xGPs
L518QMSMnUTLYktR+8TaOO97bN3LBexvMI7yra8Rd3USOujB+nxOT4hGBfXuH/84WHJf0OzigJTV
1yKW6TtYEDI+7AIHGcnV2FR8sTFc3ASmltb4Siu0lQHgzJOOmJDx0TY1uX8vfwaITrxjfGG440Hx
wkBTA0Gc8wAAAAAAAA==
--Apple-Mail=_A7EA20FE-A82F-4774-B4C5-2189DEE9BD61--


From nobody Mon Jan 25 10:38:28 2021
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 A7D5A3A1734 for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 10:38:26 -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 HCiUYQwJnfyV for <rtcweb@ietfa.amsl.com>; Mon, 25 Jan 2021 10:38:23 -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 4B8673A1731 for <rtcweb@ietf.org>; Mon, 25 Jan 2021 10:38:22 -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 AB85A7220C6CE; Mon, 25 Jan 2021 19:38:18 +0100 (CET)
From: Michael Tuexen <tuexen@fh-muenster.de>
Message-Id: <72719DA8-11DC-4B51-822A-49F643986389@fh-muenster.de>
Content-Type: multipart/signed; boundary="Apple-Mail=_2B95244D-A8F2-4A7F-BE81-AFA8F7B1E6C3"; 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:38:18 +0100
In-Reply-To: <CALaySJLX2eHrNogJ_f7FFRjyHLEasJa02-dbtgOwSmON_s2H9g@mail.gmail.com>
Cc: Victor Boivie <boivie@google.com>, Ted Hardie <ted.ietf@gmail.com>, 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>, sean+ietf@sn3rd.com, RTCWeb IETF <rtcweb@ietf.org>
To: Barry Leiba <barryleiba@computer.org>
References: <20210125092848.3AF95F40764@rfc-editor.org> <CA+9kkMBJTN-U0WNdSRJ6PdOPBHwayfWxUGebThr+iHOM_QmYqQ@mail.gmail.com> <CAFaRDoL1nCwVE=3g-O-CV-ZjVT6Ggb9rP8JX3rmMcnaLN62jPw@mail.gmail.com> <CALaySJLX2eHrNogJ_f7FFRjyHLEasJa02-dbtgOwSmON_s2H9g@mail.gmail.com>
X-Mailer: Apple Mail (2.3654.40.0.2.32)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/3G2w2CTkd2sZxleYQNiuNUigUMU>
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:38:27 -0000

--Apple-Mail=_2B95244D-A8F2-4A7F-BE81-AFA8F7B1E6C3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

> On 25. Jan 2021, at 19:33, Barry Leiba <barryleiba@computer.org> =
wrote:
>=20
> =46rom the point of view of "errata", though, the question is whether
> this was an omission that would have been fixed if it had been caught
> at the time of publication... or something that was not put in because
It was an omission.

Best regards
Michael
> it was considered to be covered elsewhere, so not an "error" in the
> RFC.
>=20
> It seems the latter, not the former.
>=20
> Barry
>=20
> On Mon, Jan 25, 2021 at 1:21 PM Victor Boivie <boivie@google.com> =
wrote:
>>=20
>> While I absolutely accept that rationale, Data Channel Establishment =
Protocol is layered on top of SCTP, and is not an SCTP extension (where =
I would definitely agree with what you're saying).
>>=20
>> While I can't see what the future brings, I could envision an =
evolution of RFC8832 being layered on top of e.g. QUIC or SRT, would the =
WebRTC project decide to change the underlying protocol from SCTP to =
something else in the future. That would be a separate RFC, though.
>>=20
>> Thanks and best regards,
>> Victor
>>=20
>> On Mon, Jan 25, 2021 at 6:40 PM Ted Hardie <ted.ietf@gmail.com> =
wrote:
>>>=20
>>> 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.
>>>=20
>>> Just my personal opinion,
>>>=20
>>> regards,
>>>=20
>>> Ted
>>>=20
>>> On Mon, Jan 25, 2021 at 1:28 AM RFC Errata System =
<rfc-editor@rfc-editor.org> wrote:
>>>>=20
>>>> The following errata report has been submitted for RFC8832,
>>>> "WebRTC Data Channel Establishment Protocol".
>>>>=20
>>>> --------------------------------------
>>>> You may review the report below and at:
>>>> https://www.rfc-editor.org/errata/eid6411
>>>>=20
>>>> --------------------------------------
>>>> Type: Technical
>>>> Reported by: Victor Boivie <boivie@google.com>
>>>>=20
>>>> Section: 5
>>>>=20
>>>> Original Text
>>>> -------------
>>>> 5.  Message Formats
>>>>=20
>>>>   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).
>>>>=20
>>>> Corrected Text
>>>> --------------
>>>> 5.  Message Formats
>>>>=20
>>>>   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).
>>>>=20
>>>>   All integer fields in an Data Channel Establishment Protocol =
message
>>>>   MUST be transmitted in network byte order, unless otherwise =
stated.
>>>>=20
>>>> Notes
>>>> -----
>>>> The byte order of integer fields in the protocol messages is not =
defined.
>>>>=20
>>>> 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.
>>>>=20
>>>> --------------------------------------
>>>> 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=C3=BCxen
>>>> Category            : PROPOSED STANDARD
>>>> Source              : Real-Time Communication in WEB-browsers
>>>> Area                : Applications and Real-Time
>>>> Stream              : IETF
>>>> Verifying Party     : IESG


--Apple-Mail=_2B95244D-A8F2-4A7F-BE81-AFA8F7B1E6C3
Content-Disposition: attachment;
	filename=smime.p7s
Content-Type: application/pkcs7-signature;
	name=smime.p7s
Content-Transfer-Encoding: base64

MIAGCSqGSIb3DQEHAqCAMIACAQExDzANBglghkgBZQMEAgEFADCABgkqhkiG9w0BBwEAAKCCEKow
ggUSMIID+qADAgECAgkA4wvV+K8l2YEwDQYJKoZIhvcNAQELBQAwgYIxCzAJBgNVBAYTAkRFMSsw
KQYDVQQKDCJULVN5c3RlbXMgRW50ZXJwcmlzZSBTZXJ2aWNlcyBHbWJIMR8wHQYDVQQLDBZULVN5
c3RlbXMgVHJ1c3QgQ2VudGVyMSUwIwYDVQQDDBxULVRlbGVTZWMgR2xvYmFsUm9vdCBDbGFzcyAy
MB4XDTE2MDIyMjEzMzgyMloXDTMxMDIyMjIzNTk1OVowgZUxCzAJBgNVBAYTAkRFMUUwQwYDVQQK
EzxWZXJlaW4genVyIEZvZXJkZXJ1bmcgZWluZXMgRGV1dHNjaGVuIEZvcnNjaHVuZ3NuZXR6ZXMg
ZS4gVi4xEDAOBgNVBAsTB0RGTi1QS0kxLTArBgNVBAMTJERGTi1WZXJlaW4gQ2VydGlmaWNhdGlv
biBBdXRob3JpdHkgMjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAMtg1/9moUHN0vqH
l4pzq5lN6mc5WqFggEcVToyVsuXPztNXS43O+FZsFVV2B+pG/cgDRWM+cNSrVICxI5y+NyipCf8F
XRgPxJiZN7Mg9mZ4F4fCnQ7MSjLnFp2uDo0peQcAIFTcFV9Kltd4tjTTwXS1nem/wHdN6r1ZB+Ba
L2w8pQDcNb1lDY9/Mm3yWmpLYgHurDg0WUU2SQXaeMpqbVvAgWsRzNI8qIv4cRrKO+KA3Ra0Z3qL
NupOkSk9s1FcragMvp0049ENF4N1xDkesJQLEvHVaY4l9Lg9K7/AjsMeO6W/VRCrKq4Xl14zzsjz
9AkH4wKGMUZrAcUQDBHHWekCAwEAAaOCAXQwggFwMA4GA1UdDwEB/wQEAwIBBjAdBgNVHQ4EFgQU
k+PYMiba1fFKpZFK4OpL4qIMz+EwHwYDVR0jBBgwFoAUv1kgNgB5oKAia4zV8mHSuCzLgkowEgYD
VR0TAQH/BAgwBgEB/wIBAjAzBgNVHSAELDAqMA8GDSsGAQQBga0hgiwBAQQwDQYLKwYBBAGBrSGC
LB4wCAYGZ4EMAQICMEwGA1UdHwRFMEMwQaA/oD2GO2h0dHA6Ly9wa2kwMzM2LnRlbGVzZWMuZGUv
cmwvVGVsZVNlY19HbG9iYWxSb290X0NsYXNzXzIuY3JsMIGGBggrBgEFBQcBAQR6MHgwLAYIKwYB
BQUHMAGGIGh0dHA6Ly9vY3NwMDMzNi50ZWxlc2VjLmRlL29jc3ByMEgGCCsGAQUFBzAChjxodHRw
Oi8vcGtpMDMzNi50ZWxlc2VjLmRlL2NydC9UZWxlU2VjX0dsb2JhbFJvb3RfQ2xhc3NfMi5jZXIw
DQYJKoZIhvcNAQELBQADggEBAIcL/z4Cm2XIVi3WO5qYi3FP2ropqiH5Ri71sqQPrhE4eTizDnS6
dl2e6BiClmLbTDPo3flq3zK9LExHYFV/53RrtCyD2HlrtrdNUAtmB7Xts5et6u5/MOaZ/SLick0+
hFvu+c+Z6n/XUjkurJgARH5pO7917tALOxrN5fcPImxHhPalR6D90Bo0fa3SPXez7vTXTf/D6OWS
T1k+kEcQSrCFWMBvf/iu7QhCnh7U3xQuTY+8npTD5+32GPg8SecmqKc22CzeIs2LgtjZeOJVEqM7
h0S2EQvVDFKvaYwPBt/QolOLV5h7z/0HJPT8vcP9SpIClxvyt7bPZYoaorVyGTkwggWsMIIElKAD
AgECAgcbY7rQHiw9MA0GCSqGSIb3DQEBCwUAMIGVMQswCQYDVQQGEwJERTFFMEMGA1UEChM8VmVy
ZWluIHp1ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYu
MRAwDgYDVQQLEwdERk4tUEtJMS0wKwYDVQQDEyRERk4tVmVyZWluIENlcnRpZmljYXRpb24gQXV0
aG9yaXR5IDIwHhcNMTYwNTI0MTEzODQwWhcNMzEwMjIyMjM1OTU5WjCBjTELMAkGA1UEBhMCREUx
RTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9lcmRlcnVuZyBlaW5lcyBEZXV0c2NoZW4gRm9yc2NodW5n
c25ldHplcyBlLiBWLjEQMA4GA1UECwwHREZOLVBLSTElMCMGA1UEAwwcREZOLVZlcmVpbiBHbG9i
YWwgSXNzdWluZyBDQTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAJ07eRxH3h+Gy8Zp
1xCeOdfZojDbchwFfylfS2jxrRnWTOFrG7ELf6Gr4HuLi9gtzm6IOhDuV+UefwRRNuu6cG1joL6W
LkDh0YNMZj0cZGnlm6Stcq5oOVGHecwX064vXWNxSzl660Knl5BpBb+Q/6RAcL0D57+eGIgfn5mI
TQ5HjUhfZZkQ0tkqSe3BuS0dnxLLFdM/fx5ULzquk1enfnjK1UriGuXtQX1TX8izKvWKMKztFwUk
P7agCwf9TRqaA1KgNpzeJIdl5Of6x5ZzJBTN0OgbaJ4YWa52fvfRCng8h0uwN89Tyjo4EPPLR22M
ZD08WkVKusqAfLjz56dMTM0CAwEAAaOCAgUwggIBMBIGA1UdEwEB/wQIMAYBAf8CAQEwDgYDVR0P
AQH/BAQDAgEGMCkGA1UdIAQiMCAwDQYLKwYBBAGBrSGCLB4wDwYNKwYBBAGBrSGCLAEBBDAdBgNV
HQ4EFgQUazqYi/nyU4na4K2yMh4JH+iqO3QwHwYDVR0jBBgwFoAUk+PYMiba1fFKpZFK4OpL4qIM
z+EwgY8GA1UdHwSBhzCBhDBAoD6gPIY6aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9v
dC1nMi1jYS9wdWIvY3JsL2NhY3JsLmNybDBAoD6gPIY6aHR0cDovL2NkcDIucGNhLmRmbi5kZS9n
bG9iYWwtcm9vdC1nMi1jYS9wdWIvY3JsL2NhY3JsLmNybDCB3QYIKwYBBQUHAQEEgdAwgc0wMwYI
KwYBBQUHMAGGJ2h0dHA6Ly9vY3NwLnBjYS5kZm4uZGUvT0NTUC1TZXJ2ZXIvT0NTUDBKBggrBgEF
BQcwAoY+aHR0cDovL2NkcDEucGNhLmRmbi5kZS9nbG9iYWwtcm9vdC1nMi1jYS9wdWIvY2FjZXJ0
L2NhY2VydC5jcnQwSgYIKwYBBQUHMAKGPmh0dHA6Ly9jZHAyLnBjYS5kZm4uZGUvZ2xvYmFsLXJv
b3QtZzItY2EvcHViL2NhY2VydC9jYWNlcnQuY3J0MA0GCSqGSIb3DQEBCwUAA4IBAQCBeEWkTqR/
DlXwCbFqPnjMaDWpHPOVnj/z+N9rOHeJLI21rT7H8pTNoAauusyosa0zCLYkhmI2THhuUPDVbmCN
T1IxQ5dGdfBi5G5mUcFCMWdQ5UnnOR7Ln8qGSN4IFP8VSytmm6A4nwDO/afr0X9XLchMX9wQEZc+
lgQCXISoKTlslPwQkgZ7nu7YRrQbtQMMONncsKk/cQYLsgMHM8KNSGMlJTx6e1du94oFOO+4oK4v
9NsH1VuEGMGpuEvObJAaguS5Pfp38dIfMwK/U+d2+dwmJUFvL6Yb+qQTkPp8ftkLYF3sv8pBoGH7
EUkp2KgtdRXYShjqFu9VNCIaE40GMIIF4DCCBMigAwIBAgIMIRX9tDE2QqO3mVLXMA0GCSqGSIb3
DQEBCwUAMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8VmVyZWluIHp1ciBGb2VyZGVydW5nIGVp
bmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYuMRAwDgYDVQQLDAdERk4tUEtJMSUw
IwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5nIENBMB4XDTE5MDYwNDE0MjkxMFoXDTIy
MDYwMzE0MjkxMFowfDELMAkGA1UEBhMCREUxIDAeBgNVBAoMF0ZhY2hob2Noc2NodWxlIE11ZW5z
dGVyMTIwMAYDVQQLDClGYWNoYmVyZWljaCBFbGVrdHJvdGVjaG5payB1bmQgSW5mb3JtYXRpazEX
MBUGA1UEAwwOTWljaGFlbCBUdWV4ZW4wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDM
r8qQcPxLFCxzPtXvRyM9KeQaxyMA8gwUNc7IIiATs6mRQFe5ib/mvwT9nc0bAa+94go6HJDiD3FJ
NkTo4u8aBsIcTt5pJtdBQLm88PLakbe3+fp/00//n7xxbTh7mAtFVCf25LxDCKkrdGk/+jglRq/R
VdwhZZ3VpYCrx8YfI/hIzdRL3+4I4z/mnQ8K0X8d2MVVPG+9nBEngdnYGez5f/8wIVOgEYYBc21k
yvMnVXLu2Ing+LwBd0gDG9Vasv87MNHCOZfJTNBlLhI2UDei/uNg9Zd4ynlMpPWZ7v0oiDWvmv8E
OuD4oric8heyD0OYK2FL4qcVC4dn4pnyulfHAgMBAAGjggJOMIICSjA+BgNVHSAENzA1MA8GDSsG
AQQBga0hgiwBAQQwEAYOKwYBBAGBrSGCLAEBBAQwEAYOKwYBBAGBrSGCLAIBBAQwCQYDVR0TBAIw
ADAOBgNVHQ8BAf8EBAMCBeAwHQYDVR0lBBYwFAYIKwYBBQUHAwIGCCsGAQUFBwMEMB0GA1UdDgQW
BBTxiodBVL/lA4p5iNesIsJRhhgd6zAfBgNVHSMEGDAWgBRrOpiL+fJTidrgrbIyHgkf6Ko7dDAg
BgNVHREEGTAXgRV0dWV4ZW5AZmgtbXVlbnN0ZXIuZGUwgY0GA1UdHwSBhTCBgjA/oD2gO4Y5aHR0
cDovL2NkcDEucGNhLmRmbi5kZS9kZm4tY2EtZ2xvYmFsLWcyL3B1Yi9jcmwvY2FjcmwuY3JsMD+g
PaA7hjlodHRwOi8vY2RwMi5wY2EuZGZuLmRlL2Rmbi1jYS1nbG9iYWwtZzIvcHViL2NybC9jYWNy
bC5jcmwwgdsGCCsGAQUFBwEBBIHOMIHLMDMGCCsGAQUFBzABhidodHRwOi8vb2NzcC5wY2EuZGZu
LmRlL09DU1AtU2VydmVyL09DU1AwSQYIKwYBBQUHMAKGPWh0dHA6Ly9jZHAxLnBjYS5kZm4uZGUv
ZGZuLWNhLWdsb2JhbC1nMi9wdWIvY2FjZXJ0L2NhY2VydC5jcnQwSQYIKwYBBQUHMAKGPWh0dHA6
Ly9jZHAyLnBjYS5kZm4uZGUvZGZuLWNhLWdsb2JhbC1nMi9wdWIvY2FjZXJ0L2NhY2VydC5jcnQw
DQYJKoZIhvcNAQELBQADggEBABs3VlmIZ1VF3HkaQdjInZYmamRabbdgJ7cz6m6o/agKL7+Vhwx7
1BaaYs2gMa5Nu/GJ3YfdqIsUlYtKdl58Yhp/89E6xBfJkItS+rE8RFdf2XgklGlx7GmsvdA3tId5
b6K6r9a5wpVN0epxY6K8wwpzEib6fJLcHylybQXZ7JSOaLRLp6WU3QPoyTT7FpvAe/0b2MSCbPX4
fc53PCn2aGgXuRFVQeCn1SP1BF3QW1ppkFhcF6G+0JcUxYFAXE6r/71WZBvUHqoG/th2hAwQnS+Y
KhUYh4SZQH3/ursXXJYXQ5vyIhkN1FZlmtWA8+ofdCnoqSTbiSX2Aa/kKbTapwgxggOdMIIDmQIB
ATCBnjCBjTELMAkGA1UEBhMCREUxRTBDBgNVBAoMPFZlcmVpbiB6dXIgRm9lcmRlcnVuZyBlaW5l
cyBEZXV0c2NoZW4gRm9yc2NodW5nc25ldHplcyBlLiBWLjEQMA4GA1UECwwHREZOLVBLSTElMCMG
A1UEAwwcREZOLVZlcmVpbiBHbG9iYWwgSXNzdWluZyBDQQIMIRX9tDE2QqO3mVLXMA0GCWCGSAFl
AwQCAQUAoIIBzzAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0yMTAx
MjUxODM4MThaMC8GCSqGSIb3DQEJBDEiBCBPXj8WysoOHxUp/9klbe3Xvmpl09i7lvQbzmJC/WiD
kTCBrwYJKwYBBAGCNxAEMYGhMIGeMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8VmVyZWluIHp1
ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUuIFYuMRAwDgYD
VQQLDAdERk4tUEtJMSUwIwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5nIENBAgwhFf20
MTZCo7eZUtcwgbEGCyqGSIb3DQEJEAILMYGhoIGeMIGNMQswCQYDVQQGEwJERTFFMEMGA1UECgw8
VmVyZWluIHp1ciBGb2VyZGVydW5nIGVpbmVzIERldXRzY2hlbiBGb3JzY2h1bmdzbmV0emVzIGUu
IFYuMRAwDgYDVQQLDAdERk4tUEtJMSUwIwYDVQQDDBxERk4tVmVyZWluIEdsb2JhbCBJc3N1aW5n
IENBAgwhFf20MTZCo7eZUtcwDQYJKoZIhvcNAQELBQAEggEAjdgoo42Y2lH90bdNgMBrh9thAW9Q
wxKb6OQ9OqaFKXD51tO0HAMgZXxBYj+mIeBBG5W1BuaqFcJ8/THavmZUPyodn8CCpLEU7mC7k+u3
WgVpxcvjzn/z/0jjZKJ9nM1r5P8qfP0ZrK6wEdr8niTRRaT/joXbFg+EaQ1NYuPyI/uqJB3YQTee
evQbnFAHeUFff/23UJUWVue8yKZ/qkuBNssp4UjKLE91P1QIrEVR1lXK80Cz1DUPRrNj/1T59hH6
bjCrkO/xU7QbtT1zCFNSpZWqxYBVp8dH6+GrV5U55julkInEOlOEykbFLFH7MiIb7mdf2qE6/JmZ
9lO7occQuQAAAAAAAA==
--Apple-Mail=_2B95244D-A8F2-4A7F-BE81-AFA8F7B1E6C3--


From nobody Tue Jan 26 01:28:06 2021
Return-Path: <harald@alvestrand.no>
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 4F68B3A086E for <rtcweb@ietfa.amsl.com>; Tue, 26 Jan 2021 01:28:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.002
X-Spam-Level: 
X-Spam-Status: No, score=0.002 tagged_above=-999 required=5 tests=[NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham 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 rmDxS7we4xtu for <rtcweb@ietfa.amsl.com>; Tue, 26 Jan 2021 01:28:03 -0800 (PST)
Received: from mork.alvestrand.no (mork.alvestrand.no [158.38.152.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F6223A017E for <rtcweb@ietf.org>; Tue, 26 Jan 2021 01:28:03 -0800 (PST)
Received: from [192.168.3.157] (unknown [188.113.93.42]) by mork.alvestrand.no (Postfix) with ESMTPSA id BA9F87C64F6 for <rtcweb@ietf.org>; Tue, 26 Jan 2021 10:28:01 +0100 (CET)
To: rtcweb@ietf.org
References: <20210125092848.3AF95F40764@rfc-editor.org>
From: Harald Alvestrand <harald@alvestrand.no>
Message-ID: <e3c7aa2c-c3c6-f44f-fbd8-c017eae0f4d2@alvestrand.no>
Date: Tue, 26 Jan 2021 10:28:01 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.1
MIME-Version: 1.0
In-Reply-To: <20210125092848.3AF95F40764@rfc-editor.org>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtcweb/M1IB6a8UxuBK3Dxj3PKgEbTpOBk>
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: Tue, 26 Jan 2021 09:28:05 -0000

I recommend this to be "accepted, held for update".

Just to have said this before the merge (which may be late or may be 
never) ... I see no reason for allowing "unless otherwise stated", and 
the new sentence should come before the existing paragraph, not after it.

On 1/25/21 10:28 AM, RFC Errata System 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
>
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb

