Re: [RAM] Crisper Terminology

jnc@mercury.lcs.mit.edu (Noel Chiappa) Fri, 08 June 2007 16:27 UTC

Return-path: <ram-bounces@iab.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwhJF-0007y6-Vs; Fri, 08 Jun 2007 12:27:33 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HwhJD-0007uL-St for ram@iab.org; Fri, 08 Jun 2007 12:27:31 -0400
Received: from mercury.lcs.mit.edu ([18.26.0.122]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HwhJC-0006F7-N9 for ram@iab.org; Fri, 08 Jun 2007 12:27:31 -0400
Received: by mercury.lcs.mit.edu (Postfix, from userid 11178) id 7046286AF0; Fri, 8 Jun 2007 12:27:30 -0400 (EDT)
To: ram@iab.org
Subject: Re: [RAM] Crisper Terminology
Message-Id: <20070608162730.7046286AF0@mercury.lcs.mit.edu>
Date: Fri, 08 Jun 2007 12:27:30 -0400
From: jnc@mercury.lcs.mit.edu
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: jnc@mercury.lcs.mit.edu
X-BeenThere: ram@iab.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Routing and Addressing Mailing List <ram.iab.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/ram>
List-Post: <mailto:ram@iab.org>
List-Help: <mailto:ram-request@iab.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ram>, <mailto:ram-request@iab.org?subject=subscribe>
Errors-To: ram-bounces@iab.org

    > From: Scott W Brim <swb@employees.org>

    > Some approaches have IP-layer identifiers that are in fact pure
    > identifiers. Others like LISP use locally-significant locators as
    > identifiers, when outside of their locator scope.

Just to clarify something (you probably meant this, but the words don't quite
say this), it's always an identifier, wherever it is in the network (i.e.
either inside or outside its locator scope).

I think there is general agreement/understanding that it's only
meaningful/useful as a locator inside its locator scope. (Which one would
think would naturally lead one to the question "What is it when it's outside
that scope, since it's not a locator out there", but I digress...)

	Noel

_______________________________________________
RAM mailing list
RAM@iab.org
https://www1.ietf.org/mailman/listinfo/ram