Re: [hiprg] HIPRG charter discussion

Xu Xiaohu <xuxh@huawei.com> Tue, 07 June 2011 03:32 UTC

Return-Path: <xuxh@huawei.com>
X-Original-To: hiprg@ietfa.amsl.com
Delivered-To: hiprg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B45A41F0C4A for <hiprg@ietfa.amsl.com>; Mon, 6 Jun 2011 20:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.81
X-Spam-Level:
X-Spam-Status: No, score=-3.81 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-4]
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 KmB-m0u9Iwn8 for <hiprg@ietfa.amsl.com>; Mon, 6 Jun 2011 20:32:34 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by ietfa.amsl.com (Postfix) with ESMTP id 905251F0C46 for <hiprg@irtf.org>; Mon, 6 Jun 2011 20:32:34 -0700 (PDT)
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 <0LME00CCFHQBNT@szxga03-in.huawei.com> for hiprg@irtf.org; Tue, 07 Jun 2011 11:30:12 +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 <0LME0073ZHQB65@szxga03-in.huawei.com> for hiprg@irtf.org; Tue, 07 Jun 2011 11:30:11 +0800 (CST)
Received: from x41208c ([10.110.98.38]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0LME00BO2HQBPC@szxml04-in.huawei.com> for hiprg@irtf.org; Tue, 07 Jun 2011 11:30:11 +0800 (CST)
Date: Tue, 07 Jun 2011 11:40:08 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <7CC566635CFE364D87DC5803D4712A6C4CEED71928@XCH-NW-10V.nw.nos.boeing.com>
To: "'Henderson, Thomas R'" <thomas.r.henderson@boeing.com>, hiprg@irtf.org
Message-id: <005601cc24c4$99060400$cb120c00$@com>
MIME-version: 1.0
X-Mailer: Microsoft Office Outlook 12.0
Content-type: text/plain; charset=gb2312
Content-language: zh-cn
Content-transfer-encoding: quoted-printable
Thread-index: AcwbdHKRVBFnMmtlTNKxL9WSddMpLQATwbNwAiShFbAAAJiHoAAAAWkAAAANkXAAGEFK8A==
References: <7CC566635CFE364D87DC5803D4712A6C4CEED71928@XCH-NW-10V.nw.nos.boeing.com>
Cc: irtf-chair@irsg.org
Subject: Re: [hiprg] HIPRG charter discussion
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/hiprg>, <mailto:hiprg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/hiprg>
List-Post: <mailto:hiprg@irtf.org>
List-Help: <mailto:hiprg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/hiprg>, <mailto:hiprg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Jun 2011 03:32:35 -0000

Hi Tom and all,

I propose to consider taking the hierarchical HIT research as a new charter
item. IMHO, there are at least two major benefits of using hierarchical HITs
from the commercial deployment perspectives:

First, the ID/HIT registration management service and the ID-to-Locator
mapping service corresponding to the hierarchical HITs could be run in a
hierarchical manner. In other words, such global mobility management service
systems could be operated by different countries and different operators
with clear administrative domain boundaries and reasonable business models,
just like the telephone number space in the telephone network and the home
address space in the mobile IP network. In addition, the existing DNS
infrastructure doesn't need to be changed largely. That's to say, HITs of
the HIP hosts could be stored directly as their corresponding AAAA RRs in
the existing DNS infrastructure.

Second, the usage of hierarchical HITs will ease the transition for HIP. For
instance, legacy IPv6 hosts could access mobile HIP hosts via provider-owned
HIP proxy devices (just as home agents in the mobile IP network) since the
hierarchical HITs could be routable in the Internet. On the contrary,
ORCHIDs are not routable in the Internet since there is no reasonable
business motivation for operators to deploy HIP proxy devices for such flat
identifiers.

There has been some proposals and presentations discussing about
hierarchical HITs in HIPRG before as follows:
http://tools.ietf.org/html/draft-xu-hip-hierarchical-02
http://tools.ietf.org/html/draft-kuptsov-hhit-02
http://tools.ietf.org/html/draft-xu-rangi-04

By the way, we have implemented the RANGI
(http://tools.ietf.org/html/draft-xu-rangi-04) prototype which uses a
hierarchical and cryptographic host IDs with delegation-oriented structure.
Hope we could have a chance to show the implementation details and
verification results at the forthcoming IETF meeting in Quebec City.

Best regards,
Xiaohu


> -----邮件原件-----
> 发件人: hiprg-bounces@irtf.org [mailto:hiprg-bounces@irtf.org] 代表
> Henderson, Thomas R
> 发送时间: 2011年6月6日 22:49
> 收件人: hiprg@irtf.org
> 抄送: 'irtf-chair@irsg.org'
> 主题: [hiprg] HIPRG charter discussion
> 
> With the completion of the experiment report (our main RG charter item
since
> the RG's inception), I would like to ask about future directions of the
RG.
> Outside of completing our current RG drafts, we need to try to define some
> new collaborative work items and define what role the RG will play
relative to
> the WG.
> 
> These work items should ideally satisfy the following criteria:
> - is the research area clear and relevant for the Internet community and
for
> HIP in particular?  What are the expected outcomes and impact?
> - will the RG foster work that would not be done otherwise?  For instance,
> participation drawn from more than a single institution or country.  Can
we
> try to identify individuals for this anticipated participation?
> 
> We can have some discussion of this at the next meeting but I would like
to see
> whether we can start identifying some topics on the list before the
meeting.
> 
> - Tom
> _______________________________________________
> hiprg mailing list
> hiprg@irtf.org
> https://www.irtf.org/mailman/listinfo/hiprg