[MEXT] MIP6 - DSMIP6 related to boot-nemo4manet

"Teco Boot" <teco@inf-net.nl> Wed, 07 November 2007 08:06 UTC

Return-path: <mext-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipfvq-000073-Pf; Wed, 07 Nov 2007 03:06:38 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ipfvo-00005g-U9 for mext@ietf.org; Wed, 07 Nov 2007 03:06:36 -0500
Received: from hpsmtp-eml14.kpnxchange.com ([213.75.38.114]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ipfvk-00068K-C5 for mext@ietf.org; Wed, 07 Nov 2007 03:06:36 -0500
Received: from hpsmtp-eml01.kpnxchange.com ([213.75.38.101]) by hpsmtp-eml14.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Nov 2007 09:06:31 +0100
Received: from M90Teco ([86.83.9.22]) by hpsmtp-eml01.kpnxchange.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 7 Nov 2007 09:06:31 +0100
From: Teco Boot <teco@inf-net.nl>
To: mext@ietf.org
Date: Wed, 07 Nov 2007 09:06:20 +0100
Message-ID: <006c01c82115$1510ee00$3f32ca00$@nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AcghFRSq01PY3uXhQw+MYBCdnAtJsA==
Content-Language: nl
X-OriginalArrivalTime: 07 Nov 2007 08:06:31.0229 (UTC) FILETIME=[1B128ED0:01C82115]
X-Spam-Score: -1.0 (-)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [MEXT] MIP6 - DSMIP6 related to boot-nemo4manet
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Errors-To: mext-bounces@ietf.org

Hi,

I published an Autoconf solution, based on what we can do with existing
protocols as much as possible.
http://www.ietf.org/internet-drafts/draft-boot-autoconf-nemo4manet-00.txt
I used NEMO for dynamic tunneling between MANET Routers and Border Routers.
The MANET Routers act as Mobile Routers; the Border Routers act as Home
Agents. Nested NEMO is used for session continuity when handover occurs.

Issue related to MIP6:
I want Border Routers advertize not only that they provide access to
Internet, but optionally also the identity of the Service Provider. I used
draft-korhonen-mip6-service-04.txt as a guideline, signaling Service
Selection Identifiers.

Issues related to DSMIP6:
In want the NEMO tunnel to transport IPv4, utilize header compression and be
protected by IPsec.
Using DSMIP6 enables IPv4 and IPsec.
DSMIP6 Header Compression is proposed in
draft-haddad-mip6-tunneling-optimization-01.txt, but nothing more than
"TBD".
Building and maintaining security associations with guaranteed anonymity is
to be analyzed.

Issue related to MONAMI6:
I propose using concurrent MANET Router - Border Router tunnels for seamless
handover. Nothing special, except it is work in progress.

Comments (and help:-) on my draft is welcome.
I may post issues concerning DSMIP6, NEMO and MONAMI6 in Autoconf context.

Regards, Teco



_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www1.ietf.org/mailman/listinfo/mext