RFC 1932: IP over ATM: A Framework Document
In plain English — editorial summary, not part of the RFC
It is hoped that this document, in classifying ATM approaches and issues will help to focus the IP over ATM working group's direction.This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC1932
- Published
- April 1996
- Authors
- R. Cole; D. Shur; C. Villamizar
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- int
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2775Internet TransparencyCurrent
February 2000
- RFC 1890RTP Profile for Audio and Video Conferences with Minimal ControlObsoleted
January 1996
- RFC 1889RTP: A Transport Protocol for Real-Time ApplicationsObsoleted
January 1996
- RFC 2914Congestion Control PrinciplesUpdated
September 2000
- RFC 2998A Framework for Integrated Services Operation over Diffserv NetworksCurrent
November 2000
- RFC 3077A Link-Layer Tunneling Mechanism for Unidirectional LinksCurrent
March 2001
- RFC 3102Realm Specific IP: FrameworkCurrent
October 2001
- RFC 3550RTP: A Transport Protocol for Real-Time ApplicationsUpdated
July 2003
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?