Hi Jouni, >> Requirement: DMM solutions SHOULD support multicast services.
So here it is a should. >> If a specific DMM solution does not support multicast services, an >> explanation MUST be provided. Why is it a must here? My comment on this requirement is in mobility area, we have never had these types of requirements. For example PMIPv6 was developed with no multicast support. MIPv6 and PMIPv6 were developed with no fast handover support. MIPSHOP WG worked on handover extensions to these protocols. As you know, Costas has changed his view "thinking wider". If we look back to the beginning of this discussion, i.e. Multimob meeting in Atlanta and Seil's presentation, we, at least myself, were mislead. In that presentation at http://www.ietf.org/proceedings/85/slides/slides-85-multimob-6.pptx We thought that he had a multicast requirement and a reasonable suggestion was to take it to dmm. However, if you look at his slide 6, he does have a requirement there but it is REQ1 from the DMM requirements draft :-). If existing requirements are covering what we want, as it seems with REQ 3/4/5, why not go with them? Regards, Behcet _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
