Hi, Patrick,
On 8/9/2016 1:02 PM, Patrick Frejborg wrote:
> Whoa!
> Will indeed have a look on URL you posted, thanks!
>
> RTP is perhaps the wrong reference, I should have referred the
> different overlay tunnels as NVO3 "codecs", the payload inside the
> RTP, the audio/video profile identifier. Then these overlay tunnel
> protocols can evolve, as the DSPs evolved/evolving in the
> communication systems.
Sure, but then:
SIP == x-bone-api
i.e., it's the way the user indicates what to deploy
RTP = x-bone-ctl
i.e., the way the resources are discovered and components configured
You don't need a protocol to specifically deploy just tunnels; they're
just one part of the overall picture (which includes addressing,
routing, etc.).
...
> The difference between SIP messages and RTCP is that SIP messages
> between a SIP UA and a SIP proxy/registrar
Yes, as per above, SIP is closer to x-bone-api (I can't speak for the
others).
> do take a different path in
> the network what the RTP messages are using - the SIP messages are off
> the data path (the signalling path) and the RTCP messages are on the
> data path.
>
RTCP are not in the data path; they're between data endpoints. There's
no requirement that they traverse the same path as the codec'd data.
Joe
_______________________________________________
nvo3 mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/nvo3
