…ES ] in Cipher Block Chaining (CBC) mode [ NIST.800-38A ] with PKCS #7 padding [RFC5652], Section 6.3 operations and HMAC [ RFC2104 , SHS ] operations. This algorithm family is called AES_CBC_HMAC_SHA2. It also defines three instances of this family, the first using 128 bit CBC k…

…andards Track publications, "Cryptographic Message Syntax" [RFC2630] [RFC3369] [RFC5652] and "Cryptographic Message Syntax (CMS) Algorithms" [RFC3370]. Support for MD2 was dropped in [RFC3370]. Turner & Chen Informational [Page 3] RFC 6149 MD2 to Historic Status March 2011 RFC 28…

…g (CBC) mode [NIST.800-38A] with PKCS #7 padding operations per Section 6.3 of [RFC5652] and HMAC ([RFC2104] and [SHS]) operations. This algorithm family is called AES_CBC_HMAC_SHA2. It also defines three instances of this family: the first using 128-bit CBC keys and HMAC SHA-256…

…ity (TLS) Protocol Version 1.2", RFC 5246 DOI 10.17487/RFC5246, August 2008, >. RFC5652 ] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652 , DOI 10.17487/RFC5652, September 2009, >. RFC5958 ] Turner, S., "Asymmetric Key Packages", RFC 5958 DOI 10.17487/RFC5958,…

…, DOI 10.17487/RFC5246, August 2008, <http://www.rfc-editor.org/info/rfc5246>. [RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652, DOI 10.17487/RFC5652, September 2009, <http://www.rfc-editor.org/info/rfc5652>. [RFC5958] Turner, S., "Asymmetric Key Pack…

…ed 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 specification of the ROA (see Section 4 of [ RFC6488 ), this document defines:…

…ildebrand Standards Track [Page 30] RFC 7516 JSON Web Encryption (JWE) May 2015 RFC5652 ] Housley, R., "Cryptographic Message Syntax (CMS)", STD 70, RFC 5652 , DOI 10.17487/RFC5652, September 2009, >. W3C.REC-xmlenc-core1-20130411 Eastlake, D., Reagle, J., Hirsch, F., and T. Roes…

…ents 1. Introduction This document defines a Cryptographic Message Syntax (CMS) RFC5652 RFC6268 protected content type for a general-purpose listing of checksums (a 'checklist'), for use with the Resource Public Key Infrastructure (RPKI) RFC6480 The CMS protected content type is …

…s document defines a "Signed Prefix List", a Cryptographic Message Syntax (CMS) RFC5652 RFC6268 protected content type to carry a list of IP address prefixes and an Autonomous System Number (the subject AS). The list of prefixes describes the maximal set of prefixes that the subj…

…different from the approach used by both "Cryptographic Message Syntax (CMS)" [ RFC5652 ] and "JSON Web Encryption (JWE)" [ RFC7516 ] where different structures are used for the content layer and for the recipient layer. Two structures are defined: COSE_Encrypt to hold the encryp…

… different from the approach used by both "Cryptographic Message Syntax (CMS)" [RFC5652] and "JSON Web Encryption (JWE)" [RFC7516] where different structures are used for the content layer and for the recipient layer. Two structures are defined: COSE_Encrypt to hold the encrypted…

…). Every RPKI signed object includes, in the Cryptographic Message Syntax (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 mu…

…ransparent IXP Route Servers do not need to be listed as PAS 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 id…

…3161] use Cryptographic Message Syntax (CMS) as the signature envelope format. [RFC5652] provides details about signature verification, and [RFC3161] provides details specific to timestamp token validation. The payload of the signed timestamp token is the TSTInfo structure define…

…lly 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 specification of the TAK object (see Section 4 of [ RFC6488 ), this docum…