The IP Over NBMA (ION) Archive

Cell Relay Retreat>ION Archive>month:1996-Dec> msg00152



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

1577 client vs classic2 server: interoperablity issues

  • From: salo@msc.edu (Tim Salo)
  • Date: Fri, 20 Dec 1996 14:58:33 -0600 (CST)
  • Cc: ion@nexen.com

> Date: Wed, 18 Dec 1996 11:07:21 -0800
> From: rajeev@trillium.com
> To: ion@nexen.com, kvm@trillium.com, bgleeson@cisco.com
> Subject: Re:  1577 client vs classic2 server: interoperablity issues
> 	[...]
> If not, then we basically have a non backward compatible spec and
> system administrators will have to explicitly configure their
> LISs to run either all v1 or all v2. Is that the intended "transition"
> from v1 to v2?

If our experience is any indication, these same systems administrators
are upgrading their ATM software on a regular basis, (to fix bugs and
to gain support for new features), and their ATM hardware on a periodic
basis.

What is the liklihood of vendors providing only minimal implementations
of v1, (i.e., that the vendors never enhanced their v1 server
implementation)?

What is the liklihood that a customer installed an early, minimal v1
server implementation and then never upgraded?

By the way, I suspect that vendors will do the "right thing" for their
customers without cluttering up the classic2 and NHRP specs.  I think
that, for example, mandatory InaATMRPs, ought to _not_ be included in
classic2.

-tjs