All,
The TR-165 "Vector of Profiles (VoP)" was recently published by the Broadband Forum (BBF). It defines an optimized object model for configuring DSL lines.
http://www.broadband-forum.org/technical/download/TR-165.pdf
It states in chapter 1.1:
...
The Vector of Profiles specified in this Technical Report obsoletes the object model for
DSL line configuration defined in the Broadband Forum’s TR-129. Legacy systems may
still use that object model for configuration management. All other object models of TR-
129 remain valid.
...
As TR-129 is is used as a reference in the draft-ietf-adslmib-vdsl2-06, the influence of TR-165 has to be considered by the group and a decision has to be made asap how to further proceed.
A stated in chapter 1.1 of TR-165, it obsoletes the object model for DSL line configuration in TR-129 and this influences directy the Configuration Template and Profile part of the MIB Draft.
I think of the following options for the working group to proceed:
1) Finish the work on the actual draft and define a new "VoP MIB" in the next step. Once, the "VoP MIB" is ready, the Configuration Template and Profile part in the existing MIB is marked as obsolete with reference to the new "VoP MIB".
2) Finish the work on the actual draft and define a new "VoP MIB" in the next step as an altenative MIB module for DSL line configuration and leave the choice, which MIB to use to the users.
3) Define the object structure based on TR-165 and put it into the existing MIB Draft before publication as a mandatory part and mark the Configuration Template and Profile part as optional.
4) Leave everything as it is.
I prefer option 1).
Any comments?
Best Regards
Markus Freudenberger
T-Systems Enterprise Services GmbH