The IETF process depends on peer review. However, IETF documents are generally written to be useful for implementors, not reviewers. In particular, while great care is generally taken to provide a complete description of the state machines and bits on the wire, this level of detail tends to get in the way of initial understanding. This document describes an approach for providing protocol "models" that allow reviewers to quickly grasp the essence of a system. This memo provides information for the Internet community.
IETF · RFCОфициальная английская аннотация
The IETF process depends on peer review. However, IETF documents are generally written to be useful for implementors, not reviewers. In particular, while great care is generally taken to provide a complete description of the state machines and bits on the wire, this level of detail tends to get in the way of initial understanding. This document describes an approach for providing protocol "models" that allow reviewers to quickly grasp the essence of a system. This memo provides information for the Internet community.
{
"id": "RFC4101",
"number": 4101,
"title_en": "Writing Protocol Models",
"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": "The IETF process depends on peer review. However, IETF documents are generally written to be useful for implementors, not reviewers. In particular, while great care is generally taken to provide a complete description of the state machines and bits on the wire, this level of detail tends to get in the way of initial understanding. This document describes an approach for providing protocol \"models\" that allow reviewers to quickly grasp the essence of a system. This memo provides information for the Internet community.",
"authors": [
"E. Rescorla",
"IAB"
],
"organizations": [],
"publication_date": "2005-06-01",
"current_status": "INFORMATIONAL",
"current_status_ru": "Информационный",
"publication_status": "INFORMATIONAL",
"publication_status_ru": "Информационный",
"lifecycle": "informational",
"lifecycle_ru": "Справочный",
"stream": "IAB",
"stream_ru": "Совет по архитектуре Интернета (IAB)",
"area": "",
"area_ru": "",
"working_group": "",
"source_draft": "draft-iab-model-03",
"page_count": 22,
"doi": "10.17487/RFC4101",
"keywords": [
"document review"
],
"formats": [
"TXT",
"HTML"
],
"relations": {
"obsoletes": [],
"obsoleted_by": [],
"updates": [],
"updated_by": [],
"is_also": [],
"see_also": []
},
"links": {
"info": "https://www.rfc-editor.org/info/rfc4101/",
"html": "https://www.rfc-editor.org/rfc/rfc4101.html",
"txt": "https://www.rfc-editor.org/rfc/rfc4101.txt",
"datatracker": "https://datatracker.ietf.org/doc/rfc4101/"
}
}