Problem Statement and Requirements of the Peer-to-Peer Streaming Protocol (PPSP)
Draft of message to be sent after approval:
From: The IESG <firstname.lastname@example.org> To: IETF-Announce <email@example.com> Cc: RFC Editor <firstname.lastname@example.org>, ppsp mailing list <email@example.com>, ppsp chair <firstname.lastname@example.org> Subject: Document Action: 'Problem Statement and Requirements of Peer-to-Peer Streaming Protocol (PPSP)' to Informational RFC (draft-ietf-ppsp-problem-statement-15.txt) The IESG has approved the following document: - 'Problem Statement and Requirements of Peer-to-Peer Streaming Protocol (PPSP)' (draft-ietf-ppsp-problem-statement-15.txt) as Informational RFC This document is the product of the Peer to Peer Streaming Protocol Working Group. The IESG contact persons are Martin Stiemerling and Spencer Dawkins. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-ppsp-problem-statement/
Technical Summary Peer-to-Peer (P2P for short) streaming systems show more and more popularity in current Internet with proprietary protocols. This document identifies problems of the proprietary protocols, proposes the development of Peer to Peer Streaming Protocol (PPSP) including the tracker and peer protocol, and discusses the scope, requirements and use cases of PPSP. Working Group Summary There is strong consensus on the WG process in this document. Document Quality The proposed protocols are being developed and there are already at least three implementations of the PPSP tracker and peer protocol. And there are some operators planning to implement the spec after they are finished. The draft describes the requirements and problem statements for the standardization of Peer and Tracker streaming protocols that are being specified in separate documents. The Problem Statement draft is not a protocol specification so the question about implementation does not apply. However, there are already both Peer and Trackers streaming protocol implementations. Personnel Stefano Previdi (email@example.com) is the document shepherd, and Martin Stiemerling (firstname.lastname@example.org) is the responsible AD.