[rrg] Some concerns about ILNP

Xu Xiaohu <xuxh@huawei.com> Fri, 31 July 2009 08:23 UTC

Return-Path: <xuxh@huawei.com>
X-Original-To: rrg@core3.amsl.com
Delivered-To: rrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B45A728C2F2 for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 01:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.28
X-Spam-Level:
X-Spam-Status: No, score=0.28 tagged_above=-999 required=5 tests=[AWL=-0.024, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, SARE_SUB_RAND_LETTRS4=0.799]
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 lTs73ep8cor6 for <rrg@core3.amsl.com>; Fri, 31 Jul 2009 01:23:26 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id 3527228C28A for <rrg@irtf.org>; Fri, 31 Jul 2009 01:23:25 -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 <0KNN000000JW8R@szxga03-in.huawei.com> for rrg@irtf.org; Fri, 31 Jul 2009 16:21:32 +0800 (CST)
Received: from x41208a ([10.111.12.94]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KNN00N0I0JV3C@szxga03-in.huawei.com> for rrg@irtf.org; Fri, 31 Jul 2009 16:21:32 +0800 (CST)
Date: Fri, 31 Jul 2009 16:21:31 +0800
From: Xu Xiaohu <xuxh@huawei.com>
To: rja@extremenetworks.com
Message-id: <004201ca11b7$e8f30b10$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="UTF-8"
Content-transfer-encoding: quoted-printable
Thread-index: AcoRt+iHrYYXRMbrTlaM9enzktGB3Q==
Cc: 'IRTF RRG' <rrg@irtf.org>
Subject: [rrg] Some concerns about ILNP
X-BeenThere: rrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IRTF Routing Research Group <rrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/rrg>
List-Post: <mailto:rrg@irtf.org>
List-Help: <mailto:rrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/rrg>, <mailto:rrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Jul 2009 08:23:26 -0000

Hi Ran,

If I understand your ILNP correctly, it is much silimar with the GSE.  If so, I'm wondering whether the issues with the GSE described in draft-ietf-ipngwg-esd-analysis  have been successfully solved by the ILNP, e.g., identifier authentication issue. It seems that  the answers to these hard issues have not been mentioned in your slides.

I noticed the following statement in your slides, do you believe that 62-bit field is long enough to prevent the security of the binding of the 62-bit hash value and the public key from being easily compromised once you use the HIP/CGA like ideas to deal with the identifier authentication issue?

*********************************
If scope bit is local, have 62 bits that can be anything:
‣ Cryptographically Generated Identifier (a la CGA proposals)
‣ Hash of a public-key (a la HIP)
‣ Pseudo-randomly generated (a la IPv6 Privacy AutoConf)
**********************************

Best regard,

Xiaohu