I am not taking about a big imaginary company. I am taking about NSI and this specific case. Regards, as On 29 Mar 2012, at 00:55, Joseph Snyder wrote:
I agree, but in a big company it generally would cost at least 10s of thousands of dollars just for training alone. The time away from the phones that would have to be covered would exceed that. Let's say you had 8000 phone staff and they were getting $10/be and training took an hour. That is 80k coverage expenses alone. For a large company I would expect a project budget of at least 250k minimal. And probably more if the company exceeds 50,000 employees.
Arturo Servin <arturo.servin@gmail.com> wrote:
Another reason to not use them.
Seriusly, if they cannot expend some thousands of dollars (because it shouldn't be more than that) in "touching code, (hopefully) testing that code, deploying it, training customer support staff to answer questions, updating documentation, etc." I cannot take them as a serious provider for my names.
Regards, .as
On 28 Mar 2012, at 21:16, John T. Yocum wrote:
On 3/28/2012 12:13 PM, Carlos Martinez-Cagnazzo wrote:
I'm not convinced. What you mention is real, but the code they need is little more than a regular expression that can be found on Google and a 20-line script for testing lames. And a couple of weeks of testing, and I think I'm exaggerating.
If they don't want to offer support for it, they can just
put up some
disclaimer.
regards,
Carlos
On 3/28/12 3:55 PM, David Conrad wrote:
On Mar 28, 2012, at 11:47 AM, Carlos Martinez-Cagnazzo wrote:
I'm not a fan of conspiracy theories, but, c'mon. For a provisioning system, an AAAA record is just a fragging string, just like any other DNS record. How difficult to support can it be ?
Of course it is more than a string. It requires touching code, (hopefully) testing that code, deploying it, training customer support staff to answer questions, updating documentation, etc. Presumably Netsol did the cost/benefit analysis and decided the potential increase in revenue generated by the vast hordes of people demanding IPv6 (or the potential lost in revenue as the vast hordes transfer away) didn't justify the expense. Simple business decision.
Regards, -drc
That's assuming their system is sanely or logically designed. It could be a total disaster of code, which makes adding such a feature a major pain.
--John