1 / 7

RTSP - Core

RTSP - Core. Magnus Westerlund / Ericsson Rob Lanphier / Real Networks Aravind Narasimhan / Sun Henning Schulzrinne / Columbia University Anup Rao / Cisco. Changes 1/3. Clarified that a PLAY request without Range header when pause point is at end of media results in 457 (Invalid Range).

sovann
Download Presentation

RTSP - Core

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. RTSP - Core Magnus Westerlund / Ericsson Rob Lanphier / Real Networks Aravind Narasimhan / Sun Henning Schulzrinne / Columbia University Anup Rao / Cisco

  2. Changes 1/3 • Clarified that a PLAY request without Range header when pause point is at end of media results in 457 (Invalid Range). • Pause while in Ready-state is allowed. Server gives a 200 OK answer with current pause point. • Resolved how Scale=-1 works together with range. Standard interpretation of Range header values (closed to open ended) although will be larger to smaller values. Exception to open ended for 0.

  3. Changes 2/3 • Resolved to not fix RTP-Info support for multiple SSRCs due to backwards compatible reasons and unclear need. Would need a new RTP-Info header to fix it. • Clarified how RTP-timestamp behaves in regards to PAUSE and resumed PLAY (continuous timestamp space). A server shall include the Range and RTP-Info header in any PLAY response.

  4. Changes 3/3 • Will write up ABNF and clear rules regarding SDP “a=range”. A single value only in SDP, for backwards compatibility. • SET_PARAMETER without body to be clarified as being allowed. Can include headers, if required to understand, use Require header. • Clarified that a failed re-SETUP must not change the previous state. The logical resolution, was however not explained.

  5. Status • Most known open issues are resolved. • Needs a updated version of the spec that contains all resolutions. • When that happens we can go to Phase 2: • Fix all examples. • Check consistency of spec. • Review readability. • Resolve any found issues. • Will not meet October milestone.

  6. Open Issues • Should REDIRECT automatically close session? • How to handle implicit redirection through session description protocol. Majority favors allowing it per default. • How to detect the updated spec? • Version number change 1.1 or 2.0 • Only use Require header and tags when necessary. • Request to Response timeout. The time a request takes until any response is received is not bound. Look at SIP solution?

  7. Way forward • Will continue with telecons every two weeks as long as we have something to discuss or follow up. • Get all resolutions written up in next version. Hopefully more progress with help of Aravind. • Support with resolving text for bugs are appreciated. • Get on specification text review.

More Related