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

IETF · RFC · RFC3581

RFC3581 · An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing

An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing

The Session Initiation Protocol (SIP) operates over UDP and TCP, among others. When used with UDP, responses to requests are returned to the source address the request came from, and to the port written into the topmost Via header field value of the request. This behavior is not desirable in many cases, most notably, when the client is behind a Network Address Translator (NAT). This extension defines a new parameter for the Via header field, called "rport", that allows a client to request that the server send the response back to the source IP address and port from which the request originated. [STANDARDS-TRACK]

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

The Session Initiation Protocol (SIP) operates over UDP and TCP, among others. When used with UDP, responses to requests are returned to the source address the request came from, and to the port written into the topmost Via header field value of the request. This behavior is not desirable in many cases, most notably, when the client is behind a Network Address Translator (NAT). This extension defines a new parameter for the Via header field, called "rport", that allows a client to request that the server send the response back to the source IP address and port from which the request originated. [STANDARDS-TRACK]

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

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

Полные импортированные сведения карточки
{
  "id": "RFC3581",
  "number": 3581,
  "title_en": "An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing",
  "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 Session Initiation Protocol (SIP) operates over UDP and TCP, among others. When used with UDP, responses to requests are returned to the source address the request came from, and to the port written into the topmost Via header field value of the request. This behavior is not desirable in many cases, most notably, when the client is behind a Network Address Translator (NAT). This extension defines a new parameter for the Via header field, called \"rport\", that allows a client to request that the server send the response back to the source IP address and port from which the request originated. [STANDARDS-TRACK]",
  "authors": [
    "J. Rosenberg",
    "H. Schulzrinne"
  ],
  "organizations": [],
  "publication_date": "2003-08-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-ietf-sip-symmetric-response-01",
  "page_count": 13,
  "doi": "10.17487/RFC3581",
  "keywords": [
    "SIP",
    "Session Initiation Protocol",
    "Symmetric Response Routing",
    "report client server"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc3581/",
    "html": "https://www.rfc-editor.org/rfc/rfc3581.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc3581.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc3581/"
  }
}