<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.spaghetti-sidrops-cms-signing-time" target="https://datatracker.ietf.org/doc/html/draft-spaghetti-sidrops-cms-signing-time-01">
   <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="June" day="7" year="2023" />
      <abstract>
	 <t>   RFC 6488 standardized a template for specifying Signed Objects that
   can be validated using the RPKI.  Since the publication of that
   document, a new additional protocol for distribution of RPKI
   repositories was developed (RFC 8182), and new insights arose with
   respect to querying and combining the different distribution
   mechanisms.  This document describes how Publishers and Relying
   Parties can use the CMS signing-time attribute to optimize seamless
   transitions from RRDP to RSYNC.  Additionally, this document updates
   RFC 6488 by mandating the presence of the CMS signing-time attribute
   and disallowing the binary-signing-time attribute.


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