IETF Logo Mail Archive

[ppsp] 回复: 答复: tracker protocol review

zhangyunfei <zhangyunfei@chinamobile.com> Mon, 05 November 2012 05:40 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 2EE9E21F88D4 for <ppsp@ietfa.amsl.com>; Sun, 4 Nov 2012 21:40:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -92.842
X-Spam-Level:
X-Spam-Status: No, score=-92.842 tagged_above=-999 required=5 tests=[AWL=-4.714, BAYES_50=0.001, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, 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 ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QRs8GtoWAoL8 for <ppsp@ietfa.amsl.com>; Sun, 4 Nov 2012 21:40:11 -0800 (PST)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id D318721F88C1 for <ppsp@ietf.org>; Sun, 4 Nov 2012 21:40:10 -0800 (PST)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id E8068E403; Mon, 5 Nov 2012 13:40:11 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id D9785E3E1; Mon, 5 Nov 2012 13:40:11 +0800 (CST)
Received: from zyf-PC ([10.2.43.220]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2012110513400822-13201 ; Mon, 5 Nov 2012 13:40:08 +0800
Date: Mon, 05 Nov 2012 13:40:06 +0800
From: zhangyunfei <zhangyunfei@chinamobile.com>
To: '邓灵莉' <denglingli@chinamobile.com>, "Yingjie Gu(yingjie)" <guyingjie@huawei.com>, 'Rui Cruz' <rui.cruz@ieee.org>
References: <2012110511283736034341@chinamobile.com>, <002001cdbb0b$9e8ff000$dbafd000$@com>
X-Priority: 3 (Normal)
X-Mailer: Foxmail 7.0.1.85[cn]
Mime-Version: 1.0
Message-ID: <201211051340060015086@chinamobile.com>
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-11-05 13:40:08, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-11-05 13:40:10, Serialize complete at 2012-11-05 13:40:10
Content-Type: multipart/alternative; boundary="----=_001_NextPart656750100165_=----"
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-19340.004
X-TM-AS-Result: No--33.874-7.0-31-10
X-imss-scan-details: No--33.874-7.0-31-10;No--33.874-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] 回复: 答复: tracker protocol review
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: Mon, 05 Nov 2012 05:40:12 -0000

Yes, Lingli. I mean it would be good to write explicitly to say how to handle this in tracker protocol.

BR
Yunfei



zhangyunfei

发件人： 邓灵莉/Lingli Deng
发送时间： 2012-11-05 12:11
收件人： 'zhangyunfei'; 'Yingjie Gu\(yingjie\)'; 'Rui Cruz'
抄送： 'ppsp'
主题： 答复: [ppsp] tracker protocol review
Yunfei,
As for your comment asking for clarification for content integrity’s relation to tracker protocol, I would like to explain that as pointed out at the end of Section 9.2,  content pollution
can be detected by incorporating integrity verification schemes for published shared contents.  As content chunks are transferred independently and concurrently, a correspondent chunk-level integrity verification MUST be used, checked with signed fingerprints received from authentic origin.
In other words, these fingerprints MUST be signed by the authentic origin of the content, and MUST be distributed in a trustworthy manner against manipulation and forgery.
It would be reasonable to expect such distribution be handled by the tracker protocol in a security-enhanced sense.
BR
Lingli
发件人: ppsp-bounces@ietf.org [mailto:ppsp-bounces@ietf.org] 代表 zhangyunfei
发送时间: 2012年11月4日 22:29
收件人: Yingjie Gu(yingjie); 'Rui Cruz'
抄送: ppsp
主题: [ppsp] tracker protocol review
 
Hi Rui and Yingjie (Speaking individually) ,
    I have read the updated tracker protocol draft and have the following comments:
1) Encoding issue: It's good to mention that PPSP-TP is intended to support binary encoding in section 4. However in section 5, 7 and 8, http+XML is still in the main page. Is this just for example? Or a general semantics desperation is enough? I think much of section 7.1 in current version can be placed in Appendix A. Are you intending to use EXI for the binary encoding and do you still need http for the underlying transport?
2)  Check the section 10 for the XML descriptions. Do we need the update of this part?
3)Security part, section 9.2, how does the content integrity check related to the tracker protocol should be better explained.
 
BR
Yunfei
 



zhangyunfei

v2.23.0 | Report a Bug | By Email