Re: DISCUSS and COMMENT: draft-ietf-adslmib-vdsl2

> Xdsl2TransmissionModeType
> =====================
> We believe that any changes to the modes listed in
> Xdsl2TransmissionModeType will probably be involved with changes to
> other components of the DSL management model, i.e., will anyhow require
> a revised RFC. This is perfectly demonstrated by the changes performed
> in the model along with adding the VDSL2 related modes to the
> Adsl2TransmissionModeType defined RFC 4706.

OK

> IANA Considerations
> =================
> The "IANA Considerations" paragraph is located in the same place as in
> RFC 4319 and RFC 4706.
> I'm unaware of any guidelines regarding the exact position of this
> section within the document.   

It's not important, just unusual.

> xdsl2LineAlarmConfTemplate
> =======================
> The name of the default template in our model is actually "DEFVAL" and
> every DSL line is, by default, associated with that template. It means
> that in the MIB table xdsl2LineConfTemplateTable, we require that there
> will always be a row with the name (i.e., xdsl2LConfTempTemplateName
> value) set to "DEFVAL". 
> Furthermore, we actually state in the DESCRIPTION clause of
> xdsl2LineConfTemplateEntry that "A default template with an index of
> 'DEFVAL' will always exist".
> We use the same default profile name for other profile tables as well.
> Those are of course separate profile tables but yet each of them has a
> row with the name "DEFVAL".

Ah, OK.

> Is there any reason to avoid using that specific name?

No, none at all.

I cleared.

Cheers,
Adrian