From lars.eggert@nokia.com Mon Oct 12 19:49:46 2009 Return-Path: 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 0DF463A694E for ; Mon, 12 Oct 2009 19:49:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599] 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 XaAgMhsX6ROi for ; Mon, 12 Oct 2009 19:49:45 -0700 (PDT) Received: from mail.fit.nokia.com (mail.fit.nokia.com [195.148.124.195]) by core3.amsl.com (Postfix) with ESMTP id 1A7EF3A69C8 for ; Mon, 12 Oct 2009 19:49:44 -0700 (PDT) Received: from [192.168.10.31] (p2139-ipbf29marunouchi.tokyo.ocn.ne.jp [219.162.45.139]) (authenticated bits=0) by mail.fit.nokia.com (8.14.3/8.14.3) with ESMTP id n9D2nDu3069673 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for ; Tue, 13 Oct 2009 05:49:36 +0300 (EEST) (envelope-from lars.eggert@nokia.com) From: Lars Eggert Content-Type: multipart/signed; boundary=Apple-Mail-33-69585356; protocol="application/pkcs7-signature"; micalg=sha1 Date: Tue, 13 Oct 2009 11:49:35 +0900 Message-Id: To: ppsp@ietf.org Mime-Version: 1.0 (Apple Message framework v1076) X-Mailer: Apple Mail (2.1076) X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.3 (mail.fit.nokia.com [212.213.221.39]); Tue, 13 Oct 2009 05:49:39 +0300 (EEST) Subject: [ppsp] chairs for PPSP X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 02:49:46 -0000 --Apple-Mail-33-69585356 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; format=flowed Hi, FYI, the chairs for the PPSP BOF will be: Gonzalo Camarillo Zhang Yunfei Lars --Apple-Mail-33-69585356 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIGbDCCAyUw ggKOoAMCAQICEAdjk36sXKbnVn15S0/qUp0wDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDYxNTExMjYxNFoXDTEwMDYxNTExMjYx NFowXDEPMA0GA1UEBBMGRWdnZXJ0MQ0wCwYDVQQqEwRMYXJzMRQwEgYDVQQDEwtMYXJzIEVnZ2Vy dDEkMCIGCSqGSIb3DQEJARYVbGFycy5lZ2dlcnRAbm9raWEuY29tMIIBIjANBgkqhkiG9w0BAQEF AAOCAQ8AMIIBCgKCAQEA7mR8A+Pn0/FsUkMX6Pyjw+FL3IFcJk8GaKV5VJ40TMI0Wh8oq20cqA9X uqnVDW9WztKwH+o+msJenLwWpprbpJm4TImYGbnUJxYyN8gb81aiX1Bw2xCpJ5z3H2+8DsReJLuY Rdl4bVvaIxLIL4odmfsRwzPyNkOK8LRtfl6OPcaDOlFWzbikULfIVGGu7BqK4lxQSpYwwpZkOMOB 6nnBSfUOtBEmqO+qZG/nL/JxWFV5vxQgg4XHbsMMTxFf6+ji18BD09BUIfDLTuJoCzFmQhrM9vLT VuRhHWSL20LoafGjXv6mPt3i9IGJHpVb2dMQUgOgRyWHTKiUJVU/rUTdWwIDAQABo14wXDAqBgUr ZQEEAQQhMB8CAQAwGjAYAgEEBBNMMnVNeWZmQk5VYk5KSmNkWjJzMCAGA1UdEQQZMBeBFWxhcnMu ZWdnZXJ0QG5va2lhLmNvbTAMBgNVHRMBAf8EAjAAMA0GCSqGSIb3DQEBBQUAA4GBADUx+67n98wt I1vydB90HeSZP4Y64VCxxb0NxGGFvfc2+JdVKeHJ/xT+l+ygYKsWNwJJprkPi4WZ5G0crkq4VK1H 5drEJIztpSPVfWI05vPidaaGuuuCR+6MvJMtOTEYEvc/6eovBnkrzRf9x5x5EyuJXAWTeuBADg80 QI3vQ1tZMIIDPzCCAqigAwIBAgIBDTANBgkqhkiG9w0BAQUFADCB0TELMAkGA1UEBhMCWkExFTAT BgNVBAgTDFdlc3Rlcm4gQ2FwZTESMBAGA1UEBxMJQ2FwZSBUb3duMRowGAYDVQQKExFUaGF3dGUg Q29uc3VsdGluZzEoMCYGA1UECxMfQ2VydGlmaWNhdGlvbiBTZXJ2aWNlcyBEaXZpc2lvbjEkMCIG A1UEAxMbVGhhd3RlIFBlcnNvbmFsIEZyZWVtYWlsIENBMSswKQYJKoZIhvcNAQkBFhxwZXJzb25h bC1mcmVlbWFpbEB0aGF3dGUuY29tMB4XDTAzMDcxNzAwMDAwMFoXDTEzMDcxNjIzNTk1OVowYjEL MAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNV BAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMIGfMA0GCSqGSIb3DQEBAQUA A4GNADCBiQKBgQDEpjxVc1X7TrnKmVoeaMB1BHCd3+n/ox7svc31W/Iadr1/DDph8r9RzgHU5VAK MNcCY1osiRVwjt3J8CuFWqo/cVbLrzwLB+fxH5E2JCoTzyvV84J3PQO+K/67GD4Hv0CAAmTXp6a7 n2XRxSpUhQ9IBH+nttE8YQRAHmQZcmC3+wIDAQABo4GUMIGRMBIGA1UdEwEB/wQIMAYBAf8CAQAw QwYDVR0fBDwwOjA4oDagNIYyaHR0cDovL2NybC50aGF3dGUuY29tL1RoYXd0ZVBlcnNvbmFsRnJl ZW1haWxDQS5jcmwwCwYDVR0PBAQDAgEGMCkGA1UdEQQiMCCkHjAcMRowGAYDVQQDExFQcml2YXRl TGFiZWwyLTEzODANBgkqhkiG9w0BAQUFAAOBgQBIjNFQg+oLLswNo2asZw9/r6y+whehQ5aUnX9M Ibj4Nh+qLZ82L8D0HFAgk3A8/a3hYWLD2ToZfoSxmRsAxRoLgnSeJVCUYsfbJ3FXJY3dqZw5jowg T2Vfldr394fWxghOrvbqNOUQGls1TXfjViF4gtwhGTXeJLHTHUb/XV9lTzGCAxAwggMMAgEBMHYw YjELMAkGA1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAq BgNVBAMTI1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAHY5N+rFym51Z9eUtP 6lKdMAkGBSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkF MQ8XDTA5MTAxMzAyNDkzNlowIwYJKoZIhvcNAQkEMRYEFC3LaAHVHTOLtA6eTX4nkYZKTXOUMIGF BgkrBgEEAYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGlu ZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBD QQIQB2OTfqxcpudWfXlLT+pSnTCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUw IwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVy c29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQB2OTfqxcpudWfXlLT+pSnTANBgkqhkiG9w0BAQEF AASCAQDVlHHT9owgAn0Ff4NQfF9OwDsPL7+M3SyxKV0k7/+LaFbwKYkG/+ypLmpjI5yaJrFsM1gJ KRwUs9TlnQhwFEbB7nWLgbCgkJ+jpaEKp0YKjrMh2pKbrOVhnhKVg7GDcB2QjNZa61LOBd0Lt+8i fKzh8jCUT326mvwZ2+qSs2sgYg9sARJB6skkTmPQ7E0DKXfxC0pspY0d+S8kYYzqtGYlvsOsHmiR d5vmJGhbViQk7nEkM9uET427uELb5v5ocBYrqM1nQtRnktHb4XWAx6kIVrms7CzsYzRMQrbE5LtQ gvWhFsxreAXfDRhQ4IHIpZcLlyXhs+pOqwL8+hreIx40AAAAAAAA --Apple-Mail-33-69585356-- From huyan@research.nec.com.cn Sun Oct 18 20:05:36 2009 Return-Path: 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 BD9393A6844 for ; Sun, 18 Oct 2009 20:05:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.005 X-Spam-Level: ** X-Spam-Status: No, score=2.005 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, TRACKER_ID=2.003] 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 B3rN9PJGhLGS for ; Sun, 18 Oct 2009 20:05:36 -0700 (PDT) Received: from spam.nec.com.cn (spam.nec.com.cn [211.100.22.6]) by core3.amsl.com (Postfix) with ESMTP id ADE923A6861 for ; Sun, 18 Oct 2009 20:05:35 -0700 (PDT) X-ASG-Debug-ID: 1255921527-078e007b0000-ZjXuBC X-Barracuda-URL: http://172.28.88.136:8000/cgi-bin/mark.cgi Received: from internal-mail.nec.com.cn (localhost [127.0.0.1]) by spam.nec.com.cn (Spam Firewall) with ESMTP id 1DE03178D759 for ; Mon, 19 Oct 2009 11:05:27 +0800 (CST) Received: from internal-mail.nec.com.cn ([172.28.88.254]) by spam.nec.com.cn with ESMTP id tnKwUVGnWASbFLpF for ; Mon, 19 Oct 2009 11:05:27 +0800 (CST) Received: from smtp.x263.net (localhost.localdomain [127.0.0.1]) by internal-mail.nec.com.cn (Postfix) with ESMTP id 1694413F4F for ; Mon, 19 Oct 2009 11:05:20 +0800 (CST) Received: from NECCNQH075010 (localhost.localdomain [127.0.0.1]) by smtp.x263.net (Postfix) with SMTP id 6A6902F4580 for ; Mon, 19 Oct 2009 11:05:23 +0800 (CST) Message-ID: <97ECA643466B44C4AE8D8F19752F89A2@idm.gad.nec.com.cn> From: "Hu Yan" To: X-ASG-Orig-Subj: Tracker-DHT-performance-comparision Date: Mon, 19 Oct 2009 11:05:24 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0067_01CA50AC.0E6D6DD0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.5843 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5579 X-Barracuda-Connect: UNKNOWN[172.28.88.254] X-Barracuda-Start-Time: 1255921527 X-Barracuda-Virus-Scanned: by Barracuda Spam Firewall at nec.com.cn Subject: [ppsp] Tracker-DHT-performance-comparision X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2009 03:08:54 -0000 This is a multi-part message in MIME format. ------=_NextPart_000_0067_01CA50AC.0E6D6DD0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Dear All,=20 A new version of I-D, = draft-hu-ppsp-tracker-dht-performance-comparison-00.txt has been = submitted by Yan Hu and posted to the IETF repository. Please review it and any comments and suggestions are highly = appreciated.=20 Best Regards, Hu Yan -------------------------------------------------------------------------= --------------------------------------------------------------- https://www.ietf.org/id/draft-hu-ppsp-tracker-dht-performance-comparison-= 00.txt Filename: draft-hu-ppsp-tracker-dht-performance-comparison Revision: 00 Title: Tracker VS. DHT Performance Comparison for P2P Streaming Creation_date: 2009-10-18 WG ID: Independent Submission Number_of_pages: 12 Abstract: The draft makes performance analysis in two kinds of resource exchange and discovery methods, tracker based and DHT based architectures in P2P streaming. Our analysis shows that centralized tracker solution for resource discovery (and chunk lookup) has much shorter response time than highly distributed DHT approach. ------=_NextPart_000_0067_01CA50AC.0E6D6DD0 Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable
Dear All,
 
A new version of I-D,=20 draft-hu-ppsp-tracker-dht-performance-comparison-00.txt has been = submitted by=20 Yan Hu and posted to the IETF repository.
Please review it and any comments and suggestions are highly = appreciated.=20
Best Regards,
Hu Yan
 
----------------------------------------------------------------= ------------------------------------------------------------------------<= /FONT>
https://www.ietf.org/id/draft-hu-ppsp-tracker-dht-performance-co= mparison-00.txt
 
Filename: = draft-hu-ppsp-tracker-dht-performance-comparison
Revision:=20 00
Title: Tracker VS. DHT Performance Comparison for P2P=20 Streaming
Creation_date: 2009-10-18
WG ID: Independent=20 Submission
Number_of_pages: 12

Abstract:
The draft makes=20 performance analysis in two kinds of resource
exchange and discovery = methods,=20 tracker based and DHT based
architectures in P2P streaming. Our = analysis=20 shows that centralized
tracker solution for resource discovery (and = chunk=20 lookup) has much
shorter response time than highly distributed DHT=20 approach.
------=_NextPart_000_0067_01CA50AC.0E6D6DD0-- From chenyishuai@gmail.com Sun Oct 18 22:20:19 2009 Return-Path: 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 09B463A67F8 for ; Sun, 18 Oct 2009 22:20:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] 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 QDm0mOn-pG1b for ; Sun, 18 Oct 2009 22:20:11 -0700 (PDT) Received: from mail-pz0-f198.google.com (mail-pz0-f198.google.com [209.85.222.198]) by core3.amsl.com (Postfix) with ESMTP id 5EF993A67AD for ; Sun, 18 Oct 2009 22:20:11 -0700 (PDT) Received: by pzk36 with SMTP id 36so3175844pzk.5 for ; Sun, 18 Oct 2009 22:20:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:from:date:message-id :subject:to:cc:content-type; bh=DZbn4xbmi1C9AbidMWm+orHu7Ep3BE9bUvzIx5Kki7g=; b=g9IyPh2Y3AbP+SrqaEs6ZfozCXfyb6fqK22qdQxA8uyxEykWEwjUhVS0jBCfbaJddj zDRD1XuzkRpy5+9BDRnm5EoFcNxjlzXvfVPAhHVmrGdxNyu97S6KyD342YbTD8Gvrdgz 41ijVMBjBYa3pKCp6ejgYG+qfl03B7s93uvI4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:from:date:message-id:subject:to:cc:content-type; b=J9rcqRMcW9YQeLkG4lWjKkImOpZMYp1rKIU/ZVQBdhc93fG/1hYQolT8eABtqt+d2P jaOgdl9NmCfJgU3ApUdMeEhM4p4Buoq0D+rvNN117U7Z8qKx6601F3+GwHSwNFgmisHQ GoycJ22TrvdYD7U+rPVuWllUcl3r0sDajJVdY= MIME-Version: 1.0 Received: by 10.142.9.31 with SMTP id 31mr292259wfi.96.1255929615254; Sun, 18 Oct 2009 22:20:15 -0700 (PDT) From: Yishuai Chen Date: Mon, 19 Oct 2009 13:19:55 +0800 Message-ID: To: ppsp@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Cc: "Chen, Chang Jia" Subject: [ppsp] Draft for Evaluation of DHT-based Chunk Discovery for P2P Streaming X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2009 05:20:19 -0000 Dear all: We have just posted a draft to evaluate the method to apply Distributed Hash Table (DHT) to do the media block search in P2P streaming systems. We discuss the disadvantages of the method, and evaluate its performance by simulation and modeling. We finally conclude this method is inappropriate for P2P live streaming system. Please see the below link for the detail. http://tools.ietf.org/html/draft-chen-ppsp-dht-chunk-discovery-evaluation-00 Welcome to your comments. Thanks! Regards Yishuai Chen Beijing Jiaotong University http://netcomm.bjtu.edu.cn Yunfei Zhang China Mobile http://labs.chinamobile.com From li.lichun1@zte.com.cn Mon Oct 19 00:15:55 2009 Return-Path: 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 BA06328C0DF for ; Mon, 19 Oct 2009 00:15:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.238 X-Spam-Level: X-Spam-Status: No, score=-99.238 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, 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 gDkOCWMz0NEs for ; Mon, 19 Oct 2009 00:15:55 -0700 (PDT) Received: from mx6.zte.com.cn (mx6.zte.com.cn [63.218.89.70]) by core3.amsl.com (Postfix) with ESMTP id 7E7413A68D8 for ; Mon, 19 Oct 2009 00:15:53 -0700 (PDT) Received: from [10.30.17.99] by mx6.zte.com.cn with surfront esmtp id 9110790912505; Mon, 19 Oct 2009 14:56:25 +0800 (CST) Received: from [10.30.3.19] by [10.30.17.99] with StormMail ESMTP id 39355.790912505; Mon, 19 Oct 2009 15:03:32 +0800 (CST) Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id n9J7FsfQ087045 for ; Mon, 19 Oct 2009 15:15:54 +0800 (CST) (envelope-from li.lichun1@zte.com.cn) To: ppsp@ietf.org MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007 Message-ID: From: li.lichun1@zte.com.cn Date: Mon, 19 Oct 2009 15:15:36 +0800 X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-10-19 15:15:41, Serialize complete at 2009-10-19 15:15:41 Content-Type: multipart/alternative; boundary="=_alternative 0028325748257654_=" X-MAIL: mse2.zte.com.cn n9J7FsfQ087045 Subject: [ppsp] about the performance of DHT-based chunk discovery X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2009 07:15:55 -0000 This is a multipart message in MIME format. --=_alternative 0028325748257654_= Content-Type: text/plain; charset="US-ASCII" Two drafts have evaluated the performance of DHT-based chunk discovery. However, multi-hop DHT is evaluated in these two drafts. In my option, one-hop DHT, instead of multi-hop DHT, should be used in the DHT-based tracker server farm. One-hop DHT has a very good performance in the server farm scenario. Amazon's dynamo is a good example. ===================================== Lichun Li ZTE Corpoporation 4F,RD Building 2,Zijinghua Road No.68 Yuhuatai District,Nanjing 210012 P.R.China Phone: +86-025-5287-7648 EMail: li.lichun1@zte.com.cn ===================================== -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system. --=_alternative 0028325748257654_= Content-Type: text/html; charset="US-ASCII"
Two drafts have evaluated the performance of DHT-based chunk discovery. However, multi-hop DHT is evaluated in these two drafts.
In my option, one-hop DHT, instead of multi-hop DHT, should be used in the DHT-based tracker server farm.
One-hop DHT has a very good performance in the server farm scenario. Amazon's dynamo is a good example.



=====================================
Lichun Li
ZTE Corpoporation
4F,RD Building 2,Zijinghua Road No.68
Yuhuatai District,Nanjing 210012
P.R.China
Phone: +86-025-5287-7648
EMail: li.lichun1@zte.com.cn              
=====================================

