[ppsp] 答复: Draft-ietf-ppsp-req-01
Ning Zong <zongning@huawei.com> Tue, 08 March 2011 01:38 UTC
Return-Path: <zongning@huawei.com>
X-Original-To: ppsp@core3.amsl.com
Delivered-To: ppsp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5ABC028C0FB for <ppsp@core3.amsl.com>; Mon, 7 Mar 2011 17:38:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -95.904
X-Spam-Level:
X-Spam-Status: No, score=-95.904 tagged_above=-999 required=5 tests=[AWL=-2.705, BAYES_00=-2.599, CHARSET_FARAWAY_HEADER=3.2, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u2Bk6MhKEIXM for <ppsp@core3.amsl.com>; Mon, 7 Mar 2011 17:38:54 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id AFE743A69E9 for <ppsp@ietf.org>; Mon, 7 Mar 2011 17:38:53 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LHP00ETDTYLWV@szxga05-in.huawei.com> for ppsp@ietf.org; Tue, 08 Mar 2011 09:39:57 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LHP00GX7TYKVY@szxga05-in.huawei.com> for ppsp@ietf.org; Tue, 08 Mar 2011 09:39:56 +0800 (CST)
Received: from z63316a ([10.138.41.31]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LHP00ICMTYF74@szxml04-in.huawei.com> for ppsp@ietf.org; Tue, 08 Mar 2011 09:39:56 +0800 (CST)
Date: Tue, 08 Mar 2011 09:39:51 +0800
From: Ning Zong <zongning@huawei.com>
In-reply-to: <C58FFCAAA14F454A85AFB7C1C2F862C4019982FC@DEMUEXC013.nsn-intra.net>
To: "'Schmidt, Christian 1. (NSN - DE/Munich)'" <christian.1.schmidt@nsn.com>, 'ext zhangyunfei' <zhangyunfei@chinamobile.com>, ppsp@ietf.org
Message-id: <009301cbdd31$b81fd120$285f7360$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_ltbVoqffXs+uv35j4biunA)"
Content-language: zh-cn
Thread-index: AcvMtEPEmNRn+yPTQ+ClbxGwB3Ot6QHZwv/QAAFhUqAAGE8+0AIKw4DAACDdMFA=
References: <201101180955204217745@chinamobile.com> <C58FFCAAA14F454A85AFB7C1C2F862C40168CE4E@DEMUEXC013.nsn-intra.net> <201101181419275009728@chinamobile.com> <C58FFCAAA14F454A85AFB7C1C2F862C401730366@DEMUEXC013.nsn-intra.net> <201101311644379687165@chinamobile.com> <C58FFCAAA14F454A85AFB7C1C2F862C401799919@DEMUEXC013.nsn-intra.net> <201102151000498905239@chinamobile.com> <C58FFCAAA14F454A85AFB7C1C2F862C401900150@DEMUEXC013.nsn-intra.net> <007801cbd482$d39d9cf0$7ad8d6d0$@com> <C58FFCAAA14F454A85AFB7C1C2F862C4019982FC@DEMUEXC013.nsn-intra.net>
Subject: [ppsp] 答复: Draft-ietf-ppsp-req-01
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Tue, 08 Mar 2011 01:38:55 -0000
Hi, Schmidt, I agree that these requirements of QoS are important to P2P streaming system. However, I still don’t see how these QoS requirements impact the design of Tracker & Peer Protocol, bearing in mind that our scope is not developing a P2P streaming system. Instead, IMO, these requirements could be addressed by some video transmission protocols such as those developed in AVT WG. Could you give some examples on how these QoS issue will apply to Tracker & Peer Protocol? Thanks. BR, Ning Zong 发件人: Schmidt, Christian 1. (NSN - DE/Munich) [mailto:christian.1.schmidt@nsn.com] 发送时间: 2011年3月7日 18:06 收件人: ext Ning Zong; ext zhangyunfei; ppsp@ietf.org 主题: RE: [ppsp] Draft-ietf-ppsp-req-01 Hi Ning Zong, I do not agree, that basic QoS issues should not be a normative requirement for PPSP system. I think they are essential to this services. what about the proposal to include a section Quality of Service Requirements? QoS.REQ-1: “Setup time to receive a new streaming channel or to switch between channels should be reasonable small. This time mainly depends on the size of the receiving buffer.” QoS.REQ-2: “End to end delay (time between content generation, e.g. camera and content consumption, e.g. user side monitor) will become critical in case of live streaming. Especially In provisioning of sports events, end to end delay of 1 minute and more seems to be not acceptable.” QoS.REQ-3: “The user should receive an error free copy of the original streaming. This can be done with addition of redundancy and the usage of packet retransmission. But the additional delay has to be taken into account.” What do you think about? BR Christian From: ext Ning Zong [mailto:zongning@huawei.com] Sent: Friday, February 25, 2011 1:28 AM To: Schmidt, Christian 1. (NSN - DE/Munich); 'ext zhangyunfei'; ppsp@ietf.org Subject: 答复: [ppsp] Draft-ietf-ppsp-req-01 Hi, Schmidt, Your suggestion is good, although I think this new text could be in explanatory text rather than in the formal requirement body. BTW, I have post a new revision -02 and forward the message to the list, but it seems that it doesn’t come out. So I attached the link to the new version as below http://tools.ietf.org/html/draft-ietf-ppsp-reqs-02 The main differences between -02 and -01 can be found in: http://tools.ietf.org/rfcdiff?url2=draft-ietf-ppsp-reqs-02.txt BR, Ning Zong 发件人: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] 代表 Schmidt, Christian 1. (NSN - DE/Munich) 发送时间: 2011年2月24日 20:56 收件人: ext zhangyunfei; ppsp@ietf.org 主题: [ppsp] Draft-ietf-ppsp-req-01 Hi Yunfei, a proposal related to PPSP.REQ-7: “PPSP.REQ-7: The Tracker Protocol and Peer Protocol SHOULD enable peers to receive streaming data within the time constraints required by specific content items.” CS: We should be a little bit more specific here. I think, that delay will be the most critical QoS issues, especially for p2p live streaming. We should add: Proposal: “PPSP.REQ-7: The Tracker Protocol and Peer Protocol SHOULD enable peers to receive streaming data within the time constraints required by specific content items. End to end delay will become critical in case of live streaming. Especially In provisioning of sports events, end to end delay of 1 minute and more seems to be not acceptable.” What do you think about? Best Regards Christian
- [ppsp] Review: draft-ietf-pp2p-problem-statement-… Schmidt, Christian 1. (NSN - DE/Munich)
- Re: [ppsp] Review: draft-ietf-pp2p-problem-statem… zhangyunfei
- Re: [ppsp] Review: draft-ietf-pp2p-problem-statem… Schmidt, Christian 1. (NSN - DE/Munich)
- Re: [ppsp] Review: draft-ietf-pp2p-problem-statem… zhangyunfei
- [ppsp] Review: draft-ietf-pp2p-problem-statement-… Schmidt, Christian 1. (NSN - DE/Munich)
- [ppsp] Draft-ietf-ppsp-req-01 Schmidt, Christian 1. (NSN - DE/Munich)
- [ppsp] 答复: Draft-ietf-ppsp-req-01 Ning Zong
- Re: [ppsp] Review: draft-ietf-pp2p-problem-statem… zhangyunfei
- Re: [ppsp] Review: draft-ietf-pp2p-problem-statem… Schmidt, Christian 1. (NSN - DE/Munich)
- [ppsp] (no subject) zhangyunfei
- [ppsp] (no subject) zhangyunfei
- Re: [ppsp] Draft-ietf-ppsp-req-01 Schmidt, Christian 1. (NSN - DE/Munich)
- [ppsp] Review: draft-ietf-pp2p-problem-statement-… Schmidt, Christian 1. (NSN - DE/Munich)
- [ppsp] (no subject) zhangyunfei
- [ppsp] 答复: Draft-ietf-ppsp-req-01 Ning Zong
- Re: [ppsp] Draft-ietf-ppsp-req-01 Schmidt, Christian 1. (NSN - DE/Munich)
- [ppsp] 答复: Draft-ietf-ppsp-req-01 Ning Zong