Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] [Dello Response] A new federated identity and interaction layer over QUIC – seeking engagement with the AFRINIC community

DELLO. A. A dello.a.a at gmail.com
Tue Mar 24 20:09:32 UTC 2026


Dear Junior,

Thank you for sharing this. The concept is interesting, but before
meaningful technical feedback can be given, the paper needs to explain a
few fundamentals more clearly, ideally with architecture and trust-flow
diagrams.

In particular, could you clarify:


   1.

   the exact problem QUIP solves that existing protocols do not
   2.

   where QUIC ends and the actual identity/application layer begins,
   3.

   how the ISP trust-anchor model works in practice, including identity
   proofing, portability, revocation, and privacy safeguards,
   4.

   how the proposed distributed CA model operates, and
   5.

   whether there is any working prototype, message flow, or
   interoperability demonstration.

At present, the paper feels too abstract for technical review, especially
without diagrams showing the architecture, trust relationships, and
end-to-end flows

Regards,

Amani Dello

On Tue, 24 Mar 2026 at 22:04, Junior <jjmututicloud at gmail.com> wrote:

> Dear AFRINIC RPD list members,
>
> My name is Junior Joseph Mututi, and I’ve been working on a new protocol
> called QUIP (QUIC Identity Protocol). QUIP is designed as an open,
> federated identity and interaction layer built entirely on QUIC (RFC 9000).
> It combines the domain-based addressing of XMPP, the vocabulary of
> ActivityStreams, and a novel trust model where ISPs act as neutral trust
> anchors – verifying user identities without owning them.
>
> The protocol’s whitepaper (attached) details its architecture: a generic
> state machine over QUIC, ISP‑based attestation, a distributed CA
> foundation, end‑to‑end encryption extensions, and built‑in federation
> mechanics. It is meant to run in parallel with the existing web and to give
> ISPs a direct role in enabling secure, privacy‑respecting communication for
> their subscribers.
>
> I’m reaching out to the AFRINIC community because Africa is a key region
> for QUIP’s vision. The whitepaper notes (Section 13.3.1) that Africa’s ISP
> landscape – with its growing number of operators, mobile‑first
> connectivity, and strong data sovereignty concerns – is a natural early
> adopter. I’d like to present QUIP at an upcoming AFRINIC meeting (e.g.,
> AFRINIC‑OPEN) to get feedback from network engineers, policy makers, and
> the ISP community.
>
> Specifically, I’d be grateful for:
>
> · Guidance on how to propose a presentation or technical talk at an
> AFRINIC meeting.
> · Feedback on the ISP trust model and its alignment with regional
> regulatory frameworks.
> · Interest from ISPs willing to participate in a pilot deployment (the
> whitepaper outlines a potential Zimbabwe pilot with ZISPA and POTRAZ).
>
> I welcome any questions or comments – I’m happy to clarify technical
> details or discuss how QUIP could fit into AFRINIC’s capacity‑building and
> infrastructure development goals.
>
> Thank you for your time, and I look forward to engaging with the community.
>
> Best regards,
> Junior Joseph Mututi
> WhatsApp/Calls: +27658095749/+27812629742
>
> _______________________________________________
> RPD mailing list
> RPD at afrinic.net
> https://lists.afrinic.net/mailman/listinfo/rpd
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.afrinic.net/pipermail/rpd/attachments/20260324/b711614a/attachment.html>


More information about the RPD mailing list