<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-sidrops-cms-signing-time" target="https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-cms-signing-time-07">
   <front>
      <title>On the use of the CMS signing-time attribute in RPKI Signed Objects</title>
      <author initials="J." surname="Snijders" fullname="Job Snijders">
         <organization>Fastly</organization>
      </author>
      <author initials="T." surname="Harrison" fullname="Tom Harrison">
         <organization>Asia Pacific Network Information Centre</organization>
      </author>
      <date month="April" day="16" year="2024" />
      <abstract>
	 <t>   In the Resource Public Key Infrastructure (RPKI), Signed Objects are
   defined as Cryptographic Message Syntax (CMS) protected content
   types.  Signed Objects contain 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.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-sidrops-cms-signing-time-07" />
   
</reference>
