Writing Protocol Models
RFC 4101, “Writing Protocol Models”, is an Informational document published in June 2005 by E. Rescorla, IAB. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 4101 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 4102 Registration of the text/red MIME Sub-Type
- RFC 4103 RTP Payload for Text Conversation
- RFC 4098 Terminology for Benchmarking BGP Device Convergence in the Control Plane
- RFC 4104 Policy Core Extension Lightweight Directory Access Protocol Schema
- RFC 4097 Middlebox Communications Protocol Evaluation
- RFC 4105 Requirements for Inter-Area MPLS Traffic Engineering
- RFC 4096 Policy-Mandated Labels Such as "Adv:" in Email Subject Headers Considered Ineffective At Best
- RFC 4106 The Use of Galois/Counter Mode in IPsec Encapsulating Security Payload