WebRTC Data Channels
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org>, rtcweb mailing list <email@example.com>, rtcweb chair <firstname.lastname@example.org> Subject: Protocol Action: 'WebRTC Data Channels' to Proposed Standard (draft-ietf-rtcweb-data-channel-13.txt) The IESG has approved the following document: - 'WebRTC Data Channels' (draft-ietf-rtcweb-data-channel-13.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-channel/
Technical Summary: This document specifies the nonmedia 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. WebRTClevel 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: 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.