[802SEC] FW: BOUNCE stds-802-sec@majordomo.ieee.org: Non-member submission from [y.hoSang@ieee.org]

["Bob O'Hara" <bob@bstormnetworks.com>]

Forwarded for Yvette.

 -Bob
 

-----Original Message-----
From: owner-stds-802-sec@majordomo.ieee.org
[mailto:owner-stds-802-sec@majordomo.ieee.org] 
Sent: Wednesday, November 13, 2002 5:01 PM
To: owner-stds-802-sec@majordomo.ieee.org
Subject: BOUNCE stds-802-sec@majordomo.ieee.org: Non-member submission
from [y.hoSang@ieee.org] 


From owner-stds-802-sec@ieee.org Wed Nov 13 20:01:02 2002
Received: from aries2.ieee.org (aries.ieee.org [140.98.191.44])
	by ruebert.ieee.org (Switch-2.2.4/Switch-2.2.4) with ESMTP id
gAE111H29309
	for <stds-802-sec@majordomo.ieee.org>; Wed, 13 Nov 2002 20:01:01
-0500 (EST)
Received: from buzz.ieee.org (localhost [127.0.0.1])
	by aries2.ieee.org (Switch-2.2.4/Switch-2.2.4) with ESMTP id
gAE110W13085;
	Wed, 13 Nov 2002 20:01:00 -0500 (EST)
Subject: Minutes for editions SEC meeting
To: stds-802-sec@ieee.org
Cc: terry.cole@amd.com, a.ortiz@ieee.org, j.t.walker@ieee.org
X-Mailer: Lotus Notes Release 5.0.8  June 18, 2001
Message-ID: <OF4A2541C3.D36E2465-ON85256C71.000102E8@ieee.org>
From: y.hoSang@ieee.org
Date: Wed, 13 Nov 2002 19:58:37 -0500
X-MIMETrack: Serialize by Router on Buzz/US/IEEE(Release 5.0.8 |June 18,
2001) at 11/13/2002
 08:00:59 PM
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii

IEEE 802 SEC Editions Meeting
13 November 2002


1. The terms used during the discussion were defined.

DEFINITIONS

   Edition: Document that basically cleans up accumulated material by
rolling in all the
   amendments and corrigenda into the base. The document contains NO NEW
technical material
   (no new work). This idea is to make WG review of the document easier.
Basically, an
   edition is a WG tool.

   Revision: Basically, a revision allows the entire document to be
opened
to comments and
   changes during ballot. Revisions usually contain technical changes.

   Reaffirmation: A standard that is balloted for an up or down vote by
determining whether
   the document still reflects state-of-the-art technology and DOES NOT
contain misleading
   or erroneous information.  During the ballot, changes are not
allowed,
however, comments
   can be referred back to the WG for consideration during the next
revision or amendment.

2. The rules governing amendments were discussed. Rules for amendments
can
be found
in 8.1.2 of the IEEE-SA Standards Board Operations Manual.

INTERPRETATION OF AMENDMENT RULES

   You can have as many amendments as you would like within two years of
   IEEE-SA Standards Board approval as a new or reaffirmed standard.
Beyond the two years,
   if the standard has two or more amendments, the standard (base PLUS
   amendments/corrigenda) MUST be revised or reaffirmed.

   Note:  WG chairs are responsible for managing documents, and
therefore
they
   should track when a revision or reaffirmation is required. RevCom can
deny
   approval of any additional amendments if the requirements are not
met.

3. The policy for editions was outlined in greater detail as given
below:

POLICY FOR EDITIONS

   Editions may be created to assist WGs during standards development.
They
   will be created on a case-by-case basis, and at a slower pace.  In
other
   words, as a second priority to the creation of  new standards or
   amendments/corrigenda.

   An edition will be sold as a draft until the WG reviews the entire
document.
   The source file of the consolidated document will be made available
ONLY
to
   the technical editor and WG Chair.  This document will not be made
publicly available
   or uploaded to WG private sites. Editions DO NOT supersede the
standard,
and therefore
   will not be included in the GET IEEE 802(TM) program. They are not
new
work, so awards
   are not issued.

   Chairs can discuss with the Publishing Manager whether an edition is
appropriate.



Yvette  Ho Sang
Manager, Standards Publishing Programs
IEEE Standards Activities
+1 732 562 3814