IETF Logo Mail Archive

Re: [rrg] Aggregatable EIDs

HeinerHummel@aol.com Tue, 29 December 2009 09:48 UTC

Return-Path: <HeinerHummel@aol.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 3B2E23A6778 for <rrg@core3.amsl.com>; Tue, 29 Dec 2009 01:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.639
X-Spam-Level:
X-Spam-Status: No, score=-0.639 tagged_above=-999 required=5 tests=[AWL=-0.730, BAYES_05=-1.11, HTML_MESSAGE=0.001, J_CHICKENPOX_33=0.6, J_CHICKENPOX_35=0.6]
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 irRnCmArMETv for <rrg@core3.amsl.com>; Tue, 29 Dec 2009 01:48:15 -0800 (PST)
Received: from imr-mb01.mx.aol.com (imr-mb01.mx.aol.com [64.12.207.164]) by core3.amsl.com (Postfix) with ESMTP id 61F553A6767 for <rrg@irtf.org>; Tue, 29 Dec 2009 01:48:14 -0800 (PST)
Received: from imo-ma03.mx.aol.com (imo-ma03.mx.aol.com [64.12.78.138]) by imr-mb01.mx.aol.com (8.14.1/8.14.1) with ESMTP id nBT9leLa031827; Tue, 29 Dec 2009 04:47:40 -0500
Received: from HeinerHummel@aol.com by imo-ma03.mx.aol.com (mail_out_v42.5.) id p.c15.52f2a5ce (29672); Tue, 29 Dec 2009 04:47:36 -0500 (EST)
From: HeinerHummel@aol.com
Message-ID: <c15.52f2a5ce.386b2a85@aol.com>
Date: Tue, 29 Dec 2009 04:48:53 -0500
To: xuxh@huawei.com, jmh@joelhalpern.com, brian.e.carpenter@gmail.com
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="-----------------------------1262080133"
X-Mailer: 9.0 SE for Windows sub 5021
X-AOL-SENDER: HeinerHummel@aol.com
Cc: rrg@irtf.org, zhangwei734@gmail.com
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: Tue, 29 Dec 2009 09:48:16 -0000

In einer eMail vom 29.12.2009 03:22:02 Westeuropäische Normalzeit schreibt  
xuxh@huawei.com:

Two  points of clarification:
> 1) EIDs need to be aggregatable only if they  are used as look up keys.
> If they are never the key for a lookup (and  some proposals have that
> property) then aggregatability is a  non-issue.
Yes,yes,yes.And if they aren't used they can be whatever they may: IPv4,  
IPv6, HIT,names,E164-numbers (without enum-mapping), etc.
 
The networking layer deserves a routable SOMETHING (as to avoid the  term 
"identifier") for its own purposes.See above: the above layers would  
benefit, too.
 
Heiner

v2.23.0 | Report a Bug | By Email