Sign in
Version 5.12.0.p2, 2015-03-02
Report a bug

STUN Usage for Consent Freshness

Document type: Replaced Internet-Draft (rtcweb WG)
Document stream: IETF
Last updated: 2013-09-23 (latest revision 2013-07-15)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

IETF State: Adopted by a WG
Other - see Comment Log
Document shepherd: No shepherd assigned

IESG State: Replaced by draft-ietf-rtcweb-stun-consent-freshness
Responsible AD: (None)
Send notices to: No addresses provided

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found here:


Verification of peer consent before sending traffic 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 application may want to detect connection failure and take appropriate action. This document describes how a WebRTC browser can verify peer consent to continue sending traffic and detect connection failure.


Muthu Perumal <>
Dan Wing <>
Ram R <>
Tirumaleswar Reddy <>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)