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

IETF · RFC · RFC8787

RFC8787 · Location Source Parameter for the SIP Geolocation Header Field

Location Source Parameter for the SIP Geolocation Header Field

There are some circumstances where a Geolocation header field may contain more than one locationValue. Knowing the identity of the node adding the locationValue allows the recipient more freedom in selecting the value to look at first rather than relying solely on the order of the locationValues. This document defines the "loc-src" parameter so that the entity adding the locationValue to the Geolocation header field can identify itself using its hostname. This document updates RFC 6442.

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

There are some circumstances where a Geolocation header field may contain more than one locationValue. Knowing the identity of the node adding the locationValue allows the recipient more freedom in selecting the value to look at first rather than relying solely on the order of the locationValues. This document defines the "loc-src" parameter so that the entity adding the locationValue to the Geolocation header field can identify itself using its hostname. This document updates RFC 6442.

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

updates: RFC6442

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

Полные импортированные сведения карточки
{
  "id": "RFC8787",
  "number": 8787,
  "title_en": "Location Source Parameter for the SIP Geolocation Header Field",
  "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": "There are some circumstances where a Geolocation header field may contain more than one locationValue. Knowing the identity of the node adding the locationValue allows the recipient more freedom in selecting the value to look at first rather than relying solely on the order of the locationValues. This document defines the \"loc-src\" parameter so that the entity adding the locationValue to the Geolocation header field can identify itself using its hostname. This document updates RFC 6442.",
  "authors": [
    "J. Winterbottom",
    "R. Jesske",
    "B. Chatras",
    "A. Hutton"
  ],
  "organizations": [],
  "publication_date": "2020-05-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-locparam-06",
  "page_count": 8,
  "doi": "10.17487/RFC8787",
  "keywords": [
    "Emergency",
    "Call",
    "Location"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC6442"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8787/",
    "html": "https://www.rfc-editor.org/rfc/rfc8787.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8787.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8787/"
  }
}