--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
--=_alternative 0028325748257654_=-- From softgear@etri.re.kr Mon Oct 19 07:19:22 2009 Return-Path: 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 E35AC28C177 for ; Mon, 19 Oct 2009 07:19:22 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.151 X-Spam-Level: X-Spam-Status: No, score=-101.151 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_MISMATCH_INFO=1.448, 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 DGrEYhnWXar8 for ; Mon, 19 Oct 2009 07:19:22 -0700 (PDT) Received: from email2.etri.info (email2.etri.re.kr [129.254.16.132]) by core3.amsl.com (Postfix) with ESMTP id ECC0D28C150 for ; Mon, 19 Oct 2009 07:19:21 -0700 (PDT) Received: from softgearpc ([129.254.232.20]) by email2.etri.info with Microsoft SMTPSVC(6.0.3790.3959); Mon, 19 Oct 2009 23:19:28 +0900 From: "Softgear Ko" To: Date: Mon, 19 Oct 2009 23:19:29 +0900 Message-ID: <008101ca50c7$2b7e4550$827acff0$@re.kr> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Office Outlook 12.0 thread-index: AcpQxnWWkaFKrisVRqO25hzrPOCDAAAADIkw Content-Language: ko X-OriginalArrivalTime: 19 Oct 2009 14:19:28.0080 (UTC) FILETIME=[2AD50D00:01CA50C7] Subject: [ppsp] Draft for Introduction of Olive and Grid Delivery X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Oct 2009 14:19:23 -0000 Dear all: We have just posted a draft to Introduction of Olive and Grid Delivery. http://www.ietf.org/internet-drafts/draft-softgear-ppsp-olive-griddeliver= y-intro-00.txt Welcome to your comments. Thank you. - Softgear Ko @ ETRI -----Original Message----- From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]=20 Sent: Monday, October 19, 2009 11:14 PM To: softgear@etri.re.kr Cc: osh93@etri.re.kr; bytelee@etri.re.kr Subject: New Version Notification for = draft-softgear-ppsp-olive-griddelivery-intro-00=20 A new version of I-D, = draft-softgear-ppsp-olive-griddelivery-intro-00.txt has been successfuly = submitted by Seok-Kap Ko and posted to the IETF repository. Filename: draft-softgear-ppsp-olive-griddelivery-intro Revision: 00 Title: Introduction of Olive and Grid Delivery Creation_date: 2009-10-18 WG ID: Independent Submission Number_of_pages: 19 Abstract: This draft briefly introduces Olive distributed media platform and=20 Grid Delivery solution. Olive platform, which is built by ETRI,=20 provides live peer-to-peer streaming service. Grid Delivery solution,=20 which is built by Peering Portal, is one of the most popular Peer-to- Peer solutions for VoD, AoD, live streaming, and file download=20 service in Korea. = =20 The IETF Secretariat. From guyingjie@huawei.com Mon Oct 19 19:46:47 2009 Return-Path: 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 C34763A6893 for ; Mon, 19 Oct 2009 19:46:47 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.665 X-Spam-Level: X-Spam-Status: No, score=-0.665 tagged_above=-999 required=5 tests=[AWL=-0.170, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] 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 hq3MvZwE8HrW for ; Mon, 19 Oct 2009 19:46:47 -0700 (PDT) Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id C3EE13A672F for ; Mon, 19 Oct 2009 19:46:46 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRS002Y2L1VW7@szxga04-in.huawei.com> for ppsp@ietf.org; Tue, 20 Oct 2009 10:46:43 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRS00C1KL1VN0@szxga04-in.huawei.com> for ppsp@ietf.org; Tue, 20 Oct 2009 10:46:43 +0800 (CST) Received: from g00107907 ([10.164.12.64]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KRS00C49L1VCK@szxml04-in.huawei.com> for ppsp@ietf.org; Tue, 20 Oct 2009 10:46:43 +0800 (CST) Date: Tue, 20 Oct 2009 10:46:43 +0800 From: "Y.J. Gu" In-reply-to: <008101ca50c7$2b7e4550$827acff0$@re.kr> To: ppsp@ietf.org Message-id: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcpQxnWWkaFKrisVRqO25hzrPOCDAAAADIkwABooTRA= Subject: Re: [ppsp] Draft for Introduction of Olive and Grid Delivery X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 02:46:47 -0000 Hi everyone, We submitted a survey draft for ppsp. Abstract: This document presents a survey of popular Peer-to-Peer streaming applications on the Internet. We focus on the Architecture and Peer Protocol/Tracker Signaling Protocol description in the presentation, and study a selection of well-known P2P streaming systems, including Joost, PPlive, and more. Through the survey, we summarize a common P2P streaming process model and the correspondent signaling process for P2P Streaming Protocol standardization. The URL for this draft is: http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt We appreciate your comments. Thanks. Regards Yingjie Gu From guyingjie@huawei.com Mon Oct 19 19:55:14 2009 Return-Path: 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 8A3B93A698A for ; Mon, 19 Oct 2009 19:55:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.623 X-Spam-Level: X-Spam-Status: No, score=-0.623 tagged_above=-999 required=5 tests=[AWL=-0.128, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1] 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 yVtwoEq89SGd for ; Mon, 19 Oct 2009 19:55:13 -0700 (PDT) Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id BAE873A689D for ; Mon, 19 Oct 2009 19:55:13 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRS0058JLFGK3@szxga04-in.huawei.com> for ppsp@ietf.org; Tue, 20 Oct 2009 10:54:52 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRS008OKLFGD7@szxga04-in.huawei.com> for ppsp@ietf.org; Tue, 20 Oct 2009 10:54:52 +0800 (CST) Received: from g00107907 ([10.164.12.64]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KRS00HC7LFE0Z@szxml04-in.huawei.com> for ppsp@ietf.org; Tue, 20 Oct 2009 10:54:51 +0800 (CST) Date: Tue, 20 Oct 2009 10:54:51 +0800 From: "Y.J. Gu" In-reply-to: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com> To: ppsp@ietf.org Message-id: <002301ca5130$b1d07830$400ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcpQxnWWkaFKrisVRqO25hzrPOCDAAAADIkwABooTRAAAE/24A== Subject: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 02:55:14 -0000 Hi everyone, We submitted a survey draft for ppsp. Abstract: This document presents a survey of popular Peer-to-Peer streaming applications on the Internet. We focus on the Architecture and Peer Protocol/Tracker Signaling Protocol description in the presentation, and study a selection of well-known P2P streaming systems, including Joost, PPlive, and more. Through the survey, we summarize a common P2P streaming process model and the correspondent signaling process for P2P Streaming Protocol standardization. The URL for this draft is: http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt We appreciate your comments. Thanks. Regards Yingjie Gu From skminh@gmail.com Tue Oct 20 02:43:25 2009 Return-Path: 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 B065428C0EF for ; Tue, 20 Oct 2009 02:43:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 gX0BCRwdHBaS for ; Tue, 20 Oct 2009 02:43:24 -0700 (PDT) Received: from mail-yx0-f192.google.com (mail-yx0-f192.google.com [209.85.210.192]) by core3.amsl.com (Postfix) with ESMTP id 8A0ED28C0D0 for ; Tue, 20 Oct 2009 02:43:24 -0700 (PDT) Received: by yxe30 with SMTP id 30so7073224yxe.29 for ; Tue, 20 Oct 2009 02:43:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=e9qm9sGU4trRo4yNsxfVrZ9O8nvrBBosdYjKiDW2PiY=; b=WIXXabznWNy+piVLdcTT74mfhyCrQN17goiSokafoT6PICXDu8+YYfmQtzMDDDweq6 5/cV1dv+KKsghDIXwMBnEU3OiR8puV+eeZPMwm2J1jg8A8OrYSF23FL4tUQrS++B2iHJ EGWx3OhFrfBDTCLC/WHW/DfC4t1NxtQtXhhI4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=HoKP/dswG1mbIVplHt2RPTE1EHZlGbUm7eqQoljGRUyQsOmFHTmHHrfRQIljNvRQHu MiMuetMcmpUCc8wogvNTgx6YrShF4bLkNVdDDCNm6elyPuwZjD77OUM8OmE7KfzuGQcc 4RO935c9S9cAwcmqNcMA/48V7n0L5cuqSR+es= MIME-Version: 1.0 Received: by 10.90.24.32 with SMTP id 32mr2543092agx.78.1256031806351; Tue, 20 Oct 2009 02:43:26 -0700 (PDT) In-Reply-To: <002301ca5130$b1d07830$400ca40a@china.huawei.com> References: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com> <002301ca5130$b1d07830$400ca40a@china.huawei.com> Date: Tue, 20 Oct 2009 11:43:26 +0200 Message-ID: <66dcf31f0910200243x33166aebi68322337672df234@mail.gmail.com> From: Minh Nguyen To: "Y.J. Gu" Content-Type: multipart/alternative; boundary=001636283cc4a4ea0f04765ab136 Cc: ppsp@ietf.org Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 09:43:25 -0000 --001636283cc4a4ea0f04765ab136 Content-Type: text/plain; charset=UTF-8 Dear all, I wonder that does PPSP work for not only Internet but also Wireless Ad hoc networks. If it's not the case, does anyone work on PPSP and Ad hoc networks? Does anyone have the suggestions in this topic? Thanks, -Minh On Tue, Oct 20, 2009 at 4:54 AM, Y.J. Gu wrote: > Hi everyone, > We submitted a survey draft for ppsp. > > Abstract: > This document presents a survey of popular Peer-to-Peer > streaming applications on the Internet. We focus on the > Architecture and Peer Protocol/Tracker Signaling Protocol > description in the presentation, and study a selection of > well-known P2P streaming systems, including Joost, PPlive, > and more. Through the survey, we summarize a common P2P > streaming process model and the correspondent signaling > process for P2P Streaming Protocol standardization. > > The URL for this draft is: > http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt > > We appreciate your comments. > Thanks. > > Regards > > Yingjie Gu > > > _______________________________________________ > ppsp mailing list > ppsp@ietf.org > https://www.ietf.org/mailman/listinfo/ppsp > -- Minh Nguyen +33 6 65 76 44 60 --001636283cc4a4ea0f04765ab136 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Dear all,
I wonder that does PPSP work for not only Internet but also Wi= reless Ad hoc networks.
If it's not the case, does anyone work on PP= SP and Ad hoc networks?
Does anyone have the suggestions in this topic?<= br>
Thanks,
-Minh

On Tue, Oct 20, 2009= at 4:54 AM, Y.J. Gu <guyingjie@huawei.com> wrote:
Hi everyone,
We submitted a survey draft for ppsp.

Abstract:
This document presents a survey of popular Peer-to-Peer
streaming applications on the Internet. =C2=A0We focus on the
Architecture and Peer Protocol/Tracker Signaling Protocol
description in the presentation, and study a selection of
well-known P2P streaming systems, including Joost, PPlive,
and more. =C2=A0Through the survey, we summarize a common P2P
streaming process model and the correspondent signaling
process for P2P Streaming Protocol standardization.

The URL for this draft is:
http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt

We appreciate your comments.
Thanks.

Regards

Yingjie Gu


_______________________________________________
ppsp mailing list
ppsp@ietf.org
ht= tps://www.ietf.org/mailman/listinfo/ppsp



--
Minh Nguyen
+33 6 65= 76 44 60

