Re: [Int-area] Continuing the addressing discussion: what is an address anyway?

Toerless Eckert <> Thu, 03 March 2022 06:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id CCDF23A1395 for <>; Wed, 2 Mar 2022 22:33:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.882
X-Spam-Status: No, score=-0.882 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=no autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9Igu43CjFQyi for <>; Wed, 2 Mar 2022 22:33:40 -0800 (PST)
Received: from ( [IPv6:2001:638:a000:4134::ffff:40]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id BBF4D3A1171 for <>; Wed, 2 Mar 2022 22:33:35 -0800 (PST)
Received: from ( []) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by (Postfix) with ESMTPS id 9B433549AF2; Thu, 3 Mar 2022 07:33:28 +0100 (CET)
Received: by (Postfix, from userid 10463) id 88D614EA7EE; Thu, 3 Mar 2022 07:33:28 +0100 (CET)
Date: Thu, 03 Mar 2022 07:33:28 +0100
From: Toerless Eckert <>
To: Dino Farinacci <>
Cc: Eliot Lear <>, "" <>, Dirk Trossen <>
Message-ID: <>
References: <> <> <Yh5M18z2/> <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <>
Archived-At: <>
Subject: Re: [Int-area] Continuing the addressing discussion: what is an address anyway?
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG Mailing List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 03 Mar 2022 06:33:43 -0000

On Tue, Mar 01, 2022 at 11:54:35AM -0800, Dino Farinacci wrote:
> > For example: The use of locator/identifier in RFC6830 (LISP) i think is,
> > to use the White Knight's terminology, only what an address is
> > called by an xTR (or the LISP instance) but nothing more: It does not
> > defining what the nature of the locator or identifier addresses are.
> An identifier (i.e. EID) typically is static (can be dynamcially assigned) and is used by the transport layer and not routable by the underlay. A locator (i.e. RLOC) is an address, according to the definition that everyone understands today, is used in the outer header encapsulation and is routable by the underlay.
> It is that simple, even though I made the description lengthy to be a bit more complete on their usage.

Thanks. Not contradicting what i claimed... I think.

My point was specifically that the LISP locator helps LISP to "locate" another
xTR, but that is different from whether or not the locator by the nature
of its address structure helps the underlay to locate the entity (xTR) that the
address is assigned to (xTR). So the name 'locator' is 'just' a good
name for what LISP calls/uses the address for, not for how the under
itself would maybe call the address or use the address for.