Re: draft-ietf-hubmib-efm-cu-mib-07 LC comments

Edward,
thanks for your note:
> 
> On the references to G.991.3, T1.424, and TS101 270-1 in EFM-CU-MIB,
> in efmCuPme10PBandplanPSDMskProfile, efmCuPme10PUPBOReferenceProfile
> and efmCuPme10PBandNotchProfiles:
> 
> 1st of all I do agree that the standards in question should be
> written the same way in all places (already fixed that in the new
> version of the draft).
> 
> What I'm contemplating now is whether to list these standards in
> the REFERENCE clauses of the relevant objects. I don't think it is
> necessary and here is my reasoning:
> 
> The tables listing these standards in the DESCRIPTION clauses are the
> exact copies of the relevant IEEE 802.3ah tables. From the EFM-CU-MIB
> point of view, the only important part of these tables is the profile
> number, which is an index of a relevant entry in a relevant table.
> In other words when describing profile(1) the only important thing to
> say about it is that it is the index of the 1st entry in the relevant
> 802.3ah table. The meaning of this entry (value of each columnar
> parameter) is described in the relevant 802.3ah section, already
> referenced in the REFERENCE clauses of the management objects. The
> 10Pass-TS PHY/equipment manufacturers would implement these tables,
> and a management station would use the efmCuPme10P*Profile objects
> to activate these entries as a single profile.

Well; that's an argument.

On the other hand, due to the columnar space restrictions enforcing
abbreviated references, it might anyway be a service for the reader
and the user of a management station to somewhere give the full
references.

If you dislike expanding the REFERENCE clauses of these objects,
an alternative might be to update the DESCRIPTION clause of the
efmCuMIB MODULE-IDENTITY, where [802.3ah] is expanded.
One possibility I envision would be to amend the IEEE 802.3ah
expansion there, without introducing new [...] style reference
tags, by a note like this:

      This document makes normative references to
      -  G.991.3,
      -  T1.424, and
      -  TS101 270-1,
      indirectly quoted as well by DESCRIPTION causes in this
      MIB module.  The full references for these standards are:

      ...
      ...
      ...

Kind regards,
  Alfred.