This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ncc-services-wg@ripe.net/
[ncc-services-wg] Transfer Voluntary Lock 2023-03
- Previous message (by thread): [ncc-services-wg] Transfer Voluntary Lock 2023-03
- Next message (by thread): [ncc-services-wg] Transfer Voluntary Lock 2023-03
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Alex Le Heux
aleheux at tucowsinc.com
Mon Jun 5 10:56:49 CEST 2023
Alex Le Heux Network Architect Tucows Inc / Ting Fiber aleheux at tucowsinc.com > On 5 Jun 2023, at 09:48, Gert Doering <gert at space.net> wrote: > > Hi, > > On Mon, Jun 05, 2023 at 09:40:01AM +0200, Alex Le Heux wrote: >> Not everyone agrees with that. > > So you're saying that for this policy to become effective, the NCC should > require paperwork with interesting logos and stamps on it, issued by some > random official somewhere in one of the many jurisdictions, and spend our > moneyz on verification that this is indeed a legally binding statement > by the authorized LIR contact (and not a photoshopped version)? How do you read that into that single sentence I wrote? Fantasize about straw men much? :) What’’s important here is that the transfer lock has the folowing properties: - it should be easy to activate - it should be robust against legal challenges - it should not open the NCC up to poptentially unlimited liability The preceived “strenght” (whatever that means) of anyone's favourite authentication crypto vs notarized documents has very little bearing on any of this. Alex
- Previous message (by thread): [ncc-services-wg] Transfer Voluntary Lock 2023-03
- Next message (by thread): [ncc-services-wg] Transfer Voluntary Lock 2023-03
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]