--001636283cc4a4ea0f04765ab136-- From zhangyunfei@chinamobile.com Tue Oct 20 02:48:19 2009 Return-Path: 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 9FD1E3A6A1A for ; Tue, 20 Oct 2009 02:48:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -96.173 X-Spam-Level: X-Spam-Status: No, score=-96.173 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RELAY_IS_221=2.222, 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 HuHLxn-QQWzJ for ; Tue, 20 Oct 2009 02:48:18 -0700 (PDT) Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.130.253.133]) by core3.amsl.com (Postfix) with ESMTP id 7EA953A6A0F for ; Tue, 20 Oct 2009 02:48:18 -0700 (PDT) Received: from LENOVO-917FFE55 ([10.2.0.40]) by mail.chinamobile.com (Lotus Domino Release 6.5.5FP1) with SMTP id 2009102017525457-15981 ; Tue, 20 Oct 2009 17:52:54 +0800 Date: Tue, 20 Oct 2009 17:48:17 +0800 From: "zhangyunfei" To: "Minh Nguyen" , "Y.J. Gu" References: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com><002301ca5130$b1d07830$400ca40a@china.huawei.com> <66dcf31f0910200243x33166aebi68322337672df234@mail.gmail.com> Message-ID: <200910201748166253822@chinamobile.com> X-mailer: Foxmail 6, 2, 103, 20 [cn] Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2009-10-20 17:52:55, Serialize by Router on cmccmta/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2009-10-20 17:48:26, Serialize complete at 2009-10-20 17:48:26 Content-Type: multipart/alternative; boundary="=====003_Dragon482103214625_=====" Cc: "ppsp@ietf.org" Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 09:48:19 -0000 This is a multi-part message in MIME format. --=====003_Dragon482103214625_===== Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="gb2312" SGkgTWluaKOsDQogUFBTUCBpcyBpbnRlbmRlZCB0byBzdXBwb3J0IGJvdGggZW52aXJubWVudHMs IGluY2x1ZGluZyB0aGUgd2lyZWxlc3MgYWQgaG9jIG5ldHdvcmsuSG93ZXZlciB0aGVyZSBpc24n dCBtdWNoIGxhcmdlIHNjYWxlIFBQU1AgcHJhY3RpY2UgaW4gYWQgaG9jIG5ldHdvcmtzIHRvIHRo ZSBiZXN0IG9mIG91ciBrbm93bGVkZ2UuSWYgeW91IGhhdmUgc3VjaCBpbmZvcm1hdGlvbiwgd2Vs Y29tZSB0byBjb250cmlidXRlIGl0Lg0KDQpUaGFua3MsDQpZdW5mZWkNCg0KDQoNCg0Kemhhbmd5 dW5mZWkNCjIwMDktMTAtMjANCg0KDQoNCreivP7Iy6O6IE1pbmggTmd1eWVuDQq3osvNyrG85KO6 IDIwMDktMTAtMjAgMTc6NDg6MTUNCsrVvP7Iy6O6IFkuSi4gR3UNCrOty82juiBwcHNwQGlldGYu b3JnDQrW98zio7ogUmU6IFtwcHNwXSBEcmFmdCBmb3IgUFBTUCBTdXJ2ZXkNCg0KRGVhciBhbGws DQpJIHdvbmRlciB0aGF0IGRvZXMgUFBTUCB3b3JrIGZvciBub3Qgb25seSBJbnRlcm5ldCBidXQg YWxzbyBXaXJlbGVzcyBBZCBob2MgbmV0d29ya3MuDQpJZiBpdCdzIG5vdCB0aGUgY2FzZSwgZG9l cyBhbnlvbmUgd29yayBvbiBQUFNQIGFuZCBBZCBob2MgbmV0d29ya3M/DQpEb2VzIGFueW9uZSBo YXZlIHRoZSBzdWdnZXN0aW9ucyBpbiB0aGlzIHRvcGljPw0KDQpUaGFua3MsDQotTWluaA0KDQoN Ck9uIFR1ZSwgT2N0IDIwLCAyMDA5IGF0IDQ6NTQgQU0sIFkuSi4gR3UgPGd1eWluZ2ppZUBodWF3 ZWkuY29tPiB3cm90ZToNCg0KSGkgZXZlcnlvbmUsDQpXZSBzdWJtaXR0ZWQgYSBzdXJ2ZXkgZHJh ZnQgZm9yIHBwc3AuDQoNCkFic3RyYWN0Og0KVGhpcyBkb2N1bWVudCBwcmVzZW50cyBhIHN1cnZl eSBvZiBwb3B1bGFyIFBlZXItdG8tUGVlcg0Kc3RyZWFtaW5nIGFwcGxpY2F0aW9ucyBvbiB0aGUg SW50ZXJuZXQuID9XZSBmb2N1cyBvbiB0aGUNCkFyY2hpdGVjdHVyZSBhbmQgUGVlciBQcm90b2Nv bC9UcmFja2VyIFNpZ25hbGluZyBQcm90b2NvbA0KZGVzY3JpcHRpb24gaW4gdGhlIHByZXNlbnRh dGlvbiwgYW5kIHN0dWR5IGEgc2VsZWN0aW9uIG9mDQp3ZWxsLWtub3duIFAyUCBzdHJlYW1pbmcg c3lzdGVtcywgaW5jbHVkaW5nIEpvb3N0LCBQUGxpdmUsDQphbmQgbW9yZS4gP1Rocm91Z2ggdGhl IHN1cnZleSwgd2Ugc3VtbWFyaXplIGEgY29tbW9uIFAyUA0Kc3RyZWFtaW5nIHByb2Nlc3MgbW9k ZWwgYW5kIHRoZSBjb3JyZXNwb25kZW50IHNpZ25hbGluZw0KcHJvY2VzcyBmb3IgUDJQIFN0cmVh bWluZyBQcm90b2NvbCBzdGFuZGFyZGl6YXRpb24uDQoNClRoZSBVUkwgZm9yIHRoaXMgZHJhZnQg aXM6DQpodHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWd1LXBwc3Atc3VydmV5LTAwLnR4dA0K DQpXZSBhcHByZWNpYXRlIHlvdXIgY29tbWVudHMuDQpUaGFua3MuDQoNClJlZ2FyZHMNCg0KWWlu Z2ppZSBHdQ0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fDQpwcHNwIG1haWxpbmcgbGlzdA0KcHBzcEBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5v cmcvbWFpbG1hbi9saXN0aW5mby9wcHNwDQoNCg0KDQoNCi0tIA0KTWluaCBOZ3V5ZW4NCiszMyA2 IDY1IDc2IDQ0IDYwDQo= --=====003_Dragon482103214625_===== Content-Transfer-Encoding: base64 Content-Type: text/html; charset="gb2312" PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w MC4yOTAwLjM0OTIiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPg0KPCEtLQ0KIC8qIEZvbnQgRGVm aW5pdGlvbnMgKi8NCiBAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OsvOzOU7DQoJcGFub3NlLTE6 MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlZlcmRhbmE7 DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh bWlseToiXEDLzszlIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCiAvKiBTdHls ZSBEZWZpbml0aW9ucyAqLw0KIHAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3Jt YWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJdGV4dC1hbGlnbjpq dXN0aWZ5Ow0KCXRleHQtanVzdGlmeTppbnRlci1pZGVvZ3JhcGg7DQoJZm9udC1zaXplOjEwLjVw dDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjt9DQphOmxpbmssIHNwYW4uTXNvSHlw ZXJsaW5rDQoJe2NvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7Y29sb3I6cHVycGxlOw0KCXRleHQt ZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5 cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseTpWZXJkYW5hOw0KCWNvbG9yOndpbmRv d3RleHQ7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQt ZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0KIC8qIFBhZ2UgRGVmaW5pdGlvbnMgKi8NCiBAcGFnZSBT ZWN0aW9uMQ0KCXtzaXplOjU5NS4zcHQgODQxLjlwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3 Mi4wcHQgOTAuMHB0Ow0KCWxheW91dC1ncmlkOjE1LjZwdDt9DQpkaXYuU2VjdGlvbjENCgl7cGFn ZTpTZWN0aW9uMTt9DQotLT4NCjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9EWT4NCjxESVY+PEZPTlQg ZmFjZT1WZXJkYW5hIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPkhpIE1pbmijrDwvRk9OVD48L0RJVj4N CjxESVY+PEZPTlQgZmFjZT1WZXJkYW5hIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPiZuYnNwO1BQU1Am bmJzcDtpcyBpbnRlbmRlZCB0byANCnN1cHBvcnQgYm90aCZuYnNwO2Vudmlybm1lbnRzLCBpbmNs dWRpbmcgdGhlIHdpcmVsZXNzIGFkIGhvYyBuZXR3b3JrLkhvd2V2ZXIgDQp0aGVyZSBpc24ndCBt dWNoIGxhcmdlIHNjYWxlIFBQU1AgcHJhY3RpY2UgaW4gYWQgaG9jIG5ldHdvcmtzIHRvIHRoZSBi ZXN0IG9mIG91ciANCmtub3dsZWRnZS5JZiB5b3UgaGF2ZSBzdWNoIGluZm9ybWF0aW9uLCB3ZWxj b21lIHRvIGNvbnRyaWJ1dGUgaXQuPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRh bmEgY29sb3I9IzAwMDBmZiBzaXplPTI+PC9GT05UPiZuYnNwOzwvRElWPg0KPERJVj48Rk9OVCBm YWNlPVZlcmRhbmEgY29sb3I9IzAwMDBmZiBzaXplPTI+VGhhbmtzLDwvRk9OVD48L0RJVj4NCjxE SVY+PEZPTlQgZmFjZT1WZXJkYW5hIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPll1bmZlaTwvRk9OVD48 L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1WZXJkYW5hIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+ DQo8RElWIGFsaWduPWxlZnQ+DQo8RElWIGFsaWduPWxlZnQ+PEZPTlQgZmFjZT1WZXJkYW5hIHNp emU9Mj4NCjxIUiBzdHlsZT0iV0lEVEg6IDEyMnB4OyBIRUlHSFQ6IDJweCIgU0laRT0yPg0KPC9G T05UPjwvRElWPg0KPERJVj48Rk9OVCBjb2xvcj0jYzBjMGMwPjxGT05UIGZhY2U9VmVyZGFuYSBz aXplPTI+emhhbmd5dW5mZWk8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBz aXplPTI+MjAwOS0xMC0yMDwvRk9OVD48L0ZPTlQ+PC9ESVY+PC9ESVY+DQo8RElWPjxGT05UIGZh Y2U9VmVyZGFuYSBzaXplPTI+DQo8SFI+DQo8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9 VmVyZGFuYT48Rk9OVCBzaXplPTI+PFNUUk9ORz63orz+yMujujwvU1RST05HPiBNaW5oIA0KTmd1 eWVuPC9GT05UPjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1WZXJkYW5hPjxGT05UIHNp emU9Mj48U1RST05HPreiy83Ksbzko7o8L1NUUk9ORz4gDQoyMDA5LTEwLTIwJm5ic3A7MTc6NDg6 MTU8L0ZPTlQ+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmE+PEZPTlQgc2l6 ZT0yPjxTVFJPTkc+ytW8/sjLo7o8L1NUUk9ORz4gWS5KLiANCkd1PC9GT05UPjwvRk9OVD48L0RJ Vj4NCjxESVY+PEZPTlQgZmFjZT1WZXJkYW5hPjxGT05UIHNpemU9Mj48U1RST05HPrOty82jujwv U1RST05HPiANCnBwc3BAaWV0Zi5vcmc8L0ZPTlQ+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBm YWNlPVZlcmRhbmE+PEZPTlQgc2l6ZT0yPjxTVFJPTkc+1vfM4qO6PC9TVFJPTkc+IFJlOiBbcHBz cF0gRHJhZnQgZm9yIA0KUFBTUCBTdXJ2ZXk8L0ZPTlQ+PC9GT05UPjwvRElWPg0KPERJVj48Rk9O VCBmYWNlPVZlcmRhbmEgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgZmFj ZT1WZXJkYW5hIHNpemU9Mj5EZWFyIGFsbCw8QlI+SSB3b25kZXIgdGhhdCBkb2VzIFBQU1Agd29y ayBmb3Igbm90IA0Kb25seSBJbnRlcm5ldCBidXQgYWxzbyBXaXJlbGVzcyBBZCBob2MgbmV0d29y a3MuPEJSPklmIGl0J3Mgbm90IHRoZSBjYXNlLCBkb2VzIA0KYW55b25lIHdvcmsgb24gUFBTUCBh bmQgQWQgaG9jIG5ldHdvcmtzPzxCUj5Eb2VzIGFueW9uZSBoYXZlIHRoZSBzdWdnZXN0aW9ucyBp biANCnRoaXMgdG9waWM/PEJSPjxCUj5UaGFua3MsPEJSPi1NaW5oPEJSPjxCUj4NCjxESVYgY2xh c3M9Z21haWxfcXVvdGU+T24gVHVlLCBPY3QgMjAsIDIwMDkgYXQgNDo1NCBBTSwgWS5KLiBHdSA8 U1BBTiANCmRpcj1sdHI+Jmx0OzxBIA0KaHJlZj0ibWFpbHRvOmd1eWluZ2ppZUBodWF3ZWkuY29t Ij5ndXlpbmdqaWVAaHVhd2VpLmNvbTwvQT4mZ3Q7PC9TUEFOPiANCndyb3RlOjxCUj4NCjxCTE9D S1FVT1RFIGNsYXNzPWdtYWlsX3F1b3RlIA0Kc3R5bGU9IlBBRERJTkctTEVGVDogMWV4OyBNQVJH SU46IDBwdCAwcHQgMHB0IDAuOGV4OyBCT1JERVItTEVGVDogcmdiKDIwNCwyMDQsMjA0KSAxcHgg c29saWQiPkhpIA0KICBldmVyeW9uZSw8QlI+V2Ugc3VibWl0dGVkIGEgc3VydmV5IGRyYWZ0IGZv ciBwcHNwLjxCUj48QlI+QWJzdHJhY3Q6PEJSPlRoaXMgDQogIGRvY3VtZW50IHByZXNlbnRzIGEg c3VydmV5IG9mIHBvcHVsYXIgUGVlci10by1QZWVyPEJSPnN0cmVhbWluZyBhcHBsaWNhdGlvbnMg DQogIG9uIHRoZSBJbnRlcm5ldC4gP1dlIGZvY3VzIG9uIHRoZTxCUj5BcmNoaXRlY3R1cmUgYW5k IFBlZXIgUHJvdG9jb2wvVHJhY2tlciANCiAgU2lnbmFsaW5nIFByb3RvY29sPEJSPmRlc2NyaXB0 aW9uIGluIHRoZSBwcmVzZW50YXRpb24sIGFuZCBzdHVkeSBhIHNlbGVjdGlvbiANCiAgb2Y8QlI+ d2VsbC1rbm93biBQMlAgc3RyZWFtaW5nIHN5c3RlbXMsIGluY2x1ZGluZyBKb29zdCwgUFBsaXZl LDxCUj5hbmQgbW9yZS4gDQogID9UaHJvdWdoIHRoZSBzdXJ2ZXksIHdlIHN1bW1hcml6ZSBhIGNv bW1vbiBQMlA8QlI+c3RyZWFtaW5nIHByb2Nlc3MgbW9kZWwgYW5kIA0KICB0aGUgY29ycmVzcG9u ZGVudCBzaWduYWxpbmc8QlI+cHJvY2VzcyBmb3IgUDJQIFN0cmVhbWluZyBQcm90b2NvbCANCiAg c3RhbmRhcmRpemF0aW9uLjxCUj48QlI+VGhlIFVSTCBmb3IgdGhpcyBkcmFmdCBpczo8QlI+PEEg DQogIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtZ3UtcHBzcC1zdXJ2ZXktMDAu dHh0IiANCiAgdGFyZ2V0PV9ibGFuaz5odHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWd1LXBw c3Atc3VydmV5LTAwLnR4dDwvQT48QlI+PEJSPldlIA0KICBhcHByZWNpYXRlIHlvdXIgY29tbWVu dHMuPEJSPlRoYW5rcy48QlI+PEJSPlJlZ2FyZHM8QlI+PEJSPllpbmdqaWUgDQogIEd1PEJSPjxC Uj48QlI+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188QlI+ cHBzcCBtYWlsaW5nIA0KICBsaXN0PEJSPjxBIGhyZWY9Im1haWx0bzpwcHNwQGlldGYub3JnIj5w cHNwQGlldGYub3JnPC9BPjxCUj48QSANCiAgaHJlZj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp bG1hbi9saXN0aW5mby9wcHNwIiANCiAgdGFyZ2V0PV9ibGFuaz5odHRwczovL3d3dy5pZXRmLm9y Zy9tYWlsbWFuL2xpc3RpbmZvL3Bwc3A8L0E+PEJSPjwvQkxPQ0tRVU9URT48L0RJVj48QlI+PEJS IA0KY2xlYXI9YWxsPjxCUj4tLSA8QlI+TWluaCBOZ3V5ZW48QlI+KzMzIDYgNjUgNzYgNDQgDQo2 MDxCUj48QlI+PC9GT05UPjwvRElWPjwvQk9EWT48L0hUTUw+DQo= --=====003_Dragon482103214625_=====-- From skminh@gmail.com Tue Oct 20 04:00:53 2009 Return-Path: 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 830CE3A68A3 for ; Tue, 20 Oct 2009 04:00:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.598 X-Spam-Level: X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001] 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 j7THxqkLzUtv for ; Tue, 20 Oct 2009 04:00:52 -0700 (PDT) Received: from mail-yw0-f183.google.com (mail-yw0-f183.google.com [209.85.211.183]) by core3.amsl.com (Postfix) with ESMTP id 0A2373A6822 for ; Tue, 20 Oct 2009 04:00:51 -0700 (PDT) Received: by ywh13 with SMTP id 13so7456511ywh.29 for ; Tue, 20 Oct 2009 04:00:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=NfMQQ/Z4e1/TsNqBtFH8/rAXl4W6BBfd0Q1vqO7YYLQ=; b=jdiRVz1sqaM/WP9/vibmV64f+5KtGW9QZzGBYUzc5nZKbtNVRQH20QJAU7iJFKCPv6 t+exCwXO43l8wzi1rs18p4bfUUbs4GfuRTKuRpU1DRWhUdEZJS+wNsaALBnYV0eHVSV+ uFx/gGLmCkroytMh6Q/Z1/ApQ3lIhvFSVjf+8= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=hkWKLoZk7uTMyH5UZs3cBHGI6pKuwx67cw1Xk+CNcAStPK1JuUf7vBRvT+yH6oGIhl slTKMo3QhriiYMrlJSv19xTUsdBuAtr/pb0iY689rlzFHAmsH500hochJGO2x1f0mBrK LbhwQTvjS9uG9NLOkCyVISgF+NbyMWjQ2cozU= MIME-Version: 1.0 Received: by 10.91.171.4 with SMTP id y4mr6041917ago.116.1256036454978; Tue, 20 Oct 2009 04:00:54 -0700 (PDT) In-Reply-To: <200910201748166253822@chinamobile.com> References: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com> <002301ca5130$b1d07830$400ca40a@china.huawei.com> <66dcf31f0910200243x33166aebi68322337672df234@mail.gmail.com> <200910201748166253822@chinamobile.com> Date: Tue, 20 Oct 2009 13:00:54 +0200 Message-ID: <66dcf31f0910200400od867e43ld5692582c9d1904f@mail.gmail.com> From: Minh Nguyen To: zhangyunfei Content-Type: multipart/alternative; boundary=0016e646065cb9571404765bc6c1 Cc: "ppsp@ietf.org" Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 11:00:53 -0000 --0016e646065cb9571404765bc6c1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Yunfei, I have just started the works for P2P video streaming over Ad hoc networks in which P2P streaming need to be operated efficiently on top of OLSR ad ho= c routing layer. As I have seen PPSP would be IETF's standard protocol for P2P streaming, It was a good choice if PPSP could be adapted for Ad hoc/Mesh networks accordingly. Do you have any recommend for that? for example, is it possible to extend o= r adapt PPSP according to the network environment? Thanks, Minh 2009/10/20 zhangyunfei > Hi Minh=EF=BC=8C > PPSP is intended to support both envirnments, including the wireless ad > hoc network.However there isn't much large scale PPSP practice in ad hoc > networks to the best of our knowledge.If you have such information, welco= me > to contribute it. > > Thanks, > Yunfei > > ------------------------------ > zhangyunfei > 2009-10-20 > ------------------------------ > *=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A* Minh Nguyen > *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A* 2009-10-20 17:48:15 > *=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A* Y.J. Gu > *=E6=8A=84=E9=80=81=EF=BC=9A* ppsp@ietf.org > *=E4=B8=BB=E9=A2=98=EF=BC=9A* Re: [ppsp] Draft for PPSP Survey > > Dear all, > I wonder that does PPSP work for not only Internet but also Wireless Ad h= oc > networks. > If it's not the case, does anyone work on PPSP and Ad hoc networks? > Does anyone have the suggestions in this topic? > > Thanks, > -Minh > > On Tue, Oct 20, 2009 at 4:54 AM, Y.J. Gu wrote: > >> Hi everyone, >> We submitted a survey draft for ppsp. >> >> Abstract: >> This document presents a survey of popular Peer-to-Peer >> streaming applications on the Internet. ?We focus on the >> Architecture and Peer Protocol/Tracker Signaling Protocol >> description in the presentation, and study a selection of >> well-known P2P streaming systems, including Joost, PPlive, >> and more. ?Through the survey, we summarize a common P2P >> streaming process model and the correspondent signaling >> process for P2P Streaming Protocol standardization. >> >> The URL for this draft is: >> http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt >> >> We appreciate your comments. >> Thanks. >> >> Regards >> >> Yingjie Gu >> >> >> _______________________________________________ >> ppsp mailing list >> ppsp@ietf.org >> https://www.ietf.org/mailman/listinfo/ppsp >> > > > > -- > Minh Nguyen > +33 6 65 76 44 60 > > --=20 Minh Nguyen +33 6 65 76 44 60 --0016e646065cb9571404765bc6c1 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Yunfei,
I have just starte= d the works for P2P video streaming over Ad hoc networks in which P2P strea= ming need to be operated efficiently on top of OLSR ad hoc routing layer.

As I have seen PPSP would be IETF's standard protocol for P2P streamin= g, It was a good choice if PPSP could be adapted for Ad hoc/Mesh networks a= ccordingly.
Do you have any recommend for that? = for example, is it possible to extend or adapt PPSP according to the networ= k environment?

Thanks,
Minh

2009/10/20 zhangyunfei <zhangyunfei@chinamobile.com&g= t;
Hi Minh=EF=BC=8C
=C2=A0PPSP=C2=A0is= intended to=20 support both=C2=A0envirnments, including the wireless ad hoc network.Howeve= r=20 there isn't much large scale PPSP practice in ad hoc networks to the be= st of our=20 knowledge.If you have such information, welcome to contribute it.
=C2=A0
Thanks,
Yunfei
=C2=A0
zhangyunfei<= /font>
2009-10-20
=E5=8F=91=E4=BB=B6=E4=BA=BA= =EF=BC=9A Minh=20 Nguyen
=E5=8F=91=E9=80=81=E6=97=B6= =E9=97=B4=EF=BC=9A=20 2009-10-20=C2=A017:48:15
=E6=94=B6=E4=BB=B6=E4=BA=BA= =EF=BC=9A Y.J.=20 Gu
=E6=8A=84=E9=80=81=EF=BC=9A= =20 ppsp@ietf.org=
=E4=B8=BB=E9=A2=98=EF=BC=9A= Re: [ppsp] Draft for=20 PPSP Survey
=C2=A0
Dear all,
I wonder that does PPSP= work for not=20 only Internet but also Wireless Ad hoc networks.
If it's not the cas= e, does=20 anyone work on PPSP and Ad hoc networks?
Does anyone have the suggestion= s in=20 this topic?

Thanks,
-Minh

On Tue, Oct 20, 2009 at 4:54 AM, Y.J. Gu <gu= yingjie@huawei.com>=20 wrote:
Hi=20 everyone,
We submitted a survey draft for ppsp.

Abstract:
Th= is=20 document presents a survey of popular Peer-to-Peer
streaming applicati= ons=20 on the Internet. ?We focus on the
Architecture and Peer Protocol/Track= er=20 Signaling Protocol
description in the presentation, and study a select= ion=20 of
well-known P2P streaming systems, including Joost, PPlive,
and m= ore.=20 ?Through the survey, we summarize a common P2P
streaming process model= and=20 the correspondent signaling
process for P2P Streaming Protocol=20 standardization.

The URL for this draft is:
http://www.ie= tf.org/id/draft-gu-ppsp-survey-00.txt

We=20 appreciate your comments.
Thanks.

Regards

Yingjie=20 Gu


_______________________________________________
ppsp mai= ling=20 list
ppsp@ietf.org<= /a>
https://www.ietf.org/mailman/listinfo/ppsp
<= br>

--
Minh Nguyen
+33 6 65 76 44=20 60




--
Minh Nguyen
+33 6 65= 76 44 60

