Re: [STDS-802-11-TGM] FW: Use of "should" in an informative annex Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-11-TGM] FW: Use of "should"
Re: discussion period begins, until Jan. 26: "natural interval extension Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: discussion period begins, until
dove_01d_0113_optx.pptx Page 1 IEEE P802.3bm 40 Gb/s and 100 Gb/s Fiber Optic Task Force 22,23 January Interim Meeting Agenda and General Information IEEE 802.3 40 Gb/s and 100 Gb/s Fiber Optic Task F
[STDS-802-11-TGBE] Revision 37 - Part 2 of IEEE802.11be Spec Text Writin Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [STDS-802-11-TGBE] Revision 37 - Pa
Re: [802SEC] Interpretation of current P&P Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [802SEC] Interpretation of current P&P To : STDS-802-SEC@LIST
Re: EUI-48 and EUI-64 Usage Question Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: EUI-48 and EUI-64 Usage Question To : ROBERT GROW < bobgrow@xxxxxxx
Re: [STDS-802-11-TGM] Do STAs inherit or aggregate PHYs? Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-11-TGM] Do STAs inherit or aggregate
[802SEC] +++ LMSC P&P Revision Ballot +++ WG Voting Procedures - Final Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index [802SEC] +++ LMSC P&P Revision Ballot
Re: [802SEC] what is an interpretation? Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [802SEC] what is an interpretation? To : David Law < davel@pdd.3
doc.: IEEE 802.11-06/1550r0 September 2006 doc.: IEEE 802.11-06/1550r0 IEEE P802.11 Wireless LANs Minutes for 802.11 Working Group Meetings in Melbourne, Australia Date: 2006-09-22 Author(s): Name Com
MainTable P802.3ah Draft 2.0 Comments # 951Cl 00 SC P L Comment Type TR I have a problem with the use of the term "loopback" for the diagnostic return path being proposed for the OAM sublayer. The pot
MainTable IEEE P802.3az D2.0 Energy Efficient Ethernet comments Comments on D2.0 September 2009 # 222Cl 00 SC P L Comment Type T This statement is confusing: If the optional Low Power Idle function is
MainTable IEEE P802.3az D2.0 Energy Efficient Ethernet comments Comments on D2.0 September 2009 Proposed Response # 1Cl 48 SC 48.2.4.2 P 128 L 42 Comment Type E "ordered set ||LPIDLE|| is a special of
MainTable P802.3ah Draft 3.2 Comments # 90003Cl 00 SC P L Comment Type TR A list of tables is now allowed for long documents, and is vital for review. SuggestedRemedy Provide a list of tables. DVJ1-xx
IEEE P802.3ae/D4.2 Comments P802.3ae Draft 4.2 Comments # 450001Cl 00 SC P L Comment Type E Clause 45 has changed all the capitalization of register names to lower case in line with comment #336 on D4
MainTable IEEE P802.3 (IEEE 802.3dc) D3.0 Maintenance #16 (Revision) Initial Sponsor ballot comments # I-43Cl FM SC FM P 1 L 26 Comment Type E Don't forget to update copyright year here and next page,
. . . May 1991 Doc: IEEE P802.11/91-64 ~ Standard for Interoperable Local Area Network (LAN) Security (SILS) Part B •• Secure Data Exchange Prepared by the IEEE 802.10 Editor of the LAN Security Worki
IEEE P802.3bt D2.4 4-Pair PoE 4th Working Group recirculation ballot comments 211Cl 00 SC 0 P L Comment Type E TODO 1-6 Topics: Figure out how other clauses link to DTE/PoE. How to address use of DTE
IEEE P802.3ca D1.3 25/50G-EPON Task Force 4th Task Force review comments Received Comments # 1Cl FM SC FM P1 L11 Comment Type ER Match new PAR title SuggestedRemedy Change "Physical Layer Specificatio
MainTable IEEE P802.3 (IEEE 802.3dc) D3.0 Maintenance #16 (Revision) Initial Sponsor ballot comments Response # I-1Cl 69 SC 69.1.1 P 3015 L 13 Comment Type T It is not necessary to specify the BER req
MainTable # 8Cl 00 SC 0 P0 L0 Comment Type G The draft is a bit rough, with lots of overly informal and unclear and/or ambiguous phrasing, to much to fix by commenting. SuggestedRemedy Have an IEEE te