From exim@www1.ietf.org  Mon Nov  3 04:29:28 2003
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA24967
	for <adslmib-archive@odin.ietf.org>; Mon, 3 Nov 2003 04:29:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGb1I-0000hu-9O
	for adslmib-archive@odin.ietf.org; Mon, 03 Nov 2003 04:29:08 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA39T85A002714
	for adslmib-archive@odin.ietf.org; Mon, 3 Nov 2003 04:29:08 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGb1I-0000hh-3z
	for adslmib-web-archive@optimus.ietf.org; Mon, 03 Nov 2003 04:29:08 -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 EAA24884
	for <adslmib-web-archive@ietf.org>; Mon, 3 Nov 2003 04:28:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGb1F-0002Yd-00
	for adslmib-web-archive@ietf.org; Mon, 03 Nov 2003 04:29:05 -0500
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGb1E-0002YX-00
	for adslmib-web-archive@ietf.org; Mon, 03 Nov 2003 04:29:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGb1G-0000gw-4D; Mon, 03 Nov 2003 04:29:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AGb0n-0000a3-KL
	for adslmib@optimus.ietf.org; Mon, 03 Nov 2003 04:28:37 -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 EAA24835
	for <adslmib@ietf.org>; Mon, 3 Nov 2003 04:28:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGb0k-0002XH-00
	for adslmib@ietf.org; Mon, 03 Nov 2003 04:28:34 -0500
Received: from smtp5.clb.oleane.net ([213.56.31.25])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AGb0j-0002Wo-00
	for adslmib@ietf.org; Mon, 03 Nov 2003 04:28:34 -0500
Received: from oleane ([194.250.212.114]) 
	by smtp5.clb.oleane.net with SMTP id hA39S3pR016713
	for <adslmib@ietf.org>; Mon, 3 Nov 2003 10:28:03 +0100
Message-ID: <017001c3a1ed$45b33780$0601a8c0@www.oleane.com>
From: "Peter Lewis" <peter.lewis@upperside.fr>
To: <adslmib@ietf.org>
Date: Mon, 3 Nov 2003 10:31:33 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_016D_01C3A1F5.A7022160"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Subject: [Adslmib] UWB Summit
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>

C'est un message de format MIME en plusieurs parties.

------=_NextPart_000_016D_01C3A1F5.A7022160
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Which proposal will be selected as the IEEE 802.15.3a standard? A =
consortium has just proposed to offer a RANDZ access to its patents. The =
industry is now waiting for the reply from the supporters of the other =
proposal.=20
This battle between technology heavyweights underlines the growing =
importance of a technology expected to generate $1.39 billion in revenue =
by 2007.
All questions and answers will be delivered during the UWB Summit to be =
held in Paris next 2-5 December.
All details at:
http://www.upperside.fr/newmobtech/uwb03cfp.htm

------=_NextPart_000_016D_01C3A1F5.A7022160
Content-Type: text/html;
	charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#111111 size=3D2>Which proposal will be selected as =
the=20
<STRONG>IEEE 802.15.3a standard</STRONG>? A consortium has just proposed =
to=20
offer a RANDZ access to its patents. The industry is now waiting for the =
reply=20
from the supporters of the other proposal. </FONT></DIV>
<DIV><FONT color=3D#111111 size=3D2>This battle between technology =
heavyweights=20
underlines the growing importance of a technology expected to generate =
$1.39=20
billion in revenue by 2007.</FONT></DIV>
<DIV><FONT color=3D#111111 size=3D2>All questions and answers will be =
delivered=20
during the <STRONG>UWB Summit </STRONG>to be held in Paris next 2-5=20
December.</FONT></DIV>
<DIV><FONT color=3D#111111 size=3D2>All details at:</FONT></DIV>
<DIV><FONT color=3D#111111 size=3D2><A=20
href=3D"http://www.upperside.fr/newmobtech/uwb03cfp.htm">http://www.upper=
side.fr/newmobtech/uwb03cfp.htm</A></FONT></DIV></BODY></HTML>

------=_NextPart_000_016D_01C3A1F5.A7022160--


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



From exim@www1.ietf.org  Fri Nov  7 09:22:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15597
	for <adslmib-archive@odin.ietf.org>; Fri, 7 Nov 2003 09:22:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI7Uw-0008DE-PQ
	for adslmib-archive@odin.ietf.org; Fri, 07 Nov 2003 09:22:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hA7EM203031564
	for adslmib-archive@odin.ietf.org; Fri, 7 Nov 2003 09:22:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI7Uw-0008D1-MG
	for adslmib-web-archive@optimus.ietf.org; Fri, 07 Nov 2003 09:22:02 -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 JAA15590
	for <adslmib-web-archive@ietf.org>; Fri, 7 Nov 2003 09:21:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI7Uu-0005hd-00
	for adslmib-web-archive@ietf.org; Fri, 07 Nov 2003 09:22:01 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI7Uu-0005hY-00
	for adslmib-web-archive@ietf.org; Fri, 07 Nov 2003 09:22:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI7Uu-0008Ce-SP; Fri, 07 Nov 2003 09:22:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AI7Um-0008CJ-2g
	for adslmib@optimus.ietf.org; Fri, 07 Nov 2003 09:21:52 -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 JAA15576
	for <adslmib@ietf.org>; Fri, 7 Nov 2003 09:21:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI7Uk-0005hF-00
	for adslmib@ietf.org; Fri, 07 Nov 2003 09:21:50 -0500
