Re: [Ipoverib] Comments on draft-ietf-ipoib-link-multicast-04.txt

Roy Brabson <rbrabson@us.ibm.com> Wed, 07 May 2003 17:39 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09583 for <ipoverib-archive@lists.ietf.org>; Wed, 7 May 2003 13:39:14 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47HlR805849; Wed, 7 May 2003 13:47:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h47HkI805773 for <ipoverib@optimus.ietf.org>; Wed, 7 May 2003 13:46:18 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA09538 for <ipoverib@ietf.org>; Wed, 7 May 2003 13:36:43 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DSsR-0003CN-00 for ipoverib@ietf.org; Wed, 07 May 2003 13:38:47 -0400
Received: from e31.co.us.ibm.com ([32.97.110.129]) by ietf-mx with esmtp (Exim 4.12) id 19DSsQ-0003Bn-00 for ipoverib@ietf.org; Wed, 07 May 2003 13:38:46 -0400
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e31.co.us.ibm.com (8.12.9/8.12.2) with ESMTP id h47Hd6Qs211712; Wed, 7 May 2003 13:39:06 -0400
Received: from d03nm118.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.193.82]) by westrelay02.boulder.ibm.com (8.12.9/NCO/VER6.5) with ESMTP id h47Hd5X3095664; Wed, 7 May 2003 11:39:06 -0600
In-Reply-To: <OFFFA16205.D161C7A5-ON88256D1F.00557D51@us.ibm.com>
To: Vivek Kashyap <vivk@us.ibm.com>
Cc: ipoverib@ietf.org, "H.K. Jerry Chu" <Jerry.Chu@eng.sun.com>
Subject: Re: [Ipoverib] Comments on draft-ietf-ipoib-link-multicast-04.txt
MIME-Version: 1.0
X-Mailer: Lotus Notes Release 6.0 September 26, 2002
From: Roy Brabson <rbrabson@us.ibm.com>
X-MIMETrack: S/MIME Sign by Notes Client on Roy Brabson/Raleigh/IBM(Release 6.0|September 26, 2002) at 05/07/2003 01:26:39 PM, Serialize by Notes Client on Roy Brabson/Raleigh/IBM(Release 6.0|September 26, 2002) at 05/07/2003 01:26:39 PM, Serialize complete at 05/07/2003 01:26:39 PM, S/MIME Sign failed at 05/07/2003 01:26:39 PM: The cryptographic key was not found, Serialize by Router on D03NM118/03/M/IBM(Release 6.0.1 [IBM]|April 17, 2003) at 05/07/2003 11:39:05, Serialize complete at 05/07/2003 11:39:05
Message-ID: <OF869F17B5.FED6F957-ON85256D1F.005E8C57-85256D1F.005FD37C@us.ibm.com>
Date: Wed, 07 May 2003 13:26:40 -0400
Content-Type: text/plain; charset="US-ASCII"
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>, <mailto:ipoverib-request@ietf.org?subject=unsubscribe>
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Post: <mailto:ipoverib@ietf.org>
List-Help: <mailto:ipoverib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>, <mailto:ipoverib-request@ietf.org?subject=subscribe>

> <VK> As I noted in my previous mail... the onus is on the router. The
> router is required to listen to multicast packets on both: a) all-router
> MGID or b) broadcast-GID
> 
> We could make that explicit in the draft. The second option, which
> apparently Roy favours is to specify that the nodes must, if the 
relevant
> MGID doesn't exist, send the packet to the MGID corresponding to the
> all-router MGID. This option is fine but it then adds another 
requirement:
> 
>    All IPoIB nodes MUST request creation request for all-router MGID
>    whether the corresponding IP layer joins the all-router IP address or
>    not.

I'm not sure I understand why an IPoIB host need to request creation of 
the all-router MGID (I do understand why an IPoIB router must, though). 
Wouldn't it be sufficient to try to "SendOnlyNonMember" join the 
all-router MGID and, if the all-router MGID doesn't exist, stop?  If the 
all-router MGID doesn't exist, then it means there are no IP routers on 
the IPoIB link who can forward the request to any off-link listeners. And, 
since the multicast group MGID doesn't exist (otherwise, the IPoIB host 
would have sent to that MGID), we already know there aren't any on-link 
IPoIB listeners.

Roy
_______________________________________________
IPoverIB mailing list
IPoverIB@ietf.org
https://www1.ietf.org/mailman/listinfo/ipoverib