Skip to main content

Definitions of Managed Objects for Very High Speed Digital Subscriber Line 2 (VDSL2)
draft-ietf-adslmib-vdsl2-07

Yes

(Dan Romascanu)

No Objection

(Cullen Jennings)
(Lisa Dusseault)
(Magnus Westerlund)
(Ralph Droms)
(Robert Sparks)
(Ron Bonica)
(Ross Callon)

Note: This ballot was opened for revision 07 and is now closed.

Dan Romascanu Former IESG member
Yes
Yes () Unknown

                            
Adrian Farrel Former IESG member
(was Discuss) No Objection
No Objection (2009-07-02) Unknown
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 }
Cullen Jennings Former IESG member
No Objection
No Objection () Unknown

                            
Lisa Dusseault Former IESG member
No Objection
No Objection () Unknown

                            
Magnus Westerlund Former IESG member
No Objection
No Objection () Unknown

                            
Ralph Droms Former IESG member
No Objection
No Objection () Unknown

                            
Robert Sparks Former IESG member
No Objection
No Objection () Unknown

                            
Ron Bonica Former IESG member
No Objection
No Objection () Unknown

                            
Ross Callon Former IESG member
No Objection
No Objection () Unknown

                            
Tim Polk Former IESG member
(was No Record, Discuss) No Objection
No Objection (2009-07-02) Unknown
This document does a nice job of implementing the security considerations template for MIBs.  Richard Barnes secdir review suggested an additional issue for consideration - are there security
issues that are derived from the readable and writable objects in combination?  Given the
the number of security relevant objects in the MIB, that seems plausible.

The authors might want to take a few minutes and conider whether such problems exist.