1 / 8

RTP Header Extension For SDES ITEMs

RTP Header Extension For SDES ITEMs. draft-westerlund-avtext-sdes-hdr-ext-01 Bo Burman (Ericsson), Roni Even (Huawei), Magnus Westerlund (Ericsson), Mo Zanaty (Cisco). Overview. Proposal Motivations Technical Details Adoption. Proposal.

lynton
Télécharger la présentation

RTP Header Extension For SDES ITEMs

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. RTP Header Extension For SDES ITEMs draft-westerlund-avtext-sdes-hdr-ext-01 Bo Burman (Ericsson), Roni Even (Huawei), Magnus Westerlund (Ericsson), Mo Zanaty (Cisco)

  2. Overview • Proposal • Motivations • Technical Details • Adoption

  3. Proposal • An RTP header extension for Source Description (SDES) items • Has been brought up in various discussions • Lets do it! • Initial Proposal in draft-westerlund-avtext-sdes-hdr-ext-01 • Adopt it as WG item and work together on a solution?

  4. Motivation • A few different proposals suggest new SDES items that would benefit from a header extension: • APPID (draft-even-mmusic-application-token-01) • SRCNAME (draft-westerlund-avtext-rtcp-sdes-srcname-03) • RFC 6051 – RTP header extension for Rapid Synchronisation of RTP Flows provide equivalent to RTCP Sender Report, but not CNAME • To enable this to be used in context when also the CNAME information can’t provided earlier than the timing information. • Unclear of the evolution of MSID in SDP (draft-ietf-mmusic-msid-01), may also require in-band signaling?

  5. Motivation • RTP/RTCP Mechanism needed when signaling can’t provide the information: • Dynamic group memberships • Multicast/Broadcast • Signaling node may not have access to actually used SSRCs at time of signaling • Fate sharing in delivery between media and relation information • AVPF ACKs can inform sender when Header Ext is received • RTP Header Extensions are useful when RTCP delivery is not timely enough: • New SSRC in a session • New Endpoint joins multiparty session • RTCP may not be timely enough when: • RTP Packet streams are to be decoded directly on reception • They have relations that SDES items expresses, e.g. • CNAME gives synchronization context

  6. Technical Details 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ID | len | SDES Item text value ... | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ • Put the SDES item string in RTP header extension: • String can be up to 255 bytes, use 1 or 2-byte headers as appropriate for SDES items intended to use in RTP session • Header Extension ID maps to SDES Item type via URN • Len: Number of bytes in SDES Item String • Future Extensibility • New SDES Items registers a URN and can then use the header extension

  7. Technical Details • URN Proposal • RTP Header Extensions are registered in URN space: • urn:ietf:params:rtp-hdrext: • Proposes to allocate urn:ietf:params:rtp-hdrext:sdes to SDES items. • Resulting URNs: URN SDES Item Reference ================================================================== urn:ietf:params:rtp-hdrext:sdes:cname CNAME [RFC3550] urn:ietf:params:rtp-hdrext:sdes:name NAME [RFC3550] urn:ietf:params:rtp-hdrext:sdes:email EMAIL [RFC3550] urn:ietf:params:rtp-hdrext:sdes:phone PHONE [RFC3550] urn:ietf:params:rtp-hdrext:sdes:loc LOC [RFC3550] urn:ietf:params:rtp-hdrext:sdes:tool TOOL [RFC3550] urn:ietf:params:rtp-hdrext:sdes:note NOTE [RFC3550] urn:ietf:params:rtp-hdrext:sdes:priv PRIV [RFC3550] urn:ietf:params:rtp-hdrext:sdes:h323-caddr H323-CADDR [Vineet_Kumar] urn:ietf:params:rtp-hdrext:sdes:apsi APSI [RFC6776]

  8. Wg Adoption? • So is this a good idea? • WG Adoption?

More Related