| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Bob, Below mail arise a sense of discomfort in my mind. Because it seems splitting PAR is an accomplished fact. I discussed this matter with you off-line, but for almost all attendees, it is a very new topic. We should discuss this topic in TF next week. Best regards, Yuji Watanabe, AGC From: ROBERT GROW <bobgrow@xxxxxxx>
Colleagues, As those of you that attended the P802.3cz teleconference this on 10 Nov know, we had a free form discussion on what is involved in division of a project into two projects, also known as a PAR split. I showed some slides
related to the process, and those will be posted to the November meeting area if you wish to review them. As we discussed, anyone can provide input on what the project documents should look like. Discussion of a PAR split is an appropriate topic for this reflector. I’m happy to answer questions privately, or on this reflector,
or in one of next week’s teleconferences. I was encouraged to start work on possible documents for consideration by the TF. Mr. Law has already created a new draft PAR for me to use in myProject. For any of you that might want to provide input to me or present
themselves to the TF on this topic, here are pointers to resources you can use. 1. Our existing P802.3cz documents are linked on the TF home page: https://www.ieee802.org/3/cz/. 2. Often when discussing a PAR and CSD, people use a template for presentation. You will find templates for PAR, PAR Modification, and CSD linked from https://www.ieee802.org/3/WG_tools/templates/index.html.
a. For example, the PAR template highlights the fields that are not automatically generated. Project Scope and Need are considered the most important by many. The template though highlights some other fields to think about.
b. Those of you that have been involved in other projects or in our discussions will note the importance of both the CSD questions that need to be answered, as well as the important that our approved CSD responses have for 802.3 members. 3. There is no form for objectives, but one could certainly start with the P802.3 Objectives to consider what might need to be modified for what remains as the P802.3cz project or be used as a starting point for objectives
for a new project. At the risk of being redundant, once again, I’ll express my willingness to work with any of you on this, or to answer any questions you might have as we consider splitting the project. Robert M. (Bob) Grow 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 |