[ppsp] 回复: Re: [Spam]回复: Re:回复: Re: Proposal to resolve Issue 10 + 13

zhangyunfei <zhangyunfei@chinamobile.com> Thu, 10 May 2012 02:18 UTC

Return-Path: <zhangyunfei@chinamobile.com>
X-Original-To: ppsp@ietfa.amsl.com
Delivered-To: ppsp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BF3B211E80AA for <ppsp@ietfa.amsl.com>; Wed, 9 May 2012 19:18:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -91.292
X-Spam-Level:
X-Spam-Status: No, score=-91.292 tagged_above=-999 required=5 tests=[AWL=-2.564, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_BASE64_TEXT=1.753, MIME_CHARSET_FARAWAY=2.45, RELAY_IS_221=2.222, SARE_SUB_ENC_GB2312=1.345, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UJZqgM6QWZdO for <ppsp@ietfa.amsl.com>; Wed, 9 May 2012 19:18:35 -0700 (PDT)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D2E6111E80AF for <ppsp@ietf.org>; Wed, 9 May 2012 19:18:34 -0700 (PDT)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id 4D239E5D2; Thu, 10 May 2012 10:18:33 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id 41CF6E5D0; Thu, 10 May 2012 10:18:33 +0800 (CST)
Received: from zyf-PC ([10.2.43.220]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2012051010183147-6045 ; Thu, 10 May 2012 10:18:31 +0800
Date: Thu, 10 May 2012 10:18:26 +0800
From: zhangyunfei <zhangyunfei@chinamobile.com>
To: "arno@cs.vu.nl" <arno@cs.vu.nl>
References: <OF97B14220.883D5968-ON482579DB.003454AD-482579DB.0035B23D@zte.com.cn> <2012041216393612240745@chinamobile.com>, <4F869775.6010007@cs.vu.nl> <2012041815001581776052@chinamobile.com>, <4F8E6DCE.90101@cs.vu.nl> <20120418183444961415101@chinamobile.com>, <4FAA0C76.9010306@cs.vu.nl>
X-Priority: 3 (Normal)
X-Mailer: Foxmail 7.0.1.85[cn]
Mime-Version: 1.0
Message-ID: <2012051010182675958722@chinamobile.com>
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-05-10 10:18:31, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-05-10 10:18:32, Serialize complete at 2012-05-10 10:18:32
Content-Type: multipart/alternative; boundary="----=_001_NextPart320220147167_=----"
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-18896.003
X-TM-AS-Result: No--41.609-7.0-31-10
X-imss-scan-details: No--41.609-7.0-31-10;No--41.609-7.0-31-10
X-TM-AS-User-Approved-Sender: No;No
X-TM-AS-User-Blocked-Sender: No;No
Cc: ppsp <ppsp@ietf.org>
Subject: [ppsp] 回复: Re: [Spam]回复: Re:回复: Re: Proposal to resolve Issue 10 + 13
X-BeenThere: ppsp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: zhangyunfei <zhangyunfei@chinamobile.com>
List-Id: discussing to draw up peer to peer streaming protocol <ppsp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ppsp>, <mailto:ppsp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ppsp>
List-Post: <mailto:ppsp@ietf.org>
List-Help: <mailto:ppsp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ppsp>, <mailto:ppsp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2012 02:18:35 -0000

Hi Arno,
    I had an email on discussing the new issues derived from PPSP requirements you proposed in the mailing list several days ago. I am not sure if you received it correctly. If not, please check the spam box again.

BR
Yunfei




zhangyunfei

发件人: Arno Bakker
发送时间: 2012-05-09 14:19
收件人: zhangyunfei
抄送: ppsp
主题: Re: [Spam]回复: Re:[ppsp]回复: Re: Proposal to resolve Issue 10 + 13
On 18/04/2012 12:34, zhangyunfei wrote:
> Hi Arno,
> Pls see inline.Thanks.

Hi all

this landed in my spam box, so sorry for the late reply. See inline.

> [Yunfei] This is what I worry about. We cannot assure that each time we 
> can request
> chunks in groups of powers of 2, as it's dependent on what the serving 
> peers have, which
> is hard to ensure that the number of available chunks being powers of 2. 

IMHO, chunks will be requested in powers of 2. First, one will likely
request more than 1 chunk at a time to be able to fill the pipeline from
sender to receiver (cf. delay-bandwidth product). Requesting 1K and then
waiting for it will not be efficient. Second, as we're computer
scientists we'll use base 2 (32K, 64K, etc) when using multiples ;o)


> In such cases, requsting
> a range of chunks needs no more bits than bin number. What's worse, if 
> the chunks peer A has is
> sparsely distributed, i.e., the chunkmap is likely to be 10001011110, 
> bin numbering needs more bits.

Bins are actually more efficient than (start,end) in this example. With
bin numbers, you'll in the worst case need an integer for every 1 in the
bitmap, so 6 in this case. In a better case we might be able to address
the 4 ones at the end as a single bin. However, if you use (start,end)
addressing, you'll actually need 2 integers per 1 bit, or 12 integers.

CU,
    Arno