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

IETF · RFC · RFC7984

RFC7984 · Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network

Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network

RFC 3263 defines how a Session Initiation Protocol (SIP) implementation, given a SIP Uniform Resource Identifier (URI), should locate the next-hop SIP server using Domain Name System (DNS) procedures. As SIP networks increasingly transition from IPv4-only to dual-stack, a quality user experience must be ensured for dual- stack SIP implementations. This document updates the DNS procedures described in RFC 3263 for dual-stack SIP implementations in preparation for forthcoming specifications for applying "Happy Eyeballs" principles to SIP.

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

RFC 3263 defines how a Session Initiation Protocol (SIP) implementation, given a SIP Uniform Resource Identifier (URI), should locate the next-hop SIP server using Domain Name System (DNS) procedures. As SIP networks increasingly transition from IPv4-only to dual-stack, a quality user experience must be ensured for dual- stack SIP implementations. This document updates the DNS procedures described in RFC 3263 for dual-stack SIP implementations in preparation for forthcoming specifications for applying "Happy Eyeballs" principles to SIP.

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

updates: RFC3263

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

Полные импортированные сведения карточки
{
  "id": "RFC7984",
  "number": 7984,
  "title_en": "Locating Session Initiation Protocol (SIP) Servers in a Dual-Stack IP Network",
  "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": "RFC 3263 defines how a Session Initiation Protocol (SIP) implementation, given a SIP Uniform Resource Identifier (URI), should locate the next-hop SIP server using Domain Name System (DNS) procedures. As SIP networks increasingly transition from IPv4-only to dual-stack, a quality user experience must be ensured for dual- stack SIP implementations. This document updates the DNS procedures described in RFC 3263 for dual-stack SIP implementations in preparation for forthcoming specifications for applying \"Happy Eyeballs\" principles to SIP.",
  "authors": [
    "O. Johansson",
    "G. Salgueiro",
    "V. Gurbani",
    "D. Worley"
  ],
  "organizations": [],
  "publication_date": "2016-09-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-dns-dual-stack-08",
  "page_count": 10,
  "doi": "10.17487/RFC7984",
  "keywords": [
    "A record",
    "address family preference",
    "AAAA record",
    "DNS",
    "getaddrinfo",
    "Happy Eyeballs",
    "IPv6 address selection",
    "SIP",
    "SRV record",
    "dual-stack",
    "IPv4",
    "IPv6"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC3263"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc7984/",
    "html": "https://www.rfc-editor.org/rfc/rfc7984.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc7984.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc7984/"
  }
}