RE: [Ipoverib] Please read - proposed WG termination

Michael Krause <krause@cup.hp.com> Tue, 30 August 2005 16:37 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EA96q-0002uf-Uf; Tue, 30 Aug 2005 12:37:16 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EA96p-0002ua-UC for ipoverib@megatron.ietf.org; Tue, 30 Aug 2005 12:37:16 -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 MAA22477 for <ipoverib@ietf.org>; Tue, 30 Aug 2005 12:37:12 -0400 (EDT)
Received: from palrel10.hp.com ([156.153.255.245]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EA98N-00062x-3E for ipoverib@ietf.org; Tue, 30 Aug 2005 12:38:53 -0400
Received: from esmail.cup.hp.com (esmail.cup.hp.com [15.0.65.164]) by palrel10.hp.com (Postfix) with ESMTP id 080E629C1; Tue, 30 Aug 2005 09:37:09 -0700 (PDT)
Received: from MK73191c.cup.hp.com (mk731916.cup.hp.com [15.8.80.134]) by esmail.cup.hp.com (8.9.3 (PHNE_29774)/8.8.6) with ESMTP id JAA00848; Tue, 30 Aug 2005 09:29:46 -0700 (PDT)
Message-Id: <6.2.0.14.2.20050829184022.02241a48@esmail.cup.hp.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.0.14
Date: Mon, 29 Aug 2005 18:41:03 -0700
To: Yaron Haviv <yaronh@voltaire.com>, ipoverib@ietf.org
From: Michael Krause <krause@cup.hp.com>
Subject: RE: [Ipoverib] Please read - proposed WG termination
In-Reply-To: <35EA21F54A45CB47B879F21A91F4862F753355@taurus.voltaire.com >
References: <35EA21F54A45CB47B879F21A91F4862F753355@taurus.voltaire.com>
Mime-Version: 1.0
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 162d87dc0b780d17da9b1934777fd451
Cc: margaret@thingmagic.com, Bill_Strahm@McAfee.com
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>
Content-Type: multipart/mixed; boundary="===============1527552243=="
Sender: ipoverib-bounces@ietf.org
Errors-To: ipoverib-bounces@ietf.org

At 03:29 PM 8/29/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
>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

I believe this is an OpenIB / OpenSM or IBTA problem space to solve not the 
IETF.

Mike

>
>Yaron
>
> > -----Original Message-----
> > From: 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