IETF Logo Mail Archive

[AVT] Usage of use-level-src-parameter-sets as per draft-ietf-avt-rtp-rfc3984bis-12

Guylain Lavoie <glavoie@media5corp.com> Wed, 24 November 2010 19:09 UTC

Return-Path: <glavoie@media5corp.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DCF983A6A82 for <avt@core3.amsl.com>; Wed, 24 Nov 2010 11:09:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.395
X-Spam-Level:
X-Spam-Status: No, score=-1.395 tagged_above=-999 required=5 tests=[AWL=0.603, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_14=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GaxjwOeq5XJt for <avt@core3.amsl.com>; Wed, 24 Nov 2010 11:09:27 -0800 (PST)
Received: from MAIL1.mediatrix.com (mail1.mediatrix.com [207.134.65.15]) by core3.amsl.com (Postfix) with ESMTP id F2ED83A6A85 for <avt@ietf.org>; Wed, 24 Nov 2010 11:09:26 -0800 (PST)
Received: from exchange.media5corp.com ([207.134.65.90]) by MAIL1.mediatrix.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 24 Nov 2010 14:10:25 -0500
Received: from exchange.media5corp.com ([207.134.65.90]) by exchange.media5corp.com ([207.134.65.90]) with mapi; Wed, 24 Nov 2010 14:10:25 -0500
From: Guylain Lavoie <glavoie@media5corp.com>
To: "avt@ietf.org" <avt@ietf.org>
Date: Wed, 24 Nov 2010 14:10:25 -0500
Thread-Topic: Usage of use-level-src-parameter-sets as per draft-ietf-avt-rtp-rfc3984bis-12
Thread-Index: AcuMCz/DkeRdESyJQmaXFugO3E5/tQ==
Message-ID: <265ED5BA1B926340AF277A54E6A83414223B84886A@exchange.media5corp.com>
Accept-Language: en-US, fr-CA
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, fr-CA
Content-Type: multipart/alternative; boundary="_000_265ED5BA1B926340AF277A54E6A83414223B84886Aexchangemedia_"
MIME-Version: 1.0
X-OriginalArrivalTime: 24 Nov 2010 19:10:25.0423 (UTC) FILETIME=[3FDDF1F0:01CB8C0B]
Subject: [AVT] Usage of use-level-src-parameter-sets as per draft-ietf-avt-rtp-rfc3984bis-12
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Nov 2010 19:09:31 -0000

Hello,

We are integrating the support for H.264 in our application based on the RFC3984bis draft 12 and while reviewing the specification we discovered that it is not possible to indicate that we support the sprop-level-parameter-sets fmtp parameter without also supporting the transport of the fmtp over the SDP ssrc attribute (as per RFC5576). The problem we have is that we currently cannot implement the support for the SDP ssrc attribute because we cannot specified the SSRC associated with each parameter sets. How can we indicate support for a=fmtp with the sprop-level-parameter-sets parameter without indicating support for a=ssrc:x fmtp:sprop-level-parameter-sets=... ?

According to our current understanding, it would seem useful to separate the support capability for sprop-level-parameter-sets from the support for the SDP ssrc attribute. Is there any reason for this, please explain.

Best Regards,
Guylain

v2.23.0 | Report a Bug | By Email