Re: Planning to close Universal DID-Native Addressing (UDNA) Community Group due to inactivity unless we hear from you

Hi Ian,

Yes, draft spec is present in the repo, I will make sure there is activity.
Thank you for guiding through the process.

Regards
Amir Hameed

On Mon, 6 Apr 2026 at 6:45 PM, Ian Jacobs <ij@w3.org> wrote:

> Hi Amir,
>
> I anticipate that the main deliverable of the CG will be the
> specification, which I believe lives in this repo:
>   https://github.com/w3c-cg/udna
>
> We check in on activity about every 6 months, so I would not expect
> another notice for a while, and we won’t send
> a notice as long there continues to be activity in that repo.
>
> Ian
>
> > On Apr 6, 2026, at 2:07 AM, Amir Hameed <amsaalegal@gmail.com> wrote:
> >
> > Hi Ian,
> >
> > In view of the ongoing discussion regarding the UDNA CG work progress ,
> I wanted to share that UDNA has an working implementation of Universal DID
> Native Addressing released by Sirraya Labs on 04.04.2026 as python sdk the
> link is https://pypi.org/project/sirraya-udna-sdk/. It serves as both
> proof of concept for our work and also ref implementation. I would request
> your guidance on how such a milestone can be made part of this UDNA CG so
> that we never get this group closure email.
> >
> > Regards
> > Amir Hameed
> > Chair, UDNA CG
> >
> > On Sat, 4 Apr 2026 at 02:13, Amir Hameed <amsaalegal@gmail.com> wrote:
> > Hi Ian,
> >
> > Thank you for guiding me through this , I will make sure I do as
> suggested in future. In case I have any difficulties I will reach out to
> you
> >
> >
> > Regards
> > Amir
> >
> > On Sat, 4 Apr 2026 at 2:09 AM, Ian Jacobs <ij@w3.org> wrote:
> > Thank you, Amir.
> >
> > One idea to help connect those conversations to your group is to send a
> note to public-did-native-addr@w3.org whenever an important conversation
> is happening on another group’s list. I would not suggest cross-posting,
> but a quick note to your CG’s mailing list saying “Hey we’re having an
> important conversation with the Credentials CG on topic x” would enable
> more people to understand where the work is happening.
> >
> > There may be other ways to “aggregate” these conversations, but sending
> short emails (with links to the conversation) to your public list is at
> least easy to do.
> >
> > Ian
> >
> > > On Apr 3, 2026, at 3:17 PM, Amir Hameed <amsaalegal@gmail.com> wrote:
> > >
> > > Hi Ian,
> > >
> > > Kindly find few discussion around UDNA that have happened in CCG
> mailing list
> > >
> > > 1. Re: Introduction and update on Universal DID-Native Addressing
> (UDNA) from Amir Hameed on 2025-09-20 (public-credentials@w3.org from
> September 2025)
> > >
> > > 2.  public-credentials@w3.org from February 2026: by date
> > >
> > > 3.  Re: [Email-to-DID Bridge] Exploring a practical migration path for
> email infrastructure from Manu Sporny on 2026-02-03 (
> public-credentials@w3.org from February 2026)
> > >
> > > 4.  [PROPOSAL] Standardizing DID Key Recovery: Three Viable
> Architectures (Social, Temporal, and Distributed) from Amir Hameed on
> 2026-02-23 (public-credentials@w3.org from February 2026) ( Work item
> adopted by CCG as DID-recovery)
> > >
> > > Some of the discussion has also happened in DIF, IETF and IANA for uri
> scheme registration,  we have implemented couple of test vectors and a
> python demo of how udna is used in a wifi messaging system to show protocol
> agonistic nature of the work, much of the work so far has been on the
> technical end, which is evident from the github repo, though most of the
> technical work and spec editing has been done by me alone considering the
> nature of the work. I would be happy to provide more as we progress but the
> work is being done. Thank you for allowing the group to continue.
> > >
> > > Regards
> > > Amir Hameed
> >
> > --
> > Ian Jacobs <ij@w3.org>
> > https://www.w3.org/People/Jacobs/
> > Tel: +1 917 450 8783
> >
> >
> >
> >
> >
>
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 917 450 8783
>
>
>
>
>
>
>

Received on Monday, 6 April 2026 13:19:32 UTC