We will first support IPv6 with our user agents: Android, Windows, and LAN Proxy.
@Mike Schroll: Timeframe for agent support and then resolver support?
Initial support for this is expected to support entering a /64 -- Looking for feedback on whether this works or doesn't work for customers
@Mike: Why only a /64?
@Adam: Some byte limits in our current architecture.
@Mike: Any timeframe for IPV6 support? Is there beta access?
@Adam: No time-frame yet -- but we'll reference this feature request and let you know once we have it available for testing!
@Mike: Are you on a timescale of weeks, months, or years? I am in a trial and this may be a deciding factor.
@Adam: Probably Q3 or Q4 of this year.
@Mike: This is good to hear!
@Adam: We are enterprise and my ISP provided me with /112.
@Jason Wiegel: Not sure why you replied to me, I'm just another customer.
However, a /112 IPv6 prefix breaks many aspects of IPv6. IPv6 subnets should not be smaller than a /64 in most cases. You should get your ISP to allocate you at least a /64. Even Comcast (barely) Business Coax gives out a /56, and their residential gives out a /64!
For some explanation, see: https://etherealmind.com/allocating-64-wasteful-ipv6-not/
@Mike: Any updates on timeframe?
+1 for me! I definitely feel this will become very important in the next 5 years
Any updates on IPv6 support in the last 7 months?