Re: [ogpx] Updated deployment and trust draft posted

Carlo Wood <carlo@alinoe.com> Sat, 06 March 2010 13:25 UTC

Return-Path: <carlo@alinoe.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2543B3A8A0C for <ogpx@core3.amsl.com>; Sat, 6 Mar 2010 05:25:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.43
X-Spam-Level:
X-Spam-Status: No, score=-1.43 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_AT=0.424, HOST_EQ_AT=0.745]
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 rDbLoNHn02hz for <ogpx@core3.amsl.com>; Sat, 6 Mar 2010 05:25:13 -0800 (PST)
Received: from viefep15-int.chello.at (viefep15-int.chello.at [62.179.121.35]) by core3.amsl.com (Postfix) with ESMTP id DF2823A8307 for <ogpx@ietf.org>; Sat, 6 Mar 2010 05:25:12 -0800 (PST)
Received: from edge03.upcmail.net ([192.168.13.238]) by viefep15-int.chello.at (InterMail vM.8.01.02.00 201-2260-120-20100118) with ESMTP id <20100306132513.XZZG4249.viefep15-int.chello.at@edge03.upcmail.net>; Sat, 6 Mar 2010 14:25:13 +0100
Received: from mail9.alinoe.com ([77.250.43.12]) by edge03.upcmail.net with edge id ppR81d07j0FlQed03pRA0X; Sat, 06 Mar 2010 14:25:13 +0100
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.71) (envelope-from <carlo@alinoe.com>) id 1Nnu0C-0006XE-FW; Sat, 06 Mar 2010 14:25:08 +0100
Date: Sat, 06 Mar 2010 14:25:08 +0100
From: Carlo Wood <carlo@alinoe.com>
To: "Infinity Linden (Meadhbh Hamrick)" <infinity@lindenlab.com>
Message-ID: <20100306132508.GA24621@alinoe.com>
References: <OFE468F9B5.25216572-ON852576CD.0053ADC1-852576CD.0053E11E@us.ibm.com> <382d73da1002170836x3c689a89ve5e62a67e6173bdc@mail.gmail.com> <OF7F0480B9.5C99B16B-ON852576CD.00623CB9-852576CD.006335DE@us.ibm.com> <e0b04bba1002180129if2eeabv5eb7f7db76bfaf1d@mail.gmail.com> <6c9fcc2a1002180918p2bf40959v32a1163848c76717@mail.gmail.com> <20100219141252.GA16509@alinoe.com> <b8ef0a221002190817q1131fdf0v87c4b48f62839baa@mail.gmail.com> <20100221105631.GA32748@alinoe.com> <OF985E62D1.9C6EC6C9-ON852576D4.005FCAC1-852576D4.006031EE@us.ibm.com> <3a880e2c1002241115w7fcb906di208f8c3eb8aac0ec@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <3a880e2c1002241115w7fcb906di208f8c3eb8aac0ec@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Cloudmark-Analysis: v=1.1 cv=dpF41kme/xf52BVFam8AAZA93/SDXlKdpo3AQ/UyHbw= c=1 sm=0 a=_swAn1J59o8A:10 a=kj9zAlcOel0A:10 a=BjFOTwK7AAAA:8 a=Jr9IHo8x4lPYu89GczkA:9 a=KtZoQxejeb66dD5Q5EOcJLwyZ7AA:4 a=CjuIK1q_8ugA:10 a=bW3kdApBr58A:10 a=34vfOihJB_IaBUTp:21 a=4ZhZH-iVYqiEMZdD:21 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: ogpx@ietf.org
Subject: Re: [ogpx] Updated deployment and trust draft posted
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 06 Mar 2010 13:25:14 -0000

Sorry for the late reply, but I couldn't find much time lately,

On Wed, Feb 24, 2010 at 11:15:02AM -0800, Infinity Linden (Meadhbh Hamrick) wrote:
> in a related issue. we use the term "client application" for an app that
> accesses services. the most visible client application is the one that renders
> the virtual world for the user. i think this kind of application is
> traditionally called a "user agent" in other IETF protocols. so...
> 
> question : does it make sense to introduce the concept of a "user agent" as the
> client application that is intended to have direct interaction with the user?  
> i think it would be good to explain that "clients" or "client applications" do
> not always have to be "user agents." if so, lemme modify the intro doc to
> reflect it.

I don't think rendering or having interaction with a human has anything to do
with VWRAP, I'd define a "user agent" as "end point"; in theory, such an end
point could be not the application that renders, it could be bot that has
no rendering or human interaction at all.

I'm ok with still using the word "user" in "user agent", but some clarification
is indeed necessary then. On the other hand, I have no problem understanding
"client application" at all. The use of "user agent" in it's place seems
only confusing to me.

-- 
Carlo Wood <carlo@alinoe.com>