RE: [AVT] Offer/answer questions on RFC 4585

"Christer Holmberg" <christer.holmberg@ericsson.com> Tue, 02 October 2007 12:13 UTC

Return-path: <avt-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Icgct-0005Lk-RJ; Tue, 02 Oct 2007 08:13:23 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Icgcs-0005Lf-VU for avt@ietf.org; Tue, 02 Oct 2007 08:13:22 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Icgcs-0001OV-Em for avt@ietf.org; Tue, 02 Oct 2007 08:13:22 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 1BCB221121 for <avt@ietf.org>; Tue, 2 Oct 2007 14:13:20 +0200 (CEST)
X-AuditID: c1b4fb3e-af833bb0000007e1-ca-470235e032d4
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 046BE2102C for <avt@ietf.org>; Tue, 2 Oct 2007 14:13:20 +0200 (CEST)
Received: from esealmw113.eemea.ericsson.se ([153.88.200.4]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Tue, 2 Oct 2007 14:13:19 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [AVT] Offer/answer questions on RFC 4585
Date: Tue, 02 Oct 2007 14:13:19 +0200
Message-ID: <CA9998CD4A020D418654FCDEF4E707DF024A28E7@esealmw113.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RE: [AVT] Offer/answer questions on RFC 4585
Thread-Index: AcgE7Z5rzGaYvf0KStei+LHD/qwFkQ==
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: avt@ietf.org
X-OriginalArrivalTime: 02 Oct 2007 12:13:19.0859 (UTC) FILETIME=[9ED52C30:01C804ED]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
Errors-To: avt-bounces@ietf.org

Hi Roni,

>>I have a couple of questions on RFC 4585, regarding the usage with
offer/answer.
>>
>>My FIRST question is: are there any TECHNICAL reasons (I know it's
probably not allowed by RFC 3264) why a user receiving an AVPF offer,
but doesn't 
>>support it, can't reply with AVP answer (instead of rejecting the
stream)? My understanding is that if you offer AVPF you still have to be
able to do 
>>AVP, so...
>>(The receiver of course needs to understand the "AVPF" string in the
SDP)

>[RE:] I think that is this case the offer will include a=rtcp-fb with
rtcp-fb-vals. Since the receiver understands AVPF but do not support any
feedback 
>message it will remove all rtcp-fb-val in the answers.
>To me that looks like support of AVP so why do you want to change the
avpf to avp.

Ok, if it works that way.

So, if I have an MGCF/MGW I can do the following:

- The MGCF answers with AVPF, but without rtcp-fb-val

- The MGCF sends AVP down to the MGW (e.g using H.248)

Regards,

Christer



_______________________________________________
Audio/Video Transport Working Group
avt@ietf.org
https://www1.ietf.org/mailman/listinfo/avt