--0016e646065cb9571404765bc6c1-- From victor.pascual.avila@gmail.com Tue Oct 20 04:11:25 2009 Return-Path: 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 BFB953A67AC for ; Tue, 20 Oct 2009 04:11:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.486 X-Spam-Level: X-Spam-Status: No, score=-2.486 tagged_above=-999 required=5 tests=[AWL=0.114, BAYES_00=-2.599] 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 ROVWlSb9J04t for ; Tue, 20 Oct 2009 04:11:25 -0700 (PDT) Received: from mail-ew0-f214.google.com (mail-ew0-f214.google.com [209.85.219.214]) by core3.amsl.com (Postfix) with ESMTP id 3E4483A6784 for ; Tue, 20 Oct 2009 04:11:24 -0700 (PDT) Received: by ewy10 with SMTP id 10so5116952ewy.9 for ; Tue, 20 Oct 2009 04:11:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=EAXKOqxxExiNYGRLH/AgQfs3G8hAmL8RKPlVQGZkBSU=; b=WSOjuiBLyfKNSQA5ljMvzAZ16jmiqh2vDlX//u8K0VTOOQJ7UU26jYXWBI2acXu4oT tcyKEY5QD2T1dMxqofLhwp4R1s4gYpDbjOgWJvWhZgK9JryK1gjpV4usAzSQd1yf4VKo 3hBlUGgfSzro7IKhi6iDNriId2RNSX53PeP0g= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=RwOfRDB8V2+ndkLSbwUcgVI4liEHcUXuyDq1ux6V8zA8602U6KE51mwt0FKcSrbdXY OSjS7EUiQQOtkHbCk0UXZvbo90LtUFXapTXQlaAFkyc9d5m32ZbtWx9UyMRVMWbAv58s v7Mvfo8cz9J6lt8gTqG7dEX/QSalwtna0d5Dk= MIME-Version: 1.0 Received: by 10.216.88.21 with SMTP id z21mr2341010wee.60.1256037088748; Tue, 20 Oct 2009 04:11:28 -0700 (PDT) In-Reply-To: <66dcf31f0910200400od867e43ld5692582c9d1904f@mail.gmail.com> References: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com> <002301ca5130$b1d07830$400ca40a@china.huawei.com> <66dcf31f0910200243x33166aebi68322337672df234@mail.gmail.com> <200910201748166253822@chinamobile.com> <66dcf31f0910200400od867e43ld5692582c9d1904f@mail.gmail.com> Date: Tue, 20 Oct 2009 13:11:28 +0200 Message-ID: <618e24240910200411k432870b4o76c1def7014a319d@mail.gmail.com> From: Victor Pascual Avila To: Minh Nguyen Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: "ppsp@ietf.org" Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 11:11:25 -0000 Hi, On Tue, Oct 20, 2009 at 1:00 PM, Minh Nguyen wrote: (snip) > is it possible to extend or > adapt PPSP according to the network environment? Could you please elaborate this approach? Cheers, --=20 Victor Pascual =C3=81vila From zhangyunfei@chinamobile.com Tue Oct 20 05:39:21 2009 Return-Path: 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 685AC3A6983 for ; Tue, 20 Oct 2009 05:39:21 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -95.873 X-Spam-Level: X-Spam-Status: No, score=-95.873 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_52=0.6, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RELAY_IS_221=2.222, 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 uTFWV3BVPdYq for ; Tue, 20 Oct 2009 05:39:19 -0700 (PDT) Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.130.253.133]) by core3.amsl.com (Postfix) with ESMTP id 33B613A696E for ; Tue, 20 Oct 2009 05:39:19 -0700 (PDT) Received: from LENOVO-917FFE55 ([10.2.0.40]) by mail.chinamobile.com (Lotus Domino Release 6.5.5FP1) with SMTP id 2009102020435189-18276 ; Tue, 20 Oct 2009 20:43:51 +0800 Date: Tue, 20 Oct 2009 20:39:12 +0800 From: "zhangyunfei" To: "Minh Nguyen" References: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com> <002301ca5130$b1d07830$400ca40a@china.huawei.com> <66dcf31f0910200243x33166aebi68322337672df234@mail.gmail.com> <200910201748166253822@chinamobile.com> <66dcf31f0910200400od867e43ld5692582c9d1904f@mail.gmail.com> Message-ID: <200910202039123754205@chinamobile.com> X-mailer: Foxmail 6, 2, 103, 20 [cn] Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2009-10-20 20:43:51, Serialize by Router on cmccmta/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2009-10-20 20:39:27, Serialize complete at 2009-10-20 20:39:27 Content-Type: multipart/alternative; boundary="=====003_Dragon756512547582_=====" Cc: "ppsp@ietf.org" Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 Oct 2009 12:39:21 -0000 This is a multi-part message in MIME format. --=====003_Dragon756512547582_===== Content-Transfer-Encoding: base64 Content-Type: text/plain; charset="gb2312" R29vZCBwb2ludCFXZSBoYXZlIGEgUFBTUCByZXF1aXJlbWVudCBkcmFmdCB0byBlbnVtZXJhdGUg dGhlIHdoYXQgZmFjdG9ycyBQUFNQIHByb3RvY29scyBuZWVkIHRvIGFkZHJlc3MuVGhlIG5ldyB2 ZXJzaW9uIG9mIHRoZSBkcmFmdCB3aWxsIGNvbWUgb3V0IHNvb24uWW91IG1heSByZWZlciB0byBp dCBhbmQgY29udHJpYnV0ZSBpbiB0aGlzIGRyYWZ0IGFib3V0IHlvdXIgY29uY2VybnMuDQoNCkJS DQpZdW5mZWkNCg0KDQoNCg0Kemhhbmd5dW5mZWkNCjIwMDktMTAtMjANCg0KDQoNCreivP7Iy6O6 IE1pbmggTmd1eWVuDQq3osvNyrG85KO6IDIwMDktMTAtMjAgMTk6MDU6MzUNCsrVvP7Iy6O6IHpo YW5neXVuZmVpDQqzrcvNo7ogWS5KLiBHdTsgcHBzcEBpZXRmLm9yZw0K1vfM4qO6IFJlOiBSZTog W3Bwc3BdIERyYWZ0IGZvciBQUFNQIFN1cnZleQ0KDQpIaSBZdW5mZWksDQpJIGhhdmUganVzdCBz dGFydGVkIHRoZSB3b3JrcyBmb3IgUDJQIHZpZGVvIHN0cmVhbWluZyBvdmVyIEFkIGhvYyBuZXR3 b3JrcyBpbiB3aGljaCBQMlAgc3RyZWFtaW5nIG5lZWQgdG8gYmUgb3BlcmF0ZWQgZWZmaWNpZW50 bHkgb24gdG9wIG9mIE9MU1IgYWQgaG9jIHJvdXRpbmcgbGF5ZXIuDQoNCkFzIEkgaGF2ZSBzZWVu IFBQU1Agd291bGQgYmUgSUVURidzIHN0YW5kYXJkIHByb3RvY29sIGZvciBQMlAgc3RyZWFtaW5n LCBJdCB3YXMgYSBnb29kIGNob2ljZSBpZiBQUFNQIGNvdWxkIGJlIGFkYXB0ZWQgZm9yIEFkIGhv Yy9NZXNoIG5ldHdvcmtzIGFjY29yZGluZ2x5Lg0KRG8geW91IGhhdmUgYW55IHJlY29tbWVuZCBm b3IgdGhhdD8gZm9yIGV4YW1wbGUsIGlzIGl0IHBvc3NpYmxlIHRvIGV4dGVuZCBvciBhZGFwdCBQ UFNQIGFjY29yZGluZyB0byB0aGUgbmV0d29yayBlbnZpcm9ubWVudD8NCg0KVGhhbmtzLA0KTWlu aA0KDQoNCjIwMDkvMTAvMjAgemhhbmd5dW5mZWkgPHpoYW5neXVuZmVpQGNoaW5hbW9iaWxlLmNv bT4NCg0KSGkgTWluaKOsDQo/UFBTUD9pcyBpbnRlbmRlZCB0byBzdXBwb3J0IGJvdGg/ZW52aXJu bWVudHMsIGluY2x1ZGluZyB0aGUgd2lyZWxlc3MgYWQgaG9jIG5ldHdvcmsuSG93ZXZlciB0aGVy ZSBpc24ndCBtdWNoIGxhcmdlIHNjYWxlIFBQU1AgcHJhY3RpY2UgaW4gYWQgaG9jIG5ldHdvcmtz IHRvIHRoZSBiZXN0IG9mIG91ciBrbm93bGVkZ2UuSWYgeW91IGhhdmUgc3VjaCBpbmZvcm1hdGlv biwgd2VsY29tZSB0byBjb250cmlidXRlIGl0Lg0KPw0KVGhhbmtzLA0KWXVuZmVpDQo/DQoNCg0K DQp6aGFuZ3l1bmZlaQ0KMjAwOS0xMC0yMA0KDQoNCg0Kt6K8/sjLo7ogTWluaCBOZ3V5ZW4NCrei y83Ksbzko7ogMjAwOS0xMC0yMD8xNzo0ODoxNQ0KytW8/sjLo7ogWS5KLiBHdQ0Ks63LzaO6IHBw c3BAaWV0Zi5vcmcNCtb3zOKjuiBSZTogW3Bwc3BdIERyYWZ0IGZvciBQUFNQIFN1cnZleQ0KPw0K RGVhciBhbGwsDQpJIHdvbmRlciB0aGF0IGRvZXMgUFBTUCB3b3JrIGZvciBub3Qgb25seSBJbnRl cm5ldCBidXQgYWxzbyBXaXJlbGVzcyBBZCBob2MgbmV0d29ya3MuDQpJZiBpdCdzIG5vdCB0aGUg Y2FzZSwgZG9lcyBhbnlvbmUgd29yayBvbiBQUFNQIGFuZCBBZCBob2MgbmV0d29ya3M/DQpEb2Vz IGFueW9uZSBoYXZlIHRoZSBzdWdnZXN0aW9ucyBpbiB0aGlzIHRvcGljPw0KDQpUaGFua3MsDQot TWluaA0KDQoNCk9uIFR1ZSwgT2N0IDIwLCAyMDA5IGF0IDQ6NTQgQU0sIFkuSi4gR3UgPGd1eWlu Z2ppZUBodWF3ZWkuY29tPiB3cm90ZToNCg0KSGkgZXZlcnlvbmUsDQpXZSBzdWJtaXR0ZWQgYSBz dXJ2ZXkgZHJhZnQgZm9yIHBwc3AuDQoNCkFic3RyYWN0Og0KVGhpcyBkb2N1bWVudCBwcmVzZW50 cyBhIHN1cnZleSBvZiBwb3B1bGFyIFBlZXItdG8tUGVlcg0Kc3RyZWFtaW5nIGFwcGxpY2F0aW9u cyBvbiB0aGUgSW50ZXJuZXQuID9XZSBmb2N1cyBvbiB0aGUNCkFyY2hpdGVjdHVyZSBhbmQgUGVl ciBQcm90b2NvbC9UcmFja2VyIFNpZ25hbGluZyBQcm90b2NvbA0KZGVzY3JpcHRpb24gaW4gdGhl IHByZXNlbnRhdGlvbiwgYW5kIHN0dWR5IGEgc2VsZWN0aW9uIG9mDQp3ZWxsLWtub3duIFAyUCBz dHJlYW1pbmcgc3lzdGVtcywgaW5jbHVkaW5nIEpvb3N0LCBQUGxpdmUsDQphbmQgbW9yZS4gP1Ro cm91Z2ggdGhlIHN1cnZleSwgd2Ugc3VtbWFyaXplIGEgY29tbW9uIFAyUA0Kc3RyZWFtaW5nIHBy b2Nlc3MgbW9kZWwgYW5kIHRoZSBjb3JyZXNwb25kZW50IHNpZ25hbGluZw0KcHJvY2VzcyBmb3Ig UDJQIFN0cmVhbWluZyBQcm90b2NvbCBzdGFuZGFyZGl6YXRpb24uDQoNClRoZSBVUkwgZm9yIHRo aXMgZHJhZnQgaXM6DQpodHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWd1LXBwc3Atc3VydmV5 LTAwLnR4dA0KDQpXZSBhcHByZWNpYXRlIHlvdXIgY29tbWVudHMuDQpUaGFua3MuDQoNClJlZ2Fy ZHMNCg0KWWluZ2ppZSBHdQ0KDQoNCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fDQpwcHNwIG1haWxpbmcgbGlzdA0KcHBzcEBpZXRmLm9yZw0KaHR0cHM6Ly93 d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9wcHNwDQoNCg0KDQoNCi0tIA0KTWluaCBOZ3V5 ZW4NCiszMyA2IDY1IDc2IDQ0IDYwDQoNCg0KDQoNCg0KLS0gDQpNaW5oIE5ndXllbg0KKzMzIDYg NjUgNzYgNDQgNjANCg== --=====003_Dragon756512547582_===== Content-Transfer-Encoding: base64 Content-Type: text/html; charset="gb2312" PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w MC4yOTAwLjM0OTIiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPg0KPCEtLQ0KIC8qIEZvbnQgRGVm aW5pdGlvbnMgKi8NCiBAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OsvOzOU7DQoJcGFub3NlLTE6 MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OlZlcmRhbmE7 DQoJcGFub3NlLTE6MiAxMSA2IDQgMyA1IDQgNCAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZh bWlseToiXEDLzszlIjsNCglwYW5vc2UtMToyIDEgNiAwIDMgMSAxIDEgMSAxO30NCiAvKiBTdHls ZSBEZWZpbml0aW9ucyAqLw0KIHAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3Jt YWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJdGV4dC1hbGlnbjpq dXN0aWZ5Ow0KCXRleHQtanVzdGlmeTppbnRlci1pZGVvZ3JhcGg7DQoJZm9udC1zaXplOjEwLjVw dDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjt9DQphOmxpbmssIHNwYW4uTXNvSHlw ZXJsaW5rDQoJe2NvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7Y29sb3I6cHVycGxlOw0KCXRleHQt ZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5 cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseTpWZXJkYW5hOw0KCWNvbG9yOndpbmRv d3RleHQ7DQoJZm9udC13ZWlnaHQ6bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsOw0KCXRleHQt ZGVjb3JhdGlvbjpub25lIG5vbmU7fQ0KIC8qIFBhZ2UgRGVmaW5pdGlvbnMgKi8NCiBAcGFnZSBT ZWN0aW9uMQ0KCXtzaXplOjU5NS4zcHQgODQxLjlwdDsNCgltYXJnaW46NzIuMHB0IDkwLjBwdCA3 Mi4wcHQgOTAuMHB0Ow0KCWxheW91dC1ncmlkOjE1LjZwdDt9DQpkaXYuU2VjdGlvbjENCgl7cGFn ZTpTZWN0aW9uMTt9DQotLT4NCjwvU1RZTEU+DQo8L0hFQUQ+DQo8Qk9EWT4NCjxESVY+PEZPTlQg ZmFjZT1WZXJkYW5hIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPkdvb2QgcG9pbnQhV2UgaGF2ZSBhIFBQ U1AgDQpyZXF1aXJlbWVudCBkcmFmdCB0byBlbnVtZXJhdGUgdGhlIHdoYXQgZmFjdG9ycyBQUFNQ IHByb3RvY29scyBuZWVkIHRvIA0KYWRkcmVzcy5UaGUgbmV3IHZlcnNpb24gb2YgdGhlIGRyYWZ0 IHdpbGwgY29tZSBvdXQgc29vbi5Zb3UgbWF5IHJlZmVyIHRvIGl0IGFuZCANCmNvbnRyaWJ1dGUg aW4gdGhpcyBkcmFmdCBhYm91dCB5b3VyIGNvbmNlcm5zLjwvRk9OVD48L0RJVj4NCjxESVY+PEZP TlQgZmFjZT1WZXJkYW5hIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4N CjxESVY+PEZPTlQgZmFjZT1WZXJkYW5hIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPkJSPC9GT05UPjwv RElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmEgY29sb3I9IzAwMDBmZiBzaXplPTI+WXVuZmVp PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmEgc2l6ZT0yPjwvRk9OVD4mbmJz cDs8L0RJVj4NCjxESVYgYWxpZ249bGVmdD4NCjxESVYgYWxpZ249bGVmdD48Rk9OVCBmYWNlPVZl cmRhbmEgc2l6ZT0yPg0KPEhSIHN0eWxlPSJXSURUSDogMTIycHg7IEhFSUdIVDogMnB4IiBTSVpF PTI+DQo8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGNvbG9yPSNjMGMwYzA+PEZPTlQgZmFjZT1W ZXJkYW5hIHNpemU9Mj56aGFuZ3l1bmZlaTwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1W ZXJkYW5hIHNpemU9Mj4yMDA5LTEwLTIwPC9GT05UPjwvRk9OVD48L0RJVj48L0RJVj4NCjxESVY+ PEZPTlQgZmFjZT1WZXJkYW5hIHNpemU9Mj4NCjxIUj4NCjwvRk9OVD48L0RJVj4NCjxESVY+PEZP TlQgZmFjZT1WZXJkYW5hPjxGT05UIHNpemU9Mj48U1RST05HPreivP7Iy6O6PC9TVFJPTkc+IE1p bmggDQpOZ3V5ZW48L0ZPTlQ+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmE+ PEZPTlQgc2l6ZT0yPjxTVFJPTkc+t6LLzcqxvOSjujwvU1RST05HPiANCjIwMDktMTAtMjAmbmJz cDsxOTowNTozNTwvRk9OVD48L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9VmVyZGFuYT48 Rk9OVCBzaXplPTI+PFNUUk9ORz7K1bz+yMujujwvU1RST05HPiANCnpoYW5neXVuZmVpPC9GT05U PjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1WZXJkYW5hPjxGT05UIHNpemU9Mj48U1RS T05HPrOty82jujwvU1RST05HPiBZLkouIEd1OyANCnBwc3BAaWV0Zi5vcmc8L0ZPTlQ+PC9GT05U PjwvRElWPg0KPERJVj48Rk9OVCBmYWNlPVZlcmRhbmE+PEZPTlQgc2l6ZT0yPjxTVFJPTkc+1vfM 4qO6PC9TVFJPTkc+IFJlOiBSZTogW3Bwc3BdIERyYWZ0IA0KZm9yIFBQU1AgU3VydmV5PC9GT05U PjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgZmFjZT1WZXJkYW5hIHNpemU9Mj48L0ZPTlQ+Jm5i c3A7PC9ESVY+DQo8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBzaXplPTI+PFNQQU4gc3R5bGU9IkNP TE9SOiByZ2IoMCwwLDE1MykiPkhpIA0KWXVuZmVpLDwvU1BBTj48QlIgc3R5bGU9IkNPTE9SOiBy Z2IoMCwwLDE1MykiPjxTUEFOIA0Kc3R5bGU9IkNPTE9SOiByZ2IoMCwwLDE1MykiPkkgaGF2ZSBq dXN0IHN0YXJ0ZWQgdGhlIHdvcmtzIGZvciBQMlAgdmlkZW8gDQpzdHJlYW1pbmcgb3ZlciBBZCBo b2MgbmV0d29ya3MgaW4gd2hpY2ggUDJQIHN0cmVhbWluZyBuZWVkIHRvIGJlIG9wZXJhdGVkIA0K ZWZmaWNpZW50bHkgb24gdG9wIG9mIE9MU1IgYWQgaG9jIHJvdXRpbmcgbGF5ZXIuPC9TUEFOPjxC Uj48QlIgDQpzdHlsZT0iQ09MT1I6IHJnYigwLDAsMTUzKSI+PFNQQU4gc3R5bGU9IkNPTE9SOiBy Z2IoMCwwLDE1MykiPkFzIEkgaGF2ZSBzZWVuIA0KUFBTUCB3b3VsZCBiZSBJRVRGJ3Mgc3RhbmRh cmQgcHJvdG9jb2wgZm9yIFAyUCBzdHJlYW1pbmcsIEl0IHdhcyBhIGdvb2QgY2hvaWNlIA0KaWYg UFBTUCBjb3VsZCBiZSBhZGFwdGVkIGZvciBBZCBob2MvTWVzaCBuZXR3b3JrcyBhY2NvcmRpbmds eS48L1NQQU4+PEJSIA0Kc3R5bGU9IkNPTE9SOiByZ2IoMCwwLDE1MykiPjxTUEFOIHN0eWxlPSJD T0xPUjogcmdiKDAsMCwxNTMpIj5EbyB5b3UgaGF2ZSBhbnkgDQpyZWNvbW1lbmQgZm9yIHRoYXQ/ IGZvciBleGFtcGxlLCBpcyBpdCBwb3NzaWJsZSB0byBleHRlbmQgb3IgYWRhcHQgUFBTUCANCmFj Y29yZGluZyB0byB0aGUgbmV0d29yayBlbnZpcm9ubWVudD88L1NQQU4+PEJSIHN0eWxlPSJDT0xP UjogcmdiKDAsMCwxNTMpIj48QlIgDQpzdHlsZT0iQ09MT1I6IHJnYigwLDAsMTUzKSI+PFNQQU4g c3R5bGU9IkNPTE9SOiByZ2IoMCwwLDE1MykiPlRoYW5rcyw8L1NQQU4+PEJSIA0Kc3R5bGU9IkNP TE9SOiByZ2IoMCwwLDE1MykiPjxTUEFOIA0Kc3R5bGU9IkNPTE9SOiByZ2IoMCwwLDE1MykiPk1p bmg8L1NQQU4+PEJSPjxCUj4NCjxESVYgY2xhc3M9Z21haWxfcXVvdGU+MjAwOS8xMC8yMCB6aGFu Z3l1bmZlaSA8U1BBTiBkaXI9bHRyPiZsdDs8QSANCmhyZWY9Im1haWx0bzp6aGFuZ3l1bmZlaUBj aGluYW1vYmlsZS5jb20iPnpoYW5neXVuZmVpQGNoaW5hbW9iaWxlLmNvbTwvQT4mZ3Q7PC9TUEFO PjxCUj4NCjxCTE9DS1FVT1RFIGNsYXNzPWdtYWlsX3F1b3RlIA0Kc3R5bGU9IlBBRERJTkctTEVG VDogMWV4OyBNQVJHSU46IDBwdCAwcHQgMHB0IDAuOGV4OyBCT1JERVItTEVGVDogcmdiKDIwNCwy MDQsMjA0KSAxcHggc29saWQiPg0KICA8RElWPg0KICA8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBj b2xvcj0jMDAwMGZmIHNpemU9Mj5IaSBNaW5oo6w8L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQg ZmFjZT1WZXJkYW5hIGNvbG9yPSMwMDAwZmYgc2l6ZT0yPj9QUFNQP2lzIGludGVuZGVkIHRvIHN1 cHBvcnQgDQogIGJvdGg/ZW52aXJubWVudHMsIGluY2x1ZGluZyB0aGUgd2lyZWxlc3MgYWQgaG9j IG5ldHdvcmsuSG93ZXZlciB0aGVyZSBpc24ndCANCiAgbXVjaCBsYXJnZSBzY2FsZSBQUFNQIHBy YWN0aWNlIGluIGFkIGhvYyBuZXR3b3JrcyB0byB0aGUgYmVzdCBvZiBvdXIgDQogIGtub3dsZWRn ZS5JZiB5b3UgaGF2ZSBzdWNoIGluZm9ybWF0aW9uLCB3ZWxjb21lIHRvIGNvbnRyaWJ1dGUgaXQu PC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBjb2xvcj0jMDAwMGZmIHNp emU9Mj48L0ZPTlQ+PzwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9VmVyZGFuYSBjb2xvcj0jMDAw MGZmIHNpemU9Mj5UaGFua3MsPC9GT05UPjwvRElWPg0KICA8RElWPjxGT05UIGZhY2U9VmVyZGFu YSBjb2xvcj0jMDAwMGZmIHNpemU9Mj5ZdW5mZWk8L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQg ZmFjZT1WZXJkYW5hIHNpemU9Mj48L0ZPTlQ+PzwvRElWPg0KICA8RElWIGFsaWduPWxlZnQ+DQog IDxESVYgYWxpZ249bGVmdD48Rk9OVCBmYWNlPVZlcmRhbmEgc2l6ZT0yPg0KICA8SFIgc3R5bGU9 Ik1JTi1IRUlHSFQ6IDJweDsgV0lEVEg6IDEyMnB4IiBTSVpFPTI+DQogIDwvRk9OVD48L0RJVj4N CiAgPERJVj48Rk9OVCBjb2xvcj0jYzBjMGMwPjxGT05UIGZhY2U9VmVyZGFuYSANCiAgc2l6ZT0y PnpoYW5neXVuZmVpPC9GT05UPjwvRk9OVD48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPVZlcmRh bmEgc2l6ZT0yPjIwMDktMTAtMjA8L0ZPTlQ+PC9ESVY+PC9ESVY+DQogIDxESVY+PEZPTlQgZmFj ZT1WZXJkYW5hIHNpemU9Mj4NCiAgPEhSPg0KICA8L0ZPTlQ+PC9ESVY+DQogIDxESVY+PEZPTlQg ZmFjZT1WZXJkYW5hPjxGT05UIHNpemU9Mj48Qj63orz+yMujujwvQj4gTWluaCANCiAgTmd1eWVu PC9GT05UPjwvRk9OVD48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPVZlcmRhbmE+PEZPTlQgc2l6 ZT0yPjxCPreiy83Ksbzko7o8L0I+IA0KICAyMDA5LTEwLTIwPzE3OjQ4OjE1PC9GT05UPjwvRk9O VD48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPVZlcmRhbmE+PEZPTlQgc2l6ZT0yPjxCPsrVvP7I y6O6PC9CPiBZLkouIEd1PC9GT05UPjwvRk9OVD48L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPVZl cmRhbmE+PEZPTlQgc2l6ZT0yPjxCPrOty82jujwvQj4gPEEgaHJlZj0ibWFpbHRvOnBwc3BAaWV0 Zi5vcmciIA0KICB0YXJnZXQ9X2JsYW5rPnBwc3BAaWV0Zi5vcmc8L0E+PC9GT05UPjwvRk9OVD48 L0RJVj4NCiAgPERJVj48Rk9OVCBmYWNlPVZlcmRhbmE+PEZPTlQgc2l6ZT0yPjxCPtb3zOKjujwv Qj4gUmU6IFtwcHNwXSBEcmFmdCBmb3IgUFBTUCANCiAgU3VydmV5PC9GT05UPjwvRk9OVD48L0RJ Vj4NCiAgPERJVj4NCiAgPERJVj48L0RJVj4NCiAgPERJViBjbGFzcz1oNT4NCiAgPERJVj48Rk9O VCBmYWNlPVZlcmRhbmEgc2l6ZT0yPjwvRk9OVD4/PC9ESVY+DQogIDxESVY+PEZPTlQgZmFjZT1W ZXJkYW5hIHNpemU9Mj5EZWFyIGFsbCw8QlI+SSB3b25kZXIgdGhhdCBkb2VzIFBQU1Agd29yayBm b3IgDQogIG5vdCBvbmx5IEludGVybmV0IGJ1dCBhbHNvIFdpcmVsZXNzIEFkIGhvYyBuZXR3b3Jr cy48QlI+SWYgaXQncyBub3QgdGhlIGNhc2UsIA0KICBkb2VzIGFueW9uZSB3b3JrIG9uIFBQU1Ag YW5kIEFkIGhvYyBuZXR3b3Jrcz88QlI+RG9lcyBhbnlvbmUgaGF2ZSB0aGUgDQogIHN1Z2dlc3Rp b25zIGluIHRoaXMgdG9waWM/PEJSPjxCUj5UaGFua3MsPEJSPi1NaW5oPEJSPjxCUj4NCiAgPERJ ViBjbGFzcz1nbWFpbF9xdW90ZT5PbiBUdWUsIE9jdCAyMCwgMjAwOSBhdCA0OjU0IEFNLCBZLkou IEd1IDxTUEFOIA0KICBkaXI9bHRyPiZsdDs8QSBocmVmPSJtYWlsdG86Z3V5aW5namllQGh1YXdl aS5jb20iIA0KICB0YXJnZXQ9X2JsYW5rPmd1eWluZ2ppZUBodWF3ZWkuY29tPC9BPiZndDs8L1NQ QU4+IHdyb3RlOjxCUj4NCiAgPEJMT0NLUVVPVEUgY2xhc3M9Z21haWxfcXVvdGUgDQogIHN0eWxl PSJQQURESU5HLUxFRlQ6IDFleDsgTUFSR0lOOiAwcHQgMHB0IDBwdCAwLjhleDsgQk9SREVSLUxF RlQ6IHJnYigyMDQsMjA0LDIwNCkgMXB4IHNvbGlkIj5IaSANCiAgICBldmVyeW9uZSw8QlI+V2Ug c3VibWl0dGVkIGEgc3VydmV5IGRyYWZ0IGZvciBwcHNwLjxCUj48QlI+QWJzdHJhY3Q6PEJSPlRo aXMgDQogICAgZG9jdW1lbnQgcHJlc2VudHMgYSBzdXJ2ZXkgb2YgcG9wdWxhciBQZWVyLXRvLVBl ZXI8QlI+c3RyZWFtaW5nIGFwcGxpY2F0aW9ucyANCiAgICBvbiB0aGUgSW50ZXJuZXQuID9XZSBm b2N1cyBvbiB0aGU8QlI+QXJjaGl0ZWN0dXJlIGFuZCBQZWVyIFByb3RvY29sL1RyYWNrZXIgDQog ICAgU2lnbmFsaW5nIFByb3RvY29sPEJSPmRlc2NyaXB0aW9uIGluIHRoZSBwcmVzZW50YXRpb24s IGFuZCBzdHVkeSBhIHNlbGVjdGlvbiANCiAgICBvZjxCUj53ZWxsLWtub3duIFAyUCBzdHJlYW1p bmcgc3lzdGVtcywgaW5jbHVkaW5nIEpvb3N0LCBQUGxpdmUsPEJSPmFuZCANCiAgICBtb3JlLiA/ VGhyb3VnaCB0aGUgc3VydmV5LCB3ZSBzdW1tYXJpemUgYSBjb21tb24gUDJQPEJSPnN0cmVhbWlu ZyBwcm9jZXNzIA0KICAgIG1vZGVsIGFuZCB0aGUgY29ycmVzcG9uZGVudCBzaWduYWxpbmc8QlI+ cHJvY2VzcyBmb3IgUDJQIFN0cmVhbWluZyBQcm90b2NvbCANCiAgICBzdGFuZGFyZGl6YXRpb24u PEJSPjxCUj5UaGUgVVJMIGZvciB0aGlzIGRyYWZ0IGlzOjxCUj48QSANCiAgICBocmVmPSJodHRw Oi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWd1LXBwc3Atc3VydmV5LTAwLnR4dCIgDQogICAgdGFy Z2V0PV9ibGFuaz5odHRwOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWd1LXBwc3Atc3VydmV5LTAw LnR4dDwvQT48QlI+PEJSPldlIA0KICAgIGFwcHJlY2lhdGUgeW91ciBjb21tZW50cy48QlI+VGhh bmtzLjxCUj48QlI+UmVnYXJkczxCUj48QlI+WWluZ2ppZSANCiAgICBHdTxCUj48QlI+PEJSPl9f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fPEJSPnBwc3AgDQog ICAgbWFpbGluZyBsaXN0PEJSPjxBIGhyZWY9Im1haWx0bzpwcHNwQGlldGYub3JnIiANCiAgICB0 YXJnZXQ9X2JsYW5rPnBwc3BAaWV0Zi5vcmc8L0E+PEJSPjxBIA0KICAgIGhyZWY9Imh0dHBzOi8v d3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcHBzcCIgDQogICAgdGFyZ2V0PV9ibGFuaz5o dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3Bwc3A8L0E+PEJSPjwvQkxPQ0tR VU9URT48L0RJVj48QlI+PEJSIA0KICBjbGVhcj1hbGw+PEJSPi0tIDxCUj5NaW5oIE5ndXllbjxC Uj4rMzMgNiA2NSA3NiA0NCANCiAgNjA8QlI+PEJSPjwvRk9OVD48L0RJVj48L0RJVj48L0RJVj48 L0RJVj48L0JMT0NLUVVPVEU+PC9ESVY+PEJSPjxCUiANCmNsZWFyPWFsbD48QlI+LS0gPEJSPk1p bmggTmd1eWVuPEJSPiszMyA2IDY1IDc2IDQ0IA0KNjA8QlI+PEJSPjwvRk9OVD48L0RJVj48L0JP RFk+PC9IVE1MPg0K --=====003_Dragon756512547582_=====-- From li.lichun1@zte.com.cn Tue Oct 20 18:17:25 2009 Return-Path: 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 DA95B3A690E; Tue, 20 Oct 2009 18:17:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -97.476 X-Spam-Level: X-Spam-Status: No, score=-97.476 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HTML_MESSAGE=0.001, MISSING_SUBJECT=1.762, RCVD_DOUBLE_IP_LOOSE=0.76, 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 xAQC8v9Gzvaw; Tue, 20 Oct 2009 18:17:24 -0700 (PDT) Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 468733A689B; Tue, 20 Oct 2009 18:17:21 -0700 (PDT) Received: from [10.30.17.101] by mx5.zte.com.cn with surfront esmtp id 111641821921442; Wed, 21 Oct 2009 08:51:32 +0800 (CST) Received: from [10.30.3.19] by [10.30.17.101] with StormMail ESMTP id 21209.1892867178; Wed, 21 Oct 2009 09:02:13 +0800 (CST) Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id n9L1HUo0021709; Wed, 21 Oct 2009 09:17:30 +0800 (CST) (envelope-from li.lichun1@zte.com.cn) To: enrico.marocco@telecomitalia.it MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007 Message-ID: From: li.lichun1@zte.com.cn Date: Wed, 21 Oct 2009 09:17:14 +0800 X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-10-21 09:17:29, Serialize complete at 2009-10-21 09:17:29 Content-Type: multipart/alternative; boundary="=_alternative 000765F348257656_=" X-MAIL: mse2.zte.com.cn n9L1HUo0021709 Cc: ppsp@ietf.org, ppsp-bounces@ietf.org Subject: [ppsp] (no subject) X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2009 01:17:26 -0000 This is a multipart message in MIME format. --=_alternative 000765F348257656_= Content-Type: text/plain; charset="US-ASCII" Indeed, TIVs should be addressed in routing layer. However, solving the problem in routing layer may involve things like changing routing protocol and replacing routers, which will pay some time and high price. In contrary, relay is an easier solution for applications sensitive to delay, and is already used somewhere. Relay can cause layer violation. Operators may not like it. But operator's participating in relay selection may reduce the harm of layer violation. Just my two cents. On Mon, Oct 12, 2009 at 8:38 PM, Enrico Marocco wrote: > Sebastian Kiesel wrote: >>> Numerous studies have reported the existence of triangle inequality >>> violations (TIV) in the Internet delay space??for about10%-30%??. It has >>> been proved to be a stable phenomenon in the Internet, and it is due >>> to the flaw of IP routing protocol. Since it is impossible to modify >>> the existing IP protocol, using QoS relay will be a complement to IP >>> routing. >> >> Do you have more information (e.g., references to papers/studies) about >> the true reasons for TIV? Are they due to >> >> 1) Non-technical, deliberate decisions of the network operators (e.g., >> no business case for upgrading a line)? >> >> 2) Technical limitations of the IP routing protocols (BGP, OSPF, etc.)? >> >> 3) Technical limitations of the IP protocol itself (IPv4)? >> >> or ... >> >> Maybe also some people working for an operator can comment on this? > > As far as I can tell, TIVs are intrinsically related to the very nature > of the Internet -- path asymmetry, route load balancing and so on -- and > at the end of they could be hardly considered a problem. However, > problem or non-problem, they entirely belong to the routing layer and > addressing them at the application level makes to me for a perfect > example of layer violation. > > -- > Ciao, > Enrico > > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto > > -- Sincerely yours, Lichun Li ZTE Corporation -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system. --=_alternative 000765F348257656_= Content-Type: text/html; charset="US-ASCII"
Indeed, TIVs should be addressed in routing layer. However, solving the problem in routing layer may involve things like changing routing protocol and replacing routers, which will pay some time and high price. In contrary, relay is an easier solution for applications sensitive to delay, and is already used somewhere.

