On Mon, 2007-02-26 at 10:37, Or Gerlitz wrote: > Hal Rosenstock wrote: > > On Sun, 2007-02-25 at 05:48, Or Gerlitz wrote: > > >> Just to have us agree on the quote, it is from section 4 of rfc 4392 > >> (page 14) eg in http://www.ietf.org/rfc/rfc4392.txt > > >>> at the time of creating an IB multicast group, multiple values such as the > >>> P_Key, Q_Key, Service Level, Hop Limit, Flow ID, TClass, MTU, etc. have > >>> to be > >>> specified. These values should be such that all potential members of the > >>> IB > >>> multicast group are able to communicate with one another when using them. > > >> OK, I suggest to remove this spec limitation, > > > IMO you would need to get the IB spec changed first in order to do this. > > do you refers to this? > > > What about the description og P_Key in MCMemberRecord (table 210 on p. > > 908 which is compliance) which states: > > > > "All members of the multicast group shall have full membership in the > > partition indicated by the partition key." > > if yes, indeed, this also has to be changed.
Yes, for one. There may be others; I didn't look exhaustively at the spec for this. -- Hal > Or. > _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
