Summary

  • The IETF Datatracker records draft-ietf-sidrops-rpki-erik-protocol-07 as an active SIDROPS Internet-Draft, updated on 16 August 2026.
  • The proposal uses Merkle trees, content-addressable storage, sequence numbers and HTTP to describe an RPKI publication path that may include an Erik Relay between publication points and relying parties.

Revision -07 is a new iteration in a discussion about how relying parties obtain routing-security data. The Datatracker record identifies it as an active Internet-Draft; the text is dated 16 August and carries the normal work-in-progress notice.

Its value is architectural clarity, not a claimed operational result. The draft describes a publication mechanism built from Merkle trees and content-addressable objects, using monotonically increasing sequence numbers and HTTP. In that design, an Erik Relay sits between an RPKI publication point and relying parties. The relay can be used with other RPKI transport mechanisms, rather than being presented as an all-or-nothing replacement.

For network operators, the question is not whether the draft has already changed validation. It is whether a synchronization design can make freshness, replay resistance and data distribution easier to reason about at the point where route-origin information is consumed. That is a useful technical question because RPKI depends on a chain from publication to relying-party processing; a sound object still needs a dependable delivery path.

The boundary matters. Revision -06 was dated 21 July, and the new revision is clearly a current update. But neither the Datatracker entry nor the draft establishes an RFC, an implementation requirement, deployment share, latency result or security outcome. The document expires on 17 February 2027 unless its work progresses.