1 / 6

Session Description Protocol draft-ietf-mmusic-sdp-new-03.txt

Session Description Protocol draft-ietf-mmusic-sdp-new-03.txt. Colin Perkins USC Information Sciences Institute. Status. Update to SDP “classic” to fix bugs, prior to advancing to draft standard RFC Trying to avoid adding new features See SDPng for that... Two revisions since last meeting:

xander
Download Presentation

Session Description Protocol draft-ietf-mmusic-sdp-new-03.txt

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. Session Description Protocoldraft-ietf-mmusic-sdp-new-03.txt Colin Perkins USC Information Sciences Institute

  2. Status • Update to SDP “classic” to fix bugs, prior to advancing to draft standard RFC • Trying to avoid adding new features • See SDPng for that... • Two revisions since last meeting: • 02 draft at end of April • 03 draft now • More to come…?

  3. Changes in -02 • Section 3.1 replaced with a reference to RFC 2119 • Use of MUST, SHOULD, etc • Use of “application/sdp” MIME type: SHOULD  MUST • Section 4 “examples of use” now mentions SIP and RTSP • Section 5.3 “private sessions” now mentions SIP and is less SAP centric • Section 6 “RTP specification” • comments about bandwidth limits rewritten to be less SAP specific • now uses MUST, SHOULD, etc

  4. Changes in -02 • The section on concatenation of session descriptions (not allowed in SAP, allowed in other cases) has been removed. • Assume transports of SDP specify this? • The section on c= talked about how “typically the address is a class D multicast address”. • Made less Mbone specific, to reflect common use of SDP. • The section on b= no longer makes a normative reference to the Mbone FAQ for bandwidth limits at various TTLs • The section on m= defines relation with MIME types • References have been updated

  5. Changes in -03 • e= and p= were mandatory, and are now optional • a=maxptime added • In the section on “t=” • Remove references to “conference”, to make it less SAP oriented • Note about wrap-around of NTP timestamps (not an issue, since SDP is a text format) • Merge draft-olson-sdp-ipv6-00.txt • please check the BNF to make sure I did this correctly...

  6. Future work? • Any other changes/additions? • Please read and comment!

More Related