Received: from smtp2.clb.oleane.net ([213.56.31.18])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AI7Uj-0005ge-00
	for adslmib@ietf.org; Fri, 07 Nov 2003 09:21:49 -0500
Received: from oleane (upper-side.rain.fr [194.250.212.114]) 
	by smtp2.clb.oleane.net with SMTP id hA7ELFfo025248
	for <adslmib@ietf.org>; Fri, 7 Nov 2003 15:21:15 +0100
Message-ID: <003501c3a53a$ecbe8160$0601a8c0@www.oleane.com>
From: "M Winkhler" <m.winkhler@fr.oleane.com>
To: <adslmib@ietf.org>
Date: Fri, 7 Nov 2003 15:24:58 +0100
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0032_01C3A543.4E3824C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Subject: [Adslmib] WiMAX Summit
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>

C'est un message de format MIME en plusieurs parties.

------=_NextPart_000_0032_01C3A543.4E3824C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Are WiMAX and WiFi complementary (local vs. metropolitan area =
networking)?=20
When and how will WiMAX evolve towards mobility?=20
Can WiMAX be considered as a migration path to 4G?=20
How is addressed the interoperability challenge?=20

These questions, among others, will be addressed during the WiMAX =
Summit, to be held in Paris on May 25 to 28, 2004.=20

A call for papers has been launched on-line at:
http://www.upperside.fr/wimax04/wimax04intro.htm


------=_NextPart_000_0032_01C3A543.4E3824C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV>
<DIV><FONT size=3D2>Are WiMAX and WiFi complementary (local vs. =
metropolitan=20
area&nbsp;networking)? <BR>When and how will WiMAX evolve towards =
mobility?=20
<BR>Can WiMAX be considered as a migration path to 4G? <BR>How is =
addressed the=20
interoperability challenge? <BR><BR>These questions, among others, will =
be=20
addressed during the <FONT class=3Dtextebold color=3D#2d795f>WiMAX =
Summit</FONT>, to=20
be held in <SPAN class=3Dunderline>Paris on May 25 to 28, </SPAN>2004. =
<BR><BR>A=20
call for papers has been launched on-line at:</FONT></DIV>
<DIV><FONT size=3D2><A=20
href=3D"http://www.upperside.fr/wimax04/wimax04intro.htm">http://www.uppe=
rside.fr/wimax04/wimax04intro.htm</A></FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV></DIV></BODY></HTML>

------=_NextPart_000_0032_01C3A543.4E3824C0--


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



From exim@www1.ietf.org  Mon Nov 17 12:08:24 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21970
	for <adslmib-archive@odin.ietf.org>; Mon, 17 Nov 2003 12:08:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmr8-0001mu-As
	for adslmib-archive@odin.ietf.org; Mon, 17 Nov 2003 12:08:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAHH86PU006863
	for adslmib-archive@odin.ietf.org; Mon, 17 Nov 2003 12:08:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmr7-0001mU-N2
	for adslmib-web-archive@optimus.ietf.org; Mon, 17 Nov 2003 12:08:05 -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 MAA21785
	for <adslmib-web-archive@ietf.org>; Mon, 17 Nov 2003 12:07:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmr5-00020I-00
	for adslmib-web-archive@ietf.org; Mon, 17 Nov 2003 12:08:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmr5-00020E-00
	for adslmib-web-archive@ietf.org; Mon, 17 Nov 2003 12:08:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmr3-0001lB-OX; Mon, 17 Nov 2003 12:08:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1ALmqJ-0001Y2-Rq
	for adslmib@optimus.ietf.org; Mon, 17 Nov 2003 12:07:15 -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 MAA21705
	for <adslmib@ietf.org>; Mon, 17 Nov 2003 12:07:02 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmqI-0001xx-00
	for adslmib@ietf.org; Mon, 17 Nov 2003 12:07:14 -0500
