RE: [MMUSIC] SDP media capabilities and nightmare SDP

"Ingemar Johansson S \(LU/EAB\)" <ingemar.s.johansson@ericsson.com> Thu, 22 March 2007 13:26 UTC

Return-path: <mmusic-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUNJg-0007IT-VC; Thu, 22 Mar 2007 09:26:56 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HUNJf-0007Hj-0U for mmusic@ietf.org; Thu, 22 Mar 2007 09:26:55 -0400
Received: from mailgw4.ericsson.se ([193.180.251.62]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HUNJX-00007X-8E for mmusic@ietf.org; Thu, 22 Mar 2007 09:26:52 -0400
Received: from mailgw4.ericsson.se (unknown [127.0.0.1]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 528A4200F1; Thu, 22 Mar 2007 14:26:34 +0100 (CET)
X-AuditID: c1b4fb3e-b1a1dbb0000061ca-7c-4602840a154d
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw4.ericsson.se (Symantec Mail Security) with ESMTP id 3A50E2006A; Thu, 22 Mar 2007 14:26:34 +0100 (CET)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Thu, 22 Mar 2007 14:26:34 +0100
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: [MMUSIC] SDP media capabilities and nightmare SDP
Date: Thu, 22 Mar 2007 14:26:32 +0100
Message-ID: <026F8EEDAD2C4342A993203088C1FC0504A56A17@esealmw109.eemea.ericsson.se>
In-Reply-To: <46027DBE.8080707@cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MMUSIC] SDP media capabilities and nightmare SDP
Thread-Index: AcdsgfP5DH8Qbi0ZSn23cFgzwWsg8gAAyXZA
From: "Ingemar Johansson S (LU/EAB)" <ingemar.s.johansson@ericsson.com>
To: Flemming Andreasen <fandreas@cisco.com>, "Robert R. Gilman" <rrg@avaya.com>
X-OriginalArrivalTime: 22 Mar 2007 13:26:34.0120 (UTC) FILETIME=[B5E0B080:01C76C85]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
Cc: "Even, Roni" <roni.even@polycom.co.il>, mmusic@ietf.org
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
Errors-To: mmusic-bounces@ietf.org

Hi

I probably stand corrected regarding the fmtp line. 
Regarding the usecase I listed "nightmare SDP" this is the result of
interworking with legacy circuit switched AMR which has a whole bunch of
mode sets depending on the underlying access network (GSM, UMTS...) but
I have heard that one can easily end up in the same situation with video
codecs that could be configured in many different ways depending on
terminal properties.

Regards

> -----Original Message-----
> From: Flemming Andreasen [mailto:fandreas@cisco.com] 
> Sent: den 22 mars 2007 14:00
> To: Robert R. Gilman
> Cc: Ingemar Johansson S (LU/EAB); Even, Roni; mmusic@ietf.org
> Subject: Re: [MMUSIC] SDP media capabilities and nightmare SDP
> 
> 
> 
> Robert R. Gilman wrote:
> > Ingemar-
> > I checked draft-ietf-avt-rtp-amr-bis-06.txt, and it seems to say the
> > fmtp: line is the place for mode-set - but it doesn't 
> matter - we play 
> > the same list-the-codecs game with the cenc: attributes.
> >
> > Roni, Flemming-
> > Shall we add the range option to the media-capabilities draft?
> Quite possible, but more importantly at this point, we should 
> understand the underlying requirements better first.
> 
> -- Flemming
> >
> > -Bob
> > ----------------------------------------------------
> > Bob Gilman       rrg@avaya.com      +1 303 538 3868
> >
> > Ingemar Johansson S (LU/EAB) wrote:
> >> Hi
> >>
> >> I believe that slept over a few lessons, 1000 thanks for 
> the help!. 
> >> This squeezed down the whole thing quite a bit. Only thing that I 
> >> find odd is that I regard the mode-set as an encoding 
> parameter and 
> >> not a format parameter but I am not 100% sure here.
> >>
> >> If the ranging option is possible I believe that it would help up 
> >> things even more, especially it would be less tedious to read.
> >>
> >> Regards
> >> Ingemar
> >>
> >>> -----Original Message-----
> >>> From: Robert R. Gilman [mailto:rrg@avaya.com] Sent: den 
> 21 mars 2007
> >>> 21:32
> >>> To: Ingemar Johansson S (LU/EAB)
> >>> Cc: mmusic@ietf.org
> >>> Subject: Re: [MMUSIC] SDP media capabilities and nightmare SDP
> >>>
> >>> Ingemar-
> >>> Nightmare indeed!  I think you wanted to define 26 AMR 
> codecs and 6 
> >>> AMR-WB codecs (I'm not sure.)  Try this (I've folded the 
> cmed: line 
> >>> and the cenc: line):
> >>>
> >>> a=creq:v1
> >>> m=audio 49152 RTP/AVP 100
> >>> a=rtpmap:100 AMR/8000/1
> >>> a=fmtp:100 mode-set=0; mode-change-capability=2; max-red=220 
> >>> a=maxptime:240 a=ptime:20
> >>> a=cmed:2 audio AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR
> >>>     AMR ARM AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR AMR
> >>>     AMR-WB AMR-WB AMR-WB AMR-WB AMR-WB AMR-WB AMR-WB 
> >>> a=cenc:2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,
> >>> 23,24,25,26
> >>>     8000/1
> >>> a=cenc:27,28,29,30,31 16000/2
> >>> a=cfmt:14 mode-set=0;
> >>> a=cfmt:2,15 mode-set=0,2,4,7;
> >>> a=cfmt:3,16 mode-set=2;
> >>> a=cfmt:4,17 mode-set=3;
> >>> a=cfmt:5,18 mode-set=4;
> >>> a=cfmt:6,19 mode-set=5;
> >>> a=cfmt:7,20 mode-set=6;
> >>> a=cfmt:8,21 mode-set=7;
> >>> a=cfmt:9,22 mode-set=0,2;
> >>> a=cfmt:10,23 mode-set=0,2,3;
> >>> a=cfmt:11,24 mode-set=0,2,3,4;
> >>> a=cfmt:12,25 mode-set==0,2,3,6;
> >>> a=cfmt:13,26 mode-set=0,2,5,7;
> >>> a=cfmt:27,30 mode-set=0,1,2;
> >>> a=cfmt:28,31 mode-set=0,1,2,5;
> >>> a=cfmt:29,32 mode-set=0,1,2,9;
> >>> a=cfmt:2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,
> >>> 23,24,25,26,
> >>>     27,28,29,30,31,32 mode-change-capability=2; max-red=220;
> >>> a=cfmt:14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31,3
> >>> 2 octet-align=1
> >>> pcfg:1
> >>> 
> m=2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24|25|26|
> >>>     27|28|29|30|31|32
> >>> pt=2:100,3:100,4:100,5:100,6:100,7:100,8:100,9:100,10:100,
> >>>     
> >>> 
> 11:100,12:100,13:100,14:100,15:100,16:100,17:100,18:100,19:100,20:10
> >>> 0,
> >>>     
> >>> 
> 21:100,22:100,23:100,24:100,25:100,26:100,27:100,28:100,29:100,30:100,
> >>>     31:100,32:100
> >>>
> >>> We've assumed the default (media line) transport.  
> Looking at this 
> >>> example, I wonder if we don't want to implement some 
> ranging on the 
> >>> media capability numbers - something like:
> >>>
> >>> a=cenc:2-26 8000/1
> >>> a=cenc:27-32 16000/1
> >>> a=cfmt:2-32 mode-change-capability=2; max-red=220;
> >>>
> >>> and
> >>>
> >>> pcfg:1
> >>> 
> m=2|3|4|5|6|7|8|9|10|11|12|13|14|15|16|17|18|19|20|21|22|23|24|25|26|
> >>>     27|28|29|30|31|32 pt=100:2-32
> >>>
> >>> Of course, the long form of the pt parameter would be used if the 
> >>> offeror wanted to distinguish the answerer's choice via 
> the payload 
> >>> type received prior to receiving the answer.  Do you have a 
> >>> suggestion for how to say "pick one codec from this range" that's 
> >>> better than the 2|3|4|... ad nauseum?
> >>> Does this more-or-less fit with what you wanted to express?
> >>> -Bob
> >>> ----------------------------------------------------
> >>> Bob Gilman       rrg@avaya.com      +1 303 538 3868
> >>>
> >>
> >>
> >
> 

_______________________________________________
mmusic mailing list
mmusic@ietf.org
https://www1.ietf.org/mailman/listinfo/mmusic