1 / 3

P2P Protocol Requirements, part 2

P2P Protocol Requirements, part 2. Henning Schulzrinne Colulmbia University. Data. Apply to client-peer and peer-peer Size limitations? protocol vs. policy likely either ~500 bytes or “infinity” Data expiration “soft state” assumed refresh should not require re-writing data

maximilian
Download Presentation

P2P Protocol Requirements, part 2

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 Protocol Requirements, part 2 Henning Schulzrinne Colulmbia University

  2. Data • Apply to client-peer and peer-peer • Size limitations? • protocol vs. policy • likely either ~500 bytes or “infinity” • Data expiration • “soft state” assumed • refresh should not require re-writing data • but can data creator modify expiration time? • allow DHT instance policy?

  3. Meta data • What data is stored with the “real” data? • Examples: • content type • creation time • last updated/refreshed • ownership • access permissions

More Related