SIP APIs for Communications on the Web
draft-sinnreich-sip-web-apis-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Alan Johnston | ||
| Last updated | 2010-06-21 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This memo describes a standards based approach to enable web based interactive multimedia communications. The objective is giving web developers the software tools to add communication widgets to web pages. The proposed SIP API does not necessarily require SIP protocol expertise by web developers for basic multimedia communications though it can be extended to port complex VoIP services to the web. The SIP API can also support the transition from network infrastructure based VoIP to rich web based communications. The benefits of the formal REST architecture of the web are extended to real time communications. Only two standard application layer protocols are required: HTTP for signaling data communications such as in SIP and/or XMPP and UDP for real time media transport. We consider replacing SDP with metadata about media, displays and user controls. RTP data functionality can also be moved to the application itself. NAT traversal and other functions are delegated to HIP.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)