Received: from bay10-f38.bay10.hotmail.com ([64.4.37.38] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1ALmqH-0001wU-00
	for adslmib@ietf.org; Mon, 17 Nov 2003 12:07:14 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Mon, 17 Nov 2003 09:06:41 -0800
Received: from 66.152.60.98 by by10fd.bay10.hotmail.msn.com with HTTP;
	Mon, 17 Nov 2003 17:06:41 GMT
X-Originating-IP: [66.152.60.98]
X-Originating-Email: [sneedmike@hotmail.com]
From: "Michael Sneed" <sneedmike@hotmail.com>
To: adslmib@ietf.org
Date: Mon, 17 Nov 2003 12:06:41 -0500
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com>
X-OriginalArrivalTime: 17 Nov 2003 17:06:41.0695 (UTC) FILETIME=[2BD3F2F0:01C3AD2D]
Subject: [Adslmib] Issue with HCTC Perf Interval MIB (and therefore with the VDSL MIB)
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>

During the IETF Last Call process there were some concerns expressed in the 
IESG about the HCTC Performance Interval MIB 
(draft-ietf-adslmib-hc-tc-06.txt) that we have recommended to go to Proposed 
Standard.  In a nutshell, the problem is one of alignment of the various 
MIBs that deal with this topic (namely RFC3593 and 2856).

As a result of this discussion, it has been recommended that we change

    - HCPerfTimeElapsed, Gauge32 (0...86399)
    - HCPerfValidIntervals, Gauge32 (0...96)
    - HCPerfInvalidIntervals, Gauge32 (0...96)

to type Integer32.


Does anyone wish to comment on this change before the editors put in in a 
new draft?

_________________________________________________________________
Is your computer infected with a virus?  Find out with a FREE computer virus 
scan from McAfee.  Take the FreeScan now! 
http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963


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



From exim@www1.ietf.org  Wed Nov 19 10:16:36 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21214
	for <adslmib-archive@odin.ietf.org>; Wed, 19 Nov 2003 10:16:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMU43-0000dd-GE
	for adslmib-archive@odin.ietf.org; Wed, 19 Nov 2003 10:16:20 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAJFGJ4G002449
	for adslmib-archive@odin.ietf.org; Wed, 19 Nov 2003 10:16:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMU43-0000dQ-D9
	for adslmib-web-archive@optimus.ietf.org; Wed, 19 Nov 2003 10:16:19 -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 KAA21151
	for <adslmib-web-archive@ietf.org>; Wed, 19 Nov 2003 10:15:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMU3w-0000u7-00
	for adslmib-web-archive@ietf.org; Wed, 19 Nov 2003 10:16:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMU3v-0000tm-00
	for adslmib-web-archive@ietf.org; Wed, 19 Nov 2003 10:16:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMU3l-0000bs-5P; Wed, 19 Nov 2003 10:16:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMU2s-0000Yx-A7
	for adslmib@optimus.ietf.org; Wed, 19 Nov 2003 10:15:06 -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 KAA21000
	for <adslmib@ietf.org>; Wed, 19 Nov 2003 10:14:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMU2q-0000sh-00
	for adslmib@ietf.org; Wed, 19 Nov 2003 10:15:04 -0500
Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMU2p-0000se-00
	for adslmib@ietf.org; Wed, 19 Nov 2003 10:15:03 -0500
Received: from pesa.com ([216.180.38.253])
	by mail.hiwaay.net (8.12.10/8.12.10) with ESMTP id hAJFF3tx963175
	for <adslmib@ietf.org>; Wed, 19 Nov 2003 09:15:03 -0600 (CST)
Received: from 192.168.0.122 ([192.168.0.122])
	by pesa.com (pesa.com [127.0.0.1])
	(MDaemon.PRO.v6.8.5.R)
	with ESMTP id 26-md50000000130.tmp
	for <adslmib@ietf.org>; Wed, 19 Nov 2003 09:14:59 -0600
Subject: Re: [Adslmib] Issue with HCTC Perf Interval MIB (and therefore
	with the VDSL MIB)
From: Bob Ray <rray@pesa.com>
Reply-To: rray@pesa.com
To: Mike Sneed <sneedmike@hotmail.com>
Cc: adslmib mail list <adslmib@ietf.org>
In-Reply-To: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com>
References: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com>
Content-Type: text/plain
Message-Id: <1069254898.27942.2.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) 
Date: 19 Nov 2003 09:14:58 -0600
Content-Transfer-Encoding: 7bit
X-Spam-Processed: pesa.com, Wed, 19 Nov 2003 09:14:59 -0600
	(not processed: message from valid local sender)
X-MDRemoteIP: 192.168.0.122
X-Return-Path: rray@pesa.com
X-MDaemon-Deliver-To: adslmib@ietf.org
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Mon, 2003-11-17 at 11:06, Michael Sneed wrote:
> During the IETF Last Call process there were some concerns expressed in the 
> IESG about the HCTC Performance Interval MIB 
> (draft-ietf-adslmib-hc-tc-06.txt) that we have recommended to go to Proposed 
> Standard.  In a nutshell, the problem is one of alignment of the various 
> MIBs that deal with this topic (namely RFC3593 and 2856).
> 
> As a result of this discussion, it has been recommended that we change
> 
>     - HCPerfTimeElapsed, Gauge32 (0...86399)
>     - HCPerfValidIntervals, Gauge32 (0...96)
>     - HCPerfInvalidIntervals, Gauge32 (0...96)
> 
> to type Integer32.
> 
> 
> Does anyone wish to comment on this change before the editors put in in a 
> new draft?

Anyone have an objection?  A chorus of 'No's would be appreciated.  Or at
least one. :) 

Bob


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



