RFC 875

Gateways, architectures, and heffalumps, September 1982

File formats:
icon for text file icon for PDF icon for HTML
Status:
UNKNOWN
Author:
M.A. Padlipsky
Stream:
[Legacy]

Cite this RFC: TXT  |  XML  |   BibTeX

DOI:  https://doi.org/10.17487/RFC0875

Discuss this RFC: Send questions or comments to the mailing list iesg@ietf.org

Other actions: Submit Errata  |  Find IPR Disclosures from the IETF  |  View History of RFC 875


Abstract

This RFC is a discussion about the role of gateways in an internetwork, especially the problems of translating or mapping protocols between different protocol suites. The discussion notes possible functionality mis-matches, undesirable routing "singularity points", flow control issues, and high cost of translating gateways. Originally published as M82-51 by the MITRE Corporation, Bedford, Massachusetts.


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.




Advanced Search