It won't be *hard*, but it won't be easy either. Since .us domains require
Nexus information there'll be an additional step to include (or more form
data) as part of the registration process for .us names (akin to the
differences with .ca with their requirements and different contact set)
Charles Daminato
OpenSRS Product Manager
Tucows Inc. - chuck@tucows.com
> -----Original Message-----
> From: owner-discuss-list@opensrs.org
> [mailto:owner-discuss-list@opensrs.org]On Behalf Of Mike Allen
> Sent: April 17, 2002 9:40 AM
> To: Scott Allan; discuss-list@opensrs.org
> Subject: Re: .US Impl.
>
>
> Thanks Scott. However I was hoping you might let us in on how
> much might be
> involved for our current custom scripts. Since you said the code would be
> available later this week, does that mean it will not be a simple
> procedure
> such as adding "us" to the domain support string etc... ?
>
>
> --
> Mike Allen, 4CheapDomains.Net
> discusslist@4CheapDomains.Net
> http://www.4CheapDomains.Net
>
> ----- Original Message -----
> From: "Scott Allan" <sallan@opensrs.org>
> To: "Mike Allen" <discusslist@4cheapdomains.net>;
> <discuss-list@opensrs.org>
> Sent: Wednesday, April 17, 2002 7:25 AM
> Subject: Re: .US Impl.
>
>
> > At 01:11 PM 4/16/02 -0500, Mike Allen wrote:
> > >I saw a question posted a few weeks ago, but I haven't found a firm
> > >response for the .US implementation from Chuck or OpenSRS in the
> archives.
> > >
> > >Someone asked if it was going to be a simple procedure to add
> .US to the
> > >CGI code (IE: just adding "us" to the available domain extensions etc.)
> > >
> > >Or if their is going to be something "Drastic" happen in the scripts.
> > >
> >
> >
> > The actual .us real-time code will be available Thursday or Friday this
> > week. You will be able to test against horizon.
> >
> > Regards,
> >
> > sA
> >
> > Scott Allan
> > Director OpenSRS
> > sallan@opensrs.org
> >
> >
>
This archive was generated by hypermail 2.1.3 : Tue Oct 19 2004 - 23:37:09 EDT