InnovationQ will be updated on Sunday, May 20, from 10am - noon ET. You may experience brief service interruptions during that time.
Browse Prior Art Database

Carrier-Grade NAT (CGN) Deployment with BGP/MPLS IP VPNs (RFC7289)

IP.com Disclosure Number: IPCOM000237608D
Original Publication Date: 2014-Jun-01
Included in the Prior Art Database: 2014-Jun-27
Document File: 40 page(s) / 46K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

V. Kuarsingh: AUTHOR [+3]


Operators are faced with near-term IPv4 address-exhaustion challenges. Many operators may not have a sufficient amount of IPv4 addresses in the future to satisfy the needs of their growing subscriber base. This challenge may also be present before or during an active transition to IPv6, somewhat complicating the overall problem space.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 6% of the total text.

Internet Engineering Task Force (IETF)                 V. Kuarsingh, Ed. Request for Comments: 7289                                 J. Cianfarani Category: Informational                            Rogers Communications ISSN: 2070-1721                                                June 2014

         Carrier-Grade NAT (CGN) Deployment with BGP/MPLS IP VPNs


   This document specifies a framework to integrate a Network Address

   Translation (NAT) layer into an operator's network to function as a

   Carrier-Grade NAT (also known as CGN or Large-Scale NAT).  The CGN

   infrastructure will often form a NAT444 environment as the subscriber

   home network will likely also maintain a subscriber-side NAT

   function.  Exhaustion of the IPv4 address pool is a major driver

   compelling some operators to implement CGN.  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 that allows the CGN

   platform to be integrated into the network, meeting the connectivity

   needs of the subscriber while being mindful of not disrupting

   existing services and meeting the technical challenges that CGN

   brings.  The model included in this document utilizes BGP/MPLS IP

   VPNs, which allow for virtual routing separation, helping ease the

   CGN's impact on the network.  This document does not intend to defend

   the merits of CGN.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Not all documents    approved by the IESG are a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7289.

 Kuarsingh & Cianfarani        Informational                     [Page 1]
 RFC 7289          CGN Deployment with BGP/MPLS IP VPNs         June 2014

 Copyright Notice

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

   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 th...