metasystema.org
UpdatedBEST CURRENT PRACTICEIETF streamBCP89

RFC 3819: Advice for Internet Subnetwork Designers

Still current, but amended. Parts of this document are changed or extended by RFC 9599. Read both.

In plain English — editorial summary, not part of the RFC

This document provides advice to the designers of digital communication equipment, link-layer protocols, and packet-switched local networks (collectively referred to as subnetworks), who wish to support the Internet protocols but may be unfamiliar with the Internet architecture and the implications of their design choices on the performance and efficiency of the Internet. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC3819
Published
July 2004
Authors
P. Karn; C. Bormann; G. Fairhurst; D. Grossman; R. Ludwig; J. Mahdavi; G. Montenegro; J. Touch; L. Wood
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
tsv
Pages
60
Also known as
BCP89
Updated by:
RFC 9599

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/3819-advice-for-internet-subnetwork-designers