metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 8224: Authenticated Identity Management in the Session Initiation Protocol (SIP)

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

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

The baseline security mechanisms in the Session Initiation Protocol (SIP) are inadequate for cryptographically assuring the identity of the end users that originate SIP requests, especially in an interdomain context. This document defines a mechanism for securely identifying originators of SIP requests. It does so by defining a SIP header field for conveying a signature used for validating the identity and for conveying a reference to the credentials of the signer. This document obsoletes RFC 4474.

Document record

Document ID
RFC8224
Published
February 2018
Authors
J. Peterson; C. Jennings; E. Rescorla; C. Wendt
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
46
Also known as
—
Obsoletes:
RFC 4474
Updated by:
RFC 8946

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/8224-authenticated-identity-management-in-the-session-initiation-protocol-sip