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

marcelo bagnulo braun <marcelo@it.uc3m.es> Thu, 29 January 2009 20:44 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 BCCBE28C185; Thu, 29 Jan 2009 12:44:28 -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 EE2C83A6A83; Thu, 29 Jan 2009 12:44:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.561
X-Spam-Level:
X-Spam-Status: No, score=-5.561 tagged_above=-999 required=5 tests=[AWL=1.038, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 bUI+Jxc+cIWG; Thu, 29 Jan 2009 12:44:27 -0800 (PST)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by core3.amsl.com (Postfix) with ESMTP id 875FF3A6A64; Thu, 29 Jan 2009 12:44:25 -0800 (PST)
Received: from marcelo-bagnulos-macbook-pro.local (134.pool85-53-135.dynamic.orange.es [85.53.135.134]) by smtp01.uc3m.es (Postfix) with ESMTP id 2AA59B4D496; Thu, 29 Jan 2009 21:44:04 +0100 (CET)
Message-ID: <49821513.8060307@it.uc3m.es>
Date: Thu, 29 Jan 2009 21:44:03 +0100
From: marcelo bagnulo braun <marcelo@it.uc3m.es>
User-Agent: Thunderbird 2.0.0.18 (Macintosh/20081105)
MIME-Version: 1.0
To: Marc Blanchet <marc.blanchet@viagenie.ca>
References: <932b01c98117$dcb28e10$8310fe81@etri.info> <498027F9.8050604@it.uc3m.es> <49820BB6.9070405@viagenie.ca> <49820D13.2060601@it.uc3m.es> <20090129202644.GZ34382@cisco.com> <4982129D.3060503@it.uc3m.es> <49821348.3000904@viagenie.ca>
In-Reply-To: <49821348.3000904@viagenie.ca>
X-TM-AS-Product-Ver: IMSS-7.0.0.3116-5.5.0.1026-16432.002
Cc: julien.laganier.IETF@googlemail.com, Scott Brim <swb@employees.org>, mif@ietf.org, mext@ietf.org
Subject: Re: [MEXT] [mif] 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-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

Marc Blanchet escribió:
> marcelo bagnulo braun a écrit :
>   
>> Scott Brim escribió:
>>     
>>> Excerpts from marcelo bagnulo braun on Thu, Jan 29, 2009 09:09:55PM
>>> +0100:
>>>  
>>>       
>>>> makes sense to me
>>>>
>>>> Marc Blanchet escribió:
>>>>    
>>>>         
>>>>> to me, the main difference is that the 'multiple interface' issue
>>>>> is not bound to mobility, and more specifically to mobility
>>>>> protocols (mobileIPv4, mobileipv6, nemo, ...).
>>>>>
>>>>> Therefore, the MIF work is not scoping about mobility protocols and
>>>>> shall not require mobility protocols.
>>>>>
>>>>> I would see that if some part of the MIF work is looking at the
>>>>> mobility protocols, then these should be then "transfered" to MEXT.
>>>>>       
>>>>>           
>>> Even without mobility considerations, the issue of how to handle
>>> multiple interfaces overlaps with IntArea, RRG, and Behave (those are
>>> the ones I can think of offhand).  Have you seen the arguments, for
>>> example, about session initialization when multiple addresses can be
>>> in play simultaneously at both ends?  I apologize but I still don't
>>> understand the MIF boundaries.
>>>
>>>   
>>>       
>> I wrote a draft a long time ago about the problems for selecting the
>> source address in multiaddressed hosts, not sure if this is related to
>> what you asking about...
>>
>> you can check it at
>>
>> http://www.watersprings.org/pub/id/draft-bagnulo-6man-rfc3484-update-00.txt
>>     
>
> there is an address selection design team that is looking at this currently.
>   
mmm, not really
maybe i missing somehting, but i understnad that the scope of the design 
team is limited to the automatic update of the rfc3484 policy table, and 
they are not dealing with the issue of how the properly select the 
source address, for instance, in the case that you need to retry due to 
ingress filtering and the like

regards, marcelo


> Marc.
>
>   
>> regards, marcelo
>>
>>     
>>> Thanks ... Scott
>>>
>>>   
>>>       
>
>
>   

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