I could see it making sense to move management gear to IPv6 eventually, but the only real reason that I could see why I'd want to do that would be if I wasn't using IPv4 for management at all... and it's probably not something that's going to be in widespread use any time soon.
Currently, the vast majority of our device management is on private IPv4 addresses, and I like it that way. If for some reason, I needed to have management interfaces on public IPs, then I would certainly want to start looking at using IPv6 for that, but at this point, I really have no desire to put things on public IPs that don't need to be, anyway. On Thu, Oct 19, 2017 at 6:34 PM, George Skorup <george.sko...@cbcast.com> wrote: > IMO, dual stack or forget IPv6 entirely. > > On 10/19/2017 6:20 PM, Forrest Christian (List Account) wrote: > > So, after the response to me mentioning https:// for device management, I > figured I'd ask about the following: > > How about IPv6? It's on my list as well to look at... Does anyone see > any real need for having your management gear on IPv6 instead of IPv4, at > least in the near term? > > -- > *Forrest Christian* *CEO**, PacketFlux Technologies, Inc.* > Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 > forre...@imach.com | http://www.packetflux.com > <http://www.linkedin.com/in/fwchristian> <http://facebook.com/packetflux> > <http://twitter.com/@packetflux> > > >