From exim@www1.ietf.org  Thu Nov 20 14:28:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19726
	for <adslmib-archive@odin.ietf.org>; Thu, 20 Nov 2003 14:28:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMuTD-0002s3-H3
	for adslmib-archive@odin.ietf.org; Thu, 20 Nov 2003 14:28:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKJS3lZ011031
	for adslmib-archive@odin.ietf.org; Thu, 20 Nov 2003 14:28:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMuTD-0002rq-EC
	for adslmib-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 14:28:03 -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 OAA19707
	for <adslmib-web-archive@ietf.org>; Thu, 20 Nov 2003 14:27:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMuTA-0000m9-00
	for adslmib-web-archive@ietf.org; Thu, 20 Nov 2003 14:28:00 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMuTA-0000m2-00
	for adslmib-web-archive@ietf.org; Thu, 20 Nov 2003 14:28:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMuTB-0002ra-FO; Thu, 20 Nov 2003 14:28:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMuSu-0002rK-Qs
	for adslmib@optimus.ietf.org; Thu, 20 Nov 2003 14:27:44 -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 OAA19697
	for <adslmib@ietf.org>; Thu, 20 Nov 2003 14:27:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMuSs-0000ll-00
	for adslmib@ietf.org; Thu, 20 Nov 2003 14:27:42 -0500
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMuSr-0000li-00
	for adslmib@ietf.org; Thu, 20 Nov 2003 14:27:41 -0500
Received: from h-68-164-78-60.snvacaid.dynamic.covad.net ([68.164.78.60] helo=oemcomputer)
	by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1AMuSr-00014s-00
	for adslmib@ietf.org; Thu, 20 Nov 2003 11:27:41 -0800
Message-ID: <012901c3af9c$9c448100$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "adslmib mail list" <adslmib@ietf.org>
References: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com> <1069254898.27942.2.camel@localhost.localdomain>
Subject: Re: [Adslmib] Issue with HCTC Perf Interval MIB (and thereforewith the VDSL MIB)
Date: Thu, 20 Nov 2003 11:29:26 -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>

Hi -

> From: "Bob Ray" <rray@pesa.com>
> To: "Mike Sneed" <sneedmike@hotmail.com>
> Cc: "adslmib mail list" <adslmib@ietf.org>
> Sent: Wednesday, November 19, 2003 7:14 AM
> Subject: Re: [Adslmib] Issue with HCTC Perf Interval MIB (and thereforewith the VDSL MIB)
>

> On Mon, 2003-11-17 at 11:06, Michael Sneed wrote:
> > During the IETF Last Call process there were some concerns expressed in the
> > IESG about the HCTC Performance Interval MIB
> > (draft-ietf-adslmib-hc-tc-06.txt) that we have recommended to go to Proposed
> > Standard.  In a nutshell, the problem is one of alignment of the various
> > MIBs that deal with this topic (namely RFC3593 and 2856).
> >
> > As a result of this discussion, it has been recommended that we change
> >
> >     - HCPerfTimeElapsed, Gauge32 (0...86399)
> >     - HCPerfValidIntervals, Gauge32 (0...96)
> >     - HCPerfInvalidIntervals, Gauge32 (0...96)
> >
> > to type Integer32.
> >
> >
> > Does anyone wish to comment on this change before the editors put in in a
> > new draft?
>
> Anyone have an objection?  A chorus of 'No's would be appreciated.  Or at
> least one. :)
...

In the spirit of collaboration, I'll say that I dislike like the proposed change, and
support it *solely* for reasons of compatibility.  The MIB review guidelines make
it pretty clear that Gauge32 would be the preferred data type, given the
semantics.

Randy



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



From exim@www1.ietf.org  Thu Nov 20 15:26:34 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23699
	for <adslmib-archive@odin.ietf.org>; Thu, 20 Nov 2003 15:26:34 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMvNX-0007ZW-VH
	for adslmib-archive@odin.ietf.org; Thu, 20 Nov 2003 15:26:16 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAKKQFIn029107
	for adslmib-archive@odin.ietf.org; Thu, 20 Nov 2003 15:26:15 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMvNW-0007ZN-W9
	for adslmib-web-archive@optimus.ietf.org; Thu, 20 Nov 2003 15:26:15 -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 PAA23631
	for <adslmib-web-archive@ietf.org>; Thu, 20 Nov 2003 15:26:01 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMvNU-0001lX-00
	for adslmib-web-archive@ietf.org; Thu, 20 Nov 2003 15:26:12 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMvNT-0001lS-00
	for adslmib-web-archive@ietf.org; Thu, 20 Nov 2003 15:26:11 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMvNP-0007Y6-Cx; Thu, 20 Nov 2003 15:26:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AMvMP-0007VJ-LB
	for adslmib@optimus.ietf.org; Thu, 20 Nov 2003 15:25:05 -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 PAA23537
	for <adslmib@ietf.org>; Thu, 20 Nov 2003 15:24:52 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMvMO-0001jT-00
	for adslmib@ietf.org; Thu, 20 Nov 2003 15:25:04 -0500
