[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [netlmm] [MEXT] [netext] NEXTEXT2: first draft of the bof description
Hi Hesham,
>Hi Raj,
>
>I told Marcelo I'll go through the exercise from the beginning again, but I
>can't help respond to this comment.
>> Quite simply, the answer is that in certain deployments it is not feasible
>> to expect DS(MIP6) capability on hosts. An operator cannot expect that every
>> host connecting to the network implements (DS)MIP6. The operator has no
>> control of the hosts or their capabilities to a large extent. The only thing
>> the operator can and does control is the network, and hence the
>> consideration to add such capabilities to a deployment which used network
>> based mobility protocol.
>=> No one I know can get a 3G data card to access the Internet from their PC
>without having to install a piece of software on their PC to make it work.
>So I think your assumption that the operator cannot mandate software on the
>host is questionable, because they already do (unfortunately).
The situation that you describe above was the same when 802.11 first rolled around as well.
You had to install a piece of software that came with the PC card. But that has changed with
wifi now being an integral part of the notebook computers.
And I think you could expect 3G chipsets and access built-in as well in due course of time. At least I know of a few
operators in the US (as well as notebook manufacturers) who offer such net/notebook computers,
i.e with integrated 3G access. I do not know what additional sw is loaded on these but at least the end user
is not installing anything else.
Does it imply that such hosts will include the software that would enable host mobility? Its an open question (i.e unknown)
and will depend largely on operator choices and vendors.
-Raj
>Hesham