|Thread Links||Date Links|
|Thread Prev||Thread Next||Thread Index||Date Prev||Date Next||Date Index|
All, In response to the comments I've received please find attached an updated version of the letter as well as a compare copy so that you may see the changes I've made. Best regards, David -----Original Message----- From: Roger Marks [mailto:firstname.lastname@example.org] On Behalf Of Roger B. Marks Sent: 03 February 2011 07:58 To: Law, David Cc: STDS-802-SEC Subject: Re: [802SEC] +++ 10-day EC Email Ballot +++ Liaison communication from the IEEE 802.3 working group ISO/IEC JTC1 SC6 WG1 David, I vote Approve. I agree with Pat's comments (and those of John Lemon). Other comments: (a) I think term "PSDO" is used too informally. I suggest replacing: The approval of the PSDO by both the IEEE and ISO in xxx of 200n with The approval of the IEEE/ISO Partner Standards Development Organization (PSDO) cooperation agreement of March 2008 (b) "significant updates and amendments since 2000" would be stronger if you quantified it in some way; for example, with the number of amendments Roger On 2011/01/28, at 10:32 AM, Pat Thaler wrote: > David, > > I'm in support of the letter, but have a couple of comments: > > Since the letter is signed by you, I assume that it is intended as communication from the 802.3 Working Group. > > Our P&P and OM don't require sponsor approval for Sponsor subgroup communications. That approval is required for IEEE 802 LMSC communications (see OM 9.1.1 and, if a liaison letter is considered a public statement, P&P 9.3.1). Our rules only require that 802.3 approve the liaison and copying "affected members of the sponsor" though I appreciate them being copied to the whole EC. > > Secondly, P&P 9.3.1 says that the first paragraph of subgroup public statements shall be identified in the first paragraph as being the position of the subgroup. The letter uses "our" and "we" but only implies who that is by your title as Chair of the 802.3 Working Group. I think it should explicitly state that the letter represents the position of the IEEE 802.3 Working Group. > > If that correction is made, I approve the motion though I don't think that our rules require the motion. > > Regards, > Pat > > > -----Original Message----- > From: ***** IEEE 802 Executive Committee List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of Law, David > Sent: Friday, January 28, 2011 9:03 AM > To: STDS-802-SEC@LISTSERV.IEEE.ORG > Subject: [802SEC] +++ 10-day EC Email Ballot +++ Liaison communication from the IEEE 802.3 working group ISO/IEC JTC1 SC6 WG1 > > Dear EC members, > > At the closing EC meeting in November I sought approval of a liaison letter from IEEE 802.3 to ISO/IEC JTC1 SC6 WG1 with respect to ISO/IEC 8802-3:2000, the letter is attached. During the discussion it was suggested that IEEE staff work with their contacts to establish exactly what the status was of ISO/IEC 8802-3:2000 before approval. > > It has now been established that ISO/IEC 8802-3:2000 has entered 'Systematic Review'. I understand this to mean that, according to the JTC1 rules, the most recent edition of a standard is reviewed by JTC 1 with a view to deciding, by a majority of the participating members voting in a meeting or by correspondence, whether it should be Confirmed; Revised; Declared as stabilized; or Withdrawn. > > On the basis that IEEE 802.3 has approved this letter, and that I believe that it contains useful information for ISO/IEC JTC1 SC6 WG1 I, would now like the make the motion below. > > Best regards, > David > > > Motion > ====== > > The LMSC Executive Committee approves the letter IEEE802d3_to_JTC1_SC6_01_1110.pdf, with editorial license granted to the Chair (or his appointed agent), as a liaison communication from the IEEE 802.3 working group ISO/IEC JTC1 SC6 WG1 with respect to ISO/IEC 8802-3:2000. > > Move: David Law > Second: Tony Jeffree > > Start of ballot: Friday 28th January > Close of ballot: Monday 7th February, 11:59PM AOE > > ---------- > 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.