RE: [Ipoverib] Please read - proposed WG termination

["Yaron Haviv" <[e-mail]>]

Jerry,

You can see how it was solved in other interconnects (e.g. Sonet)
It was added to the RFC, by requesting hosts to support UNARP RFC

I don't think we can get away with a pure IB L2 implementation, unless
you have some suggestions, how can an IPoIB traffic be rerouted to a new
path/port without updating the sender tables, or somehow making sure
that the new node uses the same GID+QP+LID as the failed one ?

The UNARP option is used to remotely invalidate an ARP entry (forcing a
new addr resolution), But there can be other solutions 

Yaron

> -----Original Message-----
> From: H.K. Jerry Chu [mailto:[e-mail]]
> Sent: Monday, August 29, 2005 2:48 PM
> To: [e-mail]; Yaron Haviv
> Cc: [e-mail]; [e-mail]
> Subject: RE: [Ipoverib] Please read - proposed WG termination
> 
> Yaron,
> 
> If the issue and possible solutions lie completely within L2
> (i.e. IB) the work doesn't seem to belong here. If it involves
> layer 3 you will have to convince the ADs, who are in doubt
> if there is sufficient interest on the approved charter work,
> let alone any new work.
> 
> Jerry
> 
> >X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
> >Content-class: urn:content-classes:message
> >MIME-Version: 1.0
> >Subject: RE: [Ipoverib] Please read - proposed WG termination
> >Date: Mon, 29 Aug 2005 21:02:51 +0300
> >X-MS-Has-Attach:
> >X-MS-TNEF-Correlator:
> >Thread-Topic: [Ipoverib] Please read - proposed WG termination
> >Thread-Index: AcWswJ1mSOybAIwqRaia2Jea2ZPrtgAAiKtg
> >From: "Yaron Haviv" <[e-mail]>
> >To: "H.K. Jerry Chu" <[e-mail]>, <[e-mail]>
> >Cc: <[e-mail]>, <[e-mail]>
> >Content-Transfer-Encoding: 8bit
> >X-MIME-Autoconverted: from quoted-printable to 8bit by
> jurassic.eng.sun.com id
> j7TI3ElM455753
> >
> >Jerry,
> >
> >I believe there is one issue that deserves further attention
> >Which is delivering highly available IPoIB solutions
> >
> >In traditional GbE MAC faking techniques can be used to fail over
> >between hosts or between routers (e.g. VRRP)
> >Unfortunately this is not applicable to IPoIB (given the IB routing &
SA
> >structure)
> >
> >Going into more commercial/enterprise environments this becomes a
real
> >necessity, today some vendors (including us) use proprietary
solutions
> >however a standard approach is required
> >
> >I proposed few directions in the pass to address the problem, e.g.
using
> >UNARP (like Sonet does) or using the SA/SM
> >
> >Yaron
> >
> >> -----Original Message-----
> >> From: [e-mail] [mailto:[e-mail]]
On
> >> Behalf Of H.K. Jerry Chu
> >> Sent: Monday, August 29, 2005 1:38 PM
> >> To: [e-mail]
> >> Cc: [e-mail]; [e-mail]
> >> 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
> >> [e-mail]
> >> https://www1.ietf.org/mailman/listinfo/ipoverib
> >


_______________________________________________
IPoverIB mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ipoverib