[802.3_1TPCE] AW: Study Group Meeting at San Diego Plenary Meeting
Team,
same content without fancy formating.
Regards,
Thomas
Team,
Please follow the preparation hints for San Diego Plenary Meeting in the week of July 13th. Our study group "1 Twisted Pair 100 Mb/s Ethernet (1TPCE)" will meet on Tuesday July 15th in the afternoon starting 1 pm and on Wednesday July 16th at 9 am. Room information will follow.
Our Project Authorization Request (PAR), Criteria for Standards Development (CSD) and objectives will be considered by IEEE 802.3 for approval at the closing Working Group meeting on Thursday afternoon. If approved by 802.3, the PAR and CSD will be considered by the IEEE 802 Executive Committee for approval at its closing meeting on Friday afternoon. Our Working Group Chair has also submitted our PAR to NesCom for consideration during the August Standards Board meeting series. Approval is required at all three levels to authorize developing an amendment to IEEE Std 802.3 for "1 Twisted Pair 100 Mb/s Ethernet".
Supporters of our proposed project are "particularly" encouraged to attend the Thursday afternoon 802.3 working group meeting to support the project and participate in voting and discussion on any SG/TF issues that may arise at the closing plenary.
Our tasks for study group sessions are:
- Listen to requested presentations. In order to request a presentation time slot, please follow the instruction on the study group webpage http://www.ieee802.org/3/1TPCESG/public/presenterGuide.html.
- Generate responses regarding the PAR/CSD to comments from the working group.
- Items that we need to work on are:
o Objective: "Support optional operation with run-time configuration, by allowing time from power_on**=FALSE to a state capable of transmitting and receiving valid data to be up to TBD." We received criticism on the "TBD". A suggested fix for that could look like: "There will be an optional mode which includes run time configuration that specifies a maximum allowable time from power_on**=FALSE to a state capable of transmitting and receiving valid data." We need to discuss and probably modify this objective
o We received the BroadR-Reach Specifications Version 3.1 and I received indications from the automotive industry on minor modifications which leads to a further but final revision 3.2. I requested to finalize all work on 3.2 by the end of this week, and a proper documentation/presentation to display the difference between 3.0 and 3.2. We need to discuss this in order to change the reference of the second objective to the new and final revision of the BroadR-Reach specification.
o Also we have some updates on the Auto Negotiation discussion which should be discussed in the study group.
I will arrive most likely on Saturday 12th and would be available for any kind of discussion already on Sunday.
Have save trip to San Diego
Mit freundlichen Grüßen / Best regards
Thomas Hogenmueller