| | Roxen Community: RFC 3819 Advice for Internet Subnetwork Designers (Best Current Practice) (Site not responding. Last check: 2007-11-02) |
 | | 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. |
 | | Subnetwork designers should be aware of the tradeoffs between fairness and efficiency inherent in many transmission scheduling algorithms. |
 | | Subnetworks connecting more than two systems must provide their own internal Layer-2 forwarding mechanisms, either implicitly (e.g., broadcast) or explicitly (e.g., switched). |
| community.roxen.com /developers/idocs/rfc/rfc3819.html (16555 words) |