Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!ncis.tis.llnl.gov!emsesmc.emse.fr!pays
From: pays@emsesmc.emse.fr (Paul-Andre PAYS)
Newsgroups: comp.protocols.iso.x400
Subject: Research areas in E-mail
Message-ID: <900206092210+0100.6385A.emsesmc*pays@emsesmc.emse.fr>
Date: 6 Feb 90 08:22:13 GMT
References: <25ce0b88.5151@polyslo.CalPoly.EDU>
Sender: root@ncis.tis.llnl.gov
Distribution: inet
Organization: The Internet
Lines: 37
Approved: post-x400@tis.llnl.gov


Let me add a few other comments,
1. some other topics
	distributed management of a domain or a set of cooperating domains
	(I am speaking of MHS domains, in the broad acceptance, ie obviously
	including X.400 MTA and UA, but also X.500, and for a lot of time
	also RFC-987 gatewaying with RFC mail systems). It is for example
	a very important issue for RARE, which we are currently investigating.
	(you may contact kaddour@cambur.emse.fr).

	security in MHS
	essential for wide acceptance in commercial organisations and use
	such as EDI or EFT. Again, this is closely related to X.500 DS.

	multimedia aspects.
	issues how to represent the time as a structuring element in a 
	a multimedia document (eg this sound must be played, while presenting
	this part of the text...)? data compression? and user interfaces
	ergonomy for such things?

2. PC to PC mail?
  I have personnaly some doubt about a pure PC to PC approach.
	. this already exist, is very limited, is outside the standard move
	. either you will never have something pewerfull, or you will bring
	   to pC user all the burden of MHS management
	. I cann't imagine MHS without DS (at least in the near future),
	   do you plan to integrate x.500 on the PC too...

  There something that seems nice for this purpose and that is part of
the standard: I mean the P7 MS (message store) approach
why not study carefully this one before starting something new,
and may be complete or make suggestions on how to extend it or
integrate it better with other PC based services (fax, telex...)

-- PAP

a