I don't see a performance drop in our implementation. an additional table lookup is not needed for forwarding. you need to figure out the scope of the DA of course, but that is needed for link-local/multicast anyway.
The issue is that you also have to check the source address and drop the packet if you would be crossing a scope boundary for the source address...
I think that a lot of routers already (in IPv4) have the capability of doing fast classification/filtering based on both source and destination addresses (among other things), so I don't know how much of a performance hit this will cause for a hardware-based routers. And, as was already pointed out, you need to do it for link-local addresses, anyway. Margaret -------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
