Maintenance Adhoc Overview - PowerPoint PPT Presentation

About This Presentation
Title:

Maintenance Adhoc Overview

Description:

... ReceiveFrame() in Clause 4 ... Clauses (31, 31B, 64) were modified to use the Clause 2 ' ... Clause 64 (Multipoint MAC Control) specifies the 'Control ... – PowerPoint PPT presentation

Number of Views:72
Avg rating:3.0/5.0
Slides: 12
Provided by: Edit156
Learn more at: https://www.ieee802.org
Category:

less

Transcript and Presenter's Notes

Title: Maintenance Adhoc Overview


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()/Receive
    Frame() functions

3
802.3-2005 MAC Control sublayer is part of MAC
4
802.3ay D2.3 MAC Control sublayer no longer
part of MAC
5
State diagram from Clause 4 (802.3ay D2.2)
6
An instance of impact on MAC Control that wasnt
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

7
MPCP Control Multiplexer
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?

9
Backup
10
PAUSE Operation Transmit State Diagram (Figure
31B-1)
11
OAM Multiplexer State Diagram (Figure 57-7)
Write a Comment
User Comments (0)
About PowerShow.com