FW: [Monami6] FW: I-DACTION:draft-hong-multipleif-mn-pb-statement-00.txt

"Yong-Geun Hong" <yghong@etri.re.kr> Wed, 26 October 2005 06:23 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUehB-0000rL-6F; Wed, 26 Oct 2005 02:23:33 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EUehA-0000qi-3H for monami6@megatron.ietf.org; Wed, 26 Oct 2005 02:23:32 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26278 for <monami6@ietf.org>; Wed, 26 Oct 2005 02:23:17 -0400 (EDT)
Received: from email1.etri.re.kr ([129.254.16.131] helo=email1.etri.info) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EUeuD-00055F-Fg for monami6@ietf.org; Wed, 26 Oct 2005 02:37:02 -0400
Received: from yghongnb ([129.254.2.22]) by email1.etri.info with Microsoft SMTPSVC(6.0.3790.211); Wed, 26 Oct 2005 15:25:16 +0900
From: Yong-Geun Hong <yghong@etri.re.kr>
To: 'Monami6 WG' <monami6@ietf.org>
Subject: FW: [Monami6] FW: I-DACTION:draft-hong-multipleif-mn-pb-statement-00.txt
Date: Wed, 26 Oct 2005 15:23:17 +0900
Organization: ETRI
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook, Build 11.0.6353
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2527
Thread-Index: AcXWVtdxRYG7MFarQZ+p2ssWUtQfJAB38uAQAG7MM0A=
Message-ID: <EMAIL1rV4ZneAzdfTVS00009d80@email1.etri.info>
X-OriginalArrivalTime: 26 Oct 2005 06:25:16.0833 (UTC) FILETIME=[07F0C910:01C5D9F6]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bf422c85703d3d847fb014987125ac48
Content-Transfer-Encoding: 7bit
Cc: khj@etri.re.kr
X-BeenThere: monami6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: Monami6 WG <monami6@ietf.org>
List-Id: Monami6 WG <monami6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/monami6>, <mailto:monami6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/monami6>
List-Post: <mailto:monami6@ietf.org>
List-Help: <mailto:monami6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/monami6>, <mailto:monami6-request@ietf.org?subject=subscribe>
Sender: monami6-bounces@ietf.org
Errors-To: monami6-bounces@ietf.org

 
Folks..

I was asked to send the review and difference between 
draft-montavont-mobileip-multihoming-pb-statement-04.txt and
my draft by Nicolas.

I think that the draft
draft-montavont-mobileip-multihoming-pb-statement-04.txt 
is a good draft which describes the requirements from the point of view of 
multihomed mobile nodes operating Mobile IPv6 and defines some issues.
We also learn many things in this draft.

But, when we were implementing a multiple interfaces mobile node(mobile
router),
we thought that the draft do not perfectly handle the problems of multiple
interfaces
of a mobile node. 

I summarize the parts related to the issues of multiple interfaces in a
mobile node
within the draft (draft-montavont-mobileip-multihoming-pb-statement-04.txt)

=============================================================

1. Section 3. Requirements 
    3th paragraph [page 8] : 

   Basically, Internet connectivity is guaranteed for a MN as long as at
   least one path is maintained between the MN and the fixed Internet.
   In some cases, it may be necessary to divert packets from a (perhaps
   failed) path to an alternative (perhaps newly established) path (e.g.
   for matters of fault recovery, preferences), or to split traffic
   between multiple paths (e.g. for load sharing, load balancing).  The
   use of an alternative path must be transparent at layers above layer
   3 if broken sessions and the establishment of new transport sessions
   has to be avoided.

2. Section 3. Requirements 
    Last paragraph [page 9] :

  One has to consider whether these goals can be achieved with
   transparency or without transparency.  Transparency is achieved when
   switching between interfaces does not cause the disruption of on-
   going sessions.  To be achieved with transparency, a necessary (may
   or may not be sufficient) condition is for the end-point addresses to
   remain unchanged.  This is in-view of the large amount of Internet
   traffic today are carried by TCP, which unlike SCTP, cannot handle
   multiple end-point address pairs.

3. Section 5.6 (n, 1, n) : n ifaces, 1, HoA, n CoAs

4. Section 6.1.3 Media Detection 

5. Section 7.3 Flow redirection

=============================================================

In my draft, I describe some practical problems.

