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

Dino Farinacci <farinacci@gmail.com> Thu, 03 March 2022 17:28 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ACF893A0FCB for <int-area@ietfa.amsl.com>; Thu, 3 Mar 2022 09:28:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level:
X-Spam-Status: No, score=-2.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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7pGgKnBcRtZI for <int-area@ietfa.amsl.com>; Thu, 3 Mar 2022 09:28:26 -0800 (PST)
Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5464E3A0F92 for <Int-area@ietf.org>; Thu, 3 Mar 2022 09:28:26 -0800 (PST)
Received: by mail-pg1-x536.google.com with SMTP id bc27so5116882pgb.4 for <Int-area@ietf.org>; Thu, 03 Mar 2022 09:28:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=g6pGCw4fvbni+s9U2JmpCZgXnoLuEMLXRKV1ksXbqmE=; b=C4he3QY1PF6QQ+3ZolSUbITejL9T2p8Z8WttAMnJiGWOVmc9e0CqY1VxBAswinuIJh CSAet+Fo65BJ9cL/ueq3jUFqzrE+lo+/JjZ7tpbt9h5/x0JvHlIcNJr9kWu46HmHC1Ia Wb0iH801gowiJpa4RFZL9B9w7wVNRPu4TxpkcAUtovInNNHvWkWkXuwQ93+5HPlC7jT8 YWurvke1PO0QqlF1KpigISYKXfBm8uMWhsEzwMKCaTzkC5gM5Ro4+ZjDCiQY/KN3yxKk uF+ODYLaqyWYQ9WPg/tMee1/uenvzLM4ff7UnOQqt1Y9LuI025+IF3KsqEvYuZvvalSE mAuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=g6pGCw4fvbni+s9U2JmpCZgXnoLuEMLXRKV1ksXbqmE=; b=nB/STvY6Kfxo/RF9a1/V8w1Aibk6tjW8/gXZWgVsd2CwFfqx7J854zyHCfvGgfWwZL PWPxKQ5LnpFq4JDrHe09cBzbDeKlHi3ZFA1SC9R1i2v0ZRSDlnU44Htd7kler+zmH2jK KqPiyATZg/PLj/SqS3qG/t8Mcl8rkNoZTiM6M1S1A9gVpE8Jt5A1ijAbARn5JkGmXQYr KB6BbaGA6fS7dfa1LLWH/FnzeXBnU6WXx4c9Lyvl4c7CLjjsXU5x4DdezO3IHaB5ERB6 6+OhGb9ZqT182jd7fxsd3b2rfhhrVCsByNFAUO/Tdo0bPTDF8K4JRmR3QyI5KVX0bHyO sSGA==
X-Gm-Message-State: AOAM530vB8+y/1uLfK/Oax+TE2ZYxN1XfpOJDeH8F3hkVx3h7vhmReti cRIxpqXO/RINA0QT5o7kuZ/d4z55UxRWng==
X-Google-Smtp-Source: ABdhPJwHqvDhJO3oyHn0iRbPN6W9iVECzzFXTaqggfFebXiZ9vaXnmlxcto0MU7s16roLgBVSqSl5A==
X-Received: by 2002:a63:1d44:0:b0:373:5612:629b with SMTP id d4-20020a631d44000000b003735612629bmr31557254pgm.352.1646328505504; Thu, 03 Mar 2022 09:28:25 -0800 (PST)
Received: from smtpclient.apple (c-98-234-33-188.hsd1.ca.comcast.net. [98.234.33.188]) by smtp.gmail.com with ESMTPSA id p2-20020a17090a348200b001bef7d1dd45sm2686598pjb.33.2022.03.03.09.28.24 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 03 Mar 2022 09:28:24 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.60.0.1.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <YiBhOKIK9bMqwx0a@faui48e.informatik.uni-erlangen.de>
Date: Thu, 03 Mar 2022 09:28:23 -0800
Cc: Eliot Lear <lear@lear.ch>, "Int-area@ietf.org" <Int-area@ietf.org>, Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <385CF477-C876-482F-ADFE-DAAD6CA7BAEC@gmail.com>
References: <57c643c667d94a77b9917bb17dc142a5@huawei.com> <7de0956f-3fde-1543-405b-b635f6e69362@lear.ch> <Yh5M18z2/YVfpW7i@faui48e.informatik.uni-erlangen.de> <A771FFF8-43A8-4D84-8B6E-A3E7AF96644E@gmail.com> <YiBhOKIK9bMqwx0a@faui48e.informatik.uni-erlangen.de>
To: Toerless Eckert <tte@cs.fau.de>
X-Mailer: Apple Mail (2.3693.60.0.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/4LdqPLRrwyGP3pAtvE8FIcaVT2Q>
Subject: Re: [Int-area] Continuing the addressing discussion: what is an address anyway?
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area WG Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Mar 2022 17:28:29 -0000

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

You think right.

> 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

Yes, where the EID is close to or the EID/RLOC are co-located in the same system.

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

Well the locator you put in an outer header destination address is called/used/assign to whatever the rules of the underlay are. If the underlay is ethernet, then its a 6-byte address where the high-order 3 bytes is an organizational ID, just to cite an example.

Dino