Relay can cause layer violation. Operators may not like it. But operator's participating in relay selection may reduce the harm of layer violation.

Just my two cents.

On Mon, Oct 12, 2009 at 8:38 PM, Enrico Marocco
<enrico.marocco@telecomitalia.it> wrote:
> Sebastian Kiesel wrote:
>>> Numerous studies have reported the existence of triangle inequality
>>> violations (TIV) in the Internet delay space??for about10%-30%??. It has
>>> been proved to be a stable phenomenon in the Internet, and it is due
>>> to the flaw of IP routing protocol. Since it is impossible to modify
>>> the existing IP protocol, using QoS relay will be a complement to IP
>>> routing.
>>
>> Do you have more information (e.g., references to papers/studies) about
>> the true reasons for TIV? Are they due to
>>
>> 1) Non-technical, deliberate decisions of the network operators (e.g.,
>>    no business case for upgrading a line)?
>>
>> 2) Technical limitations of the IP routing protocols (BGP, OSPF, etc.)?
>>
>> 3) Technical limitations of the IP protocol itself (IPv4)?
>>
>> or ...
>>
>> Maybe also some people working for an operator can comment on this?
>
> As far as I can tell, TIVs are intrinsically related to the very nature
> of the Internet -- path asymmetry, route load balancing and so on -- and
> at the end of they could be hardly considered a problem. However,
> problem or non-problem, they entirely belong to the routing layer and
> addressing them at the application level makes to me for a perfect
> example of layer violation.
>
> --
> Ciao,
> Enrico
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>



--
Sincerely yours,

