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

IETF · RFC · RFC3841

RFC3841 · Caller Preferences for the Session Initiation Protocol (SIP)

Caller Preferences for the Session Initiation Protocol (SIP)

This document describes a set of extensions to the Session Initiation Protocol (SIP) which allow a caller to express preferences about request handling in servers. These preferences include the ability to select which Uniform Resource Identifiers (URI) a request gets routed to, and to specify certain request handling directives in proxies and redirect servers. It does so by defining three new request header fields, Accept-Contact, Reject-Contact, and Request-Disposition, which specify the caller's preferences. [STANDARDS-TRACK]

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

This document describes a set of extensions to the Session Initiation Protocol (SIP) which allow a caller to express preferences about request handling in servers. These preferences include the ability to select which Uniform Resource Identifiers (URI) a request gets routed to, and to specify certain request handling directives in proxies and redirect servers. It does so by defining three new request header fields, Accept-Contact, Reject-Contact, and Request-Disposition, which specify the caller's preferences. [STANDARDS-TRACK]

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

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

Полные импортированные сведения карточки
{
  "id": "RFC3841",
  "number": 3841,
  "title_en": "Caller Preferences for the 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 describes a set of extensions to the Session Initiation Protocol (SIP) which allow a caller to express preferences about request handling in servers. These preferences include the ability to select which Uniform Resource Identifiers (URI) a request gets routed to, and to specify certain request handling directives in proxies and redirect servers. It does so by defining three new request header fields, Accept-Contact, Reject-Contact, and Request-Disposition, which specify the caller's preferences. [STANDARDS-TRACK]",
  "authors": [
    "J. Rosenberg",
    "H. Schulzrinne",
    "P. Kyzivat"
  ],
  "organizations": [],
  "publication_date": "2004-08-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": "rai",
  "area_ru": "rai",
  "working_group": "sip",
  "source_draft": "draft-ietf-sip-callerprefs-10",
  "page_count": 26,
  "doi": "10.17487/RFC3841",
  "keywords": [
    "SIP",
    "Session Initiation Protocol",
    "Uniform Resource Identifiers",
    "URI",
    "Accept-Contact",
    "Reject-Contact",
    "Request-Disposition"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3841/",
    "html": "https://www.rfc-editor.org/rfc/rfc3841.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3841.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3841/"
  }
}