UpdatedPROPOSED STANDARDIETF stream

RFC 8226: Secure Telephone Identity Credentials: Certificates

Still current, but amended. Parts of this document are changed or extended by RFC 9118. Read both.

In plain English — editorial summary, not part of the RFC

In order to prevent the impersonation of telephone numbers on the Internet, some kind of credential system needs to exist that cryptographically asserts authority over telephone numbers. This document describes the use of certificates in establishing authority over telephone numbers, as a component of a broader architecture for managing telephone numbers as identities in protocols like SIP.

Document record

Document ID
RFC8226
Published
February 2018
Authors
J. Peterson; S. Turner
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
24
Also known as
Updated by:
RFC 9118

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.

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?

canonical URL: /rfc/8226-secure-telephone-identity-credentials-certificates