Received: from bay10-f50.bay10.hotmail.com ([64.4.37.50] helo=hotmail.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AMvMN-0001if-00
	for adslmib@ietf.org; Thu, 20 Nov 2003 15:25:03 -0500
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 20 Nov 2003 12:24:32 -0800
Received: from 66.152.60.98 by by10fd.bay10.hotmail.msn.com with HTTP;
	Thu, 20 Nov 2003 20:24:31 GMT
X-Originating-IP: [66.152.60.98]
X-Originating-Email: [sneedmike@hotmail.com]
From: "Michael Sneed" <sneedmike@hotmail.com>
To: adslmib@ietf.org
Date: Thu, 20 Nov 2003 15:24:31 -0500
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_7c09_6737_28e2"
Message-ID: <BAY10-F50O0zND3oV4A00011751@hotmail.com>
X-OriginalArrivalTime: 20 Nov 2003 20:24:32.0317 (UTC) FILETIME=[4E825ED0:01C3AFA4]
Subject: [Adslmib] Liason from the DSL Forum
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>

This is a multi-part message in MIME format.

------=_NextPart_000_7c09_6737_28e2
Content-Type: text/plain; format=flowed
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA23540
Content-Transfer-Encoding: quoted-printable

Following are the contents of the most recent liason from the DSL Forum t=
o=20
adslmib, consisting of a transmission letter and a copy of a Working Text=
. =20
This liason relates to our work on LCS MIBs.

I have converted the documents to text from the original MS Word document=
s. =20
If anyone needs to see the originals let me know and I will forward them =
to=20
you.

Regards,

Mike

_________________________________________________________________
From the hottest toys to tips on keeping fit this winter, you=92ll find a=
=20
range of helpful holiday info here. =20
http://special.msn.com/network/happyholidays.armx

------=_NextPart_000_7c09_6737_28e2
Content-Type: text/plain; name="liaisontoIETF.txt"; format=flowed
Content-Disposition: attachment; filename="liaisontoIETF.txt"
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA23540
Content-Transfer-Encoding: quoted-printable









DSL Forum Liaison to:
Mike Sneed, IETF ADSLMIB Chair

From:
Gavin Young, DSL Forum Technical Committee Chair
gyoung@dslforum.org

Date: November 13, 2003

Subject: DSL Forum Liaison to the IETF

Dear Mr. Sneed,

We wish to inform the IETF that the DSL Forum has a new working text,=20
WT-096, entitled =93SCM-Specific Managed Objects in VDSL Network Elements=
=94=20
which is attached.  This document is going for straw ballot at our next=20
meeting in March 2-4, 2004.

After our last meeting we informed you that we had started work on the=20
element management of next generation ADSL.  The intent of the work being=
 to=20
create a protocol-independent object model suited to the management of th=
e=20
enhanced features of ADSL2, ADSL2plus and ADSL2lite.  Good progress has b=
een=20
made and we wish to inform you that we anticipate the working text going =
to=20
straw ballot at our meeting in May 18-20, 2004.  When the working text is=
=20
stable it will be liaised to you.

Sincerely,




Gavin Young
DSL Forum Technical Chair



------=_NextPart_000_7c09_6737_28e2
Content-Type: text/plain; name="WT-096v1.txt"; format=flowed
Content-Disposition: attachment; filename="WT-096v1.txt"
X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id PAA23540
Content-Transfer-Encoding: quoted-printable


DSL Forum

Working Text
WT-096
Revision-1

Straw Ballot

SCM Specific Managed Objects In VDSL Network Element



For
Operations and Network Management Working Group

Date:  November, 2003


Abstract:
This working text contains SCM specific managed objects that can optional=
ly=20
be used for VDSL network elements, in addition to the line-code-independe=
nt=20
parameters specified by the VDSL Network Element Management (TR-057).


Notice:
This Working Text represents work in progress by the DSL Forum and must n=
ot=20
be construed as an official DSL Forum Technical Report.  Nothing in this=20
document is binding on the DSL Forum or any of its members.  The document=
 is=20
offered as a basis for discussion and communication, both within and with=
out=20
the DSL Forum.
Contents
1Introduction	3
2SCM Specific VDSL Configuration Parameters	3
2.1Configuration Carrier Identity	3
2.2Configuration Carrier Usage	3
2.3Configuration Center Frequency Factor	4
2.4Configuration Symbol Rate Factor	4
2.5Configuration Constellation Size	4
2.6Configuration PSD Level	4
3SCM Specific VDSL Actual Parameters 	4
3.1Actual Carrier Identity	4
3.2Carrier Usage	4
3.3Center Frequency Factor	4
3.4Symbol Rate Factor	5
3.5Constellation Size	5
3.6Carrier PSD Level	5
4SCM Specific VDSL Band Measurements	5
4.1Carrier Identity	5
4.2SNR Margin	5
4.3Attenuation	5
5References	5

1Introduction

The Operations and Network Management Working Group of DSL Forum develope=
d=20
the =93VDSL Network Element Management=94 (WT-68, now TR-057). TR-57 defi=
nes the=20
line-code-independent parameters required for managing VDSL lines.

This document defines SCM line-code-specific managed objects that can be=20
optionally used in certain cases such as for diagnostics and per band=20
management, if preferred.

2SCM Specific VDSL Configuration Parameters

The following line-code-specific parameters may be used for configuring a=
n=20
SCM VDSL line. The parameters are defined per each provisioned SCM carrie=
r=20
in a line configuration.
It is assumed that line-code-specific configuration will be used only in=20
special cases such as for testing and may not be consistent with paramete=
rs=20
configured through the Configuration Parameters of VDSL Network Element=20
Management as described in TR-057[1].
If used, this set of parameters should supercede VDSL Configuration=20
Parameter configurations previously requested for Deployment Scenario and=
=20
Spectrum Management and may not be consistent with configurations for Dat=
a=20
Rate Management.
2.1Configuration Carrier Identity
An enumerated index that identifies the carrier associated with the set o=
f=20
configuration parameters.
The Configuration Carrier Identity may have one of the following values:
Optional Band (range from 25 kHz to 138 kHz. See TR-057, section 2.3.3)
1D  (transmission from VTU-C in first downstream band)
1U  (transmission from VTU-R in first upstream band)
2D  (transmission from VTU-C in second downstream band)
2U  (transmission from VTU-R in second upstream band)

Note that use and direction of the Optional Band is determined by Spectra=
l=20
Management Configuration Parameters of VDSL Network Element Management as=
=20
described in TR-057.
2.2Configuration Carrier Usage
This parameter specifies if the carrier, referred by Configuration Carrie=
r=20
Identity, is used. The values may be:
Used
Not Used

When referencing the Optional Band this parameter should reflect the=20
Optional Band Usage as determined by Spectral Management Configuration=20
Parameters that is described in TR-057.
2.3Configuration Center Frequency Factor
The integer ratio of the center frequency to 16.875 kHz, for the carrier=20
referred by Configuration Carrier Identity.
2.4Configuration Symbol Rate Factor
The integer ratio of the symbol rate to 33.75 kbaud, for the carrier=20
referred by Configuration Carrier Identity.
2.5Configuration Constellation Size
The number of bits per symbol modulated onto the carrier, referred by=20
Configuration Carrier Identity.
2.6Configuration PSD Level
The PSD level of the carrier, referred by Configuration Carrier Identity,=
 in=20
the range: -38 dBm/Hz to -140 dBm/Hz using steps of 0.25 dBm/Hz.

3SCM Specific VDSL Actual Parameters

The following parameters indicate the actual working parameters of an SCM=
=20
VDSL line. The parameters are defined per each provisioned SCM carrier in=
 a=20
line configuration.

These parameters may be the result of configuration through VDSL Network=20
Element Management - Data Rate Management with either Manual or Rate=20
Adaptation mode or the result of line-code-specific configurations as=20
described above.
3.1Actual Carrier Identity
A set of Current Configuration Parameters is recorded for the carrier=20
identified by Actual Carrier Identity.
This is an enumerated index that may have one of the following values:
Optional Band (range from 25 kHz to 138 kHz. See TR-057, section 2.3.3)
1D  (transmission from VTU-C in first downstream band)
1U  (transmission from VTU-R in first upstream band)
2D  (transmission from VTU-C in second downstream band)
2U  (transmission from VTU-R in second upstream band)
3.2Carrier Usage
This parameter specifies if the carrier, referred by Actual Carrier=20
Identity, is currently in use. The values may be:
Used
Not Used
3.3Center Frequency Factor
The integer ratio of the actual center frequency to 16.875 kHz, for the=20
carrier indicated by the Actual Carrier Identity.
3.4Symbol Rate Factor
The integer ratio of the actual symbol rate to 33.75 kbaud, for the carri=
er=20
indicated by the Actual Carrier Identity.
3.5Constellation Size
The number of bits per symbol modulated onto the carrier indicated by the=
=20
Actual Carrier Identity.
3.6Carrier PSD Level
PSD level in the range: -38 dBm/Hz to -140 dBm/Hz in 0.25 dBm/Hz steps, o=
f=20
the carrier indicated by the Actual Carrier Identity.
4SCM Specific VDSL Band Measurements

The following parameters indicate measurements per each provisioned carri=
er=20
in an SCM VDSL line configuration.
4.1Carrier Identity
A set of physical measurements parameters associated with the carrier=20
identified by Carrier Identity.
This is an enumerated index that may have one of the following values:
Optional Band (range from 25 kHz to 138 kHz. See TR-057, section 2.3.3)
1D  (transmission from VTU-C in first downstream band)
1U  (transmission from VTU-R in first upstream band)
2D  (transmission from VTU-C in second downstream band)
2U  (transmission from VTU-R in second upstream band)
4.2SNR Margin
The SNR margin measured on the carrier indicated by the Carrier Identity=20
having values in the range: -31.75 dB to +31.75 dB in steps of 0.25 dB.
4.3Attenuation
The line attenuation measured on the carrier indicated by the Carrier=20
Identity having values in the range: 0 dB to 63.75 dB in steps of 0.25 dB.

5References
[1]	DSL Forum TR-057: =93VDSL Network Element Management=94, February 200=
2.


------=_NextPart_000_7c09_6737_28e2--

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



From exim@www1.ietf.org  Mon Nov 24 10:30:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12508
	for <adslmib-archive@odin.ietf.org>; Mon, 24 Nov 2003 10:30:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOIf8-000101-0y
	for adslmib-archive@odin.ietf.org; Mon, 24 Nov 2003 10:30:07 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOFU6JE003840
	for adslmib-archive@odin.ietf.org; Mon, 24 Nov 2003 10:30:06 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOIf7-0000zr-Sf
	for adslmib-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 10:30:05 -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 KAA12475
	for <adslmib-web-archive@ietf.org>; Mon, 24 Nov 2003 10:29:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOIf5-0006n3-00
	for adslmib-web-archive@ietf.org; Mon, 24 Nov 2003 10:30:03 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOIf5-0006mz-00
	for adslmib-web-archive@ietf.org; Mon, 24 Nov 2003 10:30:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOIf4-0000zW-RB; Mon, 24 Nov 2003 10:30:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOIef-0000yo-IP
	for adslmib@optimus.ietf.org; Mon, 24 Nov 2003 10:29:37 -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 KAA12467
	for <adslmib@ietf.org>; Mon, 24 Nov 2003 10:29:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOIed-0006mp-00
	for adslmib@ietf.org; Mon, 24 Nov 2003 10:29:35 -0500
Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOIec-0006mm-00
	for adslmib@ietf.org; Mon, 24 Nov 2003 10:29:34 -0500
Received: from pesa.com ([216.180.38.253])
	by mail.hiwaay.net (8.12.10/8.12.10) with ESMTP id hAOFTWtx1004731
	for <adslmib@ietf.org>; Mon, 24 Nov 2003 09:29:33 -0600 (CST)
Received: from 192.168.0.122 ([192.168.0.122])
	by pesa.com (pesa.com [127.0.0.1])
	(MDaemon.PRO.v6.8.5.R)
	with ESMTP id 60-md50000000197.tmp
	for <adslmib@ietf.org>; Mon, 24 Nov 2003 09:29:31 -0600
Subject: Re: [Adslmib] Issue with HCTC Perf Interval MIB (and therefore
	with the VDSL MIB)
From: Bob Ray <rray@pesa.com>
Reply-To: rray@pesa.com
To: Mike Sneed <sneedmike@hotmail.com>
Cc: adslmib mail list <adslmib@ietf.org>
In-Reply-To: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com>
References: <BAY10-F38Oh8s4KWiGt0000e325@hotmail.com>
Content-Type: text/plain
Message-Id: <1069687770.2734.30.camel@localhost.localdomain>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) 
Date: 24 Nov 2003 09:29:30 -0600
Content-Transfer-Encoding: 7bit
X-Spam-Processed: pesa.com, Mon, 24 Nov 2003 09:29:31 -0600
	(not processed: message from valid local sender)
