CGN Deployment with BGP/MPLS IP VPNs
draft-ietf-opsawg-lsn-deployment-00

The information below is for an old version of the document
Document Type Active Internet-Draft (opsawg WG)
Last updated 2012-05-14
Replaces draft-kuarsingh-lsn-deployment
Stream IETF
Intended RFC status (None)
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
OPSAWG                                                 V. Kuarsingh, Ed.
Internet-Draft                                             J. Cianfarani
Intended status: Informational                     Rogers Communications
Expires: November 16, 2012                                  May 15, 2012

                  CGN Deployment with BGP/MPLS IP VPNs
                  draft-ietf-opsawg-lsn-deployment-00

Abstract

   This document specifies a framework to integrate a Network Address
   Translation layer into an operator's network to function as a Carrier
   Grade NAT (also known as CGN or Large Scale NAT).  CGN is a concept
   also described in [I-D.ietf-behave-lsn-requirements] and describes
   the model as a dual layer translation model.  Although operators may
   wish to deploy IPv6 to strategically overcome IPv4 exhaustion, near
   term needs may not be satisfied with an IPv6 deployment alone.  This
   document provides a practical integration model which allows CGN to
   be integrated into the network meeting the connectivity needs of the
   customer while being mindful of not disrupting existing services and
   meeting the technical challenges that CGN brings.  The model includes
   the use of BGP/MPLS IP VPNs defined in [RFC4364] as a tool to achieve
   this goal.  This document does not intend to defend the merits of
   CGN.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on November 16, 2012.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Kuarsingh & Cianfarani  Expires November 16, 2012               [Page 1]
Internet-Draft    CGN Deployment with BGP/MPLS IP VPNs          May 2012

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  Motivation . . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  CGN Network Deployment Requirements  . . . . . . . . . . . . .  4
     3.1.  Centralized versus Distributed Deployment  . . . . . . . .  5
     3.2.  CGN and Traditional IPv4 Service Co-existence  . . . . . .  6
     3.3.  CGN By-Pass  . . . . . . . . . . . . . . . . . . . . . . .  6
     3.4.  Routing Plane Separation . . . . . . . . . . . . . . . . .  6
     3.5.  Flexible Deployment Options  . . . . . . . . . . . . . . .  7
     3.6.  IPv4 Overlap Space . . . . . . . . . . . . . . . . . . . .  7
     3.7.  Transactional Logging for LSN Systems  . . . . . . . . . .  7
     3.8.  Additional CGN Requirements  . . . . . . . . . . . . . . .  8
   4.  BGP/MPLS IP VPN based CGN Framework  . . . . . . . . . . . . .  8
     4.1.  Service Separation . . . . . . . . . . . . . . . . . . . .  9
     4.2.  Internal Service Delivery  . . . . . . . . . . . . . . . . 10
       4.2.1.  Dual Stack Operation . . . . . . . . . . . . . . . . . 11
     4.3.  Deployment Flexibility . . . . . . . . . . . . . . . . . . 13
     4.4.  Comparison of BGP/MPLS IP VPN Option versus other CGN
           Attachment Options . . . . . . . . . . . . . . . . . . . . 13
       4.4.1.  IEEE 802.1Q  . . . . . . . . . . . . . . . . . . . . . 13
       4.4.2.  Policy Based Routing . . . . . . . . . . . . . . . . . 14
       4.4.3.  Traffic Engineering  . . . . . . . . . . . . . . . . . 14
       4.4.4.  Multiple Routing Topologies  . . . . . . . . . . . . . 14
   5.  Experiences  . . . . . . . . . . . . . . . . . . . . . . . . . 14
   6.  Basic Integration and Requirements Support . . . . . . . . . . 14
   7.  Performance  . . . . . . . . . . . . . . . . . . . . . . . . . 15
   8.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 16
   9.  Security Considerations  . . . . . . . . . . . . . . . . . . . 16
   10. Conclusions  . . . . . . . . . . . . . . . . . . . . . . . . . 17
   11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 17
Show full document text