1 / 9

PPSP Protocol Requirements Draft: Meeting the Essentials for Peer-to-Peer Streaming

This document outlines basic to advanced requirements for PPSP nodes, encompassing tracker, peer, content resource, message format, process flow, error handling, overload protection, security, additional terms like Peer list, Swarm ID, Chunk ID, and Buffer Map. The -03 version introduces unique identifier requisites for peers, public identity for trackers, content identification by swarm ID, chunk partitioning, and classification into different usage types. Tracker and peer protocols are detailed with message parameters and traffic optimization services. Error handling mandates TCP-based transport for reliable signaling message transmission.

sduet
Download Presentation

PPSP Protocol Requirements Draft: Meeting the Essentials for Peer-to-Peer Streaming

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. P2P Streaming Protocol (PPSP) Requirementsdraft-zong-ppsp-reqs-03

  2. Requirements Overview • Basic requirements to PPSP nodes (tracker and peer) and the content resource. • General requirements to the message format and process flow of PPSP tracker protocol and PPSP peer protocol. • Error handling and overload protection requirements. • Security requirements.

  3. Changes in -03 • Defined some additional terms • Peer list • A list of peer ID which are in a same swarm maintained bythe PPSP tracker • Swarm ID • An identifier of certain swarm. It is used to describe a specific resource shared among peers. • Chunk ID • An identifier of certain chunk in a resource which shows the position (e.g. time) of the chunk in the whole content resource (e.g. live streaming). • Buffer Map • A map indicating which chunks a peer currently has buffered and can share with other peers.

  4. Changes in -03 • Add some requirements to PPSP nodes • Each peer in PPSP MUST has a unique identifier, i.e. peer ID. • The tracker in PPSP MUST has a public identity that can be discovered and accessed by PPSP peers.

  5. Changes in -03 • Add some requirements to PPSP content resource • The content in PPSP MUST be identified by swarm ID. • The content resource shared by a swarm in PPSP MUST allow being partitioned into chunks with a standard format (defined by some out-of-band mechanism, e.g. meta data). • The content resources shared in PPSP MUST be classified and identified by different usage types (e.g. live, VoD). (Open Q: out-of-band mechanism?)

  6. Changes in -03 • Add some requirements to PPSP tracker protocol • The tracker request message MAY include parameter of requested number of downloading peers or preferred downloading bandwidth. • The PPSP tracker MAY generate the peer list with the help of traffic optimization services, e.g. Alto. (Open Q: implementation issue of tracker?)

  7. Changes in -03 • Add some requirements to PPSP peer protocol • The content availability update message MUST be advertised among swarm peers periodically or on-demand. (Open Q: MAY or MUST?) • The peer streaming status update information MAY be advertised among peers.

  8. Changes in -03 • Add some requirements to error handling and overload protection • The PPSP tracker protocol and peer protocol MUST use TCP based transport to ensure the reliability during the signaling message transmission. (Open Q: consensus on TCP?)

  9. Thank you

More Related