Most noteable are IEEE 754 Floating Point >> > and IEEE 1394, and other microprocessor standards.

Probably useful to the customers, although accurate network timing and good QOS are likely to be perceived as threats by IEEE 1394 zealots.

This is one place where the SG received conflicting >> information, so the more restrictive number was used ... since existence >> proofs (IEEE 1588 and IEEE 1394) shows that this kind of >> synchronization can >> easily be done with very low complexity. >> >> The numbers I quote here are open for discussion.

Regards, Edward ---------- Forwarded message --------- Hello Edward,   You allocations: TransactionID Type Status User Group Resource Ref Doc Ref Subclause Ref Location Name Req Value Description Allocated Value 1390 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 DENIED_LINK_ON_WHICH_THE_(RE)ASSOCIATION FRAME_IS_ TRANSMITTED_NOT_ACCEPTED Link not accepted because the link on which the (Re)Association Request frame is transmitted is not accepted. 139 1391 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 EPCS_DENIED_VERIFICATION_FAILURE EPCS priority access is temporarily denied because the receiving AP MLD is unable to verify that the non-AP MLD is authorized for an unspecified reason. 140 1392 Allocate Pending Edward Au TGbe StatusCodes IEEE Std 802.11-2020 9.4.1.9 Table 9-50 DENIED_OPERATION_PARAMETER_UPDATE Operation parameter update denied because the requested operation parameters or capabilities are not acceptable. 141 1393 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 MLO Link Information 133 1394 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 AID Bitmap 134 1395 Allocate Pending Edward Au TGbe Element ID Extension 1 IEEE Std 802.11-2020 9.4.2.1 Table 9-92 Bandwidth Indication 135   So you don’t need to ask twice 😊   -Robert     From: Edward Au < edward.ks.au@xxxxxxxxx > Sent: Thursday, January 26, 2023 8:22 AM To: Stacey, Robert < robert.stacey@xxxxxxxxx > Subject: 11be ANA request   Dear Robert,   I would like to request allocation of the following 6 items for TGbe:   Type of Request Resource Name Item Name Item Description Requested Value (if any) Requested by Task Group Requested by Name Allocate StatusCodes DENIED_LINK_ON_WHICH_THE_(RE)ASSOCIATION FRAME_IS_ TRANSMITTED_NOT_ACCEPTED Link not accepted because the link on which the (Re)Association Request frame is transmitted is not accepted.  

