Thread Links Date Links
Thread Prev Thread Next Thread Index Date Prev Date Next Date Index

[802SEC] FW: BOUNCE stds-802-sec@majordomo.ieee.org: Non-member submission from ["Roger B. Marks" <marks@boulder.nist.gov>]




Forwarded for Roger.

 -Bob
 

-----Original Message-----
From: owner-stds-802-sec@majordomo.ieee.org
[mailto:owner-stds-802-sec@majordomo.ieee.org] 
Sent: Thursday, February 28, 2002 6:50 AM
To: owner-stds-802-sec@majordomo.ieee.org
Subject: BOUNCE stds-802-sec@majordomo.ieee.org: Non-member submission from
["Roger B. Marks" <marks@boulder.nist.gov>] 


From owner-stds-802-sec@ieee.org Thu Feb 28 09:49:56 2002
Received: from central.bldrdoc.gov (gemini2.ieee.org [140.98.193.20])
	by ruebert.ieee.org (Switch-2.1.0/Switch-2.1.0) with ESMTP id
g1SEnti10226
	for <stds-802-sec@majordomo.ieee.org>; Thu, 28 Feb 2002 09:49:55
-0500 (EST)
Received: from [10.0.0.4] (rocky.boulder.nist.gov [132.163.48.122])
	by central.bldrdoc.gov (8.9.3/8.9.2) with ESMTP id HAA15150;
	Thu, 28 Feb 2002 07:49:53 -0700 (MST)
Mime-Version: 1.0
X-Sender: marks@central.bldrdoc.gov
Message-Id: <a05100325b8a3e9e69b2b@[10.0.0.4]>
In-Reply-To: <4.2.0.58.20020226110049.02ad1940@mail.appairent.com>
References: <4.2.0.58.20020226110049.02ad1940@mail.appairent.com>
Date: Thu, 28 Feb 2002 07:49:54 -0700
To: stds-802-sec@majordomo.ieee.org
From: "Roger B. Marks" <marks@boulder.nist.gov>
Subject: Re: [802SEC] 15.2 PAR name change
Cc: shell@symbol.com
Content-Type: text/plain; charset="iso-8859-1" ; format="flowed"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by ruebert.ieee.org id
g1SEnvi10234

802.16 yields its reserved PAR-change agenda slot (for this meeting only!).

I have a question for the veterans among us:

Many other 802 standards include the term "specific requirements", 
but I've never understood what it means. I'm wondering, for example, 
if it has a particular meaning to ISO. I notice that some of the 
802.1 standards use the term "Common speciŪcations" instead.

It occurs to me that "specific requirements" might not be the right 
description of a "Recommended Practice".

By the way, I wonder if someone could explain the significance of:

"Information technology- Telecommunication and information exchange 
between systems- "

Roger


At 6:29 PM -0500 02/02/27, Bob Heile wrote:
>Paul
>
>In classic 802.16 tradition, 15 wants to propose a name change for 
>the 15.2 PAR to clearly include the word coexistence in the title. 
>Per our discussion, I am circulating the proposal to the SEC in 
>advance with the proposition of putting it on the consent agenda for 
>Friday's meeting. 
>
>Bob
>
>Proposed name change:
>
>From:
>
>Recommended Practice for Telecommunications and Information exchange 
>between systems - LAN/MAN Specific Requirements -
>Part 15: Recommended Practice for Wireless Personal Area Networks 
>operating in unlicensed frequency bands.
>
>To:
>
>Recommended Practice for Information technology - Telecommunications 
>and information exchange between systems -
>Local and metropolitan area networks specific requirements -
>Part 15.2: Coexistence of Wireless Personal Area Networks with Other 
>Wireless Devices Operating in Unlicensed Frequency Bands.
>
>
>Bob Heile, Ph.D
>Chair, IEEE 802.15 Working Group on Wireless Personal Area Networks
>Chair, ZigBee Alliance
>11 Louis Road
>Attleboro, MA  02703
>Phone: 508-222-1393
>Mobile: 781-929-4832
>Fax:	    508-222-0515
>email:   bheile@ieee.org