ADSLMIB WG, IETF-68 Date: 20-Mar-2007 Participants: Antti Jussi Korjonan, Bert Wijnen, Dan Romascanu (AD), Johannes Reichhart, Menachem Dodge (WG Chair), Moti Morgenstern, Naren Nair, Umberto Bonollo (via Jabber). Minutes Editor: Naren Jabber Editor : Bert Minutes of the Meeting ---------------------- Menachem summarized the work done in 2006 and plans for 2007. Dan wanted to know if there were any implementations of the previous xDSL MIB implementations. Moti said that it is important to continue the standardization of the MIBs even though the implementations might not be exactly the same as what is recommended by the document. The industry looks at what the IETF does and it is important that there is a document that is beyond the general protocol independent model. Umberto indicated that his company, NEC, had implemented an earlier version of the SHDSL MIB for four-wire. VDSL2 MIB: (Moti) ----------------- Moti elaborated on the various ways that you can use the MIB. Several service providers said that they prefer ADSL2 and/or VDSL2 VDSL2 MIB is different: (e.g. One can supply modems/equipment with only part of the functionality supported as per ITU-T standard reference is same (ITU-T G.997.1) Difficulties in progressing on the IETF documents due to the fact that the related ITU-T documents were still changing. An attempt will be made to find out whether the ITU-T G.997.1 document is nearing completion so that the MIB will be as closely as possible aligned with the ITU-T document. Menachem will send a liaison before the last call to ITU-T so that the documents from IETF is as aligned as possible. At the DSL Forum a suggestion to add many more parameters, other than those requested by the ITU-T has since been removed. The idea of having 'running counters' was discussed/debated. Moti indicated that the "running counters" provide no additional information than the interval based counters. This item will be brought up on the mailing list. Naren mentioned his previous request for a Re-structure of the xdsl2ProfileLine table. Naren will resend his mail to the working group to check for agreement/disagreements. XDSL Bonding (Naren, Moti) -------------------------- Naren and Moti summarized the common xDSL bonding mib, the TDIM specific MIB design and ATM specific MIB design. Open Point 1: GBOND specific objects, where do we place them under? >> Bert expressed concern in putting them under the gBondMIB module; The common gBondMib will not have a module compliance of its own. gBondConformance will have object groups. >> gBondATM, Eth and TDIM should be under mib-2; Action Point: The editors should send an email to Dan, outlining the structure and associations between the tables. Dan will bring this to the MIB doctors. The editors should also check with RFC4181 mib review and design guidelines. Action Point: EFM-CU-MIB see if a different grouping is done conveniently for Bonding MIBs: (owner: Naren) Also to be checked: if the GBOND-TDIM-MIB has dependency on any mibs other than xDSL and Ethernet) Open Point 2: 15 min 24hr counters be modeled? Moti commented that this should be modeled according to G.998.x, and also discussed on the mailing list. The need for an informational document describing the relationship between the work done by the Adslmib and Hubmib was discussed. This issue was raised by Orly Nicklass on the email list. Editors feel that there is no need for a separate document to explain the relationship; ideally the common document should be the place for such explanations. This issue was raised again offline, after the meeting when Orly was present. It was agreed that regarding the G.Bond MIBs, at least, there is no issue, as they do not duplicate any information from other MIBs. The problem arises between the EFM-CU-MIB and the xDSL MIBs where there is duplication of objects although different naming is used. Work Plan for 2007 ------------------ Dan proposed a second working group last call in september for VDSL2 MIB The Work plan will be brought to the mailing list and then to the AD.