Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2)
RFC 4706

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

(Jari Arkko) No Objection

Comment (2006-05-11 for -)
No email
send info
> The ADSL2-LINE-MIB module requires the allocation of a new ifType
> value for Asymmetric Digital Subscriber Loop Version 2, to
> distinguish between ADSL lines that are managed with the RFC2662
> management model and ADSL/ADSL2 and ADSL2+ lines managed with the
> model defined in this document.

But Section 2.1.1 already defines the value 230 to be used.
Also, IANA registry at http://www.iana.org/assignments/ianaiftype-mib
already registers the same value, 230 to "Asymmetric Digital Subscriber
Loop Version 2".

From what I can see, this part of the IANA action is no longer
needed. Or did I miss something? If not, maybe Dan can add
an RFC Editor note to change this text to

"The ADSL2-LINE-MIB module uses the ifType
value for Asymmetric Digital Subscriber Loop Version 2, to
distinguish between ADSL lines that are managed with the RFC2662
management model and ADSL/ADSL2 and ADSL2+ lines managed with the
model defined in this document. The value 230 has already been
allocated by IANA for this purpose."

(But I'm sure IANA would have understood anyway.)

(Ross Callon) No Objection

(Brian Carpenter) No Objection

(Lisa Dusseault) No Objection

(Lars Eggert) No Objection

(Bill Fenner) No Objection

(Ted Hardie) No Objection

(Sam Hartman) No Objection

(Russ Housley) No Objection

(Cullen Jennings) No Objection

(David Kessens) No Objection

(Jon Peterson) No Objection

(Dan Romascanu) (was Discuss, Yes) No Objection

Comment (2006-05-09)
No email
send info
1. Version 07 introduced a couple of nits that lead to the two modules not to compile correctly. These can be fixed by the following changes that I propose dot be included in the editorial notes: 

OLD: 

   adsl2TCMIB MODULE-IDENTITY
      LAST-UPDATED "200604250000Z" - April 25, 2006

NEW: 

   adsl2TCMIB MODULE-IDENTITY
      LAST-UPDATED "200604250000Z" -- April 25, 2006

OLD: 

   adsl2MIB MODULE-IDENTITY
      LAST-UPDATED "200604250000Z" - April 25, 2006

NEW: 

   adsl2MIB MODULE-IDENTITY
      LAST-UPDATED "200604250000Z" -- April 25, 2006

2. The Overview section points wrongly to a section of the document that does nor exist. In order to fix this the following change is suggested. 

OLD: 

   The MIB module is located in the MIB tree under MIB 2 transmission,
   as discussed in the MIB-2 Integration (RFC 2863 [RFC2863]) section of
   this document.

NEW:

   The MIB module is located in the MIB tree under MIB 2 transmission,
   as discussed in the IANA Considerations section of this document.

3. Inconsistent use of kew-words:

In Section 2.9

OLD: 

   The ability to generate the SNMP notifications coldStart/WarmStart
   (per [RFC3418]), which are per agent (e.g., per Digital Subscriber
   Line Access Multiplexer, or DSLAM, in such a device), and linkUp/
   linkDown (per [RFC2863]), which are per interface (i.e., ADSL/ADSL2
   or ADSL2+ line) is required.

NEW: 

   The ability to generate the SNMP notifications coldStart/WarmStart
   (per [RFC3418]), which are per agent (e.g., per Digital Subscriber
   Line Access Multiplexer, or DSLAM, in such a device), and linkUp/
   linkDown (per [RFC2863]), which are per interface (i.e., ADSL/ADSL2
   or ADSL2+ line) is REQUIRED.

4. I believe that it is improper for a MIB document to impose requirements on management implementations using this MIB, other than conformance to the MIB definition. I suggest that the following text in Section 4 is changed through a RFC Editor note. 

OLD: 

   A management application intended to manage ADSL links (e.g.,
   G.992.1) with this MIB module MUST be modified to adapt itself to
   certain differences between RFC 2662 [RFC2662] and this MIB module,
   including the following aspects

NEW:

   A management application intended to manage ADSL links (e.g.,
   G.992.1) with this MIB module must be modified to adapt itself to
   certain differences between RFC 2662 [RFC2662] and this MIB module,
   including the following aspects

(Mark Townsley) No Objection

(Magnus Westerlund) No Objection