X-MDRemoteIP: 192.168.0.122
X-Return-Path: rray@pesa.com
X-MDaemon-Deliver-To: adslmib@ietf.org
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>
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

On Mon, 2003-11-17 at 11:06, Michael Sneed wrote:
> During the IETF Last Call process there were some concerns expressed in the 
> IESG about the HCTC Performance Interval MIB 
> (draft-ietf-adslmib-hc-tc-06.txt) that we have recommended to go to Proposed 
> Standard.  In a nutshell, the problem is one of alignment of the various 
> MIBs that deal with this topic (namely RFC3593 and 2856).
> 
> As a result of this discussion, it has been recommended that we change
> 
>     - HCPerfTimeElapsed, Gauge32 (0...86399)
>     - HCPerfValidIntervals, Gauge32 (0...96)
>     - HCPerfInvalidIntervals, Gauge32 (0...96)
> 
> to type Integer32.

draft-ietf-adslmib-hc-tc-07.txt has been submitted with the above
changes.

-- 
Bob Ray <rray@pesa.com>


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



From exim@www1.ietf.org  Mon Nov 24 11:46:21 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15356
	for <adslmib-archive@odin.ietf.org>; Mon, 24 Nov 2003 11:46:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOJqd-0006vR-VN
	for adslmib-archive@odin.ietf.org; Mon, 24 Nov 2003 11:46:06 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOGk3wH026618
	for adslmib-archive@odin.ietf.org; Mon, 24 Nov 2003 11:46:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOJqd-0006vF-QV
	for adslmib-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 11:46:03 -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 LAA15346
	for <adslmib-web-archive@ietf.org>; Mon, 24 Nov 2003 11:45:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOJqc-00006k-00
	for adslmib-web-archive@ietf.org; Mon, 24 Nov 2003 11:46:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOJqc-00006h-00
	for adslmib-web-archive@ietf.org; Mon, 24 Nov 2003 11:46:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOJqb-0006v0-45; Mon, 24 Nov 2003 11:46:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AOJq3-0006uE-Nt
	for adslmib@optimus.ietf.org; Mon, 24 Nov 2003 11:45:28 -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 LAA15328
	for <adslmib@ietf.org>; Mon, 24 Nov 2003 11:45:12 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOJq2-00006V-00
	for adslmib@ietf.org; Mon, 24 Nov 2003 11:45:26 -0500
