I don't understand how much time and energy is being put into the discussion 
about keeping vintage IP alive.
This time and energy would be better off spent in just deploying v6.
It's just not that difficult. You just need to develop a stepwise approach. A 
one-shot would probably fail.

-- Alex


> Am 11.06.2016 um 22:35 schrieb Gert Doering <[email protected]>:
>
> Hi,
>
>> On Sat, Jun 11, 2016 at 10:14:11PM +0300, NTX NOC wrote:
>> About IPv6 - still now in Russia there are no Home ISPs who gives IPv6
>> by default to customers. Nobody wants it, nobody needs it.
>
> The "nobody needs it" is a misconception.  Direct your energy there to
> make people understand that IPv4 is game over.
>
> Gert Doering
>        -- NetMaster
> --
> have you enabled IPv6 on something today...?
>
> SpaceNet AG                        Vorstand: Sebastian v. Bomhard
> Joseph-Dollinger-Bogen 14          Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                   HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444           USt-IdNr.: DE813185279
> <totemomail_info.html>


This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, you 
must not copy this message or attachment or disclose the contents to any other 
person. If you have received this transmission in error, please notify the 
sender immediately and delete the message and any attachment from your system. 
Merck KGaA, Darmstadt, Germany and any of its subsidiaries do not accept 
liability for any omissions or errors in this message which may arise as a 
result of E-Mail-transmission or for damages resulting from any unauthorized 
changes of the content of this message and any attachment thereto. Merck KGaA, 
Darmstadt, Germany and any of its subsidiaries do not guarantee that this 
message is free of viruses and does not accept liability for any damages caused 
by any virus transmitted therewith.



Click http://www.merckgroup.com/disclaimer to access the German, French, 
Spanish and Portuguese versions of this disclaimer.

Reply via email to