Known bugs and restrictions in version 0.12
===========================================

IP over ATM
-----------

 - clients don't always refresh their entry at ARP server (fixed ?)
 - ARP timers are too short and should be different for client and server
 - IP interfaces must not be reconfigured while up
 - requires local ATM address to be set on interface 0 on startup
 - taking an interface down and then up again hangs the system
 - encapsulation is broken (but works good enough for now)
 - atmarpd may not recover properly from link failures (but a resolution 
   request or such usually cures that)
 - atmarpd shouldn't invalidate entries on the first timeout in valid state
   but rather try one revalidation request first
 - CLIP (the old way of doing IP over ATM) isn't tested

Signaling
---------

 - never initiates a RESTART procedure
 - doesn't implement T322 (i.e. STATUS ENQUIRY is not retried)
 - atmsigd sometimes terminates ungracefully when encountering errors in
   signaling messages
 - no support for repeated information elements
 - there's currently no way to obtain SVC traffic parameters indicated by
   the remote party
 - atmsigd is reported to leak memory
 - SSCOP doesn't update the window properly
 - data retrieval is broken in SSCOP

ENI-155p driver
---------------

 - sometimes doesn't unqueue RX PDUs when being tortured with aping
 - SUNI loopback is untested
 - support for multiple adapters per machine is untested
 - doesn't handle unsolicited OAM cells gracefully
 - adapter may deadlock if buffer full of loss indications
 - doesn't properly zero pad area of AAL5 PDUs
 - driver should use bottom-half interrupt handler

ZN1221 driver
-------------

 - still hangs from time to time when sending
 - support for multiple adapters per machine is untested
 - SONET/SDH framing support is untested
 - timestamps should use uPD98401 timestamps

ATM over TCP
------------

 - driver is very limited in functionality
 - system may crash if atmtcp is killed
 - can't run IP over ATM using ATM over TCP
 - ATMTCP interfaces can't be taken down

ATM sockets and "common" layer
------------------------------

 - SVC close may block forever (waiting for atmsigd)
 - polled devices are broken as designed (and will eventually go away ...)
 - some system calls don't return full SVC SAP information
 - poor integration with other network code
 - buffer quotas/limits don't work yet

Miscellaneous
-------------

 - there are lots of known bugs not listed in this file (look for @@@ in
   the source)
 - there are still no "nice" applications
