IETF Logo Mail Archive

[BEHAVE] Per-interface NAT in mobile networks

<mohamed.boucadair@orange-ftgroup.com> Mon, 25 October 2010 14:45 UTC

Return-Path: <mohamed.boucadair@orange-ftgroup.com>
X-Original-To: behave@core3.amsl.com
Delivered-To: behave@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E82043A6A5C; Mon, 25 Oct 2010 07:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.144
X-Spam-Level:
X-Spam-Status: No, score=-3.144 tagged_above=-999 required=5 tests=[AWL=0.104, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_LOW=-1, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7d0gnP5Z4tH4; Mon, 25 Oct 2010 07:45:24 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias92.francetelecom.com [193.251.215.92]) by core3.amsl.com (Postfix) with ESMTP id 492B53A6A58; Mon, 25 Oct 2010 07:45:23 -0700 (PDT)
Received: from omfedm06.si.francetelecom.fr (unknown [xx.xx.xx.2]) by omfedm14.si.francetelecom.fr (ESMTP service) with ESMTP id 742C622C50B; Mon, 25 Oct 2010 16:47:07 +0200 (CEST)
Received: from PUEXCH21.nanterre.francetelecom.fr (unknown [10.101.44.28]) by omfedm06.si.francetelecom.fr (ESMTP service) with ESMTP id 5044827C067; Mon, 25 Oct 2010 16:47:07 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.8]) by PUEXCH21.nanterre.francetelecom.fr ([10.101.44.28]) with mapi; Mon, 25 Oct 2010 16:47:04 +0200
From: mohamed.boucadair@orange-ftgroup.com
To: Softwires list <softwires@ietf.org>, Behave WG <behave@ietf.org>, "draft-arkko-dual-stack-extra-lite@tools.ietf.org" <draft-arkko-dual-stack-extra-lite@tools.ietf.org>
Date: Mon, 25 Oct 2010 16:47:03 +0200
Thread-Topic: Per-interface NAT in mobile networks
Thread-Index: Act0U3zZ19doDnyUS5aXIdfhKMXIXQ==
Message-ID: <8806_1288018027_4CC5986B_8806_213602_1_94C682931C08B048B7A8645303FDC9F32F984DC3C6@PUEXCB1B.nanterre.francetelecom.fr>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2010.10.25.142416
Cc: RD-CORE <olivier.bernier@orange-ftgroup.com>, BINET David NCPI/NAD/TIP <david.binet@orange-ftgroup.com>, IBRAHIM Houmed RD-CORE <houmed.ibrahim@orange-ftgroup.com>, MOUQUET Antoine RD-CORE <antoine.mouquet@orange-ftgroup.com>, BERNIER
Subject: [BEHAVE] Per-interface NAT in mobile networks
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 25 Oct 2010 14:45:26 -0000

   Dear all,

   When per-interface NAT is applied to 3GPP networks, a NAT function
   can be embedded in the GGSN/PGW.  The GTP tunnel identifier will be
   used as an identifier in the NAT table to identify sessions belonging
   to each UE.  Packets are then translated and forwarded to their
   destination (either internal or external).  Distinct IPv4 address
   pools may be configured on the GGSN/PGW depending on the APN.  This
   procedure can be implemented in mono stack PDP context or in
   dual stack PDP contexts.

   Embedding a NAT in the PGW/GGSN is one of the scenarios we are
   considering to rationalise the use of IPv4 address in mobile
   networks, while promoting the invocation of IPv6 transfer
   capabilities whenever possible (our recommendation for mobile is to
   go for dual-stack connectivity).  Unlike other solutions where the
   NAT is not embedded in the PGW, the activation of the per-interface
   NAT does not impact the network availability since no new nodes will
   be introduced to embed the NAT function.

   We think per-interface NAT
   (http://datatracker.ietf.org/doc/draft-arkko-dual-stack-extra-lite/ or
   http://tools.ietf.org/html/draft-miles-behave-l2nat-00)
   is a good place to describe this use case.

   Some vendors already support a NAT function in their PGW products,
   but for harmonising the behaviour of such implementations we think it
   would be valuable to see draft-arkko-dual-stack-extra-lite be adopted
   as a WG document in Behave or Softwire.

   Is there any plan to see this I-D progress as Softwire or Behave WG
   document?

   Cheers,

   Med


*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees. 
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration. 
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************

v2.23.0 | Report a Bug | By Email