Hi Danny, I am removing all previous conversation because it all got mixed up. Let's start afresh.
I read you dhcp draft also. There is confusion in several levels. Your API draft talks about different applications on a MN needing different types of mobility services. Your DHCPv6 draft seems to give a solution on how a host can get different types of addresses/prefixes from DHCPv6 server, so is it for a host or an application? Prefix or address is assigned for an interface, that is another well known concept which your draft seem to completely ignore, i.e. a host may have multiple interfaces. Another concept is (as I already mentioned) topological correctness. If MN changes subnet, its previous prefix becomes topologically incorrect. Either it has to get a new prefix or there must be some system support, e.g. host routes. Of course another case is anchoring, like in 3GPP or in MIP. If you are anchored your prefix does not change. So you seem to ignore all these and instead introduce three types of addresses among which the sustained IP address/prefix is the key to your solution. Sustained address/prefix has this magical property: the IP address used at the beginning of the session remains usable despite the movement of the mobile host. and then you say access network anchoring, corresponding network anchoring, or some other solution can provide sustained address/prefixes. what does corresponding network anchoring mean? I have a feeling that what your drafts are saying that right now we don't know but we anticipate in the future some ways will be found to make sustained IP addresses. Is this true? BTW, your DHCPv6 draft says that DHCPv6 server can give me a Sustained address/prefix but it does not say how it will be different than the fixed one? Suppose we want to develop an access network anchoring for sustained IP addresses. What about the needs for signaling? I have a feeling that a host running very many applications, like in today's smart phones, and so many smart phones in the system that is going to involve huge amount of signaling to get/release sustained address/prefixes, right? My conclusion from all of the above is that, I think what you propose sounds like a flashy idea but it seems to me that the complications involved in any solution is intractable. Unless you can show me otherwise. Regards, Behcet _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
