Re: [regext] [hrpc] Human Rights Review of draft-ietf-regext-verificationcode

2018-10-03 Thread Erwin Lansing
> On 3 Oct 2018, at 17.39, Ulrich Wisser wrote: > > Denmark has plans to only allow registrations with a Danish electronic id. I’m sorry to barge in and distract from the real discussion here, but I cannot let such a blatant inaccuracy stand. There are no such plans, neither have there ever b

Re: [regext] Security Lock anyone? (Was: Preliminary agenda for Prague, and call for agenda items)

2019-02-25 Thread Erwin Lansing
Folks, At .dk we also offer a form form of registry lock, called VID, which I’d like to redesign at some point. Having a standardised, or at least similar “enough” product offering across different registries and TLDs would make it much more attractive for registrants. Even though I won’t be

Re: [regext] Implementations of draft-wisser-registrylock?

2020-03-25 Thread Erwin Lansing
Hi Alex, There are several business models for registry lock. One size doesn’t fit all, but rather than every registry reinventing the wheel, we are trying to boil those down to 2-4 basic models within CENTR. That work is first and foremost looking at the user experience, but should hopefully a

Re: [regext] Implementations of draft-wisser-registrylock?

2020-05-18 Thread Erwin Lansing
Hi Ulrich,Thanks for creating this draft.My impression from reviewing the different registry business models is, that most differences are related to sales channel and out-of-band unlocking methods. As long as locking trough create and update is optional for the server implementation, and since the