Re: [ppsp] PPSP Re-charter discussion

zhangyunfei <zhangyunfei@chinamobile.com> Wed, 22 February 2012 03:16 UTC

Return-Path: <zhangyunfei@chinamobile.com>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CF92421E8038 for <ppsp@ietfa.amsl.com>; Tue, 21 Feb 2012 19:16:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.277
X-Spam-Level:
X-Spam-Status: No, score=-97.277 tagged_above=-999 required=5 tests=[AWL=1.346, BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RELAY_IS_221=2.222, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k7MBD8cR6cL8 for <ppsp@ietfa.amsl.com>; Tue, 21 Feb 2012 19:16:21 -0800 (PST)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 1303621F8912 for <ppsp@ietf.org>; Tue, 21 Feb 2012 19:16:20 -0800 (PST)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id BBCB5E504; Wed, 22 Feb 2012 11:16:18 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id 94229E4D8; Wed, 22 Feb 2012 11:16:18 +0800 (CST)
Received: from pc917 ([10.1.5.3]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2012022211153641-8072 ; Wed, 22 Feb 2012 11:15:36 +0800
Date: Wed, 22 Feb 2012 11:15:28 +0800
From: zhangyunfei <zhangyunfei@chinamobile.com>
To: ZongNing <zongning@huawei.com>, ppsp <ppsp@ietf.org>
References: <2012021923584463860669@chinamobile.com>, <B0D29E0424F2DE47A0B36779EC66677914919F4B@szxeml504-mbs.china.huawei.com>
X-Priority: 3 (Normal)
X-Mailer: Foxmail 7.0.1.85[cn]
Mime-Version: 1.0
Message-ID: <2012022211100575063629@chinamobile.com>
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-02-22 11:16:16, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-02-22 11:16:18
Content-Type: multipart/alternative; boundary="----=_001_NextPart411514585705_=----"
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-18724.004
X-TM-AS-Result: No--28.365-7.0-31-10
X-imss-scan-details: No--28.365-7.0-31-10;No--28.365-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No;No
Subject: Re: [ppsp] PPSP Re-charter discussion
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: zhangyunfei <zhangyunfei@chinamobile.com>
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2012 03:16:22 -0000

Hi Ning,
    Please see inline.

BR
Yunfei




zhangyunfei

From: ZongNing
Date: 2012-02-21 16:33
To: zhangyunfei; ppsp
Subject: RE: [ppsp] PPSP Re-charter discussion
Hi,
 
Regarding “ Inclusion of media transport mechanism into PPSP WG task”, because we haven’t got consensus on mandatory data transport mechanism yet, how do you intend to progress this item?
I can see two ways, thus different milestone layout:
1)       still selecting at least one mandatory data transport mechanism and document it in peer protocol draft.
2)       produce a list of best practice data transport mechanisms for PPSP usage and document these in separate drafts (to peer protocol draft).
[Yunfei] I would prefer the second option, which makes every part of PPSP protocol suite clear. But we may need some discussion in the PPSP usage document to make the signaling and media transfer most efficient in the combined usage.
 
BR,
Ning Zong
From: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] On Behalf Of zhangyunfei
Sent: Sunday, February 19, 2012 11:59 PM
To: ppsp
Subject: [ppsp] PPSP Re-charter discussion
 
Hi all,
   Based on the discussions in Taipei meeting, Martin and I have drafted the following re-charter text with the track change mode. The basic changes include:
1) Inclusion of media transport mechanism into PPSP WG task.
2) Signaling protocol and media protocol candidates description change;
3) Document merger, submission deadline as well as new WG draft update in Goals and milestones.
    Please review it and post your comments in the mailing list. We wish to get consensus in the mailing list before submitting to talk with the AD.
P.S.: We are exploring the possibility of having an interim meeting in the early of March, before next IETF. We'll start the poll of the time soon if we get positive feedback on the progress from the proposed peer and tracker protocol authors.
 
BR
Yunfei
   
    
 
