From adslmib-bounces@ietf.org Wed Nov 01 10:26:03 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfHyR-0003um-8W; Wed, 01 Nov 2006 10:25:51 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GfHyQ-0003uF-BK for adslmib@ietf.org; Wed, 01 Nov 2006 10:25:50 -0500 Received: from eci-iron.ecitele.com ([147.234.242.112] helo=iron.ecitele.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GfHjC-0002Im-C6 for adslmib@ietf.org; Wed, 01 Nov 2006 10:10:12 -0500 Received: from ilptexfe.ecitele.com (HELO ILPTEXFE01.ecitele.com) ([172.31.244.40]) by iron.ecitele.com with ESMTP; 01 Nov 2006 17:15:48 +0200 Received: from ILPTMAIL01.ecitele.com ([147.234.245.210]) by ILPTEXFE01.ecitele.com with Microsoft SMTPSVC(6.0.3790.2499); Wed, 1 Nov 2006 17:10:00 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 1 Nov 2006 17:09:57 +0200 Message-ID: <2F7C502D2CC5EF4CBA93F7F47896E197297EF5@ilptex01.ecitele.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Items raised by the AD's Thread-Index: Acb9x8sSRbS9t7KpTyeZ0Pysg0cM1Q== From: "Menachem Dodge" To: , "Edward Beili" , "Moti Morgenstern" , X-OriginalArrivalTime: 01 Nov 2006 15:10:00.0901 (UTC) FILETIME=[CD298F50:01C6FDC7] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8fbbaa16f9fd29df280814cb95ae2290 Cc: David Kessens , Michael Sneed Subject: [Adslmib] Items raised by the AD's X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ADSLMIB List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2047124711==" Errors-To: adslmib-bounces@ietf.org This is a multi-part message in MIME format. --===============2047124711== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6FDC7.CCFC967C" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6FDC7.CCFC967C Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello All, =20 In a teleconference held yesterday between the Chairs and the AD's the following issues were raised: =20 1. xDSL Bonding MIB: =20 As these MIBs will be make use of the "Interface Stack Capability MIB (IF-CAP-STACK-MIB)" as defined by Edward in the Hubmib-efm-cu-mib, this should be indicated in the documentation and in the Module Compliance statements. See also RFC 4181 section 4.8 Compliance Statements, last paragraph. =20 "In many cases, a MIB module is always implemented in conjunction with one or more other MIB modules. That fact is REQUIRED to be noted in the surrounding documentation (see Section 3.2 above), and it SHOULD also be noted in the relevant compliance statements." =20 2. Tools If anyone has any suggestions for modifications or additions for the tools provided (see http://tools.ietf.org/ ) please let us know. =20 While on the subject of tools, there is also the following web based, MIB compiler tools at http://www.ibr.cs.tu-bs.de/projects/libsmi/tools/ =20 Best Regards, Menachem. ------_=_NextPart_001_01C6FDC7.CCFC967C Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello=20 All,

=20 In a teleconference held yesterday between the Chairs and the AD's the = following=20 issues were

raised:

=20 1. xDSL Bonding MIB:

As = these=20 MIBs will be make use of the "Interface Stack Capability MIB=20 (IF-CAP-STACK-MIB)"

as = defined by Edward=20 in the Hubmib-efm-cu-mib, this should be indicated in the documentation=20 and

in = the Module=20 Compliance statements. See also RFC 4181 section 4.8 = Compliance=20 Statements,

last=20 paragraph.

"In = many cases, a=20 MIB module is always implemented in conjunction with
   one = or more=20 other MIB modules. That fact is REQUIRED to be noted = in
  =20 the surrounding documentation (see Section 3.2 above), and it=20 SHOULD
   also be noted in the relevant compliance=20 statements."

2.=20 Tools

If = anyone has any=20 suggestions for modifications or additions for the tools=20 provided

(see http://tools.ietf.org/ ) = please let us know.

While = on=20 the subject of tools, there is also the following = web based,=20 MIB compiler tools at

http://www.ibr= .cs.tu-bs.de/projects/libsmi/tools/

Best = Regards,

Menachem.

------_=_NextPart_001_01C6FDC7.CCFC967C-- --===============2047124711== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib --===============2047124711==-- From adslmib-bounces@ietf.org Wed Nov 29 20:31:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gpalq-0002ET-E6; Wed, 29 Nov 2006 20:31:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gpaln-0002E8-Sj; Wed, 29 Nov 2006 20:31:23 -0500 Received: from nit.isi.edu ([128.9.160.116]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Gpalm-0002XQ-HJ; Wed, 29 Nov 2006 20:31:23 -0500 Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.11.20060308/8.12.11) with ESMTP id kAU1VMPA011362; Wed, 29 Nov 2006 17:31:22 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.11.20060308/8.12.11/Submit) id kAU1VLW0011361; Wed, 29 Nov 2006 17:31:21 -0800 Date: Wed, 29 Nov 2006 17:31:21 -0800 Message-Id: <200611300131.kAU1VLW0011361@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org X-Spam-Score: -14.8 (--------------) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Cc: adslmib@ietf.org, rfc-editor@rfc-editor.org Subject: [Adslmib] RFC 4706 on Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2) X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ADSLMIB List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: adslmib-bounces@ietf.org A new Request for Comments is now available in online RFC libraries. RFC 4706 Title: Definitions of Managed Objects for Asymmetric Digital Subscriber Line 2 (ADSL2) Author: M. Morgenstern, M. Dodge, S. Baillie, U. Bonollo Status: Standards Track Date: November 2006 Mailbox: moti.Morgenstern@ecitele.com, mbdodge@ieee.org, scott.baillie@nec.com.au, umberto.bonollo@nec.com.au Pages: 167 Characters: 347648 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-adslmib-adsl2-08.txt URL: http://www.rfc-editor.org/rfc/rfc4706.txt This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing parameters of the "Asymmetric Digital Subscriber Line" family of interface types: ADSL, ADSL2, ADSL2+, and their variants. [STANDARDS TRACK] This document is a product of the ADSL MIB Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From adslmib-bounces@ietf.org Thu Nov 30 04:27:39 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpiCc-0007NB-Td; Thu, 30 Nov 2006 04:27:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GpiCb-0007N5-JL for adslmib@ietf.org; Thu, 30 Nov 2006 04:27:33 -0500 Received: from eci-iron.ecitele.com ([147.234.242.112] helo=iron.ecitele.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GpiCW-00039Z-Ss for adslmib@ietf.org; Thu, 30 Nov 2006 04:27:33 -0500 Received: from ilptexfe.ecitele.com (HELO ILPTEXFE01.ecitele.com) ([172.31.244.40]) by iron.ecitele.com with ESMTP; 30 Nov 2006 11:39:51 +0200 Received: from ILPTMAIL01.ecitele.com ([147.234.245.210]) by ILPTEXFE01.ecitele.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 30 Nov 2006 11:27:16 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: FW: [Adslmib] RFC 4706 on Definitions of Managed Objects for AsymmetricDigital Subscriber Line 2 (ADSL2) Date: Thu, 30 Nov 2006 11:27:16 +0200 Message-ID: <2F7C502D2CC5EF4CBA93F7F47896E19747745F@ilptex01.ecitele.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [Adslmib] RFC 4706 on Definitions of Managed Objects for AsymmetricDigital Subscriber Line 2 (ADSL2) Thread-Index: AccUH6UvNQOXfXisQdCEnEyzF18QEAAPICmQ From: "Menachem Dodge" To: , X-OriginalArrivalTime: 30 Nov 2006 09:27:16.0748 (UTC) FILETIME=[B9F394C0:01C71461] X-Spam-Score: 0.0 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f Cc: X-BeenThere: adslmib@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ADSLMIB List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: adslmib-bounces@ietf.org Hello Everyone, Congratulations to the editors Moti, Umberto and Scott for completing this RFC. I'd also like to thank everyone on the WG who contributed and reviewed this document. Special thanks to the former Area Director, Bert Wijnen and the current Area Director, Dan Romascanu for all their hard work. Finally many thanks to the RFC Editor for all their efforts in publishing this document. Just to update everyone, work is continuing on the Vdsl2 draft and I'm expecting the initial bonding drafts to be posted within the next ten days. Best Regards, Menachem. =20 =09 -----Original Message----- From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org]=20 Sent: Thursday, November 30, 2006 3:31 AM To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org Cc: adslmib@ietf.org; rfc-editor@rfc-editor.org Subject: [Adslmib] RFC 4706 on Definitions of Managed Objects for AsymmetricDigital Subscriber Line 2 (ADSL2) A new Request for Comments is now available in online RFC libraries. =20 RFC 4706 Title: Definitions of Managed Objects for=20 Asymmetric Digital Subscriber Line 2 (ADSL2)=20 Author: M. Morgenstern, M. Dodge, S. Baillie, U. Bonollo Status: Standards Track Date: November 2006 Mailbox: moti.Morgenstern@ecitele.com,=20 mbdodge@ieee.org,=20 scott.baillie@nec.com.au, umberto.bonollo@nec.com.au Pages: 167 Characters: 347648 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-adslmib-adsl2-08.txt URL: http://www.rfc-editor.org/rfc/rfc4706.txt This document defines a Management Information Base (MIB) module for use with network management protocols in the Internet community. In particular, it describes objects used for managing parameters of the "Asymmetric Digital Subscriber Line" family of interface types: ADSL, ADSL2, ADSL2+, and their variants. [STANDARDS TRACK] This document is a product of the ADSL MIB Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and=20 suggestions for improvements.Please refer to the current edition of the=20 Internet Official Protocol Standards (STD 1) for the standardization=20 state and status of this protocol. Distribution of this memo is=20 unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body=20 help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. The RFC Editor Team USC/Information Sciences Institute ... _______________________________________________ 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