Real-Time Web Communication by using XMPP Jingle
draft-suzuki-rtcweb-jingle-web-00

 
Document
Type Expired Internet-Draft (individual)
Last updated 2012-08-31 (latest revision 2012-02-28)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

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

Abstract

XMPP Jingle specification defines an XMPP protocol extension for managing peer-to-peer media sessions between two users. And XMPP Jingle can manage multi contents simultaneously in one Jingle stream, but in the XMPP world there is no common way to layout variable multi contents on each display. In this document, a solution to this issue is provided by using Web browser's layout function. This document describes a new concept to realize one of solutions of RTCWeb. Of course, "Web Browser" is used for Web application's frontend for real-time communication, and XMPP Jingle specification (XEP-166) is used as signaling protocol. And a simple mapping manner between jingle contents and HTML graphical elements enables to unite Web browser's layout function and Jingle's media content management function to realize RTCWeb functions.

Authors

Yoshihiro Suzuki (hiro.suzuki@d3communications.jp)
Nobuo Ogashiwa (ogashiwa@c.kyoai.ac.jp)

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