Examples of devices which can be connected include computers, computer peripherals (similar to USB 2.0's 480 Mbps capability), PDA/HPCs, printers, set top boxes, information kiosks, image displays, virtual reality games, DVD players, and camcorders (similar to IEEE 1394's 400 Mbps capability).

The distinction between standards is getting fuzzy: 1394 over CAT-5, security over multiple transports, multiple transports over the same PHYs.

. >> This identifier uniquely identifies a device, such as a >> current IEEE 1394 node or a future memory, refrigerator, >> video controller, power supply, etc. >> >> Note that the same identifier must not be used for more than >> one purpose.

- 649 15 Wireless Gigabit Ethernet applications - · LOS · Data Rate:1.25 Gbps duplex · Range: ~ 6 m 653 16 · Replacement for 1394 FireWire · Replacement for USB · Military – future combat systems, secure communication - · LOS and NLOS (people) · 100 to 500 Mbps link, 1 Gbps in 2007 · Short range 665 Submission Page D.

. >> > >> >As an MSC representative, I would have provided >> >such a follow-up on the addresses used within >> >MSC sponsored projects (754, 1394, etc.), as >> >a duty to my position. >> > >> >I prefer to see the evidence before jumping into >> >denial or conclusions, since (through out my career) >> >I have seen suboptimal decisions made when this >> >ordering is reversed. >> > >> > >> >If you feel strongly about this, >> >Yes, I feel strongly about conservation of OUI space. >> >I naively thoutht that to be the premise of our charter. >> >Times change, I suppose... >> > >> >Cheers, >> >DVJ >> > >> > >> -----Original Message----- >> > >> From: Geoff Thompson [ mailto:gthompso@nortel.com ] >> > >> Sent: Wednesday, August 08, 2007 3:07 PM >> > >> To: Floyd Backes >> > >> Cc: dvj@alum.mit.edu; Geoff Thompson; a.n.weaver@IEEE.ORG; >> > >> stds-rac@IEEE.ORG >> > >> Subject: RE: Request for multiple OUI assignments >> > >> >> > >> >> > >> At 11:48 AM 8/8/2007 , Floyd Backes wrote: >> > >> >If you feel strongly about this, you could review the >> latest version of >> > >> >802.1 MAC Bridging, figure out how it can be made to work >> using the same >> > >> >MAC address on every port, get a PAR to update the >> standard, and then >> > >> >slug it out with Mick over the ensuing 2 years to produce a revised >> > >> >standard.

The distinction between standards is getting fuzzy: 1394 over CAT-5, security over multiple transports, multiple transports over the same PHYs.

Technologies such as IEEE 1394, Bluetooth and USB exist today but each has their own encapsulation, protocols, timing control, etc. such that building interworking functions is difficult.

The relevant standards include: >> >> CSMA/CD (IEEE 802.3, ISO 8802-3) >> Token Bus (IEEE 802.4, ISO 8802-4) >> >> Token Ring (IEEE 802.5, ISO/IEC 8802-5) >> >> IEEE 802.6 (ISO/IEC DIS 8802-6) FDDI (ISO 9314-2) >> >> WLAN (IEEE 802.11, ISO/IEC 8802-11) >> B) >> The 'company_id' relevant standards include: defined >> in IEEE Std >> 1212-1991 Control and Status Register (CSR) Architecture referenced >> by IEEE Std 896.2-1991 Futurebus+Physical Layers and Profiles >> IEEE Std 1596-1992 Scalable Coherent Interface >> IEEE Std 1394-1995 Serial Bus document.

The IEEE/RAC has (in my experience) attempted to avoid identifying specific instances of "things", such as I/O drivers on IEEE Std 1394.

Examples of devices which can be connected include computers, computer peripherals (similar to USB 2.0's 480 Mbps capability), PDA/HPCs, printers, set top boxes, information kiosks, image displays, virtual reality games, DVD players, and camcorders (similar to IEEE 1394's 400 Mbps capability).

All options on the table Hybrid E/O Module 1550 nm E/O Module Single Mode Fiber 1-30+ Residences 100 Base FX GBE Idealized Port cost At Market Port Cost Easily Upgraded to 10 GE or WDM for higher rates Ethernet in the Last Mile - 14 Active MDUActive MDU MDU oriented media Hybrid E/O Module 1550 nm E/O Module Single Mode Fiber 1-30+ Apartments Also suitable for urban hybrid deployment (business & residential users) 100 Base FX GBE Similar to curb criteria Ethernet in the Last Mile - 15 Digital Access GatewayDigital Access Gateway (CPE)(CPE) 100 Base FX Potentially hybrid media Hybrid E/O Module IEEE 1394 100 BaseT CATV POTS Remote Power over Copper Loop Services platform

I’ve uploaded the received comments to mentor:  https://mentor.ieee.org/802.11/dcn/23/11-23-1394-00-00bf-lb276-comments-and-approved-resolutions.xlsx A few action items: PoCs : Please review the comments that I have tentatively assigned to your area, and let me know if you any changes are needed.

