W3C home > Mailing lists > Public > public-webrtc@w3.org > February 2012

Re: [rtcweb] JSEP-02: SDP_PRANSWER and FEDEX use-case

From: Iñaki Baz Castillo <ibc@aliax.net>
Date: Mon, 20 Feb 2012 21:43:25 +0100
Message-ID: <CALiegf==frmu4VSpdV8OyN5RSHWvvER5+T3ZLOVDvSm67k39Hg@mail.gmail.com>
To: Roman Shpount <roman@telurix.com>
Cc: Christer Holmberg <christer.holmberg@ericsson.com>, "rtcweb@ietf.org" <rtcweb@ietf.org>, "public-webrtc@w3.org" <public-webrtc@w3.org>
2012/2/20 Roman Shpount <roman@telurix.com>:
> Actually codecs are a fairly bad example, since end point should be ready to
> receive media  encoded using any codec present in the offer. The fact that
> one of the codecs was not present in the answer does not mean that remote
> party is not planning to send media using this codec.

Exactly. At least SDP offer/answer mechanism allows asymmetric codecs
usage in the same media session, which means different codec in each
direction of the media stream.

-- 
Iñaki Baz Castillo
<ibc@aliax.net>
Received on Monday, 20 February 2012 20:44:14 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 15:19:27 UTC