RFC7053 · SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol
SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol
This document updates RFC 4960 by defining a method for the sender of a DATA chunk to indicate that the corresponding Selective Acknowledgment (SACK) chunk should be sent back immediately and should not be delayed. It is done by specifying a bit in the DATA chunk header, called the (I)mmediate bit, which can get set by either the Stream Control Transmission Protocol (SCTP) implementation or the application using an SCTP stack. Since unknown flags in chunk headers are ignored by SCTP implementations, this extension does not introduce any interoperability problems.
IETF · RFCОфициальная английская аннотация
This document updates RFC 4960 by defining a method for the sender of a DATA chunk to indicate that the corresponding Selective Acknowledgment (SACK) chunk should be sent back immediately and should not be delayed. It is done by specifying a bit in the DATA chunk header, called the (I)mmediate bit, which can get set by either the Stream Control Transmission Protocol (SCTP) implementation or the application using an SCTP stack. Since unknown flags in chunk headers are ignored by SCTP implementations, this extension does not introduce any interoperability problems.
{
"id": "RFC7053",
"number": 7053,
"title_en": "SACK-IMMEDIATELY Extension for the Stream Control Transmission Protocol",
"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 updates RFC 4960 by defining a method for the sender of a DATA chunk to indicate that the corresponding Selective Acknowledgment (SACK) chunk should be sent back immediately and should not be delayed. It is done by specifying a bit in the DATA chunk header, called the (I)mmediate bit, which can get set by either the Stream Control Transmission Protocol (SCTP) implementation or the application using an SCTP stack. Since unknown flags in chunk headers are ignored by SCTP implementations, this extension does not introduce any interoperability problems.",
"authors": [
"M. Tuexen",
"I. Ruengeler",
"R. Stewart"
],
"organizations": [],
"publication_date": "2013-11-01",
"current_status": "PROPOSED STANDARD",
"current_status_ru": "Предлагаемый стандарт",
"publication_status": "PROPOSED STANDARD",
"publication_status_ru": "Предлагаемый стандарт",
"lifecycle": "superseded",
"lifecycle_ru": "Заменён",
"stream": "IETF",
"stream_ru": "IETF",
"area": "wit",
"area_ru": "Веб и транспорт Интернета",
"working_group": "tsvwg",
"source_draft": "draft-ietf-tsvwg-sctp-sack-immediately-04",
"page_count": 8,
"doi": "10.17487/RFC7053",
"keywords": [],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [
"RFC9260"
],
"updates": [
"RFC4960"
],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc7053/",
"html": "https://www.rfc-editor.org/rfc/rfc7053.html",
"txt": "https://www.rfc-editor.org/rfc/rfc7053.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc7053/"
}
}