Re[2]: Last Call: SMTP Service Extension for Content Negotiation toP roposed Standard
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re[2]: Last Call: SMTP Service Extension for Content Negotiation toP roposed Standard



Michael,

I suggest you might wish to recall a few terms.  Probably, you
had occasion to deal with these terms in the past, but you appear
to have forgotten them:

USER
INSTALLED BASE
UBIQUITOUS
OPERATOR
TASK

These terms all have significant meaning outside of computer
engineering.

Go back and reread:

 JSC-EV)> FAX is NOT dead at NASA.

 JSC-EV)> We send a LOT of documents to other centers that cannot be sent via e-mail
 JSC-EV)> (photocopies of shipping documents, flight manifests, older engineering
 JSC-EV)> drawings, etc [things that are not available electronically]).  That is why
 JSC-EV)> I am so interested in seeing this work completed.

A real user speaking.

On an IETF list, it would be good to contribute to finding ways
to use the Internet to solve his problem, rather than sniping.

Gene
gene.gaines at gainesgroup.com
Sterling, Virginia


On Thursday, July 4, 2002, 3:41:03 PM, Michael wrote:

> -----BEGIN PGP SIGNED MESSAGE-----


>>>>>> "JSC-EV)" == JSC-EV) (LM <COLES> writes:
>     JSC-EV)> FAX is NOT dead at NASA.

>     JSC-EV)> We send a LOT of documents to other centers that cannot be sent via e-mail
>     JSC-EV)> (photocopies of shipping documents, flight manifests, older engineering
>     JSC-EV)> drawings, etc [things that are not available electronically]).  That is why
>     JSC-EV)> I am so interested in seeing this work completed.

>   Do you really send faxes? Is this what you really want to do? I mean to say
> you want to negotiate 9600 baud connections over the Internet using some kind
> of VoIP?

>   Or do you mean that you want a way to send a binary piece of data
> (representing an image) from one party to another in an automated, batch
> oriented way.

>   Perhaps I can introduce you to a protocol called "FTP". 
>   It has rather interesting authentication features that are in widespread use.
>   If you prefer, there is another protocol called "HTTP" that might
> help. I've heard it is pretty popular now. If you want batch transfer with
> retries, there is also UUCP-over-TCP. Port 540.

> ====

>   Seriously, we need *LESS* junk sent by email, not more.

>   The whole FAX over email problem is simply endemic of the fact that we have
> no(%) *end-user* to *end-user* file transfer protocols. 
>   (To be useful, we would ideally need a global PKI, but we can certainly
> start simpler)

> ]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
> ]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
> ] mcr at sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
> ] panic("Just another NetBSD/notebook using, kernel hacking, security guy");  [

> -----BEGIN PGP SIGNATURE-----
> Version: 2.6.3ia
> Charset: latin1
> Comment: Finger me for keys

> iQCVAwUBPSSkzYqHRg3pndX9AQH6yQP/Xl9CsNfTw61qTlWJkNtxzgwt2iqi9Ncf
> ONvV2fP+f9gU1/bH/kCnrzkiHWEc+hiDiAlvI9VSkSZvhukG+mXhO3B2fkcycPeo
> nySP//5NbtUbuc0XwAYzHZj9Uru/E6Skgz97Ar/OxjdXXQ6KohLEfNxGwgAryOPo
> og/ePO4AB3E=
> =YPaY
> -----END PGP SIGNATURE-----


-- 




Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.

Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.