Re: [addr-select-dt] RFC 3484 issues in address selection in the presence of an IPv4 NAT

Bob Hinden <bob.hinden@nokia.com> Mon, 23 March 2009 21:37 UTC

Return-Path: <Bob.Hinden@nokia.com>
X-Original-To: addr-select-dt@core3.amsl.com
Delivered-To: addr-select-dt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B38B83A6C11 for <addr-select-dt@core3.amsl.com>; Mon, 23 Mar 2009 14:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.171
X-Spam-Level:
X-Spam-Status: No, score=-6.171 tagged_above=-999 required=5 tests=[AWL=-0.172, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, RCVD_IN_DNSWL_MED=-4]
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 XJ4YRi72sNxX for <addr-select-dt@core3.amsl.com>; Mon, 23 Mar 2009 14:37:32 -0700 (PDT)
Received: from mgw-mx03.nokia.com (smtp.nokia.com [192.100.122.230]) by core3.amsl.com (Postfix) with ESMTP id 98B063A6C4F for <addr-select-dt@ietf.org>; Mon, 23 Mar 2009 14:37:31 -0700 (PDT)
Received: from esebh105.NOE.Nokia.com (esebh105.ntc.nokia.com [172.21.138.211]) by mgw-mx03.nokia.com (Switch-3.2.6/Switch-3.2.6) with ESMTP id n2NLbgwO031314; Mon, 23 Mar 2009 23:37:45 +0200
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh105.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.3959); Mon, 23 Mar 2009 23:36:48 +0200
Received: from mgw-int01.ntc.nokia.com ([172.21.143.96]) by esebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.3959); Mon, 23 Mar 2009 23:36:48 +0200
Received: from danira-pool050120.americas.nokia.com (danira-pool050120.americas.nokia.com [10.241.50.120]) by mgw-int01.ntc.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id n2NLacvH017058; Mon, 23 Mar 2009 23:36:41 +0200
From: Bob Hinden <bob.hinden@nokia.com>
To: Fred Baker <fred@cisco.com>
In-Reply-To: <A28B6BD7-6BCF-4E1B-B0C0-2A3785B845B4@cisco.com>
References: <A28B6BD7-6BCF-4E1B-B0C0-2A3785B845B4@cisco.com>
Message-Id: <695BF428-E196-4492-8FC7-51045BA2D89D@nokia.com>
Content-Type: text/plain; charset="US-ASCII"; format="flowed"; delsp="yes"
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Date: Mon, 23 Mar 2009 14:36:37 -0700
X-Mailer: Apple Mail (2.930.3)
X-OriginalArrivalTime: 23 Mar 2009 21:36:48.0120 (UTC) FILETIME=[785DE780:01C9ABFF]
X-Nokia-AV: Clean
X-Mailman-Approved-At: Mon, 23 Mar 2009 16:18:18 -0700
Cc: 6man Chairs <6man-chairs@tools.ietf.org>, 6man-ads@tools.ietf.org, Ron Bonica <rbonica@juniper.net>, addr-select-dt@ietf.org, Kurt Erik Lindqvist <kurtis@kurtis.pp.se>, draft-denis-v6ops-nat-addrsel@tools.ietf.org
Subject: Re: [addr-select-dt] RFC 3484 issues in address selection in the presence of an IPv4 NAT
X-BeenThere: addr-select-dt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: bob.hinden@nokia.com
List-Id: IPv6 Address Selection Design Team <addr-select-dt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/addr-select-dt>, <mailto:addr-select-dt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/addr-select-dt>
List-Post: <mailto:addr-select-dt@ietf.org>
List-Help: <mailto:addr-select-dt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/addr-select-dt>, <mailto:addr-select-dt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Mar 2009 21:37:32 -0000

Fred,

We have a design team in this area.  I suspect they were in the the  
v6ops session this morning.  I copied them here.

Bob


On Mar 23, 2009, at 2:02 PM, ext Fred Baker wrote:

> I'd like to bring
>
> http://tools.ietf.org/html/draft-denis-v6ops-nat-addrsel
>  "Problems with IPv6 source address selection and IPv4 NATs", Remi
>  Denis-Courmont, 18-Feb-09, <draft-denis-v6ops-nat-addrsel-00.txt>
>
> to your attention. We discussed it briefly this morning in v6ops.  
> The sense of the room was that it was likely related to your effort  
> to improve RFC 3484.
>
> Along those lines, the discussion at the mike included at least two  
> points that RFC 3484 runs afoul of. One is that RFC 3484 enables no  
> API for administrative control, and administrators are likely to  
> want to update it in their environments. The other is that the logic  
> that addresses have degrees of likelihood of being useful in a fixed  
> order - any fixed order - is problematic. Rather, one might have an  
> initial order one uses, but as the system gains experience of what  
> address selections are most useful, it would be better to have the  
> OS, guided by the application, try those addresses that have  
> historically been useful first.
>
> How would you recommend proceeding? Would you prefer to take this  
> draft into 6man and including it in the RFC 3484 update?