datatracker.ietf.org
Sign in
Version 5.7.4, 2014-11-12
Report a bug

STUN Usage for Consent Freshness
draft-muthu-behave-consent-freshness-04

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:
http://www.ietf.org/archive/id/draft-muthu-behave-consent-freshness-04.txt

Abstract

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.

Authors

Muthu Perumal <mperumal@cisco.com>
Dan Wing <dwing@cisco.com>
Ram R <rmohanr@cisco.com>
Tirumaleswar Reddy <tireddy@cisco.com>

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