[Sidrops] RFC 9589 on On the Use of the Cryptographic Message Syntax (CMS) Signing-Time Attribute in Resource Public Key Infrastructure (RPKI) Signed Objects

A new Request for Comments is now available in online RFC libraries.

        RFC 9589

        Title:      On the Use of the Cryptographic Message Syntax (CMS)
                    Signing-Time Attribute in Resource Public Key 
                    Infrastructure (RPKI) Signed Objects 
        Author:     J. Snijders,
                    T. Harrison
        Status:     Standards Track
        Stream:     IETF
        Date:       May 2024
        Mailbox:    job@fastly.com,
                    tomh@apnic.net
        Pages:      9
        Updates:    RFC 6488

        I-D Tag:    draft-ietf-sidrops-cms-signing-time-07.txt

        URL:        https://www.rfc-editor.org/info/rfc9589

        DOI:        10.17487/RFC9589

In the Resource Public Key Infrastructure (RPKI), Signed Objects are
defined as Cryptographic Message Syntax (CMS) protected content
types. A Signed Object contains a signing-time attribute,
representing the purported time at which the object was signed by its
issuer. RPKI repositories are accessible using the rsync and RPKI
Repository Delta protocols, allowing Relying Parties (RPs) to
synchronize a local copy of the RPKI repository used for validation
with the remote repositories. This document describes how the CMS
signing-time attribute can be used to avoid needless retransfers of
data when switching between different synchronization protocols. This
document updates RFC 6488 by mandating the presence of the CMS
signing-time attribute and disallowing the use of the
binary-signing-time attribute.

This document is a product of the SIDR Operations Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC