
From guyingjie@huawei.com  Sun May 30 23:22:49 2010
Return-Path: <guyingjie@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 4BB943A69D5 for <decade@core3.amsl.com>; Sun, 30 May 2010 23:22:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 4.666
X-Spam-Level: ****
X-Spam-Status: No, score=4.666 tagged_above=-999 required=5 tests=[AWL=2.561,  BAYES_50=0.001, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
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 YN+JuH-gfRNN for <decade@core3.amsl.com>; Sun, 30 May 2010 23:22:48 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 3FF183A69DD for <decade@ietf.org>; Sun, 30 May 2010 23:22:48 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3900EX8TPB96@szxga02-in.huawei.com> for decade@ietf.org; Mon, 31 May 2010 14:22:23 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L3900KJ3TPB5U@szxga02-in.huawei.com> for decade@ietf.org; Mon, 31 May 2010 14:22:23 +0800 (CST)
Received: from g00107907 ([10.138.84.88]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L390012NTPBBV@szxml04-in.huawei.com> for decade@ietf.org; Mon, 31 May 2010 14:22:23 +0800 (CST)
Date: Mon, 31 May 2010 14:22:22 +0800
From: "Y.J. Gu" <guyingjie@huawei.com>
In-reply-to: <k2j8b2769931004271504y218407b4me54fa5e764190e61@mail.gmail.com>
To: 'DECADE' <decade@ietf.org>
Message-id: <003d01cb0089$a194e380$58548a0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=UTF-8
Content-transfer-encoding: 7BIT
Thread-index: AcrmVcoN0RMvJtSfQpSqXilPV0jWVQaMrtoA
Subject: [decade] Naming mechanism.
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: Mon, 31 May 2010 06:22:49 -0000

Hi all,
At IETF #77, naming mechanism was proposed to be considered in Requirement draft. Are there anyone familiar with naming mechanism of NFS, WebDAV, etc. and is willing to post brief introduction in the mailing list? Thanks in advance. :)

