Re: [MMUSIC] FW: New Version Notification for draft-even-mmusic-application-token-00.txt

I looked this over, and it seems to solve many of the issues at hand.
There are no doubt some nits to iron out, but we should get agreement 
over the concepts before worrying too much about the details.

A couple of things I wanted to comment on:

You give examples of form:
       a=ssrc:11111 AppID:1
But you don't say too much about the meaning of this. The reason I ask 
is that you say elsewhere that the appid can move from one ssrc to 
another. My question is: If this form is used, can that appid later be 
bound to a different ssrc via the header extension? Also, is the 
following legal?
       a=ssrc:11111,22222 AppID:1

My other issue is with:
    In the CLUE WG case the mapping is from an RTP stream to a CLUE media
    capture specified in the CLUE framework [I-D.ietf-clue-framework].
This should be to a CLUE capture-encoding.

	Thanks,
	Paul

On 6/28/13 11:54 AM, Roni Even wrote:
> Hi,
> We have submitted this document that  defines a mechanism to provide the mapping between the
>     SSRCs of RTP streams and the application semantics by defining  extensions to RTP and RTCP messages.
>
> It defines a new SDP attribute, RTCP SDES message and RTP header extension for this puropose. The document explains how it can be used with the different multiplexing proposal (Plan A, Plan B and no plan).
>
> It can be used also in CLUE to map SSRCs to Clue media capture.
>
> Please review and send comments
> Thanks
> Roni Even
>
> ________________________________________
> From: internet-drafts@ietf.org [internet-drafts@ietf.org]
> Sent: Friday, June 28, 2013 6:27 PM
> To: Jonathan Lennox; Qin Wu; Roni Even
> Subject: New Version Notification for   draft-even-mmusic-application-token-00.txt
>
> A new version of I-D, draft-even-mmusic-application-token-00.txt
> has been successfully submitted by Roni Even and posted to the
> IETF repository.
>
> Filename:        draft-even-mmusic-application-token
> Revision:        00
> Title:           The Session Description Protocol (SDP) Application Token Attribute
> Creation date:   2013-06-28
> Group:           Individual Submission
> Number of pages: 11
> URL:             http://www.ietf.org/internet-drafts/draft-even-mmusic-application-token-00.txt
> Status:          http://datatracker.ietf.org/doc/draft-even-mmusic-application-token
> Htmlized:        http://tools.ietf.org/html/draft-even-mmusic-application-token-00
>
>
> Abstract:
>     The RTP fixed header includes the payload type number and the SSRC
>     values of the RTP stream.  RTP defines how you de-multiplex streams
>     within an RTP session, but in some use cases applications need
>     further identifiers in order to identify the application semantics
>     associated with particular streams within the session.
>
>     This document defines a mechanism to provide the mapping between the
>     SSRCs of RTP streams and the application semantics by defining
>     extensions to RTP and RTCP messages.
>
>
>
>
> The IETF Secretariat
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
>