Re: [rtcweb] MTI Video Codec: a novel proposal

cowwoc <cowwoc@bbs.darktech.org> Wed, 12 November 2014 01:36 UTC

Return-Path: <cowwoc@bbs.darktech.org>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 361031A8A75 for <rtcweb@ietfa.amsl.com>; Tue, 11 Nov 2014 17:36:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gKTTiAAq5QJP for <rtcweb@ietfa.amsl.com>; Tue, 11 Nov 2014 17:36:20 -0800 (PST)
Received: from mail-ie0-f177.google.com (mail-ie0-f177.google.com [209.85.223.177]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9E7321A8792 for <rtcweb@ietf.org>; Tue, 11 Nov 2014 17:36:20 -0800 (PST)
Received: by mail-ie0-f177.google.com with SMTP id tp5so12592313ieb.22 for <rtcweb@ietf.org>; Tue, 11 Nov 2014 17:36:20 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=Vxq25pdCUhmns3qa0/bXVXcC2W2b+plpb/zS+5J3idI=; b=Q7qQjZIqlc6qWGrgYCT1bIjLbK8+/Yt4SyE/71BRcHhneJJP7IQMW8hGGq+ss+tB+6 A9XHpPxteKLulXsQYDBivbsoIWCyyeX58NW8Ipg3cFABWOiVhXahsyNqgSJbWotRRflj ANEwSJo5b9vM8lEo4009LY4fzv+TTZMO4aQsV0eHEuvhGXZMiOumI4dUg0U6rFJfLSTQ I0lMMj9uifDzJ18T8d5qtp/87HeSjS2yxydDzspXSNJZqaUITKiyUIAGmJu5IAIkFUEu 04TG2Mvom0hcAz36lVsadYCdJn/NHDlec+oTI4f18BTqbeAHAJ54REYkipqtVH7SS1gf ZnaQ==
X-Gm-Message-State: ALoCoQnih22hr2UNA+qK8afLm/9ocTKNd+CEzvQMoiTr3gunAJfS+CGHZuN2p8NfOTMUaCnAQ/sy
X-Received: by 10.43.129.196 with SMTP id hj4mr46698421icc.21.1415756179872; Tue, 11 Nov 2014 17:36:19 -0800 (PST)
Received: from [192.168.1.100] (206-248-171-209.dsl.teksavvy.com. [206.248.171.209]) by mx.google.com with ESMTPSA id qo2sm2603946igb.12.2014.11.11.17.36.19 for <rtcweb@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 11 Nov 2014 17:36:19 -0800 (PST)
Message-ID: <5462B991.4030700@bbs.darktech.org>
Date: Tue, 11 Nov 2014 20:36:17 -0500
From: cowwoc <cowwoc@bbs.darktech.org>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: rtcweb@ietf.org
References: <54601E19.8080203@nostrum.com> <176316D6-D685-45F4-AA8E-A4F07521CAE4@matthew.at> <1D5CFB04-2CCB-424C-A364-1CAA05E84D12@apple.com> <20141111011054.GR8092@hex.shelbyville.oz> <E18B79D1-D8C8-4A17-A2F0-93BDAAFED698@apple.com> <BE15C090-239F-45BC-8747-501AC86653B2@gmail.com> <5461A019.6030108@alvestrand.no> <1A6093A8-A7E9-4760-B790-CC767CAA2116@gmail.com> <546265E3.7060300@alvestrand.no> <546267B9.8020605@andyet.net> <4E528337-ED7A-41ED-B196-A4CF6C4D84DF@phonefromhere.com> <54627964.7040709@bbs.darktech.org> <5462AB64.1070300@alvestrand.no>
In-Reply-To: <5462AB64.1070300@alvestrand.no>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/D3JFIIG4JfCmoT_tv3o62Qx22og
Subject: Re: [rtcweb] MTI Video Codec: a novel proposal
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Nov 2014 01:36:24 -0000

On 11/11/2014 7:35 PM, Harald Alvestrand wrote:
> Don't forget the case where one author wants to write the same 
> application in two different environments, and wants to use some 
> toolkits not written by himself. If those toolkits don't support the 
> same codecs ... he can't interoperate with himself. 

Agreed.

>> Another spin on this would be to say: all libraries/platforms
>> (abstraction layers used to write applications) must implement both
>> codecs, whereas applications (end-users) can implement as many codecs
>> as they'd like.
> That would indeed be a possible spin, but a somewhat strange one.

I don't think a "WebRTC compliant" logo would be relevant for 
applications (the end-user couldn't care less) but for 
toolkits/frameworks/libraries this is suddenly relevant. Developers will 
look for such things when researching libraries. The same applies for 
browsers. So yes, this approach might sound weird at first but the more 
I think about it the more I think these groups would benefit from 
different expectations.

Gili