RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text
RFC 4396

Note: This ballot was opened for revision 15 and is now closed.

(Allison Mankin) Yes

(Brian Carpenter) No Objection

(Margaret Cullen) No Objection

(Bill Fenner) No Objection

(Ted Hardie) No Objection

(Sam Hartman) No Objection

(Scott Hollenbeck) No Objection

(Russ Housley) No Objection

(David Kessens) No Objection

(Jon Peterson) No Objection

Comment (2005-09-01)
No email
send info
Given that timed text may or may not be synchronized with media such as video or audio, as stated in the Introduction, it seems a little odd that the recommended SDP behavior (section 9.1) suggests that the video media type is used in the SDP m= line.

(Mark Townsley) No Objection

(Bert Wijnen) No Objection

Comment (2005-08-31)
No email
send info
I see informative reference:
    [18] F. Yergeau, "UTF-8, a transformation format of Unicode and ISO
     10646", RFC 2044, October 1996.
Is that intentionally to an RFC that has been obsolted twice, first by
RFC2279 and then RFC3629 ??

I further wonder if the references to UTF8 and UTF16 should not be
normative ?? You will have to understand them if you want to implement
this spec, no?

(Alex Zinin) No Objection