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

Hannes Tschofenig <hannes.tschofenig@gmx.net> Mon, 21 March 2011 18:14 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 5C79E28C0F8 for <apps-discuss@core3.amsl.com>; Mon, 21 Mar 2011 11:14:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.156
X-Spam-Level:
X-Spam-Status: No, score=-102.156 tagged_above=-999 required=5 tests=[AWL=-0.442, BAYES_00=-2.599, HTML_FONT_FACE_BAD=0.884, HTML_MESSAGE=0.001, 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 Xhkw-wDnN59r for <apps-discuss@core3.amsl.com>; Mon, 21 Mar 2011 11:14:53 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by core3.amsl.com (Postfix) with SMTP id 9083C3A68CC for <apps-discuss@ietf.org>; Mon, 21 Mar 2011 11:14:52 -0700 (PDT)
Received: (qmail invoked by alias); 21 Mar 2011 18:16:20 -0000
Received: from a88-115-222-204.elisa-laajakaista.fi (EHLO [192.168.1.3]) [88.115.222.204] by mail.gmx.net (mp041) with SMTP; 21 Mar 2011 19:16:20 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX18kVjQSY10kQi3pRM9oHm5Xtm8ibeFVentdvzXJT9 xBkYzCU6C1C1oQ
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: multipart/alternative; boundary=Apple-Mail-11-301632893
From: Hannes Tschofenig <hannes.tschofenig@gmx.net>
In-Reply-To: <6266.1300730701.805233@puncture>
Date: Mon, 21 Mar 2011 20:16:19 +0200
Message-Id: <58FF0930-4C05-4791-A40C-B64BDA2E3165@gmx.net>
References: <4D87612E.3090900@dcrocker.net> <560B27DE-B188-45D6-AC91-51A643FD8520@gmx.net> <4D8785D2.5070306@dcrocker.net> <A4DB77E0-3041-44D5-B232-6420ACF02978@gmx.net> <AANLkTikkLBDJc4s6+okGqp-8ZbZahfen+C7ZkBJuAjjN@mail.gmail.com> <6266.1300730701.805233@puncture>
To: Dave Cridland <dave@cridland.net>
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 0
Cc: Scott Brim <scott.brim@gmail.com>, Dave CROCKER <dcrocker@bbiw.net>, General discussion of application-layer protocols <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
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 18:14:54 -0000

On Mar 21, 2011, at 8:05 PM, Dave Cridland wrote:

> With XMPP, an XMPP server will talk with other XMPP servers - this means that HTTP cannot be used. (And if anyone suggests S2S/BOSH I will throw up).

I was focusing more on the client-to-server interaction; I don't think the need for interoperability on the server-to-server side vanishes. 

The model I have in my mind is this one:
(modified from http://tools.ietf.org/html/draft-rosenberg-rtcweb-framework-00)


                +-----------+             +-----------+
                |   Web     | Server-to-  |   Web     |
                |           | Server      |           |
                |           |-------------|           |
                |  Server   |             |  Server   |
                |           |             |           |
                +-----------+             +-----------+
                     /                           \
                    /                             \   Proprietary over
                   /                               \  HTTP/Websockets
                  /                                 \
                 /  Proprietary over                 \
                /   HTTP/Websockets                   \
               /                                       \
         +-----------+                           +-----------+
         |JS/HTML/CSS|                           |JS/HTML/CSS|
         +-----------+                           +-----------+
         +-----------+                           +-----------+
         |           |                           |           |
         |           |                           |           |
         |  Browser  | ------------------------- |  Browser  |
         |           |   Media (if needed)       |           |
         |           |                           |           |
         +-----------+                           +-----------+

The browser to server side does not need to be standardized. Everyone is, however, free to use what standardized protocol they want. 
There is no shortage of standardized protocols for that interface. 

If you want cross-service provider communication then the interoperability need is on the server-to-server side. 

Given that you are heavily involved in the XMPP space you are very much familiar with this model. 

Ciao
Hannes