Received: from auemail1.lucent.com ([192.11.223.161] helo=auemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AOJq1-00005m-00
	for adslmib@ietf.org; Mon, 24 Nov 2003 11:45:25 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by auemail1.firewall.lucent.com (Switch-2.2.8/Switch-2.2.0) with ESMTP id hAOGiog17921
	for <adslmib@ietf.org>; Mon, 24 Nov 2003 10:44:51 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2656.59)
	id <XRFGD167>; Mon, 24 Nov 2003 17:25:40 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15502FB8828@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: rray@pesa.com, Mike Sneed <sneedmike@hotmail.com>
Cc: adslmib mail list <adslmib@ietf.org>
Subject: RE: [Adslmib] Issue with HCTC Perf Interval MIB (and therefore wi
	th the VDSL MIB)
Date: Mon, 24 Nov 2003 17:25:39 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
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>

Thanks, I will pick it up from there when I see it appear
in the repository.

Bert 

> -----Original Message-----
> From: Bob Ray [mailto:rray@pesa.com]
> Sent: maandag 24 november 2003 16:30
> To: Mike Sneed
> Cc: adslmib mail list
> Subject: Re: [Adslmib] Issue with HCTC Perf Interval MIB (and 
> therefore
> with the VDSL MIB)
> 
> 
> On Mon, 2003-11-17 at 11:06, Michael Sneed wrote:
> > During the IETF Last Call process there were some concerns 
> expressed in the 
> > IESG about the HCTC Performance Interval MIB 
> > (draft-ietf-adslmib-hc-tc-06.txt) that we have recommended 
> to go to Proposed 
> > Standard.  In a nutshell, the problem is one of alignment 
> of the various 
> > MIBs that deal with this topic (namely RFC3593 and 2856).
> > 
> > As a result of this discussion, it has been recommended 
> that we change
> > 
> >     - HCPerfTimeElapsed, Gauge32 (0...86399)
> >     - HCPerfValidIntervals, Gauge32 (0...96)
> >     - HCPerfInvalidIntervals, Gauge32 (0...96)
> > 
> > to type Integer32.
> 
> draft-ietf-adslmib-hc-tc-07.txt has been submitted with the above
> changes.
> 
> -- 
> 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 Nov 24 15:34:20 2003
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27906
	for <adslmib-archive@odin.ietf.org>; Mon, 24 Nov 2003 15:34:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AONPH-0006wF-Tc
	for adslmib-archive@odin.ietf.org; Mon, 24 Nov 2003 15:34:03 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id hAOKY3cS026670
	for adslmib-archive@odin.ietf.org; Mon, 24 Nov 2003 15:34:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AONPH-0006w5-QE
	for adslmib-web-archive@optimus.ietf.org; Mon, 24 Nov 2003 15:34:03 -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 PAA27826
	for <adslmib-web-archive@ietf.org>; Mon, 24 Nov 2003 15:33:49 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AONPG-00046y-00
	for adslmib-web-archive@ietf.org; Mon, 24 Nov 2003 15:34:02 -0500
