Skip to main content

Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)
RFC 8898

Revision differences

Document history

Date By Action
2022-12-03
Gunter Van de Velde Closed request for Last Call review by OPSDIR with state 'Overtaken by Events'
2021-03-27
(System) Received changes through RFC Editor sync (added Errata tag)
2020-09-10
(System)
Received changes through RFC Editor sync (created alias RFC 8898, changed title to 'Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)', changed …
Received changes through RFC Editor sync (created alias RFC 8898, changed title to 'Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)', changed abstract to 'This document defines the "Bearer" authentication scheme for the Session Initiation Protocol (SIP) and a mechanism by which user authentication and SIP registration authorization is delegated to a third party, using the OAuth 2.0 framework and OpenID Connect Core 1.0.  This document updates RFC 3261 to provide guidance on how a SIP User Agent Client (UAC) responds to a SIP 401/407 response that contains multiple WWW-Authenticate/Proxy-Authenticate header fields.', changed pages to 15, changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2020-09-10, changed IESG state to RFC Published, created updates relation between draft-ietf-sipcore-sip-token-authnz and RFC 3261)
2020-09-10
(System) RFC published