I ’ ve uploaded the received comments to mentor:  https://mentor.ieee.org/802.11/dcn/23/11-23-1394-00-00bf-lb276-comments-and-approved-resolutions.xlsx A few action items: PoCs : Please review the comments that I have tentatively assigned to your area, and let me know if you any changes are needed.

IEEE Std 802.3ae-2002 errata • Requests 1131 (4.2.7.1) and 1133 (4.2.8) – Strikeouts in approved draft not in published standard D5.0 D5.0 Std Std Num Stat Std Subclause Date Subject 1105 B 802.3ae-2002 45.2.3.15.1 14-Nov-02 Register cross reference error 1106 B 802.3ae-2002 30.3.2.1.5 20-Feb-03 Incorrect cross references 1108 E 802.3ae-2002 Annex 48B 30-May-03 Jitter test methods 1110 B 802.3ae-2002 53.15.4.3 17-Aug-03 Management Functions, item MR6 1111 B 802.3ae-2002 53.15.4.3 17-Aug-03 Management Functions, item MR7 1112 E 802.3ae-2002 Various 17-Aug-03 PICS copyright release statement 1113 B 802.3ae-2002 45.2.3 17-Aug-03 PCS registers 1114 B 802.3ae-2002 45.2.5.8 17-Aug-03 10G DTE XGXS lane status register 1115 B 802.3-2002 23.7.1, 02-Oct-03 MDI Connectors 1116 E 802.3af-2003 Annex 33A 22-Oct-03 PSE Detection of PDs - Figure 33A.2 1117 B 802.3af-2003 33.2.3.7 31-Oct-03 PSE State Diagrams 1118 B 802.3ae-2002 48.2.4.2 31-Oct-03 Idle ||I|| 1119 B 802.3af-2003 33.2.7.2 15-Nov-03 PSE classification 1120 B 802.3-2002 1.4 25-Nov-03 Definition of Type 1121 B 802.3-2002 28C.6 17-Dec-03 Message Code #5 1122 B 802.3-2002 28C.7 17-Dec-03 Message Code #6 1123 B 802.3-2002 24.2.4.2 05-Jan-04 Transmit 1124 B 802.3-2002 Front 05-Jan-04 Introduction to IEEE Std 802.3-2002 1125 B 802.3-2002 24.8.3.2 10-Feb-04 PICS - PCS functions 1126 B 802.3-2002 26.4.1 10-Feb-04 Medium Dependent Interface (MDI) 1127 B 802.3-2002 3.2.3 10-Feb-04 Address Fields 1128 E 802.3-2002 36.2.5.1.4 1-Mar-04 Functions & Variables 1131 E 802.3ae-2002 4.2.7.1 10-Mar-04 Constants, types, and variables 1132 B 802.3ae-2002 4.2.3.1 10-Mar-04 Transmit data encapsulation 1133 E 802.3ae-2002 4.2.8 16-Mar-04 Frame transmission B – Ready for Ballot E - Errata Request to be included in IEEE P802.3REVam Auto-negotiation selector field • Request from IEEE std 1394 –Allocated value 00100 –Web site will be updated – Include in IEEE P802.3REVam Auto-negotiation selector field • IEEE Std 802.3REVam Maintenance 8 – PAR approved 27 February 2004 by IEEE-SA Standards Board (continuous processing). – Plan dependent on IEEE P802.3ah approval date • Preceding based on June approval date IEEE P802.3REVam Maintenance 8 Task Force status IEEE P802.3REVam Plans • Meet at May Interim meeting – Final chance to add requests – Review draft status • Produce draft D1.0 – Consolidate edition • Including all B (Ready for Ballot) or E (Errata) request – Approved IEEE P802.3ah draft • Pre-circulate D1.0 prior to July plenary – Request Working Group Ballot • The Maintenance web site is at: http://www.ieee802.org/3/maint/index.html • The Maintenance request form is available at: http://www.ieee802.org/3 /private/maint/revision_request.html Username: ****** Password: ********* Password is case sensitive Maintenance Web Information

