Classical IP and ARP over ATM (RFC1577)
Original Publication Date: 1994-Jan-01
Included in the Prior Art Database: 2019-Feb-13
Internet Society Requests For Comment (RFCs)
This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS). [STANDARDS-TRACK]
Network Working Group M. Laubach Request for Comments: 1577 Hewlett-Packard Laboratories Category: Standards Track January 1994
Classical IP and ARP over ATM
Status of this Memo
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
This memo defines an initial application of classical IP and ARP in an Asynchronous Transfer Mode (ATM) network environment configured as a Logical IP Subnetwork (LIS) as described in Section 3. This memo does not preclude the subsequent development of ATM technology into areas other than a LIS; specifically, as single ATM networks grow to replace many ethernet local LAN segments and as these networks become globally connected, the application of IP and ARP will be treated differently. This memo considers only the application of ATM as a direct replacement for the "wires" and local LAN segments connecting IP end-stations ("members") and routers operating in the "classical" LAN-based paradigm. Issues raised by MAC level bridging and LAN emulation are beyond the scope of this paper.
This memo introduces general ATM technology and nomenclature. Readers are encouraged to review the ATM Forum and ITU-TS (formerly CCITT) references for more detailed information about ATM implementation agreements and standards.
This memo could not have come into being without the critical review from Jim Forster of Cisco Systems, Drew Perkins of FORE Systems, and Bryan Lyles, Steve Deering, and Berry Kercheval of XEROX PARC. The concepts and models presented in , written by Dave Piscitello and Joseph Lawrence, laid the structural groundwork for this work. ARP  written by Dave Plummer and Inverse ARP  written by Terry Bradley and Caralyn Brown are the foundation of ATMARP presented in this memo. This document could have not been completed without the expertise of the IP over ATM Working Group of the IETF and the ad hoc PVC committee at the Amsterdam IETF meeting.
Laubach [Page 1]
RFC 1577 Classical IP and ARP over ATM January 1993
The following language conventions are used in the items of specification in this document:
o MUST, SHALL, or MANDATORY -- the item is an absolute requirement of the specification.
o SHOULD or RECOMMEND -- this item should generally be followed for all but exceptional circumstances.
o MAY or OPTIONAL -- the item is truly optional and may be followed or ignored according to the needs of the implementor.
The goal of this specification is to allow compatible and interoperable implementations for transmitting IP datagrams and ATM Address Resolution Protocol (ATMARP) requests and replies over ATM Adaptation Layer 5 (AAL5)[2,6].
Note: this memo defines only the operation of IP...