RE: RFC 4612 - historic status
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: RFC 4612 - historic status



Frank,

No, it does not.  It's simply an alternative representation of the fax data.
The receiver could receive it and print it, create audio tones (if it
desired), produce a TIFF image and e-mail it, or whatever else it wished to
do.

Paul

> -----Original Message-----
> From: Frank Ellermann [mailto:nobody at xyzzy.claranet.de]
> Sent: Tuesday, August 15, 2006 2:55 AM
> To: ietf at ietf.org
> Subject: Re: RFC 4612 - historic status
> 
> Dave Crocker wrote:
> 
> >> | audio -- audio data.  "Audio" requires an audio output
> >> |          device (such as a speaker or a telephone) to
> >> |          "display" the contents.  An initial subtype
> >> |          "basic" is defined in this document.
> [...]
> > In what way does this not satisfy *exactly* the requirements
> > for the audio top-level MIME type?
> 
> The final receiver isn't supposed to "hear" a fax arriving as
> phone call, "whistling" the replies.  Seriously, does this
> media type require a modem somewhere on the receiver's side ?
> 
> Frank
> 
> 
> 
> _______________________________________________
> Ietf mailing list
> Ietf at ietf.org
> https://www1.ietf.org/mailman/listinfo/ietf
> 




_______________________________________________
Ietf mailing list
Ietf at ietf.org
https://www1.ietf.org/mailman/listinfo/ietf




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.