Re: [netext] I-D Action: draft-ietf-netext-logical-interface-support-03.txt

<Basavaraj.Patil@nokia.com> Thu, 08 September 2011 15:59 UTC

Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: netext@ietfa.amsl.com
Delivered-To: netext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 323C521F85BB for <netext@ietfa.amsl.com>; Thu, 8 Sep 2011 08:59:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.639
X-Spam-Level:
X-Spam-Status: No, score=-102.639 tagged_above=-999 required=5 tests=[AWL=-0.040, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CXwBm39iFAAZ for <netext@ietfa.amsl.com>; Thu, 8 Sep 2011 08:59:38 -0700 (PDT)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id CD7B721F85B5 for <netext@ietf.org>; Thu, 8 Sep 2011 08:59:37 -0700 (PDT)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.3) with ESMTP id p88G1PQB014781; Thu, 8 Sep 2011 19:01:26 +0300
Received: from smtp.mgd.nokia.com ([65.54.30.7]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 8 Sep 2011 19:01:21 +0300
Received: from 008-AM1MMR1-004.mgdnok.nokia.com (65.54.30.59) by NOK-AM1MHUB-03.mgdnok.nokia.com (65.54.30.7) with Microsoft SMTP Server (TLS) id 8.2.255.0; Thu, 8 Sep 2011 18:01:20 +0200
Received: from 008-AM1MPN1-051.mgdnok.nokia.com ([169.254.1.86]) by 008-AM1MMR1-004.mgdnok.nokia.com ([65.54.30.59]) with mapi id 14.01.0323.007; Thu, 8 Sep 2011 18:01:20 +0200
From: <Basavaraj.Patil@nokia.com>
To: <sgundave@cisco.com>, <ryuji@us.toyota-itc.com>
Thread-Topic: [netext] I-D Action: draft-ietf-netext-logical-interface-support-03.txt
Thread-Index: AQHMbakgfzZ83rhZDUeFJBDNzcp++5VCjljvgACiFQA=
Date: Thu, 8 Sep 2011 16:01:19 +0000
Message-ID: <CA8E4F30.10555%basavaraj.patil@nokia.com>
In-Reply-To: <CA8D4A79.27BF5%sgundave@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.12.0.110505
x-originating-ip: [172.19.59.19]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <01F6685D9BCFC943887D41997AAE272E@nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 08 Sep 2011 16:01:21.0038 (UTC) FILETIME=[8D0E2AE0:01CC6E40]
X-Nokia-AV: Clean
Cc: netext@ietf.org
Subject: Re: [netext] I-D Action: draft-ietf-netext-logical-interface-support-03.txt
X-BeenThere: netext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Mailing list for discusion of extensions to network mobility protocol, i.e PMIP6. " <netext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netext>, <mailto:netext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/netext>
List-Post: <mailto:netext@ietf.org>
List-Help: <mailto:netext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netext>, <mailto:netext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Sep 2011 15:59:39 -0000

Sri,

Thanks for the reference.
A few questions from the configuration of the MN in the experiment
mentioned in the paper:

1. Are multiple interfaces active at the same time (eth0 and eth1)?

2. How does the bridge interface handle the scenario when you have
multiple interfaces simultaneously active and operational? From a PMIP6
standpoint, does the MN (assuming attachment to different MAGs) obtain
different prefixes from the MAGs?

3. How does SLAAC work when the bridge IF is used? Given that you have
different EUI48s associated with Eth0 and Eth1, what does the br IF use
for address config?

-Raj

On 9/7/11 6:21 PM, "ext Sri Gundavelli" <sgundave@cisco.com> wrote:

>Hi Raj:
>
>
>
>On 9/7/11 2:57 PM, "Basavaraj.Patil@nokia.com" <Basavaraj.Patil@nokia.com>
>wrote:
>
>> 
>> Following up on Brian's point, the I-D says in Sec 4.1:
>> 
>> "
>> Depending on the OS support, it might
>>       be possible to use more than one physical interface at a time --
>>       so the node is simultaneously attached to different media -- or
>>       just to provide a fail-over mode.  Controlling the way the
>>       different media is used (simultaneous, sequential attachment, etc)
>>       is not trivial and requires additional intelligence and/or
>>       configuration at the logical interface device driver.  An example
>>       of this type of solution is the Logical interface, which is
>>       defined in this document, or the bonding driver (a Linux
>>       implementation).
>> 
>> "
>> 
>> Do you have examples of implementations wherein a logical interface is
>> able to use multiple physical interfaces simultaneously?
>> 
>
>I can think of the Linux bridge control interface, where the physical
>interface are put in a bridge mode.
>
>Since you asked :)
>
>http://www.mendeley.com/research/applicability-virtual-interface-intertech
>no
>logy-handoffs-proxy-mobile-ipv6/
>
>
>> The multiple-care-of-address solution for MIP6 enables the MN to be
>> simultaneously attached to an HA via different interfaces. But in such a
>> model, you have different CoAs associated with those physical
>>interfaces.
>> 
>
>Slight difference though. In the MCoA model, the HoA is bound to virtual
>interface, however the tunnel is established from the IP addresses
>associated with a physical interface. The relation between the two being
>the
>tunnel providing the routing path for the home address on the virtual
>interface.
>
>Regards
>Sri
>
>
>
>