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

IETF · RFC · RFC6357

RFC6357 · Design Considerations for Session Initiation Protocol (SIP) Overload Control

Design Considerations for Session Initiation Protocol (SIP) Overload Control

Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document discusses models and design considerations for a SIP overload control mechanism. This document is not an Internet Standards Track specification; it is published for informational purposes.

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

Overload occurs in Session Initiation Protocol (SIP) networks when SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document discusses models and design considerations for a SIP overload control mechanism. This document is not an Internet Standards Track specification; it is published for informational purposes.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC6357",
  "number": 6357,
  "title_en": "Design Considerations for Session Initiation Protocol (SIP) Overload Control",
  "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 SIP servers have insufficient resources to handle all SIP messages they receive. Even though the SIP protocol provides a limited overload control mechanism through its 503 (Service Unavailable) response code, SIP servers are still vulnerable to overload. This document discusses models and design considerations for a SIP overload control mechanism. This document is not an Internet Standards Track specification; it is published for informational purposes.",
  "authors": [
    "V. Hilt",
    "E. Noel",
    "C. Shen",
    "A. Abdelal"
  ],
  "organizations": [],
  "publication_date": "2011-08-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": "soc",
  "source_draft": "draft-ietf-soc-overload-design-08",
  "page_count": 25,
  "doi": "10.17487/RFC6357",
  "keywords": [
    "Session Initiation Protocol",
    "Overload Control",
    "Congestion Collapse"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6357/",
    "html": "https://www.rfc-editor.org/rfc/rfc6357.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6357.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6357/"
  }
}