🚀 go-pugleaf

There is the APS Alliance working on this problem.
Contact Frode Hernes <Frode.Hernes@maxware.noprmd.telemax.no> for details.

-- 
                   Harald Tveit Alvestrand
Harald.Alvestrand@delab.sintef.no
C=no;PRMD=uninett;O=sintef;OU=delab;S=alvestrand;G=harald
+47 7 59 70 94

roseberry@taney.uscghq.uscg.mil writes:

>	If there is a system running OSI in one location and another
>	system also running OSI in another location, is it possible
>	to do transfer files via FTAM (or send mail via X.400) using
>	something other than X.25 or a LAN ?

>	In other words is there something for making temporary connections
>	over phone lines for OSI much like SLIP does for TCP/IP (and
>	async DECNET does for DECNET) ?

The next version of X.25 is said to include an async version of LAPB.
The async HDLC variant is already defined in the 1991 Version of 
ISO 3309, so I don't expect anything revolutionaly new in X.25(92). 
Contact me, if you want a short description of async HDLC framing.

If you want to use the telephone net for CONS, check ISO 10732. For
CONS over ISDN, look at ISO 9574. They mostly refer to X.25 and define
a few additional details.

A work group (APS Aliance) is working on additional specifications for
using X.400 over the telephone net. This will perhaps eventually result
in a CCITT standard. 

If you prefer CLNP, check the latest PPP version. It supports OSI in addition
to TCP/IP.

Markus

-- 
Markus Kuhn, Computer Science student -=-=- University of Erlangen, Germany
Internet: mskuhn@immd4.informatik.uni-erlangen.de  |  X.500 entry available
----- Anyone participating in the use of MS-DOS, Heroin or Cocaine is -----
---- simply not getting the most out of life possible. (Brian Downing) ----

roseberry@taney.uscghq.uscg.mil writes:


>	If there is a system running OSI in one location and another
>	system also running OSI in another location, is it possible
>	to do transfer files via FTAM (or send mail via X.400) using
>	something other than X.25 or a LAN ?

You could use ISDN, for example.

>	In other words is there something for making temporary connections
>	over phone lines for OSI much like SLIP does for TCP/IP (and
>	async DECNET does for DECNET) ?

I do not know much about it, but X.32 is a protocol for use over phone lines. 
My understanding is that it offers similar services to X.25 and so is
effectively a "dial-up X.25", and some telecommunications service providers
offer a service whereby you can access their X.25 network via X.32.


>	I understand that whatever connection is set up, it will be very
>	slow in comparison to X.25 or LAN.

>	Thanks for any answers.

>	- Bert Roseberry
>	  roseberry@taney.uscghq.uscg.mil


			-- regards, John Gottschalk

===================================================================== 
     John Gottschalk (john@citr.uq.oz.au) 
     Project Manager,
     Centre for Information Technology Research,
     The University of Queensland, 4072, 
     Brisbane, Queensland, Australia,
     +61 7 365 4321 (phone), +61 7 365 4399 (fax)
===================================================================== 

From article <1993Jan5.211153.122@taney.uscghq.uscg.mil>, by roseberry@taney.uscghq.uscg.mil:
> 
> 	If there is a system running OSI in one location and another
> 	system also running OSI in another location, is it possible
> 	to do transfer files via FTAM (or send mail via X.400) using
> 	something other than X.25 or a LAN ?
> 
> 	In other words is there something for making temporary connections
> 	over phone lines for OSI much like SLIP does for TCP/IP (and
> 	async DECNET does for DECNET) ?
ETSI (European Telecommunications Standards Institute) is planning
a standard for file transfer over ISDN. FTAM is being considered as
one of two possible protocols (the other one is a Videotex standard).
ETSI Technical report DTR/TE-01019 "File Transfer over the ISDN" provides 
an overview and makes recommendations for further work, i.e. it is not a 
standard. Since there is a high demand for file transfer over ISDN
within Europe, the actual standard can be expected in the near future.
Exactly how near is not known to me.

-- Just van den Broecke - AT&T NS NL - The Netherlands
   jvdbroec@ihlpw.ih.att.com