From MAILER-DAEMON Fri Jan 03 13:40:07 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18UWiO-00018m-00
	for mharc-unity-irc3@gnu.org; Fri, 03 Jan 2003 13:38:40 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18UWi9-0000vZ-00
	for unity-irc3@nongnu.org; Fri, 03 Jan 2003 13:38:25 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18UWhx-0000dt-00
	for unity-irc3@nongnu.org; Fri, 03 Jan 2003 13:38:17 -0500
Received: from ms-2.rz.rwth-aachen.de ([134.130.3.131]
	helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18UWhi-0000JU-00
	for unity-irc3@nongnu.org; Fri, 03 Jan 2003 13:37:58 -0500
Received: from ms-2 (ms-dienst.rz.RWTH-Aachen.DE [134.130.3.132])
 by ms-dienst.rz.rwth-aachen.de
 (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTP id <0H8500GMPIF7DP@ms-dienst.rz.rwth-aachen.de> for
 unity-irc3@nongnu.org; Fri, 03 Jan 2003 19:37:55 +0100 (MET)
Received: from r220-1.rz.RWTH-Aachen.DE ([134.130.3.31])
	by ms-2 (MailMonitor for SMTP v1.2.0 Beta3) ; Fri,
 03 Jan 2003 19:37:54 +0100 (MET)
Received: from neuron (jast@p508DB6A2.dip.t-dialin.net [80.141.182.162])
	h03IY9Dj011890	for
	<unity-irc3@nongnu.org>; Fri, 03 Jan 2003 19:34:09 +0100 (MET)
Date: Fri, 03 Jan 2003 19:34:30 +0100
From: Jan =?ISO-8859-1?B?S3IwSBEREDlIIAQDBgFBEBA=?=
	<jan.krueger@rwth-aachen.de>
To: unity-irc3@nongnu.org
Message-id: <20030103193430.3c72a728.jan.krueger@rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; )
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: [Unity-irc3] 
 user IDs, distribution among dbservers and uniqueness of nicknames
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 03 Jan 2003 18:38:40 -0000

I've been talking about giving unique IDs to all users on the network.
The last design I talked about was a 48 bit ID, composed of:
 * domain ID (16 bits)
 * client ID on domain (32 bits)
Question: will we ever have 4 billions of users on one domain? If not, we could make the ID a bit short to save some more space.

Here's a concept on how to give out those IDs to clients:
when a client registers with a dbserver, the dbserver will pick out a random 32 bit value and see if there's a user associated to it yet. Since we won't ever have close to even 2 billion users, we will (statistically) always get a free ID with two attempts. If we have a good randomization algorithm, this would also provide us with a nice way to split the database - the distribution across 32 bits would be very good. If we, for example, had 32 dbservers on one network, we could decide which one was to get a new account by looking at the first 5 bits of the ID.

When we consequently use this ID approach, we could make all servers (and clients!) handle users by their ID only. If a client wanted a nickname for a user, it would send a query to a dbserver about that ID and would be supplied with loads of Good Stuff (tm). A client could then also choose to ignore nick changes (and override nicks with customly chosen ones).
This would get us rid of nickname registration forever, since the only important thing will be some kind of username to use in the hostmask (if at all). But that's an issue the individual dbservers will have to deal with, so let's not get too deep into it.
Of course, a lot of people won't like that, but nobody will be hogging nicknames any longer. To make a user identifyable by other users, the dbserver could choose to provide additional information (e.g. a "real name", a cloaked or real hostname, a username, an URL or just about anything else, this is not our problem right now).
Sample protocol (to be tokenized and/or binarized):

---------
[> - client to server
 < - server to client]

> DB WHOIS 19231738927
< RPL_WHOIS_INFO 19231738927 nick=billyboy domain=QuackWeb   custom=BillGates213 real="Bill Gates" ident=bill.gates   host=cloaked-5f243db34.macrosoft.com priv="IRC server operator"   priv="Database operator" idle=100239 server=irc3.foo.uk.quackweb.org
----------
nick, domain and so on are here predefined fields for WHOIS queries, we'd need to agree on what kind of fields irc3 will need.

Clients could locally store the non-connection related information (i.e. nick, domain, realname) locally and refresh when needed. Of course, we would need some tag for domains that don't want permanent registration of users so we can let the client know not to save any info for those domains but only cache it in memory.

CHANNELS
========
We could make exactly the same things apply to channels. Of course it would be up to the dbserver whether to allow multiple channels with the same name (same goes for nicknames, actually. Of course, keeping track of uniqueness of nicknames or channels will put additional load to the dbserver since we'll have to use hash tables then).

SEARCH on names of users/channels
=================================
This would of course be very CPU intensive compared to doing a whois on an ID. That's why I suggest we add yet another tier of servers for that kind of stuff. Dbserver could regularly publish nick and host info and all the like to this searching server if they want to. [This idea taken from Ian Frechette too]


BIG ADVANTAGE
=============
Routing servers would need an amazingly small amount of memory since they don't need to know a lot about remote clients and channels. We could stuff all of this into the dbservers.
We could also use another thing Ian suggested on the-project, which is storing the IDs of locally connected members of channels only. That is, don't store info about what remote clients are in a channel - only store the ID of their server. Saves a lot of memory.

Let me know what you think about all of this.
--jast




From MAILER-DAEMON Wed Jan 08 05:21:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18Vwx6-00064s-00
	for mharc-unity-irc3@gnu.org; Tue, 07 Jan 2003 11:51:44 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18VfrR-0007DL-00
	for unity-irc3@nongnu.org; Mon, 06 Jan 2003 17:36:45 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18VfrN-0007CA-00
	for unity-irc3@nongnu.org; Mon, 06 Jan 2003 17:36:44 -0500
Received: from ms-1.rz.rwth-aachen.de ([134.130.3.130]
	helo=ms-dienst.rz.rwth-aachen.de)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18VfrM-00072W-00
	for unity-irc3@nongnu.org; Mon, 06 Jan 2003 17:36:41 -0500
Received: from ms-1 (ms-dienst.rz.RWTH-Aachen.DE [134.130.3.132])
 by ms-dienst.rz.rwth-aachen.de
 (iPlanet Messaging Server 5.2 Patch 1 (built Aug 19 2002))
 with ESMTP id <0H8B00JAXCVZ7E@ms-dienst.rz.rwth-aachen.de> for
 unity-irc3@nongnu.org; Mon, 06 Jan 2003 23:23:59 +0100 (MET)
Received: from r220-1.rz.RWTH-Aachen.DE ([134.130.3.31])
 by ms-1 (MailMonitor for SMTP v1.2.0 Beta3) ; Mon,
 06 Jan 2003 23:23:59 +0100 (MET)
Received: from neuron (jast@p508D921F.dip.t-dialin.net [80.141.146.31])
	h06MNxIL020647	for
	<unity-irc3@nongnu.org>; Mon, 06 Jan 2003 23:23:59 +0100 (MET)
Date: Mon, 06 Jan 2003 23:24:21 +0100
From: Jan =?ISO-8859-1?B?S3IIMA==?= <jan.krueger@rwth-aachen.de>
To: unity-irc3@nongnu.org
Message-id: <20030106232421.0a6df331.jan.krueger@rwth-aachen.de>
MIME-version: 1.0
X-Mailer: Sylpheed version 0.8.6claws (GTK+ 1.2.10; )
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: QUOTED-PRINTABLE
Subject: [Unity-irc3] 
 user IDs, distribution among dbservers and uniqueness of nicknames
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 06 Jan 2003 22:36:46 -0000

I first sent this mail to the list 3 days ago but it seems like it go=
t lost somehow.

I've been talking about giving unique IDs to all users on the network=
.
The last design I talked about was a 48 bit ID, composed of:
 * domain ID (16 bits)
 * client ID on domain (32 bits)
Question: will we ever have 4 billions of users on one domain? If not=
, we could make the ID a bit short to save some more space.

Here's a concept on how to give out those IDs to clients:
when a client registers with a dbserver, the dbserver will pick out a=
 random 32 bit value and see if there's a user associated to it yet. =
Since we won't ever have close to even 2 billion users, we will (stat=
istically) always get a free ID with two attempts. If we have a good =
randomization algorithm, this would also provide us with a nice way t=
o split the database - the distribution across 32 bits would be very =
good. If we, for example, had 32 dbservers on one network, we could d=
ecide which one was to get a new account by looking at the first 5 bi=
ts of the ID.
Note that this paragraph deals with implementation details, it's just=
 to point out how the ID approach can actually improve everything.

When we consequently use this ID approach, we could make all servers =
(and clients!) handle users by their ID only. If a client wanted a ni=
ckname for a user, it would send a query to a dbserver about that ID =
and would be supplied with loads of Good Stuff (tm). A client could t=
hen also choose to ignore nick changes (and override nicks with custo=
mly chosen ones).
This would get us rid of nickname registration forever, since the onl=
y important thing will be some kind of username to use in the hostmas=
k (if at all). But that's an issue the individual dbservers will have=
 to deal with, so let's not get too deep into it.
Of course, a lot of people won't like that, but nobody will be hoggin=
g nicknames any longer. To make a user identifyable by other users, t=
he dbserver could choose to provide additional information (e.g. a "r=
eal name", a cloaked or real hostname, a username, an URL or just abo=
ut anything else, this is not our problem right now).
Sample protocol (to be tokenized and/or binarized):

---------
[=BB - client to server
 =AB - server to client]

=BB DB WHOIS 19231738927
=AB RPL_WHOIS_INFO 19231738927 nick=3Dbillyboy domain=3DQuackWeb cust=
om=3DBillGates213   real=3D"Bill Gates" ident=3Dbill.gates host=3Dclo=
aked-5f243db34.macrosoft.com
  priv=3D"IRC server operator" priv=3D"Database operator" idle=3D1002=
39
  server=3Dirc3.foo.uk.quackweb.org
----------
nick, domain and so on are here predefined fields for WHOIS queries, =
we'd need to agree on what kind of fields irc3 will need. Here's an o=
verview:

- nick (token: n)
- domain (d) - domain the user is registered with. This is, obviously=
, useless, since we query the domain's server to get this information=
, so do we really need it?
- custom (c) - this can be used by the dbserver for just about any ki=
nd of info
- real (r) - classic real name
- ident (i) - the ident bit as used in today's hostmasks
- host (h) - the hostname, may be cloaked
- priv (p) - privileges on IRC
- idle (i) - idle time
- server (s) - server the client is connected to currently
- list of channels (l)
Dbservers could choose themselves which of those fields they'd use - =
they could even decide to disallow nicknames (fun that would be)...

Clients could locally store the non-connection related information (i=
.e. nick, domain, realname) locally and refresh when needed. Of cours=
e, we would need some tag for domains that don't want permanent regis=
tration of users so we can let the client know not to save any info f=
or those domains but only cache it in memory.

CHANNELS
=3D=3D=3D=3D=3D=3D=3D=3D
We could make exactly the same things apply to channels. Of course it=
 would be up to the dbserver whether to allow multiple channels with =
the same name (same goes for nicknames, actually. Of course, keeping =
track of uniqueness of nicknames or channels will put additional load=
 to the dbserver since we'll have to use hash tables then).

SEARCH on names of users/channels
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
This would of course be very CPU intensive compared to doing a whois =
on an ID. That's why I suggest we add yet another tier of servers for=
 that kind of stuff. Dbserver could regularly publish nick and host i=
nfo and all the like to this searching server if they want to. [This =
idea taken from Ian Frechette too]
The Good Thing (tm) about this: we'd have a searchable database of al=
l domains on our IRC networks. Everybody could (in theory) find anoth=
er user, no matter what domain they're using.
This searchable database might also include channels - this could pre=
vent from duplicate channels establishing everywhere.


BIG ADVANTAGE
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Routing servers would need an amazingly small amount of memory since =
they don't need to know a lot about remote clients and channels. We c=
ould stuff all of this into the dbservers.
This will also (hopefully) reduce non-chatting traffic since clients =
would cache data and decide themselves how often whether they want to=
 know about nick changes and stuff.
We could also use another thing Ian suggested on the-project, which i=
s storing the IDs of locally connected members of channels only. That=
 is, don't store info about what remote clients are in a channel - on=
ly store the ID of their server. Saves a lot of memory.

Here's a question: what if we get rid of @+ prefixes in channels? Tha=
t would reduce traffic again. Like, people would contact the dbserver=
 to request a change of modes and the dbserver would confirm it, but =
no new prefixes would have to be displayed to all channel members. Al=
so, this would probably kill free op channels, since there'll be noth=
ing you can show off with (except for some powers). People would have=
 to query the dbserver to find out what privileges people have (the d=
bserver can of course decide not to publish this information to peopl=
e without power on the channel) and it wouldn't show prefixes but all=
owed operations.
The dbserver could then allow for a very finetunable configuration of=
 channel powers without having to introduce n+1 prefixes.

Let me know what you think about all of this.
--jast





From MAILER-DAEMON Sat Jan 11 20:30:43 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.10.13)
	id 18XWxW-0000Ex-00
	for mharc-unity-irc3@gnu.org; Sat, 11 Jan 2003 20:30:42 -0500
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13)
	id 18XWxT-00006p-00
	for unity-irc3@nongnu.org; Sat, 11 Jan 2003 20:30:39 -0500
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13)
	id 18XWxP-0008OB-00
	for unity-irc3@nongnu.org; Sat, 11 Jan 2003 20:30:38 -0500
