RTP Payload Format for 3rd Generation Partnership Project (3GPP) Timed Text
draft-ietf-avt-rtp-3gpp-timed-text-15
Yes
(Allison Mankin)
No Objection
(Alex Zinin)
(Bill Fenner)
(Brian Carpenter)
(David Kessens)
(Margaret Cullen)
(Mark Townsley)
(Russ Housley)
(Sam Hartman)
(Scott Hollenbeck)
(Ted Hardie)
Note: This ballot was opened for revision 15 and is now closed.
Allison Mankin Former IESG member
Yes
Yes
()
Unknown
Alex Zinin Former IESG member
No Objection
No Objection
()
Unknown
Bert Wijnen Former IESG member
No Objection
No Objection
(2005-08-31)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown
Brian Carpenter Former IESG member
No Objection
No Objection
()
Unknown
David Kessens Former IESG member
No Objection
No Objection
()
Unknown
Jon Peterson Former IESG member
No Objection
No Objection
(2005-09-01)
Unknown
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 IESG member
No Objection
No Objection
()
Unknown
Mark Townsley Former IESG member
No Objection
No Objection
()
Unknown
Russ Housley Former IESG member
No Objection
No Objection
()
Unknown
Sam Hartman Former IESG member
No Objection
No Objection
()
Unknown
Scott Hollenbeck Former IESG member
No Objection
No Objection
()
Unknown
Ted Hardie Former IESG member
No Objection
No Objection
()
Unknown