[decade] Review of draft-ietf-decade-problem-statement-01
Roni Even <Even.roni@huawei.com> Thu, 23 December 2010 10:54 UTC
Return-Path: <Even.roni@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 D40043A6C09 for <decade@core3.amsl.com>; Thu, 23 Dec 2010 02:54:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.789
X-Spam-Level:
X-Spam-Status: No, score=-103.789 tagged_above=-999 required=5 tests=[AWL=0.706, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4, 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 ScNyhDdXvBg8 for <decade@core3.amsl.com>; Thu, 23 Dec 2010 02:54:26 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 098BF3A6C07 for <decade@ietf.org>; Thu, 23 Dec 2010 02:54:26 -0800 (PST)
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 <0LDV00DJ4NPR8H@szxga03-in.huawei.com> for decade@ietf.org; Thu, 23 Dec 2010 18:56:15 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LDV00C1QNPRDA@szxga03-in.huawei.com> for decade@ietf.org; Thu, 23 Dec 2010 18:56:15 +0800 (CST)
Received: from windows8d787f9 (bzq-79-179-38-112.red.bezeqint.net [79.179.38.112]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LDV007YVNPLWL@szxml01-in.huawei.com> for decade@ietf.org; Thu, 23 Dec 2010 18:56:15 +0800 (CST)
Date: Thu, 23 Dec 2010 12:53:16 +0200
From: Roni Even <Even.roni@huawei.com>
In-reply-to: <057E4696615D964AB8053E9EE5DCD3D401987E5E@szxeml508-mbx.china.huawei.com>
To: decade@ietf.org
Message-id: <004401cba28f$9e2837d0$da78a770$%roni@huawei.com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset="us-ascii"
Content-language: en-us
Content-transfer-encoding: 7bit
Thread-index: AQHLoBsWGwto/KxaokmthCLD/scUBpOpE0nAgATJagA=
References: <057E4696615D964AB8053E9EE5DCD3D401987E5E@szxeml508-mbx.china.huawei.com>
Subject: [decade] 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: Thu, 23 Dec 2010 10:54:26 -0000
Hi, In general it looks good. I have a question about the flow in section 5.4.1. It shows that Sb can perform IAP operation. I am not sure I noticed that the in network storage can also perform the DECADE protocol. Now if it can do it than how does B know when the data is available at Sb in order to get it. In the security consideration it is not specified but I assume that the access control is used also to prevent unauthorized user from getting the content on the in network storage. Roni Even