[Jingle] 1.1 XEPs (166, 167, 177)

[Robert McQueen]

Justin Uberti wrote:
> I agree with Rob's general notion that we should not duplicate stuff in
> our signaling, but RTCP does not automatically mean AVPF. AVPF defines
> special rules for how RTCP can be transmitted, but it is still possible
> to send RTCP using the old (AVP) rules.
> 
> Therefore, I think we need some way in the signaling to indicate the use
> of AVPF.

+1 - this is what I was getting at. Signal the stuff we're actually
missing, not throw in misc SDP stuff which is redundant to what we
actually have. We just want a little <avpf/> handshake in the same way
we do for encryption, I guess? One in the offer to say we want to use
it, one in the answer to say we will?

Cheers,
Rob

> On Mon, Nov 30, 2009 at 8:02 PM, Peter Saint-Andre <stpeter at stpeter.im
> <mailto:stpeter at stpeter.im>> wrote:
> 
>     On 11/30/09 4:51 PM, Justin Karneges wrote:
>     > On Monday 30 November 2009 09:11:27 Peter Saint-Andre wrote:
>     >> On 11/25/09 11:42 AM, Justin Karneges wrote:
>     >>> I think the reason the RTP profile is not passed in the XML is
>     because
>     >>> the profile is defined rigidly in the Jingle RTP spec (or at
>     least, it is
>     >>> supposed to be).
>     >> By that do you mean XEP-0167 allows only "RTP/AVP" and any other
>     profile
>     >> would need to be defined in a separate spec?
>     >
>     > Right.
>     >
>     >>> Probably the XEP should say that component 1 is "AVP" and
>     component 2
>     >>> is "AVPF".
>     >> XEP-0167 currently says:
>     >>
>     >>    The component numbered "1" MUST be associated with RTP and the
>     >>    component numbered "2" MUST be associated with RTCP.
>     >>
>     >> Are you suggesting that we clarify the text to explicitly state that
>     >> AVPF is a (or the only) component that's associated with RTCP, with a
>     >> reference to RFC 4585?
>     >
>     > I'm not 100% sure, but I believe each component is assigned a
>     profile.  So
>     > component 1 would always be "RTP/AVP" and component 2 would always
>     > be "RTP/AVPF" (which I think is more or less synonymous with RTCP).
> 
>     In the context of RTP/AVP, yes. In the context of RTP/SAVP (which maps
>     to Jingle + <encryption/> element) the RTCP-associated component would
>     be RTP/SAVPF. And perhaps it's enough to say just that.
> 
>     Peter
> 
>     --
>     Peter Saint-Andre
>     https://stpeter.im/
> 
> 
> 


-- 
Robert McQueen                                 +44 7876 562 564
Director, Collabora Ltd.             http://www.collabora.co.uk