Re: [BEHAVE] Very late query on stateful NAT64

marcelo bagnulo braun <marcelo@it.uc3m.es> Fri, 22 October 2010 17:22 UTC

Return-Path: <marcelo@it.uc3m.es>
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 2009C3A68E7 for <behave@core3.amsl.com>; Fri, 22 Oct 2010 10:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.471
X-Spam-Level:
X-Spam-Status: No, score=-106.471 tagged_above=-999 required=5 tests=[AWL=0.128, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 9qfk6pcHDWUy for <behave@core3.amsl.com>; Fri, 22 Oct 2010 10:22:40 -0700 (PDT)
Received: from smtp03.uc3m.es (smtp03.uc3m.es [163.117.176.133]) by core3.amsl.com (Postfix) with ESMTP id 0F1203A6809 for <behave@ietf.org>; Fri, 22 Oct 2010 10:22:39 -0700 (PDT)
X-uc3m-safe: yes
Received: from marcelo-bagnulos-macbook-pro.local (40.30.18.95.dynamic.jazztel.es [95.18.30.40]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp03.uc3m.es (Postfix) with ESMTP id AE236872EA4; Fri, 22 Oct 2010 19:24:11 +0200 (CEST)
Message-ID: <4CC1C8BA.1050403@it.uc3m.es>
Date: Fri, 22 Oct 2010 19:24:10 +0200
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; es-ES; rv:1.9.2.8) Gecko/20100802 Thunderbird/3.1.2
MIME-Version: 1.0
To: Dan Wing <dwing@cisco.com>
References: <4CC0C319.1040400@gmail.com> <43f701cb7201$9c9a9020$d5cfb060$@com>
In-Reply-To: <43f701cb7201$9c9a9020$d5cfb060$@com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 8bit
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-6.0.0.1038-17720.000
Cc: draft-ietf-behave-v6v4-xlate-stateful@tools.ietf.org, 'Se-young Yu' <syu051@aucklanduni.ac.nz>, behave@ietf.org
Subject: Re: [BEHAVE] Very late query on stateful NAT64
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: Fri, 22 Oct 2010 17:22:41 -0000

  El 22/10/10 17:55, Dan Wing escribió:
>
> This text is related to existing NAPT44 behavior, where a mapping
> is kept active so long as there is an inside->outside flow (which
> makes sense, and is usually 15-30 seconds) and is kept active longer
> if there is an outside->inside response (which makes sense, too,
> and is usually ~3 minutes).  The next characteristic is that the
> NAT shouldn't keep a mapping alive if there is solely and only
> an outside->inside flow.  This is discussed (but with a focus on
> RTP flows) in draft-ietf-avt-app-rtp-keepalive, and the best
> reference is probably REQ-6 of RFC4787.
>
Right, as several have stated already, this is the same as REQ 6 in 
RFC4787 and as a guideline we have in general tried to honour the behave 
requirements (while trnaslating them to the v6 v4 translation)


> Would it be helpful to add a citation to "Section 4.3 of [RFC4787]"
> during that document's AUTH48?
>
> (The wording should be tweaked, anyway, from "MAY choose not to
> extend" to "MAY choose to not extend".)
>
let me know what you want to do and i can drop a note to the RFC editor. 
I am fine with Dan's proposed changes.

Regards, marcelo


> -d
>
>
>