Best explanation and in depth deep dive explanation on design & integrations and implementation of Segment routing concept, Conclusion - Segment routing or MPLS-TE both depends on requirement of our architecture or service provisioning, All technologies such as MPLS-L3-VPN, MPLS-L2-VPN, MPLS-TE, all are equally great and best technologies itself with its own advantages and benefits and applications.... Segment routing is Not enhancement of MPLS but technique of lower overhead of Packet encapsulation transverse over network.
Hi Doan, the idea is about simplification. Nowadays, you can deploy L3 services using EVPN as-well, without the need of traditional way of L3VPN implementation. The latest RFC about EVPN explains the use case with L3VPN services. Anyway, many options to do the same thing, as you mentioned, customers decide which way they are moving forward.
@@leonirhoxha I do agree that not involving yourself with a customer's L3 routing is easier. However I see this works only if customer wishes to have a totally Intranet. For my particular network we still have to host/exchange many routes with our customers. It all comes down to use cases and the danger of just putting a particular technology on to simply protocols shows just one specific scenario. Thanks.
Segment Routing - The best way of explaining new feature of MPLS technology.
Best explanation and in depth deep dive explanation on design & integrations and implementation of Segment routing concept, Conclusion - Segment routing or MPLS-TE both depends on requirement of our architecture or service provisioning, All technologies such as MPLS-L3-VPN, MPLS-L2-VPN, MPLS-TE, all are equally great and best technologies itself with its own advantages and benefits and applications.... Segment routing is Not enhancement of MPLS but technique of lower overhead of Packet encapsulation transverse over network.
This is the way how to explain technology.Thank you
A very instructive presentation! Thanks a lot
Thank you very much. Well said
clear and crispy
Not sure why Cisco is pusing for EVPN only. You need to allow traditional L3 services as well but that's a customer's call.
Hi Doan, the idea is about simplification. Nowadays, you can deploy L3 services using EVPN as-well, without the need of traditional way of L3VPN implementation.
The latest RFC about EVPN explains the use case with L3VPN services. Anyway, many options to do the same thing, as you mentioned, customers decide which way they are moving forward.
@@leonirhoxha I do agree that not involving yourself with a customer's L3 routing is easier. However I see this works only if customer wishes to have a totally Intranet. For my particular network we still have to host/exchange many routes with our customers. It all comes down to use cases and the danger of just putting a particular technology on to simply protocols shows just one specific scenario. Thanks.
@@dmnguye69 Sure, it's a tradeoff between technology and actual business requirements.
cheers.