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

IETF · RFC · RFC8262

RFC8262 · Content-ID Header Field in the Session Initiation Protocol (SIP)

Content-ID Header Field in the Session Initiation Protocol (SIP)

This document specifies the Content-ID header field for usage in the Session Initiation Protocol (SIP). This document also updates RFC 5621, which only allows a Content-ID URL to reference a body part that is part of a multipart message-body. This update enables a Content-ID URL to reference a complete message-body and metadata provided by some additional SIP header fields. This document updates RFC 5368 and RFC 6442 by clarifying their usage of the SIP Content-ID header field.

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

This document specifies the Content-ID header field for usage in the Session Initiation Protocol (SIP). This document also updates RFC 5621, which only allows a Content-ID URL to reference a body part that is part of a multipart message-body. This update enables a Content-ID URL to reference a complete message-body and metadata provided by some additional SIP header fields. This document updates RFC 5368 and RFC 6442 by clarifying their usage of the SIP Content-ID header field.

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

updates: RFC5368, RFC5621, RFC6442

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

Полные импортированные сведения карточки
{
  "id": "RFC8262",
  "number": 8262,
  "title_en": "Content-ID Header Field 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": "This document specifies the Content-ID header field for usage in the Session Initiation Protocol (SIP). This document also updates RFC 5621, which only allows a Content-ID URL to reference a body part that is part of a multipart message-body. This update enables a Content-ID URL to reference a complete message-body and metadata provided by some additional SIP header fields. This document updates RFC 5368 and RFC 6442 by clarifying their usage of the SIP Content-ID header field.",
  "authors": [
    "C. Holmberg",
    "I. Sedlacek"
  ],
  "organizations": [],
  "publication_date": "2017-10-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-content-id-10",
  "page_count": 14,
  "doi": "10.17487/RFC8262",
  "keywords": [
    "SIP"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC5368",
      "RFC5621",
      "RFC6442"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8262/",
    "html": "https://www.rfc-editor.org/rfc/rfc8262.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8262.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8262/"
  }
}