Re: [Monami6] Fwd: I-D ACTION:draft-bagnulo-shim6-mip-00.txt

[Nicolas Montavont <[e-mail]>]

Marcelo,

marcelo bagnulo braun wrote:

> Hi Nicolas,
>
> El 14/07/2005, a las 15:49, Nicolas Montavont escribió:
>
>> Marcelo,
>>
>> Actually I read the draft and I think it is a really interesting I-D.
>>
>
> thanks
>
>> And I think it fits very well to the scope of Monami6, since one of 
>> our goal is also to identify relation between Monami6 and other WGs. 
>> The success of our meeting also rely on our ability to identify these 
>> relations.
>>
>> I think your work may provide additional requirements for Monami6 
>> when developing solutions at one point of time.
>>
>> I think it would be nice to present it during the BOF, even if maybe 
>> it is too soon to talk about this. But the conclusion of your 
>> presentation could be to identify if we should clearly add in our 
>> charter the production of documents which makes the relation between 
>> Monami6 and other related WGs.
>>
>> Otherwise, I'd like to ask you one question about the I-D. At the end 
>> of paragraph 2, you wrote:
>>
>> If an alternative CoA is used as alternative locator, then the
>>   communication will run directly between the MN and the CN in a kind
>>   of SHIM based RO mode, recovering from the outage.  However, in this
>>   case, care must be taken because the alternative CoA may become
>>   unavailable after movement.
>>
>>
>> I assume that in this case, the communication simply uses the CoA as 
>> an address (I mean without the MIP6 mechanism) that is why if you 
>> change this CoA (let say because of a movement), you won't be able to 
>> update it.
>
>
> well, actually the text is more vague than this... the point is that 
> the SHIM work currently does not considers the mobility scenario, so 
> adding/removing addresses is still somehow undefined. So, the point 
> that the draft is trying to make is that this particular issue needs 
> further study, in order to understand how the shim can deal with this.
> imho, there are some modes of operation of the shim that could deal 
> with this situation, but i am not ssure if it would be a clean 
> approach (architecturally speaking) I mean if we are laying the SHIM 
> over the MIP, then maybe it wouldn't be the cleanest approach to 
> expose the CoAs to the shim, if you see what i mean.

I can understand that. What you are saying encourage me even more to 
consider your work in Monami6, because ideally I think all issues 
related to Mobility and Multihoming should be dealt in Monami6. Again, 
this is one of our long-term goal, i.e. to unify all work on the 
combination of Multihoming and mobility.

>
> hope this answers your question.

Sure.

Nicolas

>
> regards, marcelo
>
>
>>  And you was able to use this CoA because you set this address in the 
>> SHIM context. My question is the following: once you change CoA, 
>> can't you update the SHIM context to use the new CoA in this case? 
>> (excuse me if my question seems obvious, but I am not familiar with 
>> SHIM6...)
>>
>
>> Nicolas
>>
>> Thierry Ernst wrote:
>>
>>> Hi Marcelo,
>>>
>>> I didn't read the draft first, but, how does it relate to mobility ?
>>> Monami6 is not simply about host multihoming, but about solving
>>> multihoming issues specifi to MIP or NEMO enabled MNs and MRs
>>>
>>> Since Shim6 folks have said they wouldn't spend time looking into the
>>> mobility problem, I fail to see how this is related to Monami6 (I write
>>> this without reading the draft your mention, so my comment may not hold
>>> if you clarify this).
>>> So, could you clarify on the ML, and match with the current BOF
>>> description and WG charter ?
>>> Thierry
>>>
>>>
>>>
>>> On Thu, 14 Jul 2005 11:52:07 +0200
>>> marcelo bagnulo braun <[e-mail]> wrote:
>>>
>>>
>>>> Hi folks,
>>>>
>>>> we have submitted a draft considering the interaction between SHIM and
>>>> MIP. We think that the shim could be part of a solution for host 
>>>> multihoming and some of the possibilities for this are explored in the
>>>> draft.
>>>>
>>>> We would like to have the opportunity to present it in the monami6 bof
>>>> in Paris, do you think this would be ok?
>>>>
>>>> Regards, marcelo
>>>>
>>>> Inicio mensaje reenviado:
>>>>
>>>>
>>>>> De: [e-mail]
>>>>> Fecha: 13 de julio de 2005 21:50:01 GMT+02:00
>>>>> Para: [e-mail]
>>>>> Asunto: I-D ACTION:draft-bagnulo-shim6-mip-00.txt
>>>>> Responder a: [e-mail]
>>>>>
>>>>> A New Internet-Draft is available from the on-line Internet-Drafts 
>>>>> directories.
>>>>>
>>>>>
>>>>>     Title        : SHIM - MIPv6 Interaction
>>>>>     Author(s)    : M. Bagnulo, E. Nordmark
>>>>>     Filename    : draft-bagnulo-shim6-mip-00.txt
>>>>>     Pages        : 8
>>>>>     Date        : 2005-7-13
>>>>>     
>>>>>   In this note, we explore the interaction between the SHIM
>>>>>   protocol and MIPv6 protocol, identifying potential benefits and
>>>>>   difficulties. The analysis will consider the two modes of
>>>>>   operation of MIPv6: the Bidirectional Tunnel (BT) mode where the
>>>>>   communication is routed through the Home Agent and the Route
>>>>>   Optimization (RO) mode, where the communication flows directly
>>>>>   between the Correspondent node and the mobile node.
>>>>>
>>>>> A URL for this Internet-Draft is:
>>>>> http://www.ietf.org/internet-drafts/draft-bagnulo-shim6-mip-00.txt
>>>>>
>>>>> To remove yourself from the I-D Announcement list, send a message to
>>>>> [e-mail] with the word unsubscribe in the body
>>>>> of the message.
>>>>> You can also visit
>>>>> https://www1.ietf.org/mailman/listinfo/I-D-announce
>>>>> to change your subscription settings.
>>>>>
>>>>>
>>>>> Internet-Drafts are also available by anonymous FTP. Login with 
>>>>> the username
>>>>> "anonymous" and a password of your e-mail address. After logging in,
>>>>> type "cd internet-drafts" and then
>>>>>     "get draft-bagnulo-shim6-mip-00.txt".
>>>>>
>>>>> A list of Internet-Drafts directories can be found in
>>>>> http://www.ietf.org/shadow.html
>>>>> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>>>>
>>>>>
>>>>> Internet-Drafts can also be obtained by e-mail.
>>>>>
>>>>> Send a message to:
>>>>>     [e-mail].
>>>>> In the body type:
>>>>>     "FILE /internet-drafts/draft-bagnulo-shim6-mip-00.txt".
>>>>>     
>>>>> NOTE:    The mail server at ietf.org can return the document in
>>>>>     MIME-encoded form by using the "mpack" utility.  To use this
>>>>>     feature, insert the command "ENCODING mime" before the "FILE"
>>>>>     command.  To decode the response(s), you will need "munpack" or
>>>>>     a MIME-compliant mail reader.  Different MIME-compliant mail
>>>>>     readers exhibit different behavior, especially when dealing with
>>>>>     "multipart" MIME messages (i.e. documents which have been split
>>>>>     up into multiple messages), so check your local documentation on
>>>>>     how to manipulate these messages.
>>>>>        
>>>>>        
>>>>> Below is the data which will enable a MIME compliant mail reader
>>>>> implementation to automatically retrieve the ASCII version of the
>>>>> Internet-Draft.
>>>>> Content-Type: text/plain
>>>>> Content-ID: <[e-mail]>
>>>>>
>>>>>

_______________________________________________
Monami6 mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/monami6