RFC 2225: Classical IP and ARP over ATM
In plain English — editorial summary, not part of the RFC
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]
Document record
- Document ID
- RFC2225
- Published
- April 1998
- Authors
- M. Laubach; J. Halpern
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 28
- Also known as
- —
- Updated by:
- RFC 5494
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1577 (1994)
- RFC 1626 (1994)
- RFC 2225 (1998)
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2269Using the MARS Model in non-ATM NBMA NetworksCurrent
January 1998
- RFC 2226IP Broadcast over ATM NetworksCurrent
October 1997
- RFC 2121Issues affecting MARS Cluster SizeCurrent
March 1997
- RFC 2379RSVP over ATM Implementation GuidelinesCurrent
August 1998
- RFC 1971IPv6 Stateless Address AutoconfigurationObsoleted
August 1996
- RFC 2098Toshiba's Router Architecture Extensions for ATM : OverviewCurrent
February 1997
- RFC 2366Definitions of Managed Objects for Multicast over UNI 3.0/3.1 based ATM NetworksObsoleted
July 1998
- RFC 2022Support for Multicast over UNI 3.0/3.1 based ATM NetworksCurrent
November 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?