[pim] Re: [MSEC]Q: "open" group multicast sender a uthentication...

Hi Toerless.

I think you’re remembering the TESLA algorithm, which was documented in RFC 4082.  It needs a key management system to distribute shared keys, but does provide replay attack prevention. There are a couple of other RFCs which describe how TESLA keying material could be used with SRTP, and keys distributed by the MIKEY protocol. You can find them on this page: <https://datatracker.ietf.org/wg/msec/documents/>.

That’s all I know about it though, and I’m not aware if anyone has implemented any of this.

Hope that helps,
Brian

> On Oct 29, 2025, at 2:49 AM, Toerless Eckert <[email protected]> wrote:
> 
> Hi folks
> 
> I am trying to remember if we ever wrote down a mechanism to cryptograpically
> authenticate the sender of IP multicast packets - including replay attack
> prevention! - without having to rely on shared keys like in GDOI and hence
> the need to trust a group of receivers.
> 
> I am pretty sure that there was at some time an interesting cryptographically
> new proposal for this - a few years ago - but i don't remember enough keywords
> to find it (which WG, what was the name). Even the AI tools are thoroughly
> useless ;-))
> 
> And of course, simple authenticating packets with time-stamps 
> signing with certificate is well-known... and well-known expensive...
> 
> Cheers
>    Toerless
> 
> _______________________________________________
> MSEC mailing list -- [email protected]
> To unsubscribe send an email to [email protected]

_______________________________________________
pim mailing list -- [email protected]
To unsubscribe send an email to [email protected]