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

IETF · RFC · RFC5390

RFC5390 · Requirements for Management of Overload in the Session Initiation Protocol

Requirements for Management of Overload in the Session Initiation Protocol

Overload occurs in Session Initiation Protocol (SIP) networks when proxies and user agents have insufficient resources to complete the processing of a request. SIP provides limited support for overload handling through its 503 response code, which tells an upstream element that it is overloaded. However, numerous problems have been identified with this mechanism. This document summarizes the problems with the existing 503 mechanism, and provides some requirements for a solution. This memo provides information for the Internet community.

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

Overload occurs in Session Initiation Protocol (SIP) networks when proxies and user agents have insufficient resources to complete the processing of a request. SIP provides limited support for overload handling through its 503 response code, which tells an upstream element that it is overloaded. However, numerous problems have been identified with this mechanism. This document summarizes the problems with the existing 503 mechanism, and provides some requirements for a solution. This memo provides information for the Internet community.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC5390",
  "number": 5390,
  "title_en": "Requirements for Management of Overload in the Session Initiation Protocol",
  "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": "Overload occurs in Session Initiation Protocol (SIP) networks when proxies and user agents have insufficient resources to complete the processing of a request. SIP provides limited support for overload handling through its 503 response code, which tells an upstream element that it is overloaded. However, numerous problems have been identified with this mechanism. This document summarizes the problems with the existing 503 mechanism, and provides some requirements for a solution. This memo provides information for the Internet community.",
  "authors": [
    "J. Rosenberg"
  ],
  "organizations": [],
  "publication_date": "2008-12-01",
  "current_status": "INFORMATIONAL",
  "current_status_ru": "Информационный",
  "publication_status": "INFORMATIONAL",
  "publication_status_ru": "Информационный",
  "lifecycle": "informational",
  "lifecycle_ru": "Справочный",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "rai",
  "area_ru": "rai",
  "working_group": "sipping",
  "source_draft": "draft-ietf-sipping-overload-reqs-05",
  "page_count": 14,
  "doi": "10.17487/RFC5390",
  "keywords": [
    "sip",
    "overload handling",
    "503 response"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc5390/",
    "html": "https://www.rfc-editor.org/rfc/rfc5390.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc5390.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc5390/"
  }
}