IETF Logo Mail Archive

[ppsp] tracker protocol review

zhangyunfei <zhangyunfei@chinamobile.com> Mon, 05 November 2012 03:28 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 6304821F8979 for <ppsp@ietfa.amsl.com>; Sun, 4 Nov 2012 19:28:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -97.023
X-Spam-Level:
X-Spam-Status: No, score=-97.023 tagged_above=-999 required=5 tests=[AWL=-1.600, BAYES_50=0.001, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, MIME_BASE64_TEXT=1.753, RELAY_IS_221=2.222, 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 KUhlpXPkMAB6 for <ppsp@ietfa.amsl.com>; Sun, 4 Nov 2012 19:28:43 -0800 (PST)
Received: from imss.chinamobile.com (imss.chinamobile.com [221.130.253.135]) by ietfa.amsl.com (Postfix) with ESMTP id 8F68621F847D for <ppsp@ietf.org>; Sun, 4 Nov 2012 19:28:42 -0800 (PST)
Received: from imss.chinamobile.com (localhost [127.0.0.1]) by localhost.chinamobile.com (Postfix) with ESMTP id 98390E474; Mon, 5 Nov 2012 11:28:41 +0800 (CST)
Received: from mail.chinamobile.com (unknown [10.1.28.22]) by imss.chinamobile.com (Postfix) with ESMTP id 74B4EE3FF; Mon, 5 Nov 2012 11:28:41 +0800 (CST)
Received: from zyf-PC ([10.2.43.220]) by mail.chinamobile.com (Lotus Domino Release 6.5.6) with ESMTP id 2012110511283963-10601 ; Mon, 5 Nov 2012 11:28:39 +0800
Date: Mon, 05 Nov 2012 11:28:37 +0800
From: zhangyunfei <zhangyunfei@chinamobile.com>
To: "Yingjie Gu(yingjie)" <guyingjie@huawei.com>, 'Rui Cruz' <rui.cruz@ieee.org>
X-Priority: 3 (Normal)
X-Mailer: Foxmail 7.0.1.85[cn]
Mime-Version: 1.0
Message-ID: <2012110511283736034341@chinamobile.com>
X-MIMETrack: Itemize by SMTP Server on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-11-05 11:28:39, Serialize by Router on jtgsml01/servers/cmcc(Release 6.5.6|March 06, 2007) at 2012-11-05 11:28:40, Serialize complete at 2012-11-05 11:28:40
Content-Type: multipart/alternative; boundary="----=_001_NextPart425056685730_=----"
X-TM-AS-Product-Ver: IMSS-7.0.0.8231-6.8.0.1017-19340.004
X-TM-AS-Result: No--9.278-7.0-31-10
X-imss-scan-details: No--9.278-7.0-31-10;No--9.278-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 03:28:43 -0000

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