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

["Roni Even" <[e-mail]>]

Inline

> -----Original Message-----
> From: [e-mail] [mailto:[e-mail]] On
> Behalf Of Paul Kyzivat
> Sent: 29 June, 2013 6:59 PM
> To: [e-mail]
> Subject: 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
[Roni Even] The AppID can be mapped later using SDES or header extension to
a new SSRC and our view is that this is a replacement. An AppID can be
mapped to a single SSRC at a time.
We looked at having more than one SSRC mapped to a single AppID and decided
to leave it to discussion. It will require to distinguish between adding and
SSRC and replacing an SSRC when a new mapping is specified.
My view is that the unique mapping is clearer and I assume we can look at
using SDP grouping if want to associate two RTP media streams to an
application usage.

Roni

> 
> 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.
[Roni Even] OK, will fix it
> 
> 	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: [e-mail] [[e-mail]]
> > 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
> > [e-mail]
> > https://www.ietf.org/mailman/listinfo/mmusic
> >
> 
> _______________________________________________
> mmusic mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/mmusic