Day 2 summary:
The discussion today was very service provider BGP/ISIS/MPLS focused. It seems that the baseline knowledge necessary is more SP than R&S but having both would be best. This worries me a little bit because in my enterprise experience I work much more with R&S, Data Center & Security. I am going to have to study a lot of service provider scenarios… as you can see below.
We started the day with some really fun SDN and data center discussions. A lot of discussion around overlays: STT, VXLAN & NVGRE as well as fabrics (IE FabricPath). I pushed my thoughts around hybrid SDN models as the best answer which was met with surprisingly little resistance.
INE Scenario 2: ATM service provider moving to a packet switched model.
- Deciding between L2/L3 overlay and VPN technologies
- MPLS L3 vs L2 VPNs, VPLS, GRE, IPSec VPN, VPLS, ATOM (AnyThing Over MPLS)
- BGP RFC 4761 (Kompella) 4762 (Martini) – VPLS L2 transport using Ethernet
- BGP RFC 6624 – VPLS using any L2 protocol
- IPLS RFC draft – L2VPN working group
- ATM to MPLS migration design specifics
- MPLS FRR mechanisms
- MPLS one-hop RSVP-TE tunnels to protect LSP w/ FRR
- Hierarchical MPLS LSPs w/ RFC 3107, MPLSE TE forwarding adjacencies, Inter-are MPLS TE over IP tunnels, Hierarchical LDP
- Seamless MPLS draft
- DiffServ to MPLS TE mapping
- BGP Path Hunting
- BGP Soo
- MPLS VPN CsC (Carrier Supporting Carrier)
- Optimum Route Reflection
- Backscatter traffic collection
- MPLS 6PE