ICANN/GNSO GNSO Email List Archives

[ga]


<<< Chronological Index >>>    <<< Thread Index >>>

[ga] demand for a DNS user's error support function [was Wildcards]

  • To: "Roberto Gaetano" <ploki_xyz@xxxxxxxxxxx>
  • Subject: [ga] demand for a DNS user's error support function [was Wildcards]
  • From: "J-F C. (Jefsey) Morfin" <jefsey@xxxxxxxxxxxxxxxx>
  • Date: Mon, 22 Sep 2003 12:52:29 +0200
  • Cc: ga@xxxxxxxx
  • In-reply-to: <Law15-F60XOq3JkrKdM000200e6@hotmail.com>
  • Sender: owner-ga@xxxxxxxxxxxxxx

Dear Roberto,
Whereas I am an Internet @large member extensively using the wildcard service on my own domain names, chairing an @large users network organization (http://intlnet.org) needing that service as part of its Communnity Information Center architecture, and fully supporting the ccTLD managers using it in similar ways as VeriSign,


Whereas I am an Internet @large Member who proposed three years ago (in 2000) (a) the ".sys" TLD project - documented on the ICANN site to propose pattern matching names support (b)the ".wiz" TLD to experiement IA based naming access support; and (c) having only got as an answer from ICANN a demand of a check of $ 50.000,

Whereas having been formerly twice an @large candidate to the BoD and included urgent needs for DNS innovation in my candidate's priorities,

Whereas having organized an @large users experimentation (http://dot-root.com) to investigate and test DNS development issues in full compliance with the ICANN's call extensively developped in its ICP-3 Document,

Whereas you are the liaison to the ALAC group which claims to represent @large Members in the ICANN organization,

I formally ask ALAC that ICANN demands IAB and IETF to urgently propose the solutions which will permit users to fully integrate, not only wild card, but a real full pattern matching service in their name servers (whatever the solution) using their own database search strategies and possibly IA sollutions, without disrupting the normal functionning of the DNS.

An integrated user's error support functionnality is expected from serious online directory systems. The old age of the DNS is not an alibi for this function to be missing. To the countrary, Harald Halvestrand perfectly documented a list of problems, only show we had 20 years to address and test seriously needs we perfectly known.

I also call on every DNS server developper to tell us the solutions they propose to that urgent need. The use of wildcard is not likely to die. It is today the only way to encapsulate the DNS within upper service layers (DNS+) in the lack of a more current modern DNS.2 version. It is true that its only possible use, as currently enlighted by VeriSign, leads to layer violations. This is what is to be corrected, not the market to be curbed.

I thank you for your understanding and cooperation.
jfc


On 10:29 22/09/03, Roberto Gaetano said:

For your information,

The ICANN BoD mailing list is very busy discussing issues related to the VRSG Sitefinder "service".
The initial action has been, as already posted by Thomas, a request to voluntarily suspend the service.
Following the statement of the IAB, and individual comments from the IETF community, I am expecting (but take it only as a personal opinion) a stronger position in the future.


An interesting scenario has been also evaluated. Suppose that some company is unhappy about VRSG returning something different than NXDOMAIN for a name confusingly similar to an existing trademark, and gets a judge to oblige VRSG to reply accordingly, the practice of dealing with different names in different ways would be openly in violation of the protocol.

Roberto GAETANO
ALAC
ICANN BoD Liaison

_________________________________________________________________
Get MSN 8 Dial-up Internet Service FREE for one month. Limited time offer-- sign up now! http://join.msn.com/?page=dept/dialup






<<< Chronological Index >>>    <<< Thread Index >>>