RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text
draft-ietf-avt-rtp-3gpp-timed-text-15

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

(Allison Mankin; former steering group member) Yes

(Alex Zinin; former steering group member) No Objection

(Bert Wijnen; former steering group member) No Objection

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?

(Bill Fenner; former steering group member) No Objection

(Brian Carpenter; former steering group member) No Objection

(David Kessens; former steering group member) No Objection

(Jon Peterson; former steering group member) No Objection

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.

(Margaret Cullen; former steering group member) No Objection

(Mark Townsley; former steering group member) No Objection

(Russ Housley; former steering group member) No Objection

(Sam Hartman; former steering group member) No Objection

(Scott Hollenbeck; former steering group member) No Objection

(Ted Hardie; former steering group member) No Objection