IEEE 802.3 Open Revision Requests
Order by Request Number IEEE 802.3 Open Revision Requests Order by Request Number Req# Status Standard Clause Date Subject 1380 B 802.3.2-2019 Various, see details 08-Sep-20 MAC address format 1383 B 802.3.1-2013 Various, see details 19-Nov-20 References to IEEE Std 802.1D 1394 B 802.3-2022 98.2.1 18-Feb-22 Clause 98 HSM support 1395 B 802.3-2022 147.8 22-Mar-22 Mixing segment specifications 1396 B 802.3-2022 147.8 22-Mar-22 Mixing segment specifications 1397 B 802.3-2022 1.4.473 01-Apr-22 Definition of "PoDL PSE" 1398 B 802.3-2022 Various, see details 23-May-22 Primitive name 1399 B 802.3-2022 56.1.3 06-Jun-22 Split Table 56-1 by media type 1400 B 802.3-2022 4.1.2.2 13-Jul-22 Description of collision 1401 B 802.3-2022 144.3.5 09-Sep-22 Remove GLID from list 1402 B 802.3-2022 135F.1 01-Dec-22 Typo 1403 B 802.3-2022 Table 119-5 09-May-23 Typo 1404 B 802.3-2022 Annex 55A 12-May-23 Machine-readable extracts 1405 B 802.3-2022 Various, see details 26-May-23 Formatting error 1406 B 802.3-2022 Various, see details 26-May-23 Incorrect cross-reference 1407 B 802.3-2022 Various, see details 02-Jun-23 Update interface list 1408 B 802.3-2022 30.12.3.1.59 07-Jul-23 "PD" not "PSE" 1409 B 802.3-2022 30.12.3.1 10-Jul-23 Duplicate subclause numbers 1410 B 802.3-2022 Various, see details 06-Aug-23 Typo 1411 B 802.3-2022 99.3.6 06-Aug-23 mCRC value mapping 1412 B 802.3-2022 99.4.7.1 06-Aug-23 State diagram conventions 1413 B 802.3-2022 99.4.7.7 18-Aug-23 SMDS_ENCODE() definition 1414 B 802.3-2022 99.4.7.7 18-Aug-23 Typo 1415 B 802.3-2022 149.8.2.1 07-Sep-23 Error in return loss limit 1416 B 802.3cy-2023 165.8.2.1 07-Sep-23 Error in return loss limit 1417 B 802.3ck-2022 161.5.3.8 20-Sep-23 am_rxpayloads derivation 1418 B 802.3-2022 Figure 36-3 20-Sep-23 Incorrect title 1419 B 802.3-2022 Figure 99-6 22-Sep-23 Missing action 1420 B 802.3ck-2022 116.4 29-Sep-23 Incorrect delay constraints 1421 I 802.3-2022 97.4.2.4 11-Oct-23 infofield_complete behavior 1422 B 802.3-2022 97.4.2.4.10 11-Oct-23 Requirement conditional on EEE 1423 B 802.3ck-2022 Various, see details 08-Nov-23 AC-coupling to test points 1424 B 802.3ck-2022 Various, see details 08-Nov-23 Add measurement frequency 1425 B 802.3-2022 Figure 119-11 13-Dec-23 Typo 1426 B 802.3-2022 149.1.3 18-Jan-24 Extraneous signal 1427 B 802.3-2022 120G.3.3.5.2 25-Jan-24 Incorrect reference point 1428 R 802.3-2022 132.1.6 07-Feb-24 Incorrect cross reference 1429 R 802.3-2022 46.3.4.3 02-Apr-24 State diagram transition 1430 R 802.3-2022 Table 141-20 03-Apr-24 Incorrect column headings 1431 R 802.3-2022 Various, see details 29-Apr-24 Update reference Return to 802.3 Maintenance Requests Page Last Update: 08 May 2024

Cell: +1 (819) 609-1394 E-Mail: francois.menard@xxxxxxxxxxx Follow-Ups : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Glen Kramer Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Duane Remein Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia References : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Shawn Esser Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Marek Hajduczenia Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella Prev by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by Date: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Previous by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Index(es): Date Thread

Re: [STDS-802-11-TGAZ] TGaz Sep. 9th Telecon Agenda and Call for Submiss Thread Links Date Links Thread Prev Thread Next Thread Index Date Prev Date Next Date Index Re: [STDS-802-11-TGAZ] TGaz Sep. 9th Telecon Agenda and Call for Submissions To : STDS-802-11-TGAZ@xxxxxxxxxxxxxxxxx Subject : Re: [STDS-802-11-TGAZ] TGaz Sep. 9th Telecon Agenda and Call for Submissions From : "Das, Dibakar" < dibakar.das@xxxxxxxxx > Date : Thu, 10 Sep 2020 17:52:45 +0000 Hi Jonathan,   Can you please add the following CR submissions to the queue: 11-20-1392- CR for 11.22.6.3.3 (Dibakar Das) 11-20-1393- Misc CR for Clause 9 (Dibakar Das) 11-20-1394- Misc CR for Clause 11 (Dibakar Das) ?  

Probably useful to the customers, >although accurate network timing and good QOS are >likely to be perceived as threats by IEEE 1394 zealots. > >DVJ > > >David V.

>Although I have chaired four different IEEE WGs, and two SGs (1196 Nubus 2, >1394, 1394b, and 1394c), those were all MSC-sponsored, and I was certainly >inexperienced with 802 procedures, much less 802.3 procedures.

Some overall news: * The IEEE SA Standards board approved the 1394 revision PAR.

