Real-Time Streaming Protocol

1. Real-Time Streaming Protocol draft-ietf-mmusic-rfc2326bis-05 Magnus Westerlund / Ericsson Aravind Narasimhan / Sun Robert Lanphier / Real Networks Henning Schulzrinne / Columbia University Anup Rao / Cisco

2. Changes to Specification • Removed Ready-NM state • Edited in that “Proxy-Require” only apply for proxies. • IANA Registration for feature tags needs to specify which domains they apply to: server, proxy, or both. • Clarified what to do when PLAY request without “Range” header is received when media is at end. • Rewrote section 9 regarding connection reliability. • Clarified that one needs to use RTCP to synchronize more than one SSRC if used in RTSP media streams.

3. Changes to Specification • The following methods has changes in the text: • SETUP • PLAY • PAUSE • TEARDOWN • REDIRECT • Written some text regarding use of SETUP to change transport parameters. • Streamlined the Accept-Ranges header by removing Live signaling.

4. Changes to Specification • Session header clarified regarding where it can be used. • Removed timed activation of methods, for all except REDIRECT. • Clarified the required usage of RTP-Info depending on the usage of RTP for media delivery. • Removed the usage of SETUP and TEARDOWN in PLAY state to change the number of streams in the session. • Removed the usage of TEARDOWN * • Edited in that PAUSE is allowed in READY state.

5. Changes to Specification • Clarified that a successful untimed session targeted REDIRECT results in session termination upon 200 OK. • Made several clarifications regarding SDP: • Added text that “a=range” with open range means live media that is not seekable if not otherwise indicated. • Rewrote large parts of the text to be clearer. • Clarified that SDP may be distributed with other methods than DESCRIBE, like email and HTTP. • Clarified the URI resolution rules and updated the example to agree with these rules.

6. Changes to Specification • Clarified the usage of RTCP and when BYE is reasonable to use. • Clarified that it is allowed to setup a session with aggregated control URI also using several non-aggregated sessions. • Tried to clarify the usage of Aggregated control when not signaled as supported in session description.

7. Agreed on Changes • Implicit Redirect, by using a new 3xx code the SDP can be returned for supporting terminals. Usage of feature tag to ensure backwards compatibilities. Details needs to be written up. • The address class in SDP “c=“ needs to be checked. • If several address classes is desired to be offered by the server the usage of RFC 3388 and draft-camarillo-mmusic-alt-02.txt. • Caching of methods is unspecified. • Aggregate control URI deriving will be unspecified. • Clarify the usage of SDP a=range for TiVo type of devices.

8. Agreed on Changes • The Server MAY close the TCP connection after receiving the 2xx message for a REDIRECT request. • To write something about Request to Response time limitations. Keep the specification simple. Details to be worked out. • ABNF Syntax to be collected in a single chapter. • Changing of Transport Parameters using SETUP: • What header is necessary for synchronization? Range and RTP-Info. • Is Range allowed in the SETUP request? Does not seem to be needed.

9. Open Issues • Changing of Transport Parameters using SETUP: • What parameters are allowed to be changed? • Should the Location header work as base URI for requests with REDIRECT without SESSION header? • Request – Response time is not limited. Details need to be clarified. See list discussion.

10. Future • Very few open issues. • A lot of editorial stuff remains. • Make an effort to edit in all known bugs before the end of the year. • Make review and refining in January to March. • Target WG last call by March. • Telephone conferences will continue until everything is resolved. Next scheduled for 3rd of December.