[Info-vax] The continued ham-stringing of IPsec/VMS - Cui Bono? - TUDs - Bobby Ewing
Richard Maher
maher_rj at hotspamnotmail.com
Tue Oct 27 18:28:38 EDT 2009
Hi Bob,
"Bob Koehler" <koehler at eisner.nospam.encompasserve.org> wrote in message
news:KTdIuBVjwBNe at eisner.encompasserve.org...
> In article <hc05rh$c4f$1 at news-01.bur.connect.com.au>, "Richard Maher"
<maher_rj at hotspamnotmail.com> writes:
> >
> > So while it's great to see IPsec doing a Bobby Ewing and getting to live
> > another day, I just cannot understand how it could possibly take another
12
> > months to certify code that is already there, and will already have
shipped
> > in H1 2010 with TCP/IP 5.7.
> >
> > Can someone please explain to me what obstacles are preventing IPsec
from
> > being supported in H1 2010 with VMS 8.4?
>
> I don't work for HP, but testing and certification of reliable code
> across a great many hardware platforms takes time. I would not like
> to see VMS Engineering start cutting corners on testing.
>
So which corners would be cut by certifying IPsec with VMS 8.4 TCP/IP 5.7
Bob? Please tell us, and do let VMS know that you personally think it
imprudent to ship the whole 8.4 before H2 2010! Perhaps Bob says "A big tick
for the whole of the operating system and all of TCP/IP services (just not
the IPsec bit) across a great many hardware platforms"?
Or if we can put your bullshit inferences, FUD, and spurious claims to the
high moral ground to one side for the moment and look at the facts then
that'd be useful. IPsec was originally scheduled for 8.3 and the EAK has
been available for about two years. The code will be shipping with TCP/IP
services 5.7 in VMS 8.4 regardless. Thanks to Tequila delays VMS Engineering
has had more than ample time to test, regression-test, and retest all of VMS
umpteen times over! Just how long exactly does Bob say it takes to test &
certify TCP/IP services? I'm certainly interested that nobody else finds 12
months excessive :-(
Or perhaps it is also imprudent to ship untested and uncertified IPsec code
within TCP/IP services in the first place? Could be a time-bomb Bob! I think
you should demand the removal of this flakey, untried & untested IPsec code
before you'll accept shipment of VMS 8.4.
Regards Richard Maher
PS. So it takes HP twelve bloody months just to test a "new" version of
TCP/IP with functionality that every other OS has had for years? No wonder
such a bloated, cumbersome, and unresponsive company went down the toilet
:-( Either that or the black-hand of the IMM team is once again in action
nobbling any racket they don't control.
More information about the Info-vax
mailing list