Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

Re: suggested changes to 802 tutorial procedures

I concur with Roger's suggesstions and have one additional change.  The
list of valid reasons for holding a tutorial should be expanded to include
"Topics of wide interest to 802 participants".  An example of a well
attended tutorial that fell under this classification is one Geoff and I
did a number of years ago that reviewed the status of international cabling
standards.   Along with that expanded purpose should be an explicit
statement against overly commercial presentations, possibly with some basic
guidelines to dos and don'ts of tutorials.  For simplicity in getting rules
changes approved, the statement and guidelines should be a separately
prepared document on the web site, pointed to with a hyper-link from the
"tutorial request form", or appended to that form, and not an expansion of
our rules.

Best regards.

Robert D. Love
Program Manager, IBM ACS - US
Chair IEEE 802.5 Token Ring Working Group
500 Park Offices                   Phone: 919 543-2746
P. O. Box 12195 CNPA/656           Fax: 419 715-0359
Research Triangle Park, NC 27709, USA    E-Mail:

"Roger B. Marks" <> on 02/29/2000 12:58:36

Sent by:

Subject:  suggested changes to 802 tutorial procedures

I've expressed to Jim my concern about the 802 tutorial procedures.
While the Chair's Guidelines present a good description of an
appropriate tutorial, there are no real procedures to ensure that
tutorials are not overly commercial or to inform other working groups
regarding potential overlap of interests. There has also been poor
advance notification of the tutorials and their schedules.

Jim asked me to make some suggestions. I suggest the following:

web. Few people know about this form, and it is hard to track down.

(2) Include on the form a reference to and link to the "802 Chair's
Guidelines on IEEE 802 Tutorials"
<> so that proposers
get help understanding the rules.

(3) Add the following question (taken from the Chair's Guidelines) to
the tutorial request form:

Purpose of Tutorial (choose one and explain):
(a) Explore possible new directions for 802 efforts
(b) Summarize ongoing major work of Study Group or WG or TAG.
(c) Describe basic 802 or other standards process.

(4) Change the approval process, which currently leaves the SEC
members in the dark until Dawn issues an agenda. I suggest changing
the relevant section of the Chair's Guidelines from:

>Mechanics of Tutorials:
>- Hosted by SEC member or Study Group Chair.
>- Announced to SEC reflector before meeting.
>- Scheduled through Classic Consulting/Buzz Rigsbee
>- Conflicts to be resolved by Executive Secretary and SEC chair
>based on most importance to 802.


>Mechanics of Tutorials:
>- Hosted by SEC member or Study Group Chair.
>- Tutorial Request Form posted to SEC reflector for comment.
>- No less than 7 days after posting, SEC Chair may affirm that
>proposed tutorial is appropriate and then schedule it.
>- Conflicts will be resolved by the SEC chair, but priority will
>generally be by order of request.

I also suggest that the "APPROVAL AND CONFIRMATION" section of the
Tutorial Request Form be changed from:

>All official tutorial requests must sent to Dawn Williams at
> for final approval and confirmation with copies to
>Buzz Rigsbee and to Jim Carlo
> .  A confirmation of your request indicating time slot
>assigned will be sent within 10 days of your submission.


>Tutorial requests must be submitted by an SEC member or Study Group
>Chair to the SEC reflector. After not less than seven days for SEC
>reveiw, the SEC Chair may approve and schedule the meeting, with
>notification to the SEC reflector.

(5) I suggest deleting the following section of the Chair's Guidelines:

>All official tutorial request forms must be submitted at least 45
>days prior to the start of the next IEEE 802 LMSC Plenary Meeting.
>Please refer to the future meetings list on the IEEE 802 Web Site

No one pays attention to it anyway, and the first-come, first-serve
rule should stimulate earlier requests.