Re: [MMUSIC] M-line philosophy (Re: Wisdom sought: Prioritization of codecs)

Adam Roach <adam@nostrum.com> Mon, 19 November 2012 16:25 UTC

Return-Path: <adam@nostrum.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 E29D321F8473 for <mmusic@ietfa.amsl.com>; Mon, 19 Nov 2012 08:25:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.363
X-Spam-Level:
X-Spam-Status: No, score=-102.363 tagged_above=-999 required=5 tests=[AWL=0.237, BAYES_00=-2.599, SPF_PASS=-0.001, USER_IN_WHITELIST=-100]
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 Ljt1lXfhFLCu for <mmusic@ietfa.amsl.com>; Mon, 19 Nov 2012 08:25:18 -0800 (PST)
Received: from shaman.nostrum.com (nostrum-pt.tunnel.tserv2.fmt.ipv6.he.net [IPv6:2001:470:1f03:267::2]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF0D21F8456 for <mmusic@ietf.org>; Mon, 19 Nov 2012 08:25:17 -0800 (PST)
Received: from Orochi.local (99-152-144-32.lightspeed.dllstx.sbcglobal.net [99.152.144.32]) (authenticated bits=0) by shaman.nostrum.com (8.14.3/8.14.3) with ESMTP id qAJGOtdR050552 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Mon, 19 Nov 2012 10:24:59 -0600 (CST) (envelope-from adam@nostrum.com)
Message-ID: <50AA5D55.6080006@nostrum.com>
Date: Mon, 19 Nov 2012 10:24:53 -0600
From: Adam Roach <adam@nostrum.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; 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> <50A51F04.5090502@alum.mit.edu> <50A54895.7030006@nostrum.com> <50A9BFD4.3000601@alvestrand.no> <50AA527C.6060200@nostrum.com> <50AA588B.9090805@alvestrand.no>
In-Reply-To: <50AA588B.9090805@alvestrand.no>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Received-SPF: pass (nostrum.com: 99.152.144.32 is authenticated by a trusted mechanism)
Cc: mmusic@ietf.org
Subject: Re: [MMUSIC] M-line philosophy (Re: 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: Mon, 19 Nov 2012 16:25:19 -0000

On 11/19/12 10:04, Harald Alvestrand wrote:
> On 11/19/2012 04:38 PM, Adam Roach wrote:
>>
>>
>> There are, at the moment, 176 attributes in the IANA registry that 
>> are applicable to m= sections:
>> ...
>> Some of these are applicable to the RTP session; others only make 
>> sense as applied to a single media stream.
> And some make absolutely no sense at all in the RTCWEB context.

Perhaps not for RTCWEB, but I'm fairly certain that we'd like to see the 
same solutions applies to CLUE as RTCWEB. I concede that some of these 
are applicable only to technologies that are dead or dying; however...

> I have at one point in my life dealt with T-series fax

...T.38 fax isn't one of them. Sadly.

It sure would be nice to discount all of the existing mechanisms, but I 
suspect that they're not as wholly worthless are you're implying. 
Perhaps when I have a bit more time, I'll sit down and do a 
mechanism-by-mechanism evaluation of applicability of each to RTCWEB and 
CLUE. Until then, I expect it's relatively safe to assume that people 
haven't been putting values into that registry by performing utterly 
meaningless work; and, further, that only a fraction of it has been 
overtaken by technological progress.

/a