From exim@www1.ietf.org Mon Aug 25 07:08:55 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 HAA10318 for ; Mon, 25 Aug 2003 07:08:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rFD6-0002Zh-KY for adslmib-archive@odin.ietf.org; Mon, 25 Aug 2003 07:08:32 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7PB8W0k009891 for adslmib-archive@odin.ietf.org; Mon, 25 Aug 2003 07:08:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rFD6-0002ZS-H5 for adslmib-web-archive@optimus.ietf.org; Mon, 25 Aug 2003 07:08:32 -0400 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 HAA10276 for ; Mon, 25 Aug 2003 07:08:24 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rFCb-0002Xf-BU; Mon, 25 Aug 2003 07:08:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rFC6-0002Ni-1M for adslmib@optimus.ietf.org; Mon, 25 Aug 2003 07:07:30 -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 HAA10235 for ; Mon, 25 Aug 2003 07:07:21 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rFC1-0007CJ-00 for adslmib@ietf.org; Mon, 25 Aug 2003 07:07:25 -0400 Received: from auemail2.lucent.com ([192.11.223.163] helo=auemail2.firewall.lucent.com) by ietf-mx with esmtp (Exim 4.12) id 19rFC0-0007Bt-00 for adslmib@ietf.org; Mon, 25 Aug 2003 07:07:24 -0400 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemail2.firewall.lucent.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id h7PB7II01156 for ; Mon, 25 Aug 2003 06:07:19 -0500 (CDT) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Mon, 25 Aug 2003 13:06:51 +0200 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550245BB1A@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: "C. M. Heard" Cc: "Mike Sneed (E-mail)" , "Adslmib (E-mail)" Date: Mon, 25 Aug 2003 13:06:43 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Subject: [Adslmib] RE: Internal WG Review: Recharter of ADSL MIB (adslmib) 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: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , I will let Mike Sneed respond to this. Byt my understanding is that the WG did not make good (any?) progress on getting implementation reports. Mike ? Thanks, Bert > -----Original Message----- > From: C. M. Heard [mailto:heard@pobox.com] > Sent: zaterdag 23 augustus 2003 18:51 > To: ietf@ietf.org > Subject: Re: Internal WG Review: Recharter of ADSL MIB (adslmib) > > > Regarding the following: > > On Tue, 19 Aug 2003, IESG-Secretary wrote: > > A new charter for the ADSL MIB (adslmib) > > in the Operations and Management Area > > of the IETF is being considered. > > The draft charter is provided below for your review > > and comment. > > > > The IETF Secretariat > > > > > > ADSL MIB (adslmib) > > --------------------- > > + lines with a + sign are new text > > - lines with a - sign will be removed from charter > > > > Description of Working Group: > [ ... ] > > - In addition, the group will continue to work on the > promotion of the > > - ADSLMIB, the ADSL Extension MIB, and the HDSL2/SHDSL MIB > through the > > - IETF standards process. > > I'm curious as to why this is being removed. The WG charter currently > lists three RFCs, all at Proposed standard: > > Definitions of Managed Objects for the ADSL Lines (RFC 2662, > August 1999) > > Definitions of Managed Objects for HDSL2 and SHDSL Lines (RFC 3276, > May 2002) > > Definitions of Extension Managed Objects for Asymmetric Digital > Subscriber Lines (RFC 3440, December 2002) > > Does it mean that the WG will no longer attempt to advance these > specifications to Draft Standard? > > Mike Heard > > > _______________________________________________ > This message was passed through > ietf_censored@carmen.ipv6.cselt.it, which is a sublist of > ietf@ietf.org. Not all messages are passed. Decisions on what > to pass are made solely by Raffaele D'Albenzio. > _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From exim@www1.ietf.org Mon Aug 25 09:24:30 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 JAA15849 for ; Mon, 25 Aug 2003 09:24: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 19rHKG-0006yF-Kk for adslmib-archive@odin.ietf.org; Mon, 25 Aug 2003 09:24:05 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7PDO4Lg026789 for adslmib-archive@odin.ietf.org; Mon, 25 Aug 2003 09:24:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rHKG-0006y0-HY for adslmib-web-archive@optimus.ietf.org; Mon, 25 Aug 2003 09:24:04 -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 JAA15821 for ; Mon, 25 Aug 2003 09:23:57 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rHKD-0000qv-00 for adslmib-web-archive@ietf.org; Mon, 25 Aug 2003 09:24:01 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19rHKC-0000qr-00 for adslmib-web-archive@ietf.org; Mon, 25 Aug 2003 09:24:00 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rHKD-0006xm-9X; Mon, 25 Aug 2003 09:24:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rHJY-0006xL-Kg for adslmib@optimus.ietf.org; Mon, 25 Aug 2003 09:23:20 -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 JAA15809 for ; Mon, 25 Aug 2003 09:23:14 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rHJW-0000qo-00 for adslmib@ietf.org; Mon, 25 Aug 2003 09:23:19 -0400 Received: from bay0-hmr19.bay0.hotmail.com ([65.54.241.218] helo=BAY0-HMR19) by ietf-mx with esmtp (Exim 4.12) id 19rHJV-0000qN-00 for adslmib@ietf.org; Mon, 25 Aug 2003 09:23:17 -0400 Received: from hotmail.com ([64.4.21.45]) by BAY0-HMR19 with Microsoft SMTPSVC(5.0.2195.5600); Mon, 25 Aug 2003 06:22:45 -0700 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Mon, 25 Aug 2003 06:22:45 -0700 Received: from 66.152.60.98 by lw14fd.law14.hotmail.msn.com with HTTP; Mon, 25 Aug 2003 13:22:36 GMT X-Originating-IP: [66.152.60.98] X-Originating-Email: [sneedmike@hotmail.com] From: "Michael Sneed" To: bwijnen@lucent.com, heard@pobox.com Cc: adslmib@ietf.org Subject: Re: [Adslmib] RE: Internal WG Review: Recharter of ADSL MIB (adslmib) Date: Mon, 25 Aug 2003 09:22:36 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 25 Aug 2003 13:22:45.0297 (UTC) FILETIME=[F8695210:01C36B0B] 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: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , There has been no call to advance the documents on the mailing list, and though at the time I requested implementation reports there were a number of implementations there were none sufficiently advanced to permit advancing the documents. I expect the situation may have changed in the time since we went for reports, although some of the implementation reports were from companies and/or products that no longer exist. I haven't heard a call to totally remove the advancement of the documents from the charter; there just hasn't been much interest from the community. I certainly don't have a problem with leaving this in the charter, if the WG agrees. Certainly the milestones will need to be updated. >From: "Wijnen, Bert (Bert)" >To: "C. M. Heard" >CC: "Mike Sneed (E-mail)" , "Adslmib >(E-mail)" >Subject: [Adslmib] RE: Internal WG Review: Recharter of ADSL MIB (adslmib) >Date: Mon, 25 Aug 2003 13:06:43 +0200 > >I will let Mike Sneed respond to this. >Byt my understanding is that the WG did not make good (any?) >progress on getting implementation reports. > >Mike ? > >Thanks, >Bert > > > -----Original Message----- > > From: C. M. Heard [mailto:heard@pobox.com] > > Sent: zaterdag 23 augustus 2003 18:51 > > To: ietf@ietf.org > > Subject: Re: Internal WG Review: Recharter of ADSL MIB (adslmib) > > > > > > Regarding the following: > > > > On Tue, 19 Aug 2003, IESG-Secretary wrote: > > > A new charter for the ADSL MIB (adslmib) > > > in the Operations and Management Area > > > of the IETF is being considered. > > > The draft charter is provided below for your review > > > and comment. > > > > > > The IETF Secretariat > > > > > > > > > ADSL MIB (adslmib) > > > --------------------- > > > + lines with a + sign are new text > > > - lines with a - sign will be removed from charter > > > > > > Description of Working Group: > > [ ... ] > > > - In addition, the group will continue to work on the > > promotion of the > > > - ADSLMIB, the ADSL Extension MIB, and the HDSL2/SHDSL MIB > > through the > > > - IETF standards process. > > > > I'm curious as to why this is being removed. The WG charter currently > > lists three RFCs, all at Proposed standard: > > > > Definitions of Managed Objects for the ADSL Lines (RFC 2662, > > August 1999) > > > > Definitions of Managed Objects for HDSL2 and SHDSL Lines (RFC 3276, > > May 2002) > > > > Definitions of Extension Managed Objects for Asymmetric Digital > > Subscriber Lines (RFC 3440, December 2002) > > > > Does it mean that the WG will no longer attempt to advance these > > specifications to Draft Standard? > > > > Mike Heard > > > > > > _______________________________________________ > > This message was passed through > > ietf_censored@carmen.ipv6.cselt.it, which is a sublist of > > ietf@ietf.org. Not all messages are passed. Decisions on what > > to pass are made solely by Raffaele D'Albenzio. > > > >_______________________________________________ >Adslmib mailing list >Adslmib@ietf.org >https://www1.ietf.org/mailman/listinfo/adslmib _________________________________________________________________ Get MSN 8 and enjoy automatic e-mail virus protection. http://join.msn.com/?page=features/virus _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From exim@www1.ietf.org Wed Aug 27 02:34:51 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 CAA26392 for ; Wed, 27 Aug 2003 02:34:51 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rtSY-0000kk-Rc for adslmib-archive@odin.ietf.org; Wed, 27 Aug 2003 02:07:11 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7R6786D002884 for adslmib-archive@odin.ietf.org; Wed, 27 Aug 2003 02:07:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rr6q-00011o-4X for adslmib-web-archive@optimus.ietf.org; Tue, 26 Aug 2003 23:36:36 -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 XAA13335 for ; Tue, 26 Aug 2003 23:36:30 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rr6n-0002i3-00 for adslmib-web-archive@ietf.org; Tue, 26 Aug 2003 23:36:34 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19rr6n-0002i0-00 for adslmib-web-archive@ietf.org; Tue, 26 Aug 2003 23:36:33 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rmyA-0005rL-Ry; Tue, 26 Aug 2003 19:11:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rejW-0004r3-3d for adslmib@optimus.ietf.org; Tue, 26 Aug 2003 10:23:42 -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 KAA07703 for ; Tue, 26 Aug 2003 10:23:35 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rejT-0001VR-00 for adslmib@ietf.org; Tue, 26 Aug 2003 10:23:39 -0400 Received: from law14-f61.law14.hotmail.com ([64.4.21.61] helo=hotmail.com) by ietf-mx with esmtp (Exim 4.12) id 19rejS-0001UP-00 for adslmib@ietf.org; Tue, 26 Aug 2003 10:23:38 -0400 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 26 Aug 2003 07:23:05 -0700 Received: from 66.152.60.98 by lw14fd.law14.hotmail.msn.com with HTTP; Tue, 26 Aug 2003 14:23:05 GMT X-Originating-IP: [66.152.60.98] X-Originating-Email: [sneedmike@hotmail.com] From: "Michael Sneed" To: adslmib@ietf.org Date: Tue, 26 Aug 2003 10:23:05 -0400 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 26 Aug 2003 14:23:05.0977 (UTC) FILETIME=[90EAFE90:01C36BDD] Subject: [Adslmib] Document advancement in WG charter 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: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , As you have seen, a question has arisen as to whether advancing the current Proposed Standards document produced by this working group should be retained in the WG charter. The key to the success of of these deliverables, if we choose to retain them, is the existence of "interoperable" implementations. So, we would need WG members who have implementations to prepare implementation reports. Generally speaking the implementations should conform to the RFCs, although one feature of requiring these implementations is that problems in implementation can be identified; ie. if there are portions of the MIB that no one or only one implementation includes, then we can assume that such portions are not useful and can be eliminated, or are not implementable and must be fixed. So if you have an implementation that is largely conformant, then please consider it as a candidate. So I have three questions for the list: 1) Should we include advancement of the current Proposed Standard documents to Draft Standard in our charter? 2) Do you have implementations of any of our RFCs that you would be willing to document in an implemenation report, and to allow to be used for interoperability testing? 3) If you answer "yes" to item 2), what time frame would be required to produce such a report?. This is useful because we need to propose milestone dates with the charter. Regards, Mike _________________________________________________________________ Get MSN 8 and help protect your children with advanced parental controls. http://join.msn.com/?page=features/parental _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From exim@www1.ietf.org Wed Aug 27 02:44:27 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 CAA27414 for ; Wed, 27 Aug 2003 02:44:27 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rsKi-00058o-Js for adslmib-archive@odin.ietf.org; Wed, 27 Aug 2003 00:55:02 -0400 Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7R4sxUD019746 for adslmib-archive@odin.ietf.org; Wed, 27 Aug 2003 00:54:59 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rmis-0004y2-11 for adslmib-web-archive@optimus.ietf.org; Tue, 26 Aug 2003 18:55: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 SAA18590 for ; Tue, 26 Aug 2003 18:55:26 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rmio-00041U-00 for adslmib-web-archive@ietf.org; Tue, 26 Aug 2003 18:55:30 -0400 Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19rmio-00041Q-00 for adslmib-web-archive@ietf.org; Tue, 26 Aug 2003 18:55:30 -0400 Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rluC-0002I2-4M; Tue, 26 Aug 2003 18:03:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19rkFS-0006Bx-8r for adslmib@optimus.ietf.org; Tue, 26 Aug 2003 16:17:02 -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 QAA05028 for ; Tue, 26 Aug 2003 16:16:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19rkFQ-0000p6-00 for adslmib@ietf.org; Tue, 26 Aug 2003 16:17:00 -0400 Received: from ant.hiwaay.net ([216.180.54.10] helo=mail.hiwaay.net) by ietf-mx with esmtp (Exim 4.12) id 19rkFA-0000or-00 for adslmib@ietf.org; Tue, 26 Aug 2003 16:16:59 -0400 Received: from pesa.com ([216.180.38.253]) by mail.hiwaay.net (8.12.9/8.12.9) with ESMTP id h7QKFch0597890 for ; Tue, 26 Aug 2003 15:16:34 -0500 (CDT) Received: from 192.168.0.122 ([192.168.0.122]) by pesa.com (pesa.com [127.0.0.1]) (MDaemon.PRO.v6.8.4.R) with ESMTP id 26-md50000000600.tmp for ; Tue, 26 Aug 2003 15:15:58 -0500 From: Bob Ray Reply-To: rray@pesa.com To: "Wijnen, Bert (Bert)" Cc: "Mike Sneed (E-mail)" , Rajesh Abbi , "Randy Presuhn (E-mail)" , "Adslmib (E-mail)" In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B1550245BE62@nl0006exch001u.nl.lucent.com> References: <7D5D48D2CAA3D84C813F5B154F43B1550245BE62@nl0006exch001u.nl.lucent.com> Content-Type: text/plain Message-Id: <1061928957.11305.46.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 26 Aug 2003 15:15:58 -0500 Content-Transfer-Encoding: 7bit X-Spam-Processed: pesa.com, Tue, 26 Aug 2003 15:15:58 -0500 (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 Subject: [Adslmib] Re: AD review of draft-ietf-adslmib-vdsl-10.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: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Hi Bert. I'll make the changes you suggested (along with Randy's earlier comments) and will (hopefully) have two new drafts in after the weekend. On one of your questions: - So we ask IANA to assign a value under transmission (for the > mib module). Is it best to use 97 (for vdsl ifType) ? or > better not since other ifTypes seem included as well? are you suggesting that I just put 'transmission 97' instead of 'transmission XXXX' along with the note to the RFC Editor? If so, no problem, but will anyone else have a problem with that? Bob Ray _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib