Hi Russ, Yes, this is a CMS object. Section 3 describes this. It’s an extension of RPKI Signed Object - which is CMS.- and specifies the relevant content type (3.1) and eContent (3.2).
Tim > On 22 Mar 2018, at 17:02, Russ Housley <hous...@vigilsec.com> wrote: > > Is the intent to use CMS to sign the trust anchor list? Since ROAs are > signed with CMS, I was expecting these signatures to follow the same > convention. However, there is no reference to CMS in the draft. > > Russ > > _______________________________________________ > sidr mailing list > sidr@ietf.org > https://www.ietf.org/mailman/listinfo/sidr > _______________________________________________ sidr mailing list sidr@ietf.org https://www.ietf.org/mailman/listinfo/sidr
