Re: [STDS-802-16] Fwd: [STDS-802-16] 802 PARs for November EC agenda

["Johnston, DJ" <dj.johnston@INTEL.COM>]

Shouldn’t it either amend IEEE 802.16-2008, on the basis that that is what will be in place when the 16m is done or simply IEEE 802.16 which is the generic name for the last revision with all the outstanding amendments applied? Nothing will amend Rev2, because the name Rev2 will become 802.16-2008 on approval, assuming it’s complete in 2008.

 

DJ

 

 

----

David Johnston. dj.johnston@intel.com Cell: 503 380 5578, Desk: 503 712 4457

 

---

From: Feder, Peretz (Peretz) [mailto:pfeder@ALCATEL-LUCENT.COM]
Sent: Wednesday, November 07, 2007 10:17 PM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: Re: [STDS-802-16] Fwd: [STDS-802-16] 802 PARs for November EC agenda

 

 

 

---

From: Feder, Peretz (Peretz)
Sent: Thursday, November 08, 2007 1:14 AM
To: 'Panyuh Joo'; STDS-802-16@LISTSERV.IEEE.ORG
Subject: RE: [STDS-802-16] Fwd: [STDS-802-16] 802 PARs for November EC agenda

 

Not convinced Panyuh:

 

 

See below.

---

From: Panyuh Joo [mailto:panyuh.joo@GMAIL.COM]
Sent: Thursday, November 08, 2007 1:05 AM
To: STDS-802-16@LISTSERV.IEEE.ORG
Subject: [STDS-802-16] Fwd: [STDS-802-16] 802 PARs for November EC agenda

 

Feder,

 

The assumption is not likely right.

Each standard project is identified as related tasks whether it is revision or amendment or corrigenda or errata or new standard.

That is the same reason whay 16j upload contributions into 16j, but not into 16e/rev2/etc..

 

But when 802.16j is published, it too will amend 802.16Rev2 like 802.16g just did.

You can see the one to one match for each projects from year 2001, whether it is completed, obsoleted or active, etc...

 

They all became part of Rev2, so will 802.16j and according to my understanding of the 802.16m PAR, so should it.

The 802.16m PAR says amendment all over it. Amendment can’t be a new standard.

Hope this could help your understanding.

 

Need more convincing. PAR language is king.

panyuh