RFC 6268: Additional New ASN.1 Modules for the Cryptographic Message Syntax (CMS) and the Public Key Infrastructure Using X.509 (PKIX)
In plain English — editorial summary, not part of the RFC
The Cryptographic Message Syntax (CMS) format, and many associated formats, are expressed using ASN.1. The current ASN.1 modules conform to the 1988 version of ASN.1. This document updates some auxiliary ASN.1 modules to conform to the 2008 version of ASN.1; the 1988 ASN.1 modules remain the normative version. There are no bits- on-the-wire changes to any of the formats; this is simply a change to the syntax. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6268
- Published
- July 2011
- Authors
- J. Schaad; S. Turner
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 33
- Also known as
- —
- Updates:
- RFC 5911
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5480Elliptic Curve Cryptography Subject Public Key InformationUpdated
March 2009
- RFC 4912Abstract Syntax Notation X (ASN.X)Current
July 2007
- RFC 4911Encoding Instructions for the Robust XML Encoding Rules (RXER)Current
July 2007
- RFC 7630HMAC-SHA-2 Authentication Protocols in the User-based Security Model (USM) for SNMPv3Obsoleted
October 2015
- RFC 4792Encoding Instructions for the Generic String Encoding Rules (GSER)Current
January 2007
- RFC 7860HMAC-SHA-2 Authentication Protocols in User-Based Security Model (USM) for SNMPv3Current
April 2016
- RFC 4650HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing (MIKEY)Current
September 2006
- RFC 4515Lightweight Directory Access Protocol (LDAP): String Representation of Search FiltersCurrent
June 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?