3 ms·
I hate to be a downer, but nobody even knew about this space until it was mentioned here. I've been a ham for almost 10 years and this is the first I've heard
by jrockway 7y ago
I hate to be a downer, but nobody even knew about this space until it was mentioned here. I've been a ham for almost 10 years and this is the first I've heard of it.
The Internet and ham radio don't mix. The rules of the modern Internet are "encrypt everything and trust nothing." The laws of ham radio are literally "you must not encrypt anything". It wasn't meant to be, unless you want to change the laws in every ITU member state. By the time that's done, we will all be accessing the Hypernet with IPv20 from our personal space stations.
Selling off this IP space to Amazon so that some people can get grants is going to make way better use of this resource than than the ham community ever did.
(I like all the people on the nanog list trying to derail it. "Some of the board members don't have ham licenses!" Not actually a requirement to manage a ham radio organization. Only a requirement to transmit a signal. "There is an antique router configuration out there that creates a peering arrangement between the University of California and Amazon that's not authorized!" Guess what guys, they'll probably shut down the arrangement. They're not going to say "welp, there is no way to fix this, here's your money back Amazon!" The thought that that's a possible outcome is making me laugh. I am sure Amazon can find a transit provider if they need one.)
- nexuist 7y ago> The laws of ham radio are literally "you must not encrypt anything" Wait, really? Why is this the case?
- tesseract 7y agoTo enable enforcement of amateurism.
- pmlnr 7y agoSimilarly why gopher is not encrypted: https://gopher.floodgap.com/gopher/gw.lite?gopher://tilde.team:70/0/~rain1/phlog/20190608-encrypting-gopher.txt https://gopher.floodgap.com/gopher/gw.lite?gopher://tilde.te...
- fragmede 7y agoThe FCC, which has explicit purview over how radio frequencies are used, details the rules for amateur radio in part 97. In particular, "Amateur" is explicitly defined there to not allow commercial interests to use those radio waves. The US government allocated portions of the radio spectrum for use by (licensed) amateurs, kind of like the national parks. I'm not allowed to cut down trees in Yosemite and run my own private road so I can make a shortcut and drive right up to Half Dome. The prohibition against encryption comes from a similar place. If you're looking for privacy, ham radio is not the medium to use. FCC part 97 covers amateur operation (in the US), and the relevant part is §97.309 (4)(b), which states "data emissions using unspecified digital codes must not be transmitted for the purpose of obscuring the meaning of any communication." The intent of the "unspecified digital code" matters. My reading of this is that unspecified codes for authentication are allowed. I've always wanted to build telnet with authentication - if interested, others could to watch what I'm doing, but not be able to impersonate me.
- throwaway2048 7y agoYou've never heard of it because the ARDC has been absolutely abysmal stewards of it, now they get a nice multi-megabuck payday for decades of negligence. Don't count on these "grants" ever actually materializing, count on huge paychecks for the board though.
- nickodell 7y ago>I hate to be a downer, but nobody even knew about this space until it was mentioned here. Speak for yourself. :) >The rules of the modern Internet are "encrypt everything and trust nothing." The laws of ham radio are literally "you must not encrypt anything". It wasn't meant to be, unless you want to change the laws in every ITU member state. More to the point, the regulations around third-party communications [0] mean that this could never be routable from the public Internet. And if 44/8 will never be routable, then what's the point of using public addresses? It could use private network addresses instead. All the same, I find ARDC's response to be high-handed. They refuse to acknowledge that they are selling off what is essentially a public resource. They refuse to believe that others might not trust them to be a responsible steward of ~$50 million. [0]: https://www.law.cornell.edu/cfr/text/47/97.115 https://www.law.cornell.edu/cfr/text/47/97.115
- jrockway 7y ago> They refuse to acknowledge that they are selling off what is essentially a public resource. I think I'm OK with this. Someone decided to ask for a ton of free IP addresses when the Internet was a crazy thing nobody cared about. That person appointed a board of directors to manage the resource. The appointed board then decided "let's turn that valuable resource into money." That's just capitalism. Is it fair that someone buys stock that increases in value 100x? Is it fair that someone is born rich and you're born poor? Not really. But that's the way the world works. If you want to post to a networking mailing list "I don't like the way the world works, it's unfair," I'm totally fine with that. But being mad about who owns what today because you weren't around to claim some land before the gold rush seems irrational to me. These folks got lucky. It appears that they are going to donate 100% of their luck to charity. It's all going to be okay, probably.
- kijin 7y agoI agree. If the ham community has internal disagreements about the sale or the use of the money, they should talk to one another in a courthouse. Meanwhile, let the rest of the world make better use of those millions of IP addresses! It's not like Amazon is going to squat on their new /10. We all know they will soon be available for anyone to use on AWS.
- rb12345 7y ago> "There is an antique router configuration out there that creates a peering arrangement between the University of California and Amazon that's not authorized!" Guess what guys, they'll probably shut down the arrangement. The 44/8 route would never get used for Amazon traffic in any case given that Amazon's BGP advertisments for 44.192.0.0/10 would be more specific than 44.0.0.0/8. In the worst case, the University of California would get inadvertently DDoSed if Amazon suffer routing issues and then retract the /8 route in favour of advertising the remaining 3 /10s they care about.
- defi 7y agoover halve of this giant net uses ips in the affected allocation https://hamnetdb.net/map.cgi https://hamnetdb.net/map.cgi
- rurcliped 7y agoThis didn't come up in https://news.ycombinator.com/item?id=20363705 https://news.ycombinator.com/item?id=20363705 earlier this month. That "FreeBSD - A lesson in poor defaults" post said FreeBSD's OpenSSH port has "The NONE cipher is somewhat of a misfeature, removing the encryption bits and only keeping the data integrity. It allows users to accidentally shoot themselves in the foot pretty easily. The trade-off in performance isn't really worth it either, as the bottlenecks one might experience have a lot more to do with the MAC than the actual encryption." So, when someone uses 44.0.0.0/9 where encryption isn't allowed, and they don't want to create and maintain their own OpenSSH fork, this FreeBSD code might be exactly what they want.