Repository : ssh://git@diktynna/doc On branches: backup-redmine,main
commit b6a677e3f97684871026b84ff1e58bef612e34e3 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Mon Jul 8 12:09:56 2024 +0000
doc: open-mesh/OpenHarbors
b6a677e3f97684871026b84ff1e58bef612e34e3 open-mesh/OpenHarbors.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/open-mesh/OpenHarbors.textile b/open-mesh/OpenHarbors.textile index a47f2215..7e1e1603 100644 --- a/open-mesh/OpenHarbors.textile +++ b/open-mesh/OpenHarbors.textile @@ -33,7 +33,7 @@ The issue with option 3) is that while it is secure, as the mesh node owner can
!OpenHarbors-diagram-freifunk.png!
-h3. A) Issues with Passpoint/Hotspot 2.0/OpenRoaming solutions +h3. Issues with Passpoint/Hotspot 2.0/OpenRoaming solutions
Industry leaders currently seem to propose and advocate for solutions based on "Passpoint/Hotspot 2.0":https://en.wikipedia.org/wiki/Wi-Fi_hotspot#Hotspot_2.0 (which in turn utilizes/builds upon "WPA-Enterprise":https://en.wikipedia.org/wiki/Wi-Fi_Protected_Access#Target_users_(authentic...)). Potentially with "WBA OpenRoaming":https://wballiance.com/openroaming/ (Informational RFC: "here":https://datatracker.ietf.org/doc/draft-tomas-openroaming/ or similar trust/contract relations as a federation. Hotspot 2.0 was/is also a requirement for the EU "WiFi4EU":https://wifi4eu.ec.europa.eu/#/home initiative/funding.