TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

The State of IPv6 in 2020

6 点作者 StevePlea将近 5 年前

2 条评论

MilnerRoute将近 5 年前
There&#x27;s a theory that we&#x27;ll know when people have returned to their offices -- because most corporate networks are still running IPv4...<p><a href="https:&#x2F;&#x2F;tech.slashdot.org&#x2F;story&#x2F;20&#x2F;05&#x2F;30&#x2F;0412238&#x2F;ipv6-adoption-hits-32-will-stats-show-how-many-returned-to-the-office" rel="nofollow">https:&#x2F;&#x2F;tech.slashdot.org&#x2F;story&#x2F;20&#x2F;05&#x2F;30&#x2F;0412238&#x2F;ipv6-adopti...</a>
est31将近 5 年前
I get the issues with ipv4 and agree there needs to be a replacement.<p>One of the issues I have with ipv6 is the sheer length of them. You don&#x27;t really want to type&#x2F;copy them manually any more. This isn&#x27;t really due to their nature as 128 bit numbers. It&#x27;s more an issue of how they are being assigned. If we kept the 128 bit addresses, but assigned them more like ipv4 today, we&#x27;d have gotten a much more handleable addressing scheme.<p>E.g. we could have set the first 5 blocks to 0 for the time being and used only the last three until we exhausted them. This would have meant we&#x27;d have more handleable addresses like ::1337:120.43.88.10 and still yield us enough addresses for the forseeable future. We&#x27;d need to do some testing to ensure that all hardware&#x2F;routers&#x2F; etc support the full 128 bit for future extensions, but this is an implementation detail.<p>But you can&#x27;t even address a device in your local network using ipv6 because the numbers are just so long. I don&#x27;t need it to be globally unique. Why not have addresses like ::42 for devices in your local network?
评论 #23384171 未加载