[Mip4] Re: MIP and transition issues

Pekka Savola <pekkas@netcore.fi> Fri, 29 October 2004 15:04 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07354 for <mip4-web-archive@ietf.org>; Fri, 29 Oct 2004 11:04:20 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNYWz-0000vS-EE for mip4-web-archive@ietf.org; Fri, 29 Oct 2004 11:19:10 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNXwn-0004dq-Kw; Fri, 29 Oct 2004 10:41:45 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CNDtp-0005An-PD; Thu, 28 Oct 2004 13:17:22 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23413; Thu, 28 Oct 2004 13:17:19 -0400 (EDT)
Received: from netcore.fi ([193.94.160.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CNE7v-0005CE-RC; Thu, 28 Oct 2004 13:31:56 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.11.6/8.11.6) with ESMTP id i9SHGbt20090; Thu, 28 Oct 2004 20:16:37 +0300
Date: Thu, 28 Oct 2004 20:16:37 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: "Soliman, Hesham" <H.Soliman@flarion.com>
In-Reply-To: <A11736FE943F1A408F8BBB1B9F5FE8AD17DD59@ftmailserver.flariontech.com>
Message-ID: <Pine.LNX.4.61.0410261244340.9692@netcore.fi>
References: <A11736FE943F1A408F8BBB1B9F5FE8AD17DD59@ftmailserver.flariontech.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab
X-Mailman-Approved-At: Fri, 29 Oct 2004 10:41:44 -0400
Cc: nemo@ietf.org, mip6@ietf.org, mip4@ietf.org, miptrans@ops.ietf.org, v6ops@ops.ietf.org, Tsirtsis George <G.Tsirtsis@flarion.com>
Subject: [Mip4] Re: MIP and transition issues
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Sender: mip4-bounces@ietf.org
Errors-To: mip4-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da

Hi,

I've created a new mailing list to discuss Mobile IP transition 
issues.  There is no single good mailing list to do that, and 
crossposting to upto 4 WGs is not a good idea.

Address: miptrans@ops.ietf.org
To subscribe: 'subscribe miptrans' in the body to majordomo@psg.com
Web archives: http://ops.ietf.org/lists/miptrans/

**** DO NOT POST ANY FURTHER MESSAGES ON V6OPS LIST! ****
(if you respond, please remove the other lists from Cc:)

FWIW, I also noticed there is another related draft:

Use of MIPv6 in IPv4 and MIPv4 in IPv6 networks
draft-larsson-v6ops-mip-scenarios-00.txt
(Larsson, Gustafsson, Levkowetz)

As there have been various presentations on v6ops two times already, 
with no clear resolution, it would seem to be useful to have various 
people working on different documents bang their heads together on 
miptrans or offlist on which document(s) describing the problems and 
scenarios is the most appropriate as a basis for discussion.

On Mon, 25 Oct 2004, Soliman, Hesham wrote:
> Sorry for the cross posting, but this issue is being
> discussed in all WG listed.
>
> I submitted the following two drafts last night:
> draft-tsirtsis-dsmip-problem
> draft-soliman-v4v6-mipv6-
>
> The first deals with the problem statement and the
> second is one of the solution for using MIPv6 only.
> There is another draft that proposes using MIPv4
> only: draft-tsirtsis-v4v6-mipv4
>
> I hope we can discuss the problem statement and scenarios
> in the next meeting. While the problem statement is on the mip6
> charter, it would be useful if we can have a slot allocated for
> this in v6ops.
>
> thx
> Hesham
>
> ===========================================================
> This email may contain confidential and privileged material for the sole use
> of the intended recipient.  Any review or distribution by others is strictly
> prohibited.  If you are not the intended recipient please contact the sender
> and delete all copies.
> ===========================================================
>
>

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

-- 
Mip4 mailing list: Mip4@ietf.org
    Web interface: https://www1.ietf.org/mailman/listinfo/mip4
     Charter page: http://www.ietf.org/html.charters/mip4-charter.html
Supplemental site: http://www.mip4.org/