RE: New things for the EFM-CU-MIB

I believe that the WG should focus on completing the current charter
before discussing about any new work 'stemming from ... latest RFPs',
otherwise it risks to run forever trying to catch with the permanently
moving target of the Ethernet technology.  

Dan

 

> -----Original Message-----
> From: Edward Beili [mailto:[email protected]] 
> Sent: Friday, December 08, 2006 12:41 AM
> To: [email protected]
> Cc: Wijnen, Bert (Bert); Romascanu, Dan (Dan)
> Subject: [Hubmib] New things for the EFM-CU-MIB
> 
> Hi,
> 
> I would like to propose a few minor modifications to the 
> EFM-CU-MIB, to provide support for some carrier requirements 
> for the Ethernet over copper, stemming from some latest RFPs.
> 
> 1. Add a new leaf to efmCuPortStatusTable, showing the 
> equivalent length of the bonded link, which would be 
> calculated as a median of all the efmCuPmeEquivalentLength in 
> the link.
> 
> 2. Add an optional ability to specify Min and Max noise 
> margin (probably in efmCuPortConfEntry), which would allow 
> one to configure the working SNR range for the lines in the 
> bonded link, that is:
> - if the SNR Margin on the copper pair in the bonded link 
> (efmCuPmeSnrMgn) goes below specified Min margin, the pair 
> should re-train to achieve higher SNR margin than the Min 
> (e.g. efmCuTargetSnrMgn)
> - if the SNR Margin on the copper pair goes above specified 
> Max margin, the pair should/could lower its transmitted power 
> (e.g. using Power Back-off if efmCuAdaptiveSpectra is true).
> 
> 3. Add an ability to specify Min Power Back-off, to allow an 
> operator to limit the signal transmit power to a lower level 
> than that allowed by the spectral limitations placed by the 
> efmCuPme2BRegion and efmCuPme2BsMode.
> 
> I would appreciate your comments.
> 
> Regards,
> -E. 
>