> In all reality, virtual expiration dates is the only way a > registrar could implement such a scheme based on current > registry restrictions.
ACK! I can't imagine all the pain and horror we'd get if something went wrong and we misreported expiration dates and invoices went out at different times and things didn't update properly I have a headache just thinking about it... Charles Daminato OpenSRS Product Manager Tucows Inc. - [EMAIL PROTECTED] > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of [EMAIL PROTECTED] > Sent: August 20, 2002 2:43 PM > To: Mike Allen > Cc: erol M; discuss-list > Subject: Re: Moving renewal dates... > > > > > Try thinking of the problem differently --- virtual > expiration dates. The > > > customer would pay $N to have all expiration dates virtually > renewed to > > > allow for one expiration date. This date would be reflected in the > > registrars > > > WHOIS, but not with the registry. According to the registrar > this would be > > > the "official" expiration date, and if payment was not made > at some point > > > down the road the registrar would delete the domain. > > > > Out of the question. They want to see the same date on every record, > > otherwise they do not feel "Secure" about it all and we just > get a tone of > > emails verifying and asking why the who-is doesn't match what > we tell them. > > But that *does* solve your problem of "why the who-is doesn't match what > we tell them". It would match what you tell them. I would suggest > re-reading Erol's statement. In all reality, virtual expiration dates is > the only way a registrar could implement such a scheme based on current > registry restrictions. > >
