…A. 2.1 . Manifests Every repository publication point MUST contain a manifest [ RFC6486 ]. The manifest contains a list of the names of all objects, as well as the hash value of each object's contents that are currently published by a CA or an EE. Huston, et al. Standards Track […
…t in time (e.g., an EE certificate MAY be used to sign a sequence of manifests [RFC6486]). Such EE certificates are termed "sequential use" EE certificates. EE certificates used to validate only one instance of a signed object, and are not used thereafter or in any other validati…
… in time (e.g., an EE certificate MAY be used to sign a sequence of manifests [ RFC6486 ]). Such EE certificates are termed "sequential use" EE certificates. EE certificates used to validate only one instance of a signed object, and are not used thereafter or in any other validat…
…cts, such as Route Origin Authorizations (ROAs) RFC6482 This document obsoletes RFC6486 1.1. Requirements Language The key words " MUST ", " MUST NOT ", REQUIRED ", " SHALL ", SHALL NOT ", " SHOULD ", SHOULD NOT ", RECOMMENDED ", " NOT RECOMMENDED ", MAY ", and " OPTIONAL " in th…
…RFC5652 ] (e.g., Route Origin Authorizations (ROAs) [ RFC6482 ] and manifests [ RFC6486 ]), and certification requests [ RFC2986 ] [ RFC4211 ]. Relying parties (RPs) also use the algorithms defined in this document to verify RPKI subscribers' digital signatures [ RFC6480 ]. The R…
…nt in time. A detailed specification of the manifest's content is provided in [ RFC6486 ] but, at a high level, a manifest consists of (1) a manifest number; (2) the time the manifest was issued; (3) the time of the next planned update; and (4) a list of filename and hash value p…
…80] envisioned using Resource Certificates to enable verification of manifests [RFC6486] and Route Origin Authorizations (ROAs) [RFC6482]. ROAs and manifests include the Resource Certificates used to verify them. Reynolds, et al. Standards Track [Page 4] RFC 8209 BGPsec Router PK…
… ] envisioned using Resource Certificates to enable verification of manifests [ RFC6486 ] and Route Origin Authorizations (ROAs) [ RFC6482 ]. ROAs and manifests include the Resource Certificates used to verify them. Reynolds, et al. Standards Track [Page 4] RFC 8209 BGPsec Router…
…nt in time. A detailed specification of the manifest's content is provided in [ RFC6486 ] but, at a high level, a manifest consists of (1) a manifest number; (2) the time the manifest was issued; (3) the time of the next planned update; and (4) a list of filename and hash value p…
…es publish certificates [ RFC6487 ], RPKI signed objects RFC6488 ], manifests [ RFC6486 ], and CRLs to repositories. CAs may have an embedded mechanism to publish to these repositories, or they may use a separate Repository Server and publication protocol. RPKI repositories are c…