Cell Relay Archive

Cell Relay Retreat>List Archive>month:1997-Jul> msg00110



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

Re: ATM Applications Protocols

  • From: manfredi@arl.bna.boeing.com
  • Date: Wed, 23 Jul 1997 16:13:10 -0600

In article <5r57eb$bdq@verdi.nethelp.no>,
  sthaug@nethelp.no (Steinar Haug) wrote:
>
> [Saso STOJANOVSKI]
>
> |   start forgetting tcp.
> |
> |   think of using sscop in an end-to-end fashion.
>
> Good luck in getting ATM in all end systems. Personally, I wouldn't
> want to bet on what will be forgotten first, TCP or ATM...

Actually, the issue is not ATM vs TCP at all. It is instead SSCOP vs TCP.
Not that I disagree with your emotional outburst, Steinar, but if ATM is
to be used for reliable data transmission, it requires a
connection-oriented protocol just as IP does. After all, both ATM and IP
are best effort media, and it's only misnomer that calls ATM "connection
oriented." It is not. It is circuit switched, but still best effort.

So ATM needs something, and its native connection-oriented, error-free
protocol is called SSCOP (Service Specific Connection Oriented Protocol,
Q.SAAL1). As far as I can tell, SSCOP and TCP are functionally similar. I
have no idea whether SSCOP is any more "efficient" than TCP, when running
over any of the AALs.

Maybe we should form a SSCOP/IP political party? Just to incite the ire of
the IP-chauvinists?

Bert
manfredi@arl.bna.boeing.com

-------------------==== Posted via Deja News ====-----------------------
      http://www.dejanews.com/     Search, Read, Post to Usenet