IETF Logo Mail Archive

Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE charter

Pekka Savola <pekkas@netcore.fi> Fri, 24 October 2008 15:29 UTC

Return-Path: <v4v6interim-bounces@ietf.org>
X-Original-To: v4v6interim-archive@ietf.org
Delivered-To: ietfarch-v4v6interim-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 51F4B28C1D9; Fri, 24 Oct 2008 08:29:46 -0700 (PDT)
X-Original-To: v4v6interim@core3.amsl.com
Delivered-To: v4v6interim@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 873183A6A7C; Fri, 24 Oct 2008 02:19:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.231
X-Spam-Level:
X-Spam-Status: No, score=-2.231 tagged_above=-999 required=5 tests=[AWL=-0.232, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
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 lDstL+zWfduQ; Fri, 24 Oct 2008 02:19:45 -0700 (PDT)
Received: from netcore.fi (eunet-gw.ipv6.netcore.fi [IPv6:2001:670:86:3001::1]) by core3.amsl.com (Postfix) with ESMTP id 6D1FB3A6A6E; Fri, 24 Oct 2008 02:19:45 -0700 (PDT)
Received: from netcore.fi (localhost [127.0.0.1]) by netcore.fi (8.13.8/8.13.8) with ESMTP id m9O9KpA7001395; Fri, 24 Oct 2008 12:20:51 +0300
Received: from localhost (pekkas@localhost) by netcore.fi (8.13.8/8.13.8/Submit) with ESMTP id m9O9KpOp001392; Fri, 24 Oct 2008 12:20:51 +0300
Date: Fri, 24 Oct 2008 12:20:51 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Mark Townsley <townsley@cisco.com>
In-Reply-To: <49009C8B.80707@cisco.com>
Message-ID: <alpine.LRH.2.00.0810241218190.1106@netcore.fi>
References: <48F8539D.90608@ericsson.com> <48FB9C5E.8070402@gmail.com> <3E041E8D-8539-4A16-9188-86A1DCEEE62B@muada.com> <200810201358.29295.remi.denis-courmont@nokia.com> <8E5328A8-4937-41A8-A650-204795E074D1@muada.com> <5B78195C-1318-4325-8F98-BC19F59E1532@cisco.com> <01462145-8E18-465A-8989-D1C98D421DED@muada.com> <B5A2E7E1-7FAE-48B6-85E2-B1300DF1458D@cisco.com> <9E0384AB-A20B-44E7-8575-9275101FF920@muada.com> <49008B8E.9080408@ericsson.com> <49008F1E.3010804@cisco.com> <FABF6711-4591-4182-A1B4-002BC5F18B9D@cisco.com> <49009C8B.80707@cisco.com>
User-Agent: Alpine 2.00 (LRH 1167 2008-08-23)
MIME-Version: 1.0
X-Virus-Scanned: ClamAV version 0.94, clamav-milter version 0.94 on otso.netcore.fi
X-Virus-Status: Clean
X-Mailman-Approved-At: Fri, 24 Oct 2008 08:29:45 -0700
Cc: v4v6interim@ietf.org, 46Translation <46translation@employees.org>, Behave WG <behave@ietf.org>
Subject: Re: [v4v6interim] [BEHAVE] [46translation] Proposal for new BEHAVE charter
X-BeenThere: v4v6interim@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of coexistence topics for the 01-Oct-2008 v4-v6 coexistence interim meeting <v4v6interim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/v4v6interim>
List-Post: <mailto:v4v6interim@ietf.org>
List-Help: <mailto:v4v6interim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v4v6interim>, <mailto:v4v6interim-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: v4v6interim-bounces@ietf.org
Errors-To: v4v6interim-bounces@ietf.org

On Thu, 23 Oct 2008, Mark Townsley wrote:
>>  If #2 does not remind you of how we got into so much trouble nat44, well
>>  it should. Because of the impact on NAT66 on applications, if IETF does
>>  decide to do NAT66 specifications, I think it is very important that the
>>  specification is developed not only in the context of v6ops people but is
>>  also developed with input of folks from applications that need to use it.
>>  Today that would roughly mean behave.
>
> I think that something that operates only at the IP layer could stay in the 
> int-area.

But it doesn't; a 1:1 NAT66 would break every app (FTP, SIP, etc.) 
that's broken today with NAT4 (with or without port translation) 
unless the NAT has ALGs.  To implement such ALGs, NAT66 would need to 
operate beyond the IP layer.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings
_______________________________________________
v4v6interim mailing list
v4v6interim@ietf.org
https://www.ietf.org/mailman/listinfo/v4v6interim

v2.23.0 | Report a Bug | By Email