<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45">
<TITLE>RE: [openib-general] Multicast address aliasing in IPoIB</TITLE>
</HEAD>
<BODY>
<BR>
<BR>
<P><FONT SIZE=2>> -----Original Message-----</FONT>
<BR><FONT SIZE=2>> From: Hal Rosenstock [<A HREF="mailto:halr@voltaire.com">mailto:halr@voltaire.com</A>] </FONT>
<BR><FONT SIZE=2>> Sent: Wednesday, September 15, 2004 12:09 AM</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> On Thu, 2004-09-09 at 22:43, Roland Dreier wrote:</FONT>
<BR><FONT SIZE=2>> > I see no reason to modify the IPoIB multicast mapping just </FONT>
<BR><FONT SIZE=2>> because the </FONT>
<BR><FONT SIZE=2>> > Linux kernel does not yet have support for it.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Agreed.</FONT>
</P>
<P><FONT SIZE=2>OK. Fine with me.</FONT>
<BR><FONT SIZE=2>Note that what it means that Gen2 will be fully compliant. Gen1 may not </FONT>
<BR><FONT SIZE=2>be interoperable / ipoib compliant - because they just can't without a very</FONT>
<BR><FONT SIZE=2>ugly hack.</FONT>
</P>
<P><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> The only issue I see is where the scope and PKey would come from to </FONT>
<BR><FONT SIZE=2>> form the MGID. The scope could default to link local (2). I </FONT>
<BR><FONT SIZE=2>> would presume the PKey would come from the IPoIB interface somehow.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> -- Hal</FONT>
<BR><FONT SIZE=2>> </FONT>
</P>
<P><FONT SIZE=2>Can we leave the pkey part of the MGID blank (e.g. zeroes) to be filled by the </FONT>
<BR><FONT SIZE=2>underlying driver ? If so, then it should be OK.</FONT>
</P>
<BR>
</BODY>
</HTML>