RFC 4630: Update to DirectoryString Processing in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 5280.
Current document in this lineage: RFC 5280 — Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile
In plain English — editorial summary, not part of the RFC
This document updates the handling of DirectoryString in the Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile, which is published in RFC 3280. The use of UTF8String and PrintableString are the preferred encoding. The requirement for exclusive use of UTF8String after December 31, 2003 is removed. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4630
- Published
- August 2006
- Authors
- R. Housley; S. Santesson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 6
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 5 RFCs, each formally replacing the one before it.
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4621Design of the IKEv2 Mobility and Multihoming (MOBIKE) ProtocolCurrent
August 2006
- RFC 4616The PLAIN Simple Authentication and Security Layer (SASL) MechanismUpdated
August 2006
- RFC 4650HMAC-Authenticated Diffie-Hellman for Multimedia Internet KEYing (MIKEY)Current
September 2006
- RFC 4668RADIUS Authentication Client MIB for IPv6Current
August 2006
- RFC 4669RADIUS Authentication Server MIB for IPv6Current
August 2006
- RFC 4590RADIUS Extension for Digest AuthenticationObsoleted
July 2006
- RFC 4670RADIUS Accounting Client MIB for IPv6Current
August 2006
- RFC 4671RADIUS Accounting Server MIB for IPv6Current
August 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?