CurrentPROPOSED STANDARDIETF stream

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

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

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.

Document record

Document ID
RFC8898
Published
September 2020
Authors
R. Shekh-Yusef; C. Holmberg; V. Pascual
Status
PROPOSED STANDARD
Stream
IETF
Area
art
Pages
15
Also known as
Updates:
RFC 3261

Topics

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/8898-third-party-token-based-authentication-and-authorization-for-session-initiation