Bob,
Let me comment on my comments listed below: - #139:
- Related with 138, both are about the same topic, so I suggest they are resolved as only one.
- We have included in the table 45-313c and subclauses 45.2.3.87c.1 a binary code to instruct the PHY to generate the test pattern of 166.5.6. According to our specifications of 166.7.10 this pattern is to be generated by a signal pattern generator, but not by a BASE-AU PHY. The PHY receiver will be connected to the pattern generator using the setup of figure 166-44.
- Therefore, this entry encoding generation of test pattern for stressed receiver sensitivity measurement was added by editor erroneously. Based on that I think Luisma classified the comment EZ. Nevertheless, no problem to take it out from the bucket.
- #142: Agree
- #180: I do not follow your comment Bob. The comment is about merging the two sub-clauses in only one.
- Perhaps it is better understood the following proposed response:
- AIP: Merge content of 166.2.2.6 and 166.2.2.7 into a single subclause with title "PCS transmit bit order”.
- #206:
- This comment was in time (not late).
- Classification has been changed from "PCS encoding” to EZ later.
- #221: I suggest AIP, see #230.
Other EZ comments (for Luisma): - #200 is AIP see #227. However, #227 is AIP with with suggested remedy of #200 ;-). It is better to resolve #200 with Accept, and #227 with AIP see #200.
Thanks and best regards,
Rubén Pérez-Aranda CTO at KDPOF_____________________________________________________________
Knowledge Development for POF, S.L.A: Ronda de Poniente 14 2º CD, 28760, Tres Cantos (Madrid), Spain P: +34 91 804 33 87 Ext:110 M: +34 689 319 866 I: Subscribe our quarterly Automotive Update for regular news and technology insights.
Luisma,
The file pointed at for the EZ bucket is not current with the topics in the database and some comments were reclassified.
#7 — We removed from the EZ bucket and resolved. #21 — We removed from the EZ bucket and resolved. #198 — We removed from the EZ bucket and resolved.
As to comments to be removed from the bucket:
#139 — This is substantive enough that I think we should look at it individually. #142 — I believe this should be: REJECT See #141. #71 — I wrote the suggested remedy hastily, I wasn’t precise about suggesting a NOTE or an Editor’s Note. Perhaps an AIP Add Editor’s Note per the Suggested Remedy. #180 — I assume the “current 166.2.2.7” in the suggested remedy will be a hot link to what is 166.2.2.7 in D2.0. The ACCEPT implies the text will include “current”. #206 — I don’t find the comment in the referenced EZ file, but it is labeled EZ in the comment report file (perhaps because it was a late comment). #230 — The document tool automatically adjusts position of text and figures to minimize white space. Editor will attempt to improve position of the figures. #221 — A nit, but the suggested remedy only requests a “Check”, not a possible relocation of the references to the Figures in the text. #24 — The suggested remedy proposes two possibilities, should be an: AIP Delete the subclause and renumber subsequent subclauses.
Perhaps Motion 1 should read: Move to accept the comment responses to the remaining unresolved comments in the "EZ" bucket.
Perhaps for Motion 2: Move to create P802.3cz/D2.1 for WG recirculation ballot incorporating resolutions to P802.3cz/D2.0 comments with editorial license.
—Bob
Colleagues,
The comments received on P802.3cz/D2.0 with resolved responses
discussed until today (24 May 2022) have been posted to our Task
Force web pages (https://www.ieee802.org/3/cz/comments/index.html)
and attached to this email.
We have finished all programmed discussion on comments and
proposed responses. The only remaining bucket is the named "EZ".
As you know, "EZ" bucket contains the comments that, in my
opinion, are sufficiently clear, and do not require further
discussion. Proposed resolution for these comments are available
also in our Task Force web page
(https://www.ieee802.org/3/cz/comments/Comments_3cz_D2p0_Clause_Topic_EZ.pdf)
If you feel that this is not the case for any comment in this
bucket, please ask to take it out for discussion sending a mail to
me, Mr. Grow, or here on the reflector before tomorrow.
I would like to move two motions in our next session regarding
comment resolution:
- Motion #1: Move to accept the suggested remedies for comments
in the “EZ” bucket.
- Motion #2: Move to add closed comments received on
P802.3cz/D2.0 with editorial license in P802.3cz/D2.1.
Thanks for your support!
Kind Regards,
Luis Manuel (Luisma) Torres
Chief Editor, P802.3cz Gigabit Optical Automotive Ethernet (OMEGA)
Task Force
--
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
<Committee report_Clause_D2p0_with_responses_25_May_2022.pdf>
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
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
|