Re: [Hipsec] Selection of LSI address block

Miika Komu <miika.komu@hiit.fi> Fri, 21 August 2009 05:18 UTC

Return-Path: <miika.komu@hiit.fi>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 758663A687B for <hipsec@core3.amsl.com>; Thu, 20 Aug 2009 22:18:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
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 wUD5OikbbK+c for <hipsec@core3.amsl.com>; Thu, 20 Aug 2009 22:18:07 -0700 (PDT)
Received: from argo.otaverkko.fi (argo.otaverkko.fi [212.68.0.2]) by core3.amsl.com (Postfix) with ESMTP id A1D713A68F2 for <hipsec@ietf.org>; Thu, 20 Aug 2009 22:18:07 -0700 (PDT)
Received: from [192.168.1.2] (cs27101111.pp.htv.fi [89.27.101.111]) by argo.otaverkko.fi (Postfix) with ESMTP id CA12525ED16 for <hipsec@ietf.org>; Fri, 21 Aug 2009 08:18:12 +0300 (EEST)
Message-ID: <4A8E2E16.3060305@hiit.fi>
Date: Fri, 21 Aug 2009 08:18:14 +0300
From: Miika Komu <miika.komu@hiit.fi>
User-Agent: Thunderbird 2.0.0.22 (X11/20090608)
MIME-Version: 1.0
To: HIP <hipsec@ietf.org>
References: <4A8CF111.5010901@hiit.fi> <4A8D2557.4060705@htt-consult.com><77F357662F8BFA4CA7074B0410171B6D0A8B7264@XCH-NW-5V1.nw.nos.boeing.com> <4A8DC176.3000608@hiit.fi> <77F357662F8BFA4CA7074B0410171B6D0A8B7265@XCH-NW-5V1.nw.nos.boeing.com> <4A8E27A6.3050504@hiit.fi> <77F357662F8BFA4CA7074B0410171B6D0A8B7266@XCH-NW-5V1.nw.nos.boeing.com>
In-Reply-To: <77F357662F8BFA4CA7074B0410171B6D0A8B7266@XCH-NW-5V1.nw.nos.boeing.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Hipsec] Selection of LSI address block
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: miika.komu@hiit.fi
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 21 Aug 2009 05:18:08 -0000

Henderson, Thomas R wrote:

Hi,

>> there may be also some applications that don't scan networking and 
>> assume that all 192.168.0.0 and 10.0.0.0 networks are NATted. Such as 
>> p2p software.
> 
> good point.  Although this would be akin to a case where both peers are
> behind the same NAT, it may cause extra NAT traversal machinery to kick
> in.

btw, I am not saying that this is the right way to implement 
applications. In fact, ICE has a completely different philosophy which 
is more obvious when you think about building a large, isolate "lab" 
network from the private address range. But some apps, nevertheless, are 
just doing this even though it's "wrong".