Re: [MEXT] Multiple interfaces problems in MEXT and mif

Hui Deng <denghui02@gmail.com> Thu, 29 January 2009 10:11 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: mip6-archive@megatron.ietf.org
Delivered-To: ietfarch-mip6-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AF1303A6A22; Thu, 29 Jan 2009 02:11:25 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 82E873A6A22; Thu, 29 Jan 2009 02:11:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.927
X-Spam-Level:
X-Spam-Status: No, score=-0.927 tagged_above=-999 required=5 tests=[AWL=-1.026, BAYES_00=-2.599, FRT_MEETING=2.697, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id If0GXzCC5Z3Z; Thu, 29 Jan 2009 02:11:23 -0800 (PST)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.168]) by core3.amsl.com (Postfix) with ESMTP id A8C2D3A6359; Thu, 29 Jan 2009 02:11:22 -0800 (PST)
Received: by wf-out-1314.google.com with SMTP id 27so8386746wfd.31 for <multiple recipients>; Thu, 29 Jan 2009 02:11:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=iGEjR7U2tbWUOKmSCwLrBPxGKLhut87v9UDvg5mfLd0=; b=Yd4l+o6+nM70N9dlk5M3DSf9PB+vcqDAZIHx7HIR006oEYmtjZb4+9Wb5oQOL3VDRx OlpcUrLVcv91pclp9/vYdkPUKikk70EjhsKQLa75+Tj3O7mc5/uGKTUQP03luCc5Mzml 0jyG6uiT15UXSJMsz7BszTPIlRdLXts7ZjtjI=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=pCJw6PSM84vmMrSVB9YZt5F5GafM6JqRkxLEMFPHpqJmEY1JPjHtOEcT/7SduPr3bg TNxN80ZvFwmYXnsVBOT/zi4Fudvh16AfJVZ6roUWCvIjd3EJwgwLLZgkRhDAYp1DmIVe fuN3S/FAlTaO4NAT4iZ/U6zcfF4CKIxi9ddAg=
MIME-Version: 1.0
Received: by 10.142.191.5 with SMTP id o5mr572268wff.326.1233223864590; Thu, 29 Jan 2009 02:11:04 -0800 (PST)
In-Reply-To: <49816184.1080502@it.uc3m.es>
References: <544a01c981ba$81512a10$8310fe81@etri.info> <49816184.1080502@it.uc3m.es>
Date: Thu, 29 Jan 2009 18:11:04 +0800
Message-ID: <1d38a3350901290211g2bab9cfdhaa760405151bb3bc@mail.gmail.com>
From: Hui Deng <denghui02@gmail.com>
To: marcelo bagnulo braun <marcelo@it.uc3m.es>
Cc: julien.laganier.IETF@googlemail.com, mif@ietf.org, mext@ietf.org
Subject: Re: [MEXT] Multiple interfaces problems in MEXT and mif
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1045685914=="
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

Hi, Marcelo

For yoru question about what mif's scope at the moment, Jari already made
the comments on
http://www.ietf.org/mail-archive/web/mif/current/msg00050.html

There are also several PS drafts you could refer to:
http://tools.ietf.org/id/draft-blanchet-mif-problem-statement-00.txt
http://tools.ietf.org/id/draft-hui-ip-multiple-connections-ps-01.txt
http://tools.ietf.org/id/draft-hong-multipleif-mn-pb-statement-00.txt

thanks

-Hui

2009/1/29 marcelo bagnulo braun <marcelo@it.uc3m.es>;

