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

Alan DeKok <> Mon, 07 March 2022 13:31 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3AB823A0FFC for <>; Mon, 7 Mar 2022 05:31:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GFeFLaAUDdQs for <>; Mon, 7 Mar 2022 05:31:14 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 771C13A0FE6 for <>; Mon, 7 Mar 2022 05:31:12 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTPSA id 6B57B470; Mon, 7 Mar 2022 13:31:06 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 15.0 \(3693.\))
From: Alan DeKok <>
In-Reply-To: <>
Date: Mon, 07 Mar 2022 08:31:04 -0500
Cc: Jens Finkhaeuser <>, Toerless Eckert <>, "" <>, Dirk Trossen <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <Yh5M18z2/> <> <> <> <> <> <> <> <> <>
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: Mon, 07 Mar 2022 13:31:39 -0000

On Mar 7, 2022, at 8:00 AM, Antoine FRESSANCOURT <> wrote:
> [AFT] 3GPP provides a method to address this. Indeed, it allows bridging with other link layer technologies, termed “Non-3GPP access networks”. Wi-Fi for instance is seen as such a non-3GPP access technology, on which the 3GPP Authentication, authorization and accounting (AAA) infrastructure can be used.

  As Jens also noted, this is unlikely to happen outside of the commercial / telco / ISP space.  People have been trying to do business-to-business roaming for 25 years.  It hasn't taken off.

  Even WiFi roaming integration has taken decades to get going.  There's now OpenRoaming, which is nice.  But I was trying to get something similar done 15+ years ago, and gave up due to lack of interest and/or perceived value.

> [AFT] If you consider the identifier for the sole purpose of identification, I don’t see any problem with using this ID to do AAA on any type of access layer technology. For instance, with Wi-Fi, the identity credentials present in the SIM can be used in a RADIUS or DIAMETER authentication and network attachment procedure (This is actually done in several network offloading use cases).

  Telcos are moving to anonymous identifiers for privacy issues, especially in the WiFi offload case.

  The only people who need to see the actual identifiers are (a) the end user, and (b) the ISP that the user has a contractual relationship with.

  This process is defined in RFC 7542 (NAI).

  Perhaps this is off-topic for here, but I think it would be very nice to permit roaming for non-corporate entities.  If I visit my friends house, why do I need to go through complex steps to configure WiFi?  He (or his systems) know what the configuration is.  He trusts his systems.  I know him.  He trusts me (at least for WiFi access).  Why is there nothing to "close the loop" ?  Implementing that would require some kind of global addressing scheme.

  Alan DeKok.