IETF Logo Mail Archive

Re: [rrg] LEIDs, SPI & ordinary IP addresses as both IDs & Locs

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 19 February 2010 16:45 UTC

Return-Path: <Fred.L.Templin@boeing.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 460DD28C0FB for <rrg@core3.amsl.com>; Fri, 19 Feb 2010 08:45:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.568
X-Spam-Level:
X-Spam-Status: No, score=-6.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 dZjHffPvpMyn for <rrg@core3.amsl.com>; Fri, 19 Feb 2010 08:45:03 -0800 (PST)
Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by core3.amsl.com (Postfix) with ESMTP id 4D86528C262 for <rrg@irtf.org>; Fri, 19 Feb 2010 08:45:03 -0800 (PST)
Received: from blv-av-01.boeing.com (blv-av-01.boeing.com [130.247.48.231]) by blv-smtpout-01.ns.cs.boeing.com (8.14.4/8.14.4/8.14.4/SMTPOUT) with ESMTP id o1JGknk9021109 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 19 Feb 2010 08:46:49 -0800 (PST)
Received: from blv-av-01.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_RELAY) with ESMTP id o1JGknBf010799; Fri, 19 Feb 2010 08:46:49 -0800 (PST)
Received: from XCH-NWHT-11.nw.nos.boeing.com (xch-nwht-11.nw.nos.boeing.com [130.247.25.114]) by blv-av-01.boeing.com (8.14.4/8.14.4/UPSTREAM_RELAY) with ESMTP id o1JGknGl010779 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=OK); Fri, 19 Feb 2010 08:46:49 -0800 (PST)
Received: from XCH-NW-01V.nw.nos.boeing.com ([130.247.64.120]) by XCH-NWHT-11.nw.nos.boeing.com ([130.247.25.114]) with mapi; Fri, 19 Feb 2010 08:46:49 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>, "rrg@irtf.org" <rrg@irtf.org>
Date: Fri, 19 Feb 2010 08:46:48 -0800
Thread-Topic: [rrg] LEIDs, SPI & ordinary IP addresses as both IDs & Locs
Thread-Index: Acqxgle/u5ZaXRliTd+pG47klYzgoQAAHKbA
Message-ID: <E1829B60731D1740BB7A0626B4FAF0A649510C8803@XCH-NW-01V.nw.nos.boeing.com>
References: <20100219164103.6B91A6BE5B6@mercury.lcs.mit.edu>
In-Reply-To: <20100219164103.6B91A6BE5B6@mercury.lcs.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [rrg] LEIDs, SPI & ordinary IP addresses as both IDs & Locs
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, 19 Feb 2010 16:45:04 -0000

Noel,

> -----Original Message-----
> From: rrg-bounces@irtf.org [mailto:rrg-bounces@irtf.org] On Behalf Of Noel Chiappa
> Sent: Friday, February 19, 2010 8:41 AM
> To: rrg@irtf.org
> Cc: jnc@mercury.lcs.mit.edu
> Subject: Re: [rrg] LEIDs, SPI & ordinary IP addresses as both IDs & Locs
> 
> 
>     > From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
> 
>     >> you _always_ _have_ to do a mapping from an LEID, to get something
>     >> that _does_ have full location semantics (the RLOC)
> 
>     > if a hypothetical corporation decided to tear down its enterprise
>     > network and rebuild it from scratch, it could number the entire network
>     > out of EID space only and never have to deploy a single RLOC internally.
> 
> Please note the words "to get something that _does_ have full [i.e.
> Internetwork-wide usability] location semantics".

I can't read you mind about what you mean by "full".
Besides, for some end systems their home enterprise
may be the only scope within which they ever communicate.
For them, enterprise-local scope would be "full".

Fred
fred.l.templin@boeing.com

> 	Noel
> _______________________________________________
> rrg mailing list
> rrg@irtf.org
> http://www.irtf.org/mailman/listinfo/rrg

v2.23.0 | Report a Bug | By Email