Comment Text in PAR/CSD Remarks / Answers to the Comments Responses to IEEE 802.3 comments The plan is to open a 15.3 Revision PAR in What is the revision plan for • July and proceed with the Revision right IEEE Std It away before either amendment. We would appears that there are two include the fixes that are currently in the 15.3e PAR so those do not get lost and we approved amendments IEEE would update the 15.3d PAR so everything Std and is consistent. The revision 64 bit MAC IEEE Std addresses to 48 bit MAC addresses. at the plus an exising amendment amendment level so this would be much project. The 4th amendment simpler and . will be subject to the requirement to revise the standard after three years and three amendments. An extension can be requested, but the PAR should not be approved without knowing the revision plan. The P802.15.3d PAR should Noted. • never have been approved as submitted. The 15.3e PAR fixes these problems but if 15.3e is approved first, these fixes and Scope and Purpose changes would then be backed out by 15.3d. This makes the two – projects contingent in some way that the PAR form is equipt to handle. A modified PAR should be – submitted for 15.3d to change Scope and Purpose language to refer to the standard, not the project. This could be part of the revision plan (modified PAR or conversion of 15.3d into a revision will be submitted when approval order is clear.) Both PARs should clearly – indicate that if 15.3d is approved after 15.3e the scope and purpose should not change from that specified in 15.3e. 2.1 (non substantive) The Noted. • — correct format is <amendment “Amendment: name>”, not for “Amendment <amendment name>”. 5.1 It be unusual for 5.1 Approximate number of people expected to Action: Accept • — be actively involved in the development of this participants to increase from Change: In section 5.1, change "50" to "30". project: in activities (as indicated in the CSD) to the 50 indicated in the PAR. For 802, the resonse should relate to the TG doing the work, not the number of WG members.
Comment Text in PAR/CSD Remarks / Answers to the Comments Responses to IEEE 802.3 comments • What is the revision plan for IEEE Std It appears that there are two approved amendments IEEE Std and IEEE Std plus an exising amendment project. The 4th amendment will be subject to the requirement to revise the standard after three years and three amendments. An extension can be requested, but the PAR should not be approved without knowing the revision plan. The plan is to open a 15.3 Revision PAR in July and proceed with the Revision right away before either amendment. We would include the fixes that are currently in the 15.3e PAR so those do not get lost and we would update the 15.3d PAR so everything is consistent. The revision 64 bit MAC addresses to 48 bit MAC addresses. at the amendment level so this would be much simpler and . • The P802.15.3d PAR should never have been approved as submitted. The 15.3e PAR fixes these problems but if 15.3e is approved first, these fixes and Scope and Purpose changes would then be backed out by 15.3d. – This makes the two projects contingent in some way that the PAR form is equipt to handle. – A modified PAR should be submitted for 15.3d to change Scope and Purpose language to refer to the standard, not the project. This could be part of the revision plan (modified PAR or conversion of 15.3d into a revision will be submitted when approval order is clear.) – Both PARs should clearly indicate that if 15.3d is approved after 15.3e the scope and purpose should not change from that specified in 15.3e. Noted. • 2.1 (non substantive) — The correct format is “Amendment: <amendment name>”, not “Amendment for <amendment name>”. Noted. • 5.1 — It be unusual for participants to increase from in activities (as indicated in the CSD) to the 50 indicated in the PAR. For 802, the resonse should relate to the TG doing the work, not the number of WG members. 5.1 Approximate number of people expected to be actively involved in the development of this project: Action: Accept Change: In section 5.1, change "50" to "30".
15-15-0229-02-003e-par-csd-comments-resolutions.docx