[Hipsec] Thinking about LSIs

Robert Moskowitz <rgm@htt-consult.com> Thu, 04 September 2008 17:24 UTC

Return-Path: <hipsec-bounces@ietf.org>
X-Original-To: hip-archive@lists.ietf.org
Delivered-To: ietfarch-hip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 928CA3A6A14; Thu, 4 Sep 2008 10:24:03 -0700 (PDT)
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 5CA553A6C4C for <hipsec@core3.amsl.com>; Thu, 4 Sep 2008 10:24:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.14
X-Spam-Level:
X-Spam-Status: No, score=-0.14 tagged_above=-999 required=5 tests=[BAYES_20=-0.74, 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 F5+2f9acFNjs for <hipsec@core3.amsl.com>; Thu, 4 Sep 2008 10:24:01 -0700 (PDT)
Received: from z9m9z.htt-consult.com (z9m9z.htt-consult.com [208.83.67.147]) by core3.amsl.com (Postfix) with ESMTP id 71F423A6B0B for <hipsec@ietf.org>; Thu, 4 Sep 2008 10:24:01 -0700 (PDT)
Received: from z9m9z.htt-consult.com (localhost.localdomain [127.0.0.1]) by z9m9z.htt-consult.com (8.13.8/8.13.8) with ESMTP id m84HO76L024711 for <hipsec@ietf.org>; Thu, 4 Sep 2008 13:24:07 -0400
Received: from nc2400.htt-consult.com (onlo.htt-consult.com [208.83.67.148]) by z9m9z.htt-consult.com (Scalix SMTP Relay 11.3.0.11339) via ESMTP; Thu, 04 Sep 2008 13:23:45 -0400 (EDT)
Date: Thu, 04 Sep 2008 13:24:59 -0400
From: Robert Moskowitz <rgm@htt-consult.com>
To: HIP <hipsec@ietf.org>
Message-ID: <48C019EB.1040908@htt-consult.com>
In-Reply-To: <48BF92A6.3020200@ericsson.com>
References: <48BF92A6.3020200@ericsson.com>
x-scalix-Hops: 1
User-Agent: Thunderbird 2.0.0.16 (X11/20080724)
MIME-Version: 1.0
Content-Disposition: inline
Subject: [Hipsec] Thinking about LSIs
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
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/pipermail/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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: hipsec-bounces@ietf.org
Errors-To: hipsec-bounces@ietf.org

This past week I worked my way into thinking about LSIs through the back 
door so to speak. Originally, LSIs were to deal with HIPs need to impose 
itself between an IPv4 app and the IPv4 Internet. Well and good, as I 
have been focusing totally on an IPv6 Internet.

But I have been worn down by the lack of IPv6 applications for Linux 
Things are just not working, and I don't believe it is becuase I am 
using Centos. I started thinking about IPv4 apps on an IPv6 Internet via 
HIP and LSIs. Probably many of you that have been working with HIP code 
all these years are thinking, 'oh course, simple'.

Well it is not documented. LSIs in general are only mentioned in 4423 
and very briefly. 5201 does not say anything about the LSI. It is 
covered somewhat in draft-ietf-hip-applications-04.txt, but not as I am 
thinking about it these days.

Has anyone here have IPv4 apps working over an IPv6 only network via HIP 
and LSIs? This could a very 'compelling story' for HIP, as everything I 
have read on IPv6 migration requires dual networks until all apps have 
been converted for IPv6.

v6tun from KAME is another approach to this problem, but I can't find it 
for Linux, and though I was given a Makefile supposedly for Linux for 
v6tun, it is not working for my on Centos.


_______________________________________________
Hipsec mailing list
Hipsec@ietf.org
https://www.ietf.org/mailman/listinfo/hipsec