Hi, ------- Original Message -------
On Monday, March 7th, 2022 at 14:00, Antoine FRESSANCOURT <antoine.fressanco...@huawei.com> 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. That seems unlikely when the WiFi network is private. The main use case for drone is any kind of situation where sending a person is less desirable; very often, these coincide with limited access to the public Internet. AAA concerns here must necessarily cover cases where centralized identity systems are inaccessible. My understanding is that "Non-3GPP access networks" do require this identity system. It's also worth understanding that while the ground station authenticating the drone is of some interest, it is far more important for the drone to authenticate the ground station - verifying command & control instructions is safety critical, authenticating the drone is more of a DoS protection by comparison. > [AFT] In my view, identifiers should not have a layer relevance, otherwise > you can consider them as flat addresses. Yet, identifiers have a relevance > with regards to the identity provider (the network operator in the SIM card’s > case) and how open or willing he is to open APIs used in AAA operations for > whichever layer or access technology used. "Flat addresses" is exactly the kind of view of an identifier that's of interest here. Jens
publickey - jens@interpeer.io - 0x5C345E9C.asc
Description: application/pgp-keys
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Int-area mailing list Int-area@ietf.org https://www.ietf.org/mailman/listinfo/int-area
