Xref: utzoo comp.mail.uucp:4833 alt.fax:799 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!van-bc!sl From: sl@van-bc.wimsey.bc.ca (Stuart Lynne) Newsgroups: comp.mail.uucp,alt.fax Subject: Re: Re: Domain Registration (was Re: Imminent death of UUCP Zone predicted) Message-ID: <1075@van-bc.wimsey.bc.ca> Date: 26 Jul 90 20:30:21 GMT References: <11R41EF@xds13.ferranti.com> <961@van-bc.wimsey.bc.ca> <1990Jul26.025310.4158@chinet.chi.il.us> Organization: Unifax Communications Lines: 65 In article <1990Jul26.025310.4158@chinet.chi.il.us> les@chinet.chi.il.us (Leslie Mikesell) writes: >In article <961@van-bc.wimsey.bc.ca> sl@van-bc.wimsey.bc.ca (Stuart Lynne) writes: } }> user@+number.phone for dialup mail }> user@+number.fax for fax } }What we really need is a single machine that understands both. The originator }should put a tone on the line so that the answering machine can automatically }roll over to a voice phone or modem when something else calls, thus avoiding }the need for separate lines. It should interoperate with existing fax }machines, converting text to fax image when it detects that it is sending }a mail message to a fax-only device. When 2 similar machines connect, they }would use something resembling SMTP to exchange either text messages or }encoded images with encapsulating headers that would allow forwarding over }typical mail connections. The simplest versions would probably be PC cards }with software to view, print and manipulate using the normal PC devices. }Standalone units might have serial ports, network connections, hard disk }(of course), fax-style scanner and printer, etc. A single machine could }thus give you fax-over-internet and mail to anywhere you can dial. Actually what I had in mind was using the existing fax protocols. Specifically there is proposal to standardize a file transfer protocol (BFTP) using fax modems. So if you are sending mail you fire up your T.30 protocol engine, connect to the remote end and check if they support BFTP. If they don't you deliver the message by converting to a bitmap and sending the image. If the remote end supports BFTP you forward a (for example) BSMTP file containing the mail message and information on how to forward. With some of the new modems coming out you will be able to get Fax, 1200/2400 and MNP all in one box. So the above becomes feasible. It will probably take another year or so before the modems are able to provide mechanisms to allow incoming calls to be either fax or data. Rest assured that the modem manufacturers know that we want that. They just havn't figured out how to do it reliably. }>Are we going to allow them in routes? }> }> site_a!site_b!+18005551234.phone!site_c!site_d!user }Normally you would just dial up the one you want. Do people forward faxes? Yes, they do. And with BFTP sending a BSMTP file the above would work. We probably do want two protocols though. user@+number.phone for dialup mail Would allow mail to be forwarded to a remote site, assuming a 1200/2400 Hayes compatible modem at the far end. Perhaps a BSMTP file transferred using ZModem or Kermit. user@+number.fax for fax Would allow mail to be forwarded to a remote site by sending a bit image if the remote machine is note capable of BFTP (i.e. a real fax machine) or using BSMTP via BFTP if the remote machine is capable. We can make the assumption that the contents of the mail message is RFC822 compatible. -- Stuart.Lynne@wimsey.bc.ca ubc-cs!van-bc!sl 604-937-7532(voice)