On Nov 15, 2012, at 1:03 AM, Behcet Sarikaya wrote: > > I think we are reading too much into multicast and unicast should be > designed in an integrated manner. > > The fact is that multicast is considered as an area of specialization, > it requires knowledge of very different protocols than we are > accustomed to in mobility.
"Requirement: DMM solutions SHOULD support multicast services. If a specific DMM solution does not support multicast services, an explanation MUST be provided." To me that reads basically "do not break foundations for multicast unless you have a valid & documented reason for it". If we look e.g. into RFC625 multicast wording that is there very briefly but gives a hint to a developer where to head to. That is the level I would expect DMM documents should aim to. - Jouni > Let dmm deal with its current charter that does not include a word of > multicast and if everything goes well we can come back and discuss dmm > multicast. > > Regards, > > Behcet _______________________________________________ dmm mailing list [email protected] https://www.ietf.org/mailman/listinfo/dmm