Clause Subject Action 1394 98.2.1 Clause 98 HSM support “Ready for ballot” 1395 147.8 Mixing segment specifications “Ready for ballot” 1396 147.8 Mixing segment specifications “Ready for ballot” 1397 1.4.473 Definition of “PoDL PSE” Suggested modification to proposed change https://www.ieee802.org/3/maint/requests/maint_1394.pdf https://www.ieee802.org/3/maint/requests/maint_1395.pdf https://www.ieee802.org/3/maint/requests/maint_1396.pdf https://www.ieee802.org/3/maint/requests/maint_1397.pdf IEEE P802.3 Maintenance report – July 2008 PlenaryVersion 1.0 IEEE P802.3 (IEEE 802.3dc) ballot results July 2022 (r0) IEEE 802.3 Maintenance Task Force 5 • D3.0 initial SA ballot (opened 1 December 2021, closed 31 December 2021) • D3.1 1st SA recirc. ballot (opened 15 February 2022, closed 2 March 2022) • D3.2 2nd SA recirc. ballot (opened 15 March 2022, closed 30 March 2022) D3.0 D3.1 D3.2 Count % Status Count % Status Count % Status Actual Req’d Actual Req’d Actual Req’d Abstain 3 2 < 30 PASS 3 2 < 30 PASS 3 2 < 30 PASS Disapprove 10 - - - 4 - - - 2 - - - Disapprove w/o comment 0 - - - 0 - - - 0 - - - Approve 92 90 > 75 PASS 108 96 > 75 PASS 111 98 > 75 PASS Ballots returned 105 77 > 75 PASS 115 84 > 75 PASS 116 85 > 75 PASS Voters 136 - - - 136 - - - 136 - - - Comments 110 - - - 20 - - - 1 - - - IEEE P802.3 Maintenance report – July 2008 PlenaryVersion 1.0 Revision project status July 2022 (r0) IEEE 802.3 Maintenance Task Force 6 IEEE Std 802.3-2022 was approved by the IEEE SA Standards Board on 13 May 2022!!!

Cell: +1 (819) 609-1394 E-Mail:  francois.menard@xxxxxxxxxxx       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 Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard 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

Cell: +1 (819) 609-1394 E-Mail:  francois.menard@xxxxxxxxxxx       Follow-Ups : Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Barry Colella 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 Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Glen Kramer 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

Cell: +1 (819) 609-1394 E-Mail:  francois.menard@xxxxxxxxxxx       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 Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Francois Menard Re: [802.3_NGEPON] ONU ASIC and wavelength plans From: Glen Kramer Prev by Date: [802.3_NGEPON] Macau material is uploaded Next by Date: Re: [802.3_NGEPON] 25G ONU Options to increase Network Capacity Previous by thread: Re: [802.3_NGEPON] ONU ASIC and wavelength plans Next by thread: [802.3_NGEPON] IEEE 802.3ca Task Force :: Macau deadline approaching Index(es): Date Thread

Claudio   Assigned Ready for Motion Approved RfM+A Alecs 18 0 18 18 Ali 34 0 33 33 Assaf 26 0 0 0 Atsushi 47 12 22 34 Benedikt 8 0 0 0 Chaoming 2 0 2 2 Cheng 46 0 38 38 Chris 15 0 0 Claudio (E) 66 13 53 66 Claudio (T) 29 2 27 29 Dibakar 25 0 0 0 Dongguk 8 0 3 3 Dong 32 0 9 9 Mahmoud 17 1 10 11 Mengshi 20 0 20 20 Mike M. 1 0 1 1 Naren 34 11 10 21 Ning 1 1 0 1 Pei 11 0 11 11 Rojan 4 4 0 4 Rui Du 27 6 11 17 Rui Yang 8 0 8 8 Shuling (Julia) 4 0 0 0 Stephen S. 24 0 9 9 Xiandong 13 0 13 13 Yan 10 0 4 4 Zhanjing 8 0 8 8 Zhuqing 7 7 0 7 All 545 57 310 367 0.104587156 0.5688073 0.6733945     Submitted Ready for Motion Approved RfM+A PoC Annexes 29 2 27 29 Claudio DMG 84 12 27 39 Alecs Editorial 67 13 54 67 Claudio Exchange 98 4 72 76 Cheng Misc 26 3 21 24 Zinan OST 147 17 55 72 Chaoming Reporting 60 5 35 40 Chris SBP 34 1 19 20 Cheng All 545 57 310 367 0.104587156 0.5688073 0.673394     From: Claudio da Silva Sent: Friday, November 3, 2023 11:00 AM To: STDS-802-11-TGBF@xxxxxxxxxxxxxxxxx Subject: Updated group documents   All,   I have uploaded updated versions of our comment resolution documents: LB276 comments and approved resolutions ( https://mentor.ieee.org/802.11/dcn/23/11-23-1394-09-00bf-lb276-comments-and-approved-resolutions.xlsx ) LB276 SPs and motions ( https://mentor.ieee.org/802.11/dcn/23/11-23-1494-05-00bf-lb276-sps-and-motions.xlsx ) Please review and let me know if you find problems.

I ’ ve uploaded the received comments to mentor:  https://mentor.ieee.org/802.11/dcn/23/11-23-1394-00-00bf-lb276-comments-and-approved-resolutions.xlsx A few action items: PoCs : Please review the comments that I have tentatively assigned to your area, and let me know if you any changes are needed.

Several years ago we had a similar experience with the IEEE 1394 and USB specifications.

Flatman IEEE 802.3 Chair/Liaison Mr Grow/Mr Flatman IEEE 802.11Chair Mr Kerry, IEEE 802.15 Mr Heile IEEE 1394 Mr P.

I ’ ve uploaded the received comments to mentor:  https://mentor.ieee.org/802.11/dcn/23/11-23-1394-00-00bf-lb276-comments-and-approved-resolutions.xlsx A few action items: PoCs : Please review the comments that I have tentatively assigned to your area, and let me know if you any changes are needed.

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.

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.