SDP Media Capabilities Negotiation
Download
1 / 4

IETF 82, Taipei November 18, 2011 Flemming Andreasen ([email protected]) - PowerPoint PPT Presentation


  • 186 Views
  • Uploaded on

SDP Media Capabilities Negotiation draft-ietf-mmusic-sdp-media-capabilities-12 R. Gilman, R. Even, F. Andreasen. IETF 82, Taipei November 18, 2011 Flemming Andreasen ([email protected]). Major Change in -12.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about ' IETF 82, Taipei November 18, 2011 Flemming Andreasen ([email protected])' - zocha


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

SDP Media Capabilities Negotiationdraft-ietf-mmusic-sdp-media-capabilities-12R. Gilman, R. Even, F. Andreasen

IETF 82, Taipei

November 18, 2011

Flemming Andreasen ([email protected])


Major change in 12
Major Change in -12

  • Problem in -11a=mcap:<media-cap-num-list><encoding-name>/<clock-rate> [/<encoding-parms]

  • Definition assumes RTP-based media format, however need to support non-RTP based as well

  • Two options

    • Single attribute supporting both

    • Two different attributes; one for RTP-based and one for non-RTP-based


Media format capabilities
Media Format Capabilities

  • Went for two attributes in -12 for syntactic and semantic clarity:a=rmcap:<media-cap-num-list><encoding-name> /<clock-rate> [/<encoding-parms] a=omcap:<media-cap-num-list><encoding-name>

  • "rmcap" needs payload type mappings, "omcap"does not


Next steps
Next Steps

  • Need to update

    • Offer/Answer Section

    • Security Considerations

  • Should be ready for WGLC subsequenlty (hopefully after next IETF)

    • Reviews, comments, feedback solicited


ad