| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
| Ruben: 0520_OMEGA_report.pdf is a WG presentation. Our Public Area /15 May Motions_OMEGA_2020_05_15.pdf file should be posted soon. Following is the process used to create files. I created the WG file first (0520_OMEGA_report.pdf). The four SGs considering PARs were asked to use the same format and motions. Mr. Carlson created his B10GAUTO (proposed P802.3cy) report as a template. Objectives slides content was copied from our web site home page Objectives link. PAR slides content was copied from the file at https://mentor.ieee.org/802-ec/dcn/20/ec-20-0010-01-00EC-ieee-p802-3cz-draft-par-response.pdf. CSD slide content was copied from https://mentor.ieee.org/802-ec/dcn/20/ec-20-0011-00-00EC-ieee-p802-3cz-draft-csd-response.pdf. The PAR, CSD, and Objectives slides should be identical in 0520_OMEGA_report.pdf and Motions_OMEGA_2020_05_15.pdf. Motions were modified to point to 0520_OMEGA_report.pdf, and to point to the submitted PAR and CSD as submitted and described in the paragraph above. In addition, I added the pointer to 0520_OMEGA_report.pdf to the PAR and CSD motions as suggested by Mr. Swanson on our reflector. I also changed the hyphen on the range of slide numbers because there is one 802.3 member that correctly makes a big point of the difference between “to” and “through”. Not knowing if an 802.3 member would interpret the hyphen as a “to”, I changed the hyphen to a “through” to eliminate the possible need for comment and modification during the WG teleconference. I recommended other SGs make similar changes. PAR — Mr. Law and I shared the myProject version of the PAR prior to a software upgrade, after which I no longer had access. So, Mr. Law created the submitted pdf from myProject. It should be the same content as the PAR version we approved for submittal in Geneva. (If it looks different, the current myProject puts the new IEEE SA logo on the PAR pdf.) After copying PAR text into the slides, I had to do a little formatting (e.g., indents). I also set unmodifiable portions of the PAR to grey. There are no comments yet that require changes to the PAR (assuming the SG agrees with the proposed response on the 802.1 Title comment.) If other WGs comment and the SG agrees to make changes in the 15 May call, those changes will be documented in Responses_OMEGA_2020_05_15.pdf, with specific change marks in Motions_OMEGA_2020_05_15.pdf. After the SG call, any modified Motions_OMEGA_2020_05_15.pdf slides will be copied into 0520_OMEGA_report.pdf. CSD — The CSD flow is much the same. CSD slide content was copied from https://mentor.ieee.org/802-ec/dcn/20/ec-20-0011-00-00EC-ieee-p802-3cz-draft-csd-response.pdf (the file submitted to the EC). The CSD motion was modified similar to the PAR motion per Mr. Swanson and Mr. Grow non substantive changes. We have received comments that I personally believe should be incorporated into the CSD. Those changes are highlighted in yellow and change marked. The balanced cost changes are not agreed to by P802.3cy leadership, and are therefore subject to change (we both received the same comment on identical text). I also have marked some grammar changes. (I don’t want WG call time spent correcting grammar that I find fine, but that others might not like.) For PAR and CSD, I will make suggested changes in response to any comments received from other WGs between now and our 15 May teleconference, and if "last minute comments", the first time the SG will see them and responses is on the call. If other WG comments are sent and I see them on the 13th or 14th, I’ll send my proposals to the SG reflector. The SG is totally free to accept, modify or reject any change marking or supporting response text in Responses_OMEGA_2020_05_15.pdf that I have written. Comments to the reflector in advance of our teleconference would be appreciated. —Bob will be made as change marks to the PAR content slides of . , is pdf output from Mentor by Mr. Law, and is what has been submitted to the EC. (For EC consideration, the file has to be posted to the EC area on mentor. PAR fileIt includes the SG version of the motions in the WG presentation (edited for presentation name and slide number), and the same PAR, CSD and Objectives slides as included in the WG report. Here is my plan for how things were done and how we will handle any changes between now and the 21 May WG meeting. PAR 1. The referenced file https://mentor.ieee.org/802-ec/dcn/20/ec-20-0010-01-00EC-ieee-p802-3cz-draft-par-response.pdf is pdf output from Mentor by Mr. Law, and is what has been submitted to the EC. (For EC consideration, the file has to be posted to the EC area on mentor.) 2. The text of that file is copied into multiple slides on 0520_OMEGA_report.pdf. Some formatting was required, non modifiable text was set to grey, black text responses can be modified. 3. No comments received to date It is included this way in case the SG modifies text in response to WG decides to do any changes on 21 May. —Bob
To unsubscribe from the STDS-802-3-OMEGA list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-OMEGA&A=1 |