Re: [RPRWG] Bug reporting on 802.17, how is it to be done?
John,
>> Firstly, since the standard has not been published, it is not
>> possible to request changes to or clarifications of something
>> that does not exist.
1) From my understanding, individuals can purchase copies, so some
form of informal standard (probably the copy Tom sent to IEEE)
exists. Am I confused?
2) Its always possible to comment on what is known to be coming,
to comment in the intended format for later contributions, and
to hold those comments until the review opens.
3) I'm sure there are many implementers, who are finding bugs
on first implementations, so providing and early/convenient
submittal process could pick these up also.
I will be doing that (writing them down in the last CRD format)
because I forget things unless I write them down when first observed.
So, a hint as to the eventual process (or at least the format
for submittals) would be most helpful and lead to more complete
contributions.
>> Secondly, at the November plenary, I intend to put forward a
>> motion to adopt a specified process for handling maintenance
>> requests, and a motion to adopt a specified process for handling
>> interpretation requests. So, such requests should be possible to
>> submit sometime after the November plenary. Please watch the web
>> site for details after the November plenary.
If you schedule the motion at the beginning of the meeting,
and the submittal format is known, I can have comments available
(2 weeks before) so that you can get an early start on resolutions.
Of course, if that seems premature, I can also wait. Thanks for
the info.
DVJ
David V. James
3180 South Ct
Palo Alto, CA 94306
Home: +1.650.494.0926
+1.650.856.9801
Cell: +1.650.954.6906
Fax: +1.360.242.5508
Base: dvj@alum.mit.edu
>> -----Original Message-----
>> From: John Lemon [mailto:JLemon@luminous.com]
>> Sent: Friday, September 03, 2004 3:20 PM
>> To: David V James; STDS-802-17@listserv.ieee.org
>> Subject: RE: [RPRWG] Bug reporting on 802.17, how is it to be done?
>>
>>
>> David, et al,
>>
>> Firstly, since the standard has not been published, it is not
>> possible to request changes to or clarifications of something
>> that does not exist.
>>
>> Secondly, at the November plenary, I intend to put forward a
>> motion to adopt a specified process for handling maintenance
>> requests, and a motion to adopt a specified process for handling
>> interpretation requests. So, such requests should be possible to
>> submit sometime after the November plenary. Please watch the web
>> site for details after the November plenary.
>>
>> _______________________
>> John Lemon
>> Vice Chair, IEEE 802.17
>> _______________________
>>
>>
>> -----Original Message-----
>> From: owner-stds-802-17@listserv.ieee.org
>> [mailto:owner-stds-802-17@listserv.ieee.org]On Behalf Of David V James
>> Sent: Thursday, September 02, 2004 1:07 PM
>> To: STDS-802-17@listserv.ieee.org
>> Subject: [RPRWG] Bug reporting on 802.17, how is it to be done?
>>
>>
>> All,
>>
>> What is the procedure for submitting change requests and/or
>> possibly getting feedback on apparent errors?
>>
>> For now, I am simply keeping my own CRD, which is attached.
>> I found many of these when trying to generate a simplified
>> RBR draft.
>>
>> Any review comments, that you would believe help clarify the
>> statement or proposed resolution, are most appreciated.
>>
>> Is there a preferred way to do this? I didn't see directions
>> on the RPR site, but that I might have overlooked them.
>>
>> DVJ
>>
>> David V. James
>> 3180 South Ct
>> Palo Alto, CA 94306
>> Home: +1.650.494.0926
>> +1.650.856.9801
>> Cell: +1.650.954.6906
>> Fax: +1.360.242.5508
>> Base: dvj@alum.mit.edu