RE: [Ipoverib] Scheduling for the Salt Lake City (SLC) IETF
Brian Forbes <bforbes@brocade.com> Tue, 13 November 2001 21:41 UTC
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18090 for <ipoverib-archive@odin.ietf.org>; Tue, 13 Nov 2001 16:41:23 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id QAA26811 for ipoverib-archive@odin.ietf.org; Tue, 13 Nov 2001 16:41:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26795; Tue, 13 Nov 2001 16:40:55 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id QAA26761 for <ipoverib@optimus.ietf.org>; Tue, 13 Nov 2001 16:40:53 -0500 (EST)
Received: from mail.brocade.com (asbestos.brocade.com [63.121.140.244]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18061 for <ipoverib@ietf.org>; Tue, 13 Nov 2001 16:40:49 -0500 (EST)
Received: from hq-ex-c2.brocade.com (hq-ex-c2 [192.168.126.35]) by mail.brocade.com (8.8.8+Sun/8.8.8) with ESMTP id NAA18674; Tue, 13 Nov 2001 13:40:15 -0800 (PST)
Received: by hq-bes-c2.brocade.com with Internet Mail Service (5.5.2653.19) id <WTDQG0QN>; Tue, 13 Nov 2001 13:40:14 -0800
Message-ID: <176B85B0D4E0D411BA5200508B692E0A05DB67D6@hq-ex-1.brocade.com>
From: Brian Forbes <bforbes@brocade.com>
To: 'Bill Strahm' <bill@sanera.net>, "'ipoverib@ietf.org'" <ipoverib@ietf.org>
Subject: RE: [Ipoverib] Scheduling for the Salt Lake City (SLC) IETF
Date: Tue, 13 Nov 2001 13:40:09 -0800
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: ipoverib-admin@ietf.org
Errors-To: ipoverib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IP over InfiniBand WG Discussion List <ipoverib.ietf.org>
X-BeenThere: ipoverib@ietf.org
As you may recall, the IB switch MIB is partially modelled on the MIB described in draft-ietf-ipfc-fcmgmt-int-mib-07.txt, aka the "FA MIB", for fibre channel, including the eventual ability to describe multiple node types. The FA MIB, which seems to provide significant value to end users and has been implemented by multiple vendors, has nevertheless caused considerable IETF discussion and seems to require significant architectural work. A number of people are working out the FA MIB's future direction. Based on these considerations, Brocade proposes to defer submitting an update of the IB switch MIB until the architectural direction is set for the FA MIB or its successor, and will not need time on the Salt Lake agenda. Brian Forbes Brocade Communications -----Original Message----- From: Bill Strahm [mailto:bill@sanera.net] Sent: Tuesday, November 06, 2001 9:26 AM To: ipoverib@ietf.org Subject: [Ipoverib] Scheduling for the Salt Lake City (SLC) IETF We currently have two slots 15:45-16:45 Tuesday and 15:30-17:30 Wednesday Do not book airline tickets on this schedule however, I fully expect it to change, with the caveat that we will have a Tuesday meeting (the only day with 1 hour meetings) This gives us three hours. Topics I would like to discuss are Questions about MIB design - There are MANY new MIBs that have been hitting the reflector, I would like to discuss design issues on all of them and see where they need to go. If you are an author of a MIB, and would like some time to discuss it, please e-mail the list and request a time slot (Chair hat off, author hat on) I would like a slot to talk about the Connection MIB (Chair hat back on). I am hoping to hear from the following people Brian Forbes - Switch MIB Bill Strahm - Connection MIB Bill Swortwood - SMA MIB Carl Yang - SM MIB Sean Harnedy - IBIF MIB Have I missed any ??? For the IP encapsulation I am hoping to hear from Vivek Kashyup - Overall Architecture Design Team - Issues List Others ??? The goal for the IP encapsulation team will be to have ALL design issues closed by the end of the meeting and be able to sit down after the meeting and get a WG draft published that has rough consensus as expressed at the meeting (Note: This is not WG consensus, that will occur on the mailing list) Please speak up (even if you are listed above) with requests for talks, I would like you to summarize the issues that you want discussed and the amount of time that you will need... (Author Hat on, chair hat off) For the connection MIB, I would like the following Is this a WG item, and does it meet at least some of the requirements of a Channel adapter MIB ? There are several objects that are not Infiniband Objects - Can they be managed through other means, should we ask the IBTA to add them, should they be removed from the draft ? 10 Minutes (Chair Hat On) I would also like to talk briefly to determine what the overall layout of object trees underneath the Infiniband allocation should look like. Currently Sean is handling them in the TC MIB - Is this good for everyone ? 5 minutes (Sean, if you would talk about this in your time, that would be great - I'll even throw in this 5 minutes for it <G>) Hope to see you in SLC. Bill +========+=========+=========+=========+=========+=========+=========+ Bill Strahm Software Development is a race between Programmers Member of the trying to build bigger and better idiot proof software Technical Staff and the Universe trying to produce bigger and better bill@sanera.net idiots. (503) 601-0263 So far the Universe is winning --- Rich Cook _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org http://www.ietf.org/mailman/listinfo/ipoverib _______________________________________________ IPoverIB mailing list IPoverIB@ietf.org http://www.ietf.org/mailman/listinfo/ipoverib
- [Ipoverib] Scheduling for the Salt Lake City (SLC… Bill Strahm
- RE: [Ipoverib] Scheduling for the Salt Lake City … Bill Swortwood
- RE: [Ipoverib] Scheduling for the Salt Lake City … Brian Forbes