Re: [Adslmib] Technical comments on draft-ietf-adslmib-vdsl-ext-mcm-02. txt

"Randy Presuhn" <randy_presuhn@mindspring.com> Mon, 29 March 2004 21:44 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28430 for <adslmib-archive@odin.ietf.org>; Mon, 29 Mar 2004 16:44:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B84Xj-0006q6-Qz for adslmib-archive@odin.ietf.org; Mon, 29 Mar 2004 16:43:39 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2TLhd6D026289 for adslmib-archive@odin.ietf.org; Mon, 29 Mar 2004 16:43:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B84Xj-0006pw-3q for adslmib-web-archive@optimus.ietf.org; Mon, 29 Mar 2004 16:43:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28403 for <adslmib-web-archive@ietf.org>; Mon, 29 Mar 2004 16:43:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B84Xh-000409-00 for adslmib-web-archive@ietf.org; Mon, 29 Mar 2004 16:43:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B84Wi-0003s2-00 for adslmib-web-archive@ietf.org; Mon, 29 Mar 2004 16:42:37 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B84Vk-0003kp-00 for adslmib-web-archive@ietf.org; Mon, 29 Mar 2004 16:41:36 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B84Ul-0006ju-24; Mon, 29 Mar 2004 16:40:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B84Tr-0006h4-Eo for adslmib@optimus.ietf.org; Mon, 29 Mar 2004 16:39:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28302 for <adslmib@ietf.org>; Mon, 29 Mar 2004 16:39:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B84Tp-0003WL-00 for adslmib@ietf.org; Mon, 29 Mar 2004 16:39:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B84Sv-0003PJ-00 for adslmib@ietf.org; Mon, 29 Mar 2004 16:38:41 -0500
Received: from mallard.mail.pas.earthlink.net ([207.217.120.48]) by ietf-mx with esmtp (Exim 4.12) id 1B84S6-0003Ir-00 for adslmib@ietf.org; Mon, 29 Mar 2004 16:37:50 -0500
Received: from h-68-164-76-126.snvacaid.dynamic.covad.net ([68.164.76.126] helo=oemcomputer) by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 1B84S6-0002Ew-00 for adslmib@ietf.org; Mon, 29 Mar 2004 13:37:50 -0800
Message-ID: <005b01c415d6$7a7e51e0$7f1afea9@oemcomputer>
From: Randy Presuhn <randy_presuhn@mindspring.com>
To: adslmib@ietf.org
References: <AD2F581BD7340A4C908AF1AFB066EA3B0CA3FE@ntah901e.savan.com>
Subject: Re: [Adslmib] Technical comments on draft-ietf-adslmib-vdsl-ext-mcm-02. txt
Date: Mon, 29 Mar 2004 13:40:38 -0800
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Sender: adslmib-admin@ietf.org
Errors-To: adslmib-admin@ietf.org
X-BeenThere: adslmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=unsubscribe>
List-Id: ADSLMIB <adslmib.ietf.org>
List-Post: <mailto:adslmib@ietf.org>
List-Help: <mailto:adslmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/adslmib>, <mailto:adslmib-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Hi -

> From: <Menachem.Dodge@infineon.com>
> To: <rray@pesa.com>
> Cc: <adslmib@ietf.org>
> Sent: Monday, March 29, 2004 6:24 AM
> Subject: FW: [Adslmib] Technical comments on draft-ietf-adslmib-vdsl-ext-mcm-02. txt
...

> vdslLineMCMConfProfileTable: "The entries in this table MUST NOT be used
> for single carrier (SCM) VDSL lines."  What enforces this constraint?
>
> >>>>>
>
> Menachem: I will remove this sentence.

This doesn't address the underlyng issue.  What happens when the profile
for an SCM line uses a name that has MCM entries?  My proposal, as someone
who knows nothing about this technology, would be to use words something like this:
"If an entry in this table is referenced by a line which is does not use MCM,
it has no effect on the operation of that line."

...
> vdslLineMCMConfProfileEntry: "A default profile with an
> index of 'DEFVAL', will always exist" begs the question:
> when there is a vdslLineConfProfileEntry with an index of "DEFVAL", will
> it apply to *both* the MCM and the SCM "DEFVAL" entries?
>
>
> >>>>>>
>
> Menachem: I will remove this sentence. As these are optional a
> default value is not necessary.

Disagree.  The "DEFVAL" row is not a default value; it is a default
profile, which is required to exist in implementations of this MIB module.
The underlying question is whether it is possible / meaningful to
have default profiles for both SCM and MCM lines, and if it is,
whether there would be any problem from them both having the
index of "DEFVAL", since there would be attributes required to
have the same values for both as a consequence of any "shared"
profile configuration tables.

...
> Additional Editorial comments:
> RFC 3667 section 5.1 requires an "IPR Disclosure Acknowledgement"
>
> >>>>>>
>
> Menachem: I'll add this section before the Full Copyright
...

I'm checking with Scott Bradner to find out whether this is the right place
for it, since it will be removed at RFC time.

Randy



_______________________________________________
Adslmib mailing list
Adslmib@ietf.org
https://www1.ietf.org/mailman/listinfo/adslmib