29 Feb
2004
29 Feb
'04
7:41 a.m.
At 08:02 AM 2/29/2004, Jakob Schlyter wrote:
all users have addresses like user(a)example.com. the same user has an alias like
5551234(a)example.com (for UAs that cannot handle alphanumerical addresses).
some UAs will send a REGISTER with a To: of user(a)example.com, some with a To: of
5551234(a)example.com. both REGISTERs needs update the location records of user(a)example.com.
rewriting 5551234(a)example.com to user(a)example.com for INVITE et al can be handled using
enum and/or normal alias lookup.
the authentication user could always be required to be user(a)example.com, but I guess that
should be handled separately.
I have a feeling this should be handled like a normal alias on REGISTER processing +
allowed 3rd party register.
It seems to me the request to be able to register using different names linked to
a primary account removes lot of transparency, which is not good for security
and troubleshooting. If you have a mixed environment of fully-fledged and numbers-only
terminals, you can use numbers by default and have "nice" aliases.
-jiri
what needs to be modified so that the users can
register using either number or alphanumerical username? I want to be able to use either
name or number for registration, and perhaps for authentication too.
I do not understand the use scenario.