Lichun Li
ZTE Corporation


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
--=_alternative 000765F348257656_=-- From zongning@huawei.com Tue Oct 20 18:18:36 2009 Return-Path: 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 1DD9B3A688F for ; Tue, 20 Oct 2009 18:18:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.894 X-Spam-Level: X-Spam-Status: No, score=-99.894 tagged_above=-999 required=5 tests=[AWL=-2.188, BAYES_00=-2.599, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1, 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 bzZ6lHdc8-d1 for ; Tue, 20 Oct 2009 18:18:35 -0700 (PDT) Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id D184F3A67AF for ; Tue, 20 Oct 2009 18:18:34 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRU00GS6BMW1K@szxga04-in.huawei.com> for ppsp@ietf.org; Wed, 21 Oct 2009 09:18:32 +0800 (CST) Received: from huawei.com ([172.17.1.36]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRU009J8BMWJV@szxga04-in.huawei.com> for ppsp@ietf.org; Wed, 21 Oct 2009 09:18:32 +0800 (CST) Received: from [172.24.1.33] (Forwarded-For: [10.164.12.27]) by szxmc04-in.huawei.com (mshttpd); Wed, 21 Oct 2009 09:18:32 +0800 Date: Wed, 21 Oct 2009 09:18:32 +0800 From: zongning 63316 In-reply-to: <66dcf31f0910200400od867e43ld5692582c9d1904f@mail.gmail.com> To: Minh Nguyen Message-id: MIME-version: 1.0 X-Mailer: iPlanet Messenger Express 5.2 HotFix 2.14 (built Aug 8 2006) Content-type: text/plain; charset=gb2312 Content-language: zh-CN Content-transfer-encoding: quoted-printable Content-disposition: inline X-Accept-Language: zh-CN Priority: normal References: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com> <002301ca5130$b1d07830$400ca40a@china.huawei.com> <66dcf31f0910200243x33166aebi68322337672df234@mail.gmail.com> <200910201748166253822@chinamobile.com> <66dcf31f0910200400od867e43ld5692582c9d1904f@mail.gmail.com> Cc: "ppsp@ietf.org" Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2009 01:18:36 -0000 Hi=2C Minh Thank you for offering new use cases of PPSP=2E I think the design of PPS= P protocols including basic functionalities and message encoding will be = flexible and extensible enough to adopt as many P2P streaming application= s as possible=2E Just like RTP=2C we have seen many RTP extensions to eme= rgent new Audio/Video codecs=2E So any type of P2P streaming applications are ecouraged to be discussed i= n mailing list and we will see how much we can incorporate into PPSP desi= gn=2E BR=2C Ning Zong ----- =D4=AD=D3=CA=BC=FE ----- =B7=A2=BC=FE=C8=CB=3A Minh Nguyen =3Cskminh=40gmail=2Ecom=3E =C8=D5=C6=DA=3A =D0=C7=C6=DA=B6=FE=2C =CA=AE=D4=C2 20=C8=D5=2C 2009 =CF=C2= =CE=E77=3A02 =D6=F7=CC=E2=3A Re=3A =5Bppsp=5D Draft for PPSP Survey =CA=D5=BC=FE=C8=CB=3A zhangyunfei =3Czhangyunfei=40chinamobile=2Ecom=3E =B3=AD=CB=CD=3A =22ppsp=40ietf=2Eorg=22 =3Cppsp=40ietf=2Eorg=3E =3E Hi Yunfei=2C =3E I have just started the works for P2P video streaming over Ad hoc = =3E networksin which P2P streaming need to be operated efficiently on = =3E top of OLSR ad hoc =3E routing layer=2E =3E = =3E As I have seen PPSP would be IETF=27s standard protocol for P2P = =3E streaming=2C It =3E was a good choice if PPSP could be adapted for Ad hoc/Mesh networks =3E accordingly=2E =3E Do you have any recommend for that=3F for example=2C is it possible t= o = =3E extend or =3E adapt PPSP according to the network environment=3F =3E = =3E Thanks=2C =3E Minh =3E = =3E 2009/10/20 zhangyunfei =3Czhangyunfei=40chinamobile=2Ecom=3E =3E = =3E =3E Hi Minh=A3=AC =3E =3E PPSP is intended to support both envirnments=2C including the = =3E wireless ad =3E =3E hoc network=2EHowever there isn=27t much large scale PPSP practic= e = =3E in ad hoc =3E =3E networks to the best of our knowledge=2EIf you have such = =3E information=2C welcome =3E =3E to contribute it=2E =3E =3E =3E =3E Thanks=2C =3E =3E Yunfei =3E =3E =3E =3E ------------------------------ =3E =3E zhangyunfei =3E =3E 2009-10-20 =3E =3E ------------------------------ =3E =3E *=B7=A2=BC=FE=C8=CB=A3=BA* Minh Nguyen =3E =3E *=B7=A2=CB=CD=CA=B1=BC=E4=A3=BA* 2009-10-20 17=3A48=3A15 =3E =3E *=CA=D5=BC=FE=C8=CB=A3=BA* Y=2EJ=2E Gu =3E =3E *=B3=AD=CB=CD=A3=BA* ppsp=40ietf=2Eorg =3E =3E *=D6=F7=CC=E2=A3=BA* Re=3A =5Bppsp=5D Draft for PPSP Survey =3E =3E =3E =3E Dear all=2C =3E =3E I wonder that does PPSP work for not only Internet but also = =3E Wireless Ad hoc =3E =3E networks=2E =3E =3E If it=27s not the case=2C does anyone work on PPSP and Ad hoc net= works=3F =3E =3E Does anyone have the suggestions in this topic=3F =3E =3E =3E =3E Thanks=2C =3E =3E -Minh =3E =3E =3E =3E On Tue=2C Oct 20=2C 2009 at 4=3A54 AM=2C Y=2EJ=2E Gu =3Cguyingjie= =40huawei=2Ecom=3E = =3E wrote=3A=3E =3E =3E=3E Hi everyone=2C =3E =3E=3E We submitted a survey draft for ppsp=2E =3E =3E=3E =3E =3E=3E Abstract=3A =3E =3E=3E This document presents a survey of popular Peer-to-Peer =3E =3E=3E streaming applications on the Internet=2E =3FWe focus on the =3E =3E=3E Architecture and Peer Protocol/Tracker Signaling Protocol =3E =3E=3E description in the presentation=2C and study a selection of =3E =3E=3E well-known P2P streaming systems=2C including Joost=2C PPlive=2C= =3E =3E=3E and more=2E =3FThrough the survey=2C we summarize a common P2P= =3E =3E=3E streaming process model and the correspondent signaling =3E =3E=3E process for P2P Streaming Protocol standardization=2E =3E =3E=3E =3E =3E=3E The URL for this draft is=3A =3E =3E=3E http=3A//www=2Eietf=2Eorg/id/draft-gu-ppsp-survey-00=2Etxt =3E =3E=3E =3E =3E=3E We appreciate your comments=2E =3E =3E=3E Thanks=2E =3E =3E=3E =3E =3E=3E Regards =3E =3E=3E =3E =3E=3E Yingjie Gu =3E =3E=3E =3E =3E=3E =3E =3E=3E =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F =3E =3E=3E ppsp mailing list =3E =3E=3E ppsp=40ietf=2Eorg =3E =3E=3E https=3A//www=2Eietf=2Eorg/mailman/listinfo/ppsp =3E =3E=3E =3E =3E =3E =3E =3E =3E =3E =3E -- =3E =3E Minh Nguyen =3E =3E +33 6 65 76 44 60 =3E =3E =3E =3E =3E = =3E = =3E -- = =3E Minh Nguyen =3E +33 6 65 76 44 60 =3E From skminh@gmail.com Wed Oct 21 08:35:24 2009 Return-Path: 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 A9C1A3A6982 for ; Wed, 21 Oct 2009 08:35:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[AWL=-0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_BACKHAIR_52=1] 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 ik7vFpAAd2-N for ; Wed, 21 Oct 2009 08:35:23 -0700 (PDT) Received: from mail-gx0-f228.google.com (mail-gx0-f228.google.com [209.85.217.228]) by core3.amsl.com (Postfix) with ESMTP id E776128C0EB for ; Wed, 21 Oct 2009 08:35:22 -0700 (PDT) Received: by gxk28 with SMTP id 28so6067835gxk.9 for ; Wed, 21 Oct 2009 08:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=XOV1Lnu+CDoqWM2rrQGI9VwsDL0EYSP9qT/BlbfYJno=; b=jYjCgKn/n87bVHZmfmq7PfAH7zDxBzsNVbhhAFtfytZV25Z4iKH8imhrWFs535kkG4 evLTq+PeSTRPTJMV8REivOO/EnLUYn2SwMJfwEdwOW1c6Gt4W/dCmcxMKkWM+JMnF402 SvIw97FVfKxbHh67EpGruGeVz+kMdcFzWhibo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=cApyhXMLiOrcOAoeP3sdqpMdSOSBfstf7/ijp/SQF2B5nNoERrgyynFLb4zerDGXST uJDVFy4i20/AR7eGNatOCCcJXxifyiSyhOiIko2VNzu1jMq9wfuD1JIAd0YaGfJzIvFj eerwydoYsEJWyZteMjGlQbwqmmtobJKMItFJ0= MIME-Version: 1.0 Received: by 10.90.217.11 with SMTP id p11mr5887826agg.82.1256139327950; Wed, 21 Oct 2009 08:35:27 -0700 (PDT) In-Reply-To: References: <002201ca512f$8eee5fe0$400ca40a@china.huawei.com> <002301ca5130$b1d07830$400ca40a@china.huawei.com> <66dcf31f0910200243x33166aebi68322337672df234@mail.gmail.com> <200910201748166253822@chinamobile.com> <66dcf31f0910200400od867e43ld5692582c9d1904f@mail.gmail.com> Date: Wed, 21 Oct 2009 17:35:27 +0200 Message-ID: <66dcf31f0910210835u31b995c7y83fa4769359ecb6c@mail.gmail.com> From: Minh Nguyen To: zongning 63316 Content-Type: multipart/alternative; boundary=0016368324b26e4ea0047673ba3c Cc: "ppsp@ietf.org" , anh_minh.nguyen@telecom-sudparis.eu Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Oct 2009 15:35:24 -0000 --0016368324b26e4ea0047673ba3c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi All, To the best of my knowledge, one of the critical issues for multimedia transport through network diversity is to provide multipath transmission, especially wireless ad hoc networks. This is due in wireless networks, the high broken-link and interference make it is sensitive to delay, lost.. P2P streaming in this networks therefore need to use both multisource and multipath technique. RTP is a good example, it is started designing of single transmission from the beginning, but find it is then difficultly to use many single flows solely in the needs of using multipath. As the result, standard RTP has bee= n modified to non-standard MRTP, which is mentioned in this paperto support multi flow. Moreover, the usage of multipath in Internet can improve significantly the quality of streaming media in P2P overlay. I was not clear yet about PPSP transmission, and it seems that the requirement of PPSP transmission in the PPSP's draft is still in progress. = I think we can put the requirement of multipath transmission into this part as well. Hence, we can avoid the same problem which came from RTP protocol. BR, Minh 2009/10/21 zongning 63316 > Hi, Minh > > Thank you for offering new use cases of PPSP. I think the design of PPSP > protocols including basic functionalities and message encoding will be > flexible and extensible enough to adopt as many P2P streaming application= s > as possible. Just like RTP, we have seen many RTP extensions to emergent = new > Audio/Video codecs. > So any type of P2P streaming applications are ecouraged to be discussed i= n > mailing list and we will see how much we can incorporate into PPSP design= . > > BR, > Ning Zong > > ----- =E5=8E=9F=E9=82=AE=E4=BB=B6 ----- > =E5=8F=91=E4=BB=B6=E4=BA=BA: Minh Nguyen > =E6=97=A5=E6=9C=9F: =E6=98=9F=E6=9C=9F=E4=BA=8C, =E5=8D=81=E6=9C=88 20=E6= =97=A5, 2009 =E4=B8=8B=E5=8D=887:02 > =E4=B8=BB=E9=A2=98: Re: [ppsp] Draft for PPSP Survey > =E6=94=B6=E4=BB=B6=E4=BA=BA: zhangyunfei > =E6=8A=84=E9=80=81: "ppsp@ietf.org" > > > Hi Yunfei, > > I have just started the works for P2P video streaming over Ad hoc > > networksin which P2P streaming need to be operated efficiently on > > top of OLSR ad hoc > > routing layer. > > > > As I have seen PPSP would be IETF's standard protocol for P2P > > streaming, It > > was a good choice if PPSP could be adapted for Ad hoc/Mesh networks > > accordingly. > > Do you have any recommend for that? for example, is it possible to > > extend or > > adapt PPSP according to the network environment? > > > > Thanks, > > Minh > > > > 2009/10/20 zhangyunfei > > > > > Hi Minh=EF=BC=8C > > > PPSP is intended to support both envirnments, including the > > wireless ad > > > hoc network.However there isn't much large scale PPSP practice > > in ad hoc > > > networks to the best of our knowledge.If you have such > > information, welcome > > > to contribute it. > > > > > > Thanks, > > > Yunfei > > > > > > ------------------------------ > > > zhangyunfei > > > 2009-10-20 > > > ------------------------------ > > > *=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A* Minh Nguyen > > > *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A* 2009-10-20 17:48:15 > > > *=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A* Y.J. Gu > > > *=E6=8A=84=E9=80=81=EF=BC=9A* ppsp@ietf.org > > > *=E4=B8=BB=E9=A2=98=EF=BC=9A* Re: [ppsp] Draft for PPSP Survey > > > > > > Dear all, > > > I wonder that does PPSP work for not only Internet but also > > Wireless Ad hoc > > > networks. > > > If it's not the case, does anyone work on PPSP and Ad hoc networks? > > > Does anyone have the suggestions in this topic? > > > > > > Thanks, > > > -Minh > > > > > > On Tue, Oct 20, 2009 at 4:54 AM, Y.J. Gu > > wrote:> > > >> Hi everyone, > > >> We submitted a survey draft for ppsp. > > >> > > >> Abstract: > > >> This document presents a survey of popular Peer-to-Peer > > >> streaming applications on the Internet. ?We focus on the > > >> Architecture and Peer Protocol/Tracker Signaling Protocol > > >> description in the presentation, and study a selection of > > >> well-known P2P streaming systems, including Joost, PPlive, > > >> and more. ?Through the survey, we summarize a common P2P > > >> streaming process model and the correspondent signaling > > >> process for P2P Streaming Protocol standardization. > > >> > > >> The URL for this draft is: > > >> http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt > > >> > > >> We appreciate your comments. > > >> Thanks. > > >> > > >> Regards > > >> > > >> Yingjie Gu > > >> > > >> > > >> _______________________________________________ > > >> ppsp mailing list > > >> ppsp@ietf.org > > >> https://www.ietf.org/mailman/listinfo/ppsp > > >> > > > > > > > > > > > > -- > > > Minh Nguyen > > > +33 6 65 76 44 60 > > > > > > > > > > > > -- > > Minh Nguyen > > +33 6 65 76 44 60 > > > --=20 Minh Nguyen +33 6 65 76 44 60 --0016368324b26e4ea0047673ba3c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi All,
To the best of my kno= wledge, one of the critical issues for multimedia transport through network= diversity is to provide multipath transmission, especially wireless ad hoc= networks. This is due in wireless networks, the high broken-link and inter= ference make it is sensitive to delay, lost.. P2P streaming in this network= s therefore need to use both multisource and multipath technique. RTP is a good example, it is started= designing of single transmission from the beginning, but find it is then d= ifficultly to use many single flows solely in the needs of using multipath.= As the result, standard RTP has been modified to non-standard MRTP, which = is mentioned in this paper to support multi flow. Moreover, the usag= e of multipath in Internet can improve significantly the quality of streami= ng media in P2P overlay.
I was not clear yet about PPSP trans= mission, and it seems that the requirement of PPSP transmission in the PPSP= 's draft is still in progress. I think we can put the requirement of mu= ltipath transmission into this part=C2=A0 as well. Hence, we can avoid the = same problem which came from RTP protocol.

BR,
Minh


2009/10/21 zo= ngning 63316 <z= ongning@huawei.com>
Hi, Minh

Thank you for offering new use cases of PPSP. I think the design of PPSP pr= otocols including basic functionalities and message encoding will be flexib= le and extensible enough to adopt as many P2P streaming applications as pos= sible. Just like RTP, we have seen many RTP extensions to emergent new Audi= o/Video codecs.
So any type of P2P streaming applications are ecouraged to be discussed in = mailing list and we will see how much we can incorporate into PPSP design.<= br>
BR,
Ning Zong

----- =E5=8E=9F=E9=82=AE=E4=BB=B6 -----
=E5=8F=91=E4=BB=B6=E4=BA=BA: Minh Nguyen <skminh@gmail.com>
=E6=97=A5=E6=9C=9F: =E6=98=9F=E6=9C=9F=E4=BA=8C, =E5=8D=81=E6=9C=88 20=E6= =97=A5, 2009 =E4=B8=8B=E5=8D=887:02
=E4=B8=BB=E9=A2=98: Re: [ppsp] Draft for PPSP Survey
=E6=94=B6=E4=BB=B6=E4=BA=BA: zhangyunfei <zhangyunfei@chinamobile.com>
=E6=8A=84=E9=80=81: "ppsp@ietf.org" <ppsp@ietf.org>

> Hi Yunfei,
> I have just started the works for P2P video streaming over Ad hoc
> networksin which P2P streaming need to be operated efficiently o= n
> top of OLSR ad hoc
> routing layer.
>
> As I have seen PPSP would be IETF's standard protocol for P2P
> streaming, It
> was a good choice if PPSP could be adapted for Ad hoc/Mesh networks > accordingly.
> Do you have any recommend for that? for example, is it possible to
> extend or
> adapt PPSP according to the network environment?
>
> Thanks,
> Minh
>
> 2009/10/20 zhangyunfei <zhangyunfei@chinamobile.com>
>
> > =C2=A0Hi Minh=EF=BC=8C
> > =C2=A0PPSP is intended to support both envirnments, including the=
> wireless ad
> > hoc network.However there isn't much large scale PPSP practic= e
> in ad hoc
> > networks to the best of our knowledge.If you have such
> information, welcome
> > to contribute it.
> >
> > Thanks,
> > Yunfei
> >
> > =C2=A0------------------------------
> > =C2=A0zhangyunfei
> > 2009-10-20
> > =C2=A0------------------------------
> > =C2=A0*=E5=8F=91=E4=BB=B6=E4=BA=BA=EF=BC=9A* Minh Nguyen
> > *=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4=EF=BC=9A* 2009-10-20 17:48:= 15
> > *=E6=94=B6=E4=BB=B6=E4=BA=BA=EF=BC=9A* Y.J. Gu
> > *=E6=8A=84=E9=80=81=EF=BC=9A* pp= sp@ietf.org
> > *=E4=B8=BB=E9=A2=98=EF=BC=9A* Re: [ppsp] Draft for PPSP Survey > >
> > Dear all,
> > I wonder that does PPSP work for not only Internet but also
> Wireless Ad hoc
> > networks.
> > If it's not the case, does anyone work on PPSP and Ad hoc net= works?
> > Does anyone have the suggestions in this topic?
> >
> > Thanks,
> > -Minh
> >
> > On Tue, Oct 20, 2009 at 4:54 AM, Y.J. Gu <guyingjie@huawei.com>
> wrote:>
> >> Hi everyone,
> >> We submitted a survey draft for ppsp.
> >>
> >> Abstract:
> >> This document presents a survey of popular Peer-to-Peer
> >> streaming applications on the Internet. ?We focus on the
> >> Architecture and Peer Protocol/Tracker Signaling Protocol
> >> description in the presentation, and study a selection of
> >> well-known P2P streaming systems, including Joost, PPlive, > >> and more. ?Through the survey, we summarize a common P2P
> >> streaming process model and the correspondent signaling
> >> process for P2P Streaming Protocol standardization.
> >>
> >> The URL for this draft is:
> >> http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt<= br> > >>
> >> We appreciate your comments.
> >> Thanks.
> >>
> >> Regards
> >>
> >> Yingjie Gu
> >>
> >>
> >> _______________________________________________
> >> ppsp mailing list
> >> ppsp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ppsp
> >>
> >
> >
> >
> > --
> > Minh Nguyen
> > +33 6 65 76 44 60
> >
> >
>
>
> --
> Minh Nguyen
> +33 6 65 76 44 60
>



--
Minh Nguyen=
+33 6 65 76 44 60

--0016368324b26e4ea0047673ba3c-- From guyingjie@huawei.com Wed Oct 21 20:35:12 2009 Return-Path: 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 C53603A6781 for ; Wed, 21 Oct 2009 20:35:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.157 X-Spam-Level: X-Spam-Status: No, score=-0.157 tagged_above=-999 required=5 tests=[AWL=-0.348, BAYES_00=-2.599, CN_BODY_35=0.339, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45] 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 0f6kY4uyoh+s for ; Wed, 21 Oct 2009 20:35:11 -0700 (PDT) Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id C7CE03A6817 for ; Wed, 21 Oct 2009 20:35:10 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRW00BDOCJVN7@szxga04-in.huawei.com> for ppsp@ietf.org; Thu, 22 Oct 2009 11:33:31 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRW006XZCJVFD@szxga04-in.huawei.com> for ppsp@ietf.org; Thu, 22 Oct 2009 11:33:31 +0800 (CST) Received: from g00107907 ([10.164.12.64]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KRW00F7LCJU5W@szxml06-in.huawei.com> for ppsp@ietf.org; Thu, 22 Oct 2009 11:33:31 +0800 (CST) Date: Thu, 22 Oct 2009 11:33:29 +0800 From: "Y.J. Gu" In-reply-to: <66dcf31f0910210835u31b995c7y83fa4769359ecb6c@mail.gmail.com> To: 'Minh Nguyen' , 'zongning 63316' Message-id: <000701ca52c8$6c5fb970$400ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: multipart/alternative; boundary="Boundary_(ID_B21aVpFRsLC9qJZC36ZjNA)" Thread-index: AcpSZErhxaFJXqFaSzOg4dsdEy0NqQAYsyiw Cc: ppsp@ietf.org, anh_minh.nguyen@telecom-sudparis.eu Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2009 03:35:12 -0000 This is a multi-part message in MIME format. --Boundary_(ID_B21aVpFRsLC9qJZC36ZjNA) Content-type: text/plain; charset=gb2312 Content-transfer-encoding: quoted-printable Hi Minh, I'm interested in this topic too. Thank you very much for involving multipath transport. You said that multipath transmission is one of the critical issues for multimedia transport. Could you please disclose more specific = information on this topic? Is there any applications that using multipath transmission? = How they implement and what's the problem they met with? It will be a good instance for survey draft and we can extract specific requirements for = the requirement draft. =20 Thank you very much :) Regards Yingjie Gu =20 _____ =20 From: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] On Behalf Of = Minh Nguyen Sent: Wednesday, October 21, 2009 11:35 PM To: zongning 63316 Cc: ppsp@ietf.org; anh_minh.nguyen@telecom-sudparis.eu Subject: Re: [ppsp] Draft for PPSP Survey Hi All, To the best of my knowledge, one of the critical issues for multimedia transport through network diversity is to provide multipath = transmission, especially wireless ad hoc networks. This is due in wireless networks, = the high broken-link and interference make it is sensitive to delay, lost.. = P2P streaming in this networks therefore need to use both multisource and multipath technique. RTP is a good example, it is started designing of single transmission = from the beginning, but find it is then difficultly to use many single flows solely in the needs of using multipath. As the result, standard RTP has = been modified to non-standard MRTP, which is mentioned in this = paper to support multi flow. Moreover, the usage of multipath in Internet can = improve significantly the quality of streaming media in P2P overlay. I was not clear yet about PPSP transmission, and it seems that the requirement of PPSP transmission in the PPSP's draft is still in = progress. I think we can put the requirement of multipath transmission into this = part as well. Hence, we can avoid the same problem which came from RTP = protocol. BR, Minh 2009/10/21 zongning 63316 Hi, Minh Thank you for offering new use cases of PPSP. I think the design of PPSP protocols including basic functionalities and message encoding will be flexible and extensible enough to adopt as many P2P streaming = applications as possible. Just like RTP, we have seen many RTP extensions to emergent = new Audio/Video codecs. So any type of P2P streaming applications are ecouraged to be discussed = in mailing list and we will see how much we can incorporate into PPSP = design. BR, Ning Zong ----- =D4=AD=D3=CA=BC=FE ----- =B7=A2=BC=FE=C8=CB: Minh Nguyen =C8=D5=C6=DA: =D0=C7=C6=DA=B6=FE, =CA=AE=D4=C2 20=C8=D5, 2009 = =CF=C2=CE=E77:02 =D6=F7=CC=E2: Re: [ppsp] Draft for PPSP Survey =CA=D5=BC=FE=C8=CB: zhangyunfei =B3=AD=CB=CD: "ppsp@ietf.org" > Hi Yunfei, > I have just started the works for P2P video streaming over Ad hoc > networksin which P2P streaming need to be operated efficiently on > top of OLSR ad hoc > routing layer. > > As I have seen PPSP would be IETF's standard protocol for P2P > streaming, It > was a good choice if PPSP could be adapted for Ad hoc/Mesh networks > accordingly. > Do you have any recommend for that? for example, is it possible to > extend or > adapt PPSP according to the network environment? > > Thanks, > Minh > > 2009/10/20 zhangyunfei > > > Hi Minh=A3=AC > > PPSP is intended to support both envirnments, including the > wireless ad > > hoc network.However there isn't much large scale PPSP practice > in ad hoc > > networks to the best of our knowledge.If you have such > information, welcome > > to contribute it. > > > > Thanks, > > Yunfei > > > > ------------------------------ > > zhangyunfei > > 2009-10-20 > > ------------------------------ > > *=B7=A2=BC=FE=C8=CB=A3=BA* Minh Nguyen > > *=B7=A2=CB=CD=CA=B1=BC=E4=A3=BA* 2009-10-20 17:48:15 > > *=CA=D5=BC=FE=C8=CB=A3=BA* Y.J. Gu > > *=B3=AD=CB=CD=A3=BA* ppsp@ietf.org > > *=D6=F7=CC=E2=A3=BA* Re: [ppsp] Draft for PPSP Survey > > > > Dear all, > > I wonder that does PPSP work for not only Internet but also > Wireless Ad hoc > > networks. > > If it's not the case, does anyone work on PPSP and Ad hoc networks? > > Does anyone have the suggestions in this topic? > > > > Thanks, > > -Minh > > > > On Tue, Oct 20, 2009 at 4:54 AM, Y.J. Gu > wrote:> > >> Hi everyone, > >> We submitted a survey draft for ppsp. > >> > >> Abstract: > >> This document presents a survey of popular Peer-to-Peer > >> streaming applications on the Internet. ?We focus on the > >> Architecture and Peer Protocol/Tracker Signaling Protocol > >> description in the presentation, and study a selection of > >> well-known P2P streaming systems, including Joost, PPlive, > >> and more. ?Through the survey, we summarize a common P2P > >> streaming process model and the correspondent signaling > >> process for P2P Streaming Protocol standardization. > >> > >> The URL for this draft is: > >> http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt > >> > >> We appreciate your comments. > >> Thanks. > >> > >> Regards > >> > >> Yingjie Gu > >> > >> > >> _______________________________________________ > >> ppsp mailing list > >> ppsp@ietf.org > >> https://www.ietf.org/mailman/listinfo/ppsp > >> > > > > > > > > -- > > Minh Nguyen > > +33 6 65 76 44 60 > > > > > > > -- > Minh Nguyen > +33 6 65 76 44 60 > --=20 Minh Nguyen +33 6 65 76 44 60 --Boundary_(ID_B21aVpFRsLC9qJZC36ZjNA) Content-type: text/html; charset=gb2312 Content-transfer-encoding: quoted-printable
Hi Minh,
I'm interested in this topic too. Thank you very much for = involving=20 multipath transport.
You said that multipath transmission is one of the critical = issues for=20 multimedia transport. Could you please disclose more specific = information on=20 this topic? Is there any applications that using multipath transmission? = How=20 they implement and what's the problem they met with? It will be a good=20 instance for survey draft and we can extract specific = requirements for=20 the requirement draft.
 
Thank you very much :)

