…s function. The ROA makes use of the template for RPKI digitally signed objects RFC6488 , which defines a Cryptographic Message Syntax (CMS) wrapper RFC5652 for the ROA content as well as a generic validation procedure for RPKI signed objects. Therefore, to complete the specifica…
…AS in ASPAs. This CMS RFC5652 protected content type definition conforms to the RFC6488 template for RPKI signed objects. In accordance with Section 4 of RFC6488 , this document defines: The object identifier (OID) that identifies the ASPA signed object. This OID appears in the e…
…SC Profile and Distribution RSC follows the Signed Object Template for the RPKI RFC6488 with one exception: because RSCs MUST NOT be distributed through the global RPKI repository system, the Subject Information Access (SIA) extension MUST be omitted from the RSC's X.509 End-Enti…
…t AS. Signed Prefix List objects follow the Signed Object Template for the RPKI RFC6488 1.1. Requirements Language The key words " MUST ", " MUST NOT ", " REQUIRED ", " SHALL ", " SHALL NOT ", " SHOULD ", " SHOULD NOT ", " RECOMMENDED ", " NOT RECOMMENDED ", " MAY ", and " OPTION…
…yntax (CMS) RFC5652 wrapper of the object, the EE certificate used to verify it RFC6488 . Thus, there is no requirement to separately publish that EE certificate at the CA's repository publication point. Where multiple CA instances share a common publication point, as can occur w…
…tion The TAK object makes use of the template for RPKI digitally signed objects RFC6488 , which defines a Cryptographic Message Syntax (CMS) RFC5652 wrapper for the content, as well as a generic validation procedure for RPKI signed objects. Therefore, to complete the specificatio…
…RFC 6480 RPKI Architecture February 2012 for the newly defined signed objects [ RFC6488 ] required by this infrastructure. As noted above, the architecture is comprised of three main components: an X.509 PKI in which certificates attest to holdings of IP address space and AS numb…
…RFC 6480 RPKI Architecture February 2012 for the newly defined signed objects [ RFC6488 ] required by this infrastructure. As noted above, the architecture is comprised of three main components: an X.509 PKI in which certificates attest to holdings of IP address space and AS numb…
…tax (CMS) RFC5652 RFC6268 protected content types by way of a standard template RFC6488 That template includes an optional CMS signing-time attribute, representing the time at which the object was signed by its issuer. At the time when the standard template was defined, rsync was…
…terpretations described in the following: RFC3779 RFC6480 RFC6481 RFC6487 , and RFC6488 A process to construct and sign RPKI Trust Anchor constraints is specified in I-D.nro-sidrops-ta-constraints Such signed distributed constraints can serve as an input to the methodology specif…
…he RPKI Architecture [ RFC6480 ], and the Signed Object Template for the RPKI [ RFC6488 ]. Familiarity with these documents is assumed. 1.1 . Terminology The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONA…
…s Track [Page 5] RFC 6487 Resource Certificate Profile February 2012 structure [RFC6488]. Because of the one-to-one relationship between the EE certificate and the signed object, revocation of the certificate effectively revokes the corresponding signed object. An EE certificate …
… Track [Page 5] RFC 6487 Resource Certificate Profile February 2012 structure [ RFC6488 ]. Because of the one-to-one relationship between the EE certificate and the signed object, revocation of the certificate effectively revokes the corresponding signed object. An EE certificate…
…e Resource Public Key Infrastructure (RPKI) RFC6480 makes use of signed objects RFC6488 called manifests RFC9286 . A manifest lists each file that an issuer intends to include within an RPKI repository RFC6481 , and can be used to detect certain forms of attack against a reposito…
…ly one certificate encoded in DER format. Signed Objects: RPKI signed objects [ RFC6488 ] are published in the repository publication point referenced by the SIA of the CA certificate that issued the EE certificate used to validate the digital signature of the signed object (and …