1. Mobile IPv6-specific Issues
 : When a mobile node has multiple interfaces, it must have the ability to
look at
  all RA messages from multiple network interfaces to determine network
movement.

2. General network Issues
 : The mobile node also must update the relation between a destination
address and
  a network interface when it changes a network interface.

3. Considerations for Heterogeneous Environments
 : For the mobile node in IPv4 based network

Although the draft(draft-montavont-mobileip-multihoming-pb-statement-04.txt)
covers 
the multihoming issues including multiple interfaces node, my draft is more
focusing on
multiple interfaces node.

We think that it is better to make another document for considering multiple
interface node.
The problem of multiple interfaces is not only in network layer or Mobile
IPv6 (NEMO) but also
in below layer (layer 2). Like Link-layer Event Notification in DNA WG, it
is better to consider
link-layer to make perfect monami6 solutions.

Thanks..

Yong-Geun.



> -----Original Message-----
> From: monami6-bounces@ietf.org 
> [mailto:monami6-bounces@ietf.org] On Behalf Of Yong-Geun Hong
> Sent: Monday, October 24, 2005 10:39 AM
> To: monami6@ietf.org
> Subject: [Monami6] FW: 
> I-DACTION:draft-hong-multipleif-mn-pb-statement-00.txt 
> 
> 
>  
> Folks..
> 
> We have submitted an internet drat on analysis of multiple 
> interfaces in a mobile node to monami6 WG. You can find the 
> draft in the following link.
> http://www.ietf.org/internet-drafts/draft-hong-multipleif-mn-p
> b-statement-00
> .txt
> 
> Abstract:
> 
>    This document is an analysis of multiple interfaces in a 
> mobile node
>    using Mobile IPv6 or a mobile router using NEMO Basic Support.  The
>    current Mobile IPv6 and NEMO Basic Support are suitable 
> for a single
>    network interface.  When a mobile node or a mobile router has
>    multiple interfaces, the current Mobile IPv6 and NEMO Basic Support
>    cannot directly be used for them.  In this document, we 
> describe some
>    problems for a mobile node which has multiple network 
> interfaces when
>    the mobile node is using Mobile IPv6 as an aspect of a node.
> 
> 
> We have researched the interworking between CDMA and WLAN and 
> have implemented a mobile node using Mobile IPv6 and a mobile 
> router using NEMO Basic Support with one CDMA network 
> interface and one WLAN network interface. During this 
> research and implementation, we have met some problems and 
> described them in that draft.
> 
> Welcome any question and any comments.
> 
> Thanks..
> 
> Yong-Geun..
> 
> 
> 
> 
> 
> -----Original Message-----
> From: i-d-announce-bounces@ietf.org 
> [mailto:i-d-announce-bounces@ietf.org]
> On Behalf Of Internet-Drafts@ietf.org
> Sent: Friday, October 21, 2005 11:50 PM
> To: i-d-announce@ietf.org
> Subject: I-D ACTION:draft-hong-multipleif-mn-pb-statement-00.txt 
> 
> A New Internet-Draft is available from the on-line 
> Internet-Drafts directories.
> 
> 
> 	Title		: Analysis of multiple interfaces in a 
> Mobile Node
> 	Author(s)	: Y. Hong, et al.
> 	Filename	: draft-hong-multipleif-mn-pb-statement-00.txt
> 	Pages		: 10
> 	Date		: 2005-10-21
> 	
>    This document is an analysis of multiple interfaces in a 
> mobile node
>    using Mobile IPv6 or a mobile router using NEMO Basic Support.  The
>    current Mobile IPv6 and NEMO Basic Support are suitable 
> for a single
>    network interface.  When a mobile node or a mobile router has
>    multiple interfaces, the current Mobile IPv6 and NEMO Basic Support
>    cannot directly be used for them.  In this document, we 
> describe some
>    problems for a mobile node which has multiple network 
> interfaces when
>    the mobile node is using Mobile IPv6 as an aspect of a node.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-hong-multipleif-mn-p
> b-statement-00
> .txt
> 
> 
> 
> _______________________________________________
> Monami6 mailing list
> Monami6@ietf.org
> https://www1.ietf.org/mailman/listinfo/monami6


_______________________________________________
Monami6 mailing list
Monami6@ietf.org
https://www1.ietf.org/mailman/listinfo/monami6