RFC 1620 (rfc1620) - Page 2 of 19
Internet Architecture Extensions for Shared Media
Alternative Format: Original Text Document
RFC 1620 Shared Media IP Architecture May 1994
1. INTRODUCTION
This memo concerns the implications of shared medium networks for the
architecture of the TCP/IP protocol suite. General familiarity with
the TCP/IP architecture and the IP protocol is assumed.
The Internet architecture is founded upon what was originally called
the "Catenet model" [PSC81]. Under this model, the Internet
(originally dubbed "the Catenet") is formed using routers (originally
called "gateways") to interconnect distinct and perhaps diverse
networks. An IP host address (more correctly characterized as a
network interface address) is formed of the pair (net#,host#). Here
"net#" is a unique IP number assigned to the network (or subnet) to
which the host is attached, and "host#" identifies the host on that
network (or subnet).
The original Internet model made the implicit assumptions that each
network has a single IP network number and that networks with
different numbers may interchange packets only through routers.
These assumptions may be violated for networks implemented using a
common "shared medium" (SM) at the link layer (LL). For example,
network managers sometimes configure multiple IP network numbers
(usually subnet numbers) on a single broadcast-type LAN such as an
Ethernet. The large (switched) public data networks (LPDNs), such as
SMDS and B-ISDN, form a potentially more important example of shared
medium networks. Any two systems connected to the same shared medium
network are capable of communicating directly at the LL, without IP
layer switching by routers. This presents an opportunity to optimize
performance and perhaps lower cost by eliminating unnecessary LL hops
through the medium.
This memo discusses how unnecessary hops can be eliminated in a
shared medium, while retaining the coherence of the existing Internet
architecture. This issue has arisen in a number of IETF Working
Groups concerned with LPDNs, including IPLPDN, IP over ATM, IDRP for
IP, and BGP. It is time to take a careful look at the architectural
issues to be solved. This memo first summarizes the relevant aspects
of the original Internet architecture (Section 2), and then it
explains the extra-hop problems created by shared media networks
(Section 3). Finally, it discusses some possible solutions (Section
4).
2. THE ORIGINAL INTERNET ARCHITECTURE
We very briefly review the original architecture, to introduce the
terminology and concepts. Figure 1 illustrates a typical set of four
networks A, ... D, represented traditionally as clouds,
interconnected by routers R2, R3, and R4. Routers R1 and R5 connect
Braden, Postel & Rekhter