Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP), September 2020
- File formats:
- Also available: XML file for editing
- PROPOSED STANDARD
- RFC 3261
- R. Shekh-Yusef
- sipcore (art)
Cite this RFC: TXT | XML | BibTeX
Discuss this RFC: Send questions or comments to the mailing list firstname.lastname@example.org
Other actions: View Errata | Submit Errata | Find IPR Disclosures from the IETF | View History of RFC 8898
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.
For the definition of Status, see RFC 2026.
For the definition of Stream, see RFC 8729.