On Thu, 11 Mar 2004 [EMAIL PROTECTED] wrote: >Now, who can tell if multicast echo request is the primary >multicast debugging mechanism or not ??
Since there is no alternate mechanism, this has become the primary and preferred multicast debugging mechanism. If some mechanism is proposed which is better and is less liable to be misused, it will become the primary mechanism. The KAME project was working on a multicast traceroute tool for IPv6 a while ago. I have not personally used it. Probably Jinmei can comment further on this. Regards Suresh This communication is confidential and intended solely for the addressee(s). Any unauthorized review, use, disclosure or distribution is prohibited. If you believe this message has been sent to you in error, please notify the sender by replying to this transmission and delete the message without disclosing it. Thank you. E-mail including attachments is susceptible to data corruption, interruption, unauthorized amendment, tampering and viruses, and we only send and receive e-mails on the basis that we are not liable for any such corruption, interception, amendment, tampering or viruses or any consequences thereof. -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
