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

Nico Williams <nico@cryptonector.com> Thu, 24 March 2011 20:25 UTC

Return-Path: <nico@cryptonector.com>
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 933123A6846 for <apps-discuss@core3.amsl.com>; Thu, 24 Mar 2011 13:25:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.587
X-Spam-Level:
X-Spam-Status: No, score=-0.587 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FAKE_REPLY_C=2.012]
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 DYI-1pvOIoxw for <apps-discuss@core3.amsl.com>; Thu, 24 Mar 2011 13:25:07 -0700 (PDT)
Received: from homiemail-a24.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by core3.amsl.com (Postfix) with ESMTP id 647833A67F1 for <apps-discuss@ietf.org>; Thu, 24 Mar 2011 13:25:07 -0700 (PDT)
Received: from homiemail-a24.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTP id 31C572C806B for <apps-discuss@ietf.org>; Thu, 24 Mar 2011 13:26:42 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=GET80cRcpZZRSeo0lF35f dSJephjw7kgoMHrLsPzCF/qjXMnxuQIqIjH3cgpbi2N4ztVLK9OkAaDK3vwLExm6 xMZdm5mx4v9SpqUnQxj5UoExxPIwKc9O92zJu4yzjdjSpS8tEeNY8RtMwB2K8Hyo X4vMsaKTczdqUbX9T+UL/c=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=x0SI2WAIwsIXW/P54Hlx EPKhfBM=; b=fhsFz4QLytkH0xAvERHDMEQMkwFJ2uX5KRYZFl4mioSA+wxyXwcc SmceARu0RAdkZyUATMVFWU+R7QTS/7Lcpvyni0PSgzX/ySxblaGVVp4K9yHR/QGy 8PLWKWVoKSjuRzgIAx7cdB5TPPx+RTwilspy6Nqh2B59CHbHh9BnOfw=
Received: from mail-vx0-f172.google.com (mail-vx0-f172.google.com [209.85.220.172]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTPSA id ED9EF2C8057 for <apps-discuss@ietf.org>; Thu, 24 Mar 2011 13:26:41 -0700 (PDT)
Received: by vxg33 with SMTP id 33so347703vxg.31 for <apps-discuss@ietf.org>; Thu, 24 Mar 2011 13:26:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.18.102 with SMTP id v6mr3810454vdd.224.1300998401325; Thu, 24 Mar 2011 13:26:41 -0700 (PDT)
Received: by 10.52.159.4 with HTTP; Thu, 24 Mar 2011 13:26:41 -0700 (PDT)
In-Reply-To: <4D8B5AB7.5030202@qualcomm.com>
References: <4D87612E.3090900@dcrocker.net> <4D881C04.2080406@qualcomm.com> <AANLkTimd-K4knt6nQWbhuwvOEv8uUCqi=4bNuOk20VYP@mail.gmail.com> <4D8AB5FC.9050500@stpeter.im> <AANLkTimsFR1e53CqfTGKiq+Cbf9+CKJ6LqLn378cyUGf@mail.gmail.com> <4D8B5AB7.5030202@qualcomm.com>
Date: Thu, 24 Mar 2011 15:26:41 -0500
Message-ID: <AANLkTikwcfMY36vUDcxYCcWt477kRAcJ___CxDPBQf4L@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Pete Resnick <presnick@qualcomm.com>
Content-Type: text/plain; charset=UTF-8
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
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: Thu, 24 Mar 2011 20:25:07 -0000

On Thu, Mar 24, 2011 at 9:52 AM, Pete Resnick <presnick@qualcomm.com> wrote:
> On 3/24/11 3:45 AM, Scott Brim wrote:
> On Wed, Mar 23, 2011 at 23:09, Peter Saint-Andre <stpeter@stpeter.im> wrote:
>> Whatever the reason, most people don't want to run their
>> own services -- it's much easier to visit a website, and tell people
>> that you're "on", a popular email or IM or blogging or microblogging or
>> voice or video service than it is to install and maintain postfix or
>> Prosody or WordPress or laconica or Asterisk or Yate on the server side
>> plus Thunderbird or Pidgin or Jitsi (etc.) on the client side (let alone
>> the whole stack of OS and DNS and databases and registered domains and
>> certificates and all the rest).
>
> People do seem fully capable to grasp "Here is my phone number, you can
> reach me here" and do at least that particular kind of peer-to-peer
> communication. There is no reason that IM or email or blogging *have* to be
> a service; it's a remnant of being pre-disposed to client-server models
> (including, BTW, DNS).

"Here's my phone number, call me" is not really peer-to-peer.  "Here's
my address, drop by" is.  The former relies on quite a bit of
infrastructure (all the more so when the devices are mobile), but the
latter could work even without roads, streets, etcetera (though
addresses might have to be in the form of coordinates, but don't
forget that GPS is also infrastructure).  However, the phone system's
infrastructure is an afterthought to the user, as you demonstrate :)
The same is true of the Internet, but its engineers are aware of the
infrastructure, giving us a different viewpoint than the user's.

Looked at that way, what's so strange about NAT and SIP and XMPP?
Infrastructure mediated peer-to-peer...  seems perfectly natural to
me.  Is infrastructure really avoidable?  Without infrastructure we're
almost necessarily limited to peer-to-peer communications over a small
area: the range of voice, of available travel technologies, of our
peer-to-peer electromagnetic spectrum (further limited by device power
capacity).  Or is it the type of infrastructure that bothers some
people?  DNS is OK but "servers" are not??

I see complaints about the end of the end-to-end model implied by thin
clients.  But I don't think that's a forgone conclusion.  End-to-end
_security_ is the key at any rate (or maybe that's just me looking at
things from a security point of view, or maybe I've been conditioned
by HTTP to accept that the "network" does weird things, or...).

> I hope we can have a real discussion in Prague, without too much
> grandstanding.
>
> It's going to be difficult. I can say for myself that I've been pushing for
> a deeper discussion (and getting it in many places), but the "death of
> application protocols predicted" tone of the abstract was a bit of
> grandstanding itself, IMO. Not too conducive to rational conversation.

The Internet is as organic as it's not.  I see this as yet another
step in organic development.  Some guidance may be needed to find and
avert pitfalls before hitting them (again or for the first time), but
that's as far as we can go.

Nico
--