home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.dcom.cell-relay
- Path: sparky!uunet!sun-barr!decwrl!pa.dec.com!nntpd2.cxo.dec.com!nntpd.lkg.dec.com!carafe.enet.dec.com!goldstein
- From: goldstein@carafe.enet.dec.com (Fred R. Goldstein)
- Subject: Re: new AAL (SSCOP?)
- Message-ID: <1992Nov17.230148.14636@nntpd.lkg.dec.com>
- Sender: usenet@nntpd.lkg.dec.com (USENET News System)
- Organization: Digital Equipment Corp., Littleton MA USA
- Date: Tue, 17 Nov 1992 23:00:18 GMT
- Lines: 19
-
-
- In article <JH.92Nov12193519@etana.funet.fi>, jh@etana.funet.fi (Juha Heinanen) writes...
- >What it doesn't have is multiplexing (addressing) capability. If you
- >would add that, then you and I could use the SAME protocol for Q.93B
- >(with null address fields) and for real end-to-end transport purpose
- >(with address fields). So I'm against SSCOP only because of this
- >omission.
-
- Juha,
-
- Multiplexing is not included because it is not always required. But
- it is not forbidden, either. I think the right answer is to converge
- a simple transport layer, something like TP0 or maybe UDP, right above
- SSCOP. But for users who don't require multiplexing, it would be a
- burden to require it.
- ---
- Fred R. Goldstein goldstein@carafe.tay2.dec.com
- k1io or goldstein@delni.enet.dec.com voice:+1 508 952 3274
- Standard Disclaimer: Opinions are mine alone; sharing requires permission.
-