STUN Usage for Consent Freshness and Session Liveness
draft-muthu-behave-consent-freshness-01
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Authors | Muthu Arul Perumal , Dan Wing , Hadriel Kaplan | ||
| Last updated | 2013-01-17 (Latest revision 2012-07-16) | ||
| Replaced by | draft-ietf-rtcweb-stun-consent-freshness, RFC 7675 | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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
Verification of peer consent is necessary in WebRTC deployments to ensure that a malicious JavaScript cannot use the browser as a platform for launching attacks. A related problem is session liveness. WebRTC applications may want to detect connection failure and take appropriate actions. This document describes a STUN usage that enables a WebRTC browser to perform the following on a candidate pair ICE is using for a media component after session establishment:
Authors
Muthu Arul Perumal
Dan Wing
Hadriel Kaplan
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)