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

IETF · RFC · RFC6675

RFC6675 · A Conservative Loss Recovery Algorithm Based on Selective Acknowledgment (SACK) for TCP

A Conservative Loss Recovery Algorithm Based on Selective Acknowledgment (SACK) for TCP

This document presents a conservative loss recovery algorithm for TCP that is based on the use of the selective acknowledgment (SACK) TCP option. The algorithm presented in this document conforms to the spirit of the current congestion control specification (RFC 5681), but allows TCP senders to recover more effectively when multiple segments are lost from a single flight of data. This document obsoletes RFC 3517 and describes changes from it. [STANDARDS-TRACK]

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

This document presents a conservative loss recovery algorithm for TCP that is based on the use of the selective acknowledgment (SACK) TCP option. The algorithm presented in this document conforms to the spirit of the current congestion control specification (RFC 5681), but allows TCP senders to recover more effectively when multiple segments are lost from a single flight of data. This document obsoletes RFC 3517 and describes changes from it. [STANDARDS-TRACK]

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

obsoletes: RFC3517

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

Полные импортированные сведения карточки
{
  "id": "RFC6675",
  "number": 6675,
  "title_en": "A Conservative Loss Recovery Algorithm Based on Selective Acknowledgment (SACK) for TCP",
  "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": "This document presents a conservative loss recovery algorithm for TCP that is based on the use of the selective acknowledgment (SACK) TCP option. The algorithm presented in this document conforms to the spirit of the current congestion control specification (RFC 5681), but allows TCP senders to recover more effectively when multiple segments are lost from a single flight of data. This document obsoletes RFC 3517 and describes changes from it. [STANDARDS-TRACK]",
  "authors": [
    "E. Blanton",
    "M. Allman",
    "L. Wang",
    "I. Jarvinen",
    "M. Kojo",
    "Y. Nishida"
  ],
  "organizations": [],
  "publication_date": "2012-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": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "tcpm",
  "source_draft": "draft-ietf-tcpm-3517bis-02",
  "page_count": 15,
  "doi": "10.17487/RFC6675",
  "keywords": [
    "transmission control protocol",
    "retransmission",
    "congestion control"
  ],
  "formats": [
    "TXT",
    "HTML"
  ],
  "relations": {
    "obsoletes": [
      "RFC3517"
    ],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc6675/",
    "html": "https://www.rfc-editor.org/rfc/rfc6675.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc6675.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc6675/"
  }
}