Gaining and Maintaining Consent for Real-Time Applications
draft-thomson-rtcweb-consent-00
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Martin Thomson , Dan Wing , Cullen Fluffy Jennings | ||
Last updated | 2014-05-12 (Latest revision 2013-11-20) | ||
Replaced by | draft-ietf-rtcweb-stun-consent-freshness | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-rtcweb-stun-consent-freshness | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes how DTLS provides a WebRTC application a clear indication that a receiver is willing to receive packets. Mechanisms are described for maintaining that consent are described.
Authors
Martin Thomson
Dan Wing
Cullen Fluffy Jennings
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)