I over MLS Course Number resentation_id 2001, Cisco Systems, Inc. All rights reserved. atrick Grossetete Cisco Systems Cisco IOS I roduct Manager pgrosset@cisco.com 1
Agenda I Migration Approaches enabled by MLS 6E Approach: I over MLS/Iv4 Conclusions resentation_id 2001, Cisco Systems, Inc. All rights reserved. 2
Key Markets where MLS will facilitate I Migration Service roviders and ISs MLS already used (for MLS VN, for Layer 2 VNs, for TE, for Guaranteed Bandwidth Services ) I offered as yet another service over existing MLS Mutiservice platform Wireless 3G mobile phone networks, DAs, Academic and Research Networks resentation_id 2001, Cisco Systems, Inc. All rights reserved. 3
3G/UMTS Example I Mandated GRS Access Network MLS offers ATM + I + I switching MS Circuit Switch Access Network Applications & Services *) Legacy mobile signaling Network SC Multimedia CSCF R-SGW I Networks Mh Mw Ms CA Mm HSS *) Cx S Domain CSCF Gr Mg Gi Mr Gi EIR IM Domain MRF Gf TE MT BSS/GRAN Gb Gc Gi MGCF T-SGW *) R Um Iu A SGSN GGSN Mc Gi Gn Iu Iu 1 TE MT UTRAN STN/ MGW MGW Legacy/External R Uu Nb 2 Mc Mc Iu Nc MSC server GMSC server T-SGW *) CS Domain Alternative Access Network CA Applications & Services *) CA D HSS *) Mh C R-SGW *) IM Domain is now a sub-set of the S Domain Signalling Interface Signalling and Data Transfer Interface *) those elements are duplicated for figure layout purpose only, they belong to the same logical element in the reference model resentation_id 2001, Cisco Systems, Inc. All rights reserved. 4
I Migration Approaches Many ways to deliver I services to End Users Many Service roviders have already deployed MLS in their Iv4 backbone for various services MLS/VN, MLS/QoS, MLS/TE, ATM + I switching MLS can be used to facilitate I migration Multiple approaches for I over MLS: Iv4 -to- Tunnels I over Circuit_over_MLS Native I MLS I rovider Edge Router (6E) over MLS resentation_id 2001, Cisco Systems, Inc. All rights reserved. 5
Iv4 -to- Tunnels Dual Stack Iv4-I routers v4 v4 E E I over Iv4 Tunnels E E Iv4 v4 Dual Stack Iv4-I routers Iv4 Enterprise No impact on existing Iv4 or MLS Core ( unaware) Only s are -aware (Dual stack) Mesh of I over Iv4 Tunnels -to- overhead: Iv4 header + MLS header resentation_id 2001, Cisco Systems, Inc. All rights reserved. 6
I over Circuit_over_MLS Circuit_over_MLS (eg. ATM VC, FR VC, Ethernet, ) I routers I I I over ATM/FR/Eth No impact on existing Iv4 or MLS Core ( unaware) Edge MLS Routers need to support Circuit_over_MLS Mesh of Circuit_Over_MLS E-to-E E routers are regular I Routers (V6 over ATM, over FR, over Ethernet, ) resentation_id 2001, Cisco Systems, Inc. All rights reserved. 7
Native MLS Support of I MLS Label Switch aths for I I I I I MLS I I I routers Core Infrastructure requires full Control lane upgrade to V6 Routing in core V6 Label Distribution rotocol in core resentation_id 2001, Cisco Systems, Inc. All rights reserved. 8
Agenda I Migration Approaches enabled by MLS 6E Approach: I over MLS/Iv4 Conclusions resentation_id 2001, Cisco Systems, Inc. All rights reserved. 9
I over MLS rovider Edge Router (6E) Dual 2001:0620:: Stack Iv4-I routers 145.95.0.0 2001:0621:: 192.76.10.0 v4 v4 6E 6E M-iBG sessions V6 Internet Iv4 MLS Core Infrastructure is -unaware Es support Dual Stack/6E I reachability exchanged among Es via i-m-bg I packets transported from E to E inside Iv4 MLS LSs Iv4 MLS 6E 6E v4 2001:0420:: Dual Stack Iv4-I routers 192.254.10.0 resentation_id 2001, Cisco Systems, Inc. All rights reserved. 10
6E Routing/Label Distribution IG or M-BG advertising 2001:0420:: 6E-2 sends M-iBG advertisement to 6E-1 which says: is reachable via BG Next Hop = 192.254.10.17 (6E-2) bind BG label (*) 192.72.170.13 6E-1 IGv4 advertises reachability of 192.254.10.17 6E-2 1 2 192.254.10.17 LDv4 binds label to 192.254.10.17 IG or M-BG advertising (*) The 2 nd label allows operations with enultimate Hop opping (H) (which is typically used in current MLS networks)- it is an Aggregate label resentation_id 2001, Cisco Systems, Inc. All rights reserved. 11
6E Forwarding 2001:0420:: I packet 6E-1 192.72.170.13 6E-2 1 2 192.254.10.17 resentation_id 2001, Cisco Systems, Inc. All rights reserved. 12
6E Forwarding (6E-1) 2001:0420:: I packet 192.72.170.13 6E-1 IGv4/LD label1 to 6E-2 M-BG labelz to 2001:0420:: I packet I Forwarding and Label Imposition: 6E-1 receives an I packet Lookup is done on I prefix Result is: Labelz binded by M-BG to Label1 binded by LD/IGv4 to the Iv4 address of BG Next Hop (6E-2) 6E-2 1 2 192.254.10.17 resentation_id 2001, Cisco Systems, Inc. All rights reserved. 13
6E Forwarding (1) 2001:0420:: I-UNaware MLS Label Switching: I packet 6E-1 1 receives an MLS packet Lookup is done on Label1 Result is Label2 192.72.170.13 IGv4/LD label1 to 6E-2 M-BG labelz to 2001:0420:: I packet 6E-2 1 2 192.254.10.17 IGv4/LD label2 to 6E-2 M-BG labelz to 2001:0420:: I packet resentation_id 2001, Cisco Systems, Inc. All rights reserved. 14
6E Forwarding (2) 2001:0420:: I-UNaware MLS Label Switching: I packet 2 receives an MLS packet Lookup is done on Label2 6E-1 Result includes op label (H) 192.72.170.13 IGv4/LD label1 to 6E-2 M-BG labelz to 2001:0420:: I packet M-BG labelz to 2001:0420:: I packet 6E-2 1 2 192.254.10.17 IGv4/LD label2 to 6E-2 M-BG labelz to 2001:0420:: I packet resentation_id 2001, Cisco Systems, Inc. All rights reserved. 15
6E Forwarding (6E-2) 2001:0420:: MLS Label op and I Forwarding : 6E-2 receives an MLS packet Lookup is done on Labelz I packet 6E-1 Result is: op the label & do I lookup on I destination I packet 192.72.170.13 IGv4/LD label1 to 6E-2 M-BG labelz to 2001:0420:: I packet M-BG labelz to 2001:0420:: I packet 6E-2 1 2 192.254.10.17 IGv4/LD label2 to 6E-2 M-BG labelz to 2001:0420:: I packet resentation_id 2001, Cisco Systems, Inc. All rights reserved. 16
6E Standardisation 6E approach will be an IETF standard soon See <draft-ietf-ngtrans-bgp-tunnel-04.txt> Generic solution for transport of I over any tunnelling technique (including MLS) using M-BG IETF Working Group document, due for WG Last Call resentation_id 2001, Cisco Systems, Inc. All rights reserved. 17
6E Benefits For Ss already running MLS, 6E approach has many benefits: Core Infrastructure needs no upgrade and no config change Upgrade only on the edge (ie upgrade of existing Es to 6E, or add separate 6Es) I supported simultaneously with existing MLS services (MLS v4_vns, QoS, ATM, v4 Internet, ) 6E allows I to be deployed over existing MLS Multiservice infrastructure with marginal operational impact/cost /risk resentation_id 2001, Cisco Systems, Inc. All rights reserved. 18
6E Benefits 2001:0620:: IG M-BG M-iBG sessions IG M-BG 2001:0420:: 145.95.0.0 v4 6E 6E 2001:0621:: 192.76.10.0 v4 IG M-BG 6E Iv4 MLS 6E v4 192.254.10.0 V6 only has a single Routing eer (E) regardless of how many remote s it communicates with No change on a when remote s are added/removed (reachability automatically learnt) No tunnel/ circuit to be configured 6E offers scalable and flexible solution (benefits are analogous to RFC2547bis layer 3 VN solution for Iv4) resentation_id 2001, Cisco Systems, Inc. All rights reserved. 19
6E Benefits 2001:0620:: M-iBG sessions 2001:0420:: 145.95.0.0 6E 6E 2001:0621:: 192.76.10.0 6E Iv4 MLS 6E 192.254.10.0 6E solution can be easily extended to support same VN services for I as currently supported for Iv4 with RFC2457bis (isolation, Internet access, QoS ) resentation_id 2001, Cisco Systems, Inc. All rights reserved. 20
6E Cons 2001:0620:: M-iBG sessions 2001:0420:: 145.95.0.0 v4 6E 6E 2001:0621:: 192.76.10.0 v4 6E Iv4 MLS 6E v4 192.254.10.0 Only makes sense where network already runs MLS Requires knowledge of MLS and BG technologies Requires dual-stack and software upgrade on E (or new E) resentation_id 2001, Cisco Systems, Inc. All rights reserved. 21
Agenda I Migration Approaches enabled by MLS 6E Approach: I over MLS/Iv4 Conclusions resentation_id 2001, Cisco Systems, Inc. All rights reserved. 22
Conclusions I migration does not require MLS But, where MLS is deployed, it enables attractive approaches for I migration 6E is one such I migration approach over MLS which offers I deployment with marginal cost/risk I treated as just another service that can be supported over stable Iv4 MLS core (in addition to Iv4 Internet, MLS Layer 3 VNs, ATM, FR, ) resentation_id 2001, Cisco Systems, Inc. All rights reserved. 23
2001, Cisco Systems, Inc. 24