IETF-76 PPSP BOF

585 views
520 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
585
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
6
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

IETF-76 PPSP BOF

  1. 1. P2P Streaming Protocol (PPSP) Requirements draft-zong-ppsp-reqs-02 Ning Zong Yunfei Zhang Victor Pascual Carl Williams
  2. 2. Requirements Overview <ul><li>General functionalities of PPSP tracker protocol and basic types of information communicated by PPSP tracker protocol. </li></ul><ul><li>General functionalities of PPSP peer protocol and basic types of information communicated by PPSP peer protocol. </li></ul><ul><li>Error handling and overload protection requirements. </li></ul><ul><li>Security requirements. </li></ul>
  3. 3. PPSP Tracker Protocol Requirements <ul><li>PPSP tracker protocol MUST be able to carry peer list information, such that each peer can get the list of peers which could provide the content. </li></ul><ul><li>PPSP tracker protocol MUST be able to carry swarm ID (e.g. channel ID, streaming file ID). </li></ul>
  4. 4. PPSP Tracker Protocol Requirements <ul><li>PPSP tracker protocol MAY carry content availability of the peers. </li></ul><ul><li>- In some cases tracker may maintain the information of which pieces of content reside in which peers, such that the tracker can assign the appropriate peers for the requesting peer. </li></ul><ul><li>PPSP tracker protocol MAY carry streaming status of the peers. </li></ul><ul><li>- Streaming status of the peer include online time, link type/status, peer capability, device types, etc. Therefore, the tracker is able to select better candidate peers based on the streaming status of the peers. </li></ul><ul><li>PPSP tracker protocol MAY be able to carry the service status of the tracker, e.g. work load, capacity, etc. </li></ul>
  5. 5. PPSP Peer Protocol Requirements <ul><li>PPSP peer protocol MUST be able to carry content availability of the peers. </li></ul><ul><li>- In order to share content, peers must be able to tell each other which pieces of content reside in which peers. </li></ul><ul><li>PPSP peer protocol May exchange additional peer list between peers. </li></ul><ul><li>- Beside the peer list obtained from the tracker, peer may need additional peers to connect with. Therefore, peer may communicate with the peers in the current peer list to obtain additional peer lists. </li></ul><ul><li>PPSP peer protocol May carry streaming status of the peers. </li></ul><ul><li>- With this information, a peer can select more appropriate peers for content sharing based on some content sharing strategies and/or application requirements. </li></ul>
  6. 6. PPSP Error Handling and Overload Protection Requirements <ul><li>A tracker, when is operating close to its capacity limit, MUST be able to inform the peers about its overload status, and reject the following PPSP messages from the peers or redirect the following PPSP message to other trackers. </li></ul>
  7. 7. PPSP Security Considerations <ul><li>PPSP must be able to authenticate / authorize users for access certain media in the P2P streaming system. </li></ul><ul><li>PPSP must have mechanisms to limit potential damage caused by malfunctioning and badly behaving peers in the P2P streaming system. </li></ul><ul><li>PPSP should minimize the dependency on centralized servers. </li></ul><ul><li>Existing security mechanisms should be re-used as much as possible in PPSP, to avoid developing new security mechanisms. </li></ul><ul><li>More items available in the draft and to be discussed in the future. </li></ul>
  8. 8. Questions & Comments

×