From isis-wg-bounces@ietf.org Tue Jul 6 18:45:44 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00708 for ; Tue, 6 Jul 2004 18:45:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BhwIb-0001NK-FX; Tue, 06 Jul 2004 16:12:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bhvku-0002D6-TM; Tue, 06 Jul 2004 15:37:28 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16526; Tue, 6 Jul 2004 15:37:26 -0400 (EDT) Message-Id: <200407061937.PAA16526@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 06 Jul 2004 15:37:26 -0400 Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-mib-16.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : Management Information Base for IS-IS Author(s) : J. Parker Filename : draft-ietf-isis-wg-mib-16.txt Pages : 90 Date : 2004-7-6 This document describes a management information base for the IS-IS Routing protocol, as described in ISO 10589 [2], when it is used to construct routing tables for IP networks, as described in RFC 1195 [RFC1195]. This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo is based on an IETF draft by Chris Gunner [1]. This version has been modified to include MIB-II syntax, to exclude portions of the protocol that are not relevant to IP, such as the ES-IS protocol, and to add management support for current practice. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-mib-16.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-isis-wg-mib-16.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-isis-wg-mib-16.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: <2004-7-6152017.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-wg-mib-16.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-wg-mib-16.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-7-6152017.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Wed Jul 7 16:55:55 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16821 for ; Wed, 7 Jul 2004 16:55:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiIib-0004RQ-N2; Wed, 07 Jul 2004 16:08:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiIIh-0005eN-VS for isis-wg@megatron.ietf.org; Wed, 07 Jul 2004 15:41:52 -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 PAA13120 for ; Wed, 7 Jul 2004 15:41:49 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BiIIg-0001ks-TU for isis-wg@ietf.org; Wed, 07 Jul 2004 15:41:50 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiIHn-0001Ns-00 for isis-wg@ietf.org; Wed, 07 Jul 2004 15:40:56 -0400 Received: from mx4.broadwing.com ([216.140.57.248] helo=ausspam02.ixc-comm.com) by ietf-mx with esmtp (Exim 4.12) id 1BiIH1-0000za-00; Wed, 07 Jul 2004 15:40:07 -0400 Received: from mail pickup service by ausspam02.ixc-comm.com with Microsoft SMTPSVC; Wed, 7 Jul 2004 13:24:20 -0500 Received: from megatron.ietf.org ([132.151.6.71]) by ausspam02.ixc-comm.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 6 Jul 2004 18:16:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BhwIe-0001P4-PD; Tue, 06 Jul 2004 16:12:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bhvku-0002D6-TM; Tue, 06 Jul 2004 15:37:28 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16526; Tue, 6 Jul 2004 15:37:26 -0400 (EDT) Message-Id: <200407061937.PAA16526@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 06 Jul 2004 15:37:26 -0400 X-BeenThere: i-d-announce@ietf.org X-Mailman-Version: 2.1.5 Precedence: list X-OriginalArrivalTime: 06 Jul 2004 23:16:47.0578 (UTC) FILETIME=[4F66CBA0:01C463AF] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60 Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-mib-16.txt X-BeenThere: isis-wg@ietf.org Reply-To: internet-drafts@ietf.org List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : Management Information Base for IS-IS Author(s) : J. Parker Filename : draft-ietf-isis-wg-mib-16.txt Pages : 90 Date : 2004-7-6 This document describes a management information base for the IS-IS Routing protocol, as described in ISO 10589 [2], when it is used to construct routing tables for IP networks, as described in RFC 1195 [RFC1195]. This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo is based on an IETF draft by Chris Gunner [1]. This version has been modified to include MIB-II syntax, to exclude portions of the protocol that are not relevant to IP, such as the ES-IS protocol, and to add management support for current practice. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-mib-16.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-isis-wg-mib-16.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-isis-wg-mib-16.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: <2004-7-6152017.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-wg-mib-16.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-wg-mib-16.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-7-6152017.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Thu Jul 8 14:53:18 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17701 for ; Thu, 8 Jul 2004 14:53:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Biawv-0003CC-Pf; Thu, 08 Jul 2004 11:36:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Biad9-0004pl-CA; Thu, 08 Jul 2004 11:16:11 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00173; Thu, 8 Jul 2004 11:16:08 -0400 (EDT) Message-Id: <200407081516.LAA00173@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 08 Jul 2004 11:16:08 -0400 Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-mib-16.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : Management Information Base for IS-IS Author(s) : J. Parker Filename : draft-ietf-isis-wg-mib-16.txt Pages : 90 Date : 2004-7-6 This document describes a management information base for the IS-IS Routing protocol, as described in ISO 10589 [2], when it is used to construct routing tables for IP networks, as described in RFC 1195 [RFC1195]. This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo is based on an IETF draft by Chris Gunner [1]. This version has been modified to include MIB-II syntax, to exclude portions of the protocol that are not relevant to IP, such as the ES-IS protocol, and to add management support for current practice. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-mib-16.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-isis-wg-mib-16.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-isis-wg-mib-16.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: <2004-7-6152017.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-wg-mib-16.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-wg-mib-16.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-7-6152017.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Thu Jul 8 20:38:09 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18192 for ; Thu, 8 Jul 2004 20:38:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BiiYm-0001jy-W3; Thu, 08 Jul 2004 19:44:12 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bigie-0005tX-Pn for isis-wg@megatron.ietf.org; Thu, 08 Jul 2004 17:46:16 -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 RAA03987 for ; Thu, 8 Jul 2004 17:46:09 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BigiY-0005OZ-7s for isis-wg@ietf.org; Thu, 08 Jul 2004 17:46:10 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BiggQ-0004fr-00 for isis-wg@ietf.org; Thu, 08 Jul 2004 17:43:59 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1Bigfc-00040O-00; Thu, 08 Jul 2004 17:43:08 -0400 Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i68LgCJ00314; Thu, 8 Jul 2004 14:42:12 -0700 (PDT) Message-Id: <200407082142.i68LgCJ00314@boreas.isi.edu> To: ietf-announce@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 08 Jul 2004 14:42:11 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-8.9 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 Cc: isis-wg@ietf.org, rfc-editor@rfc-editor.org Subject: [Isis-wg] RFC 3847 on Restart Signaling for Intermediate System to Intermediate System (IS-IS) X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3847 Title: Restart Signaling for Intermediate System to Intermediate System (IS-IS) Author(s): M. Shand, L. Ginsberg Status: Informational Date: July 2004 Mailbox: mshand@cisco.com, ginsberg@cisco.com Pages: 21 Characters: 50023 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-restart-05.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3847.txt This document describes a mechanism for a restarting router to signal to its neighbors that it is restarting, allowing them to reestablish their adjacencies without cycling through the down state, while still correctly initiating database synchronization. This document additionally describes a mechanism for a restarting router to determine when it has achieved LSP database synchronization with its neighbors and a mechanism to optimize LSP database synchronization, while minimizing transient routing disruption when a router starts. This document is a product of the IS-IS for IP Internets Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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: <040708144044.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3847 --OtherAccess Content-Type: Message/External-body; name="rfc3847.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040708144044.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Fri Jul 9 06:46:18 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16835 for ; Fri, 9 Jul 2004 06:46:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bisa0-0008Po-0f; Fri, 09 Jul 2004 06:26:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BisCA-0004BD-7r for isis-wg@megatron.ietf.org; Fri, 09 Jul 2004 06:01: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 GAA14596 for ; Fri, 9 Jul 2004 06:01:22 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BisC2-0003a7-RG for isis-wg@ietf.org; Fri, 09 Jul 2004 06:01:22 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BisB6-0003HV-00 for isis-wg@ietf.org; Fri, 09 Jul 2004 06:00:25 -0400 Received: from smtp2.dataconnection.com ([192.91.191.8] helo=smtp2.datcon.co.uk) by ietf-mx with esmtp (Exim 4.12) id 1BisAE-0002iQ-00 for isis-wg@ietf.org; Fri, 09 Jul 2004 05:59:30 -0400 Received: by beiderbecke.datcon.co.uk with Internet Mail Service (5.5.2653.19) id ; Fri, 9 Jul 2004 10:58:58 +0100 Message-ID: <37701240971DD31193970000F6CCB9F7050423E4@duke.datcon.co.uk> From: Jonathan Harrison To: isis-wg@ietf.org Date: Fri, 9 Jul 2004 10:58:59 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01C4659B.5B0BA9A6" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Subject: [Isis-wg] FW: I-D ACTION:draft-harrison-isis-ipv6-te-00.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01C4659B.5B0BA9A6 Content-Type: text/plain; charset="iso-8859-1" We've just submitted this draft on adding IPv6 TE support to IS-IS. We'd be interested to hear any comments from the IS-IS WG. Thanks, Jon ------------------------------------------- Jon Harrison Network Protocols Group Data Connection Ltd Tel: +44 20 8366 1177 Fax: +44 20 8363 1039 Email: jrh@dataconnection.com Web: http://www.dataconnection.com -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org]On Behalf Of Internet-Drafts@ietf.org Sent: 06 July 2004 20:37 To: i-d-announce@ietf.org Subject: I-D ACTION:draft-harrison-isis-ipv6-te-00.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IPv6 Traffic Engineering in IS-IS Author(s) : J. Harrison, et al. Filename : draft-harrison-isis-ipv6-te-00.txt Pages : 10 Date : 2004-7-6 This draft specifies a method for exchanging IPv6 Traffic Engineering information using the IS-IS routing protocol. The described method uses three new TLVs, together with 2 new sub-TLVs of the Extended IS Reachability TLV. The information distributed allows a CSPF algorithm to calculate traffic engineered routes using IPv6 addresses. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-harrison-isis-ipv6-te-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-harrison-isis-ipv6-te-00.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-harrison-isis-ipv6-te-00.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_000_01C4659B.5B0BA9A6 Content-Type: message/rfc822 To: Subject: Date: Fri, 9 Jul 2004 10:58:58 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/mixed; boundary="----_=_NextPart_002_01C4659B.5B0BA9A6" ------_=_NextPart_002_01C4659B.5B0BA9A6 Content-Type: text/plain ------_=_NextPart_002_01C4659B.5B0BA9A6 Content-Type: application/octet-stream; name="ATT36491" Content-Disposition: attachment; filename="ATT36491" Content-type: message/external-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-7-6151938.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-harrison-isis-ipv6-te-00.txt ------_=_NextPart_002_01C4659B.5B0BA9A6 Content-Type: message/external-body; site="internet-drafts"; dir="draft-harrison-isis-ipv6-te-00.txt"; mode="ftp.ietf.org"; access-type="anon-ftp" ------_=_NextPart_002_01C4659B.5B0BA9A6-- ------_=_NextPart_000_01C4659B.5B0BA9A6 Content-Type: text/plain; name="ATT364917.txt" Content-Disposition: attachment; filename="ATT364917.txt" _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce ------_=_NextPart_000_01C4659B.5B0BA9A6 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg ------_=_NextPart_000_01C4659B.5B0BA9A6-- From isis-wg-bounces@ietf.org Fri Jul 9 19:53:30 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14325 for ; Fri, 9 Jul 2004 19:53:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bj1k0-0004kx-MS; Fri, 09 Jul 2004 16:13:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bj18w-00026p-E8; Fri, 09 Jul 2004 15:34:46 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24334; Fri, 9 Jul 2004 15:34:43 -0400 (EDT) Message-Id: <200407091934.PAA24334@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Fri, 09 Jul 2004 15:34:43 -0400 Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-igp-p2p-over-lan-04.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : Point-to-point operation over LAN in link-state routing protocols Author(s) : N. Shen, A. Zinin Filename : draft-ietf-isis-igp-p2p-over-lan-04.txt Pages : 9 Date : 2004-7-9 The two predominant circuit types used by link state routing protocols are point-to-point and broadcast. It is important to identify the correct circuit type when forming adjacencies, flooding link state database packets, and representing the circuit topologically. This document describes a simple mechanism to treat the broadcast network as a point-to-point connection from the standpoint of IP routing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-igp-p2p-over-lan-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-isis-igp-p2p-over-lan-04.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-isis-igp-p2p-over-lan-04.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: <2004-7-9154931.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-igp-p2p-over-lan-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-igp-p2p-over-lan-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-7-9154931.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Tue Jul 13 21:26:44 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21752 for ; Tue, 13 Jul 2004 21:26:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkV0Z-0004SL-Bh; Tue, 13 Jul 2004 17:40:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkTTU-0002Ed-NY; Tue, 13 Jul 2004 16:02:00 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10126; Tue, 13 Jul 2004 16:01:58 -0400 (EDT) Message-Id: <200407132001.QAA10126@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 13 Jul 2004 16:01:58 -0400 Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-admin-tags-02.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : A Policy Control Mechanism is IS-IS Using Administrative Tags Author(s) : C. Martin, et al. Filename : draft-ietf-isis-admin-tags-02.txt Pages : 6 Date : 2004-7-13 This document describes an extension to the IS-IS protocol to add operational capabilities that allow for ease of management and control over IP prefix distribution within an IS-IS domain. This document enhances the IS-IS protocol by extending the information that a Intermediate System (IS) [router] can place in Link State Protocol Data Units (LSPs) for policy use. This extension will provide operators with a mechanism to control IP prefix distribution throughout multi-level IS-IS domains. Additionally, the information can be placed in LSPs that have TLVs as yet undefined, if this information is used to convey the same meaning in these future TLVs as it is used in the currently defined TLVs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-admin-tags-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-isis-admin-tags-02.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-isis-admin-tags-02.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: <2004-7-13145135.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-admin-tags-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-admin-tags-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-7-13145135.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Wed Jul 14 10:13:39 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18697 for ; Wed, 14 Jul 2004 10:13:39 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkkIq-0005Nu-U6; Wed, 14 Jul 2004 10:00:08 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkkEB-0003uU-V2 for isis-wg@megatron.ietf.org; Wed, 14 Jul 2004 09:55:19 -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 JAA17248 for ; Wed, 14 Jul 2004 09:55:17 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkkEB-0007DC-4O for isis-wg@ietf.org; Wed, 14 Jul 2004 09:55:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkkDG-0006t4-00 for isis-wg@ietf.org; Wed, 14 Jul 2004 09:54:23 -0400 Received: from westford-nat.juniper.net ([65.194.140.2] helo=pi-smtp.jnpr.net) by ietf-mx with esmtp (Exim 4.12) id 1BkkCQ-0006FN-00 for isis-wg@ietf.org; Wed, 14 Jul 2004 09:53:30 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: FW: [Isis-wg] I-D ACTION:draft-ietf-isis-admin-tags-02.txt Date: Wed, 14 Jul 2004 09:52:59 -0400 Message-ID: <98F04BA831360C4FB5F7FC0118D91828034A291D@pi.jnpr.net> Thread-Topic: [Isis-wg] I-D ACTION:draft-ietf-isis-admin-tags-02.txt thread-index: AcRpQcbYsj/zdP9RQu6vqVKgERkTnwAZ0q0AAAAYMDA= From: "Jeelani Syed" To: X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Content-Transfer-Encoding: quoted-printable There is a typo in section 5.2 the sub tlv type value should be 2 instead of 1 -jeelani.sm -----Original Message----- From: isis-wg-bounces@ietf.org [mailto:isis-wg-bounces@ietf.org]On Behalf Of Internet-Drafts@ietf.org Sent: Tuesday, July 13, 2004 4:02 PM To: i-d-announce@ietf.org Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-admin-tags-02.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : A Policy Control Mechanism is IS-IS Using Administrative Tags Author(s) : C. Martin, et al. Filename : draft-ietf-isis-admin-tags-02.txt Pages : 6 Date : 2004-7-13 =09 This document describes an extension to the IS-IS protocol to add operational capabilities that allow for ease of management and control over IP prefix distribution within an IS-IS domain. =20 This document enhances the IS-IS protocol by extending the information that a Intermediate System (IS) [router] can place in Link State Protocol Data Units (LSPs) for policy use. This extension will provide operators with a mechanism to control IP prefix distribution throughout multi-level IS-IS domains. Additionally, the information can be placed in LSPs that have TLVs as yet undefined, if this information is used to convey the same meaning in these future TLVs as it is used in the currently defined TLVs. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-admin-tags-02.txt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. =20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. 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-isis-admin-tags-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 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-isis-admin-tags-02.txt". =09 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. =09 =09 Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Jul 14 18:56:59 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA05550 for ; Wed, 14 Jul 2004 18:56:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkqYk-0002rD-7c; Wed, 14 Jul 2004 16:40:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bkpaz-0007MX-S1; Wed, 14 Jul 2004 15:39:13 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10907; Wed, 14 Jul 2004 15:39:11 -0400 (EDT) Message-Id: <200407141939.PAA10907@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Wed, 14 Jul 2004 15:39:11 -0400 Cc: isis-wg@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-igp-p2p-over-lan-05.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : Point-to-point operation over LAN in link-state routing protocols Author(s) : N. Shen, A. Zinin Filename : draft-ietf-isis-igp-p2p-over-lan-05.txt Pages : 9 Date : 2004-7-14 The two predominant circuit types used by link state routing protocols are point-to-point and broadcast. It is important to identify the correct circuit type when forming adjacencies, flooding link state database packets, and representing the circuit topologically. This document describes a simple mechanism to treat the broadcast network as a point-to-point connection from the standpoint of IP routing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-igp-p2p-over-lan-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. 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-isis-igp-p2p-over-lan-05.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-isis-igp-p2p-over-lan-05.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: <2004-7-14154149.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-igp-p2p-over-lan-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-igp-p2p-over-lan-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-7-14154149.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Wed Jul 14 20:01:08 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA12826 for ; Wed, 14 Jul 2004 20:01:08 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BktJn-0006op-H5; Wed, 14 Jul 2004 19:37:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkqpG-0007h3-NN for isis-wg@megatron.ietf.org; Wed, 14 Jul 2004 16:58: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 QAA20056 for ; Wed, 14 Jul 2004 16:58:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkqpF-0001hu-9F for isis-wg@ietf.org; Wed, 14 Jul 2004 16:58:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1Bkqfi-0007Li-00 for isis-wg@ietf.org; Wed, 14 Jul 2004 16:48:11 -0400 Received: from adsl-66-120-207-101.dsl.sntc01.pacbell.net ([66.120.207.101] helo=coffee.rawdofmt.org) by ietf-mx with esmtp (Exim 4.12) id 1BkqVJ-0004yE-00 for isis-wg@ietf.org; Wed, 14 Jul 2004 16:37:25 -0400 Received: from [IPv6:::1] (localhost [127.0.0.1]) by coffee.rawdofmt.org (Postfix) with ESMTP id 7D37A3DCC8C for ; Wed, 14 Jul 2004 13:36:40 -0700 (PDT) Mime-Version: 1.0 (Apple Message framework v618) Content-Transfer-Encoding: 7bit Message-Id: <895C2949-D5D5-11D8-94B5-00039303E9E2@rawdofmt.org> Content-Type: text/plain; charset=US-ASCII; format=flowed To: ISIS-WG (E-mail) From: Christian Hopps Date: Wed, 14 Jul 2004 13:36:51 -0700 X-Mailer: Apple Mail (2.618) X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Draft Agenda for IETF 60 X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Content-Transfer-Encoding: 7bit Here is the draft agenda. The entire 2 hours has been allocated, but let us know if you think something is missing and we'll try and work it in. Chris. Wednesday, August 4th, 2004 1530-1730 5 min Agenda Bashing 5 min Document Status WG chairs 10 min ITU Liason Statement Jonathan Sadler 5 min draft-ietf-isis-wg-mib-16.txt Jeff Parker (Uncomfirmed) 5 min draft-ietf-isis-experimental-tlv-03.txt Christian Hopps 10 min draft-ietf-isis-igp-p2p-over-lan-04.txt Naiming Shen 10 min draft-ietf-isis-wg-multi-topology-07.txt Naiming Shen 10 min draft-ietf-isis-admin-tags-03.txt Stefano Previd 10 min draft-harrison-isis-ipv6-te-00.txt Jon Berger 10 min draft-vasseur-isis-caps-00.txt Jean Philippe Vasseur 5 min draft-vasseur-isis-te-caps-00.txt Jean Philippe Vasseur 5 min draft-vasseur-isis-link-attr-01.txt Stefano Previd 10 min draft-shen-isis-interarea-route-attr-00.txt Naiming Shen 10 min draft-shen-isis-extended-tlv-00.txt Naiming Shen 10 min Future Direction WG chairs _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Jul 15 20:30:56 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA21972 for ; Thu, 15 Jul 2004 20:30:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BlGYf-0006gJ-Lr; Thu, 15 Jul 2004 20:26:37 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BlGVn-0005pd-8J for isis-wg@megatron.ietf.org; Thu, 15 Jul 2004 20:23:39 -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 UAA21574 for ; Thu, 15 Jul 2004 20:23:36 -0400 (EDT) From: jcucchiara@mindspring.com Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BlGVl-000570-2u for isis-wg@ietf.org; Thu, 15 Jul 2004 20:23:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BlGV2-0004nN-00 for isis-wg@ietf.org; Thu, 15 Jul 2004 20:22:53 -0400 Received: from hall.mail.mindspring.net ([207.69.200.60]) by ietf-mx with esmtp (Exim 4.12) id 1BlGUF-0004SB-00 for isis-wg@ietf.org; Thu, 15 Jul 2004 20:22:03 -0400 Received: from h-66-167-175-160.cmbrmaor.dynamic.covad.net ([66.167.175.160] helo=jluciani-laptop) by hall.mail.mindspring.net with smtp (Exim 3.33 #1) id 1BlGUF-0001YH-00; Thu, 15 Jul 2004 20:22:03 -0400 Message-Id: <3.0.1.32.20040715203000.012b03fc@pop.mindspring.com> X-Sender: jcucchiara@pop.mindspring.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 15 Jul 2004 20:30:00 -0400 To: isis-wg@ietf.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL, NO_REAL_NAME autolearn=no version=2.60 Cc: jparker@axiowave.com Subject: [Isis-wg] smicng output for draft-ietf-isis-wg-mib-16.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Hi Jeff, The following is the smicng MIB compiler output for version 16 of the MIB. smicng has the flags specified by the mibtools (see http://www.ops.ietf.org/mib-review-tools.html for more details the flags). Are these going to be fixed in the next version of the MIB? thanks, -Joan >W: f(ISIS-MIB), (3118,13) Variable "isisSysLevelIndex" in notification >"isisDatabaseOverload" is an index for a table >E: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification >"isisManualAddressDrops" has access of "not-accessible" >W: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification >"isisManualAddressDrops" is an index for a table >W: f(ISIS-MIB), (3152,13) Variable "isisSysLevelIndex" in notification >"isisCorruptedLSPDetected" is an index for a table >W: f(ISIS-MIB), (3171,13) Variable "isisSysLevelIndex" in notification >"isisAttemptToExceedMaxSequence" is an index for a table >W: f(ISIS-MIB), (3190,13) Variable "isisSysLevelIndex" in notification >"isisIDLenMismatch" is an index for a table >W: f(ISIS-MIB), (3212,13) Variable "isisSysLevelIndex" in notification >"isisMaxAreaAddressesMismatch" is an index for a table >W: f(ISIS-MIB), (3234,13) Variable "isisSysLevelIndex" in notification >"isisOwnLSPPurge" is an index for a table >W: f(ISIS-MIB), (3251,13) Variable "isisSysLevelIndex" in notification >"isisSequenceNumberSkip" is an index for a table >W: f(ISIS-MIB), (3270,13) Variable "isisSysLevelIndex" in notification >"isisAuthenticationTypeFailure" is an index for a table >W: f(ISIS-MIB), (3290,13) Variable "isisSysLevelIndex" in notification >"isisAuthenticationFailure" is an index for a table >W: f(ISIS-MIB), (3309,13) Variable "isisSysLevelIndex" in notification >"isisVersionSkew" is an index for a table >W: f(ISIS-MIB), (3351,13) Variable "isisSysLevelIndex" in notification >"isisRejectedAdjacency" is an index for a table >W: f(ISIS-MIB), (3369,13) Variable "isisSysLevelIndex" in notification >"isisLSPTooLargeToPropagate" is an index for a table >W: f(ISIS-MIB), (3387,13) Variable "isisSysLevelIndex" in notification >"isisOrigLSPBuffSizeMismatch" is an index for a table >W: f(ISIS-MIB), (3411,13) Variable "isisSysLevelIndex" in notification >"isisProtocolsSupportedMismatch" is an index for a table >W: f(ISIS-MIB), (3436,13) Variable "isisSysLevelIndex" in notification >"isisAdjacencyChange" is an index for a table >W: f(ISIS-MIB), (3453,13) Variable "isisSysLevelIndex" in notification >"isisLSPErrorDetected" is an index for a table > >*** 1 error and 17 warnings in parsing > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Fri Jul 16 21:54:00 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27133 for ; Fri, 16 Jul 2004 21:54:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BleMC-00063g-2l; Fri, 16 Jul 2004 21:51:20 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BleKV-0005o4-Jw for isis-wg@megatron.ietf.org; Fri, 16 Jul 2004 21:49: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 VAA26723 for ; Fri, 16 Jul 2004 21:49:34 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BleKR-0000fI-Qo for isis-wg@ietf.org; Fri, 16 Jul 2004 21:49:31 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BleJR-0000KO-00 for isis-wg@ietf.org; Fri, 16 Jul 2004 21:48:30 -0400 Received: from natint2.juniper.net ([207.17.136.150] helo=kummer.juniper.net) by ietf-mx with esmtp (Exim 4.12) id 1BleIT-0007VQ-00 for isis-wg@ietf.org; Fri, 16 Jul 2004 21:47:29 -0400 Received: from kummer.juniper.net (localhost [127.0.0.1]) by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id i6H1kh0g025417; Fri, 16 Jul 2004 18:46:43 -0700 (PDT) (envelope-from kireeti@juniper.net) Received: from localhost (kireeti@localhost) by kummer.juniper.net (8.12.8p1/8.12.3/Submit) with ESMTP id i6H1kgD7025414; Fri, 16 Jul 2004 18:46:43 -0700 (PDT) X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs Date: Fri, 16 Jul 2004 18:46:42 -0700 (PDT) From: Kireeti Kompella To: Philip Christian Subject: Re: [Isis-wg] Re: I-D ACTION:draft-ietf-isis-experimental-tlv-03.txt In-Reply-To: <5.2.1.1.1.20040629111851.00aa6a28@customermail.easily.co.uk> Message-ID: <20040716183040.U25342@kummer.juniper.net> References: <1208.82.44.189.18.1088275712.squirrel@www.easilymail.co.uk> <20040614170235.H11354@kummer.juniper.net> <200405121412.KAA06827@ietf. org> <200405121412.KAA06827@ietf.org> <5.2.1.1.1.20040617100610.00a8e430 @customermail.easily.co.uk> <20040617185155.T29575@kummer.juniper.net> < A4668A06-C6BD-11D8-B948-00039303E9E2@procket.com> <1065.82.44.189.18.10 88260160.squirrel@www.easilymail.co.uk> <6FF741B6-C785-11D8-8570-00039303E9E2@procket.com> <1208.82.44.189.18.1088275712.squirrel@www.easilymail.co.uk> <5.2.1.1.1.20040629111851.00aa6a28@customermail.easily.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Cc: Alex Zinin , Christian Hopps , isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org On Tue, 29 Jun 2004, Philip Christian wrote: > There isn't one. > > It pragmatic / procedural decision. > > I don't know enough about SNMP IDs to know how easy they are to get, how > much they cost, if they will ever run out, and if they will always be four > bytes. I guess four bytes is a lot of numbers.... a) To get these, you ask IANA. It's free and fairly easy. http://www.iana.org/assignments/enterprise-numbers b) There are 20,838 allocated out of 2^32 possible. Yes, they will run out. No, I'm not worried. c) If running out is an issue, then OUIs have a bigger problem :-) One other reason that enterprise numbers might be useful is that RSVP (and maybe OSPF) "Vendor Private" code points will use enterprise numbers to identify the owner of private extensions. See draft-kompella-rsvp-change-xx.txt and draft-kompella-ospf-iana-00.txt The RSVP doc is pretty much ready for publication. The OSPF doc has a long way to go yet. As for the rest, I don't particularly care if there is a discriminator byte, or we use only enterprise numbers. I have a slight preference for a discriminator byte, but not enough to do something about it. Kireeti. ------- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Jul 26 15:47:56 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04130 for ; Mon, 26 Jul 2004 15:47:56 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpBEn-0008RA-Ho; Mon, 26 Jul 2004 15:34:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpB0o-0003UL-2d for isis-wg@megatron.ietf.org; Mon, 26 Jul 2004 15:19:50 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA29317 for ; Mon, 26 Jul 2004 15:19:47 -0400 (EDT) Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpB2F-0004fI-Vc for isis-wg@ietf.org; Mon, 26 Jul 2004 15:21:20 -0400 Message-ID: From: Jeff Parker To: "'jcucchiara@mindspring.com'" , isis-wg@ietf.org Date: Mon, 26 Jul 2004 15:19:11 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Cc: Jeff Parker Subject: [Isis-wg] RE: smicng output for draft-ietf-isis-wg-mib-16.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Joan - Sorry, I have been out for a couple of weeks. I believe this to be a problem with SMICNG, not with the MIB. - jeff parker > Hi Jeff, > > The following is the smicng MIB compiler output > for version 16 of the MIB. smicng has the flags > specified by the mibtools > (see http://www.ops.ietf.org/mib-review-tools.html > for more details the flags). > > Are these going to be fixed in the next version of > the MIB? > > thanks, > -Joan > > > > >W: f(ISIS-MIB), (3118,13) Variable "isisSysLevelIndex" in > notification > >"isisDatabaseOverload" is an index for a table > >E: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification > >"isisManualAddressDrops" has access of "not-accessible" > >W: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification > >"isisManualAddressDrops" is an index for a table > >W: f(ISIS-MIB), (3152,13) Variable "isisSysLevelIndex" in > notification > >"isisCorruptedLSPDetected" is an index for a table > >W: f(ISIS-MIB), (3171,13) Variable "isisSysLevelIndex" in > notification > >"isisAttemptToExceedMaxSequence" is an index for a table > >W: f(ISIS-MIB), (3190,13) Variable "isisSysLevelIndex" in > notification > >"isisIDLenMismatch" is an index for a table > >W: f(ISIS-MIB), (3212,13) Variable "isisSysLevelIndex" in > notification > >"isisMaxAreaAddressesMismatch" is an index for a table > >W: f(ISIS-MIB), (3234,13) Variable "isisSysLevelIndex" in > notification > >"isisOwnLSPPurge" is an index for a table > >W: f(ISIS-MIB), (3251,13) Variable "isisSysLevelIndex" in > notification > >"isisSequenceNumberSkip" is an index for a table > >W: f(ISIS-MIB), (3270,13) Variable "isisSysLevelIndex" in > notification > >"isisAuthenticationTypeFailure" is an index for a table > >W: f(ISIS-MIB), (3290,13) Variable "isisSysLevelIndex" in > notification > >"isisAuthenticationFailure" is an index for a table > >W: f(ISIS-MIB), (3309,13) Variable "isisSysLevelIndex" in > notification > >"isisVersionSkew" is an index for a table > >W: f(ISIS-MIB), (3351,13) Variable "isisSysLevelIndex" in > notification > >"isisRejectedAdjacency" is an index for a table > >W: f(ISIS-MIB), (3369,13) Variable "isisSysLevelIndex" in > notification > >"isisLSPTooLargeToPropagate" is an index for a table > >W: f(ISIS-MIB), (3387,13) Variable "isisSysLevelIndex" in > notification > >"isisOrigLSPBuffSizeMismatch" is an index for a table > >W: f(ISIS-MIB), (3411,13) Variable "isisSysLevelIndex" in > notification > >"isisProtocolsSupportedMismatch" is an index for a table > >W: f(ISIS-MIB), (3436,13) Variable "isisSysLevelIndex" in > notification > >"isisAdjacencyChange" is an index for a table > >W: f(ISIS-MIB), (3453,13) Variable "isisSysLevelIndex" in > notification > >"isisLSPErrorDetected" is an index for a table > > > >*** 1 error and 17 warnings in parsing > > > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Jul 26 18:01:15 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13435 for ; Mon, 26 Jul 2004 18:01:15 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpDRM-0003UH-JG; Mon, 26 Jul 2004 17:55:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpDKb-00026m-8i for isis-wg@megatron.ietf.org; Mon, 26 Jul 2004 17:48:25 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12422 for ; Mon, 26 Jul 2004 17:48:22 -0400 (EDT) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpDM2-0000QO-ON for isis-wg@ietf.org; Mon, 26 Jul 2004 17:49:57 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 26 Jul 2004 14:52:02 +0000 X-BrightmailFiltered: true Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i6QLlY8a014559 for ; Mon, 26 Jul 2004 14:47:50 -0700 (PDT) Received: from jvasseur-w2k01.cisco.com (che-vpn-cluster-1-36.cisco.com [10.86.240.36]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA20921 for ; Mon, 26 Jul 2004 14:47:33 -0700 (PDT) Message-Id: <4.3.2.7.2.20040726174428.05fea428@wells.cisco.com> X-Sender: jvasseur@wells.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 26 Jul 2004 17:47:30 -0400 To: isis-wg@ietf.org From: Jean Philippe Vasseur Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Subject: [Isis-wg] Update on ISIS cap draft X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Hi, Just to mention that as agreed at IETF-59, we merged the two ISIS capability draft. The resulting merged draft is draft-vasseur-isis-caps-02.txt. Any comment is of course very welcome. JP. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Jul 26 18:08:26 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14396 for ; Mon, 26 Jul 2004 18:08:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpDVV-0004Sh-7k; Mon, 26 Jul 2004 17:59:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpDQW-0003NT-F9 for isis-wg@megatron.ietf.org; Mon, 26 Jul 2004 17:54:32 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA12819 for ; Mon, 26 Jul 2004 17:54:29 -0400 (EDT) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpDRy-0000Xd-2O for isis-wg@ietf.org; Mon, 26 Jul 2004 17:56:04 -0400 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 26 Jul 2004 14:58:10 +0000 X-BrightmailFiltered: true Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i6QLruq4005262; Mon, 26 Jul 2004 14:53:57 -0700 (PDT) Received: from jvasseur-w2k01.cisco.com (che-vpn-cluster-1-36.cisco.com [10.86.240.36]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA03298; Mon, 26 Jul 2004 14:53:55 -0700 (PDT) Message-Id: <4.3.2.7.2.20040726174734.05ffa730@wells.cisco.com> X-Sender: jvasseur@wells.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 26 Jul 2004 17:53:53 -0400 To: ccamp@ops.ietf.org, OSPF@DISCUSS.MICROSOFT.COM, isis-wg@ietf.org From: Jean Philippe Vasseur Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Cc: zinin@psg.com Subject: [Isis-wg] Update on the ISIS TE capability draft X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Hi, A quick update on the IGP TE capability drafts. There used to be two drafts proposing several TE-related extensions: draft-vasseur-ccamp-isis-te-caps draft-vasseur-ccamp-ospf-te-caps Based on the input from our AD and WG chairs, we restructured this work and came up with three drafts: draft-vasseur-ccamp-te-router-info-00 (discussed in CCAMP) and the IGP specific (sub)TLV encoding and elements of procedure are defined in: draft-vasseur-isis-te-caps-00 (in ISIS) draft-vasseur-ospf-te-caps-00 (in OSPF) Comments are of course very welcome. JP and al. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Jul 26 18:14:11 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15077 for ; Mon, 26 Jul 2004 18:14:11 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpDbU-0000B5-Iy; Mon, 26 Jul 2004 18:05:52 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpDUb-0004GN-DP for isis-wg@megatron.ietf.org; Mon, 26 Jul 2004 17:58:45 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13212 for ; Mon, 26 Jul 2004 17:58:42 -0400 (EDT) Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpDW4-0000dc-2b for isis-wg@ietf.org; Mon, 26 Jul 2004 18:00:17 -0400 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-1.cisco.com with ESMTP; 26 Jul 2004 15:01:22 -0700 X-BrightmailFiltered: true Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id i6QLw98a022867; Mon, 26 Jul 2004 14:58:11 -0700 (PDT) Received: from jvasseur-w2k01.cisco.com (che-vpn-cluster-1-36.cisco.com [10.86.240.36]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA10858; Mon, 26 Jul 2004 14:58:07 -0700 (PDT) Message-Id: <4.3.2.7.2.20040726175746.033cd1b8@wells.cisco.com> X-Sender: jvasseur@wells.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 Date: Mon, 26 Jul 2004 17:58:05 -0400 To: ccamp@ops.ietf.org, OSPF@DISCUSS.MICROSOFT.COM, isis-wg@ietf.org From: Jean Philippe Vasseur Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Subject: [Isis-wg] Update on the IGP TE capability drafts X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org >X-BrightmailFiltered: true >X-BrightmailFiltered: true >X-Sender: jvasseur@wells.cisco.com >X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 >Date: Mon, 26 Jul 2004 17:53:53 -0400 >Reply-To: Mailing List >Sender: Mailing List >From: Jean Philippe Vasseur >Subject: Update on the ISIS TE capability draft >Comments: To: ccamp@ops.ietf.org, OSPF@DISCUSS.MICROSOFT.COM, isis-wg@ietf.org >Comments: cc: zinin@psg.com >To: OSPF@PEACH.EASE.LSOFT.COM >X-PMX-Version: 4.6.1.107272 >X-from-outside-Cisco: 128.107.250.145 > >Hi, > >A quick update on the IGP TE capability drafts. > >There used to be two drafts proposing several TE-related extensions: > draft-vasseur-ccamp-isis-te-caps > draft-vasseur-ccamp-ospf-te-caps > >Based on the input from our AD and WG chairs, we restructured this work and >came up with three drafts: > draft-vasseur-ccamp-te-router-info-00 (discussed in CCAMP) > >and the IGP specific (sub)TLV encoding and elements of procedure are >defined in: > draft-vasseur-isis-te-caps-00 (in ISIS) > draft-vasseur-ospf-te-caps-00 (in OSPF) > >Comments are of course very welcome. > >JP and al. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Mon Jul 26 21:47:31 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26406 for ; Mon, 26 Jul 2004 21:47:31 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpH16-0005RC-PQ; Mon, 26 Jul 2004 21:44:32 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpGyT-0004q2-3p for isis-wg@megatron.ietf.org; Mon, 26 Jul 2004 21:41:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26049 for ; Mon, 26 Jul 2004 21:41:46 -0400 (EDT) From: jcucchiara@mindspring.com Received: from blount.mail.mindspring.net ([207.69.200.226]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpGzy-0004yk-R2 for isis-wg@ietf.org; Mon, 26 Jul 2004 21:43:23 -0400 Received: from h-66-167-248-130.cmbrmaor.dynamic.covad.net ([66.167.248.130] helo=jluciani-laptop) by blount.mail.mindspring.net with smtp (Exim 3.33 #1) id 1BpGyO-0005WJ-00; Mon, 26 Jul 2004 21:41:45 -0400 Message-Id: <3.0.1.32.20040726214259.012dbdac@pop.mindspring.com> X-Sender: jcucchiara@pop.mindspring.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Mon, 26 Jul 2004 21:42:59 -0400 To: Jeff Parker , isis-wg@ietf.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.3 (/) X-Scan-Signature: 7fa173a723009a6ca8ce575a65a5d813 Cc: Jeff Parker Subject: [Isis-wg] RE: smicng output for draft-ietf-isis-wg-mib-16.txt X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Hi Jeff, Thanks for your response. I am fairly certain that there are issues with the MIB because smiLint also gives similar complaints. For example, indices should be not-accessible and some of these are read-only. With regard to Notifications, the MIB review guidelines http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-03. txt specify: "RFC 2578 Section 8 specifies the rules for notification definitions. In particular: - Inaccessible objects MUST NOT appear in the OBJECTS clause." which is one of the complaints from these compilers. Slightly different topic: what is the status of the MIB? Has it gone through working group last call(s) and/or MIB Doctor review? thanks, -Joan At 03:19 PM 7/26/04 -0400, Jeff Parker wrote: >Joan - > Sorry, I have been out for a couple of weeks. > I believe this to be a problem with SMICNG, not with the MIB. > >- jeff parker > >> Hi Jeff, >> >> The following is the smicng MIB compiler output >> for version 16 of the MIB. smicng has the flags >> specified by the mibtools >> (see http://www.ops.ietf.org/mib-review-tools.html >> for more details the flags). >> >> Are these going to be fixed in the next version of >> the MIB? >> >> thanks, >> -Joan >> >> >> >> >W: f(ISIS-MIB), (3118,13) Variable "isisSysLevelIndex" in >> notification >> >"isisDatabaseOverload" is an index for a table >> >E: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification >> >"isisManualAddressDrops" has access of "not-accessible" >> >W: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification >> >"isisManualAddressDrops" is an index for a table >> >W: f(ISIS-MIB), (3152,13) Variable "isisSysLevelIndex" in >> notification >> >"isisCorruptedLSPDetected" is an index for a table >> >W: f(ISIS-MIB), (3171,13) Variable "isisSysLevelIndex" in >> notification >> >"isisAttemptToExceedMaxSequence" is an index for a table >> >W: f(ISIS-MIB), (3190,13) Variable "isisSysLevelIndex" in >> notification >> >"isisIDLenMismatch" is an index for a table >> >W: f(ISIS-MIB), (3212,13) Variable "isisSysLevelIndex" in >> notification >> >"isisMaxAreaAddressesMismatch" is an index for a table >> >W: f(ISIS-MIB), (3234,13) Variable "isisSysLevelIndex" in >> notification >> >"isisOwnLSPPurge" is an index for a table >> >W: f(ISIS-MIB), (3251,13) Variable "isisSysLevelIndex" in >> notification >> >"isisSequenceNumberSkip" is an index for a table >> >W: f(ISIS-MIB), (3270,13) Variable "isisSysLevelIndex" in >> notification >> >"isisAuthenticationTypeFailure" is an index for a table >> >W: f(ISIS-MIB), (3290,13) Variable "isisSysLevelIndex" in >> notification >> >"isisAuthenticationFailure" is an index for a table >> >W: f(ISIS-MIB), (3309,13) Variable "isisSysLevelIndex" in >> notification >> >"isisVersionSkew" is an index for a table >> >W: f(ISIS-MIB), (3351,13) Variable "isisSysLevelIndex" in >> notification >> >"isisRejectedAdjacency" is an index for a table >> >W: f(ISIS-MIB), (3369,13) Variable "isisSysLevelIndex" in >> notification >> >"isisLSPTooLargeToPropagate" is an index for a table >> >W: f(ISIS-MIB), (3387,13) Variable "isisSysLevelIndex" in >> notification >> >"isisOrigLSPBuffSizeMismatch" is an index for a table >> >W: f(ISIS-MIB), (3411,13) Variable "isisSysLevelIndex" in >> notification >> >"isisProtocolsSupportedMismatch" is an index for a table >> >W: f(ISIS-MIB), (3436,13) Variable "isisSysLevelIndex" in >> notification >> >"isisAdjacencyChange" is an index for a table >> >W: f(ISIS-MIB), (3453,13) Variable "isisSysLevelIndex" in >> notification >> >"isisLSPErrorDetected" is an index for a table >> > >> >*** 1 error and 17 warnings in parsing >> > >> > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Tue Jul 27 13:43:21 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01333 for ; Tue, 27 Jul 2004 13:43:21 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpVuk-0005YW-LJ; Tue, 27 Jul 2004 13:38:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpVqC-0004u4-GA for isis-wg@megatron.ietf.org; Tue, 27 Jul 2004 13:34:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00938 for ; Tue, 27 Jul 2004 13:34:15 -0400 (EDT) Received: from nn1.excitenetwork.com ([207.159.120.55] helo=excite.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpVro-0004lF-IX for isis-wg@ietf.org; Tue, 27 Jul 2004 13:35:58 -0400 Received: by xprdmailfe20.nwk.excite.com (Postfix, from userid 110) id 7B0F1B6D3; Tue, 27 Jul 2004 13:33:39 -0400 (EDT) To: jcucchiara@mindspring.com, jparker@axiowave.com Subject: [Isis-wg] RE: smicng output for draft-ietf-isis-wg-mib-16.txt Received: from [66.32.191.130] by xprdmailfe20.nwk.excite.com via HTTP; Tue, 27 Jul 2004 13:33:39 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = 03000aad6b64c467c855745665f057cb From: "Don Goodspeed" MIME-Version: 1.0 X-Sender: dgoodspe@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040727173339.7B0F1B6D3@xprdmailfe20.nwk.excite.com> Date: Tue, 27 Jul 2004 13:33:39 -0400 (EDT) X-Spam-Score: 0.1 (/) X-Scan-Signature: 223e3c753032a50d5dc4443c921c3fcd Content-Transfer-Encoding: 7bit Cc: isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dgoodspe@excite.com List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Content-Transfer-Encoding: 7bit Jeff, Joan, Joan is right and unfortunately, my MIB compilers tend to gloss over issues in NOTIFICATION-TYPE objects since they are more concerned with get-able and set-able objects. What can be done is to create two new OBJECT-TYPE attributes under isisNotificationEntry. Call them something like isisLevelIndex and isisAreaAddress and define them both as accessible-for-notify. isisLevelIndex can have a SYNTAX of ISLevel and isisAreaAddress can have a SYNTAX of OSINSAddress. I think that should take care of the compilation issues. Cheers, Don =================================== Hi Jeff, Thanks for your response. I am fairly certain that there are issues with the MIB because smiLint also gives similar complaints. For example, indices should be not-accessible and some of these are read-only. With regard to Notifications, the MIB review guidelines http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-03. txt specify: "RFC 2578 Section 8 specifies the rules for notification definitions. In particular: - Inaccessible objects MUST NOT appear in the OBJECTS clause." which is one of the complaints from these compilers. Slightly different topic: what is the status of the MIB? Has it gone through working group last call(s) and/or MIB Doctor review? thanks, -Joan At 03:19 PM 7/26/04 -0400, Jeff Parker wrote: >Joan - > Sorry, I have been out for a couple of weeks. > I believe this to be a problem with SMICNG, not with the MIB. > >- jeff parker > >> Hi Jeff, >> >> The following is the smicng MIB compiler output >> for version 16 of the MIB. smicng has the flags >> specified by the mibtools >> (see http://www.ops.ietf.org/mib-review-tools.html >> for more details the flags). >> >> Are these going to be fixed in the next version of >> the MIB? >> >> thanks, >> -Joan >> >> >> >> >W: f(ISIS-MIB), (3118,13) Variable "isisSysLevelIndex" in >> notification >> >"isisDatabaseOverload" is an index for a table >> >E: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification >> >"isisManualAddressDrops" has access of "not-accessible" >> >W: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification >> >"isisManualAddressDrops" is an index for a table >> >W: f(ISIS-MIB), (3152,13) Variable "isisSysLevelIndex" in >> notification >> >"isisCorruptedLSPDetected" is an index for a table >> >W: f(ISIS-MIB), (3171,13) Variable "isisSysLevelIndex" in >> notification >> >"isisAttemptToExceedMaxSequence" is an index for a table >> >W: f(ISIS-MIB), (3190,13) Variable "isisSysLevelIndex" in >> notification >> >"isisIDLenMismatch" is an index for a table >> >W: f(ISIS-MIB), (3212,13) Variable "isisSysLevelIndex" in >> notification >> >"isisMaxAreaAddressesMismatch" is an index for a table >> >W: f(ISIS-MIB), (3234,13) Variable "isisSysLevelIndex" in >> notification >> >"isisOwnLSPPurge" is an index for a table >> >W: f(ISIS-MIB), (3251,13) Variable "isisSysLevelIndex" in >> notification >> >"isisSequenceNumberSkip" is an index for a table >> >W: f(ISIS-MIB), (3270,13) Variable "isisSysLevelIndex" in >> notification >> >"isisAuthenticationTypeFailure" is an index for a table >> >W: f(ISIS-MIB), (3290,13) Variable "isisSysLevelIndex" in >> notification >> >"isisAuthenticationFailure" is an index for a table >> >W: f(ISIS-MIB), (3309,13) Variable "isisSysLevelIndex" in >> notification >> >"isisVersionSkew" is an index for a table >> >W: f(ISIS-MIB), (3351,13) Variable "isisSysLevelIndex" in >> notification >> >"isisRejectedAdjacency" is an index for a table >> >W: f(ISIS-MIB), (3369,13) Variable "isisSysLevelIndex" in >> notification >> >"isisLSPTooLargeToPropagate" is an index for a table >> >W: f(ISIS-MIB), (3387,13) Variable "isisSysLevelIndex" in >> notification >> >"isisOrigLSPBuffSizeMismatch" is an index for a table >> >W: f(ISIS-MIB), (3411,13) Variable "isisSysLevelIndex" in >> notification >> >"isisProtocolsSupportedMismatch" is an index for a table >> >W: f(ISIS-MIB), (3436,13) Variable "isisSysLevelIndex" in >> notification >> >"isisAdjacencyChange" is an index for a table >> >W: f(ISIS-MIB), (3453,13) Variable "isisSysLevelIndex" in >> notification >> >"isisLSPErrorDetected" is an index for a table >> > >> >*** 1 error and 17 warnings in parsing >> > >> > _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Tue Jul 27 20:19:34 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23172 for ; Tue, 27 Jul 2004 20:19:34 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bpc8F-0007Xp-QE; Tue, 27 Jul 2004 20:17:19 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bpc7N-0007PJ-CX for isis-wg@megatron.ietf.org; Tue, 27 Jul 2004 20:16:25 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23033 for ; Tue, 27 Jul 2004 20:16:24 -0400 (EDT) From: jcucchiara@mindspring.com Received: from barry.mail.mindspring.net ([207.69.200.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bpc94-0002ic-92 for isis-wg@ietf.org; Tue, 27 Jul 2004 20:18:11 -0400 Received: from h-66-167-185-153.cmbrmaor.dynamic.covad.net ([66.167.185.153] helo=jluciani-laptop) by barry.mail.mindspring.net with smtp (Exim 3.33 #1) id 1Bpc7I-0004dm-00; Tue, 27 Jul 2004 20:16:20 -0400 Message-Id: <3.0.1.32.20040727201636.012d917c@pop.mindspring.com> X-Sender: jcucchiara@pop.mindspring.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 27 Jul 2004 20:16:36 -0400 To: dgoodspe@excite.com, jparker@axiowave.com Subject: Re: [Isis-wg] RE: smicng output for draft-ietf-isis-wg-mib-16.txt In-Reply-To: <20040727173339.7B0F1B6D3@xprdmailfe20.nwk.excite.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.3 (/) X-Scan-Signature: d16ce744298aacf98517bc7c108bd198 Cc: isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org I am wondering if there is not a different way to resolve these errors, such as putting an object in the Notification. Don and Jeff, The object contains an index (which is one of the motivations to make indices not-accessible from smiv1 to smiv2). I don't see the need to add more objects to an already sizeable MIB, so think the solution of adding an object (from the row) into the Notifications, would be simpler. -Joan At 01:33 PM 7/27/04 -0400, Don Goodspeed wrote: > >Jeff, Joan, > >Joan is right and unfortunately, my MIB compilers tend to gloss over >issues in NOTIFICATION-TYPE objects since they are more concerned >with get-able and set-able objects. > >What can be done is to create two new OBJECT-TYPE attributes >under isisNotificationEntry. Call them something like >isisLevelIndex and isisAreaAddress and define them both as >accessible-for-notify. isisLevelIndex can have a SYNTAX of ISLevel >and isisAreaAddress can have a SYNTAX of OSINSAddress. > >I think that should take care of the compilation issues. > >Cheers, >Don >=================================== >Hi Jeff, > >Thanks for your response. >I am fairly certain that there are issues >with the MIB because smiLint also gives >similar complaints. > >For example, indices should be not-accessible >and some of these are read-only. > >With regard to Notifications, the MIB review guidelines >http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review-guidelines-03. >txt > >specify: >"RFC 2578 Section 8 specifies the rules for notification definitions. >In particular: > >- Inaccessible objects MUST NOT appear in the OBJECTS clause." > >which is one of the complaints from these compilers. > >Slightly different topic: what is the status of the MIB? Has it >gone through working group last call(s) and/or MIB Doctor review? > >thanks, >-Joan > > >At 03:19 PM 7/26/04 -0400, Jeff Parker wrote: >>Joan - >> Sorry, I have been out for a couple of weeks. >> I believe this to be a problem with SMICNG, not with the MIB. >> >>- jeff parker >> >>> Hi Jeff, >>> >>> The following is the smicng MIB compiler output >>> for version 16 of the MIB. smicng has the flags >>> specified by the mibtools >>> (see http://www.ops.ietf.org/mib-review-tools.html >>> for more details the flags). >>> >>> Are these going to be fixed in the next version of >>> the MIB? >>> >>> thanks, >>> -Joan >>> >>> >>> >>> >W: f(ISIS-MIB), (3118,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisDatabaseOverload" is an index for a table >>> >E: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification >>> >"isisManualAddressDrops" has access of "not-accessible" >>> >W: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in notification >>> >"isisManualAddressDrops" is an index for a table >>> >W: f(ISIS-MIB), (3152,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisCorruptedLSPDetected" is an index for a table >>> >W: f(ISIS-MIB), (3171,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisAttemptToExceedMaxSequence" is an index for a table >>> >W: f(ISIS-MIB), (3190,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisIDLenMismatch" is an index for a table >>> >W: f(ISIS-MIB), (3212,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisMaxAreaAddressesMismatch" is an index for a table >>> >W: f(ISIS-MIB), (3234,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisOwnLSPPurge" is an index for a table >>> >W: f(ISIS-MIB), (3251,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisSequenceNumberSkip" is an index for a table >>> >W: f(ISIS-MIB), (3270,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisAuthenticationTypeFailure" is an index for a table >>> >W: f(ISIS-MIB), (3290,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisAuthenticationFailure" is an index for a table >>> >W: f(ISIS-MIB), (3309,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisVersionSkew" is an index for a table >>> >W: f(ISIS-MIB), (3351,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisRejectedAdjacency" is an index for a table >>> >W: f(ISIS-MIB), (3369,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisLSPTooLargeToPropagate" is an index for a table >>> >W: f(ISIS-MIB), (3387,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisOrigLSPBuffSizeMismatch" is an index for a table >>> >W: f(ISIS-MIB), (3411,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisProtocolsSupportedMismatch" is an index for a table >>> >W: f(ISIS-MIB), (3436,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisAdjacencyChange" is an index for a table >>> >W: f(ISIS-MIB), (3453,13) Variable "isisSysLevelIndex" in >>> notification >>> >"isisLSPErrorDetected" is an index for a table >>> > >>> >*** 1 error and 17 warnings in parsing >>> > >>> >> > >_______________________________________________ >Join Excite! - http://www.excite.com >The most personalized portal on the Web! > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Jul 28 17:25:36 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06946 for ; Wed, 28 Jul 2004 17:25:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bpvji-0005Lb-C3; Wed, 28 Jul 2004 17:13:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpvhJ-0004p3-MC for isis-wg@megatron.ietf.org; Wed, 28 Jul 2004 17:10:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05155 for ; Wed, 28 Jul 2004 17:10:45 -0400 (EDT) From: jcucchiara@mindspring.com Received: from granger.mail.mindspring.net ([207.69.200.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bpvj9-0006nP-L0 for isis-wg@ietf.org; Wed, 28 Jul 2004 17:12:44 -0400 Received: from [192.168.167.45] (helo=wamui07.slb.atl.earthlink.net) by granger.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1Bpvh8-0002uR-00; Wed, 28 Jul 2004 17:10:38 -0400 Message-ID: <13795469.1091049038761.JavaMail.root@wamui07.slb.atl.earthlink.net> Date: Wed, 28 Jul 2004 17:10:38 -0400 (GMT-04:00) To: jparker@axiowave.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Zoo Mail 1.0 X-Spam-Score: 0.3 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit Cc: isis-wg@ietf.org Subject: [Isis-wg] draft-ietf-isis-wg-mib-16.txt, question on the isisSysLevelTable X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jcucchiara@mindspring.com List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Content-Transfer-Encoding: 7bit Hi Jeff, The index for the isisSysLevelTable is read-only and should be not-accessible. Also, there are read-create objects in the entry BUT there is no RowStatus object. Based on my understanding of this table, there probably should be a RowStatus object in the entry. For example, is it possible to have NO level2IS entry? Is so, then a RowStatus object is needed. If not, then is the intention that there are 2 rows in this table (always), one row for level1IS and one row for level2IS? If so, then these read-create objects should change to read-write. thanks, -Joan _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Jul 28 17:37:07 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07831 for ; Wed, 28 Jul 2004 17:37:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpvzH-0007yF-Rm; Wed, 28 Jul 2004 17:29:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bpvkl-0005P3-Hk for isis-wg@megatron.ietf.org; Wed, 28 Jul 2004 17:14:23 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA05320 for ; Wed, 28 Jul 2004 17:14:21 -0400 (EDT) Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bpvmb-0006qS-R1 for isis-wg@ietf.org; Wed, 28 Jul 2004 17:16:21 -0400 Message-ID: From: Jeff Parker To: "'jcucchiara@mindspring.com'" , Jeff Parker Date: Wed, 28 Jul 2004 17:13:37 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: isis-wg@ietf.org Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-16.txt, question on the isisSysLevelTa ble X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org I'm not sure that we need the weight of a RowStatus object for this table. We don;t spawn off huge numbers of SysLevel objects: we can expect a Level 1 and a Level 2 object to be active, but don't expect Level 42. I will modify the access level of these objects - jdp > Hi Jeff, > > The index for the isisSysLevelTable is read-only and should be > not-accessible. Also, there are read-create objects in the entry > BUT there is no RowStatus object. > > Based on my understanding of this table, there > probably should be a RowStatus object in the entry. For > example, is it > possible to have NO level2IS entry? Is so, then a > RowStatus object is needed. > > If not, then is the intention that there are 2 rows in this > table (always), > one row for level1IS and one row for level2IS? If so, then > these read-create objects should > change to read-write. > > thanks, > -Joan > > > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Jul 28 17:42:25 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08474 for ; Wed, 28 Jul 2004 17:42:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bpw9U-0001NA-Nz; Wed, 28 Jul 2004 17:39:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bpw1X-000053-NC for isis-wg@megatron.ietf.org; Wed, 28 Jul 2004 17:31:43 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07580 for ; Wed, 28 Jul 2004 17:31:41 -0400 (EDT) Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bpw3Q-0007Cj-50 for isis-wg@ietf.org; Wed, 28 Jul 2004 17:33:41 -0400 Message-ID: From: Jeff Parker To: "'jcucchiara@mindspring.com'" , Jeff Parker Date: Wed, 28 Jul 2004 17:31:08 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Cc: isis-wg@ietf.org Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-16.txt, question on the isisSysLevelTa ble X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Joan - I have taken a look at the table, and don't understand your concern. The isisSysType object is used to select the active levels - 1, 2, or both. The issiSysLevelTable holds a number of objects: I have edited the MIB to include the relevant sections. They all seem appropriate to me: those that I want to change are read-write, while those that I want to read are not-accessible. The Overload state may be set by hand, but may also be set by the implementation when it is low on memory. Do you have a specific suggestion? - jeff isisSysType OBJECT-TYPE SYNTAX INTEGER { level1IS (1), level2IS (2), level1L2IS (3) } MAX-ACCESS read-write -- The System Level Table -- This table captures level-specific information about the System isisSysLevelTable OBJECT-TYPE SYNTAX SEQUENCE OF IsisSysLevelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Level specific information about the System." ::= { isisSysLevel 1 } isisSysLevelEntry OBJECT-TYPE SYNTAX IsisSysLevelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describe variables defined for Area or Domain." INDEX { isisSysLevelIndex } ::= { isisSysLevelTable 1 } (Edited to put field and access on a single line) isisSysLevelIndex MAX-ACCESS read-only isisSysLevelOrigLSPBuffSize MAX-ACCESS read-create isisSysLevelMinLSPGenInt MAX-ACCESS read-create isisSysLevelOverloadState MAX-ACCESS read-only isisSysLevelSetOverload MAX-ACCESS read-create isisSysLevelSetOverloadUntil MAX-ACCESS read-create isisSysLevelMetricStyle MAX-ACCESS read-create isisSysLevelSPFConsiders MAX-ACCESS read-create isisSysLevelTEEnabled MAX-ACCESS read-create > -----Original Message----- > From: jcucchiara@mindspring.com [mailto:jcucchiara@mindspring.com] > Sent: Wednesday, July 28, 2004 5:11 PM > To: jparker@axiowave.com > Cc: isis-wg@ietf.org > Subject: draft-ietf-isis-wg-mib-16.txt, question on the > isisSysLevelTable > > > > Hi Jeff, > > The index for the isisSysLevelTable is read-only and should be > not-accessible. Also, there are read-create objects in the entry > BUT there is no RowStatus object. > > Based on my understanding of this table, there > probably should be a RowStatus object in the entry. For > example, is it > possible to have NO level2IS entry? Is so, then a > RowStatus object is needed. > > If not, then is the intention that there are 2 rows in this > table (always), > one row for level1IS and one row for level2IS? If so, then > these read-create objects should > change to read-write. > > thanks, > -Joan > > > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Wed Jul 28 19:02:55 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13575 for ; Wed, 28 Jul 2004 19:02:55 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpxNP-0004yR-J8; Wed, 28 Jul 2004 18:58:23 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BpxFv-0003bz-EC for isis-wg@megatron.ietf.org; Wed, 28 Jul 2004 18:50:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12836 for ; Wed, 28 Jul 2004 18:50:36 -0400 (EDT) Received: from nn7.excitenetwork.com ([207.159.120.61] helo=excite.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BpxHe-00006l-M3 for isis-wg@ietf.org; Wed, 28 Jul 2004 18:52:37 -0400 Received: by xprdmailfe18.nwk.excite.com (Postfix, from userid 110) id 3F6E7B6D1; Wed, 28 Jul 2004 18:49:51 -0400 (EDT) To: jparker@axiowave.com, jcucchiara@mindspring.com, jparker@axiowave.com Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-16.txt, question on the isisSysLevelTa ble Received: from [64.47.48.10] by xprdmailfe18.nwk.excite.com via HTTP; Wed, 28 Jul 2004 18:49:51 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = ce00c10647f1b9e7db16a67db0936ee4 From: "Don Goodspeed" MIME-Version: 1.0 X-Sender: dgoodspe@excite.com X-Mailer: PHP Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <20040728224951.3F6E7B6D1@xprdmailfe18.nwk.excite.com> Date: Wed, 28 Jul 2004 18:49:51 -0400 (EDT) X-Spam-Score: 0.0 (/) X-Scan-Signature: 16c9da4896bf5539ae3547c6c25f06a0 Content-Transfer-Encoding: 7bit Cc: isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dgoodspe@excite.com List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Content-Transfer-Encoding: 7bit Jeff, I think that Joan says that isisSysLevelIndex should be not-accessible and that the read-create objects in this table should be read-write objects since there is no desire to add a RowStatus. -don ======================== Joan - I have taken a look at the table, and don't understand your concern. The isisSysType object is used to select the active levels - 1, 2, or both. The issiSysLevelTable holds a number of objects: I have edited the MIB to include the relevant sections. They all seem appropriate to me: those that I want to change are read-write, while those that I want to read are not-accessible. The Overload state may be set by hand, but may also be set by the implementation when it is low on memory. Do you have a specific suggestion? - jeff isisSysType OBJECT-TYPE SYNTAX INTEGER { level1IS (1), level2IS (2), level1L2IS (3) } MAX-ACCESS read-write -- The System Level Table -- This table captures level-specific information about the System isisSysLevelTable OBJECT-TYPE SYNTAX SEQUENCE OF IsisSysLevelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Level specific information about the System." ::= { isisSysLevel 1 } isisSysLevelEntry OBJECT-TYPE SYNTAX IsisSysLevelEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Describe variables defined for Area or Domain." INDEX { isisSysLevelIndex } ::= { isisSysLevelTable 1 } (Edited to put field and access on a single line) isisSysLevelIndex MAX-ACCESS read-only isisSysLevelOrigLSPBuffSize MAX-ACCESS read-create isisSysLevelMinLSPGenInt MAX-ACCESS read-create isisSysLevelOverloadState MAX-ACCESS read-only isisSysLevelSetOverload MAX-ACCESS read-create isisSysLevelSetOverloadUntil MAX-ACCESS read-create isisSysLevelMetricStyle MAX-ACCESS read-create isisSysLevelSPFConsiders MAX-ACCESS read-create isisSysLevelTEEnabled MAX-ACCESS read-create > -----Original Message----- > From: jcucchiara@mindspring.com [mailto:jcucchiara@mindspring.com] > Sent: Wednesday, July 28, 2004 5:11 PM > To: jparker@axiowave.com > Cc: isis-wg@ietf.org > Subject: draft-ietf-isis-wg-mib-16.txt, question on the > isisSysLevelTable > > > > Hi Jeff, > > The index for the isisSysLevelTable is read-only and should be > not-accessible. Also, there are read-create objects in the entry > BUT there is no RowStatus object. > > Based on my understanding of this table, there > probably should be a RowStatus object in the entry. For > example, is it > possible to have NO level2IS entry? Is so, then a > RowStatus object is needed. > > If not, then is the intention that there are 2 rows in this > table (always), > one row for level1IS and one row for level2IS? If so, then > these read-create objects should > change to read-write. > > thanks, > -Joan > > > _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Jul 29 09:13:37 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA09295 for ; Thu, 29 Jul 2004 09:13:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqAGm-0003DW-Ah; Thu, 29 Jul 2004 08:44:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bq9tz-0000JH-2q for isis-wg@megatron.ietf.org; Thu, 29 Jul 2004 08:20:51 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA06324 for ; Thu, 29 Jul 2004 08:20:14 -0400 (EDT) From: jcucchiara@mindspring.com Received: from barry.mail.mindspring.net ([207.69.200.25]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bq9vN-0003M5-CQ for isis-wg@ietf.org; Thu, 29 Jul 2004 08:22:21 -0400 Received: from h-66-167-248-17.cmbrmaor.dynamic.covad.net ([66.167.248.17] helo=jluciani-laptop) by barry.mail.mindspring.net with smtp (Exim 3.33 #1) id 1Bq9tI-0002Xp-00; Thu, 29 Jul 2004 08:20:08 -0400 Message-Id: <3.0.1.32.20040729081853.0127bba4@pop.mindspring.com> X-Sender: jcucchiara@pop.mindspring.com (Unverified) X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 29 Jul 2004 08:18:53 -0400 To: Jeff Parker , Jeff Parker In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Score: 0.3 (/) X-Scan-Signature: 0ff9c467ad7f19c2a6d058acd7faaec8 Cc: isis-wg@ietf.org Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-16.txt, question on the isisSysLevelTable X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org At 05:31 PM 7/28/04 -0400, Jeff Parker wrote: >Joan - Hi Jeff, See below. > I have taken a look at the table, and don't understand your concern. > > The isisSysType object is used to select the active levels - 1, 2, >or both. >The issiSysLevelTable holds a number of objects: I have edited the MIB to >include the relevant sections. They all seem appropriate to me: those that >I want to change are read-write, while those that I want to read are >not-accessible. The Overload state may be set by hand, but may also be set >by the implementation when it is low on memory. > So let me see if I am understanding you. If the scalar object isisSysLevelType has the value of level1IS(1), then there is ONE row in the isisSysLevelTable and this row has the isisSysLevelIndex with a value of level1IS(1). If the value of the scalar isisSysLevelType has the value of levelIS(2), the thre is ONE row in the isisSysLevelTable and this row has the isisSysLevelIndex with a value of level2IS(2). If the value of the scalar isisSysLevelType has the value of levelL1L2IS(3), then there are 2 rows in the isisSysLevelTable where one row is the isisSysLevelIndex with a value of level1IS(1) and the other row with the isisSysLevelIndex with a value of level2IS(2). Is this correct? If the above is correct than I think the DESCRIPTION clauses for both the scalar object, isisSysLevel and the isisSysLevelTable need to state this clearly so that the agent is responsible for creating/destroying rows in this table if the scalar object is changed. The operator using this MIB and the developer implementing this MIB should understand the relationship between that scalar and this table. (This wasn't obvious to me as a fairly new reader of the MIB.) Also, in addition to clarifying the DESCRIPTION clauses, I would strongly suggest moving the scalar object to just before the table to emphasize the relationship between the scalar and the table. The SMI is still incorrect in that the Index of the isisSysLevelTable needs to be not-accessible (think we are in agreement on this). Also, if the agent is responsible for creating/destroying rows, then all of the read-create objects should be changed to read-write (as Don also states). read-create is when the operator is creating/destroying rows (and related to RowStatus). Does this make sense? thanks, Joan > Do you have a specific suggestion? > >- jeff > > isisSysType OBJECT-TYPE > SYNTAX INTEGER > { > level1IS (1), > level2IS (2), > level1L2IS (3) > } > MAX-ACCESS read-write > > -- The System Level Table >-- This table captures level-specific information about the System > > isisSysLevelTable OBJECT-TYPE > SYNTAX SEQUENCE OF IsisSysLevelEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Level specific information about the System." > ::= { isisSysLevel 1 } > > isisSysLevelEntry OBJECT-TYPE > SYNTAX IsisSysLevelEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Describe variables defined for Area or Domain." > INDEX { isisSysLevelIndex } > ::= { isisSysLevelTable 1 } > >(Edited to put field and access on a single line) > > isisSysLevelIndex MAX-ACCESS read-only > isisSysLevelOrigLSPBuffSize MAX-ACCESS read-create > isisSysLevelMinLSPGenInt MAX-ACCESS read-create > isisSysLevelOverloadState MAX-ACCESS read-only > isisSysLevelSetOverload MAX-ACCESS read-create > isisSysLevelSetOverloadUntil MAX-ACCESS read-create > isisSysLevelMetricStyle MAX-ACCESS read-create > isisSysLevelSPFConsiders MAX-ACCESS read-create > isisSysLevelTEEnabled MAX-ACCESS read-create > > >> -----Original Message----- >> From: jcucchiara@mindspring.com [mailto:jcucchiara@mindspring.com] >> Sent: Wednesday, July 28, 2004 5:11 PM >> To: jparker@axiowave.com >> Cc: isis-wg@ietf.org >> Subject: draft-ietf-isis-wg-mib-16.txt, question on the >> isisSysLevelTable >> >> >> >> Hi Jeff, >> >> The index for the isisSysLevelTable is read-only and should be >> not-accessible. Also, there are read-create objects in the entry >> BUT there is no RowStatus object. >> >> Based on my understanding of this table, there >> probably should be a RowStatus object in the entry. For >> example, is it >> possible to have NO level2IS entry? Is so, then a >> RowStatus object is needed. >> >> If not, then is the intention that there are 2 rows in this >> table (always), >> one row for level1IS and one row for level2IS? If so, then >> these read-create objects should >> change to read-write. >> >> thanks, >> -Joan >> >> >> > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Jul 29 10:10:22 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13210 for ; Thu, 29 Jul 2004 10:10:22 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqB1S-00005j-Fy; Thu, 29 Jul 2004 09:32:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqAYW-0005cE-O0 for isis-wg@megatron.ietf.org; Thu, 29 Jul 2004 09:02:44 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA08806 for ; Thu, 29 Jul 2004 09:02:37 -0400 (EDT) Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqAaS-0003zS-Kg for isis-wg@ietf.org; Thu, 29 Jul 2004 09:04:45 -0400 Message-ID: From: Jeff Parker To: "'jcucchiara@mindspring.com'" , Jeff Parker , Jeff Parker Date: Thu, 29 Jul 2004 09:02:03 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: isis-wg@ietf.org Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-16.txt, question on the isisSysLevelTa ble X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org > > The isisSysType object is used to select the active > levels - 1, 2, or both. > So let me see if I am understanding you. If the > scalar object isisSysLevelType has the value of > level1IS(1), then there is ONE row in the isisSysLevelTable > and this row has the isisSysLevelIndex with a value > of level1IS(1). No. It may be useful to save the configuration of a level, even if the system currently does not enable things at that level. My car remembers the details of my wife's seat position, even when I am driving. I can add text to the description for SysLevel to this effect. I would rather not move the position of isisSysType from the rest of the old system table. > The SMI is still incorrect in that the Index of the isisSysLevelTable > needs to be not-accessible (think we are in agreement on this). Yes. You stated that some "read-only" objects should be changed: the only one I see is the isisSysLevelOverloadState. I continue to think that read-only is exactly right. To continue the car analogy, this is the oil gauge. - jeff parker > > isisSysType OBJECT-TYPE > > SYNTAX INTEGER > > { > > level1IS (1), > > level2IS (2), > > level1L2IS (3) > > } > > MAX-ACCESS read-write ... > > isisSysLevelIndex MAX-ACCESS read-only Will change > > isisSysLevelOrigLSPBuffSize MAX-ACCESS read-create > > isisSysLevelMinLSPGenInt MAX-ACCESS read-create > > isisSysLevelOverloadState MAX-ACCESS read-only > > isisSysLevelSetOverload MAX-ACCESS read-create > > isisSysLevelSetOverloadUntil MAX-ACCESS read-create > > isisSysLevelMetricStyle MAX-ACCESS read-create > > isisSysLevelSPFConsiders MAX-ACCESS read-create > > isisSysLevelTEEnabled MAX-ACCESS read-create _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Jul 29 12:11:40 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21503 for ; Thu, 29 Jul 2004 12:11:40 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqBp1-00053x-8s; Thu, 29 Jul 2004 10:23:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqBTw-0004t9-HW for isis-wg@megatron.ietf.org; Thu, 29 Jul 2004 10:02:04 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12041 for ; Thu, 29 Jul 2004 10:01:57 -0400 (EDT) Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqBVt-0004to-P5 for isis-wg@ietf.org; Thu, 29 Jul 2004 10:04:06 -0400 Message-ID: From: Jeff Parker To: "'dgoodspe@excite.com'" , jcucchiara@mindspring.com Subject: RE: [Isis-wg] RE: smicng output for draft-ietf-isis-wg-mib-16.txt Date: Thu, 29 Jul 2004 10:01:22 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Cc: isis-wg@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Don - I can see why isisSysLevel might present a problem. Why isn't CircIfIndex also a problem? Is it just masked by SysLevel? - jeff parker - axiowave networks - As scarce as truth is, the supply has always been in excess of the demand - Josh Billings > -----Original Message----- > From: Don Goodspeed [mailto:dgoodspe@excite.com] > Sent: Tuesday, July 27, 2004 1:34 PM > To: jcucchiara@mindspring.com; jparker@axiowave.com > Cc: isis-wg@ietf.org > Subject: [Isis-wg] RE: smicng output for draft-ietf-isis-wg-mib-16.txt > > > > Jeff, Joan, > > Joan is right and unfortunately, my MIB compilers tend to gloss over > issues in NOTIFICATION-TYPE objects since they are more concerned > with get-able and set-able objects. > > What can be done is to create two new OBJECT-TYPE attributes > under isisNotificationEntry. Call them something like > isisLevelIndex and isisAreaAddress and define them both as > accessible-for-notify. isisLevelIndex can have a SYNTAX of ISLevel > and isisAreaAddress can have a SYNTAX of OSINSAddress. > > I think that should take care of the compilation issues. > > Cheers, > Don > =================================== > Hi Jeff, > > Thanks for your response. > I am fairly certain that there are issues > with the MIB because smiLint also gives > similar complaints. > > For example, indices should be not-accessible > and some of these are read-only. > > With regard to Notifications, the MIB review guidelines > http://www.ietf.org/internet-drafts/draft-ietf-ops-mib-review- > guidelines-03. > txt > > specify: > "RFC 2578 Section 8 specifies the rules for notification definitions. > In particular: > > - Inaccessible objects MUST NOT appear in the OBJECTS clause." > > which is one of the complaints from these compilers. > > Slightly different topic: what is the status of the MIB? Has it > gone through working group last call(s) and/or MIB Doctor review? > > thanks, > -Joan > > > At 03:19 PM 7/26/04 -0400, Jeff Parker wrote: > >Joan - > > Sorry, I have been out for a couple of weeks. > > I believe this to be a problem with SMICNG, not with the MIB. > > > >- jeff parker > > > >> Hi Jeff, > >> > >> The following is the smicng MIB compiler output > >> for version 16 of the MIB. smicng has the flags > >> specified by the mibtools > >> (see http://www.ops.ietf.org/mib-review-tools.html > >> for more details the flags). > >> > >> Are these going to be fixed in the next version of > >> the MIB? > >> > >> thanks, > >> -Joan > >> > >> > >> > >> >W: f(ISIS-MIB), (3118,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisDatabaseOverload" is an index for a table > >> >E: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in > notification > >> >"isisManualAddressDrops" has access of "not-accessible" > >> >W: f(ISIS-MIB), (3131,13) Variable "isisManAreaAddr" in > notification > >> >"isisManualAddressDrops" is an index for a table > >> >W: f(ISIS-MIB), (3152,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisCorruptedLSPDetected" is an index for a table > >> >W: f(ISIS-MIB), (3171,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisAttemptToExceedMaxSequence" is an index for a table > >> >W: f(ISIS-MIB), (3190,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisIDLenMismatch" is an index for a table > >> >W: f(ISIS-MIB), (3212,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisMaxAreaAddressesMismatch" is an index for a table > >> >W: f(ISIS-MIB), (3234,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisOwnLSPPurge" is an index for a table > >> >W: f(ISIS-MIB), (3251,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisSequenceNumberSkip" is an index for a table > >> >W: f(ISIS-MIB), (3270,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisAuthenticationTypeFailure" is an index for a table > >> >W: f(ISIS-MIB), (3290,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisAuthenticationFailure" is an index for a table > >> >W: f(ISIS-MIB), (3309,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisVersionSkew" is an index for a table > >> >W: f(ISIS-MIB), (3351,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisRejectedAdjacency" is an index for a table > >> >W: f(ISIS-MIB), (3369,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisLSPTooLargeToPropagate" is an index for a table > >> >W: f(ISIS-MIB), (3387,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisOrigLSPBuffSizeMismatch" is an index for a table > >> >W: f(ISIS-MIB), (3411,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisProtocolsSupportedMismatch" is an index for a table > >> >W: f(ISIS-MIB), (3436,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisAdjacencyChange" is an index for a table > >> >W: f(ISIS-MIB), (3453,13) Variable "isisSysLevelIndex" in > >> notification > >> >"isisLSPErrorDetected" is an index for a table > >> > > >> >*** 1 error and 17 warnings in parsing > >> > > >> > > > > _______________________________________________ > Join Excite! - http://www.excite.com > The most personalized portal on the Web! > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu Jul 29 13:13:07 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25817 for ; Thu, 29 Jul 2004 13:13:07 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqDPS-0003y1-E2; Thu, 29 Jul 2004 12:05:34 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqBv4-0005XQ-Op for isis-wg@megatron.ietf.org; Thu, 29 Jul 2004 10:30:06 -0400 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14906 for ; Thu, 29 Jul 2004 10:29:29 -0400 (EDT) From: jcucchiara@mindspring.com Received: from hall.mail.mindspring.net ([207.69.200.60]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqBwY-0005PG-AB for isis-wg@ietf.org; Thu, 29 Jul 2004 10:31:38 -0400 Received: from [192.168.167.43] (helo=wamui05.slb.atl.earthlink.net) by hall.mail.mindspring.net with esmtp (Exim 3.33 #1) id 1BqBuR-000396-00; Thu, 29 Jul 2004 10:29:27 -0400 Message-ID: <25319033.1091111366790.JavaMail.root@wamui05.slb.atl.earthlink.net> Date: Thu, 29 Jul 2004 10:29:25 -0400 (GMT-04:00) To: Jeff Parker Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Earthlink Zoo Mail 1.0 X-Spam-Score: 0.3 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Content-Transfer-Encoding: 7bit Cc: isis-wg@ietf.org Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-16.txt, question on the isisSysLevelTa ble X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: jcucchiara@mindspring.com List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Content-Transfer-Encoding: 7bit -----Original Message----- From: Jeff Parker Sent: Jul 29, 2004 9:02 AM To: "'jcucchiara@mindspring.com'" , Jeff Parker , Jeff Parker Cc: isis-wg@ietf.org Subject: RE: draft-ietf-isis-wg-mib-16.txt, question on the isisSysLevelTa ble > > The isisSysType object is used to select the active > levels - 1, 2, or both. > So let me see if I am understanding you. If the > scalar object isisSysLevelType has the value of > level1IS(1), then there is ONE row in the isisSysLevelTable > and this row has the isisSysLevelIndex with a value > of level1IS(1). No. It may be useful to save the configuration of a level, even if the system currently does not enable things at that level. My car remembers the details of my wife's seat position, even when I am driving. jec> That is fine as long as this is clarified in the DESCRIPTION jec> clauses (for both the scalar and the table). You *might* want to consider adding a read-only jec> object to the table to indicate which row/rows are "inUse". If not, this is going to jec> be more checking/guessing for an operator. I'd rather have this info captured in jec> another row object. jec> I can add text to the description for SysLevel to this effect. jec> To be clear, text should be added to both the scalar and the table jec> about this, because the 2 are related. I would rather not move the position of isisSysType from the rest of the old system table. jec> I disagree because the current MIB style in the IETF is to jec> have scalars moved close to tables they are related to. jec> Certainly, this doesn't cause a MIB compilation error/warning, jec> because it is semantic (rather than syntactic) but all the same, jec> it is current practice in IETF MIBs to move such a scalar closer to jec> the table. I don't see why you would NOT want to do this as it jec> clarifies the relationship between the scalar and this table. > The SMI is still incorrect in that the Index of the isisSysLevelTable > needs to be not-accessible (think we are in agreement on this). Yes. You stated that some "read-only" objects should be changed: the only one I see is the isisSysLevelOverloadState. I continue to think that read-only is exactly right. To continue the car analogy, this is the oil gauge. jec> No, sorry if I wasn't clear. I stated that the read-create objects need to be changed to jec> read-write. (I'm not suggesting changes to the the read-only objects jec> except for the INDEX which we agree should be made "not-accessible". thanks, -Joan - jeff parker > > isisSysType OBJECT-TYPE > > SYNTAX INTEGER > > { > > level1IS (1), > > level2IS (2), > > level1L2IS (3) > > } > > MAX-ACCESS read-write ... > > isisSysLevelIndex MAX-ACCESS read-only Will change > > isisSysLevelOrigLSPBuffSize MAX-ACCESS read-create > > isisSysLevelMinLSPGenInt MAX-ACCESS read-create > > isisSysLevelOverloadState MAX-ACCESS read-only > > isisSysLevelSetOverload MAX-ACCESS read-create > > isisSysLevelSetOverloadUntil MAX-ACCESS read-create > > isisSysLevelMetricStyle MAX-ACCESS read-create > > isisSysLevelSPFConsiders MAX-ACCESS read-create > > isisSysLevelTEEnabled MAX-ACCESS read-create _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg