Skip to main content

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

Revision differences

Document history

Date By Action
2018-12-19
(System)
Received changes through RFC Editor sync (changed abstract to 'The baseline security mechanisms in the Session Initiation Protocol (SIP) are inadequate for cryptographically assuring the …
Received changes through RFC Editor sync (changed abstract to '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.')
2018-06-15
(System) Received changes through RFC Editor sync (added Errata tag)
2018-02-16
(System) IANA registries were updated to include RFC8224
2018-02-14
(System)
Received changes through RFC Editor sync (created alias RFC 8224, changed abstract to 'The baseline security mechanisms in the Session Initiation Protocol (SIP) are …
Received changes through RFC Editor sync (created alias RFC 8224, changed abstract to '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.', changed pages to 46, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-02-14, changed IESG state to RFC Published, created obsoletes relation between draft-ietf-stir-rfc4474bis and RFC 4474)
2018-02-14
(System) RFC published