Lost Password?
No account yet? Register
Home arrow Minutes arrow SISWG Minutes 2007-05-01 Oper. Procs.
SISWG Minutes 2007-05-01 Oper. Procs. PDF Print E-mail
Written by Matt Ball   
Tuesday, 18 December 2007
The SISWG Operating Procedures Subcommittee met on May 1, 2007 by teleconference. Here are the minutes from that meeting. Matt Ball took minutes and Eric Hibbard ran the meeting.

Attendance:
Bob Snively, Brocade
Gideon Avida, Decru
Doug Whiting, Hifn
Eric Hibbard, Hitachi Data Systems
Rob Elliott, HP
Shai Halevi, IBM
Glen Jaquette, IBM
John Geldman, Lexar
Walt Hubis, LSI Logic
Landon Noll, NeoScale
David Sheehy, PMC Sierra
Matt Ball, Quantum Corp
Bob Griffin, RSA Security

During this meeting, we discussed the proposed changes to the Security in Storage Working Group (SISWG) Operating Procedures, as distributed on April 30, 2007 (see attached files).

Concerning proxies and use of primary and secondary representatives:
- T10 is fairly loose with reassigning proxies.
- T10 needs a primary and alternate because these members require membership fees. We don't have membership fees (yet).


For voting purposes in Task Groups, should we require that a primary or secondary representative be present? --- Unanimous No


Should we require each company to designate a primary and optionally a secondary contact, per Task Group, for purposes of official notifications and letter ballots? -- unanimous Yes


Gideon: Should we add a letter ballot jeopardy? Consensus seemed to be yes.

Eric: Discussion Task Group vs. Work Group
- Should we make it like T11 or T10?
- Make sure that the Quorum issue is dealt with.
- Work Group letter ballot vs. Task Group letter ballot

Gideon: for Quorum, we should formalize what we're doing now.


Proposal: Voting Membership in SISWG is granted if an entity is a voting member of at least one SISWG Task Group. Membership is lost at the discretion of the SISWG chair from failure to respond to two out of four non-accelerated SISWG letter ballots or from losing voting membership in all SISWG Task Groups. A non-accelerated letter ballot is one that is outstanding for fewer than 30 days. -- unanimous yes


Bob S: From a legal standpoint, it is essential to keep a detailed list of attendance so that you can clearly show who has seen the patent slides.

Should we cancel a task group if there are fewer than 5 voting members?

A task group shall meet and achieve quorum at least twice a year.



Action Item: Eric has agreed to take this discussion and other comments into account and produce a second draft of the Operating Procedures.

The meeting was adjourned at 1:00 pm Pacific Time.


The following notes show comments that were received off-line:

Rob Elliot's comments:

I'm not sure if I'll make the call today (if so, only the first part of it).

On 4.2, if only the primary and secondary from a company can vote, then there needs to be a way to easily proxy to another company employee if they aren't attending a particular meeting. (e.g., accept an email from the primary or secondary allowing the other employee to vote).

[Landon] Restrict proxy to be different employee of same company


In 5, if a task group goes idle for a while, two face-to-face meetings per year may be overkill.

5.3 requiring a cell-phone doesn't seem appropriate. Some hotels are in cell phone problem zones, and not everyone has a cell phone.

5.4 "technical editor" was not defined as an officer earlier. Treasurer is the other officer position.

7.3 Stabilization is a waste of time.

7.4 Disposition is not a verb

General - should describe that IEEE membership is not required to be a SISWG task group member




Comments from Shai:

Matt, a few comments about this (I'm not sending to the group so as
not to spam people):

* Why mention a "treasurer" at all? Instead just say that additional
officers (beyong the three we now have) can be proposed by the chair
and approved by the group.

* Why the requirement that the chair be an IEEE member?

* What's the point of having "task officers" beyond the editor?

* "[...]who has attended two of the last three SISWG plenary meetings,"
What's "SISWG plenary meetings"? Why would you want to have those?

* The voting members should be clarified: Do you count each task
separately or together? If a company attends one 1619 meeting and one
1619.1 meeting, does it get voting rights?

* What's the point of section 5.4 ("Presiding officer")?

* What's the point of requiring 2/3 majority for anything? Especially
what's the point in requiring 2/3 majority to "force an early election
for an officer currently in office"?
 
< Prev
© 2017 IEEE Security in Storage Working Group
Joomla! is Free Software released under the GNU/GPL License.