Received: from uds211-48.dial.hccnet.nl ([62.251.48.211]
	helo=lightning.digitalcraze.nl)
	by monty-python.gnu.org with esmtp (Exim 4.10.13)	id 18XWxO-0008Hg-00
	for unity-irc3@nongnu.org; Sat, 11 Jan 2003 20:30:34 -0500
Received: from raz (chris.digitalcraze.nl [192.168.0.1])
	h0C1NfBE032207
	for <unity-irc3@nongnu.org>; Sun, 12 Jan 2003 02:23:41 +0100
Message-ID: <001801c2b9da$0c8d2160$0100a8c0@raz>
From: "C.W.L. Hoogenboezem" <root@digitalcraze.nl>
To: <unity-irc3@nongnu.org>
Date: Sun, 12 Jan 2003 02:29:28 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0015_01C2B9E2.6E2E7100"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Subject: [Unity-irc3] test.
X-BeenThere: unity-irc3@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: "irc3 \(Unity\) public discussion" <unity-irc3@nongnu.org>
List-Id: irc3 (Unity) public discussion <unity-irc3.nongnu.org>
List-Help: <mailto:unity-irc3-request@nongnu.org?subject=help>
List-Post: <mailto:unity-irc3@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/unity-irc3>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/unity-irc3>,
	<mailto:unity-irc3-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 12 Jan 2003 01:30:40 -0000

This is a multi-part message in MIME format.

------=_NextPart_000_0015_01C2B9E2.6E2E7100
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

test..

------=_NextPart_000_0015_01C2B9E2.6E2E7100
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2920.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>test..</FONT></DIV></BODY></HTML>

------=_NextPart_000_0015_01C2B9E2.6E2E7100--




