Re: [vwrap] Removing first name / last name assumptions?

Carlo Wood <carlo@alinoe.com> Tue, 06 April 2010 18:23 UTC

Return-Path: <carlo@alinoe.com>
X-Original-To: vwrap@core3.amsl.com
Delivered-To: vwrap@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 20CAE28C0EE for <vwrap@core3.amsl.com>; Tue, 6 Apr 2010 11:23:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.432
X-Spam-Level:
X-Spam-Status: No, score=-0.432 tagged_above=-999 required=5 tests=[AWL=0.998, 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 AQcZUGUDZt4o for <vwrap@core3.amsl.com>; Tue, 6 Apr 2010 11:23:04 -0700 (PDT)
Received: from viefep11-int.chello.at (viefep11-int.chello.at [62.179.121.31]) by core3.amsl.com (Postfix) with ESMTP id 1511C28C10A for <vwrap@ietf.org>; Tue, 6 Apr 2010 11:16:39 -0700 (PDT)
Received: from edge02.upcmail.net ([192.168.13.237]) by viefep11-int.chello.at (InterMail vM.8.01.02.02 201-2260-120-106-20100312) with ESMTP id <20100406181636.ZKKG9419.viefep11-int.chello.at@edge02.upcmail.net>; Tue, 6 Apr 2010 20:16:36 +0200
Received: from mail9.alinoe.com ([77.250.43.12]) by edge02.upcmail.net with edge id 2JGZ1e03J0FlQed02JGaHo; Tue, 06 Apr 2010 20:16:36 +0200
X-SourceIP: 77.250.43.12
Received: from carlo by mail9.alinoe.com with local (Exim 4.71) (envelope-from <carlo@alinoe.com>) id 1NzDKD-0001lo-7P; Tue, 06 Apr 2010 20:16:33 +0200
Date: Tue, 6 Apr 2010 20:16:33 +0200
From: Carlo Wood <carlo@alinoe.com>
To: Meadhbh Hamrick <ohmeadhbh@gmail.com>
Message-ID: <20100406181633.GA6424@alinoe.com>
References: <t2jb325928b1004051220i5f1d8f04od2602f26f758f3da@mail.gmail.com> <CDB96FF3-A282-40B3-94D8-A9B6A00D8AF5@bbn.com> <62BFE5680C037E4DA0B0A08946C0933DCB738C9B@rrsmsx506.amr.corp.intel.com> <y2gb325928b1004051307u5f5e64d9zd18b70bfd8307d6a@mail.gmail.com> <y2h6c9fcc2a1004052132z77168acaq26928209fa1e3e03@mail.gmail.com> <4BBB45FA.8050408@gmail.com> <j2yb325928b1004060728n29284d7fvd848fc545d54ead9@mail.gmail.com> <4BBB4D6E.60600@gmail.com> <x2zf72742de1004060851rfb49f5ep823a868c345ffb64@mail.gmail.com> <x2mb325928b1004060902h69fe1520tcaa1bcee27eca253@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <x2mb325928b1004060902h69fe1520tcaa1bcee27eca253@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
X-Cloudmark-Analysis: v=1.1 cv=29LKRTqBM1RB9flqW432dy+DURWvGDGZbgxXOX7FpSE= c=1 sm=0 a=MQuG_ZtAow4A:10 a=38zWk6xDZSoA:10 a=kj9zAlcOel0A:10 a=A1X0JdhQAAAA:8 a=BjFOTwK7AAAA:8 a=SohSSitP8kvTnixF3TwA:9 a=G1jm07bj_-Au3z6I6hEA:7 a=MXjOzoU7AiCD4BM1lIXai37NS6sA:4 a=CjuIK1q_8ugA:10 a=bW3kdApBr58A:10 a=HpAAvcLHHh0Zw7uRqdWCyQ==:117
Cc: vwrap@ietf.org
Subject: Re: [vwrap] Removing first name / last name assumptions?
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual World Region Agent Protocol - IETF working group <vwrap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vwrap>
List-Post: <mailto:vwrap@ietf.org>
List-Help: <mailto:vwrap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vwrap>, <mailto:vwrap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 06 Apr 2010 18:23:06 -0000

On Tue, Apr 06, 2010 at 09:02:10AM -0700, Meadhbh Hamrick wrote:
> okay. removing the two name option from the draft.

There is no need to remove the notion of "agentID" versus
"accountID" I think. Both are thus different that I can
imagine there is the need for an overlap period, or else
indeed very specific encoding would be needed(?) for the
one-string.

[ Perhaps it should be noted however that in theory it
is possible to use the one string as a custom xml message
in itself (like Dzontas example).

This would fall completely outside the realm of VWRAP,
but it does raise the question of there really is a need
for two different types of login strings in VWRAP therefore.

The string, as defined in VWRAP, could contain (as defined by
whoever the provider is) for example:

<type>agentID</type>
<first>Firstname</first>
<last>Lastname</last>,

or

<type>accountID</type>
<ID>email@address.example.com</ID>

or any encoding a provider wishes.]

I am assuming you mean that in the draft agentID will be
a single string, just like accountID?

-- 
Carlo Wood <carlo@alinoe.com>