I have been toying with the idea of setting up an ldap server for the Afternet.Org IRC Network. ldap would allow us to centralize our account system, so that channel services, websites, shell accounts, and more all ran off the same account.

At ldap's core are OID's. The same OIDs that you find in snmp queries. Each type of query in snmp, or type of schema in ldap are built in a tree of OIDs such as 2.16.840.1.113730.3.2.2 == Netscape corporation's definition of what fields define an internet person's identity in the ldap server. Any corporation or organization can register their own branch in the OID tree, to ensure there are no conflicts. Sort of like ip addresses only not limited to 4 numbers.

The problem is -- an organization like AfterNET doesn't have a corporation to register its OID. Being a loose fit group of people on the internet, Afternet doesn't have a cooperate office, or official mailing address to sign up for an OID in the normal way (say, in the 1.3.6.1.4.1--private internet organizations branch.)

So, I am proposing the creation of a new branch under the internet organizations branch, which assigns sub-trees based on already registered domain names, using a defined algorithm. I propose using the unicode UTF character numbers, and that we place them in 1.3.6.1.4.2 (internet.private.2).

To use it, you convert your domain, into its lowercase UTF components. For example foo.com becomes:

f=U+66=102, o=U+6F=111, o=U+6F=111, .=U+2E=46, c=63=99, o=U+6F=111, m=U+6D=109

1.3.6.1.4.2.63.111.109.46.102.111.111 (1.3.6.1.4.2.c.o.m..f.o.o) 

I will start us off by assigning afternet.org's oids under:

1.3.6.1.4.2.111.114.103.46.97.102.116.101.114.110.101.116