Version: 1
-Previous: 63ba32d815bb8c31365613a40dc400207dcb3b33
-Head: 1c9cb4576f95c0d2cc7bf96d33cc6efe5f6c313d
+Previous: 6a14eb6a550d68f0a614831316e9e1da5af94577
+Head: 6c95ce3f56a9107a63d0b8da0333ca9feaf868b0
Applied:
opt_mc_av: 1c9cb4576f95c0d2cc7bf96d33cc6efe5f6c313d
+ one_mc_join: 6c95ce3f56a9107a63d0b8da0333ca9feaf868b0
Unapplied:
addr_size: 8de02c47fbf595132105a7050ad6f755f49f9a7a
Hidden:
--- /dev/null
+Bottom: ff1f0e0cc0c31d7a9b01b551462a6a3a0612e4b9
+Top: ff1f0e0cc0c31d7a9b01b551462a6a3a0612e4b9
+Author: Sean Hefty <sean.hefty@intel.com>
+Date: 2011-04-01 15:58:19 -0700
+
+ibacm: Join only the base multicast group if using SA path resolution
+
+If the ACM service is configured to use the SA to resolve path
+record data, then only join the base multicast group. We only
+need to join other groups if we're creating path records based
+on multicast data, using the acm route protocol.
+
+Signed-off-by: Sean Hefty <sean.hefty@intel.com>
+
+
+---
+
+