| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
James, Yes I can do this, and in a sense I did. If you look at the original 'mark up' version of the P&P that I circulated earlier it includes the editorial guidance. However, I only included the 'final' version of the document with the ballot because I didn't want anyone to get confused on what version of the document to comment against. I've included the 'mark up' version again here for folk's reference. Mat Matthew Sherman, Ph.D. Engineering Fellow BAE Systems - Network Systems (NS) Office: +1 973.633.6344 Cell: +1 973.229.9520 email: matthew.sherman@baesystems.com -----Original Message----- From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@LISTSERV.IEEE.ORG] On Behalf Of James Gilb Sent: Saturday, June 28, 2008 9:25 PM To: STDS-802-SEC@LISTSERV.IEEE.ORG Subject: Re: [802SEC] IEEE model P&P Mat I a standard, you can add notes. In the balloting phase of the P&P, you could retain the notes from the baseline P&P, seeking approval of the text, minus these editorial notes. I found that reading the notes in the baseline P&P helped me to understand the constraints that 802 is under. After approval of the changes, the final P&P would delete these editorial comments. Just a suggestion. James Gilb Sherman, Matthew J. (US SSA) wrote: > John, > > I like the idea in principle, but note that the baseline P&P also > evolves, so what can and can't be changed is always changing. Tracking > it is a real pain. Actually I don't like the idea of a baseline with > non-modifiable text. If we can't change it, it shouldn't be in our > document. I should be in a superior document and reference by us so we > are always up to date. I suggested this at AudCom the other day but it > was not well received. The baseline should be an outline with draft > text as guidance. What sections are present and types of rules they > should contain should be mandatory, but not the rules themselves. > Certainly it should not mandate rules controlled by an external > organization that can be changed independent of our document and become > a synchronization issue. At least that's my take. > > Mat > > Matthew Sherman, Ph.D. > Engineering Fellow > BAE Systems - Network Systems (NS) > Office: +1 973.633.6344 > Cell: +1 973.229.9520 > email: matthew.sherman@baesystems.com > > > -----Original Message----- > From: ***** IEEE 802 Executive Committee List ***** > [mailto:STDS-802-SEC@LISTSERV.IEEE.ORG] On Behalf Of J Lemon > Sent: Friday, June 27, 2008 2:31 PM > To: STDS-802-SEC@LISTSERV.IEEE.ORG > Subject: Re: [802SEC] IEEE model P&P > > What would people think about somehow indicating the text in our P&P > that is not allowed to be changed from the model P&P? It could be some > means such as a difference in font, or underlined, or gray rather than > black. Or it could be some explicit tag. Or some other means. I think > this is useful information, and its a hassle to check through two > documents to figure out which text is so encumbered. > > jl > > On 6/27/2008 9:44 AM, Pat Thaler wrote: >> Since the question was asked during our rules call, the model P&P can > be >> found at: >> > http://standards.ieee.org/board/aud/baseline-Sponsor-clean-7June2007.doc >> >> The parent page that links to this and other governing docs is: >> http://standards.ieee.org/resources/index.html#guides >> >> Pat >> >> ---------- >> 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. ---------- This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
Attachment:
Draft_LMSC_PaP_080316_Mark_Up.doc
Description: Draft_LMSC_PaP_080316_Mark_Up.doc