Re: [STDS-802-16] Call for Resolutions of Comments regarding Maintenance Task Group
In response to the Call for Resolutions of Comments regarding Maintenance
Task Group below, no proposed resolution comments have been submitted.
Therefore to resolve the unresolved comments from the last meeting, we will
be working from the Commentary database in IEEE 80216maint-04/09r1:
http://ieee802.org/16/maint/docs/80216maint-04_09r1.zip
which contains the original comments and their reply comments.
Jon
> -----Original Message-----
> From: owner-stds-802-16@LISTSERV.IEEE.ORG
> [mailto:owner-stds-802-16@LISTSERV.IEEE.ORG]On Behalf Of
> Roger B. Marks
> Sent: Sunday, January 16, 2005 12:54 PM
> To: STDS-802-16@LISTSERV.IEEE.ORG
> Subject: [STDS-802-16] Call for Resolutions of Comments regarding
> Maintenance Task Group
>
>
> In response to the Call for Reply Comments below, nine people
> submitted input. The additional replies comments submitted have been
> integrated, and the new Commentary database is available in IEEE
> 80216maint-04/09r1:
> http://ieee802.org/16/maint/docs/80216maint-04_09r1.zip
>
> The authors of the original comments in IEEE 80216maint-04/09r1 are
> now invited to propose resolutions of their original comments, taking
> the reply comments into consideration. The deadline is 20 January AOE.
>
> To propose resolution, following the instructions below for preparing
> reply comments. However, address only comments of which you are the
> author. Also, name the exported file "Maint_resolution_Name.USR",
> where "Name" is your name.
>
> Please use the correct file naming format.
>
> Roger
>
> >This note is a Call for Reply Comments regarding the Comment
> Report at:
> > http://ieee802.org/16/maint/docs/80216maint-04_09.zip
> >
> >Note that many of the comments already include replies. We are
> >seeking additional input in the form of specific proposed comment
> >resolutions, in the form that can be adopted when the TG meets at
> >Session #35. In other words, we aren't just asking for your
> >thoughts; we are asking you to draft specific text that can be used
> >by the Task Group as resolutions of the comments and as reasons for
> >the resolutions. Such draft text should allow the TG to move more
> >quickly through the comment resolution process.
> >
> >The deadline of Thursday 13 January 2005 AOE
> ><http://tinyurl.com/65vnt>. The instructions are below.
> >
> >Keep in mind that some of these comments may yet be ruled out of
> >scope. You are welcome to suggest this in your reply comments.
> >
> >Roger
> >
> >----------------
> >To create and submit reply comments:
> >
> >(1) Obtain Commentary <http://ieee802.org/16/docs/Commentary>, if
> >you don't have it.
> >
> >(2) Unzip the Comment Report to get a ".USR" file, which will open
> >in Commentary.
> >
> >(3) Read the comments in Commentary. When you want to respond to a
> >comment, check the "Marked" box at the top of that record. Then fill
> >out the following fields:
> >
> >Recommendation by:
> >Recommendation:
> >Proposed Resolution:
> >Reason for Recommendation:
> >
> >You are justified in recommending rejection on grounds of
> >incompleteness or lack of a specific change request.
> >
> >(4) When you are finished entering replies, look under Scripts and
> >choose "Find Marked Records". This will find the records for which
> >you checked the "Marked" box. Only the found records will be
> >exported in Step (5). Don't include records on which you have no
> >reply comment.
> >
> >(5) Under Scripts, choose "Export Clause Editor's Proposals". Choose
> >the file type "FileMaker Pro Runtime Files". Enter a file name of
> >the form "Maint_reply_Name.USR", where "Name" is your name.
> >
> >(6) Upload the exported file to <http://maint.wirelessman.org>.
> >
> >Dr. Roger B. Marks <mailto:marks@nist.gov> +1 303 497 7837
> >National Institute of Standards and Technology/Boulder, CO, USA
> >Chair, IEEE 802.16 Working Group on Broadband Wireless Access
> > <http://WirelessMAN.org>