1 / 11

Maintenance Adhoc Overview

This overview delves into the changes in MAC interface definitions in IEEE Std 802.3-2005 Maintenance Adhoc, addressing impacts, modifications, and necessary adaptations in the MAC Control sublayer. Considerations such as the Control Multiplexer and duration management during frame transmission are discussed for a thorough understanding of the updates.

larimer
Download Presentation

Maintenance Adhoc Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Maintenance Adhoc Overview Jeff Mandin PMC-Sierra July 2008

  2. Background • 802.3-2005 describes two different interfaces to the MAC: • MA_DATA.Request/Indication in Clause 2 • This is the ISO/IEC/802.1 interface • TransmitFrame()/ReceiveFrame() in Clause 4 • In 802.3as it was determined that this “longstanding discrepancy” between the interface definitions should be remedied • “Service to humanity” • MAC Control sublayer no longer an “optional” sublayer inside the MAC but instead a MAC client • State diagram added to reconcile MA_DATA.Request with TransmitFrame() • MAC Control Clauses (31, 31B, 64) were modified to use the Clause 2 “service interface primitives” instead of the TransmitFrame()/ReceiveFrame() “functions” 802.3 Maintenance Adhoc

  3. 802.3-2005: MAC Control sublayer is part of MAC 802.3 Maintenance Adhoc

  4. 802.3ay D2.3:MAC Control sublayer no longer part of MAC 802.3 Maintenance Adhoc

  5. State diagram from Clause 4 (802.3ay D2.2) 802.3 Maintenance Adhoc

  6. An instance of impact on MAC Control that wasn’t recognized (Maint #1196) • There are cases where the TransmitFrame() function cannot simply be replaced by the MA_DATA.Request() primitive • TransmitFrame() has “duration” ie. it does not complete until all supplied bits are transferred to the PHY • Clause 64 (Multipoint MAC Control) specifies the “Control Multiplexer” – which transmits frames to the MAC with extra gap time after IPG to enable the PHY to include FEC parity • In 802.3-2005, the Control Multiplexer relies on the duration of TransmitFrame() as part of its calculations of gap time • When TransmitFrame() is replaced by MA_Data.Request(), this calculation needs to be modified 802.3 Maintenance Adhoc

  7. MPCP Control Multiplexer 802.3 Maintenance Adhoc

  8. Questions for the adhoc • Are there other instances in the MAC Control clauses (or elsewhere) that were affected by the MAC interface change? • eg. Is the PAUSE operation transmit state diagram in figure 31B-1 in need of modification? • Is there a need to reevaluate the MAC interface changes affecting MAC Control? 802.3 Maintenance Adhoc

  9. Backup 802.3 Maintenance Adhoc

  10. PAUSE Operation Transmit State Diagram (Figure 31B-1) 802.3 Maintenance Adhoc

  11. OAM Multiplexer State Diagram (Figure 57-7) 802.3 Maintenance Adhoc

More Related