RFC 3269: Author Guidelines for Reliable Multicast Transport (RMT) Building Blocks and Protocol Instantiation documents
In plain English — editorial summary, not part of the RFC
This document provides general guidelines to assist the authors of Reliable Multicast Transport (RMT) building block and protocol instantiation definitions. The purpose of these guidelines is to ensure that any building block and protocol instantiation definitions produced contain sufficient information to fully explain their operation and use. In addition these guidelines provide directions to specify modular and clearly defined RMT building blocks and protocol instantiations that can be refined and augmented to safely create new protocols for use in new scenarios for which any existing protocols were not designed. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3269
- Published
- May 2002
- Authors
- R. Kermode; L. Vicisano
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4315Internet Message Access Protocol (IMAP) - UIDPLUS extensionCurrent
December 2005
- RFC 3260New Terminology and Clarifications for DiffservCurrent
April 2002
- RFC 3289Management Information Base for the Differentiated Services ArchitectureCurrent
June 2002
- RFC 3248A Delay Bound alternative revision of RFC 2598Current
March 2002
- RFC 3290An Informal Management Model for Diffserv RoutersCurrent
June 2002
- RFC 3247Supplemental Information for the New Definition of the EF PHB (Expedited Forwarding Per-Hop Behavior)Current
March 2002
- RFC 3246An Expedited Forwarding PHB (Per-Hop Behavior)Current
March 2002
- RFC 3243RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP CompressionCurrent
April 2002
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?