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

Barry Leiba <barryleiba.mailing.lists@gmail.com> Tue, 06 April 2010 04:32 UTC

Return-Path: <barryleiba.mailing.lists@gmail.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 7155A3A6A55 for <vwrap@core3.amsl.com>; Mon, 5 Apr 2010 21:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=0.001]
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 AXeksrTydJib for <vwrap@core3.amsl.com>; Mon, 5 Apr 2010 21:32:14 -0700 (PDT)
Received: from mail-fx0-f227.google.com (mail-fx0-f227.google.com [209.85.220.227]) by core3.amsl.com (Postfix) with ESMTP id 3A2A13A67CC for <vwrap@ietf.org>; Mon, 5 Apr 2010 21:32:14 -0700 (PDT)
Received: by fxm27 with SMTP id 27so1678491fxm.28 for <vwrap@ietf.org>; Mon, 05 Apr 2010 21:32:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:reply-to:in-reply-to :references:date:received:message-id:subject:from:to:content-type; bh=aZ1j/oFEEo3O0GoqMZnuYL+6tE2Dz7Fc1kcNWYt0e3k=; b=LocFmWrkvPvcwB0xAd3c/DYHWtOy3c8P/jY+yYXDMIuPj6pKDyT2JFLuS7ioPfieox uHiY6+NPZUDq/Y1ZiFhsAKFkIwuFMdZhg4L+0NdB8AxFwQNojVvNQkG/CvCabJ717DXL 8h7lVI2Uza0coGP3i4ANE9y60Wt31pEYzcl5o=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:content-type; b=xSH5eUMVD8jzBKPMOV36WdNVVOJAjdqwT6hOzzpvuRwSfnQniN6oNed2l7MRJr4I/X wCqQSrUNhXubTOpstRfAbOllsWbuHdf7HZPG2LxDH11WX3ueFgW/t9nDs88RjTP6XL/B YkubWx4KhBtqpfdypnke9HkY5LPp/oRbqXFKw=
MIME-Version: 1.0
Received: by 10.223.112.15 with HTTP; Mon, 5 Apr 2010 21:32:08 -0700 (PDT)
In-Reply-To: <y2gb325928b1004051307u5f5e64d9zd18b70bfd8307d6a@mail.gmail.com>
References: <62BFE5680C037E4DA0B0A08946C0933DCB738C13@rrsmsx506.amr.corp.intel.com> <t2jb325928b1004051220i5f1d8f04od2602f26f758f3da@mail.gmail.com> <CDB96FF3-A282-40B3-94D8-A9B6A00D8AF5@bbn.com> <62BFE5680C037E4DA0B0A08946C0933DCB738C9B@rrsmsx506.amr.corp.intel.com> <y2gb325928b1004051307u5f5e64d9zd18b70bfd8307d6a@mail.gmail.com>
Date: Tue, 6 Apr 2010 00:32:08 -0400
Received: by 10.223.7.91 with SMTP id c27mr6748979fac.19.1270528328083; Mon, 05 Apr 2010 21:32:08 -0700 (PDT)
Message-ID: <y2h6c9fcc2a1004052132z77168acaq26928209fa1e3e03@mail.gmail.com>
From: Barry Leiba <barryleiba.mailing.lists@gmail.com>
To: vwrap@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: Re: [vwrap] Removing first name / last name assumptions?
X-BeenThere: vwrap@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: barryleiba@computer.org
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 04:32:15 -0000

On Mon, Apr 5, 2010 at 4:07 PM, Meadhbh Hamrick <ohmeadhbh@gmail.com> wrote:
> no. we're proposing taking it off the table because there is a very
> high likelihood that are valid first and/or last names in a particular
> implementation that include spaces and periods. this is the reason we
> came up with having first_name and last_name as separate strings in
> the transfer syntax, and not a single string identifying the avatar's
> name.
>
> why do we need to REMOVE support for Second Life from this protocol?

Well, here's the thing:

First: I've spent a lot of years designing protocols, and I think it's
a terrible idea to define a specific artifact of a specific
implementation in a new protocol.  We've done it many times before,
and it's pretty much always caused problems.  Sometimes those problems
eventually worked themselves out, but I'm quite sure it was a mistake
to go there.

Second: I don't see it as a question of "removing support for Second
Life", but one of looking at alternatives that are protocol-clean and
allow everyone to work with it.  And, by the way, I don't consider two
separate identifier fields, from which you're meant to pick which you
want to use, to be "protocol-clean".

Why not define the agent identifier in a self-parsing way?  Something
like this should work (written in ABNF):

   agent-identifier := delim 1*(id-part delim)
   id-part = string
   delim = 1char

...where the idea is that the delimiter is a single character that
appears as the first character (so it's self-identifying), and then
between ID parts.  The implementation would pick a character (which
could be a non-printable code point, such as 0x00 or 0x01, if
necessary) that doesn't appear in any identifier part.  Here's a
sampling of agent-identifiers, each within quotes just to make it
clear where they start and end:
   " Joshua Linden "
   ".Joshua.Linden."  (another way to represent the same thing)
   "/Joshua/Linden/"  (a third)
   "XJoshuaXLindenX"  (a fourth)
   " Melanie "  (an identifier with just one part)
   "rMelanier"  (the same, in another representation)
   ".Melanie."  (or less weirdly)
   " Barak Hussein Obama "   (here's one with three parts)
   "+Peter+Blair+Dennis+Bernard+Noone+" (a five-part one; extra credit
if you're old enough to know who he is)
   "~le roy~barr~"  (Meadhbh's example with an embedded blank)

This scheme only adds two characters to the identifier (the leading
and trailing delimiter, and we *could* eliminate the trailing one, if
people prefer, by defining agent-identifier as "1*(delim id-part)"...
I like having it), and seems to solve everyone's problem.

Barry, as participant