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

Dino Farinacci <> Tue, 01 March 2022 19:54 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AA7543A0C3D for <>; Tue, 1 Mar 2022 11:54:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -7.109
X-Spam-Status: No, score=-7.109 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id fH7h7V8Orr0r for <>; Tue, 1 Mar 2022 11:54:37 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::1035]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id AB0E33A0C10 for <>; Tue, 1 Mar 2022 11:54:37 -0800 (PST)
Received: by with SMTP id q8-20020a17090a178800b001bc299b8de1so3186358pja.1 for <>; Tue, 01 Mar 2022 11:54:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7hCpkh+AtHMY1ELzK3jmQ9Wp/eMgbYoErv5ibZUUqVM=; b=gILxTsq2irF9PqEABEtKmbbLZ3pUr1qMVvFM/BViaZAsITGiog+/pGf0FFQ26vKWzT 2mffGA0sK1/a8nBTxe5TIUSYHAPIBwZZh8zLqOjcYDkgCtDs/yspPYMpw63JrrxNXVFv INpsuKBxJF+vnowNjK2AwMqXD5HKVa0wKFtFcXnshm6WWIqtuGSuO2UiHyRizTpsYGBg +WkO1FE6mYIfRNkDSgol+BK49R0xsgIbcorDx8hC32zrZg4tkZbu6bKJ8Ihl3Us8xFcb 550nWpUK5g+nGUbqSdi01p/1lWWgji4qbJT5WGfDg6nlx5jYcXoeL0r4BOknM8GucgTZ wbNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7hCpkh+AtHMY1ELzK3jmQ9Wp/eMgbYoErv5ibZUUqVM=; b=37gCc7qjJU12W1S+2lu4ujSPErmE1VLwNwrD3G/CKV7f8fw0HZ1M1sFD1cxgipMmTe 18kRUBAInDLWMBomUvEqNVUv7ARpRSjGq2nGHSn0R2/LfvAGTUhPc7mA+l9LMfirQvl1 w9EensRQVfbYvcJX6YG9sK6tXiCGJexhsHVy3LGCalBi0bsn9pHXVsZUPTcwEzzoyJ/N MpaElyHAAvY1DCvHh7TE95y9/F++BGcJxQ93LtNKrERRVU9yyx3/HIK5hM0W/3FuvyDr 9QyLeCxyfa/u8P2BvDNSEk+Lr1XmBMaC8DDsGbqGYpxCg6KdmHJbheskezc9vCnt+OE+ ayFw==
X-Gm-Message-State: AOAM532iySlCDQ5Pvg7qsP5o77bCXpoE3Ff2Uwzpzu23X6PG9Hv9ti2U lIhSBt/BdOIwAkhm8wD4cn9eUad/XQbxUQ==
X-Google-Smtp-Source: ABdhPJxNuvHbr3MbOP+MEinfXxl95hPy+bjnAiA8y2JuFMsMf/u5ehN6c6FeVoBO4oC3xMTFBWgr3Q==
X-Received: by 2002:a17:902:e94f:b0:14f:1636:c8a8 with SMTP id b15-20020a170902e94f00b0014f1636c8a8mr26907289pll.130.1646164476848; Tue, 01 Mar 2022 11:54:36 -0800 (PST)
Received: from ( []) by with ESMTPSA id u9-20020a056a00158900b004de90b164d0sm19349115pfk.9.2022. (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 01 Mar 2022 11:54:36 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.\))
From: Dino Farinacci <>
In-Reply-To: <Yh5M18z2/>
Date: Tue, 01 Mar 2022 11:54:35 -0800
Cc: Eliot Lear <>, "" <>, Dirk Trossen <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <Yh5M18z2/>
To: Toerless Eckert <>
X-Mailer: Apple Mail (2.3693.
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: Tue, 01 Mar 2022 19:54:40 -0000

> 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.