What is special with this book? It is standard Cisco press book.
IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
11–20 of 64 posts
Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#12Earlier quoted context omitted.
I’ve often wondered if ipv6s less human readable addresses is the primary cause. I dread using and interacting with ipv6, compared to ipv4. Sure ipv6 solves a lot of scaling challenges, but it is so much harder to grock at first glance.
Address abbreviation helps a bunch. IPv6 (not an expert, but I’m in a class right now!) suffers from severe 2nd system syndrome: it overhauls DHCP in a totally convoluted way, overhauls so much of how the IP layer works, etc. It really is a mess.
I think it would have been better to label everything that DHCPv6 covers with an entirely new name. Its functionality is fine for what it’s tasked to do, and much of the confusion I’d argue stems from those who (think they) know IPv4 trying to map their understanding to IPv6 unmodified.
Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#13I first learned ipv6 22 years ago when I did my CCNP. Since then we've been two years away from migration every year.
I have had native IPv6 from my ISP for 11 years now.
Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#14Both of my ISPs offer IPv6 gateways. I set them up and visited several IP6 websites. I crypto exchange I use frequently, Bittrex, allows to whitelist an IP address. Since I have a static IPv4, I did so. Problem is, my request to bittrex always goes out the IP6 gateway and Bittrex does not recognize me. I had to shut down the IP6 gateway to get into the account.
You have a static ip4 but not a static ip6? Or does bittrex not allow whitelisting an ip6?
Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#15I first learned ipv6 22 years ago when I did my CCNP. Since then we've been two years away from migration every year.
Over 30% global adoption for google users, to the extent of having a public ipv6 address and using ipv6 preferentially:
Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#16What is special with this book? It is standard Cisco press book.
No one is talking about it, the rest of the comments are unrelated war stories about IPv6 deployment with have nothing to do with TFA.
Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#17Earlier quoted context omitted.
My home ISP gives me an IPv6 address as well. Much of the internal infra that I use at work has AAAA records in our local DNS. I feel comfortable saying IPv6 is here.
I wish Verizon would start offering IPV6 across their wireline footprint.
They are. I was part of the test rollout of IPv6 when I lived in Richmond, VA last year. It worked flawlessly so I'd assume they should be set for a greater rollout sooner rather than later.
Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#18Earlier quoted context omitted.
I wish Verizon would start offering IPV6 across their wireline footprint.
They are. I was part of the test rollout of IPv6 when I lived in Richmond, VA last year. It worked flawlessly so I'd assume they should be set for a greater rollout sooner rather than later.
When was that? It's been "coming soon" on Verizon's own FAQ[1] for almost half a decade now. I'm in one of the major MSAs along the eastern megalopolis, and there's no IPv6 here.
[1]: https://web.archive.org/web/20171220092540/https://www.veriz...
Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#19I first learned ipv6 22 years ago when I did my CCNP. Since then we've been two years away from migration every year.
I’ve often wondered if ipv6s less human readable addresses is the primary cause. I dread using and interacting with ipv6, compared to ipv4. Sure ipv6 solves a lot of scaling challenges, but it is so much harder to grock at first glance.
It's a silly bikeshed, but I wish they'd gone for hyphens as separators rather than colons. There's something about
[abcd-ef12-3456-7890-abcd-ef12-3456-7890]
[abcd:ef12:3456:7890:abcd:ef12:3456:7890]Re: IPv6 Fundamentals: A Straightforward Approach to Understanding IPv6, 2nd Edition
#20I first learned ipv6 22 years ago when I did my CCNP. Since then we've been two years away from migration every year.
I’ve often wondered if ipv6s less human readable addresses is the primary cause. I dread using and interacting with ipv6, compared to ipv4. Sure ipv6 solves a lot of scaling challenges, but it is so much harder to grock at first glance.
Many of the "IPv6-isms" come from the fact that renumbering networks is a big PITA and so IPv6 was built with the pipe dream of "change the config on the router and the entire network renumbers itself", like the flick of a switch. It was optimised for the least used case. IMO they should have just increased the address bit size to 128 and be done with it.
One of my own annoyances is the fact that local subnets have to be /64's (you can make smaller subnets but it breaks certain things) and ISP's are supposed to deliver a /48 or /56 to subscribers but some ISP's will only hand one /64. So if you want to create 2 separate networks in your home you're screwed.