Description of Working Group
The Peer-to-Peer Streaming Protocol (PPSP) working group develops two
signaling and control protocols for a peer-to-peer (P2P) streaming
system for transmitting live and time-shifted media content with near
real-time delivery requirements.
Two kinds of nodes exist in the targeted P2P streaming system, i.e.,
"peers" and "trackers". Peers are nodes that are actively sending and
receiving streamed media content, and include both statically connected
hosts as well as mobile devices with connectivity and IP addresses that
change over time, as well as changed link characteristics for mobile nodes.
The set of peers that are participating in a streaming
session will dynamically change over time. Trackers are well-known nodes
with stable connectivity that maintain meta information about the
streamed content and the dynamic peer set involved in the streaming. Trackers can be organized in
centralized or distributed ways.
The PPSP WG designs a protocol for signaling and control between
trackers and peers (the PPSP "tracker protocol") and a signaling and
control protocol for communication among the peers (the PPSP "peer
protocol"). The two protocols enable peers to receive streaming data
within the time constraints required by specific content items. The
tracker protocol handles the initial and periodic exchange of meta
information between trackers and peers, such as peer lists and content
information. The peer protocol controls the advertising and exchange of
media data availability between the peers, as well as the exchange of streaming media.
It is envisioned that the tracker protocol will be modeled as a
request/response protocol between peers and trackers, and will carry
information needed for the selection of peers suitable for real-time
streaming. The peer protocol is envisioned to be modeled as a
gossip-like protocol with periodic, pairwise exchanges of neighbor and
media chunk availability information. Both protocols will be carried
over TCP (or UDP, when delivery requirements cannot be met by TCP),
likely in combination with ICE for NAT traversal support. Perfect
privacy protection is a good feature to have but not a mandatory
requirement for the peer and tracker protocols. The WG will consider to
use existing protocols as design base for the tracker and peer
protocols.
Developing mechanisms for searching trackers that contain a specific
media item is out of the scope of this WG. Additionally, the WG will
work under the assumption that trackers are logically centralized
entities (e.g., a single server or a server farm performing DNS-based
local balancing). However, as far as it is possible, the WG will not
make design decisions that could preclude the use of distributed
trackers in the future (e.g., DHT-based trackers).
A peer looking for a particular media stream media chunkSuch a media stream is transported in so-called chunks, where a chunk contains the pieces of the media.
Obtaining the media chunk from the remote peer will involve some
type of signaling exchange, i.e., the tracker and peer protocols to
locate a remote peer (or peers) plus the actual media transfer of the chunks. The first, media streammedia
chunk. 
task for this WG will be to decide which signaling and media transfer
protocols will be usedThe WG will work on the peer and tracker protocol and . The WG will consider existing protocols and, if
needed, identify potential extensions to these protocols. The WG will
consider the interactions between these protocols and the peer protocol
(e.g., avoiding duplicate NAT traversal procedures). An Eexamples of a
signaling protocols to be considered are isSIP, RTSP, and HTTP. Examples
of media transfer protocols mechanismsto be considered are UDP, andTCPRTP and HTTP.
and possible extension on top of them.
PPSP is not chartered to work on media transmission protocols, media
encoding techniques or other components of a P2P streaming system such
as playout control or, scheduling and control, etc.
PPSP will explore the relationship to DECADE and ALTO working groups.
The work items of the PPSP WG are:
(1) A "problem statement" and "requirements" document. This document that gives an overview of the
proposed P2P streaming system, motivates the desire for
standardized protocols, defines the envisioned scope of those
standardized components and discusses common terminologies and
concepts. It also that details the specific functional,
operational and performance requirements of the two PPSP
protocols.
(2) A "requirements" document that details the specific functional,
operational and performance requirements of the two PPSP
protocols.
(3) An "architectural survey" document that summarizes current P2P
streaming architectures, in particular tracker-based P2P
streaming systems, and highlights best current practices, as input to the design of the peer and tracker protocols..
(4) A detailed specification of the PPSP peer protocol.
(5) A detailed specification of the PPSP tracker protocol.
(6) A detailed specification of the PPSP media transport mechanism.
(7) A "usage guide" that describes how the thewo PPSP protocols and
existing IETF protocols, such as P2PSIP,DECADEor ALTO, can be combined
to create a deployable operational P2P streaming system. This
document may also discuss variants of such a system that, for
example, use layered media encoding and related media chunk
descriptions in the peer protocol for more robust streaming.
(8) A implementation and operational experience guide document that describes the performance of the proposed protocols and usable systems.
The work items of the PPSP WG interacts with the work performed in other
IETF WGs, including P2PSIP, SIPCORE, AVT, ALTO, LEDBAT, and DECADE and MMUSIC.
Whenever extensions or modification to the protocols developed in other
WGs are deemed necessary, PPSP shall communicate and discuss the
requirements for such extensions with the relevant WGs. PPSP is not
chartered to design and specify such changes.
Goals and Milestones
Dec 20110Submit problem statement to IESG as Informational 
Apr 2011 2012Submit problem statement and requirementsarchitectural survey documentto IESG as Informational 
Apr 2011 2012Submit architectural survey requirements document to IESG as Informational 
Aug Sep20121 Jan 2013Submit PPSP tracker peer protocol to IESG as Proposed Standard 
Aug Dec20121 Jan 2013Submit PPSP tracker peer protocol to IESG as Proposed Standard 
Dec2011 Submit usage guide to IESG to IESG as Informational 

Dec 2012Jan 2013    Submit PPSP media transport mechanism to IESG as Proposed Standard
 
Apr 2013    Submit usage guide to IESG as Informational
 
Apr 2013    Submit field test to IESG as Informational
 
 



zhangyunfei