Protocol Action: 'WebRTC Data Channels' to Proposed Standard (draft-ietf-rtcweb-data-channel-13.txt)

The IESG <> Thu, 08 January 2015 14:38 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E40BD1A0366; Thu, 8 Jan 2015 06:38:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fZVARM7UyiU2; Thu, 8 Jan 2015 06:38:07 -0800 (PST)
Received: from (localhost [IPv6:::1]) by (Postfix) with ESMTP id CD9A31A1BEC; Thu, 8 Jan 2015 06:38:02 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
From: The IESG <>
To: IETF-Announce <>
Subject: Protocol Action: 'WebRTC Data Channels' to Proposed Standard (draft-ietf-rtcweb-data-channel-13.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.10.0.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <>
Date: Thu, 08 Jan 2015 06:38:02 -0800
Archived-At: <>
Cc: rtcweb mailing list <>, rtcweb chair <>, RFC Editor <>
X-Mailman-Version: 2.1.15
List-Id: "IETF announcement list. No discussions." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 08 Jan 2015 14:38:14 -0000

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:

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:

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.


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