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

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 21 March 2011 17:02 UTC

Return-Path: <hannes.tschofenig@gmx.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 BF81028C16D for <apps-discuss@core3.amsl.com>; Mon, 21 Mar 2011 10:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 x26O93Fl2sXy for <apps-discuss@core3.amsl.com>; Mon, 21 Mar 2011 10:02:18 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 6418C28C156 for <apps-discuss@ietf.org>; Mon, 21 Mar 2011 10:02:16 -0700 (PDT)
Received: (qmail invoked by alias); 21 Mar 2011 17:03:48 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.3]) [88.115.222.204] by mail.gmx.net (mp069) with SMTP; 21 Mar 2011 18:03:48 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX1+cUONeY1ic6P9tpbDc3Uede3+IEBWvCoG8z2s7+S EPou6XfcL8KGEh
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset="us-ascii"
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <AANLkTi=6aJZ7QoWZrKvPbw4E5P+sQGjyANw5C+vCdxdH@mail.gmail.com>
Date: Mon, 21 Mar 2011 19:03:46 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F5590FD-CF20-46FF-B85D-E8CA66133D00@gmx.net>
References: <4D87612E.3090900@dcrocker.net> <AANLkTik_f-4E8eoWbY2SowzTUdk53L3oiLZwFgoFS20y@mail.gmail.com> <4D876B4C.5070706@dcrocker.net> <4D877D30.9090502@stpeter.im> <AANLkTi=6aJZ7QoWZrKvPbw4E5P+sQGjyANw5C+vCdxdH@mail.gmail.com>
To: Bhumip Khasnabish <vumip1@gmail.com>
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 0
Cc: Apps Discuss <apps-discuss@ietf.org>, Scott Brim <scott.brim@gmail.com>, dcrocker@bbiw.net
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
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 17:02:18 -0000

The most important aspect to look at is where interoperability is truly needed. 
The speakers at the plenary will argue that you do not need interoperability everywhere.

Do not get me wrong - interoperability is great but it comes at a cost. 

If you look at the Web application space then you would quickly ask yourself "Where would the Web be if everything has to be standardized?"


On Mar 21, 2011, at 6:52 PM, Bhumip Khasnabish wrote:

> >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.
> >Peter
> Yes, actually each service, service provider, developer-group, etc. and so on start using own protocol/API .. the problem actually gets worse .. and the silos get bigger and bigger (not necessarily better). 
>  
> Bhumip