IETF Logo Mail Archive

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

Jens Finkhaeuser <jens@interpeer.io> Wed, 09 March 2022 07:52 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 E98D73A188E for <int-area@ietfa.amsl.com>; Tue, 8 Mar 2022 23:52:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, 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 HpvULiZ4sK6O for <int-area@ietfa.amsl.com>; Tue, 8 Mar 2022 23:52:34 -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 1E0AC3A188D for <Int-area@ietf.org>; Tue, 8 Mar 2022 23:52:32 -0800 (PST)
Date: Wed, 09 Mar 2022 07:52:26 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=interpeer.io; s=protonmail; t=1646812349; bh=97hIhhitekELSURx0Uy93/vJUFTTsMug3ZmqMH1Wtus=; 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=uI2y11hYQm/OJZkugg73MZN4nx9gPwjfIzNnPDXi+INewfcjC775+wknGz9FvKYAM sCqoxYUuwWW4cz4iSs5VAUy+vlVvU3lpMtCi/BKQ29oPhXvmg2Y7rsX7VtbzSDMi5o sQQd8qrerhC2iV9iQAlKYRmdvc8z5AaBvCwiPdA8=
To: "Bless, Roland (TM)" <roland.bless@kit.edu>
From: Jens Finkhaeuser <jens@interpeer.io>
Cc: "Int-area@ietf.org" <Int-area@ietf.org>
Reply-To: Jens Finkhaeuser <jens@interpeer.io>
Message-ID: <E37Jo1X04jfe-JTXnKVaEXZq9iZ-hges-t1lKjTEwleK8sYbew4skTPOgORFk2sFAtrjtMdIoJY84BTBzR28DLez1bwdQcDHRunH_tw24YU=@interpeer.io>
In-Reply-To: <b81feeda-32d9-8d4e-f1e2-912f9b64092a@kit.edu>
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> <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> <b81feeda-32d9-8d4e-f1e2-912f9b64092a@kit.edu>
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha512"; boundary="------6a2231bdc0be739d17b0a66a102a2aa08870bd4ed27734460aaf7d42c1ca3833"; charset="utf-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/nmhTzOLPoxIv0l8gmNtWhpKzXso>
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: Wed, 09 Mar 2022 07:52:40 -0000

Hi Roland!

(And greetings to my former hometown, Karlsruhe!)

On Tuesday, March 8th, 2022 at 12:21, Bless, Roland (TM) roland.bless@kit.edu wrote:

> I'm not sure about your requirements. I think that identifiers for AAA
> 

> can be unique and static on their "layer" and do not need to coincide
> 

> with network addresses.
> 

> (snip)

I agree; this is also the approach we currently take.

The set of requirements for drones is complex, and I have not laid it out well - mostly because this conversation thread is about addressing, while most of the issues I perceive are to do with routing. Of course the two are hard to separate. I also have another use case in mind that is unrelated to drones.

I have been pointed in some interesting directions on this list - thank you all! - and I think at this time it's best that I read through this material carefully. I can then come back, lay out my use cases, and provide some comments on which approach does and does not work so well from their point of view.

That seems a lot better than continuing, because conceptually, the split between identifier and locator as proposed makes a lot of sense to me as well; we're effectively pursuing much the same direction.

Jens

v2.23.0 | Report a Bug | By Email