1. Survey of WebRTC based P2P Streaming
draft-huang-ppsp-p2p-webrtc-survey-00
PPSP WG
IETF 89 London
Rachel Huang, Yunfei Zhang

2. Goals
Survey of architecture and communication process of current emerging WebRTC based P2P applications.
Promote discussion of the possibility of incorporating P2P streaming into WebRTC.

3. Traditional Web Based P2P Streaming Applications
Web Servers
Trackers
Tracker
protocol
HTTP
Tracker
protocol
Tracker
protocol
HTTP
HTTP
JavaScript
JavaScript
JavaScript
Plug-in
Plug-in
Plug-in
Peer in
Browser
Peer in
Browser
Peer in
Browser
Peer protocol

4. SwarmCDN and Peer CDN Web Server Coordinator Data channel Usage
Content distribution for web site owners
Communication between endpoint and coordinator
Proprietary protocol
Communication between endpoints
Data channel of WebRTC
Characteristic
Not P2P streaming,
No slice.
browsers
Only Chrome and FireFox support data channel
Private
Protocol over HTTP
HTTP
Private
Protocol over HTTP
HTTP
Data channel
JavaScript
JavaScript
WebRTC
Browser
WebRTC
Browser

5. Sharefest Usage File sharing
Communication between endpoint and coordinator
Private protocol
Communication between endpoints
Data channel of WebRTC
Characteristic
Not P2P streaming, just for file transfering.
Supporting slicing.
Available browsers
Only Chrome and FireFox support data channel

6. P2P Media Streaming with HTML5 and WebRTC - An Experiment from Aalto University
Usage
VoD service
Communication between endpoint and coordinator
tracker protocol
Communication between endpoints
Data channel of WebRTC
Characteristic
P2P streaming.
Similar to BitTorrent architecture.
Available browsers
Only Chrome and FireFox support data channel
Initially a Peer creates a torrent file
containing the metadata of the video, hashes of each piece of
the video, and uploads the torrent file to the Tracker (1). The
actual video is uploaded to the Seeder (2). When another Peer
requests the same video, the Peer first obtains the respective
tracker file and starts downloading the video pieces from the
Seeder or the original Peer or both (3). Eventually, as the video
becomes popular, missing pieces are shared by Peers, which
decreases the load on the original Peer and Seeder. Periodic
access to the Tracker for requesting the latest Peer information
is needed (4).

7. Summary
Current commercial WebRTC based P2P applications are not P2P streaming related.
Obviously, web applications supporting P2P streaming without plug-ins are more and more appealing, since technologies are ready.
The current scope of RTCWEB only points to conversational applications not streaming systems.

8. Discussions Should we incorporate P2P streaming in RTCWEB scenarios?
How to support P2P algorithms? (JavaScript can support them or not?)
Do we need WebRTC browsers to support the tracker protocol?
If no, does the tracker protocol need to do some changes?
Do we need WebRTC browsers to support the peer protocol? (data channel already supported)
If no, does the peer protocol need to do some changes?
Any security or performance issues ? e.g., content integrity protection.

9. Thank You !