Hi,
On Mon, Apr 13, 2015 at 11:31:57PM +0200, Jens Link wrote:
I told my first customer about Y2k in 1980. He called last week. If
anyone of you speaks Cobol the customer is paying $large_amount per
hour for fixing his problems.
With IPv6 there is no fixed date but I will happen too.
On 14 Apr 2015, at 08:42, Gert Doering g...@space.net wrote:
Hi,
On Mon, Apr 13, 2015 at 11:31:57PM +0200, Jens Link wrote:
I told my first customer about Y2k in 1980. He called last week. If
anyone of you speaks Cobol the customer is paying $large_amount per
hour for fixing his
Hi Phil and list,
Phil Mayers p.may...@imperial.ac.uk writes:
On 13/04/15 09:55, Benedikt Stockebrand wrote:
Which is a major effort in some environments because---contrary to what
Nick wrote---pretty much anyone involved needs to be familiarized with
IPv6. The reason here is that if there
Jens Hoffmann j...@bofh.de writes:
PS: SCNR: English is not part of the unions description of my job.
They didn't have a job. They trained to get one.
Jens
--
| Foelderichstr. 40 | 13595 Berlin, Germany
Jared Mauch ja...@puck.nether.net writes:
You have at least two addresses to configure, which leads to two DNS
records, two services to be monitored, more firewall rules, ... And in
the end more things to document.
This sure is true in an environment where humans are still the gating
Benedikt Stockebrand b...@stepladder-it.com writes:
And yes, back in 95 there were allegedly people testing the hardware
they bought for being year 2000 compliant:-)
Back in '99 my employer send me to an Oracle training. I do not remember
much about Oracle but I do remember one quote from the
Ted Mittelstaedt t...@ipinc.net writes:
sorry for the delayed answer. I was quite busy doing non IPv6 stuff ;-)
Kind of like you drafted Billy Joe Bob from Hayseed to troubleshoot your
2015 Chevy Volt and it extended the time troubleshooting because he's
still looking for the carburetor.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Am 13.04.15 um 22:51 schrieb Jens Link:
I think the worst thing I've said was learn enough english to
understand the documentation.
Das ist nicht Teil der tariflichen Arbeitsplatzbeschreibung.
Cheers,
Jens
PS: SCNR: English is not part
Hi Andy and list,
Andy Davidson a...@nosignal.org writes:
This is a strange question, but I think as a consultant I would want
to design a rollout methodology that made that overhead (cost) as
close to zero for your customer as possible.
that depends; in some cases you're far more interested
On 11/04/15 10:27, Nick Hilliard wrote:
Uh, lemme just drop this in here: http://imgur.com/AYbpRG2
;o)
The problem with stage 4 is that it requires that the expertise garnered by
the initial deployment team is spread throughout the rest of the company,
ranging from product development to
On 13/04/15 09:55, Benedikt Stockebrand wrote:
Which is a major effort in some environments because---contrary to what
Nick wrote---pretty much anyone involved needs to be familiarized with
IPv6. The reason here is that if there is any problem once IPv6 is
enabled anywhere, then *all* people
Thus wrote Andy Davidson (a...@nosignal.org):
Stage one - write v6 support requirements into RFP for equipment before you
plan to turn it on. Ideally this will be based on document RIPE-554 and be
part of your buying process already (and have been in this process for at
least the last
On 10/04/2015 21:36, Andy Davidson wrote:
Stage one - [...]
Stage two - [...]
Stage three - [...]
Stage four - utilise your new training and v6 capable edge to roll out
NEW services dual-stack. The incremental cost of adding v6 support to a
NEW rollout when you have to do a bunch of work
On 26 Mar 2015, at 09:04, BERENGUER Christophe
christophe.bereng...@solucom.fr wrote:
For a client, I would like to estimate the work overload for IT operations
team to deploy IPv6 dual stack and for day to day operations.
On the internet, I have found an estimation around 20% of work
On Fri, 3 Apr 2015, Ted Mittelstaedt wrote:
normal hardware refresh cycles is something the Fortune 1000 have.
It's a nice concept but not one universally adopted by everyone else in
the real world. Another one of these is hardware service contracts
That's not universally adopted, either.
The industrial machine was only used as an example to keep the
fools from replying why would anyone want to run Windows XP anymore
There are
still a lot of orgs that run it and run Chrome on it. And a simple
registry tweak gets you all of the patches that MS released for
Windows Embedded for
I know plenty of industrial machines that speak the pre-IP Microsoft
protocols to get G code files into them. Some also depend on the clock
rate of their 486 CPU for timing. Some have a C compiler on disk that
was used to develop the control software they run.
IPv6-enabling these devices is
All of this assumes normal hardware refresh cycles That may be the
case for ordinary office users but I got a million dollar asphalt kiln
attached to a Windows 98 controller with a serial port that says
otherwise.
Just wanting to point out that normal hardware refresh cycles more
often
Op 27 mrt. 2015, om 00:23 heeft Brian E Carpenter
brian.e.carpen...@gmail.com het volgende geschreven:
On 26/03/2015 22:04, BERENGUER Christophe wrote:
Hello everybody,
I work for a consulting firm.
For a client, I would like to estimate the work overload for IT operations
team
Without a detailed look at the client this kind of question falls in the
realm of my kid's story problems in her mathematics book - pretty
sounding things that are utterly divorced from reality.
I will just say this, however:
If you do NOT deploy IPv6 then yes it will save labor. Depending
+christophe.berenguer=solucom...@lists.cluenet.de
ipv6-ops-bounces+christophe.berenguer=solucom...@lists.cluenet.de de la part
de Ted Mittelstaedt t...@ipinc.net
Envoyé : vendredi 27 mars 2015 09:27
À : ipv6-ops@lists.cluenet.de
Objet : Re: Cost of IPv6 for IT operations team
Without a detailed look
The 20% figure is based on an IETF document
Which one? We can fix that if people think it's wrong.
(This comes just too late for yesterday's v6ops meeting
at the IETF in Dallas.)
Regards
Brian
Cedex
De : Brian E Carpenter brian.e.carpen...@gmail.com
Envoyé : vendredi 27 mars 2015 13:21
À : BERENGUER Christophe
Cc : Ted Mittelstaedt; ipv6-ops@lists.cluenet.de
Objet : Re: Cost of IPv6 for IT operations team
The 20% figure is based on an IETF
On 26/03/15 09:04, BERENGUER Christophe wrote:
Hello everybody,
I work for a consulting firm.
For a client, I would like to estimate the work overload for IT
operations team to deploy IPv6 dual stack and for day to day operations.
On the internet, I have found an estimation around 20% of
2015 13:21
À : BERENGUER Christophe
Cc : Ted Mittelstaedt; ipv6-ops@lists.cluenet.de
Objet : Re: Cost of IPv6 for IT operations team
The 20% figure is based on an IETF document
Which one? We can fix that if people think it's wrong.
(This comes just too late for yesterday's v6ops meeting
I don't think that having things in the mix extends troubleshooting.
My experience is that problems generally fall into 2 buckets:
1) Textbook ones (mistyped IP address, overload that's readily visible
if they had looked at the reports, or like you said full hard disk)
The time-suck in
Hello everybody,
I work for a consulting firm.
For a client, I would like to estimate the work overload for IT operations team
to deploy IPv6 dual stack and for day to day operations.
On the internet, I have found an estimation around 20% of work overload for the
run phase. But if you have
Hi,
Deployment work overload could be 5%.
For deployment of dual stack, you should minimise work overload by:
- taking advantage of normal refresh cycles and bundle enabling of dual
stack into the refresh or deployment of new management systems, procedures,
and services
- picking low hanging
On 26/03/2015 22:04, BERENGUER Christophe wrote:
Hello everybody,
I work for a consulting firm.
For a client, I would like to estimate the work overload for IT operations
team to deploy IPv6 dual stack and for day to day operations.
On the internet, I have found an estimation
29 matches
Mail list logo
