Hi all,
after the - somewhat uninformed discussion at IETF85 - chairs asked me
to restate requirements of a "fast handover solution" for Multicast
Mobility.
Here they are:
(i) Handover should be fast (this is only true for a direct pMAG/AR to
nMAG/AR solution such as
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast).
(ii) Multicast handover should be fully synchronized with unicast
handover (otherwise unicast and multicast states diverge as is a
well-known issue for the RAMS-approach, i.e.,
https://tools.ietf.org/html/draft-ietf-multimob-fast-handover).
(iii) Multicast handover solutions should tightly integrate with
unicast handover (only
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast
integrates with PFMIPv6 and FMIPv6).
(iv) Handover management should reuse standard mobility and multicast
protocol operations for easy implementation and deployment
(http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast
introduced the use of standard IGMP/MLD records for context description
in transfer, which has been copied several times).
(v) Multicast handover management should integrate ASM and SSM, as
well as IPv4 (IGMP) and IPv6 (MLD), which is only provided by
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast.
Based on these facts, chairs and AD proclaimed to re-decide on future
paths for Multimob fast handover solutions.
Cheers,
Thomas
--
Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group 20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt Fax: +49-40-42875-8409 °
_______________________________________________
multimob mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/multimob
