Re: [802SEC] Proposed press release for formation of 802.24
We don't have a process for general public communications. Look at the OM. We have procedures for sending liaisons to standards or governmental bodies: Clause 8 of the OM. It doesn't specify a procedure for having a standing approved TAG or Working Group communication to the world such as a report or a presentation.
Liaisons by their nature are often very time sensitive so we have to have a fairly expedited procedure for them. It isn't clear that that is the right process for a standing report, presentation, etc.
It also isn't clear to me where an SGIP SIF fits as there is no cover letter with it on the website. Perhaps if it is written to send to the NIST Smart Grid Interoperability Panel, it's a communication to a government body and covered by that process. In that case, it needs a cover letter to clearly state whether it is issued as the view of the IEEE 802 LMSC or as the view of the TAG. There doesn't seem to be any such cover letter or statement associated with the document on Mentor.
Depending on whether it is being sent from the IEEE 802 LMSC or the TAG, it needs a vote of the EC or a 5 day review before it can be released. Looking at the EC reflector, I don't see that either has occurred so even that isn't a "completed" document.
From: James Gilb [mailto:email@example.com] On Behalf Of James P. K. Gilb
Sent: Tuesday, October 16, 2012 6:32 PM
To: Pat Thaler
Subject: Re: [802SEC] Proposed press release for formation of 802.24
For internal documents, we have the same process as any other group to
approve a document. For public communications, we have the standard 802
process (e.g., what is done by 802.18 in .).
Nov. 2012 may be optimistic, but we have already completed one document
(a SIF for 802.15.4g) and I expect that we will get updates for 802.16
and perhaps 802.11 by November as well.
I will get the hyperlinks updated.
Tony, what do you want for the name of 802.1? I got the name from
http://www.ieee802.org/dots.shtml, which doesn't agree with
http://www.ieee802.org/wgchairs.shtml. I think it was the previous
Recording Secretary that messed that up.
I will change "SG" to "Smart Grid"
On 10/16/2012 05:03 PM, Pat Thaler wrote:
> Major comment: What's the review process for "white papers,
> guidelines and presentations"? The TAG was formed in July 2012 and I
> don't see any drafts of such documents posted in its document area.
> Based on that, I don't see how such WG products could have adequate
> review and be released Nov 2012. Please remove that sentence or put
> in a more realistic date. If the latter, start developing a process
> for approval of non-liaison, non-standards-project documents and get
> IEEE 802 EC acceptance of the process.
> Other items: There are hyperlinks to the websites of most WGs but
> 802.1's is missing.
> I don't think we use "LAN" in 802.1's name. After all, we do some
> work that's more WAN focused such as Provider Bridging and OAM. It's
> High Level Interface WG on the 802 WGs page.
> Some of the groups use the older grouper.ieee.org link instead of
> ieee802.org/<n> links. Both get to the same place, but I'd suggest we
> use the newer ieee802.org paths for all of them.
> SG is a confusing acronym because usually in IEEE 802 it means Study
> Group. Use Smart Grid TAG instead of SG TAG - it isn't that many
> -----Original Message----- From: ***** IEEE 802 Executive Committee
> List ***** [mailto:STDS-802-SEC@ieee.org] On Behalf Of James P. K.
> Gilb Sent: Tuesday, October 16, 2012 2:49 PM To:
> STDS-802-SEC@LISTSERV.IEEE.ORG Subject: [802SEC] Proposed press
> release for formation of 802.24
> I pre-circulating another press release, this one to announce the
> formation of 802.24. I am planning on a 6 day preliminary review
> and will ask for an early close EC email ballot beginning early next
> If you are a WG chair, check the text to make sure that the name of
> your WG is correctly described. Also check to make sure that your WG
> has not been inadvertently left our (or has been inadvertently
> James Gilb 802.24 TAG Chair
> ---------- 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.