RE: [Ipoverib] Please read - proposed WG termination

Vivek Kashyap <kashyapv@us.ibm.com> Tue, 30 August 2005 06:49 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E9zw0-0007Zo-Ll; Tue, 30 Aug 2005 02:49:28 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1E9zvy-0007ZH-Nw for ipoverib@megatron.ietf.org; Tue, 30 Aug 2005 02:49:27 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA24798 for <ipoverib@ietf.org>; Tue, 30 Aug 2005 02:49:23 -0400 (EDT)
Received: from e35.co.us.ibm.com ([32.97.110.133]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1E9zxO-0006nj-Pq for ipoverib@ietf.org; Tue, 30 Aug 2005 02:50:57 -0400
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e35.co.us.ibm.com (8.12.10/8.12.9) with ESMTP id j7U6mxBN196090 for <ipoverib@ietf.org>; Tue, 30 Aug 2005 02:49:01 -0400
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [9.17.195.167]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VERS6.7) with ESMTP id j7U6mxLB473352 for <ipoverib@ietf.org>; Tue, 30 Aug 2005 00:48:59 -0600
Received: from d03av01.boulder.ibm.com (loopback [127.0.0.1]) by d03av01.boulder.ibm.com (8.12.11/8.13.3) with ESMTP id j7U6mvBG005322 for <ipoverib@ietf.org>; Tue, 30 Aug 2005 00:48:57 -0600
Received: from sig-9-65-32-141.mts.ibm.com (sig-9-65-32-141.mts.ibm.com [9.65.32.141]) by d03av01.boulder.ibm.com (8.12.11/8.12.11) with ESMTP id j7U6muZV005287; Tue, 30 Aug 2005 00:48:56 -0600
Date: Mon, 29 Aug 2005 23:40:38 -0700
From: Vivek Kashyap <kashyapv@us.ibm.com>
X-X-Sender: kashyapv@localhost.localdomain
To: Yaron Haviv <yaronh@voltaire.com>
Subject: RE: [Ipoverib] Please read - proposed WG termination
In-Reply-To: <35EA21F54A45CB47B879F21A91F4862F753355@taurus.voltaire.com>
Message-ID: <Pine.LNX.4.62.0508292326040.5289@localhost.localdomain>
References: <35EA21F54A45CB47B879F21A91F4862F753355@taurus.voltaire.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 22bbb45ef41b733eb2d03ee71ece8243
Cc: margaret@thingmagic.com, Michael Krause <krause@cup.hp.com>, Bill_Strahm@McAfee.com, ipoverib@ietf.org
X-BeenThere: ipoverib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipoverib>, <mailto:ipoverib-request@ietf.org?subject=unsubscribe>
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>
Sender: ipoverib-bounces@ietf.org
Errors-To: ipoverib-bounces@ietf.org

On Tue, 30 Aug 2005, Yaron Haviv wrote:

> IB availability is defined today and one can migrate between ports and
> given the use of UD, can easily migrate between HCA either completely or
> relatively transparent to the network stack using the IB methods or the
> same IP address update using the same methods deployed today on all OS
> offerings.  In the end, it really is an implementation issue and fixing
> the OpenSM implementations not an IETF issue to resolve any
> deficiencies.
>
> Mike
>
> <Yaron>
>
> Mike, the solution that may work over IB is sending gratuitous ARPs
>
> This doesn't cover all the cases, e.g. how would VRRP or MAC faking work
> over IB ?
>
>
>
> By nature an IPoIB endpoint also contains QPs, so even theoretically an
> SM cannot deal with the problem
>

Am I right in assuming that you are suggesting LID + QPN + GID failover? 
LID is certainly beyond IPoIB. QPN + GID are in the ambit.

Vivek

> If we want to address interoperability between different vendors I
> believe we need to address it through standardization
>
>
>
> If you believe there is a solution that addresses my concerns and can be
> done in a standard/interoperable way please let me know
>
>
>
> Yaron
>
>> -----Original Message-----
>> From: ipoverib-bounces@ietf.org [ mailto:ipoverib-bounces@ietf.org
> <mailto:ipoverib-bounces@ietf.org> ] On
>> Behalf Of H.K. Jerry Chu
>> Sent: Monday, August 29, 2005 1:38 PM
>> To: ipoverib@ietf.org
>> Cc: margaret@thingmagic.com; Bill_Strahm@McAfee.com
>> Subject: [Ipoverib] Please read - proposed WG termination
>>
>> Hi folks,
>>
>> With the DHCP over IB draft in IESG's hand, we are done with all
>> the basic IPoIB work, including the architecture (informational),
>> encapsulation, and DHCP (standard tracked). Now seems a good time
>> to decide the next step for the WG.
>>
>> The work on IPoIB connected mode and most of the MIB drafts started
>> a while back (2003/2002). Over the years the interest/participation
>> level on these work has not been high, and now the work seems to drag
>> on indefinitely. The AD has recently questioned whether the remaining
>> work should be continued or not.
>>
>> The following is a quick update on their status:
>>
>> 1. IPoIB connected mode
>> draft-ietf-ipoib-connected-mode-00.txt
>> updated recently
>>
>> 2. MIB drafts
>> IPoIB Textual Conventions MIB
>> draft-ietf-ipoib-ibmib-tc-mib-06.txt
>>
>> IPoIB InfiniBand Interfaces MIB
>> draft-ietf-ipoib-ibif-mib-07.txt
>>
>> IPoIB subnet Management Agent MIB
>> draft-ietf-ipoib-subnet-mgmt-agent-mib-07.txt
>>
>> IPoIB Channel Adapter MIB
>> draft-ietf-ipoib-channel-adapter-mib-06.txt
>>
>> IPoIB Baseboard Management Agent MIB
>> draft-ietf-ipoib-baseboard-mgmt-agent-mib-02.txt
>>
>> IPoIB performance Management Agent MIB
>> draft-ietf-ipoib-perf-mgmt-agent-mib-03.txt
>>
>> The above 6 MIB drafts have gone through the
>> MIB doctor (Randy Presuhn) review late 2003 and
>> updated accordingly. All the updated drafts expired
>> in April 2005.
>>
>> 3. IPoIB Subnet Manager MIB
>> draft-ietf-ipoib-subnet-manager-mib-00.txt
>>
>> Submitted 3/2004 but has expired too.
>>
>> If you want to see any of the above work continue in the WG,
>> AND is willing to participate to get the work completed, please
>> speak up NOW! You will have until Sep. 20 to do so. After
>> that unless there is evidence a "sufficient" interest level
>> on any of the work above still exists, the WG will be disbanded
>> (or become dormant in order to handle the on-going work on
>> the standard-tracked RFCs) and the unfinished work abandoned.
>>
>> Note that authors of the above drafts may choose to resubmit
>> their drafts as individual submissions if they want to continue
>> to pursue their work at IETF.
>>
>> Thank you!
>>
>> Jerry & Bill
>>
>> IPoIB co-chairs
>>
>>
>> _______________________________________________
>> IPoverIB mailing list
>> IPoverIB@ietf.org
>> https://www1.ietf.org/mailman/listinfo/ipoverib
>
> _______________________________________________
> IPoverIB mailing list
> IPoverIB@ietf.org
> https://www1.ietf.org/mailman/listinfo/ipoverib
>
>

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