Re: [802SEC] Updated LMSC OM and LMSC P&P
I'm not a lawyer, but we have been using LMSC for as long as I can remember. I think things are context sensitive, and perhaps it could be argued that our context is different enough from Lockheed's, but I'd prefer not to venture an opinion.
One thing I will say is that in my editing instructions (not part of the documents) I encouraged the use of IEEE 802 rather than LMSC just for consistency. But old habits die hard, and clearly I've been slipping backwards a bit. I guess this would be one more reason to favor IEEE 802 over LMSC for a title and I will once more endeavor to do so...
Matthew Sherman, Ph.D.
BAE Systems - Electronics, Intelligence, & Support (EI&S)
Office: +1 973.633.6344
Cell: +1 973.229.9520
From: Todd Glassey [mailto:firstname.lastname@example.org]
Sent: Saturday, November 28, 2009 10:05 AM
To: Sherman, Matthew J. (US SSA)
Cc: STDS-802-SEC@LISTSERV.IEEE.ORG; 'James Gilb'
Subject: Re: [802SEC] Updated LMSC OM and LMSC P&P
Sherman, Matthew J. (US SSA) wrote:
> Attached please find an updated LMSC Operations Manual and a new LMSC Working Group Policies and Procedure for posting.
> For reference, I have taken the documents approved last week and done purely formatting changes to make them appropriate for posting. The one non-editorial change was in the section of the OM on directed positions. There was one broken link I missed that would have pointed to a section moved to the new WG P&P. For now, I have deleted the pointer (it does not change any of the meanings). We can add it back later if desired.
> For reference I have created rev's 1 and 2 of documents EC 09-006 and 09-007 (the LMSC OM and LMSC WG P&P balloted). Rev 1 includes the formatting and editorial changes I performed for reference in revisions mode. Rev 2 is a clean (final) version of each document.
> I still need to finish formatting clean-up of the LMSC P&P and forward that to AudCom for posting. I plan to complete that later today.
> The changes for the LMSC WG P&P were big and messy. Hopefully we are now past the phase of massive changes and can now focus on smaller targeted changes to improve our operations. For my own benefit, I plan to start work on a LMSC OM revision to fix minor editorial issues, and simplify the LMSC OM revision process (make it the same as the LMSC P&P except that it can be changed more than once a year). During the March Plenary I will be accepting other EC members personal pet peeves (as long as the changes aren't too massive) for inclusion in a catch all rev to the LMSC OM that I am willing to run. Please don't send your desired changes now as I'd prefer not to stock pile at this point. At the end of the March Plenary I plan to initiate another LMSC OM revision for the catch all changes.
> Regards to all,
Mat LMSC is a registered trademark of Lockheed a tech company as I
recall - did anyone think about this?
> Matthew Sherman, Ph.D.
> Engineering Fellow
> BAE Systems - Electronics, Intelligence, & Support (EI&S)
> Office: +1 973.633.6344
> Cell: +1 973.229.9520
> email: email@example.com<mailto:firstname.lastname@example.org>
> This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.
> No virus found in this incoming message.
> Checked by AVG - www.avg.com
> Version: 8.5.426 / Virus Database: 270.14.85/2531 - Release Date: 11/27/09 19:39:00
This email is sent from the 802 Executive Committee email reflector. This list is maintained by Listserv.