RFC 3148: A Framework for Defining Empirical Bulk Transfer Capacity Metrics
In plain English — editorial summary, not part of the RFC
This document defines a framework for standardizing multiple BTC (Bulk Transport Capacity) metrics that parallel the permitted transport diversity. This memo provides information for the Internet community.
Document record
- Document ID
- RFC3148
- Published
- July 2001
- Authors
- M. Mathis; M. Allman
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 16
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2924Accounting Attributes and Record FormatsCurrent
September 2000
- RFC 3417Transport Mappings for the Simple Network Management Protocol (SNMP)Updated
December 2002
- RFC 3593Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsCurrent
September 2003
- RFC 2493Textual Conventions for MIB Modules Using Performance History Based on 15 Minute IntervalsObsoleted
January 1999
- RFC 7766DNS Transport over TCP - Implementation RequirementsUpdated
March 2016
- RFC 7828The edns-tcp-keepalive EDNS0 OptionCurrent
April 2016
- RFC 8337Model-Based Metrics for Bulk Transport CapacityCurrent
March 2018
- RFC 3150End-to-end Performance Implications of Slow LinksCurrent
July 2001
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?