2 ms·
This time, I agree - this is very abstract, and reading the summary, intro and some details, I don't know what concrete problem is being solved.
by unethical_ban 6y ago
This time, I agree - this is very abstract, and reading the summary, intro and some details, I don't know what concrete problem is being solved.
- est31 6y agoIt might be related to: https://www.zdnet.com/article/ripe-opposes-chinas-internet-protocols-upgrade-plan/ https://www.zdnet.com/article/ripe-opposes-chinas-internet-p...
- MayeulC 6y agoHahaha, that one could very well be adopted faster than IPv6 if that ever happens. Apart from this, this shouldn't be a a laughing matter. Such a feature could be used for filtering based on origin, protocol and destination. Is that a good thing, or a bad thing? It depends on what is being filtered and the reason. The risk here is that mainstream protocols could appear with the assumption that they won't be filtered across domains. Censorship-resistant protocols should make sure they wouldn't be filtered across domains due to this (basing them on https should be fine for the foreseeable future). "Luckilly", company networks are sometimes worse than countries that censor the net. With such prevalent censorship, developers are incentivized to develop censorship-resistant protocols.
- Arnt 6y agoI don't think it's meant to solve a concrete problem. Just to provide fixed definitions to make some IETF quarrels less painful, by providing semiauthoritative definitions of some words. Which is good. That lets people quarrel about the substance of something instead of digressing into quarreling about what terms mean.