Johas Teener - Mike@Teener.com PGP ID 0x3179D202 23 Acacia Way, Santa Cruz, CA 95062-1313 +1-831-247-9666, fax +1-831-480-5845 ------------------- www.teener.com ------------------------ Prev by Date: Re: [RE] Overprovisioning (was Re: [RE] CE applications) Next by Date: Re: [RE] CE applications (was: RE: [RE] Focus of discussions) Prev by thread: Re: [RE] Requirement: Bridging to 1394 Next by thread: Re: [RE] Overprovisioning (was Re: [RE] CE applications) Index(es): Date Thread

The following presentations were made: #1 Geoff Thompson, Nortel – Spyder-LAN (see Spider-LAN.ppt) Discussion: 1394 compatibility 100Mbps compatibility Can spyder mode be originated and best-effort data be later sent from the same DTE Can spider elements be cascaded?

Kind regards Stephen On Thu, 16 Nov 2023 at 14:47, Hanxiao (Tony, WT Lab) < 0000177ab8f731c4-dmarc-request@xxxxxxxxxxxxxxxxx > wrote: --- This message came from the IEEE 802.11 Chairs' Advisory Committee Reflector --- Hi Stephen,          TGbf would like to request one more motion (Now totally 3 motions):     Having approved comment resolutions for all of the comments received from LB276 on P802.11bf D2.0 as contained in document 11-23/1394r12, https://mentor.ieee.org/802.11/dcn/23/11-23-1394-12-00bf-lb276-comments-and-approved-resolutions.xlsx Instruct the editor to prepare P802.11bf D3.0 incorporating these resolutions and, Approve a 30 day Working Group Recirculation Ballot asking the question “Should P802.11bf D3.0 be forwarded to SA Ballot?”  

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

From IEEE Std 1394 Serial Bus experiences, as well as the telecom industry as a whole, the value of synchronous transfers is greatly increased if time-of-day clocks can also be synchronized.

.: IEEE 802.11-98/217 Submission System Architecture Overview P r i n t e r C a m e r a G a m e P a d U S B Lamp Smoke Detector Thermostat Security System Power Line 78 Stereo Camcorder VCR TV 1394 Phone Cable Grandma’s Brownies 3 cups flour 1 cup grated chocolate 1 cup sugar 1 stick butter Control Point May 1998 Stuart K.

Most noteable are IEEE 754 Floating Point >> > and IEEE 1394, and other microprocessor standards.

. – Identified points of agreement on autonegotiation – Agreed to specify 10 GbE serial, GbE serial and 10 GbE four lane (change of Five Criteria approved to be consistent with these interface objectives) – Adopted definition of “improved FR4” – Signaling ad-hoc to be formed 16 July 2004 IEEE 802.3 Report 7 802.3aq 10GBASE-LRM • Extends Ethernet capabilities at 10 Gb/s – Operation over installed multimode fiber – New physical layer to run under 802.3ae specified XGMII • Working toward first draft 16 July 2004 IEEE 802.3 Report 8 Congestion Management SG • Adopted narrowed problem statement: 802.3 MAC client needs to be able to limit traffic being received from its peer to avoid congestion due to oversubscription • Agreed on a partial set of objectives for a possible project • Study Group extended through November plenary meeting 16 July 2004 IEEE 802.3 Report 9 Frame Expansion SG • Address request from 802.1 to expand 802.3 maximum frame size to allow addition of protocol header and trailer fields – IEEE 802.3 Ad Hoc/CFI held – Also subject of joint technical plenary with 802.1 – Half duplex repeater limits and other PHY layer limitation were discussed, additional study required for PHY layers that support retiming in the data path • Study Group approved by 802.3 and Executive Committee 16 July 2004 IEEE 802.3 Report 10 Residential Ethernet SG • Successful call for interest held on Residential Ethernet – Focus is requirements of consumer electronics within the home – Issues include latency, latency jitter, and timing synchronization for consumer media distribution/playback • Study Group approved by 802.3 and Executive Committee 16 July 2004 IEEE 802.3 Report 11 Other Activities • IEEE 1394 tutorial sponsored • New maintenance requests approved, interpretations response approved • Autumn interim meeting – Details are TBD – Target week: 27 September 2004 – Target location: North America

