Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!usc!samsung!munnari.oz.au!murtoa.cs.mu.oz.au!ditmela!smart From: smart@ditmela.oz (Robert Smart) Newsgroups: comp.protocols.iso Subject: Re: Questions about X.400 Message-ID: <8061@ditmela.oz> Date: 18 Nov 89 10:51:07 GMT References: <1987@xyzzy.UUCP> <10100002@WL9.Prime.COM> Reply-To: smart@ditmela.oz.au (Robert Smart) Organization: CSIRO, Division of Information Technology, Australia Lines: 24 In article <10100002@WL9.Prime.COM> MYNARD@WL9.Prime.COM writes: > > X.400 mail really does work. > There seems to be a really big hole in X.400 to my mind, and that is administration. For TCP/IP I know how to get an IP address, how to get a domain name, how to get the name server records set up so that I can be reached. For X.400 and OSI: How do I get an NSAP (lets stick to Geographical ones, the others are fluff); How do I get PRMD/ORG/OU names? Are there any standards for names in the OSI world? Will people be able to use the same names for FTAM as for X.400 or is this an application specific matter in OSI? Is there an X.400 "world" or just lots of pairs of machines talking X.400 to each other? Who should I connect to with X.400 and who will then be able to reach me? In case you think I know nothing about X.400, I might say that we have at least 4 X.400 implementations running in our small lab with three of them attached to Australia's experimental X.400 facility. It seems to me that X.400 is going nowhere for administrative reasons mentioned. I don't even know of any attempts to address these problems in Australia. Bob Smart or