| Thread Links | Date Links | ||||
|---|---|---|---|---|---|
| Thread Prev | Thread Next | Thread Index | Date Prev | Date Next | Date Index |
|
Colleagues, I was informed that the last link in my notice did not work correctly.
It’s the one to automatically send an email including the subject line etc.
I have fixed it in the version below and it should work correctly. This can be done with this link:
mailto: david.lewis@xxxxxxxxxxxx?cc=kohichi.tamura@xxxxxxxxxx?subject=IEEE P802.3cc 25GSMF D1.0 comments
Regards, David Lewis Chair P802.3cc Task Force From: David Lewis
Dear Colleagues: This is the announcement of the IEEE
P802.3cc Task Force first review of IEEE P802.3cc 25 Gb/s Ethernet over Single-Mode Fiber. Instructions for accessing the draft and submitting comments follow this announcement. Please take a moment to review these instructions,
as following them will help the editors respond more efficiently. Note that the options for submitting comments HAVE BEEN UPDATED, please review the commenting instructions below to ensure you are using the most up to date tools. Please note that any proposed remedies that suggest a presentation will be submitted will not be considered as the actual request for presentation time. A separate request must be made to the chair.
IEEE P802.3cc is an amendment to IEEE Std. 802.3-2015.
Please contact David Law, the IEEE 802.3 WG Chair, if you need to get a copy of it. IEEE P802.3cc Project Documentation · The Project Authorization Request for this amendment
is posted at: http://www.ieee802.org/3/cc/P802.3cc.pdf
· The responses to the Criteria for Standards
Design (CSD) for this amendment are posted at: http://www.ieee802.org/3/cc/ec-16-0059-00-ACSD-802-3cc.pdf
· The Objectives for this amendment are posted
at: http://www.ieee802.org/3/cc/P802_3cc_Objectives.pdf
___________________________________________ REVIEW SCOPE: REVIEW CLOSE: HOW TO ACCESS THE DRAFT The draft is posted for Task Force review purposes only, and neither the draft nor access information should be copied or redistributed to others in violation of document
copyrights. Draft 1.0 may be downloaded from:
HOW TO SUBMIT COMMENTS Acceptable comment types: E = Editorial ER = Editorial Required (a binding comment that is part of a DISAPPROVE vote, therefore only appropriate for an IEEE 802.3 voting member) T = Technical TR = Technical Required (a binding comment that is part of a DISAPPROVE vote, therefore only appropriate for an IEEE 802.3 voting member) 1. Prepare your comments in one of the following three ways. You are STRONGLY REQUESTED to use either the comment tool or spreadsheet. A comment entry tutorial is available at http://ieee802.org/3/ballots/p802d3_comment_entry_tutorial_v1p0.pdf.
a. Access the comment tool at the URL (last updated 16th September 2015): http://www.ieee802.org/3/WG_tools/filemaker/Generic_Commenting_Tool_FM.zip To use the tool, extract all components into a folder and do not move any component from that folder as this will cause the executable to not work correctly. The tool is: Comment_Tool_Generic_Solution.exe b. Access the comment spreadsheet at the URL: http://www.ieee802.org/3/WG_tools/spreadsheet/802d3_TFR_WGB_comments.xls c. To submit comments in text (ASCII) form, please use the form below. This will make it possible for the editor to properly record and track all submissions. Make as many copies of the template as necessary and submit as an ASCII text
file or as part of your e-mail. PLEASE NOTE: The ASCII method involves a manual transcription, hence you are recommended to check your comments to ensure accurate transcription when the comment file is made available. Please use one of the comment tools above if possible.
2. Send your comments to
david.lewis@xxxxxxxxxxxx and kohichi.tamura@xxxxxxxxxx
This can be done with this link:
mailto: david.lewis@xxxxxxxxxxxx?cc=kohichi.tamura@xxxxxxxxxx?subject=IEEE P802.3cc 25GSMF D1.0 comments
____________________________________________________________ Thank you for your participation in this review and careful review of the draft. Email: kohichi.tamura@xxxxxxxxxx |