Skip to Content.
Sympa Menu

isn-discuss - Re: [isn-discuss] Re: Interesting uses for isn

Subject: Discussion List for Freenum/ITAD Subscriber Number (ISN) Project

List archive

Re: [isn-discuss] Re: Interesting uses for isn

Chronological Thread 
  • From: "Ben Teitelbaum" <>
  • To:
  • Subject: Re: [isn-discuss] Re: Interesting uses for isn
  • Date: Thu, 29 Nov 2007 17:08:56 -0800


Sure, let's start with explicit queries, as you suggest.  I think we'll soon need a convention for resolving domains into ITADs as well.

Two advantages of the hashing approach I suggested are:

1) It makes the long term direction clearer, since, in a very explicit way, ISNs become numeric aliases for email addresses.

2) Once you've cached the domain-to-ITAD mapping and prefix, you can derive ISNs from email addresses offline.

However, a huge disadvantage of the approach I suggested is the need for a widespread local numbering convention.

-- ben

On 11/29/07, John R Covert <> wrote:
Let's get the directory url that's currently on the administrators' pages
into DNS; I suggest directory.<itad>

This would be an HTML directory, organized in whatever manner the ITAD
owner wants.

Let's add another URL to the administrators' pages, and call it

It would be a cgi, accepting either post or get, and would be able to
search by a standard set of fields.  For example, if I put the following
url into my admin page as the directorysearch URL:

Then searches could be done as follows:

and so on.  We just need to define a standard set of search keys.

The directory.<itad> page might have a window that
provides an interface to the directorysearch.<itad>
page (or any other search mechanism), but if the directorysearch URL
is provided, it would behave according to our standards.


-- ben

Archive powered by MHonArc 2.6.16.

Top of Page