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

IETF · RFC · RFC9368

RFC9368 · Compatible Version Negotiation for QUIC

Compatible Version Negotiation for QUIC

QUIC does not provide a complete version negotiation mechanism but instead only provides a way for the server to indicate that the version the client chose is unacceptable. This document describes a version negotiation mechanism that allows a client and server to select a mutually supported version. Optionally, if the client's chosen version and the negotiated version share a compatible first flight format, the negotiation can take place without incurring an extra round trip. This document updates RFC 8999.

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

QUIC does not provide a complete version negotiation mechanism but instead only provides a way for the server to indicate that the version the client chose is unacceptable. This document describes a version negotiation mechanism that allows a client and server to select a mutually supported version. Optionally, if the client's chosen version and the negotiated version share a compatible first flight format, the negotiation can take place without incurring an extra round trip. This document updates RFC 8999.

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

updates: RFC8999

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

Полные импортированные сведения карточки
{
  "id": "RFC9368",
  "number": 9368,
  "title_en": "Compatible Version Negotiation for QUIC",
  "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": "QUIC does not provide a complete version negotiation mechanism but instead only provides a way for the server to indicate that the version the client chose is unacceptable. This document describes a version negotiation mechanism that allows a client and server to select a mutually supported version. Optionally, if the client's chosen version and the negotiated version share a compatible first flight format, the negotiation can take place without incurring an extra round trip. This document updates RFC 8999.",
  "authors": [
    "D. Schinazi",
    "E. Rescorla"
  ],
  "organizations": [],
  "publication_date": "2023-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": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "quic",
  "source_draft": "draft-ietf-quic-version-negotiation-14",
  "page_count": 15,
  "doi": "10.17487/RFC9368",
  "keywords": [
    "quic",
    "version",
    "negotiation",
    "compatible",
    "incompatible",
    "not quite tls",
    "tls-ng"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [
      "RFC8999"
    ],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9368/",
    "html": "https://www.rfc-editor.org/rfc/rfc9368.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9368.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9368/"
  }
}