Recent searches

No recent searches

Search options

Only available when logged in.
toad.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Mastodon server operated by David Troy, a tech pioneer and investigative journalist addressing threats to democracy. Thoughtful participation and discussion welcome.

Administered by:

Server stats:

259
active users

toad.social: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.4.1

#128bit

0 posts0 participants0 posts today
Patrick Mevzek<p><span class="h-card" translate="no"><a href="https://infosec.space/@kkarhan" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>kkarhan</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jschauma</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ryanc</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>0xabad1dea</span></a></span> "still, a <a href="https://framapiaf.org/tags/64bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>64bit</span></a> <a href="https://framapiaf.org/tags/AddresaSpace" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AddresaSpace</span></a> would've been more than sufficient". Yes, the famous "640KB should be enough for everyone". "A <a href="https://framapiaf.org/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128bit</span></a> address space is quite inefficient" Why/where/how inefficient? Do DFZ routers have problems? Is storage SO constrained nowadays that we can't store 128bits values? Or is this again the revenge of "oh my god IPv6 is so difficult, I can't remember all those long addresses like I did in IPv4"?</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://framapiaf.org/@pmevzek" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pmevzek</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jschauma</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ryanc</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>0xabad1dea</span></a></span> still, a <a href="https://infosec.space/tags/64bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>64bit</span></a> <a href="https://infosec.space/tags/AddressSpace" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AddressSpace</span></a> would've been more than sufficient as we can see by the fact that /64 is the default <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> allocation for basically any consumer connection.</p><p>A <a href="https://infosec.space/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128bit</span></a> address space is quite inefficient given we ain't saturating even half of it.</p><p><a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZFS</span></a> does have that problem, abeit <a href="https://infosec.space/tags/Sun" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sun</span></a> engineers at the time expected <a href="https://infosec.space/tags/64bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>64bit</span></a> to be as quickly deprecared as <a href="https://infosec.space/tags/16bin" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>16bin</span></a> and <a href="https://infosec.space/tags/32bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>32bit</span></a>.</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mstdn.jp/@landley" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>landley</span></a></span> <span class="h-card" translate="no"><a href="https://mstdn.social/@jschauma" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jschauma</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@ryanc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ryanc</span></a></span> <span class="h-card" translate="no"><a href="https://infosec.exchange/@0xabad1dea" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>0xabad1dea</span></a></span> yeah, the exhaustion problem would've been shoved back with a <a href="https://infosec.space/tags/64bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>64bit</span></a> or sufficiently delayed by a 40bit number.</p><p>Unless we also hate <a href="https://infosec.space/tags/NAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>NAT</span></a> and expect every device to have a unique static <a href="https://infosec.space/tags/IP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IP</span></a> (which is a <a href="https://infosec.space/tags/privacy" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>privacy</span></a> nightmare at best that <em>"<a href="https://infosec.space/tags/PrivacyExtensions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PrivacyExtensions</span></a>"</em> barely fixed.) </p><ul><li>I mean they could've also gone the <a href="https://infosec.space/tags/DECnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DECnet</span></a> approach and use the <a href="https://infosec.space/tags/EUI48" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EUI48</span></a> / <a href="https://infosec.space/tags/MAC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MAC</span></a>-Address (or <a href="https://infosec.space/tags/EUI64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>EUI64</span></a>) as static addressing system, but that would've made <a href="https://infosec.space/tags/vendors" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vendors</span></a> and not <a href="https://infosec.space/tags/ISPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISPs</span></a> the powerful forces of allocation. (Similar to how technically the <a href="https://infosec.space/tags/ICCID" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ICCID</span></a> dictates <a href="https://infosec.space/tags/GSM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GSM</span></a> / <a href="https://infosec.space/tags/4G" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>4G</span></a> / <a href="https://infosec.space/tags/5G" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>5G</span></a> access and not the <a href="https://infosec.space/tags/IMEI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IMEI</span></a> unless places like Australia ban imported devices.</li></ul> <p>I guess using a <a href="https://infosec.space/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128bit</span></a> address space was inspired by <a href="https://infosec.space/tags/ZFS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ZFS</span></a> doing the same <em>before</em>, as the folks who designed both wanted to design a solution that clearly will outlive them (<em>way harder</em> than COBOL has outlived Grace Hopper)...</p><ul><li>Personally I've only had headaches with <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> because not only do I only have <a href="https://infosec.space/tags/IPv4only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4only</span></a> <a href="https://infosec.space/tags/Internet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Internet</span></a> but my <a href="https://infosec.space/tags/ISP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISP</span></a> refuses to allocate even a singe /64 to me (but has no problem throwing in a free /29 of <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a>'s in with my contract!)and stuff like <a href="https://infosec.space/tags/HurricaneElectric" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HurricaneElectric</span></a> / <a href="https://infosec.space/tags/HEnet" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HEnet</span></a>'s <a href="https://infosec.space/tags/Tunnelbroker" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Tunnelbroker</span></a> fail face first due to <a href="https://infosec.space/tags/Geoblocking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Geoblocking</span></a> and the fact that <a href="https://infosec.space/tags/ASNs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ASNs</span></a> get geolocated, not their <a href="https://infosec.space/tags/PoPs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PoPs</span></a>... </li></ul><p>If I was <span class="h-card" translate="no"><a href="https://social.bund.de/@BNetzA" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>BNetzA</span></a></span> I would've mandated <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DualStack</span></a> and banned <a href="https://infosec.space/tags/CGNAT" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CGNAT</span></a> (or at least the use of CGNAT in <a href="https://infosec.space/tags/RFC1918" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RFC1918</span></a> address spaces) as well as <a href="https://infosec.space/tags/DualStackLite" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DualStackLite</span></a>!</p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://lea.pet/@lea" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>lea</span></a></span> we'd still need to decide upon bit width (I'd recommend <a href="https://infosec.space/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128bit</span></a> to future-proof it!) and have like a <a href="https://infosec.space/tags/JVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>JVM</span></a> as "<a href="https://infosec.space/tags/rubtime" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rubtime</span></a>"-<a href="https://infosec.space/tags/OS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OS</span></a>...</p><p>Granted, <a href="https://infosec.space/tags/Sun" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Sun</span></a> did that already - <em>sort-of</em>...</p><p>On Desktop:<br><a href="https://en.wikipedia.org/wiki/Java_Desktop_System" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.wikipedia.org/wiki/Java_Des</span><span class="invisible">ktop_System</span></a></p><p>And Server:<br><a href="https://wetdry.world/@amycatgirl/112491811180315156" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">wetdry.world/@amycatgirl/11249</span><span class="invisible">1811180315156</span></a></p>
Kevin Karhan :verified:<p><span class="h-card"><a href="https://mstdn.social/@HopelessDemigod" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>HopelessDemigod</span></a></span> <span class="h-card"><a href="https://social.restless.systems/@ncommander" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ncommander</span></a></span> </p><p>That being said <a href="https://mstdn.social/tags/AIX" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AIX</span></a> and the <a href="https://mstdn.social/tags/RS6000" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RS6000</span></a> is as far away from a <a href="https://mstdn.social/tags/consumer" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>consumer</span></a> <a href="https://mstdn.social/tags/PC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PC</span></a> as <a href="https://mstdn.social/tags/zArchitecture" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>zArchitecture</span></a>, <a href="https://mstdn.social/tags/DB2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DB2</span></a> and a lot of other <a href="https://mstdn.social/tags/IBM" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IBM</span></a> products...</p><p>After all <a href="https://mstdn.social/tags/Services" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Services</span></a> make <a href="https://mstdn.social/tags/Software" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Software</span></a>, <br>Software makes <a href="https://mstdn.social/tags/Operating" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Operating</span></a> Systems,<br><a href="https://mstdn.social/tags/OperatingSystems" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OperatingSystems</span></a> make <a href="https://mstdn.social/tags/Hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hardware</span></a>. </p><p>Otherwise noone would deal with <a href="https://mstdn.social/tags/AMD64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>AMD64</span></a> and everyone would've transitioned to <a href="https://mstdn.social/tags/ARM64" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ARM64</span></a> or even <a href="https://mstdn.social/tags/RiscV" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RiscV</span></a> <a href="https://mstdn.social/tags/128Bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128Bit</span></a> ages ago...<br><a href="https://www.youtube.com/watch?v=XzhCGSE7KKw&amp;t=4017s" rel="nofollow noopener" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">youtube.com/watch?v=XzhCGSE7KK</span><span class="invisible">w&amp;t=4017s</span></a></p>
Kevin Karhan :verified:<p><span class="h-card"><a href="https://social.treehouse.systems/@ariadne" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>ariadne</span></a></span> I hope <a href="https://mstdn.social/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128bit</span></a> <a href="https://mstdn.social/tags/RISCV" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RISCV</span></a> will fix that...</p>
Kevin Karhan :verified:<p><span class="h-card"><a href="https://social.jvns.ca/@b0rk" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>b0rk</span></a></span> Personally, I want a native <a href="https://mstdn.social/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128bit</span></a> architecture that doesn't do anything but 128bit...</p>
Kevin Karhan :verified:<p><span class="h-card"><a href="https://peoplemaking.games/@eniko" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>eniko</span></a></span> There is no <a href="https://mstdn.social/tags/128bit" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>128bit</span></a> <a href="https://mstdn.social/tags/ix86" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ix86</span></a> <a href="https://mstdn.social/tags/CPU" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CPU</span></a>, it's not even specified.</p><p>AFAIK only <a href="https://mstdn.social/tags/RISCV" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RISCV</span></a> has an <a href="https://mstdn.social/tags/ISA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ISA</span></a> for 128bit and even that is still in <a href="https://mstdn.social/tags/draft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>draft</span></a> and not finalized with 0 <a href="https://mstdn.social/tags/ASIC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ASIC</span></a>'s produced that implement it.</p>
TrendingLive feeds
About