FW: DISCUSS and COMMENT: draft-ietf-adslmib-vdsl2
"Romascanu, Dan (Dan)" <[email protected]> Thu, 2 Jul 2009 14:51:11 +0200
| Newsgroups | gmane.ietf.adslmib |
|---|---|
| Message-ID | <EDC652A26FB23C4EB6384A4584434A0401846DD2@307622ANEX5.global.avaya.com> |
Moti, Menachem, Please address the issues raised by AD Adrian Farrel in his DISCUSS and COMMENT. Thanks and Regards, Dan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Adrian Farrel Sent: Thursday, July 02, 2009 3:28 PM To: [email protected] Cc: [email protected]; [email protected]; [email protected]; [email protected]; [email protected] Subject: DISCUSS and COMMENT: draft-ietf-adslmib-vdsl2 Discuss: I would like to hear from the Ops ADs whether they think that TCs like Xdsl2TransmissionModeType should be moved to an IANA MIB module to allow the definition of new values without requiring to respin this MIB module as a new RFC. It is odd (and possibly non-conformant) to place the IANA Considerations section at 2.2. Comment: I don't understand the default value provided in the following object. Please check that it is appropriate majick. xdsl2LineAlarmConfTemplate OBJECT-TYPE SYNTAX SnmpAdminString (SIZE(1..32)) MAX-ACCESS read-write STATUS current DESCRIPTION "The value of this object identifies the row in the xDSL2 Line Alarm Configuration Template Table, xdsl2LineAlarmConfTemplateTable, which applies to this line. This object MUST be maintained in a persistent manner." REFERENCE "DSL Forum TR-129, paragraph #5.1" DEFVAL { "DEFVAL" } ::= { xdsl2LineEntry 3 }