On Mon, Jul 12, 2010 at 02:20:22PM -0700, Roland Dreier wrote: > So the best solution I can see is to declare that an IBoE GID must be an > IPv6 address coming from an EUI-64 Ethernet address for the > corresponding port; for MGIDs I guess we use the standard IPv6 mapping > to Ethernet address 33:33:xx:xx:xx:xx.
This is what I have been advocating.. A quibble about multicast - AFAIK this is unsolved. I think some spec needs to be agreed that documents what sort of multicast snooping operations switches need to do, ie if IGMP joins imply that IBoE traffic for the same DMAC is included in the join, or if IBoE requires a seperate IGMP type process on its own ether-type. That would make it much clearer what to do with MGIDs. IPv4 could be handled by mapping a IPv4 multicast address within an IPv6 mapped address, if necessary. It would be nice to at least have a plan on how to integrate a non-link local address, if that is ever necessary in future. An extended AH with an additional 48 DMAC field seems reasonable to me? Jason -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
