One of my students was watching the Building IPv6 Service Provider Core webinar and wondered whether he should use 6PE or native IPv6 transport:
Could you explain further why it is better to choose 6PE over running IPv6 in the core? I have to implement IPv6 where I work (a small ISP) and need to fully understand why I should choose a certain implementation.
Here’s a short decision tree that should help you make that decision:
Do you already have MPLS in your network?
Yes: Do you use features like MPLS TE or FRR?
Yes: you must use 6PE.
No: you could run IPv6 natively. Do you run BGP (for Internet services) on all core routers?
- No: Don’t change the network design, use 6PE.
- Yes: You could run either native IPv6 or 6PE. Native IPv6 requires IPv6 deployment on all core routers. 6PE needs IPv6 only on PE routers and route reflectors.
No: Are you willing to deploy MPLS?
No: Forget 6PE, use native IPv6.
Yes: Will you deploy IPv6 gradually (only on a few PE-routers)?
- Yes: Introduction of MPLS and 6PE might make sense.
- No: Forget it, doesn't make sense to introduce MPLS just for IPv6
- To get an initial overview of what’s needed to deploy IPv6 in your network, watch the Service Provider IPv6 Introduction or Enterprise IPv6 – the first steps webinar.
- You’ll find IPv6 network design and deployment guidelines in the Building Large IPv6 Service Provider Networks webinar.
- All three webinars are included in the yearly subscription.