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

IETF · RFC · RFC6141

RFC6141 · Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)

Re-INVITE and Target-Refresh Request Handling in the Session Initiation Protocol (SIP)

The procedures for handling SIP re-INVITEs are described in RFC 3261. Implementation and deployment experience has uncovered a number of issues with the original documentation, and this document provides additional procedures that update the original specification to address those issues. In particular, this document defines in which situations a UAS (User Agent Server) should generate a success response and in which situations a UAS should generate an error response to a re-INVITE. Additionally, this document defines further details of procedures related to target-refresh requests. [STANDARDS-TRACK]

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

The procedures for handling SIP re-INVITEs are described in RFC 3261. Implementation and deployment experience has uncovered a number of issues with the original documentation, and this document provides additional procedures that update the original specification to address those issues. In particular, this document defines in which situations a UAS (User Agent Server) should generate a success response and in which situations a UAS should generate an error response to a re-INVITE. Additionally, this document defines further details of procedures related to target-refresh requests. [STANDARDS-TRACK]

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

updates: RFC3261

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

Полные импортированные сведения карточки
{
  "id": "RFC6141",
  "number": 6141,
  "title_en": "Re-INVITE and Target-Refresh Request Handling in 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": "The procedures for handling SIP re-INVITEs are described in RFC 3261. Implementation and deployment experience has uncovered a number of issues with the original documentation, and this document provides additional procedures that update the original specification to address those issues. In particular, this document defines in which situations a UAS (User Agent Server) should generate a success response and in which situations a UAS should generate an error response to a re-INVITE. Additionally, this document defines further details of procedures related to target-refresh requests. [STANDARDS-TRACK]",
  "authors": [
    "G. Camarillo",
    "C. Holmberg",
    "Y. Gao"
  ],
  "organizations": [],
  "publication_date": "2011-03-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-reinvite-08",
  "page_count": 26,
  "doi": "10.17487/RFC6141",
  "keywords": [
    "re-INVITE",
    "offer/answer",
    "rollback"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC3261"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6141/",
    "html": "https://www.rfc-editor.org/rfc/rfc6141.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6141.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6141/"
  }
}