[44net] Re: Comments and questions welcome: Portal Features Requirements Document

This has been discussed before and it is still being looked upon. Of course organisation like radioid.net (dmr, dstar and p25 ID's ) and echolink cannot give us all they have without consent from their user database. Using LOTW signing could also be problematic. Maybe a way to create a world wide database of ham with the capacity to ID them for every service could be done, but it is a bit outside the scope of our dashboard requirement documentation. Pierre VE2PF TAC Chairman ________________________________________ De : David Ranch via 44net <44net(a)mailman.ampr.org> Envoyé : 28 septembre 2022 14:26 À : Chris Smith; Jonathan Lassoff Cc : Amprnet 44 Net Objet : [44net] Re: Comments and questions welcome: Portal Features Requirements Document The next stage would be to get your licence and ID verified, this would typically be done by either a physical meeting, if someone is close enough, or (more likely) via a video meeting. The idea is that the more verification processes you go through, the higher your level of trust. So when you apply for resources all the verification is already in place. This is especially important for BGP requests as it currently takes some time to go through that process. Could we consider other well established forms of trust does as something signed via a valid LOTW certificate, maybe an pre-existing Echolink validation, etc? --David KI6ZHD