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

[802.3_1TPCE] Proposed Responses to P802.3bw D3.2.1 SB R2



Colleagues,

The editorial team has posted the proposed responses to comments received on
D3.2.1. Here are some guidelines on the received comments for you to keep in
mind as you look over the responses.

87 comments received during the ballot (many out of scope)

Out-of-scope: This comment is not against a changed portion of the draft, a
portion of the draft affected
by changes, or a portion of the draft that is the subject of unresolved
comments associated
with "Disapprove" votes. It is therefore out of the scope of the
recirculation ballot.

12 comments received after ballot close (identified by the commenter as
out-of-scope)
	The TF must choose whether to consider these
	If considered, these comments are non-binding
	Otherwise, all that is required is to notify the commenter that the
comments were received
	Suggest the TF vote to consider them

74 out-of-scope, plus 12 out-of-scope late
	Out-of-scope comments can be rejected with no further reason needed
	Use this wisely---carefully consider each comment on its merit
	If something is broken, let's fix it

60 ?rogue? comments from people not part of the SB ballot group made via the
Chair?s Standard Offer (many out-of-scope)
	These are non-binding but must be considered, including out-of-scope

7 ?must be satisfied? comments

We are trying to produce the best possible draft and I thank all the
commenters for their thorough review. We want the next recirculation, SB R3,
to come back clean (no comments.) At that point, the work of the Task Force
will be finished.


Best regards,

Steve

Steven B. Carlson
Chair, IEEE P802.3bp 1000BASE-T1 PHY Task Force
http://www.ieee802.org/3/bp/index.html
Chair, IEEE P802.3bw 100BASE-T1 PHY Task Force
http://www.ieee802.org/3/bw/index.html
Executive Secretary, IEEE 802.3 Ethernet Working Group
http://www.ieee802.org/3/index.html
President
High Speed Design, Inc.
Portland, OR
scarlson@xxxxxxxxxxxxx