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

IETF · RFC · RFC3327

RFC3327 · Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts

Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts

The REGISTER function is used in a SIP system primarily to associate a temporary contact address with an address-of-record. This contact is generally in the form of a URI, such as Contact: <sip:alice@pc33.atlanta.com> and is generally dynamic and associated with the IP address or hostname of the SIP UA. The problem is that network topology may have one or more SIP proxies between the UA and the registrar, such that any request travelling from the user's home network to the registered UA must traverse these proxies. The REGISTER method does not give us a mechanism to discover and record this sequence of proxies in the registrar for future use. This document defines an extension header field, 'Path' which provides such a mechanism

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

The REGISTER function is used in a SIP system primarily to associate a temporary contact address with an address-of-record. This contact is generally in the form of a URI, such as Contact: <sip:alice@pc33.atlanta.com> and is generally dynamic and associated with the IP address or hostname of the SIP UA. The problem is that network topology may have one or more SIP proxies between the UA and the registrar, such that any request travelling from the user's home network to the registered UA must traverse these proxies. The REGISTER method does not give us a mechanism to discover and record this sequence of proxies in the registrar for future use. This document defines an extension header field, 'Path' which provides such a mechanism

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

updated_by: RFC5626

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

Полные импортированные сведения карточки
{
  "id": "RFC3327",
  "number": 3327,
  "title_en": "Session Initiation Protocol (SIP) Extension Header Field for Registering Non-Adjacent Contacts",
  "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 REGISTER function is used in a SIP system primarily to associate a temporary contact address with an address-of-record. This contact is generally in the form of a URI, such as Contact: <sip:alice@pc33.atlanta.com> and is generally dynamic and associated with the IP address or hostname of the SIP UA. The problem is that network topology may have one or more SIP proxies between the UA and the registrar, such that any request travelling from the user's home network to the registered UA must traverse these proxies. The REGISTER method does not give us a mechanism to discover and record this sequence of proxies in the registrar for future use. This document defines an extension header field, 'Path' which provides such a mechanism",
  "authors": [
    "D. Willis",
    "B. Hoeneisen"
  ],
  "organizations": [],
  "publication_date": "2002-12-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": "rai",
  "area_ru": "rai",
  "working_group": "sip",
  "source_draft": "draft-willis-sip-path-08",
  "page_count": 17,
  "doi": "10.17487/RFC3327",
  "keywords": [
    "SIP",
    "Session Initiation Protocol",
    "3gpp",
    "register",
    "contact",
    "path",
    "registrar",
    "user agent",
    "ua"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [
      "RFC5626"
    ],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3327/",
    "html": "https://www.rfc-editor.org/rfc/rfc3327.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3327.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3327/"
  }
}