[STDS-802-3-MAINT] [P802.3cv]Announcement - D1.0 Tack Force Review: IEEE

Thread Links	Date Links
Thread Prev	Thread Next	Thread Index	Date Prev	Date Next	Date Index

All, a typo was pointed out to me: “REVIEW CLOSE: Sunday, 4 November 2019, Midnight AOE (The intention is for comments to be in Dave’s and my inbox Monday morning. Late comments cannot be accepted.)“

Nov 4 is a Monday. The intent is to close the ballot on Sunday (as stated in the follow on text). Therefore, the closing date is November 3, 2019, 11:59pm AOE.

I will resend the announcement with this correction.

Regards,

Chad Jones

Technical Leader, Cisco Systems

Chair, IEEE P802.3cq Task Force

Chair, IEEE P802.3cv Task Force

Chair, IEEE SPMD Study Group

Principal, NFPA 70 CMP3

From: "Chad Jones (cmjones)" <00000b60b3f54e8d-dmarc-request@xxxxxxxx>
Reply-To: Chad Jones <cmjones@xxxxxxxxx>
Date: Thursday, October 3, 2019 at 2:02 PM
To: CQ Maint <STDS-802-3-MAINT@xxxxxxxxxxxxxxxxx>
Subject: [STDS-802-3-MAINT] [P802.3cv]Announcement - D1.0 Tack Force Review: IEEE P802.3cv

Dear Colleagues:

This is the announcement of the review of the IEEE P802.3cv Power over Ethernet (Maintenance #15) Task Force draft amendment D1.0. Instructions for accessing the draft and submitting comments follow this announcement.

IEEE P802.3cv is an amendment to IEEE Std 802.3-2018 which is available through the “Get 802” program at the URL:

http://standards.ieee.org/getieee802/802.3.html

The Project Authorization Request for this amendment is posted at: http://www.ieee802.org/3/cv/P802d3cv_PAR.pdf

___________________________________________

REVIEW SCOPE:

The scope of the review is the entire IEEE P802.3cv D1.0 Draft along with any maintenance items for IEEE 802.3bt-2018 with the following caveat: comments will only be accepted if they fix errors. New features cannot be added via the maintenance process.

REVIEW OPEN:

Thursday, 3 October 2019

REVIEW CLOSE:

Sunday, 4 November 2019, Midnight AOE (The intention is for comments to be in Dave’s and my inbox Monday morning. Late comments cannot be accepted.)

-------------------------------------------------------------------------

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 should be used for commenting and may be downloaded from:

URL: http://www.ieee802.org/3/private/maint/cvballot/8023cv_D1p0.pdf

While generating the draft, the editor had a few comments. That file can be downloaded here:

URL: http://www.ieee802.org/3/private/maint/cvballot/editors_comments_D1p0.txt

These documents are in the password protected IEEE P802.3cv private area. Username and password: distributed at meetings

IEEE802.3bt-2018 can be accessed via the “Get 802” program mentioned above.

If commenting against the IEEE 802.3bt-2018 document, please be sure to note that you are commenting against this document and not against IEEE P802.3cv. Include the page of the text in question and include a copy of the text in question (to ease the editors job of finding the text in question). There are no line numbers on this published standard. Therefore, the line number field will be used to give the approximate quarter of the page where the text being commented against lies. The top quarter is ‘1’, second quarter is ‘2’, third quarter is ‘3’, and bottom quarter is ‘4’. There should be no other entries aside from 1,2,3,4 in this field for comments made against IEEE 802.3bt-2018.

The documents are posted in Adobe "pdf" document format and can be downloaded and printed if desired. If you do not have Adobe Acrobat Reader, it is available for free downloading from Adobe at:

URL: http://www.adobe.com/prodindex/acrobat/readstep.html

_______________________________________

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)~~ Not applicable in Task Force review

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)~~ Not applicable in Task Force review

1. Prepare your comments in one of the following three ways. You are STRONGLY REQUESTED to use the spreadsheet. The comment tool would be the second choice. A comment entry tutorial is available at:

<http://ieee802.org/3/ballots/p802d3_comment_entry_tutorial_v1p0.pdf>

a. Access the comment spreadsheet at the URL (PREFERRED):

<http://www.ieee802.org/3/WG_tools/spreadsheet/802d3_TFR_WGB_comments.xls>

b. Access the comment tool at the URL:

<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

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.

------CUT AND PASTE TEXT BELOW THIS LINE ONLY PLEASE--------

CommentID: (Leave Blank)

CommenterName:

CommenterEmail:

CommenterPhone:

CommenterCellPhone:

CommenterCompany:

Clause:

Subclause:

Page:

Line:

CommentType: (E, ER, T, or TR)

Comment:

CommentEnd:

SuggestedRemedy:

RemedyEnd:

--------------------end comment template------------------

2. Send your comments to: david.abramson@xxxxxx, CC’ing cmjones@xxxxxxxxx and paste into the subject line:

IEEE P802.3cv Power over Ethernet (Maintenance #15) Task Force D1.0 comments

Be sure to make the filename of your comment file unique by appending your name to the filename.

_____________________________________________________________

Thank you for your participation in this review and careful review of the draft.