Real-Time Transport Protocol (RTP) Payload for Text Conversation Interleaved in an Audio Stream
draft-ietf-avt-audio-t140c-00

Received changes through RFC Editor sync (changed abstract to 'This memo describes how to carry real-time text conversation session contents in RTP packets. Text conversation session contents are specified in ITU-T Recommendation T.140.

One payload format is described for transmitting audio and text data within a single RTP session.

This RTP payload description recommends a method to include redundant text from already transmitted packets in order to reduce the risk of text loss caused by packet loss. This memo defines a Historic Document for the Internet community.')

IANA Comments:
We understand the IANA actions to be as follows:

1) Register the audio/t140c MIME Media Type in the following registry:
http://www.iana.org/assignments/media-types/audio/

2) Register a RTP payload format named "t140" in the following registry:
http://www.iana.org/assignments/rtp-parameters

What would the clock rate and channels be for this registration?

Section 10.2 describes SDP mapping of MIME parameters.  Does the IANA have any actual actions related to this or is this the RTP request mentioned in 2) above?

Section 10.3 describes Offer/Answer Consideration.  Does the IANA have any actual actions related to this?

IANA has sent a separate message to the authors of this document to get answers to the above questions.

[Ballot comment]
Gen-ART review comment by David Black:

I have one concern that I think needs attention - this draft is
proposed for initial publication as an Historic RFC.  It should
have a few sentences added to explain why this is being done,
including what implementers who are tempted to use this format
ought to do instead.

BC: There was some mild contention about this during LC.
An IESG note might be useful.