IP modifications for ATM
Tony Zaide <tony.zaide@wcom.com> Wed, 22 May 1996 22:51 UTC
Received: from ietf.cnri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01584; 22 May 96 18:51 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa01580; 22 May 96 18:51 EDT
Received: from guelah.nexen.com by CNRI.Reston.VA.US id aa05860; 22 May 96 18:51 EDT
Received: from maelstrom.nexen.com (maelstrom.nexen.com [204.249.97.5]) by guelah.nexen.com (8.7.3/8.7.3) with ESMTP id SAA29940; Wed, 22 May 1996 18:36:18 -0400 (EDT)
Received: (from root@localhost) by maelstrom.nexen.com (8.7.3/8.7.3) id SAA03760 for ip-atm-out; Wed, 22 May 1996 18:30:06 -0400 (EDT)
Received: from nexen.nexen.com (nexen.nexen.com [204.249.96.18]) by maelstrom.nexen.com (8.7.3/8.7.3) with ESMTP id SAA03750 for <ip-atm@nexen.com>; Wed, 22 May 1996 18:30:03 -0400 (EDT)
Received: from juliet (juliet.wiltel.com [165.122.152.60]) by nexen.nexen.com (8.7.3/8.7.3) with ESMTP id SAA01623 for <ip-atm@nexen.com>; Wed, 22 May 1996 18:29:59 -0400 (EDT)
Received: from GWSMTP.WCOM.COM (actually host gwsmtp.wiltel.com) by juliet; Wed, 22 May 1996 17:28:21 -0500
Received: from NGWDTULCHE03-Message_Server by GWSMTP.WCOM.COM with Novell_GroupWise; Wed, 22 May 1996 17:27:49 -0500
Message-Id: <s1a34e95.008@GWSMTP.WCOM.COM>
X-Mailer: Novell GroupWise 4.1
Date: Wed, 22 May 1996 17:27:38 -0500
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Tony Zaide <tony.zaide@wcom.com>
To: ip-atm@nexen.com
Subject: IP modifications for ATM
UUEncode: TRUE
X-Orig-Sender: owner-ip-atm@nexen.com
Precedence: bulk
X-Info: Please send "unsubscribe ip-atm" to majordomo@nexen.com
X-Info: Please send "subscribe ion" to majordomo@nexen.com
X-Info: You can send both requests in one message
Hello everyone My intent is not to fuel another debate, but simply for my own understanding. I have posed the following question at the ATM Year '96 but did not obtain a clear answer: With all the work that has been proposed to modify the IP protocol suite (i.e., RSVP MARS, .... etc) to give QoS and signalling capabilities among others, has there been any thought to let IP know the concept of virtual circuits? In other words, can the IP hardware interface drivers be modified such it can recognize the presence of either an ATM-based underlying network (NMBA), or a LAN-based network (CSMA/CD, TR, ... ). If it sees an ATM-based network, then it sends the traffic at a VC rate, rather than at the link speed. The purpose would be to increase the throughput of IP over ATM traffic not to provide QoS, since sending traffic at VC rate might decrease the probability of packet discards at the relatively smaller ingress buffers on the ATM switch, thus decreasing re-transmitts. Rgs, Tony >>> Albert Manfredi <manfredi@engr05.comsys.rockwell.com> 05/06/96 - 02:13pm >>> The reason why ATM seems to be receiving so much bad press lately with respect to carrying IP (and in many circles, carrying IP is seen as being critical to its survival), is that IP over ATM is perceived as being hopelessly complicated. In my opinion, one reason for this state of affairs is that IP over ATM proposals are invariably IP over generic NBMA net proposals. So ATM's assets must always be discounted or ignored, and ATM ends up being a liability every time, compared with broadcast LANs. And, of course, all the cases that have to be covered result in complicated header formats.
- IP modifications for ATM Tony Zaide
- Re: IP modifications for ATM Bryan Gleeson
- Re: IP modifications for ATM Paul Doolan