Re: [rrg] Aggregatable EIDs
Xu Xiaohu <xuxh@huawei.com> Mon, 28 December 2009 01:18 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 A20433A685E for <rrg@core3.amsl.com>; Sun, 27 Dec 2009 17:18:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.907
X-Spam-Level:
X-Spam-Status: No, score=0.907 tagged_above=-999 required=5 tests=[AWL=0.517, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 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 EL7pJlv5ahpL for <rrg@core3.amsl.com>; Sun, 27 Dec 2009 17:18:13 -0800 (PST)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id 7CD183A6783 for <rrg@irtf.org>; Sun, 27 Dec 2009 17:18:12 -0800 (PST)
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 <0KVC00GMJ8XHRW@szxga04-in.huawei.com> for rrg@irtf.org; Mon, 28 Dec 2009 09:17:41 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KVC000TG8XGKY@szxga04-in.huawei.com> for rrg@irtf.org; Mon, 28 Dec 2009 09:17:40 +0800 (CST)
Received: from HUAWEIE75F8F11 ([10.111.12.116]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KVC00AGQ8XG78@szxml04-in.huawei.com> for rrg@irtf.org; Mon, 28 Dec 2009 09:17:40 +0800 (CST)
Date: Mon, 28 Dec 2009 09:17:41 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <c6a.64e0c78b.3868bd93@aol.com>
To: HeinerHummel@aol.com, brian.e.carpenter@gmail.com, zhangwei734@gmail.com
Message-id: <000f01ca875b$8d8c8250$740c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: multipart/alternative; boundary="Boundary_(ID_LY+cgAVsj5Rov9tmP7N8qg)"
Thread-index: AcqG+f1prGl8adFhQgqOYWZAxC6GnwAYCEOw
Cc: rrg@irtf.org
Subject: Re: [rrg] Aggregatable EIDs
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: Mon, 28 Dec 2009 01:18:16 -0000
_____ 发件人: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] 代表 HeinerHummel@aol.com 发送时间: 2009年12月27日 21:40 收件人: brian.e.carpenter@gmail.com; zhangwei734@gmail.com 抄送: rrg@irtf.org 主题: Re: [rrg] Aggregatable EIDs In einer eMail vom 26.12.2009 20:34:56 Westeuropäische Normalzeit schreibt brian.e.carpenter@gmail.com: This argument fails for exactly the same reason that geographically based BGP aggregation fails. Brian, who has ever done it ? Why do you say this and what do you mean by saying this ? It must be something quite different from what I understand. This thread "Aggregatable EIDs" is concerned about aggregating EIDs and the problems with mapping the prefixes to RLOCs. This objective wouldn't even exist if both EID and RLOC-ID are asigned a "third" information (I proposed it not long ago) which itself is universally routable and which wouldn't need any authoritative provisioner either. No need for aggregating any two EIDs! No need for mapping any EID-IP-address to any RLOC-IP-address provided that they share a common attribute that is derived from geographical coordinates. By sticking to non-routable identifiers none of the 14 solutions becomes any better than LISP. Note, not only IPv4 / IPv6 addresses are non-routable, AS numbers aren't either. With 99 % of the hosts being mobile, wouldn't it be appropriate to have mainly provider-independent FQDNs and a DNS that is fairly up-to-date with the correlation between a respective HIT and the current location, i.e. completely independent of the current AS? Since the HIT is already a provider-independent host identifier, why should each host be assigned with a FQDN as another provider-independent ID? Taken the current cell-phone mobile network as an example, does every cell-phone need a FQDN-like global name besides the cell-phone number itself? Xiaohu The geographic coordinates would be the only non-mobile data in a world of mobile hosts, mobile routers and fast changed providers Heiner
- Re: [rrg] Aggregatable EIDs HeinerHummel
- Re: [rrg] Aggregatable EIDs Xu Xiaohu
- Re: [rrg] Aggregatable EIDs Brian E Carpenter
- Re: [rrg] Aggregatable EIDs tvest
- Re: [rrg] Aggregatable EIDs HeinerHummel
- Re: [rrg] Aggregatable EIDs HeinerHummel
- Re: [rrg] Aggregatable EIDs Peter Sherbin
- Re: [rrg] Aggregatable EIDs tvest
- Re: [rrg] Aggregatable EIDs Tony Li
- Re: [rrg] Aggregatable EIDs Xu Xiaohu
- Re: [rrg] Aggregatable EIDs HeinerHummel
- Re: [rrg] Aggregatable EIDs HeinerHummel
- Re: [rrg] Aggregatable EIDs Tony Li
- Re: [rrg] Aggregatable EIDs HeinerHummel
- Re: [rrg] Aggregatable EIDs Tony Li
- [rrg] Aggregatable EIDs hummelresearch
- Re: [rrg] Aggregatable EIDs Tony Li
- Re: [rrg] Aggregatable EIDs heinerhummel
- Re: [rrg] Aggregatable EIDs Lixia Zhang
- Re: [rrg] Aggregatable EIDs Noel Chiappa
- Re: [rrg] Aggregatable EIDs heinerhummel
- Re: [rrg] Aggregatable EIDs Darrel Lewis (darlewis)
- Re: [rrg] Aggregatable EIDs heinerhummel
- [rrg] Aggregatable EIDs heinerhummel
- [rrg] Embedding geo info in PA addresses=>A compr… Xu Xiaohu