Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!botter!star!ast
From: ast@cs.vu.nl
Newsgroups: comp.std.internat
Subject: Query about OSI Transport address structure
Message-ID: <487@ast.cs.vu.nl>
Date: Wed, 2-Sep-87 04:52:11 EDT
Article-I.D.: ast.487
Posted: Wed Sep  2 04:52:11 1987
Date-Received: Sat, 5-Sep-87 09:42:08 EDT
Sender: ast@cs.vu.nl
Reply-To: ast@cs.vu.nl ()
Organization: VU Informatica, Amsterdam
Lines: 12


If anyone knows how transport addresses (TSAPs) are constructed in the OSI
model, could you let me know please.  In particular, is a TSAP a 
concatenation of an NSAP (e.g., an X.121 address) and a local part?
If not, when a session entity does a CONNECT.request, how does the
transport entity figure out which NSAP it has to use to access the
relevant remote  transport entity?  Is there an ISO standard on TSAP
naming?

Thanks.

Andy Tanenbaum (ast@cs.vu.nl)