ietf
[Top] [All Lists]

Re: RFC 4612 - historic status

2006-08-14 07:50:43


John C Klensin wrote:
is needed to do anything useful.  Unlike what Paul seems to
imply by his assertion that the signaling mechanisms are
essentially audio because they are analogous to DTMF tones, I
believe those non-text top-level types are differentiated by the
base capability that is required to _render_ the type, 


RFC2046:
    (3)   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.


As Paul indicated, T.38 is used between gateways.

The receiving gateway turns the data into a telephone call.

In what way does this not satisfy *exactly* the requirements for the audio
top-level MIME type?

d/
-- 

  Dave Crocker
  Brandenburg InternetWorking
  bbiw.net

_______________________________________________
Ietf mailing list
Ietf(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/ietf

<Prev in Thread] Current Thread [Next in Thread>