Re: [Mip6] concensus on [issue94] fixing encapsulation mechanism inIPv4 network

[Vijay Devarapalli <vijay.devarapalli at azairenet.com>]

Sri Gundavelli wrote:
> I prefer option "A". 
>
> Reason:
> > From the MIP4 experience, many times and for various reasons,
> deployments choose UDP Tunneling even in the absence of NAT. The
> ability for the client to hint that choice from any connected
> network is important. 

The problem is that the client may not know. It might be
setting the flag all the time. Do we have a mechanism to
say when the MN should be setting this bit?

> Besides the "U" bit in the request, the HA should have some
> config policy on to accept "forced" UDP tunneling or not. 

Agree on this.

Vijay

So,
> the final control can be given to the HA in the form of policy, 
> but the client should be able to specify its preferences.
>
>
> Sri
>
>
>
> -----Original Message-----
> From: Hesham Soliman [mailto:Hesham at elevatemobile.com] 
> Sent: Wednesday, March 28, 2007 12:33 AM
> To: 'Keiichi SHIMA'
> Cc: mip6 at ietf.org
> Subject: [Mip6] concensus on [issue94] fixing encapsulation mechanism inIPv4
> network
>
> Kiichi, all, 
>
> I think we've seen the different angles of this issue now and it's time to
> close it. 
> So I suggest that we choose one of the two options listed below. 
>
> Folks, 
>
> The "new" issue is about whether or not the MN can request one form of
> tunnelling (i.e. UDP) when sending a BU to the HA. The two choices we have
> are:
>
> A. Add a flag that allows the MN to request UDP tunnelling interface
> (independently of the presence of a NAT) from the HA, when sending the BU.
> The HA can override the MN's request. Or, 
>
> B. Do nothing. I.e. the MN sends the BU as described in the spec today and
> the HA tells the MN in the BA whether it should use UDP tunnelling or IP in
> IP. 
>
> Please express your preference for one of the options above. Let's not make
> things complicated and get into negotiating the tunnelling mechanism, one of
> the two above will suffice. 
>
> I'll leave it open till next Tuesday. 
>
> Thanks,
> Hesham
>
>
>
> _______________________________________________
> Mip6 mailing list
> Mip6 at ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6
>
> _______________________________________________
> Mip6 mailing list
> Mip6 at ietf.org
> https://www1.ietf.org/mailman/listinfo/mip6


_______________________________________________
Mip6 mailing list
Mip6 at ietf.org
https://www1.ietf.org/mailman/listinfo/mip6