Thanks, LinkedIn. Whenever a popular site enables IPv6, that's a bit less traffic for ISPs' carrier-grade NAT equipment to carry, so more resources can be focused on longer-term solutions.
Note that the screenshot of the developer console actually demonstrates a formatting bug; it should say "[2620:109:c006:102::6cae:281]:443" instead of "2620:109:c006:102::6cae:281:443". I think this was just recently fixed in Chrome 37.
3 comments
[ 3.9 ms ] story [ 16.5 ms ] threadNote that the screenshot of the developer console actually demonstrates a formatting bug; it should say "[2620:109:c006:102::6cae:281]:443" instead of "2620:109:c006:102::6cae:281:443". I think this was just recently fixed in Chrome 37.
http://www.verizon.com/Support/Residential/Internet/HighSpee...