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

[Carlo Wood <[e-mail]>]

2.3.1.  Agent Identifier
2.3.2.  Account Identifier

These paragraphs (and possibly further on in the document)
refer to a first_name and last_name that together identity
an agent.

The very word 'name', certainly in combination with 'first'
and 'last', strongly suggest that these two are sequences
of octets from a restricted set, most notably, that they
should not contain unprintable characters, punctuation or
spaces.

* What is missing the definition of what characters each
  name may be made up of, and what are the maximum lengths
  that need to be supported.

Moreover, if first_name and last_name may not contain a
space, and if neither makes ever sense to be used alone
(which is the case imho), it is not really the business
of VWRAP to deal with first_name and last_name separately.

Instead one can simply define an opaque sequence of octets
representing the "Agent Identifier", which in practise
might or might not be "first_name last_name" (separated
by a space).

* I miss the point that makes it necessary to take the
  Agent Identifier apart into two not further defined
  strings.

Note that if a client application wishes to make an
explicit difference between the "first name" and "last
name" part, for example by using two separate input
fields when the user has to input them, then it can
still do so, and catenate the two before sending it
to the agent domain.

1. I propose to remove the notion of "first and last
   names" from the VWRAP documents. And only speak
   about Agent Identifier (a single sequence of octets),
   and Account Identifier (likewise).

2. Maximum length and the characters that need to
   be supported should be defined in the document.

Finally, note that if Second Life (tm) requires
a First and Last name string internally, they can
still have those: The Agent Identifier is generated
by Linden Lab, they can enforce that it exists of
two names separated by a space. So, it would be
minor/small change to accept a single string in
the authentication protocol and than separate that
again into two tokens upon receipt.

-- 
Carlo Wood <[e-mail]>