Folks, There was discussion about necessity of APIs for DMM yesterday. Let's continue that discussion here.
It is true that IETF's primary focus is "protocol design". But when it's necessary, IETF also defines APIs. See, IPv6 basic socket API, for example. And, as a very relevant item, see RFC 5014, source address selection API. In RFC 5014, there's even consideration to "mobility", in terms of apps selecting home address vs care-of address as their source address. I think by now it's clear to everyone that we can no longer treat all IP flows equally when it comes to providing IP mobility treatment to them. This is already recognized in the charter. The way to take apps' mobility need into account is to give them an API. RFC 5014 already made an attempt at that, but fell short. Now that we have a better understanding of the issues, we should extend that API. Once we define that API, other APIs (OS specific ones that are not under the control of IETF) can follow the same path. Discussion welcome. Alper _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