Received: from [132.151.1.19] (helo=optimus.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AONPF-00046v-00
	for adslmib-web-archive@ietf.org; Mon, 24 Nov 2003 15:34:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AONPF-0006vO-51; Mon, 24 Nov 2003 15:34:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AONNB-0006jL-M8
	for adslmib@optimus.ietf.org; Mon, 24 Nov 2003 15:31:53 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27333;
	Mon, 24 Nov 2003 15:31:38 -0500 (EST)
Message-Id: <200311242031.PAA27333@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: adslmib@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Date: Mon, 24 Nov 2003 15:31:38 -0500
Subject: [Adslmib] I-D ACTION:draft-ietf-adslmib-hc-tc-07.txt
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>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the ADSL MIB Working Group of the IETF.

	Title		: High Capacity Textual Conventions for MIB Modules 
			  Using Performance History Based on 15 Minute Intervals
	Author(s)	: B. Ray, R. Abbi
	Filename	: draft-ietf-adslmib-hc-tc-07.txt
	Pages		: 10
	Date		: 2003-11-24
	
This document presents a set of High Capacity Textual Conventions 
for use in MIB modules which require performance history based upon 
15 minute intervals.  The Textual Conventions defined in this 
document extend the conventions presented in RFC 2493 to 64 bit 
resolution using the conventions presented in RFC 2856.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-adslmib-hc-tc-07.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-adslmib-hc-tc-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-adslmib-hc-tc-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2003-11-24152309.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-adslmib-hc-tc-07.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-adslmib-hc-tc-07.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-11-24152309.I-D@ietf.org>

--OtherAccess--

--NextPart--



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



