RFC4774 · Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
There have been a number of proposals for alternate semantics for the Explicit Congestion Notification (ECN) field in the IP header RFC 3168. This document discusses some of the issues in defining alternate semantics for the ECN field, and specifies requirements for a safe coexistence in an Internet that could include routers that do not understand the defined alternate semantics. This document evolved as a result of discussions with the authors of one recent proposal for such alternate semantics. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
IETF · RFCОфициальная английская аннотация
There have been a number of proposals for alternate semantics for the Explicit Congestion Notification (ECN) field in the IP header RFC 3168. This document discusses some of the issues in defining alternate semantics for the ECN field, and specifies requirements for a safe coexistence in an Internet that could include routers that do not understand the defined alternate semantics. This document evolved as a result of discussions with the authors of one recent proposal for such alternate semantics. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
{
"id": "RFC4774",
"number": 4774,
"title_en": "Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field",
"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": "There have been a number of proposals for alternate semantics for the Explicit Congestion Notification (ECN) field in the IP header RFC 3168. This document discusses some of the issues in defining alternate semantics for the ECN field, and specifies requirements for a safe coexistence in an Internet that could include routers that do not understand the defined alternate semantics. This document evolved as a result of discussions with the authors of one recent proposal for such alternate semantics. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.",
"authors": [
"S. Floyd"
],
"organizations": [],
"publication_date": "2006-11-01",
"current_status": "BEST CURRENT PRACTICE",
"current_status_ru": "Лучшая современная практика",
"publication_status": "BEST CURRENT PRACTICE",
"publication_status_ru": "Лучшая современная практика",
"lifecycle": "active",
"lifecycle_ru": "Действующий",
"stream": "IETF",
"stream_ru": "IETF",
"area": "wit",
"area_ru": "Веб и транспорт Интернета",
"working_group": "tsvwg",
"source_draft": "draft-ietf-tsvwg-ecn-alternates-02",
"page_count": 15,
"doi": "10.17487/RFC4774",
"keywords": [],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [
"RFC6040"
],
"is_also": [
"BCP124"
],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc4774/",
"html": "https://www.rfc-editor.org/rfc/rfc4774.html",
"txt": "https://www.rfc-editor.org/rfc/rfc4774.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc4774/"
}
}