IETF Logo Mail Archive

Re: [BEHAVE] predictable translations

<mohamed.boucadair@orange.com> Fri, 23 September 2011 05:57 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: behave@ietfa.amsl.com
Delivered-To: behave@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE80C21F86EC for <behave@ietfa.amsl.com>; Thu, 22 Sep 2011 22:57:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.228
X-Spam-Level:
X-Spam-Status: No, score=-2.228 tagged_above=-999 required=5 tests=[AWL=0.019, BAYES_00=-2.599, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001, UNPARSEABLE_RELAY=0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F04QS9X+9Vl4 for <behave@ietfa.amsl.com>; Thu, 22 Sep 2011 22:57:37 -0700 (PDT)
Received: from relais-inet.francetelecom.com (relais-ias244.francetelecom.com [80.12.204.244]) by ietfa.amsl.com (Postfix) with ESMTP id 6094421F86D0 for <behave@ietf.org>; Thu, 22 Sep 2011 22:57:37 -0700 (PDT)
Received: from omfeda06.si.francetelecom.fr (unknown [xx.xx.xx.199]) by omfeda14.si.francetelecom.fr (ESMTP service) with ESMTP id 8E3182AC61D; Fri, 23 Sep 2011 08:00:09 +0200 (CEST)
Received: from PUEXCH11.nanterre.francetelecom.fr (unknown [10.101.44.27]) by omfeda06.si.francetelecom.fr (ESMTP service) with ESMTP id 74B06C8060; Fri, 23 Sep 2011 08:00:09 +0200 (CEST)
Received: from PUEXCB1B.nanterre.francetelecom.fr ([10.101.44.7]) by PUEXCH11.nanterre.francetelecom.fr ([10.101.44.27]) with mapi; Fri, 23 Sep 2011 08:00:09 +0200
From: mohamed.boucadair@orange.com
To: "Poscic, Kristian (Kristian)" <kristian.poscic@alcatel-lucent.com>, "'behave@ietf.org'" <behave@ietf.org>
Date: Fri, 23 Sep 2011 08:00:07 +0200
Thread-Topic: predictable translations
Thread-Index: Acx5WV97aAu68hVNTaay9qYQdmoSIAAJTlUgAA1r3VA=
Message-ID: <94C682931C08B048B7A8645303FDC9F355A8E5A5FC@PUEXCB1B.nanterre.francetelecom.fr>
References: <737DDEA1297B0348BA6AB9EA3216A67F02CDB54BE4@USNAVSXCHMBSC3.ndc.alcatel-lucent.com> <2073A6C5467C99478898544C6EBA3F4602BC3C820D@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
In-Reply-To: <2073A6C5467C99478898544C6EBA3F4602BC3C820D@USNAVSXCHMBSC3.ndc.alcatel-lucent.com>
Accept-Language: fr-FR
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: fr-FR
Content-Type: multipart/alternative; boundary="_000_94C682931C08B048B7A8645303FDC9F355A8E5A5FCPUEXCB1Bnante_"
MIME-Version: 1.0
X-PMX-Version: 5.5.9.395186, Antispam-Engine: 2.7.2.376379, Antispam-Data: 2011.9.23.22414
Subject: Re: [BEHAVE] predictable translations
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Fri, 23 Sep 2011 05:57:39 -0000

Dear Kris,

Could please precise more what you mean by "predictable translation"?

(1) Do you want to eliminate the volume of CGN logs (e.g, few entries per customer) or (2) you want to eliminate the CGN logging (e.g., rely on DHCP records)?

(1) can be done in the CGN itself by design or configuration of the CGN to use port ranges. This is already supported by CGN implementation including A(..)U ;-)

(2) can be supported only if you eliminate the NAT function in the CGN which should be a PRR (Port Range Router; http://tools.ietf.org/html/draft-boucadair-port-range-02#section-6) instead.


Cheers,
Med

________________________________
De : behave-bounces@ietf.org [mailto:behave-bounces@ietf.org] De la part de Poscic, Kristian (Kristian)
Envoyé : vendredi 23 septembre 2011 01:28
À : 'behave@ietf.org'
Objet : Re: [BEHAVE] predictable translations

I looked at this draft draft-bsd-softwire-stateless-port-index-analysis-00<http://datatracker.ietf.org/doc/draft-bsd-softwire-stateless-port-index-analysis/> which examines 6 different algorithms for predictable translation applicable to v4/v6 translation but I guess it can be potentially adopted for v4 to v4 conversions as well.

As my coworker (who is probably on this list) says "too many deterministic nat drafts make for non-deterministic behaviours".
Is there any plan to adopt one as a standard?
Thanks,
Kris

From: Poscic, Kristian (Kristian)
Sent: Thursday, September 22, 2011 11:57 AM
To: behave@ietf.org
Subject: predictable translations

Hi there -
Does anyone knows of any draft that is addressing a more predictable translations between the inside IP and outside IP + port range when it comes to NAT44.
For example in order to avoid logging, IPv4 inside address would be automatically (via an algorithm) be converted to an outside IPv4 address  + a port range. This mapping would be unique so that no logging is required. The revertive algo would be able to convert the outside IP + port back  to the inside IP.

I've seen some drafts addressing something similar in the softwire WG but they all deal with IPv4/IPv6 translations.
Thanks,
Kris

v2.23.0 | Report a Bug | By Email