STONE@SUMEX-AIM.ARPA (Jeffrey Stone) (09/29/86)
A few months ago, I sent out a query for commercially available X.400 implementations. This message collects the responses I received which provide information about X.400 implementations. I contacted Sydney and Retix who were both cooperative in getting me further information about their X.400 products. In the U.S. contact Sydney at (213) 479 4621 in Los Angeles. I spoke with Caleb Greenberg. Contact Charles Fogg of Retix (Santa Monica) at (213) 829 4922. The following messages were received in response to my query for commercially available X.400 packages. Thanks to all who contributed. Jeffrey Stone Menlo Park, California ================================================================= > To: Jeffrey Stone <STONE@sumex-aim.arpa> > Subject: Re: x.400 implementations > Date: Wed, 02 Jul 86 09:58:59 +0100 > From: Teus Hagen <mcvax!oce-rd1!teus@seismo.CSS.GOV> > > Apart from the obvious ones (like from Canada and Japan) I'm aware > of the following X.400 implementations: > - COSAC developed by French CNET > - GIPSI developed by INRIA in Paris, taken over by BULL Paris > - EAN probably the same as from Canada > > ========================================================================== > Date: Wed, 2 Jul 86 13:32:21 pdt > From: Gerald Neufeld <neufeld%ubc.csnet@CSNET-RELAY.ARPA> > To: Jeffrey Stone <STONE@SUMEX-AIM.ARPA> > Subject: x.400 implementations > > You will likely get several pointers to this software but... > > The EAN system is a X.400 system which was developed using Unix 4.2bsd. > It also runs on Dec VMS and Unix System V. It includes X.25 support for > the 4.2bsd kernel, TP0 transport , session, most of P1 and P2. It does > not durrently implement P3. EAN was developed at the University of > British Columbia, Dept of Computer Science (distributed systems research > group). EAN also includes a gateway to RFC822. It is running in several > countries, including Canada (CDNnet), England, Sweden, Finland, Germany, > AUstralia etc. > > For two papers on EAN see the "Second Internation Symposium on Computer > Message Systems",IFIP TC.6, Sept, 1985 Washington, D.C. > > It is also available commercially via Sydney Developement Corp. Vancouver > B.C. > > Gerald > ========================================================================== > Date: 2 Jul 1986 15:32:41 PDT > From: POSTEL@B.ISI.EDU > Subject: re: X.400 > To: stone@SUMEX-AIM.ARPA > cc: postel@B.ISI.EDU > > > Jeffery: > > You should find out about Charlie Lynn's implementation at BBN. Ask > Lynn (CLYNN@A.BBN.CON) or Harry Forsdick (Forsdick@Diamond.BBN.COM). > > --jon. > ------- ========================================================================== > Date: Tue, 8 Jul 86 12:06:02 pdt > From: estrin%usc-cseb@usc-cse.usc.edu (Deborah L. Estrin) > To: stone@sumex-aim.arpa > Subject: x.400 > > There is a company called RETIX in santa monica california that > has an x.400 supposedly in c and developed under unix 4.2. > I would very much like to see your list after you get it. > To get product literature from Retix, call (213)829-4922 > Deborah Estrin ========================================================================== > Date: 17 Jul 86 19:08 +0200 > From: Nicholas_Newman_CEC%QZCOM.MAILNET@MIT-MULTICS.ARPA > To: "Jeffrey Stone" <STONE@SUMEX-AIM.ARPA>, > Sue_Hamer_F_&_L%EUROKOM@UCL-CS.ARPA, > Sue_Hamer_FLAS%EUROKOM@UCL-CS.ARPA > Subject: Your request for information on MHS implementations > > In text 184341 of 2/7/86 (original date 1/7/86) (NB European date order) > you asked for information on X.400 implementations. I relayed your > request to Sue Hamer of Fischer & Lorentz in Denmark, who uses the > Eurokom service at University College Dublin. She has asked me to > relay her reply to you. Please note she is known on QZ COM > as person 5503 or as person 10583 if you find it as difficult as I do > to remember how to string network names together. > Likewise Sue, Jeffrey Stone is known as person 20118. > > Here is Sue's text: > > > (188428) 86-07-16 21.02 /25 lines/ @EUROKOM: Sue Hamer F & L > Receiver: Nicholas Newman CEC <713> -- Received: 86-07-17 18.42 > Sender: Transfer (from) JANET > Receiver: @EUROKOM: Sue Hamer F & L <3> -- Received: 86-07-16 21.05 > Subject: Subject: response to Mr. Stones request for mhs info > ------------------------------------------------------------ > %Original date: 16 Jul 86 12:12 CET. TF: DSKC:239770.MAI > %FROM: Sue Hamer F & L@EUROKOM > > Please transfer a message to Mr. Stone, since Janet doesnt like my > addressing scheme. Since I am an external user of QZCOM (@ sue hamer) > it should be possible for you to include me in the conference to receive > replies. I would be grateful if you could arrange this for me. > regards, > sue > > subject: Response to request for info on x.400 implementations > In response to your request for information on X.400 implementations: > we are currently performing a survey on European message handling > products for the Commission of the European Communities and expect to > produce a report in August. Perhaps we could pool ideas?? > regards > sue hamer > Fischer an Lorenz > Vangede Bygade 65, > dk-2820 gentofte > denmark > tel: 45 1 683100 > email QZCOM : @ sue hamer .. note I am an external user > > > (Text 188428)------------------------------ > > > > > ========================================================================== > Date: Fri, 8 Aug 86 13:39:47 pdt > From: Erik Skovgaard <erik%sydney.cdn%ubc.csnet@CSNET-RELAY.ARPA> > To: Jeffrey Stone <STONE@SUMEX-AIM.ARPA> > Subject: commerically available x.400 > > Sydney's X.400 package is available on the following operating systems: > > - Unix 4.2 BSD > - Unix V (rel 2) > - VAX/VMS > - VM/CMS > - MS-DOS > - The Guardian (Tandem) > > In addition, the software has been run on Data General, Nixdorf, Siemens, > Apollo, SUN, Perkin-Elmer (Concurrent), ITL and other proprietary systems. > > The software is currently RUNNING and available (not just a "future") as > you know. We would like to make a bit of a distinction between the EAN > software and Sydcom M400 that Sydney provides. In addition to the formats > mentioned above, we now also have a number of different architectures > available, including a separate UA which runs on a PC. The UA-MTA protocol > is P3. > > Our support ranges from education to turnkey systems. The software is > supported out of our Vancouver and London (UK) offices. In addition to > straight X.400, we also support gateways to ARPAmail (this message > was composed on my X.400 system and gateway'd to ARPA), UUCP and PROFS. > > For further info contact: > > Erik Skovgaard, Director, Research and Engineering > Sydney Development Corp. > > Mailbox addresses: EAN: erik@sydney.cdn > ARPA: erik%sydney%ubc.mailnet@MIT-MULTICS.arpa > UUCP: ...!hnp4!alberta!ubc-vision!sydney.cdn!erik > Envoy: E.SKOVGAARD > Telemail: [E.Skovgaard]TELECOM/CANADA > > > I'd be interested in your list when it is finished. > > > > ....Erik. > > P.S. DEC now has a gateway to their All-in-1. This is commercially available. > > ========================================================================== > Posted-Date: Fri, 8 Aug 86 18:40:50 mdt > Date: Fri, 8 Aug 86 18:40:50 mdt > From: ut-sally!dougm@ico.ISC.COM (Doug McCallum) > To: STONE@SUMEX-AIM.ARPA > Subject: Re: commercially available x.400 > > I would be interested in your list when it is complete. I have > some information back at the office that I can send you on OSI > vendors, some of which have (or will have, or claim to have) > X.400. I don't have current status information (this is very > old), so don't trust any of it. It should give you an idea about > status or at least that they are working on things. The data was > gathered sometime between January and March. The addresses and > phone numbers aren't on-line. Here are the names and notes from > talking to a sales/marketting type at the company: > > OSI Software: vendor: OMNICOM > contact: Paul Luebbe > > Transport Layers and above - all written in C > > Layer 4 - 7 > Class 0 and Class 2 are finished > Class 4 will be finished soon > Session: BAS and BCS are finished > BSS will be read soon > Presentation is ready - includes an ASN.1 compiler > CASE is nearly complete - CCR eventually > Odette until FTAM is available > X.400 is for later > > All software is written in portable C and is currently running on a > System V (AT&T 3B2/400) as a user process. It has been ported to > MS-DOS as well. Throughput measurements are supposed to be good. All > software is layered with a kernel that is optional. It is possible to > mix and match or subset the software in many ways. UNIX dependencies > are minimized by keeping any OS or hardware specific functions > separate. The code has been designed with byte-swap problems in mind > so don't have to worry about byte ordering. > > OMNICOM's emphasis is on the upper layers. The contact and his > manager are active members of ISO SC21. > > Development is being done in France by Marben Informatique. > > OSI Software: vendor: TITN > contact: David Rogers, Pierre DuBos > > Layers 3-7 planned > X.25 for network layer > Transport Class 0 and Class 2 available > Transport Class 4 in development > Working on Session > Working on X.400 > > Written in C. Mostly an X.25 company. Moving toward OSI since > that is where X.25 is going. They are an international comapny > with offices in Europe. > > > I hope this is of some help. You should give all the vendors a > call to get current status on any product. About the two vendors > you mentioned, Sydney has had the EAN stuff for a long time and > have a number of customers. I currently have a leaning toward > Retix for OSI software. No real reason, they just seemed to be > more conversant on the subject than anyone else I talked to. > > Another company which doesn't have X.400 but is moving into the > OSI and MAP arenas is Touch Communications which is being run > by Charly Bass (of Ungermann-Bass). > > Doug McCallum > Interactive Systems > UUCP: {hao, nbires, cbosgd}!ico!dougm > or dougm@ico.UUCP > or dougm@ico.ISC.COM > > ========================================================================== > Date: Mon, 11 Aug 86 16:56 N > From: <PIETIKAI%FINFUN.BITNET@WISCVM.ARPA> (Panu Pietik{inen) > Subject: RE: commerically available x.400 > To: STONE@sumex-aim.arpa > X-Original-To: STONE@sumex-aim.arpa, PIETIKAINEN > > I have heard of the X.400 implementation made at KDD. That is the Japanese > equivalent to PTT's. I received a bit information on their system but > never got to see any documentation although I have requested it. The > person I have contacted at KDD is a Unix manager so he isn't just the > right person to contact there but better than nothing. I have received > *ONE* message from him. I'll include it here for you. > > I would be greatful if you made a short summary of all the X.400 > products you find and mail a copy of the summary to me. > > --Panu Pietikainen > Finnish University Network Coordinator > > P.S. Digital has announced a "X.400" product shortly. > > ----------------------------------------------------------------------------- > Return-Path: <asami@kddspeech> > Date: Thu, 22 May 86 18:23:44 jst > From: kddlab!asami@hplabs.ARPA (TOHRU ASAMI ) > Subject: KDD's MHS > To: PIETIKAI@FINFUN.BITNET > Message-Id: <517137824/asami@kddspeech> > > Panu: > >I have heard that you at the KDD have developed a mailing system > >that conforms with the CCITT X.400 or the Message Handling Systems > >(MHS) standard. I would be very intersted to receive more infomation > >about your system. I appreciate all your help. > Our MHS was developed on Mitshubishi's minicomputers, and the compatibility > of our MHS and UBC's MHS (developed on UNIX) was wholely checked. If > you want to have some documentation, I'll send it to you as soon as > possible. > > Tohru > > P.S. Your mail was received on Apr. 18. Sorry to reply late. > ========================================================================== > Date: Tue 12 Aug 86 18:00:40-PDT > From: Karl Auerbach <AUERBACH@CSL.SRI.COM> > Subject: X.400 Implementation > To: Stone@SUMEX-AIM.ARPA > > Our company, Epilogue Technology Corporation, is developing various X.400 > products. These will not be available until sometime after the first of > the year. We are not yet willing to publish details on the net. However, > we might be able to disclose some of our plans if I know how the information > would be used and to whom it would be disseminated. > > (It IS OK, however, to mention publicly that Epilogue IS working on X.400 > products. For information contact: > > Karl Auerbach > Epilogue Technology Corporation > P.O. Box 5432 > Redwood City, CA 94063 > USA > (415) 594-1141 > > > By-the-way, I would be interested in seeing your list. > > Good Luck with your search, > > --karl-- (Karl Auerbach, auerbach@csl.sri.com) > ------- ========================================================================== > Date: Thu, 14 Aug 86 18:09:37 CDT > From: sue@rsch.wisc.edu (Sue Klein Lebeck) > To: stone@sumex-aim.arpa > Subject: mhs implementations > Cc: sue@rsch.wisc.edu > > Jeffrey -- > > Hi; I happened by an old query from you (sent to mhs_implementation > and to arpa-mhs) regarding the availability of X.400 implementations. > I don't remember whether I responded at that time or not. Assuming not, > and risking repeating myself, I'm including a blurb below about > my future X400 implementation (written in C, FOR 4.2bsd Unix.) > > Cheers, Sue > > > Here at the University of Wisconsin, we are implementing a fairly > complete OSI protocol suite. Our work is funded by IBM; our target > machine is an IBM PC/RT running 4.2bsd Unix. > > I am implementing the X.400 component of this suite. I am approximately > half finished; I expect to be finished at year's end. > > I have no authoritative information as to the availability of this > software. It is reasonable and probable that it will be available > to Universities. In any case, there will almost certainly be a > beta-test site search in some months. Perhaps you would be interested? > > My software (as well as our FTAM software) utilizes our own Session > implementation, as well as TP and IP implementations (the latter > two being in the kernel.) Planned "network solutions" include > Ethernet (TP4/IP/Ethernet), IBM token-ring (TP4/IP/token-ring) and, > hopefully X.25 (TP0/X.25). > > My software can also be used over the standard 4.2bsd TCP/IP implementation. > No ad hoc protocol exchange has been added to support passing back and forth > of the "turn" when in that mode, so only the MONOLOGUE dialogue mode is > supported when using TCP. > > I stated above that the X.400 implementation will be "finished" at > year's end. Note, however, that various ease-of-use features (such as > runtime configuration capabilities, notification-correlation, etc.) > will probably be added next year. > > > Sue Klein Lebeck > Univ. of WI-Madison > Comp. Sci. Dept. > 1210 W. Dayton > Madison, WI 53706 > 608-263-4076 > sue@rsch.wisc.edu > -------