Re: [802SEC] +++EC Email Ballot+++ENDS 13 JAN+++motion to hold plenary sessions outside NA
I can live with that wording too!
Matthew Sherman, Ph.D.
Senior Member Technical Staff
BAE SYSTEMS, CNIR
Office: +1 973.633.6344
email: matthew.sherman@baesystems.com
-----Original Message-----
From: owner-stds-802-sec@ieee.org [mailto:owner-stds-802-sec@ieee.org]
On Behalf Of Rigsbee, Everett O
Sent: Friday, December 31, 2004 2:07 AM
To: STDS-802-SEC@listserv.ieee.org
Subject: Re: [802SEC] +++EC Email Ballot+++ENDS 13 JAN+++motion to hold
plenary sessions outside NA
Bill, OK, that works for me !!!
We (IEEE 802) and the local sponsor organization are each a cohost for
the same session. It makes sense.
Thanx, Buzz
Dr. Everett O. (Buzz) Rigsbee
Boeing - SSG
PO Box 3707, M/S: 7M-FM
Seattle, WA 98124-2207
(425) 865-2443 Fx: (425) 865-6721
Cell: (425) 417-1022
everett.o.rigsbee@boeing.com
-----Original Message-----
From: Bill Quackenbush [mailto:quackenbush@ieee.org]
Sent: Thursday, December 30, 2004 8:58 PM
To: STDS-802-SEC@listserv.ieee.org
Subject: Re: [802SEC] +++EC Email Ballot+++ENDS 13 JAN+++motion to hold
plenary sessions outside NA
Buzz,
Actually, if you read the P&P, you will find that the concepts cohosts
and cohosting are very flexible and can deal with the relationships you
envision without modification. The flexibility is in the agreement
between the cohosts defining who is responsible for what. All you need
to do is to speak of cohosts, not hosts.
wlq
"Rigsbee, Everett O" wrote:
>
> Bill, I understand your point and am not looking to make more work
> for Matt, but it seems to me that the type of host and/or co-host that
would be defined in our P&Ps is rapidly becoming an extinct species, and
more and more they are becoming like what I am proposing for the
International Session Hosts (entities which may co-sponsor but do not
assume full financial responsibility for the session), so perhaps it
would make sense to correct our definitions in the P&Ps to allow for
either type of hosting entity (or maybe change to the new type), but to
at least allow our International Hosts to be described as "Hosts"
without undue confusion. I think we often overdo it with putting too
much specificity in our P&Ps and wind up creating unnecessary confusion
and conflicts for ourselves. A Host is a Host whether they provide
full-financial, partial-financial, or non-financial (logistical-only)
support and we should not have to invent new words for a concept that is
well known !
just
> because of some language in our P&Ps.
>
> Partnerships have their own set of legal ramifications that I would
> just a soon not choose to open Pandora's Box on.
>
> Thanx, Buzz
> Dr. Everett O. (Buzz) Rigsbee
> Boeing - SSG
> PO Box 3707, M/S: 7M-FM
> Seattle, WA 98124-2207
> (425) 865-2443 Fx: (425) 865-6721
> Cell: (425) 417-1022
> everett.o.rigsbee@boeing.com
>
> -----Original Message-----
> From: Bill Quackenbush [mailto:quackenbush@ieee.org]
> Sent: Thursday, December 30, 2004 11:47 AM
> To: STDS-802-SEC@listserv.ieee.org
> Subject: Re: [802SEC] +++EC Email Ballot+++ENDS 13 JAN+++motion to
> hold plenary sessions outside NA
>
> Buzz,
>
> Given that the LMSC P&P very specifically defines the roll of a
> session "host" or "cohost", I suggest that it would be desirable to
> use a different word for the organizational entity with which the LMSC
> partners to put on a session outside of the North America if that
> entity is not is not a "host" or "cohost" as defined in the P&P.
> "Sponsor" is a possibility, but there is a potential ambiguity here
> between the "sponsor of a session" and the "sponsor of a standard".
> The the term "partner" comes to mind as a possibility. I don't recall
> that "partner" has any IEEE defined meaning. And there are other
> possibilities.
>
> wlq
>
> -----Original Message-----
> Subject:
> Re: [802SEC] +++EC Email Ballot+++ENDS 13 JAN+++motion to
hold plenary sessions outside NA
> Date:
> Wed, 29 Dec 2004 20:06:40 -0800
> From:
>
> ----------
> This email is sent from the 802 Executive Committee email reflector.
> This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector.
This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector.
This list is maintained by Listserv.
----------
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.