⌕ Поиск по атласу

IETF · RFC · RFC8898

RFC8898 · Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)

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

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.

Официальная английская аннотация

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.

Связи документа

updates: RFC3261

Официальный источник · 2020-09-01

Полные импортированные сведения карточки
{
  "id": "RFC8898",
  "number": 8898,
  "title_en": "Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "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.",
  "authors": [
    "R. Shekh-Yusef",
    "C. Holmberg",
    "V. Pascual"
  ],
  "organizations": [],
  "publication_date": "2020-09-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "art",
  "area_ru": "Приложения и взаимодействие в реальном времени",
  "working_group": "sipcore",
  "source_draft": "draft-ietf-sipcore-sip-token-authnz-17",
  "page_count": 15,
  "doi": "10.17487/RFC8898",
  "keywords": [
    "SIP OAuth",
    "3rd party authentication",
    "Third party authentication"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC3261"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8898/",
    "html": "https://www.rfc-editor.org/rfc/rfc8898.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8898.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8898/"
  }
}