John S. wants to make sure that we provide what is necessary to support requirements for 1394.

- Speeds - Connectivity Study Item 3: Investigating existing mechanismsInvestigating existing mechanisms - 802.3 Clause 64, Clause 65 - 1394 isochronous - Gibson MaGIC Study Item 4: Interactions with 802.1Interactions with 802.1 - Ex: 802.1d, 802.1p, 802.1q, etc… IEEE 802.3 CFI Portland July 2004 7July 2004 Call for InterestCall for Interest Request 802.3 at the Closing Plenary to form a Residential Ethernet Study Group to develop a standards project proposal (PAR and 5 Criteria) for Residential Ethernet.

Here is a list of some of my relevant qualifications: Performance modeling activities: Founded and run AmerNet which specializes in architecture analysis and performance modeling for networking and communication products and have many clients in various committees of the IEEE 802 and elsewhere Recognized expert in the field of network/communication performance analysis and modeling and author of many publications, articles and papers on various aspects of LAN/Networking performance analysis Worked in the LAN performance analysis group at IBM since 1988 Activities in RPR: Have been participating in the RPRSG since the first meeting in May 2000 Volunteered to chair the adhoc committee on performance modeling for the RPRSG Successfully led the performance adhoc committee to reach agreement on a lot of open issues related to the performance modeling efforts Drafted and posted a draft charter for the RPR performance committee as well as the list of its accomplishments  Activities in the IEEE 802 standards and other standard bodies: An active participant in the IEEE 802 since 1992 Have been a voting member of 802.3, 802.5, 802.15 and 802.17 Represented IBM's position in various IEEE 802 committees Provided a tutorial on QoS and priorities in Token Ring LANs based on extensive simulations and performance analysis The main IEEE 802 representative for Rockwell Semiconductor Systems Chaired the QoS study group from July 1998 till March 1999 An active participant in the IETF, NP Forum and IEEE 1394 Educational background: MS degree in Electrical Engineering (Caltech - 1986) Professional background: Specialized in the area of LAN performance analysis for my entire career Responsible for the performance analysis of many system architectures and networking chips at IBM Responsible for joint research work between IBM and NC-State University in the area of multimedia performance in LAN environments Founded AmerNet in May 1998 which specializes in performance modeling and architectural analysis In response to a request from our chair to clarify why I am active in IEEE 802.17:   AmerNet provides services related to IEEE activities.

Most noteable are IEEE 754 Floating Point > and IEEE 1394, and other microprocessor standards.

.: Corning Cable SystemsThe future proof solution wagner_1_1100 Pattern for other protocolls • 1000BASE-T on 4 pairs is bound to use the signalling pairs (part of the 802.3af objectives) • ATM, Token Ring, IEEE 1394, FDDI TP-PMD, PBX and other may follow suit easily 13Slide Nr.: Corning Cable SystemsThe future proof solution wagner_1_1100 Signal Pairs 1,2 – 3,6 Idle Pairs 4,5 – 7,8 Technical feasibility Economical feasibility Whenever pairs present and not used by 3rd party Compliant with ISO/IEC 11801 Standard worldwide NO Liaison Letter proper consideration of NO Easy to implement for 1000BASE-T NO Futureproof NO Appliable to installed cabling park 100 % < 70 % Exploitation of park beyond ICO/IEC 11801 NO End system Win - End user Win loose 14Slide Nr.: Corning Cable SystemsThe future proof solution wagner_1_1100 CONCLUSION To provide power via the MDI The Signal pairs 1-2 , 3-6 are the optimal solution for the largest market segment.

(ADSL2+, 1394, …) • Any other outreach (companies, countries) of importance to inform or engage?