Date: Fri, 2 Jun 2017 15:46:14 -0400 From: "James B. Byrne" <byrnejb@harte-lyne.ca> To: "Jon Radel" <jon@radel.com> Cc: freebsd-questions@harte-lyne.ca Subject: Re: IPv4 to IPv6 Message-ID: <ecc0b96205d3069bc9fce594796bc542.squirrel@webmail.harte-lyne.ca> In-Reply-To: <691d853e-e2f7-b5f3-d281-73511845bd6a@radel.com> References: <74b7b58aa45cc01585338ef2270ccc57.squirrel@webmail.harte-lyne.ca> <691d853e-e2f7-b5f3-d281-73511845bd6a@radel.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, June 2, 2017 11:43, Jon Radel wrote:
> Do you really plan to remove IPv4 from everything other than your SMTP
> and DNS servers? If so, how will your users [assuming you have such]
> reach resources on the IPv4 Internet? Or have I misunderstood?
>
> An orderly migration to being dual-stacked on everything would
> probably be a lot less painful than what I think you're planning.
> While there are possible mechanisms for an IPv6-only client to
> reach resources on the IPv4 Internet, I'm unclear on the benefits
> of bothering with such an architecture.
>
We will be running dual stack for a while, possibly into the next
century. Internally we will move to IPv6 as equipment is replaced or
reconfigured. There seems little point in disturbing that which
already works. Externally, the first services to be IPv6 enabled will
be DNS followed closely by SMTP. Then we will start looking at SSH
and VPN. Finally, we will enable HTTP services on IPv6.
It still strikes me as odd that the ITEF managed to come up with a
replacement addressing scheme that is not zero configuration
compatible with the existing IPv4 one.
--
*** e-Mail is NOT a SECURE channel ***
Do NOT transmit sensitive data via e-Mail
Do NOT open attachments nor follow links sent by e-Mail
James B. Byrne mailto:ByrneJB@Harte-Lyne.ca
Harte & Lyne Limited http://www.harte-lyne.ca
9 Brockley Drive vox: +1 905 561 1241
Hamilton, Ontario fax: +1 905 561 0757
Canada L8E 3C3
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ecc0b96205d3069bc9fce594796bc542.squirrel>