[rtcweb] draft on media multiplexing submitted to AVTCORE

["Ejzak, Richard P (Richard)" <[e-mail]>]

Please see the mail attached below that I just sent to avtcore announcing a personal ID I just submitted on the topic of media multiplexing.  I am sending this notice to rtcweb since this is the group that triggered recent work on RTP multiplexing.

I also request the rtcweb chairs consider giving me some time to present this work at next week's interim meeting if there is time on the agenda.  It might be useful to discuss the ideas in the ID before avtcore meets in Vancouver.

Richard


-----Original Message-----
From: Ejzak, Richard P (Richard)
Sent: Sunday, June 03, 2012 6:08 PM
To: '[e-mail]'
Subject: [AVTCORE] multi session draft-ejzak-avtcore-rtp-subsessions-00.txt



http://www.ietf.org/id/draft-ejzak-avtcore-rtp-subsessions-00.txt



In response to the chairs' request for additional input on the multi session issue, I have submitted this draft for your consideration.  There are superficial similarities with an expired draft from last year in http://tools.ietf.org/id/draft-rosenberg-rtcweb-rtpmux-00.txt, but my draft has a different take on the use of SSRC as the basis for multi session multiplexing that I think is superior and worthy of consideration as a potential replacement for BUNDLE and/or SHIM.  Please comment.



Richard



-----Original Message-----

From: [e-mail] [mailto:[e-mail]]

Sent: Sunday, June 03, 2012 5:16 PM

To: Ejzak, Richard P (Richard)

Subject: New Version Notification for draft-ejzak-avtcore-rtp-subsessions-00.txt



A new version of I-D, draft-ejzak-avtcore-rtp-subsessions-00.txt has been successfully submitted by Richard Ejzak and posted to the IETF repository.



Filename:   draft-ejzak-avtcore-rtp-subsessions

Revision:   00

Title:            Media multiplexing with Real-time Transport Protocol (RTP) subsessions

Creation date:    2012-06-04

WG ID:            Individual Submission

Number of pages: 9



Abstract:

   This document describes a means of multiplexing RTP streams having

   different media types within a single transport connection and how to

   represent this multiplexing option in SDP.  This mechanism is an

   alternative to the BUNDLE and SHIM proposals currently under active

   consideration in AVTCORE.  Instead of adding an extra multiplexing

   header as in SHIM to allow multiple RTP sessions within a single

   transport connection, or using the payload type field to separate

   different media streams within a single RTP session, this document

   describes how to partition the existing SSRC space to create RTP

   subsessions from a single RTP session.  A filter can be used to

   identify each RTP subsession for different QoS handling as necessary.

   RTP subsessions can be treated like RTP sessions with a few

   restrictions.  In particular, SSRC mapping may be needed when

   forwarding RTP streams into an RTP subsession to avoid SSRC

   conflicts, but there are few use cases in which this limitation is a

   concern and RTP subsessions can be disabled if necessary.









The IETF Secretariat