IETF Logo Mail Archive

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

Jens Finkhaeuser <jens@interpeer.io> Tue, 08 March 2022 09:45 UTC

Return-Path: <jens@interpeer.io>
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 C21893A0E91 for <int-area@ietfa.amsl.com>; Tue, 8 Mar 2022 01:45:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.106
X-Spam-Level:
X-Spam-Status: No, score=-2.106 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=interpeer.io
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 H1tizeaA2x9J for <int-area@ietfa.amsl.com>; Tue, 8 Mar 2022 01:45:40 -0800 (PST)
Received: from mail-4022.proton.ch (mail-4022.proton.ch [185.70.40.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2FD2F3A0E79 for <Int-area@ietf.org>; Tue, 8 Mar 2022 01:45:38 -0800 (PST)
Date: Tue, 08 Mar 2022 09:45:34 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interpeer.io; s=protonmail; t=1646732735; bh=ECijVdQ5iVHGbKszd91L3UJTurqKJVbv/bWNqoz1Pc8=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=ZooR+GTkNxi3KWev9ewOA9vGynTVLD8tGoMMPJtd+HwiIHxJ7VWIQ8yu+WYd4dsl9 QKawtkrwNiEt4/7CuuUTXbOhPpbBmxHBOZB7qBNdQoPK8PAyg/QIRdIhOLlasHYDiF RZeXrs+A9Vo1R18h8/fS4CuzfTfCBbWncBf6remE=
To: Dino Farinacci <farinacci@gmail.com>
From: Jens Finkhaeuser <jens@interpeer.io>
Cc: Antoine FRESSANCOURT <antoine.fressancourt@huawei.com>, Toerless Eckert <tte@cs.fau.de>, "Int-area@ietf.org" <Int-area@ietf.org>, Dirk Trossen <dirk.trossen=40huawei.com@dmarc.ietf.org>
Reply-To: Jens Finkhaeuser <jens@interpeer.io>
Message-ID: <XTRZmAuKYO_r-kwrA0kY8svxdX3qY3JUzSnzQWzw0x9UYiG4JT9EAuKiEWfWW_xrPWBVqkMHE9TPS2y5Do8L0MjQ9-v1s_yOsn6ecC-VhfI=@interpeer.io>
In-Reply-To: <68CD1BCC-C2E5-467E-AC62-AE6DBFBF7B42@gmail.com>
References: <57c643c667d94a77b9917bb17dc142a5@huawei.com> <YiBhOKIK9bMqwx0a@faui48e.informatik.uni-erlangen.de> <385CF477-C876-482F-ADFE-DAAD6CA7BAEC@gmail.com> <YiH6iHwv+U9QFA06@faui48e.informatik.uni-erlangen.de> <499a3364-7ea5-4268-cce3-43f010f36a72@gmail.com> <Gpm-qFUmOVey9DYUJV6S_UNYb02p7ANbT8rEjy8JA54B__1YeX6Uny2E16uEg_o-R7v9CWPdDbyOgNW7nJyACAbx7Ok99Q-zad1EsgYBerc=@interpeer.io> <d128f1fc15824cae9012ab5f30358221@huawei.com> <6uJDmm2bhEUi36qYOVl6ATxQChEKP29xDlBGSJfyOeV2gNk5MbfYVt3CO_5m4S_Pj-OmZsZT5ayxBWYBfxyRjIEPCJTxarx69ML7dEWShcg=@interpeer.io> <68CD1BCC-C2E5-467E-AC62-AE6DBFBF7B42@gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------a7d5f131e5d1b9d9b01e16530a0f40d4c03afdf7c6073a8d17beca4ce201aa24"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/nGxGo3lANikq4sjbgrWskpnzV70>
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: Tue, 08 Mar 2022 09:45:46 -0000

Dino,

thank you for this and your other answers!

I can see that it's possible to treat EIDs as sufficiently static to treat them as (stand-ins for) unique identifiers.

I can still (quite easily) construct scenarios with drones where the EID-to-RLOC mapping on a LISP map server is not going to suffice for AAA. I'd gladly discuss this further, but it is increasingly out of scope of the current topic on the distinction between identifiers and locators.

I'm conducting some ongoing research on this more general AAA topic, however. I can see that there is space for a LISP extension at some point to cover such scenarios. That is a highly interesting conclusion in its own right. If you don't mind, I shall reach out to you regarding this in some time, because you appear to be the right person for this!

Jens

v2.23.0 | Report a Bug | By Email