RFC 2225 (rfc2225) - Page 2 of 28

Classical IP and ARP over ATM

Alternative Format: Original Text Document
< Previous
Next >
RFC 2225                  IP and ARP over ATM                 April 1998


   8.7.1  ATMARP/InATMARP Request and Reply Packet Formats  . . . . 18
   8.7.2  Receiving Unknown ATMARP packets  . . . . . . . . . . . . 20
   8.7.3  TL, ATM Number, and ATM Subaddress Encoding . . . . . . . 20
   8.7.4  ATMARP_NAK Packet Format  . . . . . . . . . . . . . . . . 21
   8.7.5  Variable Length Requirements for ATMARP Packets . . . . . 21
   8.8  ATMARP/InATMARP Packet Encapsulation  . . . . . . . . . . . 22
   9. IP BROADCAST ADDRESS  . . . . . . . . . . . . . . . . . . . . 23
   10. IP MULTICAST ADDRESS . . . . . . . . . . . . . . . . . . . . 23
   11. SECURITY CONSIDERATIONS  . . . . . . . . . . . . . . . . . . 23
   12. MIB SPECIFICATION  . . . . . . . . . . . . . . . . . . . . . 24
   13. OPEN ISSUES  . . . . . . . . . . . . . . . . . . . . . . . . 24
   14. REFERENCES . . . . . . . . . . . . . . . . . . . . . . . . . 24
   15. AUTHORS' ADDRESSES . . . . . . . . . . . . . . . . . . . . . 26
   APPENDIX A - Update Information  . . . . . . . . . . . . . . . . 27
   FULL COPYRIGHT STATEMENT . . . . . . . . . . . . . . . . . . . . 28

1.  ABSTRACT

   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 5.  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.

2.  ACKNOWLEDGMENT

   The authors would like to thank the efforts of the IP over ATM
   Working Group of the IETF.  Without their substantial, and sometimes
   contentious support, of the Classical IP over ATM model, this updated
   memo would not have been possible.  Section 7, on Default MTU, has
   been incorporated directly from Ran Atkinson's RFC 1626, with his
   permission.  Thanks to Andy Malis for an early review and comments
   for rolc and ion related issues.






Laubach & Halpern           Standards Track
< Previous
Next >