
From xuxh@huawei.com  Thu Jul 23 20:14:04 2009
Return-Path: <xuxh@huawei.com>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3C02E3A6B92 for <hiprg@core3.amsl.com>; Thu, 23 Jul 2009 20:14:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.095
X-Spam-Level: 
X-Spam-Status: No, score=-0.095 tagged_above=-999 required=5 tests=[AWL=-0.285, BAYES_00=-2.599, CN_BODY_35=0.339, MIME_CHARSET_FARAWAY=2.45]
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 M-uzRGawAXhd for <hiprg@core3.amsl.com>; Thu, 23 Jul 2009 20:14:03 -0700 (PDT)
Received: from szxga04-in.huawei.com (szxga04-in.huawei.com [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 5542C3A695F for <hiprg@irtf.org>; Thu, 23 Jul 2009 20:13:29 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KN9001K1MF44J@szxga04-in.huawei.com> for hiprg@irtf.org; Fri, 24 Jul 2009 10:47:29 +0800 (CST)
Received: from x41208a ([10.111.12.94]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KN9006P2MF4IB@szxga04-in.huawei.com> for hiprg@irtf.org; Fri, 24 Jul 2009 10:47:28 +0800 (CST)
Date: Fri, 24 Jul 2009 10:47:26 +0800
From: Xu Xiaohu <xuxh@huawei.com>
To: hiprg@irtf.org
Message-id: <002f01ca0c09$147fcfc0$5e0c6f0a@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=gb2312
Content-transfer-encoding: quoted-printable
Thread-index: AcoDZGzFOCUVdKrQRDeVykxGPcfwDgAAxoTQAAJMabACJWT2AA==
Subject: [hiprg] fwd: [rrg] New Version Notification for draft-xu-rangi-proxy-01
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/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: Fri, 24 Jul 2009 03:14:04 -0000

Hi all,

I just updated the draft of the proxy mechanism for RANGI
(http://www.ietf.org/internet-drafts/draft-xu-rangi-proxy-01.txt), a =
kind of
id/locator split approach.  Since I believe most parts of the proxy
mechanisms described in this draft can also be suitable for HIP,  I  =
mention
it here, too.

The major changes from the -00 version are as follows (note: the -00 =
draft
had been presented on the HIPRG session of IETF74):

1. Except of the site proxy mechanism defined in the -00 version,  a =
transit
proxy mechanism is introduced to support communications from legacy IPv6
hosts to RANGI hosts in the scenario where the legacy site network has =
not
yet deployed any site proxy.  With this mechanism, the transit proxies =
are
deployed in the transit networks by ISPs and the identifier-based =
routing is
also supported in the transit netwroks. To some extent, the transit =
proxy is
similar to the APR in the VA
(http://tools.ietf.org/html/draft-ietf-grow-va-00) and the PTR in the =
LISP.

2.  For RANGI hosts to initiate communications with the legacy hosts in =
the
above scenario, the RANGI hosts will establish sessions in the =
traditional
IPv6 fashion once they recognizes that the identifiers of the =
destination
hosts are IPv6 addresses (i.e. locators).

Any comments are welcome.

Xiaohu

=20

> -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> =B7=A2=BC=FE=C8=CB: Xu Xiaohu [mailto:xuxh@huawei.com]=20
> =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA7=D4=C213=C8=D5 12:17
> =CA=D5=BC=FE=C8=CB: 'Xu Xiaohu'; 'IRTF RRG'
> =D6=F7=CC=E2: =B4=F0=B8=B4: [rrg] New Version Notification for =
draft-xu-rangi-proxy-01
>=20
>=20
> The link is attached.=20
> http://www.ietf.org/internet-drafts/draft-xu-rangi-proxy-01.txt
>=20
> Xiaohu
> =20
>=20
> > -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> > =B7=A2=BC=FE=C8=CB: rrg-bounces@irtf.org =
[mailto:rrg-bounces@irtf.org] =B4=FA=B1=ED Xu
Xiaohu
> > =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA7=D4=C213=C8=D5 11:42
> > =CA=D5=BC=FE=C8=CB: 'IRTF RRG'
> > =D6=F7=CC=E2: Re: [rrg] New Version Notification for =
draft-xu-rangi-proxy-01
> >=20
> > Hi all,
> >=20
> > A updated version of draft-xu-rangi-proxy has just been submitted.=20
> > This document describes some transition mechanisms for the RANGI=20
> > (Routing Architecture for the Next Generation
> > Internet) . The major changes from the -00 version are as follows:
> >=20
> > 1. Except of the site proxy mechanism defined in the -00=20
> version,  a=20
> > transit proxy mechanism is introduced to support=20
> communications from=20
> > legacy IPv6 hosts to RANGI hosts in the scenario where the=20
> legacy site=20
> > network has not yet deployed any site proxy.  With this=20
> mechanism, the=20
> > transit proxies are deployed in the transit networks by=20
> ISPs and the=20
> > identifier-based routing is also supported in the transit=20
> netwroks. To=20
> > some extent, the transit proxy is similar to the APR in the VA
> > (http://tools.ietf.org/html/draft-ietf-grow-va-00) and the=20
> PTR in the=20
> > LISP.
> >=20
> > 2.  For RANGI hosts to initiate communications with the=20
> legacy hosts=20
> > in the above scenario, the RANGI hosts will establish=20
> sessions in the=20
> > traditional
> > IPv6 fashion once they recognizes that the identifiers of the=20
> > destination hosts are IPv6 addresses (i.e. locators).
> >=20
> > 3. Some editorial updates.
> >=20
> > Any comments are welcome.
> >=20
> > Xiaohu
> > =20
> >=20
> > > -----=D3=CA=BC=FE=D4=AD=BC=FE-----
> > > =B7=A2=BC=FE=C8=CB: IETF I-D Submission Tool =
[mailto:idsubmission@ietf.org]
> > > =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA7=D4=C213=C8=D5 10:48
> > > =CA=D5=BC=FE=C8=CB: xuxh@huawei.com
> > > =D6=F7=CC=E2: New Version Notification for draft-xu-rangi-proxy-01
> > >=20
> > >=20
> > > A new version of I-D, draft-xu-rangi-proxy-01.txt has been
> > successfuly
> > > submitted by Xiaohu Xu and posted to the IETF repository.
> > >=20
> > > Filename:	 draft-xu-rangi-proxy
> > > Revision:	 01
> > > Title:		 Transition Mechanisms for Routing=20
> > > Architecture for the Next Generation Internet (RANGI)
> > > Creation_date:	 2009-07-13
> > > WG ID:		 Independent Submission
> > > Number_of_pages: 9
> > >=20
> > > Abstract:
> > > The Routing Architecture for the Next Generation Internet
> > > (RANGI) described in [RANGI] is a proposal for solving routing=20
> > > scalability, mobility, multihoming, traffic engineering and other=20
> > > issues facing the current Internet.
> > > This document describes some transition mechanisms for the
> > RANGI. With
> > > these mechanisms, legacy IPv4 and IPv6 hosts can communicate with=20
> > > RANGI hosts, and vice versa.
> > >                                                              =20
> > >                    =20
> > >=20
> > >=20
> > > The IETF Secretariat.
> > >=20
> > >=20
> >=20
> > _______________________________________________
> > rrg mailing list
> > rrg@irtf.org
> > http://www.irtf.org/mailman/listinfo/rrg
> >=20


From gurtov@cs.helsinki.fi  Mon Jul 27 01:19:51 2009
Return-Path: <gurtov@cs.helsinki.fi>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0D4743A6C05 for <hiprg@core3.amsl.com>; Mon, 27 Jul 2009 01:19:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 coNc1i1IU9j3 for <hiprg@core3.amsl.com>; Mon, 27 Jul 2009 01:19:50 -0700 (PDT)
Received: from mail.cs.helsinki.fi (courier.cs.helsinki.fi [128.214.9.1]) by core3.amsl.com (Postfix) with ESMTP id F30153A6C04 for <hiprg@irtf.org>; Mon, 27 Jul 2009 01:19:49 -0700 (PDT)
Received: from [78.64.88.124] (host-78-64-88-124.homerun.telia.com [78.64.88.124]) (AUTH: PLAIN gurtov, SSL: TLSv1/SSLv3,256bits,AES256-SHA) by mail.cs.helsinki.fi with esmtp; Mon, 27 Jul 2009 11:19:49 +0300 id 00063DD3.4A6D6325.00004E7E
Message-ID: <4A6D6322.9080104@cs.helsinki.fi>
Date: Mon, 27 Jul 2009 11:19:46 +0300
From: Andrei Gurtov <gurtov@cs.helsinki.fi>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: hiprg@irtf.org
X-Enigmail-Version: 0.96.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Subject: [hiprg] agenda for IETF'75
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/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: Mon, 27 Jul 2009 08:19:51 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

The updated agenda for HIPRG meeting on Tuesday has been posted
http://www.ietf.org/proceedings/75/agenda/HIPRG.txt

Since the agenda is pretty full, I request the presenters to mail me the
slides in advance to avoid A/V glitches.

Let's hope we have a productive discussion on the role of HIP in
Internet of Things, hierarchical HIP, as well as other agenda topics.

BR
Andrei
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkptYyIACgkQP7jp0uceFkQ9cwCfT7bNzrqOBK2WfAzmXj15eaaD
InkAn1hvpg44KJxfM6h5vSs8aMLgQjCI
=OonG
-----END PGP SIGNATURE-----

From heer@informatik.rwth-aachen.de  Tue Jul 28 06:02:03 2009
Return-Path: <heer@informatik.rwth-aachen.de>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A79963A6F54 for <hiprg@core3.amsl.com>; Tue, 28 Jul 2009 06:02:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.001
X-Spam-Level: 
X-Spam-Status: No, score=-4.001 tagged_above=-999 required=5 tests=[AWL=-0.400, BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, J_CHICKENPOX_16=0.6, J_CHICKENPOX_19=0.6, RCVD_IN_DNSWL_MED=-4]
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 aECAbY3AXXqY for <hiprg@core3.amsl.com>; Tue, 28 Jul 2009 06:02:03 -0700 (PDT)
Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by core3.amsl.com (Postfix) with ESMTP id 6B2713A6F4E for <hiprg@irtf.org>; Tue, 28 Jul 2009 06:02:03 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Received: from ironport-out-2.rz.rwth-aachen.de ([134.130.5.41]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KNH00B99TJFYM70@mta-2.ms.rz.RWTH-Aachen.de> for hiprg@irtf.org; Tue, 28 Jul 2009 15:02:03 +0200 (CEST)
X-IronPort-AV: E=Sophos;i="4.43,283,1246831200";   d="scan'208";a="11204973"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-2.rz.rwth-aachen.de with ESMTP; Tue, 28 Jul 2009 15:02:03 +0200
Received: from dhcp-11f5.meeting.ietf.org ([unknown] [130.129.17.245]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KNH0050OTJF4B70@relay-auth-1.ms.rz.rwth-aachen.de> for hiprg@irtf.org; Tue, 28 Jul 2009 15:02:03 +0200 (CEST)
Message-id: <C1CCBFC6-D133-4CCE-8ABF-3B7A88EC9B0B@cs.rwth-aachen.de>
From: Tobias Heer <heer@cs.rwth-aachen.de>
To: zhangdacheng@huawei.com, Xu Xiaohu <xuxh@huawei.com>
Date: Tue, 28 Jul 2009 15:02:00 +0200
X-Mailer: Apple Mail (2.935.3)
Cc: hiprg@irtf.org
Subject: [hiprg] draft-zhang-hip-hierarchical-parameter-00: Including hieararchy in HIT generation
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/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, 28 Jul 2009 13:02:03 -0000

Hi!

I just wanted to clarify my comment in the HIPRG meeting on including  
the hierarchy in the HIT creation process. I think it would be good to  
have the hierarchy information in the HIT creation process because the  
hierarchy will be bound to the HIT itself.

Below I briefly sketched a possible way of including it without  
revealing the hierarchy to all hosts.

HIT generation could work like this:

1. Pick random secret X

2. H(Hierarchy, X) => HTag

3. H(PubKey, ..., HTag) => HIT (Orchid)

--> Only use LTag if you do not want to reveal hierarchy.
--> Use hierarchy and X if you want to reveal the hierarchy.

The random secret X prevents dictionary attacks on a limited number of  
hierarchies. H is a hash function. Of course, you should not only use  
H for generating the HIT (step 3) but use the regular way defined in  
the RFCs. If you want to avoid that people can try many instances of X  
for creating many different HITs you can also make X depend on the  
public key, which will make creating many different HITs notably more  
complex.

Best regards,

Tobias



-- 
Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer








From heer@informatik.rwth-aachen.de  Tue Jul 28 07:29:43 2009
Return-Path: <heer@informatik.rwth-aachen.de>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 69FA93A6FCF for <hiprg@core3.amsl.com>; Tue, 28 Jul 2009 07:29:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.808
X-Spam-Level: 
X-Spam-Status: No, score=-1.808 tagged_above=-999 required=5 tests=[AWL=-2.392, BAYES_00=-2.599, CN_BODY_35=0.339, HELO_EQ_DE=0.35,  HELO_MISMATCH_DE=1.448, J_CHICKENPOX_16=0.6, J_CHICKENPOX_19=0.6, MIME_CHARSET_FARAWAY=2.45, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
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 87dUBncYjBVp for <hiprg@core3.amsl.com>; Tue, 28 Jul 2009 07:29:42 -0700 (PDT)
Received: from mta-1.ms.rz.rwth-aachen.de (mta-1.ms.rz.RWTH-Aachen.DE [134.130.7.72]) by core3.amsl.com (Postfix) with ESMTP id 75F6A3A6FB6 for <hiprg@irtf.org>; Tue, 28 Jul 2009 07:29:42 -0700 (PDT)
MIME-version: 1.0
Content-type: text/plain; charset=GB2312; format=flowed; delsp=yes
Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-1.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KNH005G5XLIJJ50@mta-1.ms.rz.RWTH-Aachen.de> for hiprg@irtf.org; Tue, 28 Jul 2009 16:29:42 +0200 (CEST)
X-IronPort-AV: E=Sophos;i="4.43,283,1246831200";   d="scan'208";a="20656426"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Tue, 28 Jul 2009 16:29:42 +0200
Received: from dhcp-11f5.meeting.ietf.org ([unknown] [130.129.17.245]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KNH0053KXLI4B80@relay-auth-1.ms.rz.rwth-aachen.de> for hiprg@irtf.org; Tue, 28 Jul 2009 16:29:42 +0200 (CEST)
Message-id: <59A80D41-60DA-4C54-8C4F-020FC26762E4@cs.rwth-aachen.de>
From: Tobias Heer <heer@cs.rwth-aachen.de>
To: hiprg@irtf.org
In-reply-to: <f96ac8d1255a3.255a3f96ac8d1@huawei.com>
Content-transfer-encoding: quoted-printable
Date: Tue, 28 Jul 2009 16:29:39 +0200
References: <C1CCBFC6-D133-4CCE-8ABF-3B7A88EC9B0B@cs.rwth-aachen.de> <f96ac8d1255a3.255a3f96ac8d1@huawei.com>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [hiprg] draft-zhang-hip-hierarchical-parameter-00: Including hieararchy in HIT generation
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/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, 28 Jul 2009 14:29:43 -0000

Hi Dacheng,

Am 28.07.2009 um 16:14 schrieb zhangdacheng 00133208:

> Hi, Tobias:
>
> I think you propose a very interesting solution. But, we still have =20=

> to face the problem, i.e., how to transfer the hierarchy information =20=

> and X in case they are needed in HIP header, do we?

Of course. In my opinion you still need an additional parameter to =20
express the hierarchy if you want to reveal the hierarchy to the peer. =20=

Additionally you need to transmit the "cloaked" or "hidden" hierarchy =20=

(Parameter X - the randomly picked value) whenever you want to conceal =20=

the hierarchy.

> In addtion, transporting hierarchical information in parameters can =20=

> be more flexible. Hierarchical information can be formated in many =20
> different ways, e.g., fqdn, nai..

Yes, I agree. I think can also work with the proposed HIT creation.

I am posting this reply to the list to let other people participate as =20=

well.

BR,

Tobias

>
> looking forward to have further discussions.
>
> BR
>
> Dacheng
>
> =
**************************************************************************=
****************
> This email and its attachments contain confidential information from =20=

> HUAWEI, which is intended only for the person or entity whose =20
> address is listed above. Any use of the information contained here =20
> in any way (including, but not limited to, total or partial =20
> disclosure, reproduction, or dissemination) by persons other than =20
> the intended recipient(s) is prohibited. If you receive this email =20
> in error, please notify the sender by phone or email
> immediately and delete it!
> =
**************************************************************************=
***************
>
> ----- =D4=AD=D3=CA=BC=FE -----
> =B7=A2=BC=FE=C8=CB: Tobias Heer <heer@cs.rwth-aachen.de>
> =C8=D5=C6=DA: =D0=C7=C6=DA=B6=FE, =C6=DF=D4=C2 28=C8=D5, 2009 =CF=C2=CE=E7=
3:02
> =D6=F7=CC=E2: draft-zhang-hip-hierarchical-parameter-00: Including =
hieararchy =20
> in HIT generation
> =CA=D5=BC=FE=C8=CB: zhangdacheng@huawei.com, Xu Xiaohu =
<xuxh@huawei.com>
> =B3=AD=CB=CD: hiprg@irtf.org
>
>> Hi!
>>
>> I just wanted to clarify my comment in the HIPRG meeting on
>> including
>> the hierarchy in the HIT creation process. I think it would be
>> good to
>> have the hierarchy information in the HIT creation process because
>> the
>> hierarchy will be bound to the HIT itself.
>>
>> Below I briefly sketched a possible way of including it without
>> revealing the hierarchy to all hosts.
>>
>> HIT generation could work like this:
>>
>> 1. Pick random secret X
>>
>> 2. H(Hierarchy, X) =3D> HTag
>>
>> 3. H(PubKey, ..., HTag) =3D> HIT (Orchid)
>>
>> --> Only use LTag if you do not want to reveal hierarchy.
>> --> Use hierarchy and X if you want to reveal the hierarchy.
>>
>> The random secret X prevents dictionary attacks on a limited
>> number of
>> hierarchies. H is a hash function. Of course, you should not only
>> use
>> H for generating the HIT (step 3) but use the regular way defined
>> in
>> the RFCs. If you want to avoid that people can try many instances
>> of X
>> for creating many different HITs you can also make X depend on the
>>
>> public key, which will make creating many different HITs notably
>> more
>> complex.
>>
>> Best regards,
>>
>> Tobias
>>
>>
>>
>> --=20
>> Dipl.-Inform. Tobias Heer, Ph.D. Student
>> Distributed Systems Group
>> RWTH Aachen University, Germany
>> tel: +49 241 80 207 76
>> web: http://ds.cs.rwth-aachen.de/members/heer
>>
>>
>>
>>
>>
>>
>>
>>




-- =20

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer








From heer@informatik.rwth-aachen.de  Tue Jul 28 07:32:12 2009
Return-Path: <heer@informatik.rwth-aachen.de>
X-Original-To: hiprg@core3.amsl.com
Delivered-To: hiprg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D2C453A7013 for <hiprg@core3.amsl.com>; Tue, 28 Jul 2009 07:32:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.723
X-Spam-Level: 
X-Spam-Status: No, score=-3.723 tagged_above=-999 required=5 tests=[AWL=0.478,  BAYES_00=-2.599, HELO_EQ_DE=0.35, HELO_MISMATCH_DE=1.448, J_CHICKENPOX_19=0.6, RCVD_IN_DNSWL_MED=-4]
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 VtEKPsCJvJC2 for <hiprg@core3.amsl.com>; Tue, 28 Jul 2009 07:32:12 -0700 (PDT)
Received: from mta-2.ms.rz.rwth-aachen.de (mta-2.ms.rz.RWTH-Aachen.DE [134.130.7.73]) by core3.amsl.com (Postfix) with ESMTP id 092F23A6FFE for <hiprg@irtf.org>; Tue, 28 Jul 2009 07:32:12 -0700 (PDT)
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Received: from ironport-out-1.rz.rwth-aachen.de ([134.130.5.40]) by mta-2.ms.rz.RWTH-Aachen.de (Sun Java(tm) System Messaging Server 6.3-7.04 (built Sep 26 2008)) with ESMTP id <0KNH00BI9XPONSD0@mta-2.ms.rz.RWTH-Aachen.de> for hiprg@irtf.org; Tue, 28 Jul 2009 16:32:12 +0200 (CEST)
X-IronPort-AV: E=Sophos;i="4.43,283,1246831200";   d="scan'208";a="20656777"
Received: from relay-auth-1.ms.rz.rwth-aachen.de (HELO relay-auth-1) ([134.130.7.78]) by ironport-in-1.rz.rwth-aachen.de with ESMTP; Tue, 28 Jul 2009 16:32:11 +0200
Received: from dhcp-11f5.meeting.ietf.org ([unknown] [130.129.17.245]) by relay-auth-1.ms.rz.rwth-aachen.de (Sun Java(tm) System Messaging Server 7.0-3.01 64bit (built Dec 9 2008)) with ESMTPA id <0KNH0054MXPN4B80@relay-auth-1.ms.rz.rwth-aachen.de> for hiprg@irtf.org; Tue, 28 Jul 2009 16:32:12 +0200 (CEST)
Message-id: <AA0AC784-BE7B-4C8C-B274-501F50D33D12@cs.rwth-aachen.de>
From: Tobias Heer <heer@cs.rwth-aachen.de>
To: hiprg@irtf.org
In-reply-to: <59A80D41-60DA-4C54-8C4F-020FC26762E4@cs.rwth-aachen.de>
Date: Tue, 28 Jul 2009 16:32:09 +0200
References: <C1CCBFC6-D133-4CCE-8ABF-3B7A88EC9B0B@cs.rwth-aachen.de> <f96ac8d1255a3.255a3f96ac8d1@huawei.com> <59A80D41-60DA-4C54-8C4F-020FC26762E4@cs.rwth-aachen.de>
X-Mailer: Apple Mail (2.935.3)
Subject: Re: [hiprg] draft-zhang-hip-hierarchical-parameter-00: Including hieararchy in HIT generation
X-BeenThere: hiprg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "Host Identity Protocol \(HIP\) Research Group" <hiprg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/listinfo/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, 28 Jul 2009 14:32:12 -0000

Hi,

Am 28.07.2009 um 16:29 schrieb Tobias Heer:

> Of course. In my opinion you still need an additional parameter to  
> express the hierarchy if you want to reveal the hierarchy to the  
> peer. Additionally you need to transmit the "cloaked" or "hidden"  
> hierarchy (Parameter X - the randomly picked value) whenever you  
> want to conceal the hierarchy.


I have to correct myself. Of course you should not transmit X in that  
case that you want to conceal your hierarchy but the HTag =  
H(Hierarchy, X).

BR,

Tobias


--  

Dipl.-Inform. Tobias Heer, Ph.D. Student
Distributed Systems Group
RWTH Aachen University, Germany
tel: +49 241 80 207 76
web: http://ds.cs.rwth-aachen.de/members/heer







