RFC 9549: Internationalization Updates to RFC 5280
In plain English — editorial summary, not part of the RFC
The updates to RFC 5280 described in this document provide alignment with the 2008 specification for Internationalized Domain Names (IDNs) and includes support for internationalized email addresses in X.509 certificates. The updates ensure that name constraints for email addresses that contain only ASCII characters and internationalized email addresses are handled in the same manner. This document obsoletes RFC 8399.
Document record
- Document ID
- RFC9549
- Published
- March 2024
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9540Discovery of Oblivious Services via Service Binding RecordsCurrent
February 2024
- RFC 9529Traces of Ephemeral Diffie-Hellman Over COSE (EDHOC)Current
March 2024
- RFC 9528Ephemeral Diffie-Hellman Over COSE (EDHOC)Current
March 2024
- RFC 9525Service Identity in TLSCurrent
November 2023
- RFC 9576The Privacy Pass ArchitectureCurrent
June 2024
- RFC 9577The Privacy Pass HTTP Authentication SchemeCurrent
June 2024
- RFC 9578Privacy Pass Issuance ProtocolsCurrent
June 2024
- RFC 9579Use of Password-Based Message Authentication Code 1 (PBMAC1) in PKCS #12 SyntaxObsoleted
May 2024
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?