> Hi Hong,
>
> what is the scope of MIF?
> I mean, in the bof wiki page there is no charter proposed, is there a
> charter somewhere?
> In particular, is MIF going to work in MIPv6/NEMO related issues?
>
> Regards, marcelo
>
>
> Hong Yong-Geun escribió:
>
>>  Hi, Marcelo.
>>  Thanks for your comments.
>>  I agree that  the current MEXT WG charter already has several items about
>> supporting multiple interfaces.
>>  My documents are old version which were submitted to monami6 WG at 64th
>> IETF meeting and they were
>> not updated properly. So, it seems that some contents are similar to the
>> works in MEXT WG.
>> I will update my documents to focus on mif's scope.
>>  It is appreciate to understand that (even though the scope of mif is not
>> fixed) mif has different directions to
>> MEXT.
>>  Best regards.
>>  Yong-Geun.
>>
>> -----원본 메시지-----
>> *From:* "marcelo bagnulo braun" <marcelo@it.uc3m.es>;
>> *From Date:* 2009-01-28 오후 6:40:09
>> *To:* "Hong Yong-Geun" <yghong@etri.re.kr>;
>> *Cc:* "mext@ietf.org"; <mext@ietf.org>;, "mif@ietf.org"; <mif@ietf.org>;, "
>> julien.laganier.IETF@googlemail.com"; <julien.laganier.IETF@googlemail.com>;,
>> "denghui02@gmail.com"; <denghui02@gmail.com>;
>> *Subject:* Re: Multiple interfaces problems in MEXT and mif
>>
>>
>>
>> Hi,
>>
>> In the current MEXT charter there are several items about supporting
>> multiple interfaces, including the following two:
>>
>> - A document explaining the motivations for a node using multiple
>> interfaces and the scenarios where it may end up with multiple
>> global addresses on its interfaces [Informational]
>>
>> - An analysis document explaining what are the limitations for
>> mobile hosts using multiple simultaneous Care-of Addresses and Home
>> Agent addresses using Mobile IPv6, whether issues are specific to
>> Mobile IPv6 or not [Informational].
>>
>> I think this is very similar to the scope of one of you documents at
>> least, so i would find very strange that the same work is chartered in
>> two different working groups.
>>
>> Moreover, we do have wg documents for these two, but we find very hard
>> to find reviewers for those, which makes me think that there is not much
>> interest on these. So, if you find a more motivated crew to do the work,
>> that would be great, we can either do it in mext or soemwhere else, if
>> people feels that needs to be done, but that is certainly not the
>> feeling i am getting from the input in mext
>>
>> Regards, marcelo
>>
>>
>>
>> Hong Yong-Geun escribi?:
>> >
>> > Hi, all in MEXT and mif.
>> >
>> > >
>> > In IETF mif (Multiple Interface) mailing list
>> > (_https://www.ietf.org/mailman/listinfo/mif_
>> > <https://www.ietf.org/mailman/listinfo/mif>),
>> >
>> > we now discuss the host which would like to use multiple interfaces.
>> >
>> > I understand that MEXT WG is also related to the use of multiple
>> > interfaces of a host
>> > using Mobile IPv6 or a mobile router using NEMO Basic Support and
>> > their variants
>> >
>> > MEXT WG is focuing on monami6 related topic (multiple CoA, Multiple
>> > HoA, and Multple HA, etc.,)
>> > and extedning Mobile IPv6 and NEMO for these, but mif is not related
>> > to this direction.
>> > In mif, source address selection, routing and DNS control protocol are
>> > consideration items
>> > due to multiple interfaces of a host.
>> >
>> > >
>> > For mif's scope, Jari Arkko made some comments and classification of
>> > problems.
>> >
>> > _http://www.ietf.org/mail-archive/web/mif/current/msg00050.html_
>> >
>> > Among these classification which includes access selection, split DNS,
>> > configuration reconciliation,
>> > routing, address selection, tunnel multihoming, and the communication
>> > way between the host and
>> > the network about their policies regarding all of the above, Jari said
>> > that access selection is already
>> > coverd in RFC 5113 and tunnel multihoming is already covered in MEXT
>> > WG work items.
>> >
>> > >
>> > At monami6 WG in 64th IETF meetinng, I submitted and presented two
>> > Internet Drafts.
>> >
>> > - Analysis of multiple interfaces in a Mobile Node
>> >
>> > _http://tools.ietf.org/id/draft-hong-multipleif-mn-pb-statement-00.txt_
>> >
>> > - Virtual network interface for multiple interfaces in a Mobile node
>> > using Mobile IPv6
>> >
>> > _http://tools.ietf.org/id/draft-hong-virtualif-mn-mipv6-00.txt_
>> > <http://tools.ietf.org/id/draft-hong-virtualif-mn-mipv6-00.txt>
>> >
>> > Because these two drafts were not in the monami6 WG's scope and
>> > virtual network interface draft was
>> >
>> > implementation specific, there were not adoped in monami6 WG's work
>> > items. The intentions of two drafts
>> > are supporting multiple interfaces of a host without extending Mobile
>> > IPv6/NEMO.
>> >
>> > >
>> > I think that multiple interfaces problems of a host are related to
>> > both Mobile IP/NEMO specific issues and
>> > general network issues. Mobile IP/NEMO specific issues are related to
>> > extending of Mobile IP/NEMO and
>> > these are already studied in MEXT WG and general network issues which
>> > were not related to
>> > Mobile IP/NEMO could be studied in mif. As same manner, I think that
>> > my drafts could be discussed and
>> > developed in mif. In the first draft (Analysis document), I classified
>> > multiple interface problems into
>> > Mobile IPv6-sepcific issues, General network issues, and heterogeneous
>> > environment issues.
>> >
>> > >
>> > Including Hui Deng in mif, with regarding to these drafts, they want
>> > to hear comments from MEXT WG's point of view,
>> > because it seems that these drafts are quite related to monami6/MEXT
>> > WG. So, I ask MEXT to review whether there are
>> >
>> > some overlap between MEXT works and my drafts or not.
>> >
>> > It is appreciate to give comments.
>> >
>> > >
>> > Best regards.
>> >
>> > Yong-Geun.
>> >
>>
>>
>
_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext