1 / 4

IETF 82, Taipei November 18, 2011 Flemming Andreasen (fandreas@cisco)

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 (fandreas@cisco.com). Major Change in -12.

zocha
Télécharger la présentation

IETF 82, Taipei November 18, 2011 Flemming Andreasen (fandreas@cisco)

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. SDP Media Capabilities Negotiationdraft-ietf-mmusic-sdp-media-capabilities-12R. Gilman, R. Even, F. Andreasen IETF 82, Taipei November 18, 2011 Flemming Andreasen (fandreas@cisco.com)

  2. 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

  3. 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

  4. Next Steps • Need to update • Offer/Answer Section • Security Considerations • Should be ready for WGLC subsequenlty (hopefully after next IETF) • Reviews, comments, feedback solicited

More Related