Re: [MULTIMOBSEC-API] first steps in APIs

Shinta Sugimoto <shinta@sfc.wide.ad.jp> Tue, 25 April 2006 06:08 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYGia-00045C-Ja; Tue, 25 Apr 2006 02:08:12 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FYGiZ-000457-9o for multimobsec-api@ietf.org; Tue, 25 Apr 2006 02:08:11 -0400
Received: from mail.sfc.wide.ad.jp ([203.178.142.146]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FYGiX-0003np-U0 for multimobsec-api@ietf.org; Tue, 25 Apr 2006 02:08:11 -0400
Received: from [193.234.219.165] (w165.nomadiclab.com [193.234.219.165]) by mail.sfc.wide.ad.jp (Postfix) with ESMTP id A2F9F4D876; Tue, 25 Apr 2006 15:08:05 +0900 (JST)
Date: Tue, 25 Apr 2006 09:08:04 +0300
From: Shinta Sugimoto <shinta@sfc.wide.ad.jp>
To: Michael Richardson <mcr@sandelman.ottawa.on.ca>
Subject: Re: [MULTIMOBSEC-API] first steps in APIs
In-Reply-To: <10723.1145750635@sandelman.ottawa.on.ca>
References: <Pine.SOL.4.64.0604222216380.17569@kekkonen.cs.hut.fi> <10723.1145750635@sandelman.ottawa.on.ca>
Message-Id: <20060425090109.12AA.SHINTA@sfc.wide.ad.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Mailer: Becky! ver. 2.21.03 [ja]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Cc: multimobsec-api@ietf.org
X-BeenThere: multimobsec-api@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "Multihoming, mobility and security APIs" <multimobsec-api.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/multimobsec-api>, <mailto:multimobsec-api-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www1.ietf.org/mailman/private/multimobsec-api>
List-Post: <mailto:multimobsec-api@ietf.org>
List-Help: <mailto:multimobsec-api-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/multimobsec-api>, <mailto:multimobsec-api-request@ietf.org?subject=subscribe>
Errors-To: multimobsec-api-bounces@ietf.org

Hello Michael,

On Sat, 22 Apr 2006 20:03:55 -0400
Michael Richardson <mcr@sandelman.ottawa.on.ca> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> >>>>> "Miika" == Miika Komu <miika@iki.fi> writes:
>     Miika> Initially, we though that we could have one "core" draft
>     Miika> which includes only the things that are common for all
>     Miika> working groups. In the end, we though that it might be better
>     Miika> to have a core draft that describes all "peripheral" things
>     Miika> like general locator management, failure and reachability
>     Miika> detection. Things really specific to individual working
>     Miika> groups could be described in separate extension drafts.
> 
>   My impression is that we actually have two commonalities, not three.
>   I.e. the venn diagram looks like:
> 
> 
> 	      *****************
>               *		      *
>        .------*-----.	      *
>        |      *     |	      *
>        |IPsec * HIP |  shim6  *
>        |      *     |	      *
>        |      *     |	      *
>        .------*-----.	      *
> 	      *		      *
> 	      *****************
> 
> 
>   What does shim6 have in common with IPsec over IPv4?
>   This question is not an argument, but rather, a genuine question.

As you pointed out, currently SHIM6 only handles IPv6 addresses
in its locator management.  But in the future, it could also
support IPv4 locator as well.  It is addressed in Section 1.3 of
Erik Nordmark's draft <draft-nordmark-shim6-esd-00.txt>.

So, there is not need to exclude IPv4 locator management from
the common part, I think.


Regards,
Shinta


_______________________________________________
MULTIMOBSEC-API mailing list
MULTIMOBSEC-API@ietf.org
https://www1.ietf.org/mailman/listinfo/multimobsec-api