RTCWeb standard signaling protocol
draft-partha-rtcweb-signaling-00

Document Type Expired Internet-Draft (individual)
Last updated 2012-04-05 (latest revision 2011-10-03)
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-partha-rtcweb-signaling-00.txt

Abstract

The standardization of Real time communication between browsers is to provide the infrastructure for audio, video, text communication using standard interface so that interoperable communication can be established between any compatible browsers. RTCWeb specific Javascript API will be provided by browsers for developing real-time web application. It is possible to develop signaling protocol like Session Initiation Protocol (SIP) or Jingle or websocket extension or custom-made signaling protocol in Javascript. There are lots of issues in Javascript based signaling protocol. This document list the need for standard signaling protocol between RTCWeb client (browser) and RTCWeb server and possible signaling protocol for the same.

Authors

Parthasarathi Ravindran (pravindran@sonusnet.com)

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