IETF Logo Mail Archive

Re: [lisp] [ipdir] LISP WG

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 13 March 2009 16:18 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: lisp@core3.amsl.com
Delivered-To: lisp@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 89B7B3A687F; Fri, 13 Mar 2009 09:18:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.01
X-Spam-Level:
X-Spam-Status: No, score=-6.01 tagged_above=-999 required=5 tests=[AWL=0.589, 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 9fp+vnAa4ZyX; Fri, 13 Mar 2009 09:18:23 -0700 (PDT)
Received: from stl-smtpout-01.boeing.com (stl-smtpout-01.boeing.com [130.76.96.56]) by core3.amsl.com (Postfix) with ESMTP id BFFA23A65A5; Fri, 13 Mar 2009 09:18:23 -0700 (PDT)
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by stl-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id n2DGIlKO001323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 13 Mar 2009 11:18:47 -0500 (CDT)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id n2DGIknV009246; Fri, 13 Mar 2009 11:18:47 -0500 (CDT)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id n2DGIfYQ008968; Fri, 13 Mar 2009 11:18:46 -0500 (CDT)
Received: from XCH-NW-7V2.nw.nos.boeing.com ([130.247.54.35]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 13 Mar 2009 09:18:43 -0700
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5
Date: Fri, 13 Mar 2009 09:18:42 -0700
Message-ID: <39C363776A4E8C4A94691D2BD9D1C9A105B0AB7D@XCH-NW-7V2.nw.nos.boeing.com>
In-Reply-To: <1368441D-65C6-40E6-82FA-964E193C826B@lilacglade.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [lisp] [ipdir] LISP WG
Thread-Index: Acmj9V5DKfoTHtPwTEWkotwVAPgs/QAAHOeQ
References: <49AFF574.6090805@piuha.net> <1368441D-65C6-40E6-82FA-964E193C826B@lilacglade.org>
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Margaret Wasserman <mrw@lilacglade.org>, Jari Arkko <jari.arkko@piuha.net>
X-OriginalArrivalTime: 13 Mar 2009 16:18:43.0864 (UTC) FILETIME=[61220980:01C9A3F7]
Cc: ipdir@ietf.org, IESG IESG <iesg@ietf.org>, lisp@ietf.org
Subject: Re: [lisp] [ipdir] LISP WG
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lisp>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 13 Mar 2009 16:18:24 -0000

Margaret,
 
> Please note that I am not arguing against creation of this WG or  
> against publication of the mechanisms described in the LISP drafts.

> Specifically, I am concerned about the accuracy of calling this  
> mechanism an ID/Locator split mechanism and/or conflating the concept

> of IDs (in the ID/Loc sense) with the LISP concept of an EID, as EIDs

> serve as both a topological locator and an identifier.

I agree, and this is a point that I have raised several
times also. A *true* endpoint identifier would not be
routable within any scope, whereas the LISP EID is
routable within the scope of an edge network (i.e.,
even if that scope is only node-local). Conversely,
HIP provides an example of a true endpoint identifier.

An EID *does* identify an endpoint's interface, however.
Therefore, I believe a more accurate expansion of the
term is Endpoint *Interface* iDentifier (EID).

Fred
fred.l.templin@boeing.com

v2.23.0 | Report a Bug | By Email