Re: [regext] Idea about AuthCodeSEC: use Public Key Cryptography for AuthCode

g-PAJi/https%3A%2F%2Fgithub.com%2Fxinbenlv%2Frfc-draft-authcodesec%2Fblob%2Fmain%2FREADME.md> and I would love to see if anyone is interested in participate in future discussion of a possible RFC and maybe co-author? Victor Zhou z...@namefi.io (work) / z...@zzn.im (personal) On Sun, Mar 17, 2024 at 3:58

[regext] Re: Question regarding client identifiers and password requirement of RFC-5730

> attempts to extend the protocol that I’m aware of. > > > > Scott > > > > *From:* Victor Zhou > *Sent:* Thursday, October 17, 2024 5:37 PM > *To:* regext@ietf.org > *Cc:* Hollenbeck, Scott > *Subject:* [EXTERNAL] Question regarding client identifiers and passwo

[regext] Re: Call for agenda items IETF 121

.1 > >S: > > > > The EPP login command would include: > > > >C: > >C:urn:ietf:params:xml:ns:epp:authcodesec-0.1 > >C: > > > > I’m interested in what enhancements you propose. > > > > Thanks, > &

[regext] Re: Call for agenda items IETF 121

Dear REGEXT WG and chairs, Could we have 10min to talk about rfc-draft-AuthCodeSEC: https://github.com/xinbenlv/rfc-draft-authcodesec/blob/main/README.md Victor Zhou, Building Namefi (https://namefi.io) by D3Serve Labs Inc (https://d3serve.xyz ) --- Dear REGEXT WG, This is a call for agenda

[regext] Re: Thoughts on AuthCodeSEC

Christian, Yes the goal is the receiver will need to be known at the time AuthCode(SEC) is submitted to the registry. Assuming you are talking about Model B In the Model B, the receiver is Gaining Registrar. (As opposed to in Model A the receiver is the Gaining Registrant.) In Model B, 1. The re

[regext] Re: Call for agenda items IETF 121

/xinbenlv/rfc-draft-authcodesec/blob/main/draft-authcodesec-00.txt Talk to you tomorrow Victor, CEO & founder of Namefi <http://namefi.io>, tokenizing domain names for trading, DeFi and future Internet. https://namefi.io On Thu, Oct 31, 2024 at 8:20 PM Victor Zhou wrote: > D

[regext] Question regarding client identifiers and password requirement of RFC-5730

t more sophisticated login / authentication schemes? For example if a server announces a public-key authentication algorithm and relevant parameter it chose, a client can login with a signature given a server challenge. Thank you! Victor Zhou, CEO & founder of Namefi <http://namefi.io>, t

[regext] Re: Call for IETF122 Agenda Items

Hi Antoin and REGEXT WG We revised AuthCodeSEC RFC based on feedback we received from the last IETF 121 REGEXT sessions. Is it ok that we take 10min to present the modification and ask for a new round of feedback? Victor, CEO/Founder of Namefi (D3Serve Labs Inc.) Building dig

[regext] Re: PLEASE RESPOND: INTERIM MEETING PLANNING (was: simplifying the extensions rules)

I am interested in attending this meeting Victor, building Namefi for digital trust and future Internet. https://namefi.io On Wed, Apr 2, 2025 at 15:53 Tom Harrison wrote: > On Wed, Apr 02, 2025 at 10:21:18AM -0400, James Galvin wrote: > > A virtual interim meeting is certai

[regext] Fwd: Idea about AuthCodeSEC: use Public Key Cryptography for AuthCode

ZtL4QjLxLNC1oDuLWu-S47Yu3xfJH1sQpHzN0cYdjg-PAJi/https%3A%2F%2Fgithub.com%2Fxinbenlv%2Frfc-draft-authcodesec%2Fblob%2Fmain%2FREADME.md> and I would love to see if anyone is interested in participate in future discussion of a possible RFC and maybe co-author? Victor Zhou z...@namefi.io (work) / z...@