RFC 8398: Internationalized Email Addresses in X.509 Certificates
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9598.
Current version: RFC 9598 — Internationalized Email Addresses in X.509 Certificates
In plain English — editorial summary, not part of the RFC
This document defines a new name form for inclusion in the otherName field of an X.509 Subject Alternative Name and Issuer Alternative Name extension that allows a certificate subject to be associated with an internationalized email address. This document updates RFC 5280.
Document record
- Document ID
- RFC8398
- Published
- May 2018
- Authors
- A. Melnikov; W. Chuang
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 12
- Also known as
- —
Topics
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 8410Algorithm Identifiers for Ed25519, Ed448, X25519, and X448 for Use in the Internet X.509 Public Key InfrastructureUpdated
August 2018
- RFC 8813Clarifications for Elliptic Curve Cryptography Subject Public Key InformationCurrent
August 2020
- RFC 9162Certificate Transparency Version 2.0Current
December 2021
- RFC 9216S/MIME Example Keys and CertificatesCurrent
April 2022
- RFC 9295Clarifications for Ed25519, Ed448, X25519, and X448 Algorithm IdentifiersCurrent
September 2022
- RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current
January 2015
- RFC 9802Use of the HSS and XMSS Hash-Based Signature Algorithms in Internet X.509 Public Key InfrastructureCurrent
June 2025
- RFC 6960X.509 Internet Public Key Infrastructure Online Certificate Status Protocol - OCSPUpdated
June 2013
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?