[ogpx] Fwd: Re: Feedback to draft-hamrick-vwrap-authentication-00.txt

Meadhbh Hamrick <ohmeadhbh@gmail.com> Sun, 07 March 2010 02:44 UTC

Return-Path: <ohmeadhbh@gmail.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 219EE3A89DB for <ogpx@core3.amsl.com>; Sat, 6 Mar 2010 18:44:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.425
X-Spam-Level:
X-Spam-Status: No, score=-2.425 tagged_above=-999 required=5 tests=[AWL=0.173, BAYES_00=-2.599, HTML_MESSAGE=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 AIPWEWtvpXaf for <ogpx@core3.amsl.com>; Sat, 6 Mar 2010 18:44:14 -0800 (PST)
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) by core3.amsl.com (Postfix) with ESMTP id E677B3A8152 for <ogpx@ietf.org>; Sat, 6 Mar 2010 18:44:13 -0800 (PST)
Received: by pwi3 with SMTP id 3so3449768pwi.31 for <ogpx@ietf.org>; Sat, 06 Mar 2010 18:44:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=8fWbyL3sm/9FoHydItaOHpTO1v4KOLgbqTCBPPzq1ac=; b=EryjTOs3Hn0dNPWLZW4vd6i6bfqcQhR3VtQ6ztvfoNTTE44ug/dc9fT+Hw5R5uZOwA 3hV/DPS3dsQ+FEX7U7TFFOY3U3RRE4Uc08hEm9kgt9fFsSgqqN0c77+3X+jhexVCQhhw TBMrv5ziNb6a7749s+yEbo1LDmBf5giicAdZc=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=MPTXQrs8DmvgdAny46N7LCawMG96DuEDembXTYRxWAy4tZftyD5eY1dsz8v/XRif5i CB8v5CeBGHxFhMfrW9ztpesauK/c//9moChpAk+/uGPxMbM+T1xqmoz9OGVgZksRf+6k Dfvg6PlV3vjAtADdseirsZaAxvBxYcLFZJ9Eg=
MIME-Version: 1.0
Received: by 10.142.122.6 with SMTP id u6mr2027260wfc.8.1267929854599; Sat, 06 Mar 2010 18:44:14 -0800 (PST)
In-Reply-To: <b325928b1003060818lf8d45b0qc5149340857a93f1@mail.gmail.com>
References: <20100306142607.GB24621@alinoe.com> <b325928b1003060818lf8d45b0qc5149340857a93f1@mail.gmail.com>
Date: Sat, 06 Mar 2010 18:44:14 -0800
Message-ID: <b325928b1003061844kd9e14f7lffa27aab87a0015c@mail.gmail.com>
From: Meadhbh Hamrick <ohmeadhbh@gmail.com>
To: ogpx@ietf.org
Content-Type: multipart/alternative; boundary="001636e0ba039561eb04812cec74"
Subject: [ogpx] Fwd: Re: Feedback to draft-hamrick-vwrap-authentication-00.txt
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: Sun, 07 Mar 2010 02:44:15 -0000

Sorry. Yes, this was supposed to go to the list.

---------- Forwarded message ----------
From: "Meadhbh Hamrick" <ohmeadhbh@gmail.com>
Date: Mar 6, 2010 8:18 AM
Subject: Re: [ogpx] Feedback to draft-hamrick-vwrap-authentication-00.txt
To: "Carlo Wood" <carlo@alinoe.com>

hey carlo.

i think the intent was that names (first, last and account) were to be
LLSD strings, which are defined in the LLSD / LLIDL draft. at a first
order of approximation, this means they can consist of any unicode
code point (note that this is not precisely true. refer to the type
system draft for more info.)

the rationale behind using a first and last name is to support
existing systems like Second Life and OpenSimulator, both of which
still consume first/last/password in the login sequence. the auth
draft includes an option to log in using an "account" identifier.

i think the idea here is that implementers that currently expect a
first/last/pass that want to use VWRAP to transport the authentication
info would use the agent identifier while implementers that wanted to
use a different ID ( like email address ) would use the account
identifier.

so they're there for two different use cases. agent id is for legacy
systems (and for people who just want to continue using
first/last/pass) and account id is for future implementations that may
want to use a single id.

that these two points weren't obvious probably points to a need to add
some verbiage in the draft discussing the motivation for account vs.
agent identifiers, and to mention (at least in passing) that
identifiers are strings as defined in the type-system draft.

thx for bringing this up, carlo.

-cheers
-meadhbh
--
meadhbh hamrick * it's pronounced "maeve"
@OhMeadhbh * http://meadhbh.org/ * OhMeadhbh@gmail.com




On Sat, Mar 6, 2010 at 6:26 AM, Carlo Wood <carlo@alinoe.com> wrote:
> 2.3.1.  Agent Identifier
>...