Sri, I take advantage of your email to insert another comment.
I have already posted this comment one year ago. I have also stated it at the microphone in Maastricht recent IETF meeting: If you cite rfc3775 (Mobile IPv6) in the node req document then please cite rfc3963 (NEMOv6, mobile networks) too, because the latter is a simple extension of the former. It is hard to get code accepted in the linux mainline kernel, because of high reliability requirements. For MIP6 it took several years, with at least a couple of simultaneous multiple person projects geared at that. Alex Le 20/08/2010 17:22, Sri Gundavelli a écrit :
Couple of comments on Section 9.0 (Mobility): draft-ietf-6man-node-req-bis-05 1.) When Mobile IPv6 was designed, one important feature that made into the protocol is the support for Route Optimization. The ability for a mobile node to provide the information on the direct (non-anchor or non-triangular) path to a Correspondent Node. This was not possible in Mobile IPv4, as any change requirement to IPv4 did not make much sense. This is one feature of Mobile IPv6 that stands out. The semantics of RO, say Type-II RH, is part of the basic IPv6 feature. Most IPv6 stacks have support for these options and in most cases the RO procedure as well. Given this, It is very important that the IPv6 Correspondent Node functionality is mandated on every IPv6 node. However, the Home Agent functionality on IPv6 routers, or the Mobile Node stack on a IPv6 node, can be optional, that is fine. But, its important that the end-points has natural RO support. 2.) I'd additionally remove the comments around lack of deployment experience around the protocol. This comment applies to practically every IPv6 feature, SEND or other extensions. In fact with Mobile IPv4 being a core mobility protocol in CDMA, we probably have bit more related experience on the node requirements from IPv6 node perspective. 3.) Section 9.0 should be reviewed by MEXT, NETLMM and NETEXT working groups, so the node requirements with respect to IP Mobility are properly presented. Regards Sri -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
-- Alexandru Petrescu CEA LIST Ingénieur Chercheur tél 0169089223 [email protected] http://www-list.cea.fr -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