Regards

Yingjie Gu

 

From: ppsp-bounces@ietf.org=20 [mailto:ppsp-bounces@ietf.org] On Behalf Of Minh = Nguyen
Sent:=20 Wednesday, October 21, 2009 11:35 PM
To: zongning=20 63316
Cc: ppsp@ietf.org;=20 anh_minh.nguyen@telecom-sudparis.eu
Subject: Re: [ppsp] = Draft for=20 PPSP Survey

Hi All,To = the best of=20 my knowledge, one of the critical issues for multimedia transport = through=20 network diversity is to provide multipath transmission, especially = wireless ad=20 hoc networks. This is due in wireless networks, the high broken-link = and=20 interference make it is sensitive to delay, lost.. P2P streaming in = this=20 networks therefore need to use both multisource and multipath=20 technique.
RTP is a good example, it is started = designing of=20 single transmission from the beginning, but find it is then = difficultly to use=20 many single flows solely in the needs of using multipath. As the = result,=20 standard RTP has been modified to non-standard MRTP, which is = mentioned in this=20 paper to support multi flow. Moreover, the usage of multipath in = Internet=20 can improve significantly the quality of streaming media in P2P=20 overlay.
I was not clear yet about PPSP = transmission, and=20 it seems that the requirement of PPSP transmission in the PPSP's draft = is=20 still in progress. I think we can put the requirement of multipath=20 transmission into this part  as well. Hence, we can avoid the = same=20 problem which came from RTP protocol.
BR,
Minh


2009/10/21 zongning 63316 <zongning@huawei.com>
Hi,=20 Minh

Thank you for offering new use cases of PPSP. I think = the design=20 of PPSP protocols including basic functionalities and message = encoding will=20 be flexible and extensible enough to adopt as many P2P streaming=20 applications as possible. Just like RTP, we have seen many RTP = extensions to=20 emergent new Audio/Video codecs.
So any type of P2P streaming=20 applications are ecouraged to be discussed in mailing list and we = will see=20 how much we can incorporate into PPSP design.

BR,
Ning=20 Zong

----- =D4=AD=D3=CA=BC=FE -----
=B7=A2=BC=FE=C8=CB: = Minh Nguyen <skminh@gmail.com>
=C8=D5=C6=DA= : =D0=C7=C6=DA=B6=FE, =CA=AE=D4=C2 20=C8=D5,=20 2009 =CF=C2=CE=E77:02
=D6=F7=CC=E2: Re: [ppsp] Draft for PPSP = Survey
=CA=D5=BC=FE=C8=CB: zhangyunfei=20 <zhangyunfei@chinamobile.com>
=B3=AD=CB=CD:=20 "ppsp@ietf.org" <ppsp@ietf.org>

> Hi Yunfei,
> I have just started the = works for=20 P2P video streaming over Ad hoc
> networksin which P2P = streaming=20 need to be operated efficiently on
> top of OLSR ad hoc
> routing = layer.
>
>=20 As I have seen PPSP would be IETF's standard protocol for = P2P
>=20 streaming, It
> was a good choice if PPSP could be adapted for = Ad=20 hoc/Mesh networks
> accordingly.
> Do you have any = recommend for=20 that? for example, is it possible to
> extend or
> adapt = PPSP=20 according to the network environment?
>
> = Thanks,
>=20 Minh
>
> 2009/10/20 zhangyunfei <zhangyunfei@chinamobile.com>
>
>=20 >  Hi Minh=A3=AC
> >  PPSP is intended to = support both=20 envirnments, including the
> wireless ad
> > hoc=20 network.However there isn't much large scale PPSP practice
> = in ad=20 hoc
> > networks to the best of our knowledge.If you have=20 such
> information, welcome
> > to contribute = it.
>=20 >
> > Thanks,
> > Yunfei
> >
> = >=20  ------------------------------
> > =  zhangyunfei
>=20 > 2009-10-20
> > =  ------------------------------
>=20 >  *=B7=A2=BC=FE=C8=CB=A3=BA* Minh Nguyen
> > = *=B7=A2=CB=CD=CA=B1=BC=E4=A3=BA* 2009-10-20=20 17:48:15
> > *=CA=D5=BC=FE=C8=CB=A3=BA* Y.J. Gu
> = > *=B3=AD=CB=CD=A3=BA* ppsp@ietf.org
> > = *=D6=F7=CC=E2=A3=BA* Re: [ppsp]=20 Draft for PPSP Survey
> >
> > Dear all,
> = > I=20 wonder that does PPSP work for not only Internet but also
> = Wireless=20 Ad hoc
> > networks.
> > If it's not the case, = does anyone=20 work on PPSP and Ad hoc networks?
> > Does anyone have the=20 suggestions in this topic?
> >
> > Thanks,
> = >=20 -Minh
> >
> > On Tue, Oct 20, 2009 at 4:54 AM, = Y.J. Gu=20 <guyingjie@huawei.com>
>= =20 wrote:>
> >> Hi everyone,
> >> We = submitted a=20 survey draft for ppsp.
> >>
> >> = Abstract:
>=20 >> This document presents a survey of popular = Peer-to-Peer
>=20 >> streaming applications on the Internet. ?We focus on = the
>=20 >> Architecture and Peer Protocol/Tracker Signaling = Protocol
>=20 >> description in the presentation, and study a selection = of
>=20 >> well-known P2P streaming systems, including Joost, = PPlive,
>=20 >> and more. ?Through the survey, we summarize a common = P2P
>=20 >> streaming process model and the correspondent = signaling
>=20 >> process for P2P Streaming Protocol standardization.
> = >>
> >> The URL for this draft is:
> = >> http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt>=20 >>
> >> We appreciate your comments.
> = >>=20 Thanks.
> >>
> >> Regards
> = >>
>=20 >> Yingjie Gu
> >>
> >>
> = >>=20 _______________________________________________
> >> = ppsp=20 mailing list
> >> ppsp@ietf.org
> >> https://www.ietf.org/mailman/listinfo/ppsp
>=20 >>
> >
> >
> >
> > = --
> >=20 Minh Nguyen
> > +33 6 65 76 44 60
> >
>=20 >
>
>
> --
> Minh Nguyen
> +33 6 65 = 76 44=20 60
>



--
Minh=20 Nguyen
+33 6 65 76 44 60

--Boundary_(ID_B21aVpFRsLC9qJZC36ZjNA)-- From abegen@cisco.com Wed Oct 21 21:13:48 2009 Return-Path: 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 D0C123A686B for ; Wed, 21 Oct 2009 21:13:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.074 X-Spam-Level: X-Spam-Status: No, score=-5.074 tagged_above=-999 required=5 tests=[AWL=-1.264, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4] 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 vUN1EXJxQigF for ; Wed, 21 Oct 2009 21:13:47 -0700 (PDT) Received: from sj-iport-4.cisco.com (sj-iport-4.cisco.com [171.68.10.86]) by core3.amsl.com (Postfix) with ESMTP id 6C55F28C0DD for ; Wed, 21 Oct 2009 21:13:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=abegen@cisco.com; l=8371; q=dns/txt; s=sjiport04001; t=1256184835; x=1257394435; h=from:sender:reply-to:subject:date:message-id:to:cc: mime-version:content-transfer-encoding:content-id: content-description:resent-date:resent-from:resent-sender: resent-to:resent-cc:resent-message-id:in-reply-to: references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:list-owner:list-archive; z=From:=20"Ali=20C.=20Begen=20(abegen)"=20|Subject:=20RE:=20[ppsp]=20Draft=20for=20PPSP=20Survey |Date:=20Wed,=2021=20Oct=202009=2021:13:19=20-0700 |Message-ID:=20<04CAD96D4C5A3D48B1919248A8FE0D540A792AA2@ xmb-sjc-215.amer.cisco.com>|To:=20"Y.J.=20Gu"=20,=20"Minh=20Nguyen"=20,=0D =0A=20=20=20=20=20=20=20=20"zongning=2063316"=20|Cc:=20,=20|MIME-Version:=201.0 |Content-Transfer-Encoding:=20quoted-printable |In-Reply-To:=20<000701ca52c8$6c5fb970$400ca40a@china.hua wei.com>|References:=20<66dcf31f0910210835u31b995c7y83fa4 769359ecb6c@mail.gmail.com>=20<000701ca52c8$6c5fb970$400c a40a@china.huawei.com>; bh=FUEQOs+yocne5FOE3ucmw0Ry6VduVe8CxkWnJWFtL58=; b=EOl0NSASl6P7BtkZI5w3u4b19Xljf6kc8u3M9TsPS1BbOB/iIzKQXtns YR5npCJrpy9ToT+R0SmmMT5ao9GjZTycxg/mSK1iecNNkZ9nV9Bz2tcHr UV29Tq+ktudKo5GWbRGZuntDno8I2WNr95FUEpG+2gofzVPD1pObkQXYD 8=; Authentication-Results: sj-iport-4.cisco.com; dkim=neutral (message not signed) header.i=none X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: ApsEAOd430qrR7Ht/2dsb2JhbACEc7x5hwsHkUWBLoI5VgQ X-IronPort-AV: E=Sophos;i="4.44,602,1249257600"; d="scan'208";a="46307925" Received: from sj-core-1.cisco.com ([171.71.177.237]) by sj-iport-4.cisco.com with ESMTP; 22 Oct 2009 04:13:50 +0000 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.14.3) with ESMTP id n9M4Dp5k027222; Thu, 22 Oct 2009 04:13:51 GMT Received: from xmb-sjc-215.amer.cisco.com ([171.70.151.169]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Oct 2009 21:13:51 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: quoted-printable Date: Wed, 21 Oct 2009 21:13:19 -0700 Message-ID: <04CAD96D4C5A3D48B1919248A8FE0D540A792AA2@xmb-sjc-215.amer.cisco.com> In-Reply-To: <000701ca52c8$6c5fb970$400ca40a@china.huawei.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ppsp] Draft for PPSP Survey Thread-Index: AcpSZErhxaFJXqFaSzOg4dsdEy0NqQAYsyiwAAFJ/TA= References: <66dcf31f0910210835u31b995c7y83fa4769359ecb6c@mail.gmail.com> <000701ca52c8$6c5fb970$400ca40a@china.huawei.com> From: "Ali C. Begen (abegen)" To: "Y.J. Gu" , "Minh Nguyen" , "zongning 63316" X-OriginalArrivalTime: 22 Oct 2009 04:13:51.0248 (UTC) FILETIME=[0FA1C100:01CA52CE] Cc: ppsp@ietf.org, anh_minh.nguyen@telecom-sudparis.eu Subject: Re: [ppsp] Draft for PPSP Survey X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2009 04:13:48 -0000 A few notes here. Multipath transport can be used for different purposes. One is to = increase the throughput. Assuming that the client is not the bottleneck, = by connecting to multiple servers, one can download a content faster (or = stream at a higher bitrate). The second purpose is to improve = reliability. Assuming the physical links are disjoint (or at least they = don=A1=AFt share the point of congestion), using two paths to receive = the same data twice will reduce the effective loss rate (from p to p^2). = In a p2p environment, the first purpose makes sense (actually it is = mostly needed) since often the upload speeds of ordinary peers are = pretty low for the average service bandwidth. A peer needs to connect to = multiple peers to increase the throughput. It is also good for = unexpected events like peer churns. But as for the second purpose, it is = a difficult task to make sure that the underlying links are indeed not = sharing the point of congestion. In an overlay network, this is pretty = difficult. One needs to do a lot of correlation computations to figure = out whether congested locations are shared or not (Search for PoC = sharing, congestion correlation, etc. in google and look for = nossdav/sigmetrics/etc. papers). In majority of the papers, multipath transport has been overrated due to = the simplified assumptions on loss events/correlations. In wireless = world, things are not easier (especially in ad hoc networks). If not = properly designed and run, multipath transport can create catastrophic = results in such environments. Cheers, -acbegen > -----Original Message----- > From: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] On Behalf = Of Y.J. Gu > Sent: Wednesday, October 21, 2009 11:33 PM > To: 'Minh Nguyen'; 'zongning 63316' > Cc: ppsp@ietf.org; anh_minh.nguyen@telecom-sudparis.eu > Subject: Re: [ppsp] Draft for PPSP Survey >=20 > Hi Minh, > I'm interested in this topic too. Thank you very much for involving = multipath transport. > You said that multipath transmission is one of the critical issues for = multimedia > transport. Could you please disclose more specific information on this = topic? Is there any > applications that using multipath transmission? How they implement and = what's the problem > they met with? It will be a good instance for survey draft and we can = extract specific > requirements for the requirement draft. >=20 > Thank you very much :) >=20 > Regards >=20 > Yingjie Gu >=20 >=20 >=20 >=20 > ________________________________ >=20 > From: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] On Behalf = Of Minh Nguyen > Sent: Wednesday, October 21, 2009 11:35 PM > To: zongning 63316 > Cc: ppsp@ietf.org; anh_minh.nguyen@telecom-sudparis.eu > Subject: Re: [ppsp] Draft for PPSP Survey >=20 >=20 > Hi All, > To the best of my knowledge, one of the critical issues for = multimedia transport > through network diversity is to provide multipath transmission, = especially wireless ad hoc > networks. This is due in wireless networks, the high broken-link and = interference make it > is sensitive to delay, lost.. P2P streaming in this networks therefore = need to use both > multisource and multipath technique. > RTP is a good example, it is started designing of single transmission = from the > beginning, but find it is then difficultly to use many single flows = solely in the needs of > using multipath. As the result, standard RTP has been modified to = non-standard MRTP, which > is mentioned in this paper > = to support multi flow. > Moreover, the usage of multipath in Internet can improve significantly = the quality of > streaming media in P2P overlay. > I was not clear yet about PPSP transmission, and it seems that the = requirement of > PPSP transmission in the PPSP's draft is still in progress. I think we = can put the > requirement of multipath transmission into this part as well. Hence, = we can avoid the > same problem which came from RTP protocol. >=20 > BR, > Minh >=20 >=20 >=20 > 2009/10/21 zongning 63316 >=20 >=20 > Hi, Minh >=20 > Thank you for offering new use cases of PPSP. I think the design of = PPSP > protocols including basic functionalities and message encoding will be = flexible and > extensible enough to adopt as many P2P streaming applications as = possible. Just like RTP, > we have seen many RTP extensions to emergent new Audio/Video codecs. > So any type of P2P streaming applications are ecouraged to be = discussed in > mailing list and we will see how much we can incorporate into PPSP = design. >=20 > BR, > Ning Zong >=20 > ----- =D4=AD=D3=CA=BC=FE ----- > =B7=A2=BC=FE=C8=CB: Minh Nguyen > =C8=D5=C6=DA: =D0=C7=C6=DA=B6=FE, =CA=AE=D4=C2 20=C8=D5, 2009 = =CF=C2=CE=E77:02 >=20 > =D6=F7=CC=E2: Re: [ppsp] Draft for PPSP Survey >=20 > =CA=D5=BC=FE=C8=CB: zhangyunfei > =B3=AD=CB=CD: "ppsp@ietf.org" >=20 >=20 > > Hi Yunfei, > > I have just started the works for P2P video streaming over Ad hoc >=20 > > networksin which P2P streaming need to be operated efficiently on >=20 > > top of OLSR ad hoc > > routing layer. > > > > As I have seen PPSP would be IETF's standard protocol for P2P > > streaming, It > > was a good choice if PPSP could be adapted for Ad hoc/Mesh = networks > > accordingly. > > Do you have any recommend for that? for example, is it possible to > > extend or > > adapt PPSP according to the network environment? > > > > Thanks, > > Minh > > > > 2009/10/20 zhangyunfei > > > > > Hi Minh=A3=AC > > > PPSP is intended to support both envirnments, including the > > wireless ad > > > hoc network.However there isn't much large scale PPSP practice > > in ad hoc > > > networks to the best of our knowledge.If you have such > > information, welcome > > > to contribute it. > > > > > > Thanks, > > > Yunfei > > > > > > ------------------------------ > > > zhangyunfei > > > 2009-10-20 > > > ------------------------------ > > > *=B7=A2=BC=FE=C8=CB=A3=BA* Minh Nguyen > > > *=B7=A2=CB=CD=CA=B1=BC=E4=A3=BA* 2009-10-20 17:48:15 > > > *=CA=D5=BC=FE=C8=CB=A3=BA* Y.J. Gu > > > *=B3=AD=CB=CD=A3=BA* ppsp@ietf.org > > > *=D6=F7=CC=E2=A3=BA* Re: [ppsp] Draft for PPSP Survey > > > > > > Dear all, > > > I wonder that does PPSP work for not only Internet but also > > Wireless Ad hoc > > > networks. > > > If it's not the case, does anyone work on PPSP and Ad hoc = networks? > > > Does anyone have the suggestions in this topic? > > > > > > Thanks, > > > -Minh > > > > > > On Tue, Oct 20, 2009 at 4:54 AM, Y.J. Gu > > wrote:> > > >> Hi everyone, > > >> We submitted a survey draft for ppsp. > > >> > > >> Abstract: > > >> This document presents a survey of popular Peer-to-Peer > > >> streaming applications on the Internet. ?We focus on the > > >> Architecture and Peer Protocol/Tracker Signaling Protocol > > >> description in the presentation, and study a selection of > > >> well-known P2P streaming systems, including Joost, PPlive, > > >> and more. ?Through the survey, we summarize a common P2P > > >> streaming process model and the correspondent signaling > > >> process for P2P Streaming Protocol standardization. > > >> > > >> The URL for this draft is: > > >> http://www.ietf.org/id/draft-gu-ppsp-survey-00.txt > > >> > > >> We appreciate your comments. > > >> Thanks. > > >> > > >> Regards > > >> > > >> Yingjie Gu > > >> > > >> > > >> _______________________________________________ > > >> ppsp mailing list > > >> ppsp@ietf.org > > >> https://www.ietf.org/mailman/listinfo/ppsp > > >> > > > > > > > > > > > > -- > > > Minh Nguyen > > > +33 6 65 76 44 60 > > > > > > > > > > > > -- > > Minh Nguyen > > +33 6 65 76 44 60 > > >=20 >=20 >=20 >=20 >=20 > -- > Minh Nguyen > +33 6 65 76 44 60 >=20 >=20 From zongning@huawei.com Wed Oct 21 23:46:44 2009 Return-Path: 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 1E48A28C110 for ; Wed, 21 Oct 2009 23:46:44 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.246 X-Spam-Level: X-Spam-Status: No, score=-101.246 tagged_above=-999 required=5 tests=[AWL=1.353, BAYES_00=-2.599, 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 LVGOemq0gqrS for ; Wed, 21 Oct 2009 23:46:43 -0700 (PDT) Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 437963A6918 for ; Wed, 21 Oct 2009 23:46:43 -0700 (PDT) Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRW00KU2LI2XU@szxga04-in.huawei.com> for ppsp@ietf.org; Thu, 22 Oct 2009 14:46:51 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRW00CV5LI2AO@szxga04-in.huawei.com> for ppsp@ietf.org; Thu, 22 Oct 2009 14:46:50 +0800 (CST) Received: from z63316 ([10.164.12.81]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KRW00M5YLI2K6@szxml06-in.huawei.com> for ppsp@ietf.org; Thu, 22 Oct 2009 14:46:50 +0800 (CST) Date: Thu, 22 Oct 2009 14:46:50 +0800 From: Ning Zong To: ppsp@ietf.org Message-id: <001801ca52e3$6f10db70$510ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Thread-index: AcpS4gVjcwITK8ahTTe+oYvMTc+TcQAABoYA Subject: [ppsp] FW: New Version Notification for draft-zhang-ppsp-problem-statement-05 X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2009 06:46:44 -0000 Hi, Folks, A new version of PPSP Problem Statement has been uploaded to IETF website. Any comments and suggestions are highly appreciated. Abstract: We propose to standardize the key signaling protocols among various P2P streaming system components including the tracker and the peers. These protocols, called PPSP, are a part of P2P streaming protocols. This document describes the terminologies, concepts, incentives, and scope of developing PPSP, as well as the use cases of PPSP. The URL for this I-D is: http://www.ietf.org/id/draft-zhang-ppsp-problem-statement-05.txt BR, Ning Zong -----Original Message----- From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] Sent: Thursday, October 22, 2009 2:35 PM To: zongning@huawei.com Cc: zhangyunfei@chinamobile.com; Gonzalo.Camarillo@ericsson.com; james.seng@pplive.com; yry@cs.yale.edu Subject: New Version Notification for draft-zhang-ppsp-problem-statement-05 A new version of I-D, draft-zhang-ppsp-problem-statement-05.txt has been successfuly submitted by Ning Zong and posted to the IETF repository. Filename: draft-zhang-ppsp-problem-statement Revision: 05 Title: Problem Statement of P2P Streaming Protocol (PPSP) Creation_date: 2009-10-20 WG ID: Independent Submission Number_of_pages: 19 Abstract: We propose to standardize the key signaling protocols among various P2P streaming system components including the tracker and the peers. These protocols, called PPSP, are a part of P2P streaming protocols. This document describes the terminologies, concepts, incentives, and scope of developing PPSP, as well as the use cases of PPSP. The IETF Secretariat. From zongning@huawei.com Thu Oct 22 20:20:39 2009 Return-Path: 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 CF3053A68C2 for ; Thu, 22 Oct 2009 20:20:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -100.494 X-Spam-Level: X-Spam-Status: No, score=-100.494 tagged_above=-999 required=5 tests=[AWL=-0.226, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227, 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 4WnGj9wnw8dX for ; Thu, 22 Oct 2009 20:20:39 -0700 (PDT) Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 0693D3A68B4 for ; Thu, 22 Oct 2009 20:20:39 -0700 (PDT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRY00A4A6MENN@szxga03-in.huawei.com> for ppsp@ietf.org; Fri, 23 Oct 2009 11:20:38 +0800 (CST) Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KRY00L3J6MEIT@szxga03-in.huawei.com> for ppsp@ietf.org; Fri, 23 Oct 2009 11:20:38 +0800 (CST) Received: from z63316 ([10.164.12.81]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KRY000HK6ME48@szxml04-in.huawei.com> for ppsp@ietf.org; Fri, 23 Oct 2009 11:20:38 +0800 (CST) Date: Fri, 23 Oct 2009 11:20:37 +0800 From: Ning Zong To: ppsp@ietf.org Message-id: <004201ca538f$cafd3120$510ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Thread-index: AcpTjve4DKqIiJjrSF6+9ZBpBz5u0gAAI7uA Subject: [ppsp] FW: New Version Notification for draft-zong-ppsp-reqs-02 X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Oct 2009 03:20:39 -0000 Hi, Folks, A new version of PPSP Requirements has been uploaded to IETF website. Any comments and suggestions are highly appreciated. Abstract: The objective of the PPSP work is to standardize the key signaling protocols that apply to tracker and peers in a Peer-to-Peer (P2P) streaming system. These protocols are called PPSP. This document enumerates the requirements for the PPSP, which should be considered when designing PPSP. The URL for this I-D is: http://www.ietf.org/id/draft-zong-ppsp-reqs-02.txt BR, Ning Zong -----Original Message----- From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] Sent: Friday, October 23, 2009 11:14 AM To: zongning@huawei.com Cc: zhangyunfei@chinamobile.com; victor@iptel.org; carlw@mcsr-labs.org Subject: New Version Notification for draft-zong-ppsp-reqs-02 A new version of I-D, draft-zong-ppsp-reqs-02.txt has been successfuly submitted by Ning Zong and posted to the IETF repository. Filename: draft-zong-ppsp-reqs Revision: 02 Title: P2P Streaming Protocol (PPSP) Requirements Creation_date: 2009-10-22 WG ID: Independent Submission Number_of_pages: 12 Abstract: The objective of the PPSP work is to standardize the key signaling protocols that apply to tracker and peers in a Peer-to-Peer (P2P) streaming system. These protocols are called PPSP. This document enumerates the requirements for the PPSP, which should be considered when designing PPSP. The IETF Secretariat. From li.lichun1@zte.com.cn Sun Oct 25 20:44:13 2009 Return-Path: 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 1B1FC3A6891; Sun, 25 Oct 2009 20:44:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -99.657 X-Spam-Level: X-Spam-Status: No, score=-99.657 tagged_above=-999 required=5 tests=[AWL=2.181, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_DOUBLE_IP_LOOSE=0.76, 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 dvthklI78YRt; Sun, 25 Oct 2009 20:44:12 -0700 (PDT) Received: from mx5.zte.com.cn (mx5.zte.com.cn [63.217.80.70]) by core3.amsl.com (Postfix) with ESMTP id 546D23A6857; Sun, 25 Oct 2009 20:44:11 -0700 (PDT) Received: from [10.30.17.100] by mx5.zte.com.cn with surfront esmtp id 111641821921442; Mon, 26 Oct 2009 11:17:55 +0800 (CST) Received: from [10.30.3.19] by [10.30.17.100] with StormMail ESMTP id 14630.1892867178; Mon, 26 Oct 2009 11:32:29 +0800 (CST) Received: from notes_smtp.zte.com.cn ([10.30.1.239]) by mse2.zte.com.cn with ESMTP id n9Q3i9DY065278; Mon, 26 Oct 2009 11:44:10 +0800 (CST) (envelope-from li.lichun1@zte.com.cn) To: enrico.marocco@telecomitalia.it MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5.6 March 06, 2007 Message-ID: From: li.lichun1@zte.com.cn Date: Mon, 26 Oct 2009 11:43:55 +0800 X-MIMETrack: Serialize by Router on notes_smtp/zte_ltd(Release 6.5.4|March 27, 2005) at 2009-10-26 11:44:01, Serialize complete at 2009-10-26 11:44:01 Content-Type: multipart/alternative; boundary="=_alternative 0014D4C14825765B_=" X-MAIL: mse2.zte.com.cn n9Q3i9DY065278 Cc: ppsp@ietf.org, ppsp-bounces@ietf.org Subject: Re: [ppsp] [alto] ????: Re: New draft on relay usage for ALTO X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Oct 2009 03:44:13 -0000 This is a multipart message in MIME format. --=_alternative 0014D4C14825765B_= Content-Type: text/plain; charset="US-ASCII" Sorry to repost the mail. The former mail's title is missing. Indeed, TIVs should be addressed in routing layer. However, solving the problem in routing layer may involve things like changing routing protocol and replacing routers, which will pay some time and high price. In contrary, relay is an easier solution for applications sensitive to delay, and is already used somewhere. Relay can cause layer violation. Operators may not like it. But operator's participating in relay selection may reduce the harm of layer violation. Just my two cents. On Mon, Oct 12, 2009 at 8:38 PM, Enrico Marocco wrote: > Sebastian Kiesel wrote: >>> Numerous studies have reported the existence of triangle inequality >>> violations (TIV) in the Internet delay space??for about10%-30%??. It has >>> been proved to be a stable phenomenon in the Internet, and it is due >>> to the flaw of IP routing protocol. Since it is impossible to modify >>> the existing IP protocol, using QoS relay will be a complement to IP >>> routing. >> >> Do you have more information (e.g., references to papers/studies) about >> the true reasons for TIV? Are they due to >> >> 1) Non-technical, deliberate decisions of the network operators (e.g., >> no business case for upgrading a line)? >> >> 2) Technical limitations of the IP routing protocols (BGP, OSPF, etc.)? >> >> 3) Technical limitations of the IP protocol itself (IPv4)? >> >> or ... >> >> Maybe also some people working for an operator can comment on this? > > As far as I can tell, TIVs are intrinsically related to the very nature > of the Internet -- path asymmetry, route load balancing and so on -- and > at the end of they could be hardly considered a problem. However, > problem or non-problem, they entirely belong to the routing layer and > addressing them at the application level makes to me for a perfect > example of layer violation. > > -- > Ciao, > Enrico > > _______________________________________________ > alto mailing list > alto@ietf.org > https://www.ietf.org/mailman/listinfo/alto > > -- Sincerely yours, Lichun Li ZTE Corporation -------------------------------------------------------- ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender. This message has been scanned for viruses and Spam by ZTE Anti-Spam system. --=_alternative 0014D4C14825765B_= Content-Type: text/html; charset="US-ASCII"
Sorry to repost the mail. The former mail's title is missing.

