Re: [apps-discuss] IETF technical plenary: the end of application protocols

Dave CROCKER <dhc@dcrocker.net> Mon, 21 March 2011 16:36 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BEA9A28C0F4 for <apps-discuss@core3.amsl.com>; Mon, 21 Mar 2011 09:36:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.591
X-Spam-Level:
X-Spam-Status: No, score=-6.591 tagged_above=-999 required=5 tests=[AWL=0.008, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 YbZHjDWWrBCv for <apps-discuss@core3.amsl.com>; Mon, 21 Mar 2011 09:36:30 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by core3.amsl.com (Postfix) with ESMTP id 4F85028C157 for <apps-discuss@ietf.org>; Mon, 21 Mar 2011 09:36:30 -0700 (PDT)
Received: from [192.168.1.4] (adsl-67-127-56-68.dsl.pltn13.pacbell.net [67.127.56.68]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id p2LGbtTZ023419 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 21 Mar 2011 09:38:00 -0700
Message-ID: <4D877EDF.1090500@dcrocker.net>
Date: Mon, 21 Mar 2011 09:37:51 -0700
From: Dave CROCKER <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
MIME-Version: 1.0
To: Peter Saint-Andre <stpeter@stpeter.im>
References: <4D87612E.3090900@dcrocker.net> <AANLkTik_f-4E8eoWbY2SowzTUdk53L3oiLZwFgoFS20y@mail.gmail.com> <4D876B4C.5070706@dcrocker.net> <4D877D30.9090502@stpeter.im>
In-Reply-To: <4D877D30.9090502@stpeter.im>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.17]); Mon, 21 Mar 2011 09:38:01 -0700 (PDT)
Cc: Scott Brim <scott.brim@gmail.com>, Apps Discuss <apps-discuss@ietf.org>
Subject: Re: [apps-discuss] IETF technical plenary: the end of application protocols
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Mar 2011 16:36:31 -0000

On 3/21/2011 9:30 AM, Peter Saint-Andre wrote:
> On 3/21/11 9:14 AM, Dave CROCKER wrote:
>> To me, one of the more serious problems is the failure to see that these
>> implement a potential explosion of proprietary protocols.
>
> This is what I see, too: each service will have its own API / protocol,
> resulting in wonderful vendor lock-in for the service provider but a
> distinct lack of interoperability across services. We've just moved the
> problem elsewhere.


I think Claudio raises another fundamental point, namely the loss of 
interoperability.  The proposed model is a pure silo, with no apparent ability 
to have variations or incremental capabilities that build on the base, except by 
the single vendor providing the proprietary protocol.

The point that Claudio and Ted make about possible inefficiencies due to 
repeated download is also worth noting.'

d/

-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net