Sign in
Version 5.13.0, 2015-03-25
Report a bug

RTCWEB Generic Identity Provider Interface

Document type: Expired Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2012-09-13 (latest revision 2012-03-12)
Intended RFC status: Unknown
Other versions: (expired, archived): plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: Expired
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:


Security for RTCWEB communications requires that the communicating endpoints be able to authenticate each other. While authentication may be mediated by the calling service, there are settings in which this is undesirable. This document describes a generic mechanism for leveraging existing identity providers (IdPs) such as BrowserID or OAuth to provide this authentication service.


Eric Rescorla <>

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