Indeed, TIVs should be addressed in routing layer. However, solving the problem in routing layer may involve things like changing routing protocol and replacing routers, which will pay some time and high price. In contrary, relay is an easier solution for applications sensitive to delay, and is already used somewhere.

Relay can cause layer violation. Operators may not like it. But operator's participating in relay selection may reduce the harm of layer violation.

Just my two cents.

On Mon, Oct 12, 2009 at 8:38 PM, Enrico Marocco
<enrico.marocco@telecomitalia.it> wrote:
> Sebastian Kiesel wrote:
>>> Numerous studies have reported the existence of triangle inequality
>>> violations (TIV) in the Internet delay space??for about10%-30%??. It has
>>> been proved to be a stable phenomenon in the Internet, and it is due
>>> to the flaw of IP routing protocol. Since it is impossible to modify
>>> the existing IP protocol, using QoS relay will be a complement to IP
>>> routing.
>>
>> Do you have more information (e.g., references to papers/studies) about
>> the true reasons for TIV? Are they due to
>>
>> 1) Non-technical, deliberate decisions of the network operators (e.g.,
>>    no business case for upgrading a line)?
>>
>> 2) Technical limitations of the IP routing protocols (BGP, OSPF, etc.)?
>>
>> 3) Technical limitations of the IP protocol itself (IPv4)?
>>
>> or ...
>>
>> Maybe also some people working for an operator can comment on this?
>
> As far as I can tell, TIVs are intrinsically related to the very nature
> of the Internet -- path asymmetry, route load balancing and so on -- and
> at the end of they could be hardly considered a problem. However,
> problem or non-problem, they entirely belong to the routing layer and
> addressing them at the application level makes to me for a perfect
> example of layer violation.
>
> --
> Ciao,
> Enrico
>
> _______________________________________________
> alto mailing list
> alto@ietf.org
> https://www.ietf.org/mailman/listinfo/alto
>
>



--
Sincerely yours,

Lichun Li
ZTE Corporation


--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.
--=_alternative 0014D4C14825765B_=-- From gonzalo.camarillo@ericsson.com Wed Oct 28 13:22:34 2009 Return-Path: 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 7022B3A68E7 for ; Wed, 28 Oct 2009 13:22:34 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.167 X-Spam-Level: X-Spam-Status: No, score=-6.167 tagged_above=-999 required=5 tests=[AWL=0.082, BAYES_00=-2.599, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-4] 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 10ZyhpLR317A for ; Wed, 28 Oct 2009 13:22:33 -0700 (PDT) Received: from mailgw4.ericsson.se (mailgw4.ericsson.se [193.180.251.62]) by core3.amsl.com (Postfix) with ESMTP id 73D3428C155 for ; Wed, 28 Oct 2009 13:22:33 -0700 (PDT) X-AuditID: c1b4fb3e-b7bf6ae000005dda-c3-4ae8a8173fe9 Received: from esealmw129.eemea.ericsson.se (Unknown_Domain [153.88.253.124]) by mailgw4.ericsson.se (Symantec Mail Security) with SMTP id 50.2D.24026.718A8EA4; Wed, 28 Oct 2009 21:22:47 +0100 (CET) Received: from esealmw129.eemea.ericsson.se ([153.88.254.177]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Oct 2009 21:22:46 +0100 Received: from mail.lmf.ericsson.se ([131.160.11.50]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Wed, 28 Oct 2009 21:22:46 +0100 Received: from [131.160.126.211] (rvi2-126-211.lmf.ericsson.se [131.160.126.211]) by mail.lmf.ericsson.se (Postfix) with ESMTP id 6602A244F; Wed, 28 Oct 2009 22:22:46 +0200 (EET) Message-ID: <4AE8A815.60409@ericsson.com> Date: Wed, 28 Oct 2009 22:22:45 +0200 From: Gonzalo Camarillo User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: ppsp@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 28 Oct 2009 20:22:46.0846 (UTC) FILETIME=[69A085E0:01CA580C] X-Brightmail-Tracker: AAAAAA== Subject: [ppsp] Draft agenda for our meeting in Japan X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Oct 2009 20:22:34 -0000 Folks, I have just uploaded our draft agenda for Japan. http://www.ietf.org/proceedings/09nov/agenda/ppsp.html Cheers, Gonzalo From zhangyunfei@chinamobile.com Fri Oct 30 00:16:02 2009 Return-Path: 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 3AC383A6852 for ; Fri, 30 Oct 2009 00:16:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -95.07 X-Spam-Level: X-Spam-Status: No, score=-95.07 tagged_above=-999 required=5 tests=[AWL=2.106, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, RELAY_IS_221=2.222, 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 riPLamJR6si7 for ; Fri, 30 Oct 2009 00:16:01 -0700 (PDT) Received: from cmccmta.chinamobile.com (cmccmta.chinamobile.com [221.130.253.133]) by core3.amsl.com (Postfix) with ESMTP id 6DD893A63D3 for ; Fri, 30 Oct 2009 00:16:01 -0700 (PDT) Received: from LENOVO-917FFE55 ([10.1.5.3]) by mail.chinamobile.com (Lotus Domino Release 6.5.5FP1) with SMTP id 2009103015213104-16144 ; Fri, 30 Oct 2009 15:21:31 +0800 Date: Fri, 30 Oct 2009 15:16:04 +0800 From: "zhangyunfei" To: "ppsp@ietf.org" Message-ID: <200910301516037965872@chinamobile.com> X-mailer: Foxmail 6, 2, 103, 20 [cn] Mime-Version: 1.0 X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2009-10-30 15:21:32, Serialize by Router on cmccmta/servers/cmcc(Release 6.5.5FP1 | April 14, 2006) at 2009-10-30 15:16:19, Serialize complete at 2009-10-30 15:16:19 Content-Type: multipart/alternative; boundary="=====003_Dragon337367257744_=====" Subject: [ppsp] a reference for ppsp implementation X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Oct 2009 07:16:02 -0000 This is a multi-part message in MIME format. --=====003_Dragon337367257744_===== Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="gb2312" Hi, I just read a paper of "GoalBit: The First Free and Open Source Peer-to-Peer Streaming Network", which is an protocol introduction of Goalbit, a system Ping ever menetioned in the mailing list. From a quick glance, the work of GoalBit is well suited with PPSP scope,esp. part 3.You can refer it through http://goalbit.sourceforge.net/publications/lanc2009-20090717-CAMERAREADY.pdf for more details. BR Yunfei zhangyunfei 2009-10-30 --=====003_Dragon337367257744_===== Content-Transfer-Encoding: 7bit Content-Type: text/html; charset="gb2312"
Hi,
   I just read a paper of "GoalBit: The First Free and Open Source Peer-to-Peer Streaming Network", which is an protocol introduction of Goalbit, a system Ping ever menetioned in the mailing list.
  From a quick glance, the work of GoalBit is well suited with PPSP scope,esp. part 3.You can refer it through http://goalbit.sourceforge.net/publications/lanc2009-20090717-CAMERAREADY.pdf for more details.
 
BR
 Yunfei
 
zhangyunfei
2009-10-30
 --=====003_Dragon337367257744_=====-- From zongning@huawei.com Fri Oct 30 17:40:12 2009 Return-Path: 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 034713A696C for ; Fri, 30 Oct 2009 17:40:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -98.52 X-Spam-Level: X-Spam-Status: No, score=-98.52 tagged_above=-999 required=5 tests=[AWL=-2.110, BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, J_CHICKENPOX_53=0.6, RDNS_NONE=0.1, 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 cOAv1IFuCwb3 for ; Fri, 30 Oct 2009 17:40:10 -0700 (PDT) Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 510EE3A6936 for ; Fri, 30 Oct 2009 17:40:10 -0700 (PDT) Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KSC004W0SJ5CQ@szxga02-in.huawei.com> for ppsp@ietf.org; Sat, 31 Oct 2009 08:40:17 +0800 (CST) Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KSC003JOSJ40X@szxga02-in.huawei.com> for ppsp@ietf.org; Sat, 31 Oct 2009 08:40:16 +0800 (CST) Received: from z63316 ([10.164.12.81]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KSC0058LSJ4HP@szxml06-in.huawei.com> for ppsp@ietf.org; Sat, 31 Oct 2009 08:40:16 +0800 (CST) Date: Sat, 31 Oct 2009 08:40:16 +0800 From: Ning Zong In-reply-to: <200910301516037965872@chinamobile.com> To: 'zhangyunfei' , ppsp@ietf.org Message-id: <001601ca59c2$b7548ea0$510ca40a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 X-Mailer: Microsoft Office Outlook 11 Content-type: multipart/alternative; boundary="Boundary_(ID_cnn6AAYd4zI+Jr6NMFHOQg)" Thread-index: AcpZMROQFXZ0+ZFuSRynNXZH6Jz2HQAkXSFg Subject: Re: [ppsp] a reference for ppsp implementation X-BeenThere: ppsp@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: discussing to draw up peer to peer streaming protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 31 Oct 2009 00:40:12 -0000 This is a multi-part message in MIME format. --Boundary_(ID_cnn6AAYd4zI+Jr6NMFHOQg) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi, Yunfei, Thank you for the reference. I would think it also worth studying in the Hiroshima PPSP BoF. BR, Ning Zong _____ From: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] On Behalf Of zhangyunfei Sent: Friday, October 30, 2009 3:16 PM To: ppsp@ietf.org Subject: [ppsp] a reference for ppsp implementation Hi, I just read a paper of "GoalBit: The First Free and Open Source Peer-to-Peer Streaming Network", which is an protocol introduction of Goalbit, a system Ping ever menetioned in the mailing list. From a quick glance, the work of GoalBit is well suited with PPSP scope,esp. part 3.You can refer it through http://goalbit.sourceforge.net/publications/lanc2009-20090717-CAMERAREADY.pd f for more details. BR Yunfei _____ zhangyunfei 2009-10-30 --Boundary_(ID_cnn6AAYd4zI+Jr6NMFHOQg) Content-type: text/html; charset=us-ascii Content-transfer-encoding: quoted-printable

Hi, = Yunfei,

 <= /span>

Thank you for the reference. I would think it also worth studying in the Hiroshima PPSP = BoF.

 <= /span>

BR,

Ning = Zong

 <= /span>

From: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] On Behalf Of zhangyunfei
Sent: Friday, October 30, = 2009 3:16 PM
To: ppsp@ietf.org
Subject: [ppsp] a = reference for ppsp implementation

 

Hi,

   I just read a paper of = "GoalBit: The First Free and Open Source Peer-to-Peer Streaming Network", = which is an protocol introduction of Goalbit, a system Ping ever menetioned in the mailing list.

  From a quick glance, the work of = GoalBit is well suited with PPSP scope,esp. part 3.You can refer it through http://goalbit.sourceforge.net/publications/lanc2009-200907= 17-CAMERAREADY.pdf for more details.

 

BR

 Yunfei

 

zhangyunfei

2009-10-30

--Boundary_(ID_cnn6AAYd4zI+Jr6NMFHOQg)--