This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/db-wg@ripe.net/
Ripe change to whois
- Previous message (by thread): Ripe change to whois
- Next message (by thread): Ripe change to whois
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Joao Luis Silva Damas
joao at ripe.net
Mon Nov 30 14:17:54 CET 1998
Dear Hank, May be (or may be not) the "human engineering aspects" were discussed enough but, please, if things like this affect your work so much, get into the db-wg mailing list and give your input. The TLD wg was also involved in this and they were actually very much looking forward to have this mechanism in place. If you still feel that "This needs to be rectified" you can discuss this with the community, although it would have been better to discuss all this when the design was proposed instead of going around the loop again (which, of course, we'll do if users want to). I'll wait and listen. Regards, Joao Hank Nussbacher <hank at ibm.net.il> writes: * At 01:01 PM 11/30/98 +0100, Joao Luis Silva Damas wrote: * * Yes, that may be all correct - from a techno standpoint. What I am * stressing is the human engineering aspect. Up till now, thousands of hits * are sent to the whois.ripe.net every month to determine whether a domain * exists or not. Users have been doing this for years. Suddenly, the output * is different and they do not realize it. I highly doubt that the human * engineering aspect was discussed or analyzed to any extent in the DB WG. -H * ank *
- Previous message (by thread): Ripe change to whois
- Next message (by thread): Ripe change to whois
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ db-wg Archives ]