…. The algorithms used in the RPKI (and associated key sizes) are specified in [ RFC6485 ]. . Signed Object Syntax The RPKI signed object is a profile of the CMS [ RFC5652 ] signed-data object, with the restriction that RPKI signed objects MUST be encoded using the ASN.1 Distingui…

…A. 4.3. Signature Algorithm The algorithm used in this profile is specified in [RFC6485]. Huston, et al. Standards Track [Page 6] RFC 6487 Resource Certificate Profile February 2012 4.4. Issuer The value of this field is a valid X.501 distinguished name. An issuer name MUST conta…

… 4.3 . Signature Algorithm The algorithm used in this profile is specified in [ RFC6485 ]. Huston, et al. Standards Track [Page 6] RFC 6487 Resource Certificate Profile February 2012 4.4 . Issuer The value of this field is a valid X.501 distinguished name. An issuer name MUST con…

…cts (for compatibility with objects produced by implementations conforming to [ RFC6485 ]). 3 . Asymmetric Key Pair Formats The RSA key pairs used to compute the signatures MUST have a 2048-bit modulus and a public exponent (e) of 65,537. Huston & Michaelson Standards Track [Page…

…uting system. 6. Security Considerations The security considerations of RFC6481 RFC6485 , and RFC6488 also apply to ASPAs. 7. IANA Considerations 7.1. SMI Security for S/MIME Module Identifier registry IANA is requested to allocate for id-mod-rpki-aspa-2023 in the "SMI Security f…

… in fact it is just a typo. Only a very inexperienced implementor would put the RFC6485 algorithm OID in the signature field of the POPOSigningKey. This problem was noted in a message to the sidr list https://www.ietf.org/mail-archive/web/sidr/current/msg06587.html and supported …

… in fact it is just a typo. Only a very inexperienced implementor would put the RFC6485 algorithm OID in the signature field of the POPOSigningKey. This problem was noted in a message to the sidr list https://www.ietf.org/mail-archive/web/sidr/current/msg06587.html and supported …