1 / 6

PPSP Base Tracker Protocol

This presentation discusses the Base Tracker Protocol that facilitates operation in peer-to-peer streaming services. It employs two key messages: a CONNECT.Request for registering and managing actions on content swarms and a STAT-REPORT.Request to periodically update the Tracker with status and statistics. The presentation also addresses open issues from IETF 84 regarding IP address handling and encoding concerns. Recommendations for further protocol development include adopting the draft-cruz-ppsp-base-tracker-protocol as a working group item.

suzuki
Download Presentation

PPSP Base Tracker Protocol

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. PPSP Base Tracker Protocol draft-cruz-ppsp-base-tracker-protocol PPSP WG IETF 84 Vancouver Yingjie Gu (presenter) Rui Cruz, Mário Nunes, Jinwei Xia, João Taveira, Deng Lingli

  2. Recap • The Base Tracker Protocol uses two messages for the operation: • a CONNECT Request message to “register” and/or request actions on swarm(s) of streaming contents; • a STAT-REPORT Request messageto periodically inform the Tracker about its status and supply statistic information; • To terminate all its activity in the P2P streaming service the Peer may: • Send a CONNECT Requesting action to LEAVE swarm(s); • Stop sending periodic STAT_REPORT;

  3. Open issues from IETF 84 • IP Address in TP request? • Encoding?

  4. Revision record • IP address is optional in request message from Peer to Tracker, and mandatory in response Peer list from Tracker to Peer. • Encoding is irrelevant to protocol design. Move section 7.1 to Appendix.

  5. Detail consideration • IP address issue: If a peer has public IP addresses, the Tracker can get it from the packet header. If a peer is behind NAT, in most case, providing private IP address in request message won’t help.

  6. Next Step • We ask the WG to adopt draft-cruz-ppsp-base-tracker-protocol as a WG item.

More Related