Radio interface and Tree Discovery [wasRE: [nemo] NEMO multihoming]

"Pascal Thubert \(pthubert\)" <pthubert@cisco.com> Mon, 25 October 2004 07:09 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25385 for <nemo-archive@lists.ietf.org>; Mon, 25 Oct 2004 03:09:14 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLyxC-0006Bp-4P; Mon, 25 Oct 2004 03:07:42 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CLywx-00069G-I8 for nemo@megatron.ietf.org; Mon, 25 Oct 2004 03:07:27 -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 DAA25258 for <nemo@ietf.org>; Mon, 25 Oct 2004 03:07:25 -0400 (EDT)
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CLzAM-0007PT-Aq for nemo@ietf.org; Mon, 25 Oct 2004 03:21:18 -0400
Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 25 Oct 2004 09:23:39 +0200
X-BrightmailFiltered: true
Received: from xbh-ams-331.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i9P76TT1011253; Mon, 25 Oct 2004 09:06:52 +0200 (MEST)
Received: from xmb-ams-337.cisco.com ([144.254.231.82]) by xbh-ams-331.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 25 Oct 2004 09:06:48 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Radio interface and Tree Discovery [wasRE: [nemo] NEMO multihoming]
Date: Mon, 25 Oct 2004 09:06:43 +0200
Message-ID: <7892795E1A87F04CADFCCF41FADD00FC345405@xmb-ams-337.emea.cisco.com>
Thread-Topic: Radio interface and Tree Discovery [wasRE: [nemo] NEMO multihoming]
Thread-Index: AcS6SwfuA+TbVSx8QcGfePytG4Vs5QAE48Jw
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Vikrant Kaulgud <vikrantsk@gmail.com>, IETF NEMO WG <nemo@ietf.org>, "Gupta, Vivek G" <vivek.g.gupta@intel.com>
X-OriginalArrivalTime: 25 Oct 2004 07:06:48.0445 (UTC) FILETIME=[31DE1AD0:01C4BA61]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8
Content-Transfer-Encoding: quoted-printable
X-BeenThere: nemo@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: NEMO Working Group <nemo.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:nemo@ietf.org>
List-Help: <mailto:nemo-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/nemo>, <mailto:nemo-request@ietf.org?subject=subscribe>
Sender: nemo-bounces@ietf.org
Errors-To: nemo-bounces@ietf.org
Content-Transfer-Encoding: quoted-printable

Hi Vikrant:

As I understand it, 802.21 is defining a super radio layer (2.5 or less
:) that would perform intelligent handover over various radio
technologies.

At the moment, though:

L3 triggers (e.g. RAs in the NEMO case, or IGP messages) are ill/not
defined. There is no way for the access router to push them to the AP,
for APs to send the RAs as class1 on .11, or for the MN to know about
APs other then the one it is associated to. Even if that was available
(MN can get RAs from all APs in range), there's no control from L3 to
force an association to the best AP, in terms of reachability, from MN
standpoint.

Say there was, there's still a missing link for NEMO basic support to
operate efficiently. That's extended reachability information, inside
the RAs, besides plain ND. IMHO, there are 2 drafts that provide for
this in different contexts:

- For plain MN and multihoming, we have
draft-ietf-ipv6-router-selection-03.txt that gives us reachability
information in a routed topology.

- For Nested NEMO, we have draft-thubert-tree-discovery-01.txt that
enables the selection of the AR that builds the shallowest tree of
Mobile Routers to the Infrastructure (and much more :)

My thinking is that it's good for us to interact with 802.21 to get the
complete picture. But also and mostly, our responsibility is to move
forward with our own side of the 2.5 boundary, and in particular for
NEMO, there's work to do on the TD technology.

Pascal

> -----Original Message-----
> From: nemo-bounces@ietf.org [mailto:nemo-bounces@ietf.org] On Behalf
Of Vikrant Kaulgud
> Sent: lundi 25 octobre 2004 06:21
> To: IETF NEMO WG
> Subject: [nemo] NEMO multihoming
> 
> Hi,
> 
> Ubiquity is one of the benefits mentioned in the draft and rightly so.
> Over the last few months, IEEE 802.21 has shown lot of activity in
> addressing media independent handoff between heterogeneous networks
> (http://www.ieee802.org/21)
> 
> Although 802.21 work is directed towards the MN, the basic concepts
> would still apply to multihoming in mobile networks also.
> 
> ~~~~~~~~
> Regards
> Vikrant