RE: New things for the EFM-CU-MIB

Dear Hubmib group members,

I would like to hear your opinion on the proposed additions to the =
EFM-CU-MIB specified in my original mail below.

Regards,
-E.


> -----Original Message-----
> From: Romascanu, Dan (Dan) [mailto:[email protected]]=20
> Sent: Monday, December 11, 2006 16:22
> To: Edward Beili; [email protected]
> Cc: Wijnen, Bert (Bert)
> Subject: RE: [Hubmib] New things for the EFM-CU-MIB
>=20
> I believe that the WG should focus on completing the current=20
> charter before discussing about any new work 'stemming from=20
> ... latest RFPs', otherwise it risks to run forever trying to
> catch with the permanently moving target of the Ethernet technology. =20
>=20
> Dan
>=20
> -----Original Message-----
> From: Matt Squire [mailto:[email protected]]=20
> Sent: Friday, December 08, 2006 2:53
> To: Edward Beili; [email protected]
> Cc: Wijnen, Bert (Bert); Dan Romascanu (E-mail)
> Subject: RE: [Hubmib] New things for the EFM-CU-MIB
>=20
> Hi Ed -=20
>=20
> The second two seem useful.  The first one doesn't seem that=20
> useful as it is easily derived from other entries.  In=20
> general, I'm not a big fan of adding 2nd level data (e.g.=20
> stuff derived from other stuff). =20
>=20
> My 2 cents.=20
>=20
> - Matt =20
>=20
> > -----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
> >=20
> > Hi,
> >=20
> > 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=20
> > copper, stemming from some latest RFPs.
> >=20
> > 1. Add a new leaf to efmCuPortStatusTable, showing the equivalent=20
> > length of the bonded link, which would be calculated as a median of=20
> > all the efmCuPmeEquivalentLength in the link.
> >=20
> > 2. Add an optional ability to specify Min and Max noise margin=20
> > (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=20
> > re-train to achieve higher SNR margin than the Min (e.g.=20
> > efmCuTargetSnrMgn)
> > - if the SNR Margin on the copper pair goes above specified Max=20
> > margin, the pair should/could lower its transmitted power (e.g. =
using=20
> > Power Back-off if efmCuAdaptiveSpectra is true).
> >=20
> > 3. Add an ability to specify Min Power Back-off, to allow an =
operator=20
> > to limit the signal transmit power to a lower level than that =
allowed=20
> > by the spectral limitations placed by the efmCuPme2BRegion and=20
> > efmCuPme2BsMode.
> >=20
> > I would appreciate your comments.
> >=20
> > Regards,
> > -E.=20