[rtcweb] Protocol Action: 'WebRTC Data Channel Establishment Protocol' to Proposed Standard (draft-ietf-rtcweb-data-protocol-09.txt)

The IESG <iesg-secretary@ietf.org> Thu, 08 January 2015 14:39 UTC

Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150108143933.26487.75577.idtracker@ietfa.amsl.com>
Date: Thu, 08 Jan 2015 06:39:33 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtcweb/-pr3bp0Eva76d668XPp-pet75c4>
Cc: rtcweb mailing list <rtcweb@ietf.org>, rtcweb chair <rtcweb-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [rtcweb] Protocol Action: 'WebRTC Data Channel Establishment Protocol' to Proposed Standard (draft-ietf-rtcweb-data-protocol-09.txt)

The IESG has approved the following document:
- 'WebRTC Data Channel Establishment Protocol'
(draft-ietf-rtcweb-data-protocol-09.txt) as Proposed Standard

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

The IESG contact persons are Richard Barnes and Alissa Cooper.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-rtcweb-data-protocol/

Technical Summary:

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.

Working Group Summary:

There was early discussion of the stacking order, but there has been no significant controversy since that was fixed. There have been a number of discussion on how to manage particular aspects of the larger context (e.g. WebRTC-level congestion control, since SCTP manages congestion control at the association level) and this has played a part in those, but not in any way that mde it the focus of controversy.

Document Quality:

Are there existing implementations of the protocol? Have a significant number of vendors indicated their plan to implement the specification? Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted?\

There are implmentations of previous versions of this document, and we expect updates to them to the final version. Vendor support seems solid. This document did not require expert review of the types noted.

Personnel:
The document shepherd is Ted Hardie; the responsible Area Director is Richard Barnes.

[rtcweb] Protocol Action: 'WebRTC Data Channel Es… The IESG