5 ms·
It seems that this article is missing the forest for the trees. The biggest improvement will come not from the raw speed but from the entire IPv6 eco-system. Fo
by teleforce 4y ago
It seems that this article is missing the forest for the trees. The biggest improvement will come not from the raw speed but from the entire IPv6 eco-system. For example, the new segment routing for IPv6 or SRv6 should improve the Quality of Service (QoS) for examples bandwidth, delay and jitter by having control at the edge. This is unlike MPLS where the control is done in the core itself and that's why MPLS is called layer 2.5 because it's not truly native IP layer or layer 3. This new approach of networking is considered as IP 2.0 [1].
[1]SRv6 Network Programming: Ushering in a New Era of IP Network:
https://www.routledge.com/SRv6-Network-Programming-Ushering-in-a-New-Era-of-IP-Networks/Li-Hu-Li/p/book/9781032016245 https://www.routledge.com/SRv6-Network-Programming-Ushering-...
- virtuallynathan 4y agoSadly not much stuff supports SRv6, and I'm not aware of many deployments.
- kazen44 4y agoalso, SRv6 in my opinion, is just a mess of security holes [0] and reinventing the same architecture over and over again while it is far more cumbersome to implement in hardware compared to simple MPLS LSP lookups.[1] [0] https://mailarchive.ietf.org/arch/msg/v6ops/GbWiie-bjQ_Bp1JKB1PlDh_fPdc/ https://mailarchive.ietf.org/arch/msg/v6ops/GbWiie-bjQ_Bp1JK... [1] https://packetpushers.net/srx6-snake-oil-or-salvation/ https://packetpushers.net/srx6-snake-oil-or-salvation/
- iso1631 4y agoA poor link - a book written by Huwaei doesn't scream "This is a widely used standard" Wikipedia would be a far better link, as it has links to RFCs, Cisco, Juniper Arista etc pages on it, and generally lets normal people who likely haven't heard of it read about it
- teleforce 4y agoSheesh, it take real guts to dismiss a book written by engineers who themselves directly involved in coming up with open industry networking standards, and currently working with arguably the biggest networking and communication company in the world. This take the idiom of "judge a book by its cover" to a whole new level.
- fach 4y agoThere has been a long history of Huawei stealing IP as well as generating less than useful drafts/standards in the IETF. There are very real reasons to judge this book by its cover.
- teleforce 4y agoSorry to be blunt, but there is a real reason the idiom existed for several hundred years. Perhaps you should read the book so we can have more civilized discussions?
- iso1631 4y agoOr perhaps you could link to a wider range of literature rather than try to get people to buy a $100 book
- teleforce 4y agoThat's fair enough but to simply dismissed a book by the fact that it's written by some qualified and professional company engineers is not acceptable. To be honest there are only two books on segment routing at the moment both are over $100, just trying to be helpful on the book because the recommended one is what I have. Here is the main website for segment routing for the IETF documents, software, papers, etc: https://www.segment-routing.net/ https://www.segment-routing.net/
- robjs 4y agoSRv6 is not going to transform the quality of experience/quality of service that you see from Internet applications. Traffic engineering technologies like this (MPLS-based, IP-based, emulated circuit based...) are used inside networks to select paths through them, this has been done for many years, and the segment routing data-plane - whether it be MPLS or IPv6, is a different realisation of how to achieve that path selection through a network. There are networks that have done this traffic engineering using IP encapsulation for many years. The whole "IP 2.0" presumption that appears to be being made here is that suddenly some external traffic source will be able to select a route through someone else's network -- but this just isn't the commercial reality. Some more performant paths are going to have costs associated with them (even if it's just to build more capacity), so there is going to be a cost of choosing that route through the network. That cost is going to need to be covered somewhere - so you are very unlikely to actually be able to get to choosing a path without some commercial contract. Guess what? We've already had those -- they just tend to use the DSCP bits to indicate what the traffic class, and hence associated requested SLO is - not an explicitly chosen path. Equally, let's think about how this would even work - if you are going to choose a path through the network to get better QoS, you're going to need to know something about what IDs to use, which implies knowledge of the topology. Inter-domain topology exposure is going to /significantly/ increase the complexity and fragility of inter-domain routing -- there are reasons that we don't run a global link-state protocol :-) In conclusion - I think this is hype with little technical justification, and is unlikely to have any different impact than other intra-domain traffic engineering that the industry has been running for many years.
- teleforce 4y agoYes sure MPLS works as combustion engines work as long we can remember, but it's not stopping EV as a new contender as the near future vehicle platform whether we like it or not. Now we have hybrid MPLS or SR-MPLS as a stopgap measure similar to what we have now with PHEV, etc. Personally I think the networking industry has already learned their mistakes from the ATM days and hopefully SRv6 will take off for better and more effective IP based networking.
- robjs 4y ago