RE: Augmenting MAU-MIB - was: RE: EFM MIB Internet-Drafts, WG Meetings

Yep, my bad.  Forgot about that half-dup stuff.  

- Matt

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Monday, October 27, 2003 9:57 AM
> To: Matt Squire
> Cc: Edward Beili; Romascanu, Dan (Dan); [email protected]
> Subject: Re: Augmenting MAU-MIB - was: RE: [Hubmib] EFM MIB
> Internet-Drafts, WG Meetings
> 
> 
> Matt,
> 
> Since EFMCu uses the half-duplex mode of the MAC to do MAC-PHY rate
> matching, PAUSE frames cannot be used. The current text of the draft
> (D2.1) states:
> 
> "Both EFM Copper port PHYs are only defined for full duplex operation
> (notwithstanding the definition of PHY-MAC Rate Matching (see 61.2.1)
> which requires that the MAC operates in half-duplex mode for 
> the purposes
> of flow control). PAUSE frame transmission via EFM Copper PHYs is
> therefore precluded, since the requirements of 31B.1 (see Clause 31)
> restrict the transmission of PAUSE frames to DTEs configured 
> to the full
> duplex mode of operation."
> 
> Regards,
> 
> Michael Beck
> Editor, EFM/Copper
> 
> Matt Squire wrote:
> > 
> > > Dan,
> > >
> > > Here are some arguments for not supporting the EtherLike-MIB
> > > (just for the purpose of argument):
> > >
> > > Let's look at some of the control groups in EtherLike-MIB 
> (rfc-3635):
> > > - dot3PauseTable - The EFMCu interfaces do not support Pause
> > > frames so this
> > > may be omitted.
> > 
> > I don't know this is true.  I know that it is discussed 
> that PAUSE can slow down or interfere with OAM operation on 
> Ethernet links.  But nothing really stops one from 
> implementing PAUSE if they wanted to.
>