[Sidrops] Re: new MerkleTree/HTTP-based cache syncing approach: draft-spaghetti-sidrops-rpki-erik-protocol-00

[Loganaden Velvindron <[e-mail]>]

(Speaking for myself)

"10. Operational Considerations

As of July 2025, the global Internet's RPKI churn rate appears to be 2
new objects per second."

It might be good to cite the source ?


On Tue, 8 Jul 2025 at 00:55, Job Snijders <[e-mail]> wrote:
>
> Dear SIDROPS,
>
> Here the internet-draft that accompanies the earlier request for a
> presentation slot at IETF 123. Request archived here:
> https://mailarchive.ietf.org/arch/msg/sidrops/1BI8PMtGicJnys5GAHBttqWMeVw/
>
> Erik Synchronization is a novel promising approach for RPKI data
> distribution. Please do a read over when you have a chance! :-)
>
> Kind regards,
>
> Job
>
> ----- Forwarded message from [e-mail] -----
>
> Date: Mon, 07 Jul 2025 13:36:26 -0700
> From: [e-mail]
> To: Job Snijders <[e-mail]>, Tim Bruijnzeels <[e-mail]>, Tom
>         Harrison <[e-mail]>, Wataru Ohgai <[e-mail]>
> Subject: New Version Notification for
>         draft-spaghetti-sidrops-rpki-erik-protocol-00.txt
>
> A new version of Internet-Draft
> draft-spaghetti-sidrops-rpki-erik-protocol-00.txt has been successfully
> submitted by Job Snijders and posted to the
> IETF repository.
>
> Name:     draft-spaghetti-sidrops-rpki-erik-protocol
> Revision: 00
> Title:    The Erik Synchronization Protocol for use with the Resource Public Key Infrastructure (RPKI)
> Date:     2025-07-07
> Group:    Individual Submission
> Pages:    14
> URL:      https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-erik-protocol-00.txt
> Status:   https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rpki-erik-protocol/
> HTML:     https://www.ietf.org/archive/id/draft-spaghetti-sidrops-rpki-erik-protocol-00.html
> HTMLized: https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-rpki-erik-protocol
>
>
> Abstract:
>
>    This document specifies the Erik Synchronization Protocol for use
>    with the Resource Public Key Infrastructure (RPKI).  Erik
>    Synchronization can be characterized as a data replication system
>    using Merkle trees, a content-addressable naming scheme, concurrency
>    control using monotonically increasing sequence numbers, and HTTP
>    transport.  Relying Parties can combine information retrieved via
>    Erik Synchronization with other RPKI transport protocols.  The
>    protocol's design is intended to be efficient, fast, and easy to
>    implement.
>
>
>
> The IETF Secretariat
>
>
>
> ----- End forwarded message -----
>
> _______________________________________________
> Sidrops mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]