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.

Simple light weight encoders that compress 9 or 10 to one have been suggested to allow this content to then be sent to a remote device over 1394 or other networks.

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!!!

RBR includes features appropriate for the > low-latency > backplane environment: destination-based flow control, low-power > short-haul > PHY, backplane-to-backplane links, transport of IEEE-1394 isochronous > data, > and support of IEEE-1596 memory-update operations." > > Background material includes: > http://grouper.ieee.org/groups/msc/MSC200404/RbrSlides2004Mar31.pdf > http://grouper.ieee.org/groups/msc/MSC200401/RprBackplane.pdf > > Items on the agenda include: > 1) Formulation of email reflector lists. > 2) Review of approved PAR. > 3) Sollicitation of technical inputs and strawman proposals. > 4) Discussion of related activities. > 5) Future meeting schedule. > 6) Other items as requested. > > In particular, this is an opportunity to suggest directions, revisions > of the slides and objectives, and/or strawman proposals.

- 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.

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 distinction between standards is getting fuzzy: 1394 over CAT-5, security over multiple transports, multiple transports over the same PHYs.

Your may also want to read IEEE 1394, which (some of us feel) should be useful for background and is also highly desirable to support in a reasonably transparent-to-traffic fashion.

Its good for 802 and its good for 1394.

We are also looking at a 1394 traffic model (low quality video model).

It was noted that meshing also needs “hand over”. 11:42 Peter Johansson presented new MAC primitives for Synchronization support for 1394 or any time sync’ed protocol adaptation (document 03-0444-00-0030).

. >> 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.

There is an additional standard, Wireless 1394, in development with expected completion in September 2001. 13.

Like the 1394 standards for wireless, this would provide another example of the importance and usefulness of having and following standards that any consumer or engineering manager could point to - which ultimately helps us all.  

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.

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

. 802.3af, 802.3at TIA-862 building automation and security devices Remote cameras IP telephone Multimedia devices supported by IEEE Std 1394-2008.

. > >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.

Simple light weight encoders that compress 9 or 10 to one have been suggested to allow this content to then be sent to a remote device over 1394 or other networks.

