Security Authentication of WebRTC Communication Service for Telephony Terminal
draft-cheng-rtcweb-teleauth-00

Document Type Expired Internet-Draft (individual)
Last updated 2014-08-22 (latest revision 2014-02-18)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-cheng-rtcweb-teleauth-00.txt

Abstract

The WebRTC use-cases and related requirements are defined in [draft-ietf-rtcweb-use-cases-and-requirements] that contains browser to browser use-cases and browser-GW/server use-cases (e.g., telephony terminal). In the use-case of telephony terminal, it is necessary for telephony terminal to be able to attest his identity to the telephony operator. Unlike the current authentication specified in [draft-ietf-rtcweb-security] such as PKI based authentication and web based peer authentication WebRTC communication is directly controlled by the telephony operator, which poses new authentication methods, including re-using existence authentication mechanism of telephony operator and authentication by using web credentials. This document presents the security authentication of WebRTC communication for telephony terminal.

Authors

Minpeng Qi (qiminpeng@chinamobile.com)
Judy Zhu (zhuhongru@chinamobile.com)
Ziyao Cheng (chengziyao@chinamobile.com)

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