RE: MIBs for ITU-T G.Bond and T1E1 M2DSL projects

Alternative One would be an approach similar to what has
been done with VDSL.  That is, breaking the line code
specific functionality out into separate documents.

My suggestion was merely tossing out the notion of
introducing a stratifying structure where a draft would
allow the reuse of existing efforts (i.e. dsl, ethernet,
t1/e1, etc.) by specifying that a given "line" is actually 
composed of subordinate lines of a given ifType.

For example, say the iana defines a new ifType bonded(xxx)
(http://www.iana.org/assignments/ianaiftype-mib), and you
define a MIB to manage a bonded line.  

Using an ifStack approach (see interfaces MIB) and RFC2127
(http://www.ietf.org/rfc/rfc2127.txt), it would appear that 
a bonded line could be defined in a single document without 
having multiple documents defined for the well-known (?) 
lower layers.

For example, a fractional T1 (or E1) line can be considered a 
collection of bonded DS0s, no?  Representing this fractional
T1 line via the ifStack table should be straightforward (and
is done to some degree in RFC2127).

Please note that the above is borne aloft solely on the soiled
wings of my ignorance and curiosity.

Regards,
Bob Ray