70 likes | 260 Views
CGN Deployment with BGP/MPLS IP VPNs. draft-ietf-opsawg-lsn-deployment-00 IETF84 Vancouver Victor Kuarsingh, Rogers Communications. Baseline. First Presented in BEHAVE at IETF78 – Maastricht Presented to OPSAWG at IETF83 – Paris Accepted as OPSAWG WG Document
E N D
CGN Deployment with BGP/MPLS IP VPNs draft-ietf-opsawg-lsn-deployment-00 IETF84 Vancouver Victor Kuarsingh, Rogers Communications
Baseline • First Presented in BEHAVE at IETF78 – Maastricht • Presented to OPSAWG at IETF83 – Paris • Accepted as OPSAWG WG Document • Potential Move to SUNSET4 in the future (up to AD) • (did not exist at the time) • Show real world implementation option for CGN (based on NAT444 Model) • Includes models for IPv6 Dual Stack with CGN/NAT444 • Can be used in Wireless or Wireline domains
Status • Some, but not too much chatter (comments) on draft from WG • Move to SUNSET4 unknown at this time • Model in document in production (Wireless/Wireline environments) • Move comments welcome (to clean up document)
Basic Model (Diagram) • CGN Traffic in IP VPN (BGP/MPLS) • Post translated traffic on Global (Internet) routing table • Allows separation of legacy IPv4 and CGN IPv4 traffic • Utilizes common operation technologies • Provides efficient way to accomplish CGN by-pass • CGN hardware can be located anywhere on network (no policy routing required)
Dual Stack Concept with LSN (Diagram) • Supports dual stack operation if IPv6 is needed with CGN/NAT444
Next Steps • Further comments welcome • Is Document read to progress? • When to move to WGLC?