[Sidrops] Re: Call for adoption: draft-spaghetti-sidrops-rpki-erik-protocol-04 (Ends 2025-11-29)

[Libin Liu <[e-mail]>]

Hi WG,

I support the adoption of this document. The document presents measurement results illustrating network traffic consumption of Rsync, RRDP+Rsync, and Erik under different RP synchronization frequencies and demonstrates the practical value of Erik.

I have a small question for the authors: could you please share any insight into the proportion of RPs that synchronize less frequently than every 15 minutes or every hour? I am asking because longer synchronization intervals may lead to increased delays before updated objects take effect.


Best,
Libin
________________________________
From: Russ Housley via Datatracker <[e-mail]>
Sent: Saturday, November 8, 2025 11:13 PM
To: [e-mail] <[e-mail]>; [e-mail] <[e-mail]>; [e-mail] <[e-mail]>
Subject: [Sidrops] Call for adoption: draft-spaghetti-sidrops-rpki-erik-protocol-04 (Ends 2025-11-29)


Subject: Call for adoption: draft-spaghetti-sidrops-rpki-erik-protocol-04
(Ends 2025-11-29)

This message starts a 3-week Call for Adoption for this document.

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, easy to
   implement, and robust in the face of partitions or faults in the
   network.

File can be retrieved from:
https://datatracker.ietf.org/doc/draft-spaghetti-sidrops-rpki-erik-protocol/

Please reply to this message keeping [e-mail] in copy by indicating
whether you support or not the adoption of this draft as a WG document.
Comments to motivate your preference are highly appreciated.

Authors, and WG participants in general, are reminded of the Intellectual
Property Rights (IPR) disclosure obligations described in BCP 79 [2].
Appropriate IPR disclosures required for full conformance with the provisions
of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any.
Sanctions available for application to violators of IETF IPR Policy can be
found at [3].

Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/
[2] https://datatracker.ietf.org/doc/bcp79/
[3] https://datatracker.ietf.org/doc/rfc6701/



_______________________________________________
Sidrops mailing list -- [e-mail]
To unsubscribe send an email to [e-mail]