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

[Koen van Hove <[e-mail]>]

Dear Rob Beck, all,

rsync is currently mandatory to implement. 
draft-ietf-sidrops-prefer-rrdp-02 [1] tried to change that but has since 
expired.

Cordially,
Koen

[1] https://datatracker.ietf.org/doc/draft-ietf-sidrops-prefer-rrdp/

On 11/11/2025 01:51, Bob Beck wrote:
> I support adoption. I think this is a reasonable start and it makes sense for the working group to look at this together to evaluate the complexity and benefits.
>
> While I share some of the thoughts mentioned others about the existing distribution methods,  I think a desire deprecating anything existing really should not predicate adopting this draft (or any other “better” method) and attempting to bring it to a useful state.
>
>   I don’t believe there is currently anything stating either of RRDP or rsync are a “must implement” beyond the influence of what RPKI implementations themselves support (correct me if I’m missing something)  Given that, and the differing limitations of the current methods I don’t  think a current method will end up being deprecated before something better arrives and matures in the ecosystem.  Something better could be this.
>
>> On Nov 8, 2025, at 08:13, Russ Housley via Datatracker <[e-mail]> wrote:
>>
>>
>> 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]
> _______________________________________________
> Sidrops mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]