1 / 7

draft-gu-ppsp-peer-protocol-01

draft-gu-ppsp-peer-protocol-01. Y. Gu, D. A. Bryan IETF-79, Beijing China, November 12, 2010. Updates…. We have slightly changed our thoughts since the draft Do not want to have RELOAD as only way to establish connections between peers

rhea-oneil
Télécharger la présentation

draft-gu-ppsp-peer-protocol-01

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. draft-gu-ppsp-peer-protocol-01 Y. Gu, D. A. Bryan IETF-79, Beijing China, November 12, 2010

  2. Updates… • We have slightly changed our thoughts since the draft • Do not want to have RELOAD as only way to establish connections between peers • Instead, allow different mechanisms to perform the establishment of connections • Peer Protocol itself becomes just about the messages exchanged via the gossip protocol

  3. Proposed Architecture Tracker IP and PeerID Tracker Protocol NAT Traversal / Connection Peer Peer Peer Protocol Peer

  4. Overview of Proposal • Early work to promote conversation! • Current version (-01) does not yet define specific messages • Defines where existing protocols will be reused, and where new work is required • Presents a list of requirements for the new protocol • Will be turned over to the requirements editors once we start the actual protocol definition

  5. Overview of Proposal (continued) • Protocol for exchanging information between peers, supporting mechanisms for the following: • Find peers participating in a swarm or channel • (This is in addition to peers returned by tracker) • Exchange information with other peers • Chunk lists (offline case) • Location/stream offset (live stream case) • Works with existing protocols to enable • Locating and establishing connections between peers • Negotiation of connection to exchange data • Peers then exchange data. The transmission protocol is also existing protocol, not newly defined or specified by PPSP group.

  6. Negotiating Transfer • Provide mechanism to negotiate actual connection • Allows flexibility for streaming (negotiate RTP or similar) or chunk transmission (perhaps HTTP). No fixed transfer protocol. • Several options: • Reuse SIP offer/answer mechanism (this is rather heavy) • Something like the Advertisement/Proposal model for session description (draft-peterson-sipcore-advprop-00) • Use messages in the peer protocol w/SDP to negotiate connections

  7. Open Issues / Questions • Similarity in query/response format for peer lists between tracker and peer protocols? • Allow both mechanisms? • Same format? • What search capabilities do we want for finding peers? • Can we search for dynamic properties, or only static? • Search on tracker or only peers? • Do we define bitmap format in protocol, or application/deployment specific? • Currently prefer deployment specific… • Again, the thorny question of encoding…XML/text or binary • We propose same encoding for peer and tracker protocol

More Related