The IP Over NBMA (ION) Archive[Date Prev][Date Next][Thread Prev][Thread Next] [Date Index][Thread Index][Author Index][Subject Index] ATMARP server source code/"classic IP"
Claudia Grandy writes:
>
> I'm doing some research on classic IP, and am looking for ATMARP server source
> [...]
I am curious about the genesis of the term "classic IP." Can anyone tell
me where this came from. In particular it appears to be a euphemism for
unicast IP, i.e. IP minus many-to-many multicast.
RFC 1577 "Classical IP and ARP over ATM" January 1993 states:
This memo describes the initial deployment of ATM within "classical"
IP networks as a direct replacement for local area networks
(ethernets) and for IP links which interconnect routers, either
within or between administrative domains. The "classical" model here
refers to the treatment of the ATM host adapter as a networking
interface to the IP protocol stack operating in a LAN-based paradigm.
Characteristics of the classical model are:
o The same maximum transmission unit (MTU) size is used for all VCs
in a LIS [2]. (Refer to Section 5.)
o Default LLC/SNAP encapsulation of IP packets.
o End-to-end IP routing architecture stays the same.
o IP addresses are resolved to ATM addresses by use of an ATMARP
service within the LIS - ATMARPs stay within the LIS. From a
client's perspective, the ATMARP architecture stays faithful to
the basic ARP model presented in [3].
o One IP subnet is used for many hosts and routers. Each VC
directly connects two IP members within the same LIS.
The term "end-to-end" above appears to assume point-to-point connections
to match the connection-oriented nature of ATM.
Thanks in advance for any insights here.
all the best, Don
--
Don Brutzman Naval Postgraduate School, Code UW/Br Root 200 work 408.656.2149
Monterey California 93943-5000 USA fax 408.656.3679
Virtual worlds/underwater robots/Internet http://www.stl.nps.navy.mil/~brutzman
|
|