Transports for WebRTC
draft-ietf-rtcweb-transports-17

Approval announcement
Draft of message to be sent after approval:

Announcement

From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: draft-ietf-rtcweb-transports@ietf.org, rtcweb-chairs@ietf.org, alissa@cooperw.in, rtcweb@ietf.org, fluffy@iii.ca, "The IESG" <iesg@ietf.org>, rfc-editor@rfc-editor.org
Subject: Protocol Action: 'Transports for WebRTC' to Proposed Standard (draft-ietf-rtcweb-transports-17.txt)

The IESG has approved the following document:
- 'Transports for WebRTC'
  (draft-ietf-rtcweb-transports-17.txt) as Proposed Standard

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

The IESG contact persons are Alexey Melnikov, Ben Campbell and Alissa
Cooper.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-rtcweb-transports/

Ballot Text

Technical Summary

  This document describes the data transport protocols used by WebRTC,
  including the protocols used for interaction with intermediate boxes
  such as firewalls, relays and NAT boxes.

Working Group Summary

  Nothing particularly controversial in this spec. It is largely just a 
  pointer to other specifications saying if you do WebRTC, then you need 
  to what RFC X,Y, and Z says. 

  Based on the WGLC comments, the chairs suggest adding an RFC Ed note 
  to include an informative reference to draft-ietf-rtcweb-return 
  however there is not WG consensus to make this a MUST or SHOULD 
  implement. (Cleary nothing forbids implementing it so it is already an 
  MAY implement)

Document Quality

  Much of this is implemented in chrome and firefox which share a 
  significant amount of code with respect to this so some parts of it 
  has 2 implementations, some parts 1, and some none. 

Personnel

  Cullen Jennings is the document shepherd. Alissa Cooper is the 
  responsible AD.

RFC Editor Note