Well, I'm not 100% on the .info thing (heck, I can't do EVERYthing
*grin*), but I'll try here...
Charles Daminato
TUCOWS Product Manager
[EMAIL PROTECTED]
On Fri, 17 Aug 2001, Kai Schaetzl wrote:
> > My advice is to create a handle for the registrant to use as registrant ID
> > and then one for yourself to use as admin and tech (if needed). This would
> > be the easiest solution. I believe that you will be able to edit contacts
> > down the road (this could likely not happen til November/December) but it is
> > in the cards at sometime.
> >
>
> Looking at the new interface I have the following questions/suggestions:
>
> 1. I would like to have pre-loaded tech and bill contacts. (sunrise)
>
Since you can create contacts, you basically create once, and use the
handle over and over again :)
> 2. I would like to have nameservers pre-loaded in Landrush (like it is in
> Sunrise).
>
Hrm... not tooooo sure why this didn't happen - possibly timelines,
possibly due to the fact that the .info registry requires all nameservers
be 'registered' to have domains associated with them (akin to ccTLD
nameservers at VeriSign registry). No worries - we've done out best to
prepopulate at the registry - you'll still have to pick each time for this
:(
> 3. Related, I can now load a profile for Sunrise (which is almost
> over) while I can't for Landrush (which will carry a much bigger
> domain load). Are you planning in changing this? You could simply use
> the same form like for Sunrise but display all the necessary contact
> fields (empty if not possible to fill them) instead of the Contact ID.
>
Due to the handles, I think that overrides the need to use profiles - but
this is a good idea. I'll see if I can't noogie someone into submission
:)
> 4. So, now we need 1 username and 2 passwords for registering a
> domain? And some more passwords for the contacts? Can't we have it
> even more complicated? How is this going to work when it comes to
> actually managing domains? We then need FOUR words (domain, username,
> 2 passwords) to get to a single domain and won't even be able to
> change contact data because these are protected by their own
> passwords. Don't you fear that many users will simply loose that
> information? I understand that you probably did not have any other way
> to interface with Afilias but I feel lots of trouble ahead for us
> because of this over-protection for any single domain.
>
Well - there's the OpenSRS management password. Then there's the registry
mandated Registrant password. And the registry mandated contact
passwords. This is the different between a thin registry (like VeriSign)
and a thick registry (although, Nominet and CIRA are thick <pardon the
pun> but we managed to *hide* this). Don't you love handles?
Don't you guys WANT handles? ;)
> 5. I would like to pre-configure "save" instead of "Register now" for all
> domain reg forms.
>
I'll have to ask about this...
> 5. I would like to pre-configure "Renew automatically" for all domain
> reg forms. It's so easy to overlook this and now we have some domains
> registered without this and most as auto-renew. I hope this doesn't
> create any problems when renewal time comes, all other registries we
> do direct business with just auto-renew if you don't cancel two or
> four weeks before expiration and this is fine.
>
This is more of a system wide enhancement - due to the strict timelines,
and realtime registrations (where the features will be around and count
more) looming, we have to allocate resources where we can. Still, I'll
see if the noogie-ing will still work here :)
>
> Kai
>
> --
>
> Kai Sch�tzl, Berlin, Germany
> Get your web at Conactive Internet Services: http://www.conactive.com
> IE-Center: http://ie5.de & http://msie.winware.org
> ClubWin - Help for Windows Users: http://www.clubwin.com
>
>
>
>
