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: John Todd <>
  • To:
  • Subject: Re: [isn-discuss] Re: Interesting uses for isn
  • Date: Fri, 30 Nov 2007 17:57:45 -0800

Title: Re: [isn-discuss] Re: Interesting uses for isn
Peter -
  The plan is for the information in the zone to remain rooted on the Freenum nameservers, though you (the administrator) have control over many of the fields that are not taken verbatim from the IANA pages.  While there is no specific objection to delegating the data, it doesn't make a lot of sense at the domain (ITAD) level if it is editable by the admin.   In order to delegate, that would have to be done at the zone level, which would mean that it would be possible to control completely the data about the ITAD.  This might be perceived as potentially "bad" since it could allow spoofing.  If the data is kept/logged/filtered through the Freenum pages, then it is less likely that there would be intentional or unintentional data corruption or absence in the future.


At 1:33 PM -0500 2007/11/30, Peter Grace wrote:

Will you be delegating this to the people who host their own isn records?  For instance, I have  Will you also be delegating to me or will you be keeping the directory hosted at freenum?

On Nov 30, 2007 1:07 PM, John Todd < > wrote:

FYI: the new "directory" element is now in the DNS zones for each
<itad> zone.

The new zone should be distributed in the next half-hour or so.  So
far, only four entries, and none of them valid.   Start coding!  :-)

; new format dns entry
o                   IN  TXT "Hyjynx Technology Systems, Inc."
street              IN  TXT "14625 Baltimore Avenue, PMB 170"
localityName        IN  TXT "Laurel"
stateOrProvince     IN  TXT "MD"
postalCode          IN  TXT "20707"
c                   IN  TXT "US"
friendlyCountryName IN  TXT "United States"
tz                  IN  TXT "UTC-0800"
friendlyTimezone    IN  TXT "US/Pacific"
lang                IN  TXT "en"
friendlyLanguage    IN  TXT "English"
email               IN  TXT " "
directory           IN  TXT ""


>Date: Thu, 29 Nov 2007 17:42:24 -0800
>From: John Todd <>
>Subject: [isn-discuss] Re: Interesting uses for isn
>John -
>   OK, I've requested that "directory" be the record identifier for
>that URL, and hopefully it will be running shortly.
>   I like the search criteria for an automated tool.  Is there any
>type of search syntax that can be used from a pre-existing platform
>like LDAP?
>Here are some obvious search tools:
>postal address
>email address (full)
>  - regular expressions/wildcards?
>  - limits on returned queries?
>  - security model?
>At 7:06 PM -0500 2007/11/29, 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.

Archive powered by MHonArc 2.6.16.

Top of Page