From mailnull@www1.ietf.org Thu Jan 2 20:01:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18637 for ; Thu, 2 Jan 2003 20:01:49 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h031AKr05676 for adslmib-archive@odin.ietf.org; Thu, 2 Jan 2003 20:10:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h031AKJ05673 for ; Thu, 2 Jan 2003 20:10:20 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18616 for ; Thu, 2 Jan 2003 20:01:18 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h031AGJ05658; Thu, 2 Jan 2003 20:10:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h02Hj1J08071 for ; Thu, 2 Jan 2003 12:45:01 -0500 Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09223; Thu, 2 Jan 2003 12:36:07 -0500 (EST) Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id h02HdID13700; Thu, 2 Jan 2003 09:39:18 -0800 (PST) Message-Id: <200301021739.h02HdID13700@gamma.isi.edu> To: IETF-Announce: ; Cc: rfc-editor@rfc-editor.org, adslmib@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 02 Jan 2003 09:39:18 -0800 Subject: [Adslmib] RFC 3440 on Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines 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: , --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3440 Title: Definitions of Extension Managed Objects for Asymmetric Digital Subscriber Lines Author(s): F. Ly, G. Bathrick Status: Standards Track Date: December 2002 Mailbox: faye@pedestalnetworks.com, greg.bathrick@nokia.com Pages: 36 Characters: 76058 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-adslmib-adslext-12.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3440.txt This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes additional managed objects used for managing Asymmetric Digital Subscriber Line (ADSL) interfaces not covered by the ADSL Line MIB (RFC 2662). This document is a product of the ADSL MIB Working Group of the IETF. This is now a Proposed Standard Protocol. 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.echo 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. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <030102093706.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3440 --OtherAccess Content-Type: Message/External-body; name="rfc3440.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <030102093706.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart-- _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Jan 8 09:09:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20338 for ; Wed, 8 Jan 2003 09:09:51 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h08EL5524366 for adslmib-archive@odin.ietf.org; Wed, 8 Jan 2003 09:21:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08EL5J24363 for ; Wed, 8 Jan 2003 09:21:05 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20271 for ; Wed, 8 Jan 2003 09:08:40 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08EJhJ24236; Wed, 8 Jan 2003 09:19:43 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08E01J22635 for ; Wed, 8 Jan 2003 09:00:01 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19262; Wed, 8 Jan 2003 08:48:11 -0500 (EST) Message-Id: <200301081348.IAA19262@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: Wed, 08 Jan 2003 08:48:11 -0500 Subject: [Adslmib] I-D ACTION:draft-ietf-adslmib-vdsl-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: , List-Id: ADSLMIB List-Post: List-Help: List-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 : Definitions of Managed Objects for Very High Speed Digital Subscriber Lines (VDSL) Author(s) : B. Ray, R. Abbi Filename : draft-ietf-adslmib-vdsl-07.txt Pages : 82 Date : 2003-1-7 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 Very high speed Digital Subscriber Line (VDSL) interfaces [T1E1311, T1E1011, T1E1013, ETSI2701, ETSI2702, ITU9931]. This document specifies a MIB module in a manner that is compliant to the SMIv2 (STD 58 [RFC2578, RFC2579, RFC2580]). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-adslmib-vdsl-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-vdsl-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-vdsl-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-1-7160455.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-adslmib-vdsl-07.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-adslmib-vdsl-07.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-1-7160455.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Jan 8 09:12:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20463 for ; Wed, 8 Jan 2003 09:12:59 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h08EOD624589 for adslmib-archive@odin.ietf.org; Wed, 8 Jan 2003 09:24:13 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08EODJ24586 for ; Wed, 8 Jan 2003 09:24:13 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20292 for ; Wed, 8 Jan 2003 09:09:06 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08EJmJ24255; Wed, 8 Jan 2003 09:19:48 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h08E0RJ22658 for ; Wed, 8 Jan 2003 09:00:27 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA19279; Wed, 8 Jan 2003 08:48:16 -0500 (EST) Message-Id: <200301081348.IAA19279@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: Wed, 08 Jan 2003 08:48:16 -0500 Subject: [Adslmib] I-D ACTION:draft-ietf-adslmib-hc-tc-03.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: , --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-03.txt Pages : 12 Date : 2003-1-7 This document presents a set of Textual Conventions for MIB modules which extends the conventions presented in RFC2493 to 64 bit resolution using the conventions presented in RFC2856. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-adslmib-hc-tc-03.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-03.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-03.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-1-7160518.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-adslmib-hc-tc-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-adslmib-hc-tc-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-1-7160518.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Wed Jan 15 13:20:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05688 for ; Wed, 15 Jan 2003 13:20:57 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0FIZf331815 for adslmib-archive@odin.ietf.org; Wed, 15 Jan 2003 13:35:41 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FIZfJ31812 for ; Wed, 15 Jan 2003 13:35:41 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05678 for ; Wed, 15 Jan 2003 13:20:26 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FIZVJ31802; Wed, 15 Jan 2003 13:35:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0FIYZJ31758 for ; Wed, 15 Jan 2003 13:34:35 -0500 Received: from lmmx1.fl.icn.siemens.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA05668 for ; Wed, 15 Jan 2003 13:19:20 -0500 (EST) Received: from stca200a.bus.sc.rolm.com (stca200a.bus.sc.rolm.com [165.218.68.180]) by lmmx1.fl.icn.siemens.com (8.9.3/8.9.3) with ESMTP id NAA09766 for ; Wed, 15 Jan 2003 13:22:41 -0500 (EST) Received: by stca200a.bus.sc.rolm.com with Internet Mail Service (5.5.2653.19) id ; Wed, 15 Jan 2003 10:22:41 -0800 Message-ID: From: "El Houmaidi, Mounire" To: "'adslmib@ietf.org'" Date: Wed, 15 Jan 2003 10:22:34 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL draf t)? 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: , Hello To all, In RFC 2662 (ADSL), adslLineSpecific under the adslLineTable may be used to determine shelf/slot/port of the ATUC interface in a DSLAM. This mapping is important for mapping an IfIndex to a Physical interface (depending on implementation) in the entity Physical Table (RFC 2737) or to an enterprise Table containing the Physical entities. we don't see that mapping done in RFC 3276 (SHDSL) or VDSL draft. How can we provide the same feature for SHDSL and VDSL? Regards Mounire El Houmaidi Siemens ICN,Lake Mary , Florida _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Thu Jan 16 02:03:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA26284 for ; Thu, 16 Jan 2003 02:03:33 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0G7IWd26947 for adslmib-archive@odin.ietf.org; Thu, 16 Jan 2003 02:18:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G7IVJ26944 for ; Thu, 16 Jan 2003 02:18:31 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25839 for ; Thu, 16 Jan 2003 02:03:01 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G7IGJ26928; Thu, 16 Jan 2003 02:18:16 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0G7HbJ26884 for ; Thu, 16 Jan 2003 02:17:37 -0500 Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25062; Thu, 16 Jan 2003 02:02:06 -0500 (EST) From: Moti.Morgenstern@inoviatele.com Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125]) by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id IAA16606; Thu, 16 Jan 2003 08:59:59 +0200 (IST) Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL draf t)? To: "El Houmaidi, Mounire" Cc: adslmib@ietf.org, adslmib-admin@ietf.org X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 Message-ID: Date: Thu, 16 Jan 2003 09:05:11 +0200 X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at 01/16/2003 09:05:12 AM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii 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: , Hi, The purpose of adslLineSpecific, as I understand it, is to behave as a hook for any vendor specific MIB extension. Such an extension can ALSO be used for providing the type of information you mention but it's its main purpose. Best regards, Moti Morgenstern Senior System Engineer Inovia Telecoms Ltd. Member of the ECI Telecom group 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 e-mail: Moti.Morgenstern@inoviatele.com "El Houmaidi, Mounire" To: "'adslmib@ietf.org'" t)? Sent by: adslmib-admin@ ietf.org 15/01/03 20:22 Hello To all, In RFC 2662 (ADSL), adslLineSpecific under the adslLineTable may be used to determine shelf/slot/port of the ATUC interface in a DSLAM. This mapping is important for mapping an IfIndex to a Physical interface (depending on implementation) in the entity Physical Table (RFC 2737) or to an enterprise Table containing the Physical entities. we don't see that mapping done in RFC 3276 (SHDSL) or VDSL draft. How can we provide the same feature for SHDSL and VDSL? Regards Mounire El Houmaidi Siemens ICN,Lake Mary , Florida _______________________________________________ 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 mailnull@www1.ietf.org Thu Jan 16 08:12:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09315 for ; Thu, 16 Jan 2003 08:12:21 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0GDRRO20575 for adslmib-archive@odin.ietf.org; Thu, 16 Jan 2003 08:27:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GDRRJ20572 for ; Thu, 16 Jan 2003 08:27:27 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09307 for ; Thu, 16 Jan 2003 08:11:49 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GDRKJ20543; Thu, 16 Jan 2003 08:27:20 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GDQ3J20440 for ; Thu, 16 Jan 2003 08:26:03 -0500 Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09202; Thu, 16 Jan 2003 08:10:23 -0500 (EST) From: Moti.Morgenstern@inoviatele.com Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125]) by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id PAA18442; Thu, 16 Jan 2003 15:08:30 +0200 (IST) Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL draf t)? To: adslmib@ietf.org, adslmib-admin@ietf.org, Mounire.El.Houmaidi@icn.siemens.com Cc: Moti.Morgenstern@inoviatele.com X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 Message-ID: Date: Thu, 16 Jan 2003 15:13:39 +0200 X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at 01/16/2003 03:13:43 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii 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: , Mounire, I'm sorry for omitting an important word in the last sentence: The proprietary extension can ALSO be used for providing the type of information you mention but it's NOT its main purpose. Moti Moti.Morgenstern @inoviatele.com To: "El Houmaidi, Mounire" Sent by: cc: adslmib@ietf.org, adslmib-admin@ietf.org adslmib-admin@ Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL ietf.org draf t)? 16/01/03 09:05 Hi, The purpose of adslLineSpecific, as I understand it, is to behave as a hook for any vendor specific MIB extension. Such an extension can ALSO be used for providing the type of information you mention but it's its main purpose. Best regards, Moti Morgenstern Senior System Engineer Inovia Telecoms Ltd. Member of the ECI Telecom group 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 e-mail: Moti.Morgenstern@inoviatele.com "El Houmaidi, Mounire" To: "'adslmib@ ietf.org'" t)? Sent by: adslmib-admin@ ietf.org 15/01/03 20:22 Hello To all, In RFC 2662 (ADSL), adslLineSpecific under the adslLineTable may be used to determine shelf/slot/port of the ATUC interface in a DSLAM. This mapping is important for mapping an IfIndex to a Physical interface (depending on implementation) in the entity Physical Table (RFC 2737) or to an enterprise Table containing the Physical entities. we don't see that mapping done in RFC 3276 (SHDSL) or VDSL draft. How can we provide the same feature for SHDSL and VDSL? Regards Mounire El Houmaidi Siemens ICN,Lake Mary , Florida _______________________________________________ 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 _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Thu Jan 16 10:49:30 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14284 for ; Thu, 16 Jan 2003 10:49:30 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0GG4ea32468 for adslmib-archive@odin.ietf.org; Thu, 16 Jan 2003 11:04:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GG4eJ32465 for ; Thu, 16 Jan 2003 11:04:40 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14243 for ; Thu, 16 Jan 2003 10:48:58 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GG4XJ32436; Thu, 16 Jan 2003 11:04:33 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GG1NJ32263 for ; Thu, 16 Jan 2003 11:01:23 -0500 Received: from lmmx1.fl.icn.siemens.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14168; Thu, 16 Jan 2003 10:45:41 -0500 (EST) Received: from stca200a.bus.sc.rolm.com (stca200a.bus.sc.rolm.com [165.218.68.180]) by lmmx1.fl.icn.siemens.com (8.9.3/8.9.3) with ESMTP id KAA05835; Thu, 16 Jan 2003 10:48:55 -0500 (EST) Received: by stca200a.bus.sc.rolm.com with Internet Mail Service (5.5.2653.19) id ; Thu, 16 Jan 2003 07:48:54 -0800 Message-ID: From: "El Houmaidi, Mounire" To: "'Moti.Morgenstern@inoviatele.com'" , adslmib@ietf.org, adslmib-admin@ietf.org Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? Date: Thu, 16 Jan 2003 07:48:54 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) 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: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Moti, I want to thank you for taking your time to answer our question. The use of the object is understood and i agree with you. My question is about the Other MIBS, SHDSL (RFC 3276) and VDSL draft: where such Object/feature (a hook to a specific MIB as you called it) is implemented in those MIBs? Mounire -----Original Message----- From: Moti.Morgenstern@inoviatele.com [mailto:Moti.Morgenstern@inoviatele.com] Sent: Thursday, January 16, 2003 8:14 AM To: adslmib@ietf.org; adslmib-admin@ietf.org; El Houmaidi, Mounire Cc: Moti.Morgenstern@inoviatele.com Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL draf t)? Mounire, I'm sorry for omitting an important word in the last sentence: The proprietary extension can ALSO be used for providing the type of information you mention but it's NOT its main purpose. Moti Moti.Morgenstern @inoviatele.com To: "El Houmaidi, Mounire" Sent by: cc: adslmib@ietf.org, adslmib-admin@ietf.org adslmib-admin@ Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL ietf.org draf t)? 16/01/03 09:05 Hi, The purpose of adslLineSpecific, as I understand it, is to behave as a hook for any vendor specific MIB extension. Such an extension can ALSO be used for providing the type of information you mention but it's its main purpose. Best regards, Moti Morgenstern Senior System Engineer Inovia Telecoms Ltd. Member of the ECI Telecom group 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 e-mail: Moti.Morgenstern@inoviatele.com "El Houmaidi, Mounire" To: "'adslmib@ ietf.org'" t)? Sent by: adslmib-admin@ ietf.org 15/01/03 20:22 Hello To all, In RFC 2662 (ADSL), adslLineSpecific under the adslLineTable may be used to determine shelf/slot/port of the ATUC interface in a DSLAM. This mapping is important for mapping an IfIndex to a Physical interface (depending on implementation) in the entity Physical Table (RFC 2737) or to an enterprise Table containing the Physical entities. we don't see that mapping done in RFC 3276 (SHDSL) or VDSL draft. How can we provide the same feature for SHDSL and VDSL? Regards Mounire El Houmaidi Siemens ICN,Lake Mary , Florida _______________________________________________ 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 _______________________________________________ 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 mailnull@www1.ietf.org Thu Jan 16 11:20:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15048 for ; Thu, 16 Jan 2003 11:20:01 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0GGZCQ02192 for adslmib-archive@odin.ietf.org; Thu, 16 Jan 2003 11:35:12 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GGZCJ02189 for ; Thu, 16 Jan 2003 11:35:12 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15034 for ; Thu, 16 Jan 2003 11:19:29 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GGZ5J02171; Thu, 16 Jan 2003 11:35:05 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GGX2J02019 for ; Thu, 16 Jan 2003 11:33:02 -0500 Received: from mink.ecitele.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14993; Thu, 16 Jan 2003 11:17:18 -0500 (EST) From: Moti.Morgenstern@inoviatele.com Received: from olive.ecitele.com (ilsmtp04.ecitele.com [147.234.8.125]) by mink.ecitele.com (8.9.1a/8.9.1) with ESMTP id SAA10051; Thu, 16 Jan 2003 18:15:21 +0200 (IST) Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? To: "El Houmaidi, Mounire" Cc: adslmib@ietf.org, adslmib-admin@ietf.org X-Mailer: Lotus Notes Release 5.0.2b (Intl) 16 December 1999 Message-ID: Date: Thu, 16 Jan 2003 18:14:49 +0200 X-MIMETrack: Serialize by Router on ILSMTP04/ECI Telecom(Release 5.0.9a |January 7, 2002) at 01/16/2003 06:20:34 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii 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: , Mounire, As long as the index/key to the proprietary MIB extension is the (same) one used by the IETF MIB I believe you don't really need an explicit "pointer" from within the VDSL/SHDSL MIBs to that proprietary MIB. However, it will be interesting to hear other opinions on this issue. Moti "El Houmaidi, Mounire" To: "'Moti.Morgenstern@inoviatele.com'" , Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? 16/01/03 17:48 Moti, I want to thank you for taking your time to answer our question. The use of the object is understood and i agree with you. My question is about the Other MIBS, SHDSL (RFC 3276) and VDSL draft: where such Object/feature (a hook to a specific MIB as you called it) is implemented in those MIBs? Mounire -----Original Message----- From: Moti.Morgenstern@inoviatele.com [mailto:Moti.Morgenstern@inoviatele.com] Sent: Thursday, January 16, 2003 8:14 AM To: adslmib@ietf.org; adslmib-admin@ietf.org; El Houmaidi, Mounire Cc: Moti.Morgenstern@inoviatele.com Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL draf t)? Mounire, I'm sorry for omitting an important word in the last sentence: The proprietary extension can ALSO be used for providing the type of information you mention but it's NOT its main purpose. Moti Moti.Morgenstern @inoviatele.com To: "El Houmaidi, Mounire" Sent by: cc: adslmib@ietf.org, adslmib-admin@ietf.org adslmib-admin@ Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL ietf.org draf t)? 16/01/03 09:05 Hi, The purpose of adslLineSpecific, as I understand it, is to behave as a hook for any vendor specific MIB extension. Such an extension can ALSO be used for providing the type of information you mention but it's its main purpose. Best regards, Moti Morgenstern Senior System Engineer Inovia Telecoms Ltd. Member of the ECI Telecom group 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 e-mail: Moti.Morgenstern@inoviatele.com "El Houmaidi, Mounire" To: "'adslmib@ ietf.org'" t)? Sent by: adslmib-admin@ ietf.org 15/01/03 20:22 Hello To all, In RFC 2662 (ADSL), adslLineSpecific under the adslLineTable may be used to determine shelf/slot/port of the ATUC interface in a DSLAM. This mapping is important for mapping an IfIndex to a Physical interface (depending on implementation) in the entity Physical Table (RFC 2737) or to an enterprise Table containing the Physical entities. we don't see that mapping done in RFC 3276 (SHDSL) or VDSL draft. How can we provide the same feature for SHDSL and VDSL? Regards Mounire El Houmaidi Siemens ICN,Lake Mary , Florida _______________________________________________ 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 _______________________________________________ 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 mailnull@www1.ietf.org Thu Jan 16 12:19:29 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16689 for ; Thu, 16 Jan 2003 12:19:29 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0GHYel06764 for adslmib-archive@odin.ietf.org; Thu, 16 Jan 2003 12:34:40 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GHYdJ06761 for ; Thu, 16 Jan 2003 12:34:39 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16664 for ; Thu, 16 Jan 2003 12:18:57 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GHYQJ06745; Thu, 16 Jan 2003 12:34:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GHXKJ06683 for ; Thu, 16 Jan 2003 12:33:20 -0500 Received: from mail.hiwaay.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16654; Thu, 16 Jan 2003 12:17:37 -0500 (EST) Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.6/8.12.6) with ESMTP id h0GHKu9M394012; Thu, 16 Jan 2003 11:20:57 -0600 (CST) Received: from rray ([192.168.0.199]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.5.2.R); Thu, 16 Jan 2003 11:20:55 -0600 From: "Bob Ray" To: , "El Houmaidi, Mounire" Cc: , Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? Date: Thu, 16 Jan 2003 11:19:06 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-MDRemoteIP: 192.168.0.199 X-Return-Path: rray@pesa.com 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: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Please read RFC2863. Regards, Bob Ray -----Original Message----- From: adslmib-admin@ietf.org [mailto:adslmib-admin@ietf.org]On Behalf Of Moti.Morgenstern@inoviatele.com Sent: Thursday, January 16, 2003 10:15 AM To: El Houmaidi, Mounire Cc: adslmib@ietf.org; adslmib-admin@ietf.org Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? Mounire, As long as the index/key to the proprietary MIB extension is the (same) one used by the IETF MIB I believe you don't really need an explicit "pointer" from within the VDSL/SHDSL MIBs to that proprietary MIB. However, it will be interesting to hear other opinions on this issue. Moti "El Houmaidi, Mounire" To: "'Moti.Morgenstern@inoviatele.com'" , Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? 16/01/03 17:48 Moti, I want to thank you for taking your time to answer our question. The use of the object is understood and i agree with you. My question is about the Other MIBS, SHDSL (RFC 3276) and VDSL draft: where such Object/feature (a hook to a specific MIB as you called it) is implemented in those MIBs? Mounire -----Original Message----- From: Moti.Morgenstern@inoviatele.com [mailto:Moti.Morgenstern@inoviatele.com] Sent: Thursday, January 16, 2003 8:14 AM To: adslmib@ietf.org; adslmib-admin@ietf.org; El Houmaidi, Mounire Cc: Moti.Morgenstern@inoviatele.com Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL draf t)? Mounire, I'm sorry for omitting an important word in the last sentence: The proprietary extension can ALSO be used for providing the type of information you mention but it's NOT its main purpose. Moti Moti.Morgenstern @inoviatele.com To: "El Houmaidi, Mounire" Sent by: cc: adslmib@ietf.org, adslmib-admin@ietf.org adslmib-admin@ Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL ietf.org draf t)? 16/01/03 09:05 Hi, The purpose of adslLineSpecific, as I understand it, is to behave as a hook for any vendor specific MIB extension. Such an extension can ALSO be used for providing the type of information you mention but it's its main purpose. Best regards, Moti Morgenstern Senior System Engineer Inovia Telecoms Ltd. Member of the ECI Telecom group 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 e-mail: Moti.Morgenstern@inoviatele.com "El Houmaidi, Mounire" To: "'adslmib@ ietf.org'" t)? Sent by: adslmib-admin@ ietf.org 15/01/03 20:22 Hello To all, In RFC 2662 (ADSL), adslLineSpecific under the adslLineTable may be used to determine shelf/slot/port of the ATUC interface in a DSLAM. This mapping is important for mapping an IfIndex to a Physical interface (depending on implementation) in the entity Physical Table (RFC 2737) or to an enterprise Table containing the Physical entities. we don't see that mapping done in RFC 3276 (SHDSL) or VDSL draft. How can we provide the same feature for SHDSL and VDSL? Regards Mounire El Houmaidi Siemens ICN,Lake Mary , Florida _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Thu Jan 16 12:57:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18258 for ; Thu, 16 Jan 2003 12:57:09 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0GICJR10472 for adslmib-archive@odin.ietf.org; Thu, 16 Jan 2003 13:12:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GICJJ10469 for ; Thu, 16 Jan 2003 13:12:19 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18231 for ; Thu, 16 Jan 2003 12:56:36 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GIC3J10418; Thu, 16 Jan 2003 13:12:03 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GIB8J10380 for ; Thu, 16 Jan 2003 13:11:08 -0500 Received: from lmmx1.fl.icn.siemens.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18147; Thu, 16 Jan 2003 12:55:25 -0500 (EST) Received: from stca200a.bus.sc.rolm.com (stca200a.bus.sc.rolm.com [165.218.68.180]) by lmmx1.fl.icn.siemens.com (8.9.3/8.9.3) with ESMTP id MAA02035; Thu, 16 Jan 2003 12:58:42 -0500 (EST) Received: by stca200a.bus.sc.rolm.com with Internet Mail Service (5.5.2653.19) id ; Thu, 16 Jan 2003 09:58:42 -0800 Message-ID: From: "El Houmaidi, Mounire" To: "'Bob Ray'" , Moti.Morgenstern@inoviatele.com Cc: adslmib@ietf.org, adslmib-admin@ietf.org Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draft)? Date: Thu, 16 Jan 2003 09:58:34 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) 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: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Hello to All, I remember a long discussion about xDSL Profile indexing (integer versus String) and the discussion came down to preserving consistency between xDSL Mibs: This is a similar issue: The ADSL Mib (2662) provides a mapping object (adslLineSpecific); so SHDSL, VDSL should follow the same spirit. We can't tell our customers we do it this way with ADSL but SHDSL and VDSL we don't. That's the message I am trying to pass to every one. How RFC 2863 will solve such inconsistency? Regards Mounire EL Houmaidi -----Original Message----- From: Bob Ray [mailto:rray@pesa.com] Sent: Thursday, January 16, 2003 12:19 PM To: Moti.Morgenstern@inoviatele.com; El Houmaidi, Mounire Cc: adslmib@ietf.org; adslmib-admin@ietf.org Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? Please read RFC2863. Regards, Bob Ray -----Original Message----- From: adslmib-admin@ietf.org [mailto:adslmib-admin@ietf.org]On Behalf Of Moti.Morgenstern@inoviatele.com Sent: Thursday, January 16, 2003 10:15 AM To: El Houmaidi, Mounire Cc: adslmib@ietf.org; adslmib-admin@ietf.org Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? Mounire, As long as the index/key to the proprietary MIB extension is the (same) one used by the IETF MIB I believe you don't really need an explicit "pointer" from within the VDSL/SHDSL MIBs to that proprietary MIB. However, it will be interesting to hear other opinions on this issue. Moti "El Houmaidi, Mounire" To: "'Moti.Morgenstern@inoviatele.com'" , Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VD SL draf t)? 16/01/03 17:48 Moti, I want to thank you for taking your time to answer our question. The use of the object is understood and i agree with you. My question is about the Other MIBS, SHDSL (RFC 3276) and VDSL draft: where such Object/feature (a hook to a specific MIB as you called it) is implemented in those MIBs? Mounire -----Original Message----- From: Moti.Morgenstern@inoviatele.com [mailto:Moti.Morgenstern@inoviatele.com] Sent: Thursday, January 16, 2003 8:14 AM To: adslmib@ietf.org; adslmib-admin@ietf.org; El Houmaidi, Mounire Cc: Moti.Morgenstern@inoviatele.com Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL draf t)? Mounire, I'm sorry for omitting an important word in the last sentence: The proprietary extension can ALSO be used for providing the type of information you mention but it's NOT its main purpose. Moti Moti.Morgenstern @inoviatele.com To: "El Houmaidi, Mounire" Sent by: cc: adslmib@ietf.org, adslmib-admin@ietf.org adslmib-admin@ Subject: Re: [Adslmib] IfIndex mapping to Physical entity index ( RFC 3276 and VDSL ietf.org draf t)? 16/01/03 09:05 Hi, The purpose of adslLineSpecific, as I understand it, is to behave as a hook for any vendor specific MIB extension. Such an extension can ALSO be used for providing the type of information you mention but it's its main purpose. Best regards, Moti Morgenstern Senior System Engineer Inovia Telecoms Ltd. Member of the ECI Telecom group 30 Hasivim St. Petach Tikva, Israel 49133 Tel.: +972-3-9266258 Fax: +972-3-9268182 e-mail: Moti.Morgenstern@inoviatele.com "El Houmaidi, Mounire" To: "'adslmib@ ietf.org'" t)? Sent by: adslmib-admin@ ietf.org 15/01/03 20:22 Hello To all, In RFC 2662 (ADSL), adslLineSpecific under the adslLineTable may be used to determine shelf/slot/port of the ATUC interface in a DSLAM. This mapping is important for mapping an IfIndex to a Physical interface (depending on implementation) in the entity Physical Table (RFC 2737) or to an enterprise Table containing the Physical entities. we don't see that mapping done in RFC 3276 (SHDSL) or VDSL draft. How can we provide the same feature for SHDSL and VDSL? Regards Mounire El Houmaidi Siemens ICN,Lake Mary , Florida _______________________________________________ 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 _______________________________________________ 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 _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib From mailnull@www1.ietf.org Thu Jan 16 14:11:17 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21059 for ; Thu, 16 Jan 2003 14:11:16 -0500 (EST) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h0GJQUq16097 for adslmib-archive@odin.ietf.org; Thu, 16 Jan 2003 14:26:30 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GJQUJ16090 for ; Thu, 16 Jan 2003 14:26:30 -0500 Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21035 for ; Thu, 16 Jan 2003 14:10:45 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GJQNJ16078; Thu, 16 Jan 2003 14:26:23 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h0GJPqJ16035 for ; Thu, 16 Jan 2003 14:25:52 -0500 Received: from mail.hiwaay.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21015; Thu, 16 Jan 2003 14:10:06 -0500 (EST) Received: from mailserver ([216.180.38.253]) by mail.hiwaay.net (8.12.6/8.12.6) with ESMTP id h0GJDR9M452238; Thu, 16 Jan 2003 13:13:27 -0600 (CST) Received: from rray ([192.168.0.199]) by pesahsv.com ([127.0.0.1]) with SMTP (MDaemon.PRO.v6.5.2.R); Thu, 16 Jan 2003 13:13:25 -0600 From: "Bob Ray" To: "El Houmaidi, Mounire" , Cc: , Subject: RE: [Adslmib] IfIndex mapping to Physical index ( RFC 3276 and VDSL draft)? Date: Thu, 16 Jan 2003 13:11:35 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 In-Reply-To: X-MDRemoteIP: 192.168.0.199 X-Return-Path: rray@pesa.com 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: , List-Id: ADSLMIB List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Mounire EL Houmaidi writes: >This is a similar issue: The ADSL Mib (2662) provides a mapping object >(adslLineSpecific); so SHDSL, VDSL should follow the same spirit. We can't >tell our customers we do it this way with ADSL but SHDSL and VDSL we don't. I suggest you tell them, "One of the editors is an aging irritable goat". Follow this declaration with a mildly theatric shrug. :) >How RFC 2863 will solve such inconsistency? By keeping proprietary grouping mechanisms out of MIBs... One might ask: if we put an explicit unbundling mechanism in a MIB (to map shelf/slot/device-in-slot to ifIndex), what happens when someone has a grouping we didn't predict (say, t3 over gigabit ethernet) but they still want to use standard MIBs? Do we say, "Sorry, but the spirit of our work precludes that!"? Of course not. How about if we don't put a defined mechanism in a MIB, but just put a big hole that some can exploit (i.e. a "proprietary hooks go here" object)? Will all vendors implement THAT field the same way? Of course not. The next question is if a field is proprietary, and hence its usage cannot be standardized, what is it doing in a supposedly standard MIB? ------ The following does not presume to represent the opinions of anyone other than myself. ------ When SNMPv1 erupted, most managed telecommunications equipment was rack based. Some vendors supported the standard MIBs by using community string to convey shelf/slot/device information to/from an agent. Other vendors created proprietary versions of the standard MIBs by adding shelf/slot/device indices to the MIB tables (along with other transforms). Then some clever people noted that they could read the community strings with packet sniffers and hence control the networked equipment. This concern over security led directly to SNMPv2. The vendors who used community strings to convey indices couldn't support SNMPv2 because the community string disappeared (as plaintext passwords should). This led to SNMPv2c, which restored plaintext community strings and allowed the indices-in-community-string vendors to keep trudging along proclaiming compliance with standard MIBs. The plaintext 'password' was available to anyone with a packet sniffer. So... there was still the need to secure access to these devices (i.e. get rid of the plaintext). Enter SNMPv3. There was still the need to support mapping standard MIBs to ifIndex. Enter RFC2863. Also note that 2863 is greater than 2662 yet strangely smaller than 3276. :) Regards, Bob Ray Those who cannot remember the past are condemned to repeat it. George Santayana _______________________________________________ Adslmib mailing list Adslmib@ietf.org https://www1.ietf.org/mailman/listinfo/adslmib