Re: [MMUSIC] Wisdom sought: Prioritization of codecs

Flemming Andreasen <fandreas@cisco.com> Thu, 15 November 2012 16:12 UTC

Return-Path: <fandreas@cisco.com>
X-Original-To: mmusic@ietfa.amsl.com
Delivered-To: mmusic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB88521F896F for <mmusic@ietfa.amsl.com>; Thu, 15 Nov 2012 08:12:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.298
X-Spam-Level:
X-Spam-Status: No, score=-10.298 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_15=0.6, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zqtjVPVYCLNw for <mmusic@ietfa.amsl.com>; Thu, 15 Nov 2012 08:12:58 -0800 (PST)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com [173.37.86.77]) by ietfa.amsl.com (Postfix) with ESMTP id B7B6A21F8945 for <mmusic@ietf.org>; Thu, 15 Nov 2012 08:12:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=9632; q=dns/txt; s=iport; t=1352995978; x=1354205578; h=message-id:date:from:mime-version:to:cc:subject: references:in-reply-to; bh=fVin0hvjWZtKE6vk09L2FBBRdMH/oP7zzQUNcOJk8XU=; b=VXYAcj1qoi41AoVBYxpoJ1myBYPbE7cuA+WG3bz2TmQsa7rZD+eIBQet HtLSeTfyHU/TejAp4rvDwYhm2g7O8XH4Ubai8J/U5NJkfw4Gcwcwl+Lg7 ObSJO4+QL6ZXA7vBAV7lvMKRYUUPscUnFB29emAn9w59Cym1aa4wQiAn0 A=;
X-IronPort-AV: E=McAfee;i="5400,1158,6896"; a="142813181"
Received: from rcdn-core2-1.cisco.com ([173.37.113.188]) by rcdn-iport-6.cisco.com with ESMTP; 15 Nov 2012 16:12:58 +0000
Received: from rtp-fandreas-8713.cisco.com (rtp-fandreas-8713.cisco.com [10.117.7.84]) by rcdn-core2-1.cisco.com (8.14.5/8.14.5) with ESMTP id qAFGCvRp010628; Thu, 15 Nov 2012 16:12:57 GMT
Message-ID: <50A51489.9060506@cisco.com>
Date: Thu, 15 Nov 2012 11:12:57 -0500
From: Flemming Andreasen <fandreas@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: Harald Alvestrand <harald@alvestrand.no>
References: <50A4AC20.5030306@alvestrand.no> <50A4AE7F.4040403@alvestrand.no>
In-Reply-To: <50A4AE7F.4040403@alvestrand.no>
Content-Type: multipart/alternative; boundary="------------060506010702050700040409"
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] Wisdom sought: Prioritization of codecs
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 16:12:59 -0000

On 11/15/12 3:57 AM, Harald Alvestrand wrote:
> Found some answers in RFC 3264.
>
That's the right place to look assuming this is all for use in an 
Offer/Answer context.


> On 11/15/2012 09:47 AM, Harald Alvestrand wrote:
>> I've been searching RFC 4566 (SDP) for this info, but came up blank....
>>
>> in an M-line, we typically have
>>
>> m=video blabla 111 112 113
>> a=rtpmap:111 ....
>> a=rtpmap:112 ...
>> a=rtpmap:113 ....
>>
>> Section 5.14 says this:
>>
>>        If the <proto> sub-field is "RTP/AVP" or "RTP/SAVP" the <fmt>
>>        sub-fields contain RTP payload type numbers.  When a list of
>>        payload type numbers is given, this implies that all of these
>>        payload formats MAY be used in the session, but the first of these
>>        formats SHOULD be used as the default format for the session.
>>
>> Now, the questions...
>>
>> 1) In offer/answer, does this sequence in an offer mean that the 
>> offerer prefers that the answerer use codec 111, if supported?
>
> 3264 5.1:
>
>     In all cases, the formats in the "m=" line MUST be listed in order of
>     preference, with the first format listed being preferred.  In this
>     case, preferred means that the recipient of the offer SHOULD use the
>     format with the highest preference that is acceptable to it.
>
>>
>> 2) in offer/answer, does this sequence in an answer mean that the 
>> answerer prefers that the offerer use codec 111?
> 3264 6.1:
>
>    The
>     media formats in the "m=" line MUST be listed in order of preference,
>     with the first format listed being preferred.  In this case,
>     preferred means that the offerer SHOULD use the format with the
>     highest preference from the answer.
>
>
>>
>> 3) is there any preference expressed between codec 112 and codec 113?
> Clear from 3264. If we ever update 4566, might want to harmonize those.
4566bis is work-in-progress - do you see a disconnect between 4566 and 
3264 (or are you just looking to repeat the information in 4566) ?

>>
>> 4) Should the sequence of a=rtpmap: lines be completely ignored, or 
>> does it matter?
>
> I hope the answer is "completely ignored", have found no evidence to 
> the contrary.
>
It should not matter, but I don't think we have any text explicitly 
stating that anywhere.

-- Flemming


>>
>> I'm trying to fix a bug, and want to make sure I fix it according to 
>> spec.
>>
>>                Harald
>>
>>
>>
>>
>>
>> _______________________________________________
>> mmusic mailing list
>> mmusic@ietf.org
>> https://www.ietf.org/mailman/listinfo/mmusic
>
>
>
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic