Re: [apps-discuss] IETF technical plenary: the end of application protocols
Hannes Tschofenig <hannes.tschofenig@gmx.net> Tue, 22 March 2011 09:10 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 E46333A67E5 for <apps-discuss@core3.amsl.com>; Tue, 22 Mar 2011 02:10:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.83
X-Spam-Level:
X-Spam-Status: No, score=-102.83 tagged_above=-999 required=5 tests=[AWL=-0.231, 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 r8wRhgUtQhIf for <apps-discuss@core3.amsl.com>; Tue, 22 Mar 2011 02:10:52 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by core3.amsl.com (Postfix) with SMTP id 5CF3F3A67E1 for <apps-discuss@ietf.org>; Tue, 22 Mar 2011 02:10:49 -0700 (PDT)
Received: (qmail invoked by alias); 22 Mar 2011 09:12:21 -0000
Received: from unknown (EHLO [10.255.135.249]) [192.100.123.77] by mail.gmx.net (mp032) with SMTP; 22 Mar 2011 10:12:21 +0100
X-Authenticated: #29516787
X-Provags-ID: V01U2FsdGVkX19ui/lzGJRu5+lmB3jUBsVwHStAjl7cgbxudskaTT cAnfbIPvtj3Wzr
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: <6.2.5.6.2.20110322002954.0ca26cc8@resistor.net>
Date: Tue, 22 Mar 2011 11:12:16 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <4B3040C3-BA44-4AA8-A0BC-395BA0E6DDB7@gmx.net>
References: <4D87612E.3090900@dcrocker.net> <4D881C04.2080406@qualcomm.com> <6.2.5.6.2.20110321223051.0e352650@resistor.net> <3D3C75174CB95F42AD6BCC56E5555B450404241E@FIESEXC015.nsn-intra.net> <6.2.5.6.2.20110322002954.0ca26cc8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1082)
X-Y-GMX-Trusted: 0
Cc: 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
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: Tue, 22 Mar 2011 09:10:57 -0000
On Mar 22, 2011, at 10:47 AM, SM wrote: > I read "post-standardization environment" in terms of an organization trying to find something to do when its mission is obsoleted by events. We had to find some term to describe this paradigm and concept. When you look through the broader standardization landscape then you for sure will notice that there are architectural differences in where groups see the need for standards and interoperability and what degree of interoperability is necessary. For example, compare a 3GPP IMS architecture, the IETF SIP architecture, and the RTCWeb-based architecture. I hope you recognize differences - differences that go beyond the protocol level. I assume that you do not just randomly standardize something and wait for someone else to pick it up (although researchers like to explore the entire solution space and that's fine as well). While it is difficult to provide suggestions regarding the approach a protocol designer should take there are various side-effects of any decision you make. When we interviewed folks in the Web community (from inside the IETF as well as outside) it was not so clear where the limits for the Web (HTML/JavaScript) model are. In any case they are changing rapidly. We hope to get more feedback from those who have been exposed to some of the mentioned Web technologies. Are you this Web person? Ciao Hannes
- [apps-discuss] IETF technical plenary: the end of… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Claudio Allocchio
- Re: [apps-discuss] IETF technical plenary: the en… Bhumip Khasnabish
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Claudio Allocchio
- Re: [apps-discuss] IETF technical plenary: the en… Peter Saint-Andre
- Re: [apps-discuss] IETF technical plenary: the en… Ted Hardie
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Claudio Allocchio
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Cyrus Daboo
- Re: [apps-discuss] IETF technical plenary: the en… Bhumip Khasnabish
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Graham Klyne
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Claudio Allocchio
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland
- Re: [apps-discuss] IETF technical plenary: the en… Claudio Allocchio
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Ted Hardie
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland
- Re: [apps-discuss] IETF technical plenary: the en… Pete Resnick
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… SM
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Tschofenig, Hannes (NSN - FI/Espoo)
- Re: [apps-discuss] IETF technical plenary: the en… Graham Klyne
- Re: [apps-discuss] IETF technical plenary: the en… SM
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Mark Nottingham
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Leslie Daigle
- [apps-discuss] IETF-port-80 technical plenary Re:… Leslie Daigle
- Re: [apps-discuss] IETF-port-80 technical plenary… Mark Nottingham
- Re: [apps-discuss] IETF technical plenary: the en… Paul Hoffman
- Re: [apps-discuss] IETF technical plenary: the en… Claudio Allocchio
- Re: [apps-discuss] IETF technical plenary: the en… Nico Williams
- Re: [apps-discuss] IETF technical plenary: the en… Peterson, Jon
- Re: [apps-discuss] IETF technical plenary: the en… SM
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Nico Williams
- Re: [apps-discuss] AJAX is the new NAT Carsten Bormann
- Re: [apps-discuss] AJAX is the new NAT Marc Petit-Huguenin
- Re: [apps-discuss] AJAX is the new NAT Ted Hardie
- Re: [apps-discuss] AJAX is the new NAT Peterson, Jon
- Re: [apps-discuss] AJAX is the new NAT Marc Petit-Huguenin
- Re: [apps-discuss] IETF technical plenary: the en… Peter Saint-Andre
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland
- Re: [apps-discuss] IETF technical plenary: the en… Scott Brim
- Re: [apps-discuss] IETF technical plenary: the en… Pete Resnick
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Lyndon Nerenberg (VE6BBM/VE7TFX)
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland
- Re: [apps-discuss] IETF technical plenary: the en… Peter Saint-Andre
- Re: [apps-discuss] IETF technical plenary: the en… Nico Williams
- [apps-discuss] HYBI Alexey Melnikov
- Re: [apps-discuss] HYBI Salvatore Loreto
- Re: [apps-discuss] HYBI Graham Klyne
- Re: [apps-discuss] IETF technical plenary: the en… Graham Klyne
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Dave CROCKER
- Re: [apps-discuss] IETF technical plenary: the en… Hannes Tschofenig
- Re: [apps-discuss] IETF technical plenary: the en… Dave Cridland