Reconciliation sub layer Layer Model MAC and Higher layers Page 5 Clause 28 background Established for copper technologies and can Negotiate Multiple speeds Clause 28 state machines verified over years and have been made robust 7 years of AN Interoperability testing shows that most issues are associated with Software/Drivers that control the AN process (Device Management) The protocol and state machine itself is robust Most problems show up when system does not properly use the information provided by the AN protocol[2] Initial interoperability tests focused on accuracy of AN State Machines but later new tests were added to focus on Device Management to address system level issues (Reference: [2] UNH- IOL Clause 28 AN management system test suite Page 6 Advantages of using Clause 28 Auto-Negotiation function located below the PMD layer (Fig 28-2) [4] Perfect position of sub layer within PHY Ability to negotiate multiple speeds Ability to work with different signaling NRZ and non NRZ signaling (MLS) Does not depend on PCS encoding Self Clocking Interoperability issues have been identified and most issues are associated with Device Management The state machine has been field proven over multiple PHY generations Page 7 Clause 28 Base Page Clause 28 Base Page definition S0 S1 S2 S3 S4 A0 A1 A2 A3 A4 A5 A6 A7 RF Ack NP Next Page Acknowledge Remote Fault Page 8 Proposed 802.3ap Base Page Clause 28 Base Page definition S0 S1 S2 S3 S4 A0 A1 A2 A3 A4 A5 A6 A7 RF Ack NP IEEE Std 1394 00100 Reserved for future Auto-Negotiation development11111 IEEE 802.3ap Backplane Ethernet10100 IEEE Std 802.5 11000 IEEE Std 802.9 ISLAN-16T01000 IEEE Std 802.310000 Reserved for future Auto-Negotiation development00000 Selector descriptionS 0 S 1 S 2 S 3 S 4 Proposed selector field for 802.3ap TBDA7 Reserved for Future TechnologyA4 TBDA6 Pause OperationA5 Reserved for Future TechnologyA3 802.3ap 10Gb/s 4-LaneA2 802.3ap 10Gb/s 1-LaneA1 802.3ap 1Gb/s 1-LaneA0 Technology field bit assignmentsBit Proposed 802.3 Base page bit assignments Next Page Acknowledge Remote Fault Page 9 Next Page Assignment Continue to have Next Page for future proofing and to negotiate additional parameters if any Next Page encodings same as Clause 28.2.3.4 Page 10 Functional reference diagram Use Clause 28 functional reference diagram Technology dependent PMAs for 802.3ap Page 11 Transmit & Receive state machines Use Clause 28.3 State diagrams and transmit/receive/arbitration state machine definitions for exchanging base and next pages [4] The state diagram timers to use clause 28.3.2 definitions Some of the timer variables could be redefined for faster link convergence Goal: maximum 3 sec for link convergence NLP Receive link integrity state diagram is not needed and all reference in state machines will be removed for 802.3ap Page 12 Management Data Interface Use Clause 45 MDIO interface and Register space [4] Clause 22 Management frame format Clause 45.4 Electrical interface definition Clause 45.2.1 PMA/PMD register set definition Use Clause 45 interface (ST=00) to access Clause 45 registers Access Clause 22 registers if present in a legacy device through Clause 45 management interface (Register 2.5.0 & STcode =01) Other options considered: Using Clause 22 mechanism to access Clause 45 register set (Leverage mechanism defined by 802.3ah EFM [5]) Since there is no need to access control bits relevant to 10/100/1000 twisted pair operation it is proposed to use clause 45 interface to access clause 45 register space Page 13 Management Registers Use Clause 45.2.1 PMA/PMD register set [4][5] Define additional bits and registers for 802.3ap Lot of space available for future proofing Define 1.0.5:2 speed selector bits for 1G speeds: 0x00=10Gb/s; 0x01 taken by EFM; 0x02=1Gb/s Add 1Gb/s speed ability bit to Register 1.4.3 to indicate 1G speed (Table 45-5) Bit 1.5.0 to indicate clause 22 registers implemented and accessed through clause 45 interface Bit 1.5.1 indicates PMA/PMD device present in package Define 1.7.4:3 (two bits) to indicate different 802.3ap PMA/PMD types Add additional bits to the 10G PMA/PMD extended abilities register (Register 1.11) to indicate 802.3ap PMD types (Bits:1.11:3:2); Bit 1.11.0 taken by 10GBASE-CX4 and 1.11.1 possibly by 10GBASE-T Continue to use Registers 1.9 and 1.10 for Transmit/Receive functions Define 1.110 to 1.1xx new registers for 802.3ap specific functions Page 14 Summary Locate Auto-Neg function to be below PMD as shown in layer model (Figure 28-2) [4] New base page and selector fields for 802.3ap Backplane Ethernet Use Proposed SERDES compatible FLP [1] Use Clause 28 state machines for exchanging pages [4] Provide an informative annex for operation with legacy devices not supporting 802.3ap Auto-Negotiation Page 15 References [1] SERDES compatible FLP AN proposal for 802.3ap, July 04 Plenary http://ieee802.org/3/ap/public/jul04/szczepanek_02_0704.pdf [2] UNH-IOL Clause 28 Auto-Negotiation Management System Test Suite, UNH IOL Ethernet Interoperability Testing presentation http://ftp.iol.unh.edu/fec/anegSystem.pdf http://www.nbl.org.tw/nbl_old/nbl-iol-workshop/07_Ethernet_Overview.pdf [3] Earlier Auto-Neg presentations to Backplane Ethernet SG/TF http://www.ieee802.org/3/bladesg/public/mar04/chang_01_0304.pdf http://www.ieee802.org/3/ap/public/may04/ganga_01_0504.pdf [4] IEEE Std 802.3-2002, IEEE Std 802.3ae-2002 [5] IEEE Std 802.3ak-2004, P802.3ah approved draft D3.3 (to be published as IEEE Std 802.3ah-2004 )

I could imagine one that is used to tag all IEC 61883-type packets (the normal tagging and formatting system for consumer-electronics type streams in 1394). -- --------------------------------------------------------------- Michael D.

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).

There is an additional standard, Wireless 1394, in development with expected completion in September 2001. 13.

Its good for 802 and its good for 1394.