home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!decwrl!decwrl!netcomsv!iscnvx!news
- From: news@iscnvx.ogi.edu
- Newsgroups: comp.dcom.cell-relay
- Subject: Re: new AAL (SSCOP?)
- Message-ID: <1992Nov9.225234.2523@iscnvx.lmsc.lockheed.com>
- Date: 9 Nov 92 22:52:34 GMT
- Article-I.D.: iscnvx.1992Nov9.225234.2523
- References: <1992Nov8.231642.7509@nntpd.lkg.dec.com> <1992Nov9.135828.5489@iscnvx.lmsc.lockheed.com>,<JH.92Nov9215100@etana.funet.fi>
- Sender: news@iscnvx.lmsc.lockheed.com (News)
- Reply-To: young@bantha.decnet.lockheed.com
- Organization: LMSC, Sunnyvale, California
- Lines: 20
-
- In article <JH.92Nov9215100@etana.funet.fi>, jh@etana.funet.fi (Juha Heinanen) writes:
- >after reading all messages related to SSCOP, i noticed that also
- >others suspected if there is sense in the current SSCOP proposal.
- >
- >we have two options:
- >
- >1. fix SSCOP to become a real transport protocol (hopefully the same
- >as being worked in ISO)
- >
- >2. make whatever changes are needed to an existing transport protocol
- >(eg. TCP) to satisfy the requirements of ATM (signalling)
-
- Wave protocols like a very high speed transport with receiver initiated
- selective recovery, rate based flow control, two way connection set up,
- and operates right over the path layer. Explicit connection teardown,
- multicast optional (wave can do its own), software implementable checksum
- in trailer. Wave doesn't need a network layer.
- Matt Young
- Lockheed
- (408) 756-6789
-