Re: [rprsg] URGENT: Agenda almost ready
Although we are now in a time bind for the upcoming meeting it is a pleasure
to see the tremendous response for contributions to get 802.17 off and
rolling at high speed. Certainly the performance Ad Hoc is important and we
do need to look for ways to provide that group with additional time. One
way of gaining that time is to run one of the ad hoc sessions in parallel
with the Exec meeting 7pm - midnight on Thursday evening. Probably some of
the participants will have gone home by then, but enough may be around to
make the session worth while. Another way of increasing the productivity of
the ad hoc group is to try to jump start it with email discussions over the
reflector (even an ad-hoc only reflector). Those discussions can include
presentations to be studied, followed by email discussion. Then by the time
the March meeting is underway the group can be ready to discuss in detail
the presentations they have already been reviewing.
Given the tremendous time pressure we have here, everyone needs to be
thinking about what we will want to be accomplishing at the May interim
meeting, and how much time it will take to do that. There is a whole week
available. How much of that time can we use productively? How much time
are people willing to give to an interim meeting?
Best regards,
Robert D. Love
Chair, Resilient Packet Ring Alliance
President, LAN Connect Consultants
7105 Leveret Circle Raleigh, NC 27615
Phone: 919 848-6773 Mobile: 919 810-7816
email: rdlove@xxxxxxxx Fax: 720 222-0900
----- Original Message -----
From: "Khaled Amer" <khaledamer@xxxxxxx>
To: <tak@xxxxxxxxx>; <stds-802-rprsg@xxxxxxxx>
Sent: Tuesday, February 20, 2001 1:21 AM
Subject: Re: [rprsg] URGENT: Agenda almost ready
>
> Mike,
>
> The problem is that I'm estimating that we'll need about 8 hours in the
> March meeting. We have a very short slot Monday morning, which will barely
> get us started on discussing what we want to accomplish during the week.
So
> the plan was to have both evenings for about 3 hours each.
>
> As you know, we have a lot to do in order to converge on how to proceed
and
> keep on running into time limits that stop us from making progress.
> I was hoping that we'll get all the time we need (well ... almost all the
> time we need!), and be able to get the starting-point issues resolved and
> start some simulation activities in an organized, coherent fashion. We
were
> unable to do so in the interim last time because we ran out of time to
> discuss things. As you saw, we've also been using the reflector for
> discussing a lot of issues as you saw, but we need the time to be able to
> make progress.
>
> In fact, even though we didn't really close on several open issues in
> January, for the benefit of the group, I've also already started some
> preliminary simulations for rings of regular Ethernet switches. But I want
> to make sure that we all do this type of work in an organized, coherent
> fashion.
>
> I know that I'm not making your life any easier, but I'm trying to do my
> best to facilitate for the group to provide what they signed up for.
>
> I think that we're going to have to divide the group into several adhoc
> groups very soon, which will work in parallel on one of the days (like
Wed)
> all day. Then they can each give a report to the main group on Thursday.
> This way we can all make progress and not miss the main thrust.
>
> All that said, on behalf of the group, I'd say that we'll leave it to your
> judgement. We all want what's best for the whole 802.17 WG. We believe
that
> we have an important part of the pie to deliver and that we need the time
to
> be able to do so. However, if you (as the Chair) see that you really need
> the slot, and that there is no other way out, and that not doing so would
> have a bigger impact on the progress of 802.17 than cutting short the perf
> adhoc group, then of course we'll cooperate.
>
> By the way, another evening for either of these activities is Wed evening
> after the social (let's say at 8:30 or 9:00). Maybe this can help
alleviate
> the problem a little bit, if people are not opposed to having sessions at
> that time.
>
> Khaled Amer
> President, AmerNet Inc.
> Architecture Analysis and Performance Modeling Specialists
> Address: 13711 Solitaire Way, Irvine, CA 92620
> Phone: (949)552-1114 Fax: (949)552-1116
> e-mail: khaledamer@xxxxxxx
> Web: www.performancemodeling.com
>
>
>
> ----- Original Message -----
> From: Mike Takefman <tak@xxxxxxxxx>
> To: Khaled Amer <khaledamer@xxxxxxx>; <stds-802-rprsg@xxxxxxxx>
> Sent: Monday, February 19, 2001 9:58 PM
> Subject: Re: [rprsg] URGENT: Agenda almost ready
>
>
> > Khaled,
> >
> > thanks for reminding me.
> >
> > So you could use monday night for the adhoc or I could
> > use monday night for the additional time.
> >
> > So I modify what I said before, one of monday or tuesday
> > for continuing .17 with Perf ad-hoc meeting on the other
> > day.
> >
> > mike
> >
> > Khaled Amer wrote:
> > >
> > > Mike,
> > >
> > > In response to your e-mail:
> > >
> > > >I would like schedule a meeting on Tuesday
> > > >night so that I can open up the schedule a
> > > >little (allow for more discussion).
> > > >I was thinking of a session from 8pm to 10:30pm.
> > >
> > > That was a time slot that we at the perf adhoc planned on using so
that
> it
> > > doesn't conflict with the mainstream of 802.17, since the adhoc
> participants
> > > are keen on not missing any of the sessions there. So, these evening
> slots
> > > (Monday and Tuesday) are the only ones we could use to avoid that
> conflict.
> > >
> > > >Please respond to the reflector with your
> > > >thoughts on whether this is a good or bad idea.
> > >
> > > Based on that, my input is that it's a 'bad idea'!
> > > :-)
> > >
> > > Khaled Amer
> > > President, AmerNet Inc.
> > > Architecture Analysis and Performance Modeling Specialists
> > > Address: 13711 Solitaire Way, Irvine, CA 92620
> > > Phone: (949)552-1114 Fax:
(949)552-1116
> > > e-mail: khaledamer@xxxxxxx
> > > Web: www.performancemodeling.com
> > >
> > > ----- Original Message -----
> > > From: Mike Takefman <tak@xxxxxxxxx>
> > > To: <stds-802-rprsg@xxxxxxxx>
> > > Sent: Monday, February 19, 2001 9:28 PM
> > > Subject: [rprsg] URGENT: Agenda almost ready
> > >
> > > >
> > > > People,
> > > >
> > > > I've got a preliminary agenda pulled together, but
> > > > it is really tight. Here is the rough view,
> > > > we work from 8 am to 6 pm each day.
> > > >
> > > > Monday AM Parallel sessions
> > > > - Performance Ad-Hoc
> > > > - Introduction to RPR for new antendees
> > > >
> > > > Monday Afternoon
> > > > - administrivia
> > > > - end-user presentations
> > > >
> > > > Tuesday
> > > > - Overall Scope / Objectives / Requirements
> > > > - Resiliency Objectives
> > > > - Interoperability Requirements
> > > >
> > > > Wednesday
> > > > - Bandwidth Management
> > > > - Simulation Results
> > > > - Action Items from previous meetings
> > > >
> > > > Thursday
> > > > - Perf Adhoc Report
> > > > - Voting Rights Administration
> > > > - Election of Officers
> > > > - Motions on Objectives
> > > > - Planning the next meeting
> > > >
> > > > I've had to cut people's presentations a little
> > > > to include time for questions. This will force people
> > > > to be concise :) I.E. a 30 minute presention is
> > > > 24 minutes to talk and 6 minutes of questions.
> > > >
> > > > I would like schedule a meeting on tuesday
> > > > night so that I can open up the schedule a
> > > > little (allow for more discussion).
> > > >
> > > > Right now there are not many tutorials scheduled
> > > > so I think we will not conflict at all.
> > > >
> > > > I was thinking of a session from 8pm to 10:30pm.
> > > >
> > > > Please respond to the reflector with your
> > > > thoughts on whether this is a good or bad idea.
> > > >
> > > > I will send out the current schedule to all
> > > > presenters tonight to make sure that I did not
> > > > miss anyone. If you did not see a message from
> > > > me with a pdf of the schedule then I missed you
> > > > so yell.
> > > >
> > > > thanks,
> > > >
> > > > mike
> > > >
> > > > --
> > > > Michael Takefman tak@xxxxxxxxx
> > > > Manager HW Engineering, Cisco Systems
> > > > Chair IEEE 802.17 Stds WG
> > > > 2000 Innovation Dr, Ottawa, Canada, K2K 3E8
> > > > voice: 613-271-3399 fax: 613-271-4867
> >
> > --
> > Michael Takefman tak@xxxxxxxxx
> > Manager HW Engineering, Cisco Systems
> > Chair IEEE 802.17 Stds WG
> > 2000 Innovation Dr, Ottawa, Canada, K2K 3E8
> > voice: 613-271-3399 fax: 613-271-4867
>