> At the moment Verisign (the registry) accepts registrations and
> renewals for 1 year increments. Therefore this would require a change
> at the registry level.
Correct.
> In the past when there were problems with transfers and domains had a
> year taken away due to 'interesting policies' Verisign was able to add
> months to registrations to give domain owners time to renew their
> domains, so they do have the technology to add less than 12 months to a
> domain name.
Also correct.
> Now a customer has for example 150 domain names expiring on 150
> different days.
> Which expiration date do we standardize to?
Let the customer decide what day is most convenient to them. The math is
still the same for the registry regardless.
> Or do we give a choice of 4 days eg Jan 15, April 15, July 15, October
> 15 - to coincide with fiscal quarters?
Just as a point of note, I've NEVER worked for a company whose fiscal
quarter ended in the middle of month.
1/1-3/31,4/1-6/30,7/1-9/30,10/1-12/31 seems to be the schedule I've
usually seen, with some occasional variation on which one is actually
"first" in the fiscal year (e.g., my present employer runs 7/1-6/30).
> How do we bill for this?
We = RSP's? However you like.
> do we take the new expiration date, subtract the current expiration
> date, divide that by number of days in the year and multiply by the
> annual renewal fee? Does OpenSRS do the same for our billing? Do we
> have a minimum renewal fee (moving expiration date from October 13 to
> October 15?) results in a minimum renewal fee of $1.00?
I think the logic of:
N = number of days to move an expiration forward (only forward!)
A = annual cost (presently $10.00)
C = (N/365)*A = Cost to change expiration date,
although I could also accept
F = Handling Fee
C = ( (N/365)*A) + F )
D
