4 ms·
The document in question is only accessible for ITU members, but I found an accessible source discussing Huawei's proposal: https://www.internetsociety.org/reso
by jeroenhd 6y ago
The document in question is only accessible for ITU members, but I found an accessible source discussing Huawei's proposal: https://www.internetsociety.org/resources/doc/2020/discussion-paper-an-analysis-of-the-new-ip-proposal-to-the-itu-t/ https://www.internetsociety.org/resources/doc/2020/discussio...
Personally, I would not trust anything Huawei produces because of their history of design flaws and bad software practices, as well as their ties to the Chinese government. However, I do see value in reworking some systems, such as BGP and DNS, which have been patched with optional additions to compensate for the trusting nature of its designers back when ARPAnet was small and contained little reason to execute hijacks of resources.
Protections for existing protocols are available though, so instead of reworking protocols and creating telecom-only protocols, perhaps enforcing certain features (BGP security, DNSSEC, etc.) for a provider to be able to name their service "5G" (or "6G" or whatever the next standard is) to make companies give a damn about security. The same tactic can also enforce proper filtering to prevent spoofed phone calls on the backbone that American wireless carriers seem to be so awful at.
- deleted 6y ago[deleted]
- C1sc0cat 6y agoNot sure why the ITU isn't it another body the ratifies RFC's Might well use lobbying of smaller ITU member nations to try and get this through. Oh all that debt for that port we built as part of the belt and road. And the optics of China putting pressure on the WHO in the early stages of the pandemic not looking good.
- xster 6y ago> their history of design flaws and bad software practices Do you have references to what you're referring to?
- noisem4ker 6y agoFrom my browsing history: https://www.theregister.co.uk/2019/03/28/hcsec_huawei_oversight_board_savaging_annual_report/ https://www.theregister.co.uk/2019/03/28/hcsec_huawei_oversi... You can also search this site for "huawei". Almost none of the submissions paint them in a good light.
- jeroenhd 6y agoI don't have the exact links available right now but my position comes from claimed "backdoors" in their software and hardware. Research found no backdoors, but all reported vulnerabilities were due to unsafe coding practices, many many different version of the same library being reused across the software of their devices with many of those versions being outdated and just generally a crummy job at coding. There was very little malice found, only bad practices. This was compared to vendors like Cisco where secret passwords and backdoors were hidden obfuscated in their code, which can only mean the company intended for the backdoor to be there. Personally, I'd buy Huawei before Cisco given that incompetence is easier to forgive than straight-out malice in my opinion, but the conclusion remains that Huawei software isn't always up to snuff which can be a problem when you're trying to push a replacement for the core of the internet for your software.
- gigatexal 6y agoCall me a Xenophobe but the Chinese connections to Huawei are sketchy but perhaps with international involvement we can make it a good rework of the network stack. Is there any opportunity for input from outsiders or is this a take-it-or-leave-it thing?
- nix23 6y agoThat has nothing to do with xenophobic, but if you really trust china/russia/us you should probably learn from the past, they have their own agenda and not a single point of it has something to do with your privacy or security. And to be honest, china can give a really big shit about 'international' they are the producers of goods for the world and or payed them self into other country's, so its take it or leave it, and Huawei has the best router's for that new shit ;)
- dang 6y agoWe've changed the URL from https://www.europarl.europa.eu/doceo/document/E-9-2020-002042-ASW_EN.html https://www.europarl.europa.eu/doceo/document/E-9-2020-00204... to that one, which has a lot more information. Thanks!