>>>>> On Thu, 11 Mar 2004 23:53:05 -0500 (EST), >>>>> Suresh Krishnan <[EMAIL PROTECTED]> said:
>> 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. Our experimental implementation of multicast traceroute for IPv6 is described in a paper available at the following URL: http://www.isoc.org/isoc/conferences/inet/00/cdproceedings/1c/1c_2.htm But in any event, I don't think it helps this particular discussion. It's just experimental, and I've even never written an I-D on this (partly because the standardization of IPv4 multicast traceroute has been pending). For the original discussion, I agree with Pekka; I prefer to (continue to) allow responding to multicasted echo requests by default, for almost the same reasons he provided. JINMEI, Tatuya Communication Platform Lab. Corporate R&D Center, Toshiba Corp. [EMAIL PROTECTED] -------------------------------------------------------------------- IETF IPv6 working group mailing list [EMAIL PROTECTED] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
