[decade] WG review of draft-ietf-decade-problem-statement-01

Ning Zong <zongning@huawei.com> Tue, 28 December 2010 08:23 UTC

Return-Path: <zongning@huawei.com>
X-Original-To: decade@core3.amsl.com
Delivered-To: decade@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9D56B28C0DE for <decade@core3.amsl.com>; Tue, 28 Dec 2010 00:23:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.077
X-Spam-Level:
X-Spam-Status: No, score=-100.077 tagged_above=-999 required=5 tests=[AWL=0.417, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_MESSAGE=0.001, 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 vs1QGiitx9mc for <decade@core3.amsl.com>; Tue, 28 Dec 2010 00:23:24 -0800 (PST)
Received: from szxga01-in.huawei.com (unknown [119.145.14.64]) by core3.amsl.com (Postfix) with ESMTP id E08DF28C0DF for <decade@ietf.org>; Tue, 28 Dec 2010 00:23:23 -0800 (PST)
Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LE4002VMQ267G@szxga05-in.huawei.com> for decade@ietf.org; Tue, 28 Dec 2010 16:25:18 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LE400JYBQ2656@szxga05-in.huawei.com> for decade@ietf.org; Tue, 28 Dec 2010 16:25:18 +0800 (CST)
Received: from z63316a ([10.138.41.69]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LE4007JIQ215S@szxml06-in.huawei.com> for decade@ietf.org; Tue, 28 Dec 2010 16:25:18 +0800 (CST)
Date: Tue, 28 Dec 2010 16:25:13 +0800
From: Ning Zong <zongning@huawei.com>
To: decade@ietf.org
Message-id: <000001cba668$bfede680$3fc9b380$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: multipart/alternative; boundary="Boundary_(ID_vlBD2WhjrMmBxb111gDahA)"
Content-language: zh-cn
Thread-index: AcumaL+Jp0ZTa+vESBeZZYBUDX08WA==
Subject: [decade] WG review of draft-ietf-decade-problem-statement-01
X-BeenThere: decade@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "To start the discussion on DECoupled Application Data Enroute, to discuss the in-network data storage for p2p applications and its access protocol" <decade.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/decade>, <mailto:decade-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/decade>
List-Post: <mailto:decade@ietf.org>
List-Help: <mailto:decade-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/decade>, <mailto:decade-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Dec 2010 08:23:28 -0000

(As a reviewer)

 

Just a few update suggestions:

1)       In clause 1, paragraph 5, it would be better to briefly introduce
what DECADE is before using this term. We can add some text before paragraph
5 as follows:

"In this document, DECADE is defined as a standard interface for various P2P
applications to access storage and data transport services in the network to
improve their efficiency and reduce the stress on the network
infrastructure."

 

2)       In clause 4, it would be better to explicitly clarify "DECADE" and
"IAP" in some places to reduce the potential confusion to new readers. We
can update some text as follows:

2.1) paragraph 1 changes to:

"The objective of this working group is to design DECADE, which mainly
consists of an in-network storage access protocol (IAP) to address the
problems discussed in the preceding section."

2.2) clause 4.1, the first sentence changes to:

"P2P application clients use the IAP protocol to read data from an
in-network storage, store data to an in-network storage, or remove data from
an in-network storage."

2.3) clause 4.3, the first sentence changes to:

"A user uses the IAP protocol to manage the resources on in-network storage
that can be used by other peers, e.g., the bandwidth or connections."

 

3)       In clause 9.2, we need to update the fourth reference to:

[I-D.ietf-ppsp-problem-statement] Zhang, Y., Zong, N., Camarillo, G., Seng,
J., and Y. Yang, "Problem Statement of P2P Streaming Protocol (PPSP)",
draft-ietf-ppsp-problem-statement-00 (work in progress), October 2010.

 

BR,

Ning Zong