-----BEGIN PGP SIGNED MESSAGE----- I'm working on an Internet Draft that describes current practice for IPv4 Multicast routing. This Internet Draft includes a table of IPv4 multicast groups that I've sort of picked up over time that are generally black-holed. Following is the table that I have; do you use the same table of known-bad groups? Are there any other groups that you believe should be included in this table? 224.0.1.2/32: SGI "Dogfight" game 224.0.1.3/32: RWHOD 224.0.1.22/32: SVRLOC 224.0.1.24/32: MICROSOFT-DS 224.0.1.35/32: SVRLOC-DA 224.0.1.39/32: Cisco's Rendezvous Point Announcement Protocol 224.0.1.40/32: Cisco's Rendezvous Point Discovery Protocol 224.0.1.60/32: HP's Device Discovery Protocol 224.0.2.2/32: Sun's Remote Procedure Call Protocol 229.55.150.208/32: Norton "Ghost" disk duplication software Please send me direct email and I'll summarize the results back to these lists (wg-multicast, nanog, and mboned). Thank you, === Bill Nickless http://www.mcs.anl.gov/people/nickless +1 630 252 7390 PGP:0E 0F 16 80 C5 B1 69 52 E1 44 1A A5 0E 1B 74 F7 nickless@mcs.anl.gov -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.8 for non-commercial use <http://www.pgp.com> iQCVAwUBOs0RVKwgm7ipJDXBAQHUUQP9EJOcCFZIsZTv4UH+S3/Hf9pYiWd7XSf9 QXFTwfUL7y31Xke0gp+PNq/Cyc0Xo+vkw6zmLgHQpGrkOW9MMXDSe1O2jsuJut/8 a2RYlnysl7U13QZSu3CZoElJAaAjtLEDAR3auj5cM0jsY3CRgtQ7POhzNMv/nw9R qpXBaCWFlaM= =LyCp -----END PGP SIGNATURE-----