[Adslmib] FW: DISCUSS and COMMENT: draft-ietf-adslmib-vdsl2

["Romascanu, Dan (Dan)" <dromasca at 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: iesg-bounces at ietf.org [mailto:iesg-bounces at ietf.org] On Behalf Of
Adrian Farrel
Sent: Thursday, July 02, 2009 3:28 PM
To: iesg at ietf.org
Cc: adslmib-chairs at tools.ietf.org; fayely at juniper.net;
rray at core3.amsl.com; Greg_Bathrick at pmc-sierra.com; rray at pesa.com
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 }