From isis-wg-admin@ietf.org Tue Oct 1 18:29:11 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07265 for ; Tue, 1 Oct 2002 18:29:11 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91MR7v00947; Tue, 1 Oct 2002 18:27:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g91MNHv00835 for ; Tue, 1 Oct 2002 18:23:17 -0400 Received: from mail4.nec.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07106 for ; Tue, 1 Oct 2002 18:21:12 -0400 (EDT) Received: from netkeeper.sj.nec.com (netkeeper.sj.nec.com [131.241.31.2]) by mail4.nec.com (/) with ESMTP id g91MN8v07773 for ; Tue, 1 Oct 2002 15:23:08 -0700 (PDT) Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1]) by netkeeper.sj.nec.com (8.9.1a/8.9.1) with ESMTP id PAA28709 for ; Tue, 1 Oct 2002 15:23:01 -0700 (PDT) Received: from bunny.tdd.sj.nec.com by necsun.tdd.sj.nec.com with ESMTP id g91MFPxN021371 for ; Tue, 1 Oct 2002 15:15:25 -0700 (PDT) Received: from ems11 (ems11 [131.241.5.62]) by bunny.tdd.sj.nec.com with SMTP id g91MFOKq001503 for ; Tue, 1 Oct 2002 15:15:24 -0700 (PDT) Received: by localhost with Microsoft MAPI; Tue, 1 Oct 2002 15:29:15 -0700 Message-ID: <01C2695F.4D4A9BE0.ramsrm@tdd.sj.nec.com> From: ramanathan rams Reply-To: "ramsrm@tdd.sj.nec.com" To: "'isis-wg@ietf.org'" Organization: NEC X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 Encoding: 44 TEXT Subject: [Isis-wg] ISIS-GMPLS extensions doubts Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 1 Oct 2002 15:29:14 -0700 hi all, I have the following doubts, could u please explain me? If I am wrong with my assumptions please correct me. Assumptions : * In optical domain - control channel and data channel are separate. ISIS will be running in the control channel and advertise thecontrol channel connectivity. For GMPLS/TE purpose we r adding the data channel properties along with control channel properties in ISIS LSPs and flooding it. so i assume that we need not establish data channel adjacency in each and every data channel using hellos. Hellos will be exchanged only in control channel and control channel adjacency will be established. In LSPs along with control channel link state, data channel properties will be advertised. * we can have multiple data channels between two systems ( many point to point links ). for each link local end will assign local link identifer and remote end will assign remote link identifier. Doubts : From ISIS GMPLS extension : * Section 6.5 says Link's local and remote identifers are exchanged using 3 way PP handshake. using 3 way PP Handshake, we can exchange local and remote identifiers. In this case it is done for the link where data and control channel are not separate. In optical domain since we exchange hellos only in control channel, how do we exchange link identifiers for so many data channels that are running between two machines. * SRLG option is unique for local and remote link identifier combination right?, if that is the case anyway we r advertising the local and remote idenitfier in IS extended reachability field as a sub TLV, so we can add SRLG as a sub TLV of IS extended reachability right? why do we need a separate TLV?( assumption : if we have n data links between two machines A and B, in A's LSP IS extended reachability for neighbour B, will appear n times for n different links ) thanks rams. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu Oct 3 07:23:43 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02490 for ; Thu, 3 Oct 2002 07:23:43 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93BLev07281; Thu, 3 Oct 2002 07:21:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g93BDcv06787 for ; Thu, 3 Oct 2002 07:13:38 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01906; Thu, 3 Oct 2002 07:11:36 -0400 (EDT) Message-Id: <200210031111.HAA01906@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-multi-topology-05.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 03 Oct 2002 07:11:36 -0400 --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 : M-ISIS: Multi Topology (MT)Routing in IS-IS Author(s) : T. Przygienda, N. Shen, N. Sheth Filename : draft-ietf-isis-wg-multi-topology-05.txt Pages : 11 Date : 2002-10-2 This draft describes an optional mechanism within ISIS used today by many ISPs for IGP routing within their clouds. This draft describes how to run within a single ISIS domain a set of independent IP topologies that we call Multi-Topologies (MTs). This MT extension can be used for variety of purposes such as an in-band management network ``on top'' of the original IGP topology, maintain separate IGP routing domains for isolated multicast or IPv6 islands within the backbone, or force a subset of an address space to follow a different topology. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-multi-topology-05.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-wg-multi-topology-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-wg-multi-topology-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: <2002-10-2132845.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-wg-multi-topology-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-wg-multi-topology-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-10-2132845.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 19:31:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09819 for ; Mon, 7 Oct 2002 19:31:35 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g97NT4v16634; Mon, 7 Oct 2002 19:29:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g97NPTv16559 for ; Mon, 7 Oct 2002 19:25:29 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA09594 for ; Mon, 7 Oct 2002 19:23:16 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 11BA33E22; Mon, 7 Oct 2002 19:25:18 -0400 (EDT) To: dparker@axiowave.com, isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 19:25:18 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021007232518.11BA33E22@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Updates to IS-IS MIB Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 19:25:18 -0400 (EDT) Content-Transfer-Encoding: 7bit Dave, Do you have the isisLSPTable on the to-do list for the IS-IS MIB? We had previously discussed methods on how to do this, but I saw no mention in version -09 of the draft. Thanks, Don P.S. I'm getting ready to send emails with my comments on the existing MIB draft. I'll be sending each issue separately since some may generate zero discussion and others may generate more discussion, and I like to keep issues separate from each other. ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 19:59:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10255 for ; Mon, 7 Oct 2002 19:59:27 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g97NwAv17940; Mon, 7 Oct 2002 19:58:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g97Nt6v17852 for ; Mon, 7 Oct 2002 19:55:06 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10191 for ; Mon, 7 Oct 2002 19:52:53 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 906F23E1E; Mon, 7 Oct 2002 19:54:54 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 19:54:54 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021007235454.906F23E1E@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: SYNTAX statement on SystemID needs to be indented Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 19:54:54 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 9 of draft mib-09, the SYNTAX statement needs to be indented. -don I said some of these would be minor... ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 20:04:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10413 for ; Mon, 7 Oct 2002 20:04:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98033v18118; Mon, 7 Oct 2002 20:03:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9800lv18055 for ; Mon, 7 Oct 2002 20:00:47 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA10237 for ; Mon, 7 Oct 2002 19:58:34 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id BEEC43E24; Mon, 7 Oct 2002 20:00:35 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 20:00:35 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008000035.BEEC43E24@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: SupportedProtocol # of ipV6 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 20:00:35 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 10 of draft mib-09, the enumerated value for ipV6 is 205, but when I checked a copy of TR9577, the value is 142. Also, routers that start with a "j" send a protocol support TLV with a value of 0x8e (142) for IPv6. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 20:12:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10768 for ; Mon, 7 Oct 2002 20:12:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g980A5v18843; Mon, 7 Oct 2002 20:10:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98072v18327 for ; Mon, 7 Oct 2002 20:07:02 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10432 for ; Mon, 7 Oct 2002 20:04:50 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 695D73E2B; Mon, 7 Oct 2002 20:06:51 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 20:06:51 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008000651.695D73E2B@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: ISLevel enumerations Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 20:06:51 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 11 of draft mib-09, ISLevel has the current enumerations: area(1), domain(2), none(3) Should we instead utilize the more common names of: l1(1), l2(2), none(3) or even: none(0), l1(1), l2(2), l1L2(3) Just a question, Don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 20:13:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10838 for ; Mon, 7 Oct 2002 20:13:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g980D3v18922; Mon, 7 Oct 2002 20:13:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9809Rv18814 for ; Mon, 7 Oct 2002 20:09:27 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10520 for ; Mon, 7 Oct 2002 20:07:14 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 47A7B3E2B; Mon, 7 Oct 2002 20:09:15 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 20:09:15 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008000915.47A7B3E2B@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: ISPriority, any implementation allow zero? Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 20:09:15 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 11 of draft mib-09, ISPriority's range is defined as 1..127. Do any current implementations allow a value of zero? If so, we should probably modify the range to include zero. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 20:38:32 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11760 for ; Mon, 7 Oct 2002 20:38:32 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g980bIv20170; Mon, 7 Oct 2002 20:37:18 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g980Y6v19552 for ; Mon, 7 Oct 2002 20:34:06 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11534 for ; Mon, 7 Oct 2002 20:31:52 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 2F1143DEF; Mon, 7 Oct 2002 20:33:54 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 20:33:54 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008003354.2F1143DEF@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: need for isisOverloadTimeLeft Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 20:33:54 -0400 (EDT) Content-Transfer-Encoding: 7bit Since many implemenations allow overload to be set for a given time, we should have a MIB attribute called something like isisSysOverloadTimeLeft (or TimeRemaining) that would serve two functions. When set along with isisSysSetOverload, would set overload for the configured time period (unit should be in seconds). When read, it would show the time remaining in the overload state. If not set, or if set to zero, when isisSysSetOverload is set, means an infinite overload period (which is the current operation). -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 20:44:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11894 for ; Mon, 7 Oct 2002 20:44:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g980i4v20398; Mon, 7 Oct 2002 20:44:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g980fkv20339 for ; Mon, 7 Oct 2002 20:41:46 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA11789 for ; Mon, 7 Oct 2002 20:39:32 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 389E13E22; Mon, 7 Oct 2002 20:41:34 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 20:41:34 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008004134.389E13E22@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: should we include Auth settings? Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 20:41:34 -0400 (EDT) Content-Transfer-Encoding: 7bit All, Should we include any MIB attributes for Authentication settings in the ISIS MIB? Possible attributes would include at each of {system, level, circuit, circuit-level} attributes for: auth-type (none, password, or MD5) auth-password (or auth-key): would be write-only auth-check Possible additional attributes might include settings for: hello-auth-type hello-auth-password (or key) hello-auth-check I know some vendors also allow control of security on other types (psnp's, etc.) as well. This could be a can of worms, but I thought I'd raise the issue. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 21:07:38 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12198 for ; Mon, 7 Oct 2002 21:07:38 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9816Ev21062; Mon, 7 Oct 2002 21:06:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9813Ov20994 for ; Mon, 7 Oct 2002 21:03:24 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12114 for ; Mon, 7 Oct 2002 21:01:12 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 429203E10; Mon, 7 Oct 2002 21:03:11 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 21:03:11 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008010311.429203E10@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: create isisSysOperStatus to go along with AdminState Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:03:11 -0400 (EDT) Content-Transfer-Encoding: 7bit I'm a big believer in having an OperStatus to go along with an AdminState (where it makes sense). The two places, I'd like to see an OperStatus is in the isisSys table, and in the isisCircTable. At the system level, the OperStatus might still be up for a few seconds when the protocol has been disabled to clean up some internal entities. At the circuit level, a lower-level link status of down would cause the OperStatus of the circuit to be down as opposed to up. Just my thoughts, Don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 21:11:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12337 for ; Mon, 7 Oct 2002 21:11:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98191v21726; Mon, 7 Oct 2002 21:09:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9815Fv21038 for ; Mon, 7 Oct 2002 21:05:15 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12149 for ; Mon, 7 Oct 2002 21:03:03 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 6E49D3E22; Mon, 7 Oct 2002 21:05:03 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 21:05:03 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008010503.6E49D3E22@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: space needed on DEFVAL of isisSysSetOverload Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:05:03 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 19 of the draft mib-09, there needs to be a space after the open brace on the DEFVAL declaration for isisSysSetOverload. Should be: DEFVAL { overloadClear } -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 21:16:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12451 for ; Mon, 7 Oct 2002 21:16:31 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981F4v21988; Mon, 7 Oct 2002 21:15:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981Cbv21927 for ; Mon, 7 Oct 2002 21:12:37 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12283 for ; Mon, 7 Oct 2002 21:10:25 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 2EBF53DFC; Mon, 7 Oct 2002 21:12:25 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 21:12:25 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008011225.2EBF53DFC@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: minimum value on range for isisSysMaxAge Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:12:25 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 20 of draft mib-09, the range for isisSysMaxAge is defined as 1200..65535. Since some vendors are allowing a value as low as 350 seconds, should we modify the range to be 350..65535? -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 21:33:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12924 for ; Mon, 7 Oct 2002 21:33:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981XEv22580; Mon, 7 Oct 2002 21:33:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981Ufv22493 for ; Mon, 7 Oct 2002 21:30:41 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12681 for ; Mon, 7 Oct 2002 21:28:29 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 4CAC33DEF; Mon, 7 Oct 2002 21:30:29 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 21:30:29 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008013029.4CAC33DEF@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: remove comments lines on such-and-such Groups Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:30:29 -0400 (EDT) Content-Transfer-Encoding: 7bit In the draft mib-09, there are several comment lines included that "could" be removed for one of two reasons. Either they say that the group is not supported (e.g. ES Adjacency) or the text is redundant (either with the COMPLIANCE statements or with other comments on Table's that immediately follow the group comments). Anyways, the locations and groups are found on: pg 24: System Integrated Group comments pg 29: Circuit Group comments pg 48: Circuit IS Group comments pg 48: IS Adjacency Group comments pg 53: IS Adjacency IP Group comments pg 54: IS Adjacency Integrated Group comments pg 55: ES Adjacency Group comments pg 55: Reachable Address Group comments pg 61: IP Reachable Address Group comments pg 64: Circuit CLNS Group comments pg 65: IP Destination Group (and Table) comments -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 21:41:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13301 for ; Mon, 7 Oct 2002 21:41:25 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981dOv23354; Mon, 7 Oct 2002 21:39:24 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981aCv22708 for ; Mon, 7 Oct 2002 21:36:12 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12950 for ; Mon, 7 Oct 2002 21:33:59 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 590273E2D; Mon, 7 Oct 2002 21:35:59 -0400 (EDT) To: jparker@axiowave.com, lliu@chiaro.com, isis-wg@ietf.org Subject: [Isis-wg] RE: isisRedistributeAddrTable in mib09 Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 21:35:59 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008013559.590273E2D@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:35:59 -0400 (EDT) Content-Transfer-Encoding: 7bit Jeff, The problem is that this is one table for which platform independence cannot probably be achieved. Every vendor usually has leaking tied into route policies since route ranges can come into play as well as only leaking internal vs external ISIS routes, etc. I don't know that we can create one table in the ISIS MIB that replaces all of this functionality. My 2 cents, Don --- On Wed 09/25, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: lliu@chiaro.com, isis-wg@ietf.org Date: Wed, 25 Sep 2002 13:18:47 -0400 Subject: [Isis-wg] RE: isisRedistributeAddrTable in mib09 > > > Jeff, > > > > My question was triggered by the discussion on the mailing > > list a while ago > > about up/down bit referring to "IS-IS extensions for Traffic > > Engineering" > > draft v.04 section 5.1: > > > > "If a prefix is advertised from an area to another area at > > the same level, > > then the up/down bit shall be set to 1. This situation can > > arise when a > > router implements multiple virtual routers at the same level, but in > > different areas.". > > > > Can we use isisRedistributeAddrTable for all the up/down bit set to > 1 > > routes? > > > > regards, > > Laura > > Laura - > The goal is to have a platform independent way to specify > which routes can be leaked down from L2 to L1. > > - jeff parker > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 21:48:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13413 for ; Mon, 7 Oct 2002 21:48:53 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981mCv23698; Mon, 7 Oct 2002 21:48:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981jcv23615 for ; Mon, 7 Oct 2002 21:45:38 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13332 for ; Mon, 7 Oct 2002 21:43:26 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 5AC9E3E2B; Mon, 7 Oct 2002 21:45:26 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 21:45:26 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008014526.5AC9E3E2B@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: comments on text comments for Circuit Table Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:45:26 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 29 of the mib-09 draft, the comments for Circuit Table read: -- Each broadcast or point-to-point interface on the system -- corresponds to one entry in the Circuit table. There may be -- many X.25 DA circuit entries in the Circuit table for an -- X.25 interface. I'd like to propose the following for readability: -- Each broadcast or point-to-point interface on the system -- corresponds to one entry in the Circuit table. However, there -- may be multiple X.25 DA circuit entries in the Circuit table -- for a given X.25 interface. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 21:54:17 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13525 for ; Mon, 7 Oct 2002 21:54:17 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981s7v23857; Mon, 7 Oct 2002 21:54:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981p6v23776 for ; Mon, 7 Oct 2002 21:51:06 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13423 for ; Mon, 7 Oct 2002 21:48:53 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 726583E2C; Mon, 7 Oct 2002 21:50:53 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 21:50:53 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008015053.726583E2C@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: blank references on mesh group attributes Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:50:53 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 33 of the mib-09 draft, the REFERENCE clauses for isisCirc- MeshGroupEnabled and isisCircMeshGroup are both blank. Do we want to refer to RFC2973 or remove them? -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:00:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13651 for ; Mon, 7 Oct 2002 22:00:27 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98207v24058; Mon, 7 Oct 2002 22:00:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981vZv23959 for ; Mon, 7 Oct 2002 21:57:35 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13554 for ; Mon, 7 Oct 2002 21:55:23 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id CB3563E2B; Mon, 7 Oct 2002 21:57:22 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 21:57:22 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008015722.CB3563E2B@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: text for isisCircMeshGroup Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:57:22 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 33 of the mib-09 draft, in the DESCRIPTION text for isisCircMeshGroup, the final sentence needs to also say "or blocked". Per RFC 2973, the integer value for group "is valid only if the value of meshGroupEnabled attribute is 'meshSet'." -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:03:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13741 for ; Mon, 7 Oct 2002 22:03:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98233v24183; Mon, 7 Oct 2002 22:03:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g981xbv24016 for ; Mon, 7 Oct 2002 21:59:37 -0400 Received: from gnat.inet.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA13588 for ; Mon, 7 Oct 2002 21:57:24 -0400 (EDT) Received: from extremenetworks.com (unknown [10.30.20.242]) by gnat.inet.org (Postfix) with ESMTP id F387467107; Mon, 7 Oct 2002 18:14:49 -0400 (EDT) Subject: Re: [Isis-wg] MIB: should we include Auth settings? Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v546) Cc: isis-wg@ietf.org To: dgoodspe@excite.com From: RJ Atkinson In-Reply-To: <20021008004134.389E13E22@xmxpita.excite.com> Message-Id: <90394EDE-DA61-11D6-B058-00039357A82A@extremenetworks.com> Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.546) Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 21:59:22 -0400 Content-Transfer-Encoding: 7bit On Monday, Oct 7, 2002, at 20:41 America/Montreal, Don Goodspeed wrote: > > All, > > Should we include any MIB attributes for Authentication settings > in the ISIS MIB? No. That would create operational security problems. We discussed the topic at some length a while back. The current absence of authentication related data is quite deliberate. Ran rja@extremenetworks.com _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:07:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13832 for ; Mon, 7 Oct 2002 22:07:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98268v24326; Mon, 7 Oct 2002 22:06:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9823nv24215 for ; Mon, 7 Oct 2002 22:03:49 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13696 for ; Mon, 7 Oct 2002 22:01:37 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id DB1863E32; Mon, 7 Oct 2002 22:03:36 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:03:36 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008020336.DB1863E32@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: UpTime attributes are better as LastUpTime attributes Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:03:36 -0400 (EDT) Content-Transfer-Encoding: 7bit The two UpTime-defined attributes in the mib-09 draft (isisCircUpTime on page 33 and isisISAdjUpTime on page 49) are measured in seconds since the circuit or adjacency last entered the 'Up' state. These two attributes should probably be changes to ...LastUpTime attributes measures in TimeTicks. Instead of being updated every second, they only need to set when the 'Up' event happens, and be set to the value of sysUpTime when that occurs. NMS systems can take care of the subtraction to display the time since 'up' based on the current value of sysUpTime. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:10:42 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13959 for ; Mon, 7 Oct 2002 22:10:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982A5v25046; Mon, 7 Oct 2002 22:10:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9827Sv24950 for ; Mon, 7 Oct 2002 22:07:28 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13791 for ; Mon, 7 Oct 2002 22:05:15 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 42F433E32; Mon, 7 Oct 2002 22:07:12 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:07:12 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008020712.42F433E32@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: should we include "passive" under isisCircLevel as well? Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:07:12 -0400 (EDT) Content-Transfer-Encoding: 7bit Currently, we have an attribute for isisCircPassiveCircuit in the mib-09 draft. Should we also include a per-level setting for each circuit in the isisCircLevelTable? -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:15:35 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14158 for ; Mon, 7 Oct 2002 22:15:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982F4v25204; Mon, 7 Oct 2002 22:15:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982CKv25136 for ; Mon, 7 Oct 2002 22:12:20 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA13922 for ; Mon, 7 Oct 2002 22:10:07 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 42B3E3E2A; Mon, 7 Oct 2002 22:12:07 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:12:07 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008021207.42B3E3E2A@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: isisCircLevelDesIS should be defined as size 0|7 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:12:07 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 36 of the mib-09 draft, isisCircLevelDesIS is defined as a being 0..7 octets, but in the text, this value could be either be seven octets or a null string of zero octects. The SYNTAX clause should reflect this as: SYNTAX OCTET STRING (SIZE (0|7)) -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:18:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14262 for ; Mon, 7 Oct 2002 22:18:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982Htv25348; Mon, 7 Oct 2002 22:17:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982Fcv25221 for ; Mon, 7 Oct 2002 22:15:38 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14033 for ; Mon, 7 Oct 2002 22:13:25 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 5D6513E0C; Mon, 7 Oct 2002 22:15:25 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:15:25 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008021525.5D6513E0C@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: text for isisSysStatLSPDbaseOloads Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:15:25 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 41 of the mib-09 draft, the DESCRIPTION text for the isisSysStatLSPDbaseOloads attribute reads: "Number of times the LSP L1 database has become overloaded." Since this attribute is index'ed by level, this text should be: "Number of times the LSP database for this level has become overloaded." -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:21:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14330 for ; Mon, 7 Oct 2002 22:21:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982Kxv25495; Mon, 7 Oct 2002 22:20:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982I0v25366 for ; Mon, 7 Oct 2002 22:18:00 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14187 for ; Mon, 7 Oct 2002 22:15:48 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 056D93E0C; Mon, 7 Oct 2002 22:17:48 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:17:48 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008021748.056D93E0C@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: include # of adjacencies in isisCircuitCounterTable? Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:17:48 -0400 (EDT) Content-Transfer-Encoding: 7bit In the isisCircuitCounterTable, should we include an attribute for the # of adjacencies at that level? I know it's not a true counter, but this table is index'ed correctly for this attribute. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:24:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14384 for ; Mon, 7 Oct 2002 22:24:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982O3v25627; Mon, 7 Oct 2002 22:24:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982Lpv25525 for ; Mon, 7 Oct 2002 22:21:51 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14289 for ; Mon, 7 Oct 2002 22:19:38 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 7A74D3E0C; Mon, 7 Oct 2002 22:21:38 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:21:38 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008022138.7A74D3E0C@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: should we have an isisPacketCounterUnknowns Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:21:38 -0400 (EDT) Content-Transfer-Encoding: 7bit Should we have an attribute to track unknown packet types in the isisPacketCounterTable? -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:27:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14453 for ; Mon, 7 Oct 2002 22:27:26 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982R8v25754; Mon, 7 Oct 2002 22:27:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982Nnv25616 for ; Mon, 7 Oct 2002 22:23:49 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14328 for ; Mon, 7 Oct 2002 22:21:36 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 49D023E0C; Mon, 7 Oct 2002 22:23:36 -0400 (EDT) To: isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: UpTime attributes are better as LastUpTime attributes Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:23:36 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008022336.49D023E0C@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:23:36 -0400 (EDT) Content-Transfer-Encoding: 7bit Sorry, that's page 51, not page 49 as I indicated below. -don --- On Mon 10/07, Don Goodspeed wrote: From: Don Goodspeed [mailto: dgoodspe@excite.com] To: isis-wg@ietf.org Date: Mon, 7 Oct 2002 22:03:36 -0400 (EDT) Subject: [Isis-wg] MIB: UpTime attributes are better as LastUpTime attributes > > The two UpTime-defined attributes in the mib-09 draft (isisCircUpTime > on page 33 and isisISAdjUpTime on page 49) are measured in seconds > since the circuit or adjacency last entered the 'Up' state. > > These two attributes should probably be changes to ...LastUpTime > attributes measures in TimeTicks. Instead of being updated every > second, they only need to set when the 'Up' event happens, and be > set to the value of sysUpTime when that occurs. > > NMS systems can take care of the subtraction to display the time > since 'up' based on the current value of sysUpTime. > > -don > > ------------------------------------------------ > Changed your e-mail? Keep your contacts! Use this free e-mail change of > address service from Return Path. Register now! > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:30:20 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14647 for ; Mon, 7 Oct 2002 22:30:20 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982U4v25845; Mon, 7 Oct 2002 22:30:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982R0v25746 for ; Mon, 7 Oct 2002 22:27:00 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14380 for ; Mon, 7 Oct 2002 22:24:47 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 165EC3E33; Mon, 7 Oct 2002 22:26:47 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:26:47 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008022647.165EC3E33@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: 3WayAdjState in isisISAdjTable? Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:26:47 -0400 (EDT) Content-Transfer-Encoding: 7bit I think we need to define an attribute for the 3WayAdjState in the isisISAdjTable since this state is independant of the isisISAdjState attribute. The same enumerations could probably be used. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:33:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14993 for ; Mon, 7 Oct 2002 22:33:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982XCv25965; Mon, 7 Oct 2002 22:33:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982V2v25872 for ; Mon, 7 Oct 2002 22:31:02 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14529 for ; Mon, 7 Oct 2002 22:28:49 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id D2B913DF9; Mon, 7 Oct 2002 22:30:48 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:30:48 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008023048.D2B913DF9@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: split isisISAdjNeighSysID into 2 attributes Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:30:48 -0400 (EDT) Content-Transfer-Encoding: 7bit This attribute is found on page 59 of the mib-09 draft, and serves 2 purposes. One is to indicate the neighbor system ID (which is seven octets) and the other is to indicate an extended circuit ID only if the circuit is p2p and 3way handshaking is enabled. I propose that we split this attribute into two. Keep the name of the existing attribute, but contrain it's size to seven octets. The new attribute "isisISAdjNeighExtendedCircID" would contain either a zero octet string or a four octet string. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:36:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15113 for ; Mon, 7 Oct 2002 22:36:28 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982a3v26063; Mon, 7 Oct 2002 22:36:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982Wsv25951 for ; Mon, 7 Oct 2002 22:32:54 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14697 for ; Mon, 7 Oct 2002 22:30:41 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 9878D3DF9; Mon, 7 Oct 2002 22:32:41 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:32:41 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008023241.9878D3DF9@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: isisRAFullMetric can be removed Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:32:41 -0400 (EDT) Content-Transfer-Encoding: 7bit Found on page 59 of the mib-09 draft, this attribute can be removed since the wide-metrics (I believe) do not apply to RA entries, only to IP ones. Of course, I've been wrong before.....-don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:40:58 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15399 for ; Mon, 7 Oct 2002 22:40:58 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982eCv26787; Mon, 7 Oct 2002 22:40:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982bpv26679 for ; Mon, 7 Oct 2002 22:37:51 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15062 for ; Mon, 7 Oct 2002 22:35:38 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 35BFE3DEB; Mon, 7 Oct 2002 22:37:38 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:37:38 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008023738.35BFE3DEB@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: re-index isisIPRATable to be in line with other IP tables Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:37:38 -0400 (EDT) Content-Transfer-Encoding: 7bit Found on page 61 of the mib-09 draft, the isisIPRATable is currently index'ed by isisSysInstance, isisIPRAIndex, and isisIPRAType. First, the type is not needed in the index since there cannot be both a manual and an automatic version of the route in the route table at the same time. Second, in keeping with the re-indexing of the other IP tables on the list recently, this table should be indexed by: isisSysInstance, isisIPRADest, isisIPRADestPrefixLen, and either the isisIPRASNPAAddress or a new attribute for isisIPRADestNextHop -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:43:11 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15517 for ; Mon, 7 Oct 2002 22:43:11 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982h3v26894; Mon, 7 Oct 2002 22:43:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982dIv26714 for ; Mon, 7 Oct 2002 22:39:18 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15150 for ; Mon, 7 Oct 2002 22:37:05 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 29F4E3E0C; Mon, 7 Oct 2002 22:39:05 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:39:05 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008023905.29F4E3E0C@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: change to MAX-ACCESS of isisIPRAType Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:39:05 -0400 (EDT) Content-Transfer-Encoding: 7bit If the isisIPRAType attribute found on page 62 of the mib-09 draft is removed from being an index into the isisIPRATable, it's MAX- ACCESS clause needs to change from "not-accessible" to "read-create". -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:46:15 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15595 for ; Mon, 7 Oct 2002 22:46:15 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982jrv27068; Mon, 7 Oct 2002 22:45:53 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982gRv26881 for ; Mon, 7 Oct 2002 22:42:27 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15291 for ; Mon, 7 Oct 2002 22:40:14 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 622193DF9; Mon, 7 Oct 2002 22:42:14 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:42:14 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008024214.622193DF9@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: modified text for isisRejectedAdjacency Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:42:14 -0400 (EDT) Content-Transfer-Encoding: 7bit Since an ISIS adjacency can be rejected for any # of reasons these days, the DESCRIPTION text for the isisRejectedAdjacency notification on page 73 of the mib-09 draft should reflect this. One could modify "... due to a lack of resources." to be "...due to a lack of resources, or any other reason." These days, an adjacency "could" be rejected for having an invalid level, an incorrect IP address for the subnet, an invalid authentication key, etc. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:56:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15756 for ; Mon, 7 Oct 2002 22:56:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982u5v27394; Mon, 7 Oct 2002 22:56:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982rAv27314 for ; Mon, 7 Oct 2002 22:53:10 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15665 for ; Mon, 7 Oct 2002 22:50:56 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 92F5D3E28; Mon, 7 Oct 2002 22:52:56 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:52:56 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008025256.92F5D3E28@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: include isisPduFragment on additional notifications Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:52:56 -0400 (EDT) Content-Transfer-Encoding: 7bit The isisPduFragment var-bind should be included for both the isisRejectedAdjacency and isisProtocolsSupportedMismatch notifications, since it's usually a hello packet that causes these events, not an LSP. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 7 22:59:18 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15859 for ; Mon, 7 Oct 2002 22:59:18 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982x4v27518; Mon, 7 Oct 2002 22:59:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g982t5v27379 for ; Mon, 7 Oct 2002 22:55:05 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15693 for ; Mon, 7 Oct 2002 22:52:52 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 7A7163DF9; Mon, 7 Oct 2002 22:54:52 -0400 (EDT) To: isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe9.nwk.excite.com via HTTP; Mon, 07 Oct 2002 22:54:52 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008025452.7A7163DF9@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: remove isisLSPSize from isisAreaMismatch notification Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 7 Oct 2002 22:54:52 -0400 (EDT) Content-Transfer-Encoding: 7bit On page 72 of the mib-09 draft, the isisAreaMismatch notification includes the isisLSPSize varbind, but since this is always caused by a hello PDU, we can probably remove the isisLSPSize from being a varbind. -don ------------------------------------------------ Changed your e-mail? Keep your contacts! Use this free e-mail change of address service from Return Path. Register now! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 05:04:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03911 for ; Tue, 8 Oct 2002 05:04:57 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9893iv21105; Tue, 8 Oct 2002 05:03:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g988xsv20963 for ; Tue, 8 Oct 2002 04:59:54 -0400 Received: from net4u.net4u.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03834 for ; Tue, 8 Oct 2002 04:57:48 -0400 (EDT) Received: from net4u.ch ([195.15.182.49]) by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g988xmq26164; Tue, 8 Oct 2002 10:59:49 +0200 Message-ID: <3DA29E53.4080706@net4u.ch> From: "Antoni B. Przygienda" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dgoodspe@excite.com CC: isis-wg@ietf.org Subject: Re: [Isis-wg] MIB: need for isisOverloadTimeLeft References: <20021008003354.2F1143DEF@xmxpita.excite.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 08 Oct 2002 01:58:59 -0700 Content-Transfer-Encoding: 7bit Don Goodspeed wrote: >Since many implemenations allow overload to be set for a given time, >we should have a MIB attribute called something like >isisSysOverloadTimeLeft (or TimeRemaining) that would serve two >functions. > >When set along with isisSysSetOverload, would set overload for the >configured time period (unit should be in seconds). When read, >it would show the time remaining in the overload state. If not set, >or if set to zero, when isisSysSetOverload is set, means an infinite >overload period (which is the current operation). > > actually, the intent is often to overload after the bootup for a certain amount of seconds so you may want more variables to get that behavior -- tony > > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 05:20:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04127 for ; Tue, 8 Oct 2002 05:20:05 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g989Ixv22143; Tue, 8 Oct 2002 05:18:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98918v21009 for ; Tue, 8 Oct 2002 05:01:08 -0400 Received: from net4u.net4u.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03840 for ; Tue, 8 Oct 2002 04:59:03 -0400 (EDT) Received: from net4u.ch ([195.15.182.49]) by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g98913q26327; Tue, 8 Oct 2002 11:01:04 +0200 Message-ID: <3DA29E9E.9050003@net4u.ch> From: "Antoni B. Przygienda" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: dgoodspe@excite.com CC: isis-wg@ietf.org Subject: Re: [Isis-wg] MIB: minimum value on range for isisSysMaxAge References: <20021008011225.2EBF53DFC@xmxpita.excite.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 08 Oct 2002 02:00:14 -0700 Content-Transfer-Encoding: 7bit Don Goodspeed wrote: >On page 20 of draft mib-09, the range for isisSysMaxAge is defined >as 1200..65535. Since some vendors are allowing a value as low >as 350 seconds, should we modify the range to be 350..65535? > > my take would be, get it down maybe even 60 seconds or so. Why have MIB limiting what can be done. But anyway, I would assume a specific MIB implementaitn could ignore the defined values (but that leaves problems with NMSes written by third-parties). Good topic -- tony > > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 05:22:26 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA04192 for ; Tue, 8 Oct 2002 05:22:25 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g989Kxv22266; Tue, 8 Oct 2002 05:20:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9892Bv21044 for ; Tue, 8 Oct 2002 05:02:11 -0400 Received: from net4u.net4u.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA03861 for ; Tue, 8 Oct 2002 05:00:06 -0400 (EDT) Received: from net4u.ch ([195.15.182.49]) by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g98924q26466; Tue, 8 Oct 2002 11:02:05 +0200 Message-ID: <3DA29EDB.3020203@net4u.ch> From: "Antoni B. Przygienda" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: RJ Atkinson CC: dgoodspe@excite.com, isis-wg@ietf.org Subject: Re: [Isis-wg] MIB: should we include Auth settings? References: <90394EDE-DA61-11D6-B058-00039357A82A@extremenetworks.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 08 Oct 2002 02:01:15 -0700 Content-Transfer-Encoding: 7bit RJ Atkinson wrote: > > On Monday, Oct 7, 2002, at 20:41 America/Montreal, Don Goodspeed wrote: > >> >> All, >> >> Should we include any MIB attributes for Authentication settings >> in the ISIS MIB? > > > No. That would create operational security problems. We discussed the > topic at some length a while back. The current absence of authentication > related data is quite deliberate. yes, my experience was taht any passwords/security keys in MIBs were a simple backdoor into the system so far -- tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 09:35:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11834 for ; Tue, 8 Oct 2002 09:35:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98DYMv03857; Tue, 8 Oct 2002 09:34:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98DUlv03735 for ; Tue, 8 Oct 2002 09:30:47 -0400 Received: from mta2 (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11584 for ; Tue, 8 Oct 2002 09:28:36 -0400 (EDT) Received: from mta2 (localhost [127.0.0.1]) by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26 2002)) with ESMTP id <0H3O007FH083Z2@mta2.huawei.com> for isis-wg@ietf.org; Tue, 08 Oct 2002 21:31:16 +0800 (CST) Received: from mailin.huawei.com ([10.18.1.252]) by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26 2002)) with ESMTP id <0H3O007DU082WL@mta2.huawei.com> for isis-wg@ietf.org; Tue, 08 Oct 2002 21:31:15 +0800 (CST) Received: from CL5002VJAMRIT ([10.18.4.151]) by mailin.huawei.com (Netscape Messaging Server 4.15) with ESMTP id H3O09P00.625 for ; Tue, 08 Oct 2002 21:32:13 +0800 From: Vijay Amrit Agrawal To: isis Message-id: <006701c26ed0$c5ca7d30$9704120a@in.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Mailer: Microsoft Outlook Express 5.50.4133.2400 Content-type: multipart/alternative; boundary="Boundary_(ID_AWXQSUJW+DwPJpjE/IALug)" X-Priority: 3 X-MSMail-priority: Normal Subject: [Isis-wg] Regarding router id TLV Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 08 Oct 2002 19:14:06 +0530 This is a multi-part message in MIME format. --Boundary_(ID_AWXQSUJW+DwPJpjE/IALug) Content-type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 7BIT Posting for a colleague: I have few queries regarding router id TLV in extension for Traffic Engineering forISIS 1. Can we have a multiple router id TLV in different fragments ?? 2. In OSPF the router id TLV and LInk TLV are tied together in a opaque LSA.. In ISIS TE draft no relation is specified clearly regarding the router id TLV and Extended IS reachability TLV. Can ISIS also follow the same approach as of OSPF ?? Will there not be any interoperability issues ?? thanx & rgds satish hampali (For some strange reason few of my colleagues are not able to post directly to IS-IS mailing list even after registration. Is anyone else having the same problem? - Vijay) --Boundary_(ID_AWXQSUJW+DwPJpjE/IALug) Content-type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 7BIT
Posting for a colleague:
I have few queries regarding router id TLV in extension for Traffic Engineering forISIS
 
1. Can we have a multiple router id TLV in different fragments ??
2. In OSPF the router id TLV and LInk TLV are tied together in a opaque LSA.. In ISIS TE draft no relation  is specified clearly regarding the router id TLV and Extended IS reachability TLV.  Can ISIS also follow the same approach as of OSPF ?? Will there not be any interoperability issues ??
 
thanx & rgds
satish hampali
(For some strange reason few of my colleagues are not able to post directly to IS-IS mailing list even after registration. Is anyone else having the same problem? - Vijay)
 
--Boundary_(ID_AWXQSUJW+DwPJpjE/IALug)-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 09:51:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13069 for ; Tue, 8 Oct 2002 09:51:24 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98DoBv05181; Tue, 8 Oct 2002 09:50:11 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Dl7v05035 for ; Tue, 8 Oct 2002 09:47:07 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12574 for ; Tue, 8 Oct 2002 09:45:00 -0400 (EDT) Message-ID: From: Jeff Parker To: "'dgoodspe@excite.com'" , isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: should we include Auth settings? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 09:46:48 -0400 > All, > > Should we include any MIB attributes for Authentication settings > in the ISIS MIB? Possible attributes would include at each of > {system, level, circuit, circuit-level} attributes for: > auth-type (none, password, or MD5) > auth-password (or auth-key): would be write-only > auth-check > > Possible additional attributes might include settings for: > hello-auth-type > hello-auth-password (or key) > hello-auth-check > > I know some vendors also allow control of security on other types > (psnp's, etc.) as well. This could be a can of worms, but I thought > I'd raise the issue. > > -don Don - You might want to check the archives on this. I had something similar, and was asked to remove it. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 10:08:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14187 for ; Tue, 8 Oct 2002 10:08:07 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98E7Av06197; Tue, 8 Oct 2002 10:07:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98E4Hv05827 for ; Tue, 8 Oct 2002 10:04:17 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13945 for ; Tue, 8 Oct 2002 10:02:10 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Subject: FW: [Isis-wg] MIB: isisCircLevelDesIS should be defined as size 0 |7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 10:04:03 -0400 As I'm working through Don's extensive set of suggestions, I'd like to reply in a point-to-point fashion on the smaller items, rather than spaming the list. However, my reply to Don address bounces. If someone (Don?) has a better address to use, I would be happy to conduct most of the minor corrections with a point-to-point, rather than broadcast, link. - jeff parker > On page 36 of the mib-09 draft, isisCircLevelDesIS is defined as > a being 0..7 octets, but in the text, this value could be either be > seven octets or a null string of zero octects. The SYNTAX clause > should reflect this as: > SYNTAX OCTET STRING (SIZE (0|7)) > > -don > > ------------------------------------------------ > Changed your e-mail? Keep your contacts! Use this free > e-mail change of address service from Return Path. Register now! > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 11:11:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17543 for ; Tue, 8 Oct 2002 11:11:57 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98FAKv10209; Tue, 8 Oct 2002 11:10:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98F47v09402 for ; Tue, 8 Oct 2002 11:04:07 -0400 Received: from rchss001.chiaro.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA17207 for ; Tue, 8 Oct 2002 11:01:59 -0400 (EDT) Received: (qmail 22465 invoked from network); 8 Oct 2002 14:54:38 -0000 Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81) by rchss001.chiaro.com with SMTP; 8 Oct 2002 14:54:38 -0000 Received: by MAIL with Internet Mail Service (5.5.2653.19) id ; Tue, 8 Oct 2002 10:03:34 -0500 Message-ID: From: Laura Liu To: dgoodspe@excite.com, isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r IP tables MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 10:03:33 -0500 --=_IS_MIME_Boundary Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: Don Goodspeed [mailto:dgoodspe@excite.com] > Sent: Monday, October 07, 2002 9:38 PM > To: isis-wg@ietf.org > Subject: [Isis-wg] MIB: re-index isisIPRATable to be in line > with other > IP tables > > > > Found on page 61 of the mib-09 draft, the isisIPRATable is currently > index'ed by isisSysInstance, isisIPRAIndex, and isisIPRAType. > > First, the type is not needed in the index since there cannot be > both a manual and an automatic version of the route in the route > table at the same time. > I totally agree. Instead of using type (manual or automatic) as index, it can be an attribute of each prefix. > Second, in keeping with the re-indexing of the other IP tables > on the list recently, this table should be indexed by: > isisSysInstance, isisIPRADest, isisIPRADestPrefixLen, and > either the isisIPRASNPAAddress or a new attribute for > isisIPRADestNextHop. And a new attribute for isisIPRASourceType, which indicate where the prefix learned from: static, directly connected, OSPF, BGP or ISIS. Laura > > -don > > ------------------------------------------------ > Changed your e-mail? Keep your contacts! Use this free > e-mail change of address service from Return Path. Register now! > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > --=_IS_MIME_Boundary Content-Type: text/plain;charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit ----------------------------------------- (on rchss001) This e-mail and any files transmitted with it are the property of Chiaro Networks, Ltd., and may contain confidential and privileged material for the sole use of the intended recipient(s) to whom this e-mail is addressed. If you are not one of the named recipient(s), or otherwise have reason to believe that you have received this message in error, please notify the sender and delete all copies from your system. Any other use, retention, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. --------------------------------------------------------- --=_IS_MIME_Boundary-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 13:53:48 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23844 for ; Tue, 8 Oct 2002 13:53:48 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Hpxv19353; Tue, 8 Oct 2002 13:51:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Hl3v19153 for ; Tue, 8 Oct 2002 13:47:03 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23522 for ; Tue, 8 Oct 2002 13:44:54 -0400 (EDT) Message-ID: From: Jeff Parker To: "'dgoodspe@excite.com'" , isis-wg@ietf.org Subject: RE: [Isis-wg] Updates to IS-IS MIB MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 13:46:53 -0400 > Dave, > > Do you have the isisLSPTable on the to-do list for the > IS-IS MIB? We had previously discussed methods on how > to do this, but I saw no mention in version -09 of > the draft. > > Thanks, > Don > > P.S. I'm getting ready to send emails with my comments on the > existing MIB draft. I'll be sending each issue separately since > some may generate zero discussion and others may generate more > discussion, and I like to keep issues separate from each other. Dan - I have it on the todo list, and have not folded it in. - JEFF parker - jparker@axiowave.com _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 13:55:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23910 for ; Tue, 8 Oct 2002 13:55:24 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98HsWv19478; Tue, 8 Oct 2002 13:54:32 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98HmIv19194 for ; Tue, 8 Oct 2002 13:48:18 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23580 for ; Tue, 8 Oct 2002 13:46:08 -0400 (EDT) Message-ID: From: Jeff Parker To: "'dgoodspe@excite.com'" , isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: ISPriority, any implementation allow zero? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 13:48:00 -0400 > On page 11 of draft mib-09, ISPriority's range is defined as 1..127. > > Do any current implementations allow a value of zero? If so, we > should probably modify the range to include zero. > > -don Don - Done - jeff _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 13:58:03 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA24026 for ; Tue, 8 Oct 2002 13:58:02 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Huwv19596; Tue, 8 Oct 2002 13:56:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98HnBv19267 for ; Tue, 8 Oct 2002 13:49:11 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23639 for ; Tue, 8 Oct 2002 13:47:01 -0400 (EDT) Message-ID: From: Jeff Parker To: "'dgoodspe@excite.com'" , isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: space needed on DEFVAL of isisSysSetOverload MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 13:48:53 -0400 > On page 19 of the draft mib-09, there needs to be a space after the > open brace on the DEFVAL declaration for isisSysSetOverload. > > Should be: > DEFVAL { overloadClear } > > -don Don - One of the changes since 9 was to split this into per-level info. This is now a boolean, and I think the space is there. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 14:00:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24149 for ; Tue, 8 Oct 2002 14:00:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Hwsv19665; Tue, 8 Oct 2002 13:58:54 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98HnPv19276 for ; Tue, 8 Oct 2002 13:49:25 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23643 for ; Tue, 8 Oct 2002 13:47:16 -0400 (EDT) Message-ID: From: Jeff Parker To: "'dgoodspe@excite.com'" , isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: text for isisCircMeshGroup MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 13:49:14 -0400 > On page 33 of the mib-09 draft, in the DESCRIPTION text for > isisCircMeshGroup, > the final sentence needs to also say "or blocked". Per RFC 2973, the > integer value for group "is valid only if the value of > meshGroupEnabled > attribute is 'meshSet'." > > -don Don - Thanks. Done. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 14:03:54 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24290 for ; Tue, 8 Oct 2002 14:03:54 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98I3Jv19917; Tue, 8 Oct 2002 14:03:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Hrov19431 for ; Tue, 8 Oct 2002 13:53:50 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23782 for ; Tue, 8 Oct 2002 13:51:40 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Subject: FW: [Isis-wg] MIB: isisCircLevelDesIS should be defined as size 0 |7 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 13:53:43 -0400 > Jeff, > > Personally, I'd as soon see the answers become part of > the archive, now that the questions have. :-) > > That would be the case even when the answer is "see > archive". Otherwise, to the reasonably attentive review, it > might seem that these questions were left unanswered. > > I would not worry that people will feel you're spamming > the list by responding in kind to Don's questions. I have followed the suggestion above, and I'm replying to the list on Don's suggestions. I think Don's review is important, and I'll try to keep the record stratight on the exchanges - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 14:07:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24414 for ; Tue, 8 Oct 2002 14:07:26 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98I6dv20079; Tue, 8 Oct 2002 14:06:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98HtCv19541 for ; Tue, 8 Oct 2002 13:55:12 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23823 for ; Tue, 8 Oct 2002 13:53:02 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Subject: [Isis-wg] MIB: ISLevel enumerations MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 13:55:05 -0400 > On page 11 of draft mib-09, ISLevel has the current enumerations: > area(1), domain(2), none(3) > > Should we instead utilize the more common names of: > l1(1), l2(2), none(3) > > or even: I've changed none to 0. This is TC is only used in one place, and it must be L1 or L2: L3 is not a valid choice - jeff parker - axiowave networks - echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 14:10:08 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24545 for ; Tue, 8 Oct 2002 14:10:07 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98I9dv20824; Tue, 8 Oct 2002 14:09:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98I6pv20159 for ; Tue, 8 Oct 2002 14:06:51 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24319 for ; Tue, 8 Oct 2002 14:04:41 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] Other Edits to IS-IS MIB Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 14:06:44 -0400 I deleted many of Don's mails after making the changes. I have made a dozen imediate changes, and will address larger changes soon. Here is the list I have so far of what I've done. -- Numerous edits from Dan Goodspeed -- Added 0 to ISPriority range -- Changed encoding of 'none' in ISLevel to 0, rather than 3 -- Replaced UpTime with TimeTicks -- Rewrote descriptions of CircUpTime and AdjUpTime -- Removed Comments on Depricated Groups -- Edited description of isisCircEntry -- Added References for MeshGroup and MeshGroupEnabled -- Updated description -- Remove L1 from isisSysStatLSPDbaseOloads description -- Added isisCircAdj to count adjacencies on circuit -- Added isisPacketCountUnknown -- Removed LSPSize from isisAreaMismatch -- Added isisPDUFragment to isisRejectedAdjacency -- Updated description - jeff parker - axiowave networks - echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 14:15:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24864 for ; Tue, 8 Oct 2002 14:15:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98IF0v21081; Tue, 8 Oct 2002 14:15:00 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98I7ov20777 for ; Tue, 8 Oct 2002 14:07:50 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24355 for ; Tue, 8 Oct 2002 14:05:40 -0400 (EDT) Message-ID: From: Jeff Parker To: "'dgoodspe@excite.com'" , isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: should we include "passive" under isisCircLeve l as well? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 14:07:40 -0400 > Currently, we have an attribute for isisCircPassiveCircuit in > the mib-09 draft. Should we also include a per-level setting > for each circuit in the isisCircLevelTable? > > -don I think of this as a per circuit attribute, as Laura Liu suggested. - jdp _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 14:29:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25346 for ; Tue, 8 Oct 2002 14:29:23 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98ISMv21642; Tue, 8 Oct 2002 14:28:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98INdv21531 for ; Tue, 8 Oct 2002 14:23:39 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25046 for ; Tue, 8 Oct 2002 14:21:29 -0400 (EDT) Message-ID: From: Jeff Parker To: isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r IP tables MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 14:23:33 -0400 > Found on page 61 of the mib-09 draft, the isisIPRATable is currently > index'ed by isisSysInstance, isisIPRAIndex, and isisIPRAType. > > First, the type is not needed in the index since there cannot be > both a manual and an automatic version of the route in the route > table at the same time. > > Second, in keeping with the re-indexing of the other IP tables > on the list recently, this table should be indexed by: > isisSysInstance, isisIPRADest, isisIPRADestPrefixLen, and > either the isisIPRASNPAAddress or a new attribute for > isisIPRADestNextHop > > -don Reworked to use different index. I included DestType to distinguish ipv4 from ipv6. The usual changes in MAX-ACCESS needed to make smicng happy. I'd love to find a way to reach Don directly with a copy before submitting a new version. Don? - jdp isisIPRAEntry OBJECT-TYPE SYNTAX IsisIPRAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry defines an IP Reachable Address to a network, subnetwork or host." INDEX { isisSysInstance, isisIPRAIndex, isisIPRADestType, isisIPRADest, isisIPRADestPrefixLen, isisIPRASNPAAddress } ::= { isisIPRATable 1 } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 14:32:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25455 for ; Tue, 8 Oct 2002 14:32:25 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98IW8v21879; Tue, 8 Oct 2002 14:32:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98ITIv21746 for ; Tue, 8 Oct 2002 14:29:18 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25195 for ; Tue, 8 Oct 2002 14:27:07 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] MIB: isisRAFullMetric can be removed MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 14:29:11 -0400 > Found on page 59 of the mib-09 draft, this attribute can be > removed since the wide-metrics (I believe) do not apply to > RA entries, only to IP ones. Of course, I've been wrong > before.....-don Done _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 14:59:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26396 for ; Tue, 8 Oct 2002 14:59:30 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98IwCv23430; Tue, 8 Oct 2002 14:58:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Isov23329 for ; Tue, 8 Oct 2002 14:54:50 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26175 for ; Tue, 8 Oct 2002 14:52:39 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] Don's MIB ToDo list Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 14:54:41 -0400 For those keeping score at home, what is left from Don's suggestions today. There are a half-dozen remaining points, with some thoughts on each. 1) isisLSPTable - On the todo list. May not make it into version 10 of mib. 2) isisSysOverloadTimeLeft - I think I had this once, and I'm trying to remember why it disappeared. 3) OperStatus is in the isisSys table and isisCircTable. Again, I think we had this once, and I wonder why it isn't there now. 4) isisRedistributeAddrTable - platform > independence cannot probably be achieved. > Every vendor > usually has leaking tied into route policies since > route ranges can come into play as well as only leaking > internal vs external ISIS routes, etc. I see Don's point, though I would like to think we could retain something. Any suggestions? Here is a snapshot of the contents. -- The Redistribution table defines addresses that should be leaked from -- L2 to L1 if isisSysL2toL1Leaking is enabled. isisRedistributeAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF IsisRedistributeAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides criteria to decide if a route should be leaked from L2 to L1 when Domain Wide Prefix leaking is enabled. Addresses that match the summary mask in the table will be announced at L1 by routers when isisSysL2toL1Leaking is enabled. Routes that fall into the ranges specified are are announced as is, without being summarized." ::= { isisSystem 6 } .... IsisRedistributeAddrEntry ::= SEQUENCE { isisRedistributeAddrType InetAddressType, isisRedistributeAddrAddress InetAddress, isisRedistributeAddrPrefixLen InetAddressPrefixLength, isisRedistributeAddrExistState RowStatus } 5) Add 3WayAdjState as well as isisISAdjState. I had hoped this could be combined. Will re-read RFC. - jeff parker - axiowave networks - echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 15:01:51 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26701 for ; Tue, 8 Oct 2002 15:01:51 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98J1Yv23629; Tue, 8 Oct 2002 15:01:34 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Iv7v23395 for ; Tue, 8 Oct 2002 14:57:07 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26226 for ; Tue, 8 Oct 2002 14:54:56 -0400 (EDT) Message-ID: From: Jeff Parker To: isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: split isisISAdjNeighSysID into 2 attributes MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 14:56:59 -0400 > This attribute is found on page 59 of the mib-09 draft, and > serves 2 purposes. One is to indicate the neighbor system > ID (which is seven octets) and the other is to indicate > an extended circuit ID only if the circuit is p2p and 3way > handshaking is enabled. > > I propose that we split this attribute into two. Keep the name > of the existing attribute, but contrain it's size to seven octets. > The new attribute "isisISAdjNeighExtendedCircID" would contain > either a zero octet string or a four octet string. > > -don I have added a "3WayEnabled" bit to the CircEntry (this is per circ, not per circ/level) and a 4 byte Extended Circ ID. I am using 0 to mean "not valid" - jeff parker isisCirc3WayEnabled OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Is this circuit enabled to run 3Way handshake?" ::= { isisCircEntry 14 } isisISAdjExtendedCircID OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The 4 byte Extended Circuit ID learned from the Neighbor during 3-way handshake, or 0." ::= { isisISAdjEntry 4 } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 15:23:59 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27568 for ; Tue, 8 Oct 2002 15:23:59 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98JNHv25183; Tue, 8 Oct 2002 15:23:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98JKKv25046 for ; Tue, 8 Oct 2002 15:20:20 -0400 Received: from rchss001.chiaro.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA27360 for ; Tue, 8 Oct 2002 15:18:09 -0400 (EDT) Received: (qmail 29811 invoked from network); 8 Oct 2002 19:10:54 -0000 Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81) by rchss001.chiaro.com with SMTP; 8 Oct 2002 19:10:54 -0000 Received: by MAIL with Internet Mail Service (5.5.2653.19) id ; Tue, 8 Oct 2002 14:19:50 -0500 Message-ID: From: Laura Liu To: Jeff Parker , isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r IP tables MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 14:19:48 -0500 --=_IS_MIME_Boundary Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: Jeff Parker [mailto:jparker@axiowave.com] > Sent: Tuesday, October 08, 2002 1:24 PM > To: isis-wg@ietf.org > Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with > othe r IP tables > > > > Found on page 61 of the mib-09 draft, the isisIPRATable is currently > > index'ed by isisSysInstance, isisIPRAIndex, and isisIPRAType. > > > > First, the type is not needed in the index since there cannot be > > both a manual and an automatic version of the route in the route > > table at the same time. > > > > Second, in keeping with the re-indexing of the other IP tables > > on the list recently, this table should be indexed by: > > isisSysInstance, isisIPRADest, isisIPRADestPrefixLen, and > > either the isisIPRASNPAAddress or a new attribute for > > isisIPRADestNextHop > > > > -don > > Reworked to use different index. I included DestType to > distinguish ipv4 from ipv6. The usual changes in MAX-ACCESS > needed to make smicng happy. > > I'd love to find a way to reach Don directly with a copy > before submitting a new version. Don? > > - jdp > > isisIPRAEntry OBJECT-TYPE > SYNTAX IsisIPRAEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Each entry defines an IP Reachable Address to a network, > subnetwork or host." > INDEX { isisSysInstance, > isisIPRAIndex, > isisIPRADestType, > isisIPRADest, > isisIPRADestPrefixLen, > isisIPRASNPAAddress } > ::= { isisIPRATable 1 } I think it would make more sense to use isisIPRADestNextHop as attribute instead of isisIPRASNPAAddress as index. My 2 cents, Laura --=_IS_MIME_Boundary Content-Type: text/plain;charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit ----------------------------------------- (on rchss001) This e-mail and any files transmitted with it are the property of Chiaro Networks, Ltd., and may contain confidential and privileged material for the sole use of the intended recipient(s) to whom this e-mail is addressed. If you are not one of the named recipient(s), or otherwise have reason to believe that you have received this message in error, please notify the sender and delete all copies from your system. Any other use, retention, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. --------------------------------------------------------- --=_IS_MIME_Boundary-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 15:33:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27988 for ; Tue, 8 Oct 2002 15:33:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98JWCv25561; Tue, 8 Oct 2002 15:32:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98JTLv25464 for ; Tue, 8 Oct 2002 15:29:21 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27706 for ; Tue, 8 Oct 2002 15:27:10 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Laura Liu'" , isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r IP tables MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 15:29:09 -0400 > > > isisIPRATable ... should be indexed by:.... > > > either the isisIPRASNPAAddress or a new attribute for > > > isisIPRADestNextHop > > > > > > -don > > > > Reworked to use [isisIPRASNPAAddress] > > > > - jdp > > I think it would make more sense to use > isisIPRADestNextHop as attribute > > Laura Comments? I don't need to rev this in real time. Current table below - jeff parker isisIPRASNPAAddress isisIPRATable OBJECT-TYPE SYNTAX SEQUENCE OF IsisIPRAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table of IP Reachable Addresses to networks, subnetworks or hosts either manually configured or learned from another protocol." ::= { isisIPReachAddr 1 } .... IsisIPRAEntry ::= SEQUENCE { isisIPRAIndex Integer32, isisIPRADestType InetAddressType, isisIPRADest InetAddress, isisIPRADestPrefixLen InetAddressPrefixLength, isisIPRASNPAAddress OSINSAddress, isisIPRAType INTEGER, isisIPRAExistState RowStatus, isisIPRAAdminState AdminState, isisIPRAMetric DefaultMetric, isisIPRAMetricType MetricType, isisIPRAFullMetric FullMetric } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 16:33:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29781 for ; Tue, 8 Oct 2002 16:33:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98KWqv28760; Tue, 8 Oct 2002 16:32:52 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98KT6v28586 for ; Tue, 8 Oct 2002 16:29:06 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA29522 for ; Tue, 8 Oct 2002 16:26:56 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Laura Liu'" , Jeff Parker , isis-wg@ietf.org Subject: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r I P tables MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 16:28:56 -0400 > I think it would make more sense to use isisIPRADestNextHop > as attribute > instead of isisIPRASNPAAddress as index. > > Laura I've tossed SNPA, and replaced with IP Next hop. If there is need to retain of next hop types other than IPV4 and IPV6, drop me a line. - jeff parker isisIPRAEntry OBJECT-TYPE SYNTAX IsisIPRAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry defines an IP Reachable Address to a network, subnetwork or host." INDEX { isisSysInstance, isisIPRAIndex, isisIPRADestType, isisIPRADest, isisIPRADestPrefixLen } ::= { isisIPRATable 1 } IsisIPRAEntry ::= SEQUENCE { isisIPRAIndex Integer32, isisIPRADestType InetAddressType, isisIPRADest InetAddress, isisIPRADestPrefixLen InetAddressPrefixLength, isisIPRANextHopType InetAddressType, isisIPRANextHop InetAddress, isisIPRAType INTEGER, isisIPRAExistState RowStatus, isisIPRAAdminState AdminState, isisIPRAMetric DefaultMetric, isisIPRAMetricType MetricType, isisIPRAFullMetric FullMetric } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 8 18:45:04 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02679 for ; Tue, 8 Oct 2002 18:45:04 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98MiDv03213; Tue, 8 Oct 2002 18:44:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98MfVv03156 for ; Tue, 8 Oct 2002 18:41:31 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02602 for ; Tue, 8 Oct 2002 18:39:19 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 3ECA8B71F; Tue, 8 Oct 2002 18:41:19 -0400 (EDT) To: jparker@axiowave.com, isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: split isisISAdjNeighSysID into 2 attributes Received: from [63.104.212.252] by xprdmailfe18.nwk.excite.com via HTTP; Tue, 08 Oct 2002 18:41:19 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008224119.3ECA8B71F@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 18:41:19 -0400 (EDT) Content-Transfer-Encoding: 7bit Jeff, I forgot to mention it should be numeric, but we probably want to make it an Unsigned32, not Integer32 since this # will not be negative. Also, in the MIB update you sent me, you list the ExtendedCircID after NeighSysID, but you put it just after SNPAAddress (oid 4 in the table). -don --- On Tue 10/08, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: isis-wg@ietf.org Date: Tue, 8 Oct 2002 14:56:59 -0400 Subject: RE: [Isis-wg] MIB: split isisISAdjNeighSysID into 2 attributes > > This attribute is found on page 59 of the mib-09 draft, and > > serves 2 purposes. One is to indicate the neighbor system > > ID (which is seven octets) and the other is to indicate > > an extended circuit ID only if the circuit is p2p and 3way > > handshaking is enabled. > > > > I propose that we split this attribute into two. Keep the name > > of the existing attribute, but contrain it's size to seven octets. > > The new attribute "isisISAdjNeighExtendedCircID" would > contain > > either a zero octet string or a four octet string. > > > > -don > > I have added a "3WayEnabled" bit to the CircEntry (this is > per circ, not per circ/level) and a 4 byte Extended Circ ID. > I am using 0 to mean "not valid" > > - jeff parker > > > isisCirc3WayEnabled OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "Is this circuit enabled to run 3Way handshake?" > ::= { isisCircEntry 14 } > > isisISAdjExtendedCircID OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The 4 byte Extended Circuit ID learned from the > Neighbor during 3-way handshake, or 0." > ::= { isisISAdjEntry 4 } > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ 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-admin@ietf.org Tue Oct 8 18:48:04 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02757 for ; Tue, 8 Oct 2002 18:48:04 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Ml3v03285; Tue, 8 Oct 2002 18:47:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98MhXv03204 for ; Tue, 8 Oct 2002 18:43:33 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02635 for ; Tue, 8 Oct 2002 18:41:21 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 0EEE6B71F; Tue, 8 Oct 2002 18:43:21 -0400 (EDT) To: jparker@axiowave.com, lliu@chiaro.com, jparker@axiowave.com, isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r I P tables Received: from [63.104.212.252] by xprdmailfe18.nwk.excite.com via HTTP; Tue, 08 Oct 2002 18:43:21 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008224321.0EEE6B71F@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 18:43:21 -0400 (EDT) Content-Transfer-Encoding: 7bit Jeff, We may want to keep SNPAAddress in the table, just not as an INDEX to the table. But I do prefer the indexing by NextHop IP address. Thanks, Don --- On Tue 10/08, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: lliu@chiaro.com, jparker@axiowave.com, isis-wg@ietf.org Date: Tue, 8 Oct 2002 16:28:56 -0400 Subject: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r I P tables > > > I think it would make more sense to use isisIPRADestNextHop > > as attribute > > instead of isisIPRASNPAAddress as index. > > > > Laura > > I've tossed SNPA, and replaced with IP Next hop. > If there is need to retain of next hop types other > than IPV4 and IPV6, drop me a line. > > - jeff parker > > isisIPRAEntry OBJECT-TYPE > SYNTAX IsisIPRAEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Each entry defines an IP Reachable Address to a > network, > subnetwork or host." > INDEX { isisSysInstance, > isisIPRAIndex, > isisIPRADestType, > isisIPRADest, > isisIPRADestPrefixLen } > ::= { isisIPRATable 1 } > > IsisIPRAEntry ::= > SEQUENCE { > isisIPRAIndex > Integer32, > isisIPRADestType > InetAddressType, > isisIPRADest > InetAddress, > isisIPRADestPrefixLen > InetAddressPrefixLength, > isisIPRANextHopType > InetAddressType, > isisIPRANextHop > InetAddress, > isisIPRAType > INTEGER, > isisIPRAExistState > RowStatus, > isisIPRAAdminState > AdminState, > isisIPRAMetric > DefaultMetric, > isisIPRAMetricType > MetricType, > isisIPRAFullMetric > FullMetric > } > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ 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-admin@ietf.org Tue Oct 8 19:00:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02991 for ; Tue, 8 Oct 2002 19:00:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98MxDv03585; Tue, 8 Oct 2002 18:59:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g98Mu4v03524 for ; Tue, 8 Oct 2002 18:56:04 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02862 for ; Tue, 8 Oct 2002 18:53:52 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id F1C7FB6DD; Tue, 8 Oct 2002 18:55:51 -0400 (EDT) To: jparker@axiowave.com, isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: should we include Auth settings? Received: from [63.104.212.252] by xprdmailfe18.nwk.excite.com via HTTP; Tue, 08 Oct 2002 18:55:51 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021008225551.F1C7FB6DD@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 18:55:51 -0400 (EDT) Content-Transfer-Encoding: 7bit Yes, I see it was removed between versions 3 and 4 of the MIB. It was hard to find all of the archives, though (hint, hint to ADs). It would be nice to have both the isis and isis-wg archives together and be searchable. I'd really like to see this on all the IETF WGs instead of on a one-by-one basis. Cheers, Don --- On Tue 10/08, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: dgoodspe@excite.com, isis-wg@ietf.org Date: Tue, 8 Oct 2002 09:46:48 -0400 Subject: RE: [Isis-wg] MIB: should we include Auth settings? > > All, > > > > Should we include any MIB attributes for Authentication settings > > in the ISIS MIB? Possible attributes would include at each of > > {system, level, circuit, circuit-level} attributes for: > > auth-type (none, password, or MD5) > > auth-password (or auth-key): would be write-only > > auth-check > > > > Possible additional attributes might include settings for: > > hello-auth-type > > hello-auth-password (or key) > > hello-auth-check > > > > I know some vendors also allow control of security on other types > > (psnp's, etc.) as well. This could be a can of worms, but I thought > > I'd raise the issue. > > > > -don > > Don - > You might want to check the archives on this. > I had something similar, and was asked to remove it. > > - jeff parker > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ 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-admin@ietf.org Tue Oct 8 20:31:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04797 for ; Tue, 8 Oct 2002 20:31:19 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g990NXv07401; Tue, 8 Oct 2002 20:23:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g990KZv07353 for ; Tue, 8 Oct 2002 20:20:35 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA04536 for ; Tue, 8 Oct 2002 20:18:22 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 2516EB6EE; Tue, 8 Oct 2002 20:20:22 -0400 (EDT) To: jparker@axiowave.com, isis-wg@ietf.org Received: from [63.104.212.252] by xprdmailfe18.nwk.excite.com via HTTP; Tue, 08 Oct 2002 20:20:22 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021009002022.2516EB6EE@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Subject: [Isis-wg] MIB: Need for isisRedistributeAddrTable Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 8 Oct 2002 20:20:22 -0400 (EDT) Content-Transfer-Encoding: 7bit Jeff and all, I think I can clarify the usefulness of this table. We can use the table to show what routes "are" being leaked based on policies for leaking that are defined elsewhere. We can keep the ExistState attribute, although some implementation may not allow it to be controlled via SNMP. We should also include an isisRedistributeType attribute (not part of the index) for controlling whether this route prefix is automatic or manual. Some implementation will not allow this to be set via SNMP either (they'll always have only automatic routes in this table). Finally, we should dual-purpose the table and also show which routes are being leaked from L1 into L2 as well. Since a route can be leaked in only one direction, this does not need to be part of the index, and it's only two values would be leakL1ToL2(1) or leakL2ToL1(2). It would also be read-create, and have the same caveat that some implementations may implement this as read-only. I hope this will work for everyone -don --- On Tue 10/08, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: isis-wg@ietf.org Date: Tue, 8 Oct 2002 14:54:41 -0400 Subject: [Isis-wg] Don's MIB ToDo list > 4) isisRedistributeAddrTable - platform > > independence cannot probably be achieved. > > Every vendor > > usually has leaking tied into route policies since > > route ranges can come into play as well as only leaking > > internal vs external ISIS routes, etc. > > I see Don's point, though I would like to think > we could retain something. Any suggestions? Here > is a snapshot of the contents. > > -- The Redistribution table defines addresses that should be leaked from > -- L2 to L1 if isisSysL2toL1Leaking is enabled. > > isisRedistributeAddrTable OBJECT-TYPE > SYNTAX SEQUENCE OF IsisRedistributeAddrEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table provides criteria to decide if a route > should > be leaked from L2 to L1 when Domain Wide Prefix leaking is > enabled. > > Addresses that match the summary mask in the table will > be announced at L1 by routers when isisSysL2toL1Leaking > is enabled. Routes that fall into the ranges specified > are are announced as is, without being summarized." > ::= { isisSystem 6 } > .... > IsisRedistributeAddrEntry ::= > SEQUENCE { > isisRedistributeAddrType > InetAddressType, > isisRedistributeAddrAddress > InetAddress, > isisRedistributeAddrPrefixLen > InetAddressPrefixLength, > isisRedistributeAddrExistState > RowStatus > } ------------------------------------------------ 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-admin@ietf.org Wed Oct 9 00:01:03 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA08711 for ; Wed, 9 Oct 2002 00:01:03 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g993rdv17161; Tue, 8 Oct 2002 23:53:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g993o8v17097 for ; Tue, 8 Oct 2002 23:50:08 -0400 Received: from web8207.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id XAA08479 for ; Tue, 8 Oct 2002 23:47:54 -0400 (EDT) Message-ID: <20021009034957.80329.qmail@web8207.mail.in.yahoo.com> Received: from [202.9.170.75] by web8207.mail.in.yahoo.com via HTTP; Wed, 09 Oct 2002 04:49:57 BST From: =?iso-8859-1?q?Rajesh=20Saluja?= Subject: Re: [Isis-wg] Don's MIB ToDo list To: Jeff Parker , "ISIS-WG \(E-mail\)" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-464424340-1034135397=:79975" Content-Transfer-Encoding: 8bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 04:49:57 +0100 (BST) --0-464424340-1034135397=:79975 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Jeff Parker wrote: 5) Add 3WayAdjState as well as isisISAdjState. I had hoped this could be combined. Will re-read RFC. Jeff, 3 way state is different from 10589 adjacency state. Thanks, Rajesh Yahoo! Properties Special Buy, sell, rent...your flat, or even post an ad --0-464424340-1034135397=:79975 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit

  Jeff Parker <jparker@axiowave.com> wrote:


5) Add 3WayAdjState as well as isisISAdjState.
I had hoped this could be combined. Will re-read RFC.


Jeff,

3 way state is different from 10589 adjacency state.

Thanks,

Rajesh

Yahoo! Properties Special new Buy, sell, rent...your flat, or even post an ad --0-464424340-1034135397=:79975-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 00:25:46 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA09685 for ; Wed, 9 Oct 2002 00:25:46 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g994HEv18396; Wed, 9 Oct 2002 00:17:14 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g994Eqv18335 for ; Wed, 9 Oct 2002 00:14:52 -0400 Received: from web8201.mail.in.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id AAA08961 for ; Wed, 9 Oct 2002 00:12:37 -0400 (EDT) Message-ID: <20021009041441.19727.qmail@web8201.mail.in.yahoo.com> Received: from [202.9.170.75] by web8201.mail.in.yahoo.com via HTTP; Wed, 09 Oct 2002 05:14:41 BST From: =?iso-8859-1?q?Rajesh=20Saluja?= Subject: Re: [Isis-wg] Other Edits to IS-IS MIB To: Jeff Parker , "ISIS-WG \(E-mail\)" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-173980788-1034136881=:19692" Content-Transfer-Encoding: 8bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 05:14:41 +0100 (BST) --0-173980788-1034136881=:19692 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Jeff, I noticed that default metric range is 0 to 63. Shouldn't it be 1 to 63? Also I would appreciate if you could share the basis of choosing the range and default values of the following parameters: isisSysMaxPathSplits - range 1 to 32, default 2 isisSysOrigLnLSPBuffSize - range 512 to 16000 bytes isisSysReceiveLSPBuffersize - range 1492 to 65535 bytes isisSummAddrMetric - default 20 isisSysMaxAge: range 1200 to 65535 isisCircLevelHelloTime: default 3 sec isisCircLevelHelloMultiplier: range 2 to 100 I am sorry if these questions have been addresses before. Thanks, Rajesh Jeff Parker wrote: I deleted many of Don's mails after making the changes. I have made a dozen imediate changes, and will address larger changes soon. Here is the list I have so far of what I've done. -- Numerous edits from Dan Goodspeed -- Added 0 to ISPriority range -- Changed encoding of 'none' in ISLevel to 0, rather than 3 -- Replaced UpTime with TimeTicks -- Rewrote descriptions of CircUpTime and AdjUpTime -- Removed Comments on Depricated Groups -- Edited description of isisCircEntry -- Added References for MeshGroup and MeshGroupEnabled -- Updated description -- Remove L1 from isisSysStatLSPDbaseOloads description -- Added isisCircAdj to count adjacencies on circuit -- Added isisPacketCountUnknown -- Removed LSPSize from isisAreaMismatch -- Added isisPDUFragment to isisRejectedAdjacency -- Updated description - jeff parker - axiowave networks - echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg Yahoo! Properties Special Buy, sell, rent...your flat, or even post an ad --0-173980788-1034136881=:19692 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit

Jeff,

I noticed that default metric range is 0 to 63. Shouldn't it be 1 to 63? Also I would appreciate if you could share the basis of choosing the range and default values of the following parameters:

isisSysMaxPathSplits - range 1 to 32, default 2

isisSysOrigLnLSPBuffSize - range 512 to 16000 bytes

isisSysReceiveLSPBuffersize - range 1492 to 65535 bytes

isisSummAddrMetric - default 20

isisSysMaxAge: range 1200 to 65535

isisCircLevelHelloTime: default 3 sec

isisCircLevelHelloMultiplier: range 2 to 100

I am sorry if these questions have been addresses before.

Thanks,

Rajesh

  Jeff Parker <jparker@axiowave.com> wrote:

I deleted many of Don's mails after making the changes.
I have made a dozen imediate changes, and will address larger changes
soon. Here is the list I have so far of what I've done.

-- Numerous edits from Dan Goodspeed
-- Added 0 to ISPriority range
-- Changed encoding of 'none' in ISLevel to 0, rather than 3
-- Replaced UpTime with TimeTicks
-- Rewrote descriptions of CircUpTime and AdjUpTime
-- Removed Comments on Depricated Groups
-- Edited description of isisCircEntry
-- Added References for MeshGroup and MeshGroupEnabled
-- Updated description
-- Remove L1 from isisSysStatLSPDbaseOloads description
-- Added isisCircAdj to count adjacencies on circuit
-- Added isisPacketCountUnknown
-- Removed LSPSize from isisAreaMismatch
-- Added isisPDUFragment to isisRejectedAdjacency
-- Updated description

- jeff parker
- axiowave ! networks
- echo
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg

Yahoo! Properties Special new Buy, sell, rent...your flat, or even post an ad --0-173980788-1034136881=:19692-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 10:10:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18137 for ; Wed, 9 Oct 2002 10:10:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99E7Jv24210; Wed, 9 Oct 2002 10:07:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99E3Mv23540 for ; Wed, 9 Oct 2002 10:03:22 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17501 for ; Wed, 9 Oct 2002 10:01:12 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] RE: isisSysStatAuthFails and isisCircAuthFails Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 10:03:17 -0400 > I see value of isisCircAuthFails count, which records auth > fails happened per circuit, per level. What is the use of > isisSysStatAuthFails? It would just be the sum [over] > all interfaces [of] isisCircAuthFails... > Same question to isisSysStatsAuthTypeFails, > isisSysStatsIDFieldlenMismatches > and isisSysStatsMaxAreaAddrMismatches. A NMS can poll these system counters, rather than the circuit counters, looking for this type of problem. Only if the system counts are rising do we need to poll this attribute on the circuit level. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 10:14:06 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18464 for ; Wed, 9 Oct 2002 10:14:06 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EC9v24449; Wed, 9 Oct 2002 10:12:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99E9Rv24325 for ; Wed, 9 Oct 2002 10:09:27 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17806 for ; Wed, 9 Oct 2002 10:07:17 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Cc: "Don Goodspeed (E-mail)" Subject: RE: [Isis-wg] MIB: split isisISAdjNeighSysID into 2 attributes MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 10:09:22 -0400 > I forgot to mention it should be numeric, but we probably want to > make it an Unsigned32, not Integer32 since this # will not be > negative. > > Also, in the MIB update you sent me, you list the ExtendedCircID > after NeighSysID, but you put it just after SNPAAddress (oid 4 > in the table). Thanks. Fixed. - jdp _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 10:25:04 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19250 for ; Wed, 9 Oct 2002 10:25:04 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EJ5v24873; Wed, 9 Oct 2002 10:19:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EDRv24475 for ; Wed, 9 Oct 2002 10:13:27 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18187 for ; Wed, 9 Oct 2002 10:11:17 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Cc: "Don Goodspeed (E-mail)" Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r I P tables MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 10:13:21 -0400 > We may want to keep SNPAAddress in the table, just not as > an INDEX to the table. Done. - jdp isisIPRAEntry OBJECT-TYPE SYNTAX IsisIPRAEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry defines an IP Reachable Address to a network, subnetwork or host." INDEX { isisSysInstance, isisIPRAIndex, isisIPRADestType, isisIPRADest, isisIPRADestPrefixLen } ::= { isisIPRATable 1 } IsisIPRAEntry ::= SEQUENCE { isisIPRAIndex Integer32, isisIPRADestType InetAddressType, isisIPRADest InetAddress, isisIPRADestPrefixLen InetAddressPrefixLength, isisIPRANextHopType InetAddressType, isisIPRANextHop InetAddress, isisIPRAType INTEGER, isisIPRAExistState RowStatus, isisIPRAAdminState AdminState, isisIPRAMetric DefaultMetric, isisIPRAMetricType MetricType, isisIPRAFullMetric FullMetric, isisIPRASNPAAddress OSINSAddress } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 10:38:08 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19976 for ; Wed, 9 Oct 2002 10:38:08 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EWJv25737; Wed, 9 Oct 2002 10:32:19 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99ERAv25403 for ; Wed, 9 Oct 2002 10:27:10 -0400 Received: from rchss001.chiaro.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA19244 for ; Wed, 9 Oct 2002 10:25:00 -0400 (EDT) Received: (qmail 17950 invoked from network); 9 Oct 2002 14:17:11 -0000 Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81) by rchss001.chiaro.com with SMTP; 9 Oct 2002 14:17:11 -0000 Received: by MAIL with Internet Mail Service (5.5.2653.19) id ; Wed, 9 Oct 2002 09:26:07 -0500 Message-ID: From: Laura Liu To: dgoodspe@excite.com, jparker@axiowave.com, isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: Need for isisRedistributeAddrTable MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 09:25:59 -0500 --=_IS_MIME_Boundary Content-Type: text/plain; charset="iso-8859-1" Don, It seems to me that you want to keep isisRedistributeAddrTable for the routes leaking between ISIS levels; and use isisIPRATable for OTHER prefixes that are redistributed into ISIS. Those prefixes could be manually configured or learned from other routing protocols like OSPF and BGP etc. This makes sense to prevent the same prefix being monitored in both tables. I think we only need a new attribute isisLeakDirection in isisRedistributeAddrTable and keep the isisIPRAType in isisIPRATable. isisRedistributeAddrTable does not need isisRedistributeType attribute. Laura > -----Original Message----- > From: Don Goodspeed [mailto:dgoodspe@excite.com] > Sent: Tuesday, October 08, 2002 7:20 PM > To: jparker@axiowave.com; isis-wg@ietf.org > Subject: [Isis-wg] MIB: Need for isisRedistributeAddrTable > > > > Jeff and all, > > I think I can clarify the usefulness of this table. We can use > the table to show what routes "are" being leaked based on policies > for leaking that are defined elsewhere. We can keep the ExistState > attribute, although some implementation may not allow it to be > controlled via SNMP. > > We should also include an isisRedistributeType attribute (not part > of the index) for controlling whether this route prefix is automatic > or manual. Some implementation will not allow this to be set via > SNMP either (they'll always have only automatic routes in this table). > > Finally, we should dual-purpose the table and also show which > routes are > being leaked from L1 into L2 as well. Since a route can be leaked in > only one direction, this does not need to be part of the > index, and it's > only two values would be leakL1ToL2(1) or leakL2ToL1(2). It would > also be read-create, and have the same caveat that some > implementations > may implement this as read-only. > > I hope this will work for everyone > -don > > --- On Tue 10/08, Jeff Parker wrote: > From: Jeff Parker [mailto: jparker@axiowave.com] > To: isis-wg@ietf.org > Date: Tue, 8 Oct 2002 14:54:41 -0400 > Subject: [Isis-wg] Don's MIB ToDo list > > > 4) isisRedistributeAddrTable - platform > > > independence cannot probably be achieved. > > > Every vendor > > > usually has leaking tied into route policies since > > > route ranges can come into play as well as only leaking > > > internal vs external ISIS routes, etc. > > > > I see Don's point, though I would like to think > > we could retain something. Any suggestions? Here > > is a snapshot of the contents. > > > > -- The Redistribution table defines addresses that should > be leaked from > > -- L2 to L1 if isisSysL2toL1Leaking is enabled. > > > > isisRedistributeAddrTable OBJECT-TYPE > > SYNTAX SEQUENCE OF IsisRedistributeAddrEntry > > MAX-ACCESS not-accessible > > STATUS current > > DESCRIPTION > > "This table provides criteria to decide if a route > > should > > be leaked from L2 to L1 when Domain Wide > Prefix leaking is > > enabled. > > > > Addresses that match the summary mask in the table will > > be announced at L1 by routers when isisSysL2toL1Leaking > > is enabled. Routes that fall into the ranges specified > > are are announced as is, without being summarized." > > ::= { isisSystem 6 } > > .... > > IsisRedistributeAddrEntry ::= > > SEQUENCE { > > isisRedistributeAddrType > > InetAddressType, > > isisRedistributeAddrAddress > > InetAddress, > > isisRedistributeAddrPrefixLen > > InetAddressPrefixLength, > > isisRedistributeAddrExistState > > RowStatus > > } > > > ------------------------------------------------ > 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 > --=_IS_MIME_Boundary Content-Type: text/plain;charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit ----------------------------------------- (on rchss001) This e-mail and any files transmitted with it are the property of Chiaro Networks, Ltd., and may contain confidential and privileged material for the sole use of the intended recipient(s) to whom this e-mail is addressed. If you are not one of the named recipient(s), or otherwise have reason to believe that you have received this message in error, please notify the sender and delete all copies from your system. Any other use, retention, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. --------------------------------------------------------- --=_IS_MIME_Boundary-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 10:52:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20503 for ; Wed, 9 Oct 2002 10:52:05 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EhCv26850; Wed, 9 Oct 2002 10:43:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EeFv26769 for ; Wed, 9 Oct 2002 10:40:15 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19974 for ; Wed, 9 Oct 2002 10:38:04 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Rajesh Saluja'" , "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] Don's MIB ToDo list MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 10:40:03 -0400 > 3 way state is different from 10589 adjacency state. > > Rajesh Rajesh - Thanks. I have added new state, and re-ordered the enums on the isisISAdjState, which are not carried on the wire. The 3Way state retains the on-the-wire encoding. Should we retain the "down" and "failed" states? I would think that 'initiailizing' and 'up' are the only states we'll see. - jeff parker isisISAdjState OBJECT-TYPE SYNTAX INTEGER { down (1), initializing (2), up (3), failed(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "The state of the adjacency" REFERENCE "{ISIS.aoi adjacencyState (78)}" ::= { isisISAdjEntry 2 } isisIS3WayAdjState OBJECT-TYPE SYNTAX INTEGER { up (0), initializing (1), down (2), failed (3) } MAX-ACCESS read-only STATUS current DESCRIPTION "The 3Way state of the adjacency" REFERENCE "{ RFC 3373 }" ::= { isisISAdjEntry 3 } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 11:02:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA21053 for ; Wed, 9 Oct 2002 11:02:33 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Es7v27281; Wed, 9 Oct 2002 10:54:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99EpYv27186 for ; Wed, 9 Oct 2002 10:51:34 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20386 for ; Wed, 9 Oct 2002 10:49:26 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Rajesh Saluja'" , "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] Other Edits to IS-IS MIB MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 10:51:24 -0400 Rajesh - I'm not sure that I can come up with the origin of each of these, but there has been an ongoing discussion. For example, isisSysReceiveLSPBuffersize is assumed to be at least 1492, but could be made larger (discussion on the ISIS-Update list). Is 2^16 the right upper bound? Probably not. The HelloTime and HelloMultiplier were discussed recently on this list. Many of the others were inherited from the original version of the MIB. If you have specific suggestions, we should discuss them. - jeff parker ------------ forwarded -------------- I noticed that default metric range is 0 to 63. Shouldn't it be 1 to 63? Also I would appreciate if you could share the basis of choosing the range and default values of the following parameters: isisSysMaxPathSplits - range 1 to 32, default 2 isisSysOrigLnLSPBuffSize - range 512 to 16000 bytes isisSysReceiveLSPBuffersize - range 1492 to 65535 bytes isisSummAddrMetric - default 20 isisSysMaxAge: range 1200 to 65535 isisCircLevelHelloTime: default 3 sec isisCircLevelHelloMultiplier: range 2 to 100 I am sorry if these questions have been addresses before. Thanks, Rajesh _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 11:48:50 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22676 for ; Wed, 9 Oct 2002 11:48:49 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Fdev30729; Wed, 9 Oct 2002 11:39:40 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99FZ6v29944 for ; Wed, 9 Oct 2002 11:35:06 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22100 for ; Wed, 9 Oct 2002 11:32:57 -0400 (EDT) Message-ID: From: Jeff Parker To: isis-wg@ietf.org Cc: "Don Goodspeed (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] RE: Need for isisRedistributeAddrTable Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 11:35:00 -0400 > We can use [the isisRedistributeAddrTable] > the table to show what routes "are" being leaked based on policies > for leaking that are defined elsewhere. We can keep the ExistState > attribute, although some implementation may not allow it to be > controlled via SNMP. > > We should also include an isisRedistributeType attribute (not part > of the index) for controlling whether this route prefix is automatic > or manual. Some implementation will not allow this to be set via > SNMP either (they'll always have only automatic routes in this table). I guess I am not following this. This table is to manager L2 to L1 leaking. If you want to leak a static route into L1, I don't think this is the place to define that. We have skirted the whole issue of route policy as being very proprietary. > Finally, we should dual-purpose the table and also show which > routes are being leaked from L1 into L2 as well. Laura addressed this previously. The summary has been around for a long time, and covers that case. See if it has what you need. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 11:58:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23100 for ; Wed, 9 Oct 2002 11:58:53 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Fnxv31181; Wed, 9 Oct 2002 11:49:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Fldv31069 for ; Wed, 9 Oct 2002 11:47:39 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22576 for ; Wed, 9 Oct 2002 11:45:29 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Laura Liu'" Cc: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r IP tables MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 11:47:29 -0400 > And a new attribute for isisIPRASourceType, which indicate > where the prefix > learned from: static, directly connected, OSPF, BGP or ISIS. > > Laura Laura - I have added the following. All - Are other protocols called for? Two version of ISIS - L1 and L2? - jdp isisIPRASourceType OBJECT-TYPE SYNTAX INTEGER { static (1), direct (2), ospf (3), isis (4), bgp (5), other (6) } MAX-ACCESS read-only STATUS current DESCRIPTION "The origin of this route." ::= { isisIPRAEntry 14 } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 12:30:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24495 for ; Wed, 9 Oct 2002 12:30:24 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99GLQv01270; Wed, 9 Oct 2002 12:21:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99GImv01127 for ; Wed, 9 Oct 2002 12:18:48 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23944 for ; Wed, 9 Oct 2002 12:16:38 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] OperStatus in System and Circ MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 12:18:40 -0400 We are closing in on Don's list: updates below. However, this mail is really about OperState > 1) isisLSPTable - On the todo list. > 2) isisSysOverloadTimeLeft - I think I had this once, and I'm > trying to remember why it disappeared. > 3) OperStatus is in the isisSys table and isisCircTable. > ...we had this once, and I wonder why it isn't there... > > At the system level, the OperStatus might still be up for a few seconds > > when the protocol has been disabled to clean up some internal entities. > > At the circuit level, a lower-level link status of down would cause > > the OperStatus of the circuit to be down as opposed to up. > > > > Don Goodspeed [Looking back, we replace OperState with AdminState] If you have enabled a circuit, when do you think it is operational? 1) When you hear from the kernel that you have carrier [Don's choice, above] 2) When you send a packet out without error 3) When you see your info in the far side's Hello Pkt 4) Some other measure I'm not sure I know what ISIS OperState represents, or how much credit to put into anything but #3. The first is already in the Interface MIB, the second is in the PacketCount area, and the third is in the Adjacency area. You could make the case that "isisCircOperational" means 1) and that the circuit is enabled for ISO, however that is defined on your system - PPP negotiation is complete, or right mcast addresses are enabled on Ethernet, etc. I'm not adverse to putting this in if it has value. I do wonder what we gain. > 4) isisRedistributeAddrTable Don - are we in agreement on this yet? > 5) Add 3WayAdjState Revised, in review. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 12:40:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24929 for ; Wed, 9 Oct 2002 12:40:25 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Ga7v01952; Wed, 9 Oct 2002 12:36:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99GXXv01845 for ; Wed, 9 Oct 2002 12:33:33 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24569 for ; Wed, 9 Oct 2002 12:31:23 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Cc: "Don Goodspeed (E-mail)" , "'lliu@chiaro.com'" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] FW: IS-IS MIB (metric comments) Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 12:33:27 -0400 A question about the validity of a metric of 0 arose this morning. Digging through old mail, I find the following request. I'm open to suggestions. Current version allows a metric of 0 for both Wide and Classic. - jeff parker --- On Tue 06/04, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: dgoodspe@excite.com Cc: isis-wg@spider.juniper.net Date: Tue 06/04 Subject: RE: IS-IS MIB (metric comments) ... > > In version 0.8 of the ISIS MIB, you have a Textual Convention > > for DefaultMetric which is defined as (1..63). Should we > > allow zero in the range, as our passive interfaces have a > > metric of zero. > > ... > > -don _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 12:56:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25473 for ; Wed, 9 Oct 2002 12:56:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99GqPv03138; Wed, 9 Oct 2002 12:52:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Glkv03007 for ; Wed, 9 Oct 2002 12:47:46 -0400 Received: from cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25090 for ; Wed, 9 Oct 2002 12:45:36 -0400 (EDT) Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp169.cisco.com [10.50.0.168]) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id RAA24918; Wed, 9 Oct 2002 17:47:07 +0100 (BST) Message-Id: <4.3.2.7.2.20021009174550.0454b7e8@jaws.cisco.com> X-Sender: mshand@jaws.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: Jeff Parker From: mike shand Subject: Re: [Isis-wg] FW: IS-IS MIB (metric comments) Cc: "ISIS-WG (E-mail)" , "Don Goodspeed (E-mail)" , "'lliu@chiaro.com'" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 09 Oct 2002 17:47:06 +0100 Zero is OK for leaves, but its dangerous for links. Mike At 12:33 09/10/2002 -0400, Jeff Parker wrote: >A question about the validity of a metric of 0 >arose this morning. Digging through old mail, >I find the following request. > >I'm open to suggestions. Current version >allows a metric of 0 for both Wide and Classic. > >- jeff parker > >--- On Tue 06/04, Jeff Parker wrote: >From: Jeff Parker [mailto: jparker@axiowave.com] >To: dgoodspe@excite.com > Cc: isis-wg@spider.juniper.net >Date: Tue 06/04 >Subject: RE: IS-IS MIB (metric comments) > >... > > > In version 0.8 of the ISIS MIB, you have a Textual Convention > > > for DefaultMetric which is defined as (1..63). Should we > > > allow zero in the range, as our passive interfaces have a > > > metric of zero. > > > ... > > > -don >_______________________________________________ >Isis-wg mailing list >Isis-wg@ietf.org >https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 13:56:40 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27436 for ; Wed, 9 Oct 2002 13:56:40 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99HqKv06621; Wed, 9 Oct 2002 13:52:21 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Hmvv06489 for ; Wed, 9 Oct 2002 13:48:57 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27107 for ; Wed, 9 Oct 2002 13:46:47 -0400 (EDT) Message-ID: From: Jeff Parker To: "'mike shand'" Cc: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 13:48:38 -0400 > Zero is OK for leaves, but its dangerous for links. > > Mike The TextualConventions DefaultMetric comes up in 4 tables SummaryAddress CircuitLevelEntry IsisRAEntry (reachable Entry) IsisIPRAEntry (Imported route) The results for the Wide Metric TC are similar. I could use a different textual convention for Circuit, as that is the only way we would get distance to a Neighbor. However, passive links get the distance to an IP net through this same metric. So I don't see any easy way to remove the conflict: it arises from the two uses of the Circuit Metric: for IP nets and neighbors on active links, and for IP nets on passive links. Options 1) Split DefaultMetric into CircDefaultMetric and rest. (though I don;t think this makes any difference) 2) Add text on isisCircLevelMetric saying 0 is illegal unless passive 3) Add a new variable to be used only for passive circuits (Now what happens when we change from passive to active and the metrics don't match?) I don't think that the third solution matches what most people do here. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 14:37:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28950 for ; Wed, 9 Oct 2002 14:37:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99Ib9v08971; Wed, 9 Oct 2002 14:37:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99IWdv08576 for ; Wed, 9 Oct 2002 14:32:39 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA28675 for ; Wed, 9 Oct 2002 14:30:28 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id F304DB6C3; Wed, 9 Oct 2002 14:32:29 -0400 (EDT) To: jparker@axiowave.com, rs_isis@yahoo.co.in, isis-wg@ietf.org Subject: RE: [Isis-wg] isisISAdjState and 3Way State (was Don's ...) Received: from [63.104.212.252] by xprdmailfe15.nwk.excite.com via HTTP; Wed, 09 Oct 2002 14:32:29 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021009183229.F304DB6C3@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 14:32:29 -0400 (EDT) Content-Transfer-Encoding: 7bit Jeff, I assume you are asking "if we should keep the down and failed states for the isisISAdjState". If so, I'd say yes. If we add a notification (like OSPF has) for adjacency state changes, down will be needed. And failed is possibly used by some vendors when the adjacency is rejected. -don --- On Wed 10/09, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: rs_isis@yahoo.co.in, isis-wg@ietf.org Date: Wed, 9 Oct 2002 10:40:03 -0400 Subject: RE: [Isis-wg] Don's MIB ToDo list > > 3 way state is different from 10589 adjacency state. > > > > Rajesh > > Rajesh - > Thanks. I have added new state, and re-ordered the > enums on the isisISAdjState, which are not carried on the > wire. The 3Way state retains the on-the-wire encoding. > > Should we retain the "down" and "failed" states? > I would think that 'initiailizing' and 'up' are the > only states we'll see. > > - jeff parker > > isisISAdjState OBJECT-TYPE > SYNTAX INTEGER > { > down (1), > initializing (2), > up (3), > failed(4) > } > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The state of the adjacency" > REFERENCE "{ISIS.aoi adjacencyState (78)}" > ::= { isisISAdjEntry 2 } > > isisIS3WayAdjState OBJECT-TYPE > SYNTAX INTEGER > { > up (0), > initializing (1), > down (2), > failed (3) > } > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The 3Way state of the adjacency" > REFERENCE "{ RFC 3373 }" > ::= { isisISAdjEntry 3 } > > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ 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-admin@ietf.org Wed Oct 9 15:59:49 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01878 for ; Wed, 9 Oct 2002 15:59:49 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99JxTv13921; Wed, 9 Oct 2002 15:59:29 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99JuHv13803 for ; Wed, 9 Oct 2002 15:56:17 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01632 for ; Wed, 9 Oct 2002 15:54:05 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id E7778B6F7; Wed, 9 Oct 2002 15:56:07 -0400 (EDT) To: lliu@chiaro.com, jparker@axiowave.com, isis-wg@ietf.org Subject: RE: [Isis-wg] MIB: Need for isisRedistributeAddrTable Received: from [63.104.212.252] by xprdmailfe15.nwk.excite.com via HTTP; Wed, 09 Oct 2002 15:56:07 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021009195607.E7778B6F7@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 15:56:07 -0400 (EDT) Content-Transfer-Encoding: 7bit I agree. On a separate note, I still wonder if we should just make this table completely read-only. -don --- On Wed 10/09, Laura Liu wrote: From: Laura Liu [mailto: lliu@chiaro.com] To: dgoodspe@excite.com, jparker@axiowave.com, isis-wg@ietf.org Date: Wed, 9 Oct 2002 09:25:59 -0500 Subject: RE: [Isis-wg] MIB: Need for isisRedistributeAddrTable > Don, > > It seems to me that you want to keep isisRedistributeAddrTable for the > routes leaking between ISIS levels; and use isisIPRATable for OTHER > prefixes > that are redistributed into ISIS. Those prefixes could be manually > configured or learned from other routing protocols like OSPF and BGP etc. > This makes sense to prevent the same prefix being monitored in both > tables. > I think we only need a new attribute isisLeakDirection in > isisRedistributeAddrTable and keep the isisIPRAType in isisIPRATable. > isisRedistributeAddrTable does not need isisRedistributeType attribute. > > Laura > > ------------------------------------------------ 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-admin@ietf.org Wed Oct 9 16:04:43 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02251 for ; Wed, 9 Oct 2002 16:04:43 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99K4Av14099; Wed, 9 Oct 2002 16:04:10 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99K1Av14029 for ; Wed, 9 Oct 2002 16:01:10 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01827 for ; Wed, 9 Oct 2002 15:58:58 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id F3F9BB6C3; Wed, 9 Oct 2002 16:01:00 -0400 (EDT) To: jparker@axiowave.com, isis-wg@ietf.org Subject: [Isis-wg] RE: Need for isisRedistributeAddrTable Received: from [63.104.212.252] by xprdmailfe15.nwk.excite.com via HTTP; Wed, 09 Oct 2002 16:01:00 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021009200100.F3F9BB6C3@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 16:01:00 -0400 (EDT) Content-Transfer-Encoding: 7bit Jeff and all, But not everyone supports summaries, and most support leaking via route policies. Also, leaking does go the other way since L1 externals are not leaked into L2 by default. For some implementations, this is controlled via policies as well. I think that table could be dual-purposed; meaning, there is no need to create a separate table to reflect which routes are being leaked from L1 into L2. -don --- On Wed 10/09, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: isis-wg@ietf.org Cc: dgoodspe68@yahoo.com Date: Wed, 9 Oct 2002 11:35:00 -0400 Subject: [Isis-wg] RE: Need for isisRedistributeAddrTable > > We can use [the isisRedistributeAddrTable] > > the table to show what routes "are" being leaked based on > policies > > for leaking that are defined elsewhere. We can keep the ExistState > > attribute, although some implementation may not allow it to be > > controlled via SNMP. > > > > We should also include an isisRedistributeType attribute (not part > > of the index) for controlling whether this route prefix is automatic > > or manual. Some implementation will not allow this to be set via > > SNMP either (they'll always have only automatic routes in this > table). > > I guess I am not following this. This table is to manager L2 to L1 > leaking. If you want to leak a static route into L1, I don't > think this is the place to define that. > > We have skirted the whole issue of route policy as being very > proprietary. > > > > Finally, we should dual-purpose the table and also show which > > routes are being leaked from L1 into L2 as well. > > Laura addressed this previously. > The summary has been around for a long time, > and covers that case. See if it has what you need. > > - jeff parker > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ 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-admin@ietf.org Wed Oct 9 16:12:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02723 for ; Wed, 9 Oct 2002 16:12:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KBtv14955; Wed, 9 Oct 2002 16:11:55 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99K4uv14142 for ; Wed, 9 Oct 2002 16:04:56 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01946 for ; Wed, 9 Oct 2002 16:02:44 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id C1D8CB701; Wed, 9 Oct 2002 16:04:46 -0400 (EDT) To: jparker@axiowave.com, lliu@chiaro.com Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r IP tables Received: from [63.104.212.252] by xprdmailfe15.nwk.excite.com via HTTP; Wed, 09 Oct 2002 16:04:46 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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 Cc: isis-wg@ietf.org Message-Id: <20021009200446.C1D8CB701@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 16:04:46 -0400 (EDT) Content-Transfer-Encoding: 7bit Don't forget RIP! -don --- On Wed 10/09, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: lliu@chiaro.com Cc: isis-wg@ietf.org Date: Wed, 9 Oct 2002 11:47:29 -0400 Subject: RE: [Isis-wg] MIB: re-index isisIPRATable to be in line with othe r IP tables > > > And a new attribute for isisIPRASourceType, which indicate > > where the prefix > > learned from: static, directly connected, OSPF, BGP or ISIS. > > > > Laura > > Laura - > > I have added the following. > > All - > Are other protocols called for? Two version of ISIS - L1 and L2? > > - jdp > > isisIPRASourceType OBJECT-TYPE > SYNTAX INTEGER > { > static (1), > direct (2), > ospf (3), > isis (4), > bgp (5), > other (6) > } > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The origin of this route." > ::= { isisIPRAEntry 14 } > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ 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-admin@ietf.org Wed Oct 9 16:14:34 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02840 for ; Wed, 9 Oct 2002 16:14:34 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KE1v15085; Wed, 9 Oct 2002 16:14:01 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KABv14906 for ; Wed, 9 Oct 2002 16:10:11 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02357 for ; Wed, 9 Oct 2002 16:07:58 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 96F58B6FD; Wed, 9 Oct 2002 16:10:01 -0400 (EDT) To: jparker@axiowave.com, isis-wg@ietf.org Subject: RE: [Isis-wg] OperStatus in System and Circ Received: from [63.104.212.252] by xprdmailfe15.nwk.excite.com via HTTP; Wed, 09 Oct 2002 16:10:01 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021009201001.96F58B6FD@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 16:10:01 -0400 (EDT) Content-Transfer-Encoding: 7bit Jeff, On issue #3 (oper state), I guess the isisCircOperStatus is a one-stop place to see if the circuit is up or down. As for the isisOperStatus, some protocols (BGP, for one) need some time to come down operationally when administratively disabled. I guess it's not much of an issue for ISIS since we don't have much to clean up, and do it sub-second usually. So, I'd still like to see the isisCircOperStatus, but not the isisOperStatus. As for #4, I just sent some replies to the list separately. Thanks, Don --- On Wed 10/09, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: isis-wg@ietf.org Date: Wed, 9 Oct 2002 12:18:40 -0400 Subject: RE: [Isis-wg] OperStatus in System and Circ > We are closing in on Don's list: updates below. > > However, this mail is really about OperState > > > 1) isisLSPTable - On the todo list. > > 2) isisSysOverloadTimeLeft - I think I had this once, and I'm > > trying to remember why it disappeared. > > > 3) OperStatus is in the isisSys table and isisCircTable. > > ...we had this once, and I wonder why it isn't there... > > > > At the system level, the OperStatus might still be up for a few > seconds > > > when the protocol has been disabled to clean up some internal > entities. > > > > At the circuit level, a lower-level link status of down would > cause > > > the OperStatus of the circuit to be down as opposed to up. > > > > > > Don Goodspeed > > [Looking back, we replace OperState with AdminState] > > If you have enabled a circuit, when do you think it > is operational? > > 1) When you hear from the kernel that you have > carrier [Don's choice, above] > 2) When you send a packet out without error > 3) When you see your info in the far side's > Hello Pkt > 4) Some other measure > > I'm not sure I know what ISIS OperState represents, > or how much credit to put into anything but #3. > The first is already in the Interface MIB, the second > is in the PacketCount area, and the third is in the > Adjacency area. You could make the case that > "isisCircOperational" means 1) and that the circuit > is enabled for ISO, however that is defined on your > system - PPP negotiation is complete, or right mcast > addresses are enabled on Ethernet, etc. > > I'm not adverse to putting this in if it has value. > I do wonder what we gain. > > > 4) isisRedistributeAddrTable > Don - are we in agreement on this yet? > > > 5) Add 3WayAdjState > Revised, in review. > > - jeff parker > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ 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-admin@ietf.org Wed Oct 9 16:18:00 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03034 for ; Wed, 9 Oct 2002 16:17:59 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KHCv15359; Wed, 9 Oct 2002 16:17:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KDgv15071 for ; Wed, 9 Oct 2002 16:13:42 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02654 for ; Wed, 9 Oct 2002 16:11:30 -0400 (EDT) Message-ID: From: Jeff Parker To: isis-wg@ietf.org Cc: "Don Goodspeed (E-mail)" Subject: RE: [Isis-wg] RE: Need for isisRedistributeAddrTable MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 16:13:34 -0400 > But not everyone supports summaries, and most support leaking via > route policies. Also, leaking does go the other way since > L1 externals are not leaked into L2 by default. For some > implementations, > this is controlled via policies as well. I think that table > could be dual-purposed; meaning, there is no need to create a > separate table to reflect which routes are being leaked from L1 > into L2. > > -don Don - The description of the Summary Table is in RFC 1195, section 3.2. If it isn't in every implementation, we could discuss making it optional. However, I believ I need to provide knobs for everything discussed in an RFCs. You can return to the discussion of the other tables, but I don't see any choice about including this one. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 9 16:20:52 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA03153 for ; Wed, 9 Oct 2002 16:20:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KK9v15506; Wed, 9 Oct 2002 16:20:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g99KG1v15320 for ; Wed, 9 Oct 2002 16:16:01 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02810 for ; Wed, 9 Oct 2002 16:13:48 -0400 (EDT) Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 9 Oct 2002 16:15:51 -0400 > I had suggested the change from 1 to zero, and now > I'm agreeing that zero is not needed. -don Great. I will have modified the metrics as below. - jeff parker DefaultMetric ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Integer sub-range for default metric for single hop. ISO 10589 provides for 4 types of metric. Only the 'default' metric is used in practice." SYNTAX Integer32 (1..63) WideMetric ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Wide Metric for IS Neighbors. ISO 10589 provides a 6 bit metric. Traffic Engineering extensions provide 24 bit metrics." SYNTAX Integer32 (1..16777215) _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu Oct 10 16:37:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23223 for ; Thu, 10 Oct 2002 16:37:27 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKWqv02322; Thu, 10 Oct 2002 16:32:53 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKTTv02085 for ; Thu, 10 Oct 2002 16:29:29 -0400 Received: from dmz1.procket.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22690 for ; Thu, 10 Oct 2002 16:27:11 -0400 (EDT) Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60]) by dmz1.procket.com (Postfix) with ESMTP id 2E83B23C24; Wed, 9 Oct 2002 16:36:41 -0700 (PDT) Received: from EXCHANGE0-0.na.procket.com (exchange0a.na.procket.com [10.1.7.7]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id g9AKTHiI028329; Thu, 10 Oct 2002 13:29:17 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) Message-ID: Thread-Topic: [Isis-wg] FW: IS-IS MIB (metric comments) Thread-Index: AcJvvUnQTRfWzMPLTX+nuM5FCOan6gA3lT6g From: "Tony Li" To: "Jeff Parker" , "mike shand" Cc: "ISIS-WG (E-mail)" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9AKTTv02086 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Oct 2002 13:29:16 -0700 Content-Transfer-Encoding: 8bit Don't we need metric zero for pseudo-nodes? Tony | -----Original Message----- | From: Jeff Parker [mailto:jparker@axiowave.com] | Sent: Wednesday, October 09, 2002 10:49 AM | To: 'mike shand' | Cc: ISIS-WG (E-mail) | Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) | | | > Zero is OK for leaves, but its dangerous for links. | > | > Mike | | The TextualConventions DefaultMetric comes up in | 4 tables | | SummaryAddress | CircuitLevelEntry | IsisRAEntry (reachable Entry) | IsisIPRAEntry (Imported route) | | The results for the Wide Metric TC are similar. | | I could use a different textual convention | for Circuit, as that is the only way we would | get distance to a Neighbor. However, passive | links get the distance to an IP net through | this same metric. So I don't see any easy | way to remove the conflict: it arises from | the two uses of the Circuit Metric: for | IP nets and neighbors on active links, | and for IP nets on passive links. | | Options | | 1) Split DefaultMetric into | CircDefaultMetric and rest. | (though I don;t think this makes | any difference) | 2) Add text on isisCircLevelMetric | saying 0 is illegal unless passive | 3) Add a new variable to be used only | for passive circuits (Now what | happens when we change from passive | to active and the metrics don't match?) | | I don't think that the third solution matches | what most people do here. | | - jeff parker | _______________________________________________ | Isis-wg mailing list | Isis-wg@ietf.org | https://www1.ietf.org/mailman/listinfo/isis-wg | _______________________________________________ | Isis-wg-external mailing list | Isis-wg-external@mailist.procket.com | http://mailist.procket.com/mailman/listinfo/isis-wg-external | _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu Oct 10 16:41:00 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23410 for ; Thu, 10 Oct 2002 16:41:00 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKdIv03251; Thu, 10 Oct 2002 16:39:18 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AKaTv02566 for ; Thu, 10 Oct 2002 16:36:29 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23082 for ; Thu, 10 Oct 2002 16:34:16 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Tony Li'" Cc: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Oct 2002 16:36:08 -0400 > Don't we need metric zero for pseudo-nodes? > > Tony > | > Zero is OK for leaves, but its dangerous for links. > | > > | > Mike At issue is the "metric" command and equivalents. The resolution is to drop 0 from the range for this class of parameters. This won't prevent your implementation from slapping a 0 into the PN LSP: it never consulted the circuit metric anyway. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu Oct 10 18:33:22 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA26041 for ; Thu, 10 Oct 2002 18:33:22 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AMWRv09078; Thu, 10 Oct 2002 18:32:27 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9AMT6v09000 for ; Thu, 10 Oct 2002 18:29:06 -0400 Received: from dmz2.procket.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25929 for ; Thu, 10 Oct 2002 18:26:54 -0400 (EDT) Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60]) by dmz2.procket.com (Postfix) with ESMTP id C815F3443F; Thu, 10 Oct 2002 15:37:28 -0700 (PDT) Received: from EXCHANGE0-0.na.procket.com (exchange0a.na.procket.com [10.1.7.7]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id g9AMSwiI010778; Thu, 10 Oct 2002 15:28:59 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) Message-ID: Thread-Topic: [Isis-wg] FW: IS-IS MIB (metric comments) Thread-Index: AcJwnLZz8wjTj7sBS9mPRvQgeU3ysQAD5uyg From: "Tony Li" To: "Jeff Parker" Cc: "ISIS-WG (E-mail)" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9AMT6v09001 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 10 Oct 2002 15:28:58 -0700 Content-Transfer-Encoding: 8bit Then how does a MIB entry report the zero metric for the pseudonode? Tony | -----Original Message----- | From: Jeff Parker [mailto:jparker@axiowave.com] | Sent: Thursday, October 10, 2002 1:36 PM | To: Tony Li | Cc: ISIS-WG (E-mail) | Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) | | | | > Don't we need metric zero for pseudo-nodes? | > | > Tony | | > | > Zero is OK for leaves, but its dangerous for links. | > | > | > | > Mike | | At issue is the "metric" command and equivalents. | The resolution is to drop 0 from the range for this | class of parameters. This won't prevent your | implementation from slapping a 0 into the PN LSP: | it never consulted the circuit metric anyway. | | - jeff parker | _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Fri Oct 11 14:06:31 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00859 for ; Fri, 11 Oct 2002 14:06:31 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BI1Zv07345; Fri, 11 Oct 2002 14:01:35 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9BHvsv07219 for ; Fri, 11 Oct 2002 13:57:54 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00475 for ; Fri, 11 Oct 2002 13:55:42 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 725693DFC; Fri, 11 Oct 2002 13:57:47 -0400 (EDT) To: Tony.Li@procket.com, jparker@axiowave.com Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) Received: from [63.104.212.252] by xprdmailfe12.nwk.excite.com via HTTP; Fri, 11 Oct 2002 13:57:47 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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 Cc: isis-wg@ietf.org Message-Id: <20021011175747.725693DFC@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 11 Oct 2002 13:57:47 -0400 (EDT) Content-Transfer-Encoding: 7bit Tony, Since pseudonodes do not have any reachable addresses associated with themselves, there will be no entries in the isisRA or isisIPRA table with the pseudonode as an endpoint. And since all non- pseudonode's will be reachable over a "transit" link that has a non-zero metric, all reachable addresses will have a non-zero metric associated with them. However, if anyone's implementation stores the metric to a direct or a passive interface in either table as zero, then we will need zero in the range. WG, does anyone do this? Cheers, Don --- On Thu 10/10, Tony Li wrote: From: Tony Li [mailto: Tony.Li@procket.com] To: jparker@axiowave.com Cc: isis-wg@ietf.org Date: Thu, 10 Oct 2002 15:28:58 -0700 Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) > > > Then how does a MIB entry report the zero metric for > the pseudonode? > > Tony > > > | -----Original Message----- > | From: Jeff Parker [mailto:jparker@axiowave.com] > | Sent: Thursday, October 10, 2002 1:36 PM > | To: Tony Li > | Cc: ISIS-WG (E-mail) > | Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) > | > | > | > | > Don't we need metric zero for pseudo-nodes? > | > > | > Tony > | > | > | > Zero is OK for leaves, but its dangerous for links. > | > | > > | > | > Mike > | > | At issue is the "metric" command and equivalents. > | The resolution is to drop 0 from the range for this > | class of parameters. This won't prevent your > | implementation from slapping a 0 into the PN LSP: > | it never consulted the circuit metric anyway. > | > | - jeff parker > | > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > ------------------------------------------------ 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-admin@ietf.org Sat Oct 12 07:20:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24387 for ; Sat, 12 Oct 2002 07:20:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CBHjv26351; Sat, 12 Oct 2002 07:17:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9CBCEv26271 for ; Sat, 12 Oct 2002 07:12:14 -0400 Received: from strange-brew.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24230 for ; Sat, 12 Oct 2002 07:10:03 -0400 (EDT) Received: from there (ams-clip-vpn-dhcp4233.cisco.com [10.50.16.136]) by strange-brew.cisco.com (8.11.6+Sun/8.8.8) with SMTP id g9CBBO718168; Sat, 12 Oct 2002 13:11:25 +0200 (CEST) Message-Id: <200210121111.g9CBBO718168@strange-brew.cisco.com> Content-Type: text/plain; charset="iso-8859-1" From: stefano previdi To: dgoodspe@excite.com, Tony.Li@procket.com, jparker@axiowave.com Subject: Re: [Isis-wg] FW: IS-IS MIB (metric comments) X-Mailer: KMail [version 1.3.1] Cc: isis-wg@ietf.org References: <20021011175747.725693DFC@xmxpita.excite.com> In-Reply-To: <20021011175747.725693DFC@xmxpita.excite.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9CBCEv26272 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Sat, 12 Oct 2002 13:11:20 +0200 Content-Transfer-Encoding: 8bit On Friday 11 October 2002 19:57, Don Goodspeed wrote: > Tony, > > Since pseudonodes do not have any reachable addresses associated > with themselves, there will be no entries in the isisRA or isisIPRA > table with the pseudonode as an endpoint. And since all non- > pseudonode's will be reachable over a "transit" link that has > a non-zero metric, all reachable addresses will have a non-zero > metric associated with them. > > However, if anyone's implementation stores the metric to a > direct or a passive interface in either table as zero, then > we will need zero in the range. WG, does anyone do this? I know at least one major implementation that assign a 0-metric to passive interfaces. s. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 14 12:20:41 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24924 for ; Mon, 14 Oct 2002 12:20:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EGIov08586; Mon, 14 Oct 2002 12:18:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EGD3v08482 for ; Mon, 14 Oct 2002 12:13:03 -0400 Received: from strange-brew.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24723 for ; Mon, 14 Oct 2002 12:10:50 -0400 (EDT) Received: from there (dhcp-wireless-144-254-102-42.cisco.com [144.254.102.42]) by strange-brew.cisco.com (8.11.6+Sun/8.8.8) with SMTP id g9EGCP725194; Mon, 14 Oct 2002 18:12:25 +0200 (CEST) Message-Id: <200210141612.g9EGCP725194@strange-brew.cisco.com> Content-Type: text/plain; charset="iso-8859-1" From: stefano previdi To: Jeff Parker Subject: Re: [Isis-wg] FW: IS-IS MIB (metric comments) X-Mailer: KMail [version 1.3.1] References: In-Reply-To: Cc: isis-wg@ietf.org MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g9EGD3v08483 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 14 Oct 2002 18:12:18 +0200 Content-Transfer-Encoding: 8bit On Monday 14 October 2002 16:37, Jeff Parker wrote: > Stephano - > I need to strike the balance between documenting > what is there and trying to prevent people from doing > things which might be there, but are broken. what I try to understand is why "reporting" a 0-metric in a mib is a problem. Taking the statement below: Since pseudonodes do not have any reachable addresses associated with themselves, there will be no entries in the isisRA or isisIPRA table with the pseudonode as an endpoint. And since all non- pseudonode's will be reachable over a "transit" link that has a non-zero metric, all reachable addresses will have a non-zero metric associated with them. However, if anyone's implementation stores the metric to a direct or a passive interface in either table as zero, then we will need zero in the range. WG, does anyone do this? now, I don't believe it's a problem if a passive interface has a 0-metric. This because we won't advertise any neighbor over a passive interface. The implementation I was referring to does advertise the IP prefix of passive interfaces with metric 0 but in no case you'll have a neighbor over it. Also, I would tend to put into MIBs what a router allows to configure. If an implementation decides to allow 0-metric for neighbors, then the MIB should reflect this and it's under responsibility of the CLI to allow/disallow this. s. > Why don't you post your note below to the list, > and see who pipes up. > > - jeff parker > - axiowave networks > - Success is relative; the more success, the more relatives. > > > > > -----Original Message----- > > From: stefano previdi [mailto:sprevidi@cisco.com] > > Sent: Monday, October 14, 2002 10:35 AM > > To: Jeff Parker > > Subject: Re: [Isis-wg] FW: IS-IS MIB (metric comments) > > > > > > On Monday 14 October 2002 16:23, Jeff Parker wrote: > > > > but what is the problem of keeping 0 in range ? > > > > > > > > s. > > > > > > If we can advertise a neighbor as 0 distance, we can get loops. > > > > I think we're talking about MIB values, right ? > > So I suppose MIBs are intended to relfect the > > reality of something.... no matter what it is. > > > > If 0-metric have been around for a while then MIBs > > should just ignore possible implication on algorithm > > outside the scope of SNMP MIBs.... > > > > s. > > > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 14 12:26:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25080 for ; Mon, 14 Oct 2002 12:26:28 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EGPuv08842; Mon, 14 Oct 2002 12:25:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EGHjv08562 for ; Mon, 14 Oct 2002 12:17:45 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA24810 for ; Mon, 14 Oct 2002 12:15:32 -0400 (EDT) Message-ID: From: Jeff Parker To: "'stefano previdi'" , Jeff Parker Cc: isis-wg@ietf.org Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 14 Oct 2002 12:17:35 -0400 > what I try to understand is why "reporting" a 0-metric in a > mib is a problem. > Taking the statement below: Stephano - We don't split passive interfaces from other interfaces in the MIB. Thus, given the current design, if we allow a 0 metric on a passive circuit, we are allowing a 0 metric on any circuit, and thus allowing a 0-cost path to a neighbor. We can add a warning that 0 should only be used when the interface is passive, but it is not enforceable. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 14 16:53:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02512 for ; Mon, 14 Oct 2002 16:53:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EKqPv23677; Mon, 14 Oct 2002 16:52:26 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EKnqv23609 for ; Mon, 14 Oct 2002 16:49:52 -0400 Received: from strange-brew.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02398 for ; Mon, 14 Oct 2002 16:47:37 -0400 (EDT) Received: from SPREVIDI-W2K1.cisco.com ([10.49.250.54]) by strange-brew.cisco.com (8.11.6+Sun/8.8.8) with ESMTP id g9EKnA720627; Mon, 14 Oct 2002 22:49:10 +0200 (CEST) Message-Id: <4.3.2.7.2.20021014224741.00b2c360@strange-brew.cisco.com> X-Sender: sprevidi@strange-brew.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: Jeff Parker From: stefano previdi Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) Cc: Jeff Parker , isis-wg@ietf.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 14 Oct 2002 22:49:09 +0200 At 06:17 PM 10/14/2002, Jeff Parker wrote: >> what I try to understand is why "reporting" a 0-metric in a >> mib is a problem. >> Taking the statement below: > >Stephano - > We don't split passive interfaces from other interfaces >in the MIB. Thus, given the current design, if we allow a 0 >metric on a passive circuit, we are allowing a 0 metric on >any circuit, and thus allowing a 0-cost path to a neighbor. > We can add a warning that 0 should only be used when the >interface is passive, but it is not enforceable. but what are you going to do with implementations that already assign 0-metric to (passive)interfaces ? I think you should accept them. Again, I don't believe it's the role of a MIB/SNMP agent to handle these issues. s. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 14 18:39:13 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04838 for ; Mon, 14 Oct 2002 18:39:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EMbMv29344; Mon, 14 Oct 2002 18:37:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EMYfv28801 for ; Mon, 14 Oct 2002 18:34:41 -0400 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04730 for ; Mon, 14 Oct 2002 18:32:25 -0400 (EDT) Received: from redback.com (yoo-hoo.redback.com [155.53.12.43]) by prattle.redback.com (Postfix) with ESMTP id D8EF04F41A8; Mon, 14 Oct 2002 15:34:33 -0700 (PDT) To: stefano previdi Cc: Jeff Parker , isis-wg@ietf.org Subject: Re: [Isis-wg] FW: IS-IS MIB (metric comments) In-reply-to: Mail from stefano previdi dated Mon, 14 Oct 2002 22:49:09 +0200 <4.3.2.7.2.20021014224741.00b2c360@strange-brew.cisco.com> From: Naiming Shen Message-Id: <20021014223433.D8EF04F41A8@prattle.redback.com> Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 14 Oct 2002 15:34:33 -0700 ] > We don't split passive interfaces from other interfaces ] >in the MIB. Thus, given the current design, if we allow a 0 ] >metric on a passive circuit, we are allowing a 0 metric on ] >any circuit, and thus allowing a 0-cost path to a neighbor. I think we should allow 0 to be inside the range. It's up to the implementation to block certain MIB settings. The MIB can give a union of all the possible configures exist/possible-to-have, if it does not want to specify the each specific cases. It's a local implementation issue to honor such a MIB request. The reverse approach, take a common dominate, does not sound right. ] > We can add a warning that 0 should only be used when the ] >interface is passive, but it is not enforceable. ] ] ] but what are you going to do with implementations that ] already assign 0-metric to (passive)interfaces ? I think ] you should accept them. ] ] Again, I don't believe it's the role of a MIB/SNMP agent ] to handle these issues. ] ] s. ] ] _______________________________________________ ] Isis-wg mailing list ] Isis-wg@ietf.org ] https://www1.ietf.org/mailman/listinfo/isis-wg - Naiming _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 14 18:41:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04895 for ; Mon, 14 Oct 2002 18:41:07 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EMe2v29524; Mon, 14 Oct 2002 18:40:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9EMbPv29352 for ; Mon, 14 Oct 2002 18:37:25 -0400 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04769 for ; Mon, 14 Oct 2002 18:35:09 -0400 (EDT) Received: from redback.com (yoo-hoo.redback.com [155.53.12.43]) by prattle.redback.com (Postfix) with ESMTP id 9F43F4F41BC; Mon, 14 Oct 2002 15:37:18 -0700 (PDT) To: isis-wg@ietf.org Subject: Re: [Isis-wg] FW: IS-IS MIB (metric comments) In-reply-to: Mail from Naiming Shen dated Mon, 14 Oct 2002 15:34:33 PDT <20021014223433.D8EF04F41A8@prattle.redback.com> From: Naiming Shen Message-Id: <20021014223718.9F43F4F41BC@prattle.redback.com> Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 14 Oct 2002 15:37:18 -0700 ] ] > We don't split passive interfaces from other interfaces ] ] >in the MIB. Thus, given the current design, if we allow a 0 ] ] >metric on a passive circuit, we are allowing a 0 metric on ] ] >any circuit, and thus allowing a 0-cost path to a neighbor. ] ] I think we should allow 0 to be inside the range. It's up to the ] implementation to block certain MIB settings. The MIB can give a ] union of all the possible configures exist/possible-to-have, if it ] does not want to specify the each specific cases. It's a local ] implementation issue to honor such a MIB request. The reverse approach, ] take a common dominate, does not sound right. ^^^^^^^^^ denominator. ] ] ] > We can add a warning that 0 should only be used when the ] ] >interface is passive, but it is not enforceable. ] ] ] ] ] ] but what are you going to do with implementations that ] ] already assign 0-metric to (passive)interfaces ? I think ] ] you should accept them. ] ] ] ] Again, I don't believe it's the role of a MIB/SNMP agent ] ] to handle these issues. ] ] ] ] s. ] ] ] ] _______________________________________________ ] ] Isis-wg mailing list ] ] Isis-wg@ietf.org ] ] https://www1.ietf.org/mailman/listinfo/isis-wg ] ] - Naiming - Naiming _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 14 22:43:03 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA08948 for ; Mon, 14 Oct 2002 22:43:03 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F2gSv08100; Mon, 14 Oct 2002 22:42:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F2dOv07990 for ; Mon, 14 Oct 2002 22:39:24 -0400 Received: from web20609.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA08817 for ; Mon, 14 Oct 2002 22:37:06 -0400 (EDT) Message-ID: <20021015023914.9590.qmail@web20609.mail.yahoo.com> Received: from [207.135.89.72] by web20609.mail.yahoo.com via HTTP; Mon, 14 Oct 2002 19:39:14 PDT From: Satish Dattatri Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) To: stefano previdi , Jeff Parker , Naiming Shen Cc: isis-wg@ietf.org In-Reply-To: <4.3.2.7.2.20021014224741.00b2c360@strange-brew.cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 14 Oct 2002 19:39:14 -0700 (PDT) The metric configured does not matter when an interface is passive, IP prefix advertisement will always be with zero cost. At a later point if the interface is made non-passive, the IP prefix advertisement will have the metric of the interface. Since, the configured value is not considered anyways for the advertisement of the IP prefix when passive, I think MIB range need not start with 0. Satish ] ] > We don't split passive interfaces from other interfaces ] ] >in the MIB. Thus, given the current design, if we allow a 0 ] ] >metric on a passive circuit, we are allowing a 0 metric on ] ] >any circuit, and thus allowing a 0-cost path to a neighbor. ] ] I think we should allow 0 to be inside the range. It's up to the ] implementation to block certain MIB settings. The MIB can give a ] union of all the possible configures exist/possible-to-have, if it ] does not want to specify the each specific cases. It's a local ] implementation issue to honor such a MIB request. The reverse approach, ] take a common dominate, does not sound right. ^^^^^^^^^ denominator. ] ] ] > We can add a warning that 0 should only be used when the ] ] >interface is passive, but it is not enforceable. ] ] ] ] ] ] but what are you going to do with implementations that ] ] already assign 0-metric to (passive)interfaces ? I think ] ] you should accept them. ] ] ] ] Again, I don't believe it's the role of a MIB/SNMP agent ] ] to handle these issues. ] ] ] ] s. ] ] ] ] _______________________________________________ ] ] Isis-wg mailing list ] ] Isis-wg@ietf.org ] ] https://www1.ietf.org/mailman/listinfo/isis-wg ] ] - Naiming - Naiming _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 14 23:26:49 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09607 for ; Mon, 14 Oct 2002 23:26:49 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F3QCv09676; Mon, 14 Oct 2002 23:26:12 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F3NDv09595 for ; Mon, 14 Oct 2002 23:23:13 -0400 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA09522 for ; Mon, 14 Oct 2002 23:20:55 -0400 (EDT) Received: from redback.com (yoo-hoo.redback.com [155.53.12.43]) by prattle.redback.com (Postfix) with ESMTP id 67FF2842F1; Mon, 14 Oct 2002 20:23:03 -0700 (PDT) To: Satish Dattatri Cc: stefano previdi , Jeff Parker , isis-wg@ietf.org Subject: Re: [Isis-wg] FW: IS-IS MIB (metric comments) In-reply-to: Mail from Satish Dattatri dated Mon, 14 Oct 2002 19:39:14 PDT <20021015023914.9590.qmail@web20609.mail.yahoo.com> From: Naiming Shen Message-Id: <20021015032303.67FF2842F1@prattle.redback.com> Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 14 Oct 2002 20:23:03 -0700 ] The metric configured does not matter when an interface is passive, changing passive interface metric(thus the metric of it's prefix) to control the inter-as traffic is a well-known technique used by ISPs. ] IP prefix advertisement will always be with zero cost. At a later ] point if the interface is made non-passive, the IP prefix advertisement ] will have the metric of the interface. Since, the configured value is ] not considered anyways for the advertisement of the IP prefix when ] passive, I think MIB range need not start with 0. ] ] Satish ] ] ] ] > We don't split passive interfaces from other interfaces ] ] ] >in the MIB. Thus, given the current design, if we allow a 0 ] ] ] >metric on a passive circuit, we are allowing a 0 metric on ] ] ] >any circuit, and thus allowing a 0-cost path to a neighbor. ] ] ] ] I think we should allow 0 to be inside the range. It's up to the ] ] implementation to block certain MIB settings. The MIB can give a ] ] union of all the possible configures exist/possible-to-have, if it ] ] does not want to specify the each specific cases. It's a local ] ] implementation issue to honor such a MIB request. The reverse approach, ] ] take a common dominate, does not sound right. ] ^^^^^^^^^ denominator. ] ] ] ] ] > We can add a warning that 0 should only be used when the ] ] ] >interface is passive, but it is not enforceable. ] ] ] ] ] ] ] ] ] but what are you going to do with implementations that ] ] ] already assign 0-metric to (passive)interfaces ? I think ] ] ] you should accept them. ] ] ] ] ] ] Again, I don't believe it's the role of a MIB/SNMP agent ] ] ] to handle these issues. ] ] ] ] ] ] s. ] ] ] ] ] ] _______________________________________________ ] ] ] Isis-wg mailing list ] ] ] Isis-wg@ietf.org ] ] ] https://www1.ietf.org/mailman/listinfo/isis-wg ] ] ] ] - Naiming ] ] - Naiming ] _______________________________________________ ] Isis-wg mailing list ] Isis-wg@ietf.org ] https://www1.ietf.org/mailman/listinfo/isis-wg ] ] ] ] __________________________________________________ ] Do you Yahoo!? ] Faith Hill - Exclusive Performances, Videos & More ] http://faith.yahoo.com ] _______________________________________________ ] Isis-wg mailing list ] Isis-wg@ietf.org ] https://www1.ietf.org/mailman/listinfo/isis-wg - Naiming _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 15 01:30:07 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11773 for ; Tue, 15 Oct 2002 01:30:06 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F5TUv14736; Tue, 15 Oct 2002 01:29:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9F5QKv14687 for ; Tue, 15 Oct 2002 01:26:20 -0400 Received: from net4u.net4u.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA11657 for ; Tue, 15 Oct 2002 01:23:59 -0400 (EDT) Received: from net4u.ch (zux006-011-046.adsl.green.ch [81.6.11.46]) by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g9F5Pwq07018; Tue, 15 Oct 2002 07:25:58 +0200 Message-ID: <3DAC24B8.7060807@net4u.ch> From: Tony Przygienda Reply-To: prz@net4u.ch User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Naiming Shen CC: stefano previdi , Jeff Parker , isis-wg@ietf.org Subject: Re: [Isis-wg] FW: IS-IS MIB (metric comments) References: <20021014223433.D8EF04F41A8@prattle.redback.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 07:22:48 -0700 Content-Transfer-Encoding: 7bit Naiming Shen wrote: > ] > We don't split passive interfaces from other interfaces > ] >in the MIB. Thus, given the current design, if we allow a 0 > ] >metric on a passive circuit, we are allowing a 0 metric on > ] >any circuit, and thus allowing a 0-cost path to a neighbor. > >I think we should allow 0 to be inside the range. It's up to the >implementation to block certain MIB settings. The MIB can give a >union of all the possible configures exist/possible-to-have, if it >does not want to specify the each specific cases. It's a local >implementation issue to honor such a MIB request. The reverse approach, >take a common dominate, does not sound right. > tend to agree, goes into the discussion I encouraged as 'good topic' on what the right range of MIB values should be. I don't think enforcing strict ranges except brain-dead values buys much and causes trouble later (when an implementation for some valid reason allows values outside the range) thanks -- tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 15 10:06:39 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02456 for ; Tue, 15 Oct 2002 10:06:39 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FE5fv16762; Tue, 15 Oct 2002 10:05:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FE22v16654 for ; Tue, 15 Oct 2002 10:02:02 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02146 for ; Tue, 15 Oct 2002 09:59:49 -0400 (EDT) Message-ID: From: Jeff Parker To: "'prz@net4u.ch'" , Naiming Shen Cc: stefano previdi , Jeff Parker , isis-wg@ietf.org Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 10:01:34 -0400 > > ] >... if we allow a 0 metric on a passive > > ] >circuit, we are allowing a 0 metric on > > ] >any circuit... > > > > I think we should allow 0 to be inside the range. > > > [I] tend to agree.... I don't think enforcing > strict ranges except brain-dead values buys > much and causes trouble later I have changed the minimum on DefaultMetric and WideMetric back to 0. I will be submitting the current version, which has undergone many changes in the last 2 months, at the end of the week. Drop me a line if you have the time and interest in reviewing it. Change log below. - jeff parker -- Changes in version 10 -- Add text to description of isisISAdjUsage -- Change default on throttle for Neal Castagnoli -- Rip out L1 and L2 objects from System and created SystemLevelTable -- Numerous changes in text accompany this -- Added isisIPRASourceType -- Restore min of 0 to Metric Textual Conventions -- Added SystemInstance variable to all notifications -- Rerordered objects in notifications to be more predictable -- Numerous edits from Dan Goodspeed -- Added 0 to ISPriority range -- Changed encoding of 'none' in ISLevel to 0, rather than 3 -- Replaced UpTime syntax with TimeTicks -- Rewrote descriptions of CircUpTime and AdjUpTime -- Rename variables to CircLastUpTime, AdjLastUpTime -- Removed comments about deprecated groups -- Edited description of isisCircEntry -- Added References for MeshGroup and MeshGroupEnabled -- Updated description -- Remove L1 from isisSysStatLSPDbaseOloads description -- Added isisCircNumAdj to count adjacencies on circuit -- Added isisPacketCountUnknown -- Removed LSPSize from isisAreaMismatch -- Added isisPDUFragment to isisRejectedAdjacency -- Updated description -- Remove isisRAFullMetric -- Changed indexing for isisIPRATable -- Replaced SNPA in index with IPNextHop -- Split isisISAdjNeighSysID into SysID and AdjExtendedCircID -- Added boolean isisCirc3WayEnabled -- Added isisISAdj3WayState, reordered enums in isisISAdjState -- Drop range on isisSysMaxAge from 1200 to 350 -- Added isisSysSetOverloadUntil object -- Added Adjacency Change notification _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 15 14:56:33 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11985 for ; Tue, 15 Oct 2002 14:56:33 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FIsgv00938; Tue, 15 Oct 2002 14:54:42 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FInIv00725 for ; Tue, 15 Oct 2002 14:49:18 -0400 Received: from xprdmailfe28.nwk.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11545 for ; Tue, 15 Oct 2002 14:47:02 -0400 (EDT) Received: by xprdmailfe28.nwk.excite.com (Postfix, from userid 110) id 8205FE57E; Tue, 15 Oct 2002 14:49:09 -0400 (EDT) To: satish_dattatri@yahoo.com, sprevidi@cisco.com, jparker@axiowave.com, naiming@redback.com Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) Received: from [63.104.212.252] by xprdmailfe28.nwk.excite.com via HTTP; Tue, 15 Oct 2002 14:49:09 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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 Cc: isis-wg@ietf.org Message-Id: <20021015184909.8205FE57E@xprdmailfe28.nwk.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 14:49:09 -0400 (EDT) Content-Transfer-Encoding: 7bit Satish, The metric can still be zero in isisIPRATable for the subnet that the passive interface belongs to. The attribute isisIPRAMetric is also mapped to the textual convention DefaultMetric. So even if the configured value is maintained (for when the interface is made non-passive), the cost to that interface in the isisIPRA Table would still be zero in some implementations. Whether the software zeroes the isisCircLevelMetric is up to the implementation. -don --- On Mon 10/14, Satish Dattatri wrote: From: Satish Dattatri [mailto: satish_dattatri@yahoo.com] To: sprevidi@cisco.com, jparker@axiowave.com, naiming@redback.com Cc: isis-wg@ietf.org Date: Mon, 14 Oct 2002 19:39:14 -0700 (PDT) Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) > The metric configured does not matter when an interface is passive, > IP prefix advertisement will always be with zero cost. At a later > point if the interface is made non-passive, the IP prefix advertisement > will have the metric of the interface. Since, the configured value is > not considered anyways for the advertisement of the IP prefix when > passive, I think MIB range need not start with 0. > > Satish > > ] ] > We don't split passive interfaces from other interfaces > ] ] >in the MIB. Thus, given the current design, if we allow a 0 > ] ] >metric on a passive circuit, we are allowing a 0 metric on > ] ] >any circuit, and thus allowing a 0-cost path to a neighbor. > ] > ] I think we should allow 0 to be inside the range. It's up to the > ] implementation to block certain MIB settings. The MIB can give a > ] union of all the possible configures exist/possible-to-have, if it > ] does not want to specify the each specific cases. It's a local > ] implementation issue to honor such a MIB request. The reverse > approach, > ] take a common dominate, does not sound right. > ^^^^^^^^^ denominator. > ] > ] ] > We can add a warning that 0 should only be used when > the > ] ] >interface is passive, but it is not enforceable. > ] ] > ] ] > ] ] but what are you going to do with implementations that > ] ] already assign 0-metric to (passive)interfaces ? I think > ] ] you should accept them. > ] ] > ] ] Again, I don't believe it's the role of a MIB/SNMP agent > ] ] to handle these issues. > ] ] > ] ] s. > ] ] > ] ] _______________________________________________ > ] ] Isis-wg mailing list > ] ] Isis-wg@ietf.org > ] ] https://www1.ietf.org/mailman/listinfo/isis-wg > ] > ] - Naiming > > - Naiming > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > > > > __________________________________________________ > Do you Yahoo!? > Faith Hill - Exclusive Performances, Videos & More > http://faith.yahoo.com > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ 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-admin@ietf.org Tue Oct 15 15:16:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12631 for ; Tue, 15 Oct 2002 15:16:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FJC7v02328; Tue, 15 Oct 2002 15:12:07 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FJ7Fv02124 for ; Tue, 15 Oct 2002 15:07:15 -0400 Received: from celox-ma1-ems1.celoxnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12232 for ; Tue, 15 Oct 2002 15:05:00 -0400 (EDT) Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19) id <4LBT7VHP>; Tue, 15 Oct 2002 15:07:10 -0400 Message-ID: <1117F7D44159934FB116E36F4ABF221B0102EA33@celox-ma1-ems1.celoxnetworks.com> From: "Ganguly, Shamik" To: "'isis-wg@ietf.org'" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] Queries for ISIS-MIB draft9 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 15:07:10 -0400 Jeff, I have a few queries regarding the newly released Draft 9 of ISIS-MIB. 1. Is there any special reason that the MIB has no table to read the LSP database? I mean, tables to see LSPs in the database and some information relating to them. 2. Why do you have separate tables for Reachable Addresses, namely isisRATable and isisIPRATable? Can they be clubbed together? Also if we do not have any plans for deploying our implementations in OSI networks, can the isisRATable be removed? Expanding the scope of the question, what value are you adding by both of these tables? 3. This query is regarding the table isisRedistributeAddrTable. In our ISIS implementation, if the global L2toL1Leaking flag is enabled, all L2 routes are leaked into L1. We can configure summary-filters to prevent certain prefixes to get into L1. But isisRedistributeAddrTable in draft9 works differently. Only those routes that match entries in this table are leaked into L1 by L2 routers. Could you explain the reasoning behind the design of this table? -Shamik _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 15 15:53:00 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13649 for ; Tue, 15 Oct 2002 15:53:00 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FJm5v04201; Tue, 15 Oct 2002 15:48:05 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FJh7v04034 for ; Tue, 15 Oct 2002 15:43:07 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13238 for ; Tue, 15 Oct 2002 15:40:51 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Ganguly, Shamik'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] Queries for ISIS-MIB draft9 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 15:42:51 -0400 > 1. Is there any special reason that the MIB has no table to > read the LSP database? I mean, tables to see LSPs in the > database and some information relating to them. Shamik - Excellent point. I don't know what I was thinking of. I will add the LSP table and send you a review copy by private mail. > 2. Why do you have separate tables for Reachable Addresses, namely > isisRATable and isisIPRATable? Can they be clubbed together? The RATable is for OSI addresses and the IPRA table is for IP addresses. I could club them together, but you wouldn't like the result. > .. if we do not have any plans for deploying our > implementations in OSI networks, can > the isisRATable be removed? Well, it is pretty easy to reply to a get on an empty table. > Expanding the scope of the question, what value > are you adding by both of these tables? Support Dual Protocol Routers > 3. This query is regarding the table > isisRedistributeAddrTable. In our ISIS > implementation, if the global L2toL1Leaking flag is enabled, > all L2 routes > are leaked into L1. We can configure summary-filters to > prevent certain > prefixes to get into L1. But isisRedistributeAddrTable in draft9 works > differently. Only those routes that match entries in this > table are leaked > into L1 by L2 routers. Could you explain the reasoning behind > the design of > this table? > > -Shamik Please review the version in the table I send you and I'll be happy to take your review comments. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 15 15:53:01 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13663 for ; Tue, 15 Oct 2002 15:53:01 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FJqov04392; Tue, 15 Oct 2002 15:52:50 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FJhPv04045 for ; Tue, 15 Oct 2002 15:43:25 -0400 Received: from xmxpita.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13262 for ; Tue, 15 Oct 2002 15:41:08 -0400 (EDT) Received: by xmxpita.excite.com (Postfix, from userid 110) id 7D8CC1E491; Tue, 15 Oct 2002 15:43:16 -0400 (EDT) To: sganguly@celoxnetworks.com, isis-wg@ietf.org Subject: RE: [Isis-wg] Queries for ISIS-MIB draft9 Received: from [63.104.212.252] by xprdmailfe25.nwk.excite.com via HTTP; Tue, 15 Oct 2002 15:43:16 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021015194316.7D8CC1E491@xmxpita.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 15:43:16 -0400 (EDT) Content-Transfer-Encoding: 7bit Answering #1 and #2 ... Shamik, 1) The syntax for the LSP Table is being reviewed by Jeff, myself, and a few others and will probably be included in version -11 of the MIB. 2) If you do not support OSI reachability (as some newer implemen- tations are going), you just do not return anything for the isisRATable. Supporting a table does not mean you HAVE to polulate a table. It just means you recognize it when a get, get-next, etc. is done on that table (don't crash, return proper error codes, etc.). As for #3, I second your question. We "may" need another attribute to handle this. At the very least, your implementation should install a 0.0.0.0/0 entry in the table indicating you are leaking all L2 routes into L1 by default. Cheers, -don --- On Tue 10/15, Ganguly, Shamik wrote: From: Ganguly, Shamik [mailto: sganguly@celoxnetworks.com] To: isis-wg@ietf.org Date: Tue, 15 Oct 2002 15:07:10 -0400 Subject: [Isis-wg] Queries for ISIS-MIB draft9 > Jeff, > > I have a few queries regarding the newly released Draft 9 of ISIS-MIB. > > 1. Is there any special reason that the MIB has no table to read the LSP > database? I mean, tables to see LSPs in the database and some information > relating to them. > > 2. Why do you have separate tables for Reachable Addresses, namely > isisRATable and isisIPRATable? Can they be clubbed together? Also if we > do > not have any plans for deploying our implementations in OSI networks, can > the isisRATable be removed? Expanding the scope of the question, what > value > are you adding by both of these tables? > > 3. This query is regarding the table isisRedistributeAddrTable. In our > ISIS > implementation, if the global L2toL1Leaking flag is enabled, all L2 > routes > are leaked into L1. We can configure summary-filters to prevent certain > prefixes to get into L1. But isisRedistributeAddrTable in draft9 works > differently. Only those routes that match entries in this table are > leaked > into L1 by L2 routers. Could you explain the reasoning behind the design > of > this table? > > -Shamik > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ 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-admin@ietf.org Tue Oct 15 16:15:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14276 for ; Tue, 15 Oct 2002 16:15:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FK3Gv04966; Tue, 15 Oct 2002 16:03:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FJwpv04773 for ; Tue, 15 Oct 2002 15:58:51 -0400 Received: from celox-ma1-ems1.celoxnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13741 for ; Tue, 15 Oct 2002 15:56:34 -0400 (EDT) Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19) id <4LBT7VPL>; Tue, 15 Oct 2002 15:58:45 -0400 Message-ID: <1117F7D44159934FB116E36F4ABF221B0102EA35@celox-ma1-ems1.celoxnetworks.com> From: "Ganguly, Shamik" To: "'dgoodspe@excite.com'" , "'Jeff Parker'" , isis-wg@ietf.org Subject: RE: [Isis-wg] Queries for ISIS-MIB draft9 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 15:58:44 -0400 Don and Jeff, Thanx for the quick responses. For your response to #3. We can change the interpretation of the isisRedistributeTable. The entries in this table are the ones that are NOT leaked to L1. Are there ISIS implementations that have a behaviour as in draft9 of this table? Another question related to the same point. Draft9 does not seem to have something to regulate leaking of routes to L2 from L1. We can either add a new field to isisRedistributeTable to differentiate between the two or create a separate table. -Shamik -----Original Message----- From: Don Goodspeed [mailto:dgoodspe@excite.com] Sent: Tuesday, October 15, 2002 3:43 PM To: sganguly@celoxnetworks.com; isis-wg@ietf.org Subject: RE: [Isis-wg] Queries for ISIS-MIB draft9 Answering #1 and #2 ... Shamik, 1) The syntax for the LSP Table is being reviewed by Jeff, myself, and a few others and will probably be included in version -11 of the MIB. 2) If you do not support OSI reachability (as some newer implemen- tations are going), you just do not return anything for the isisRATable. Supporting a table does not mean you HAVE to polulate a table. It just means you recognize it when a get, get-next, etc. is done on that table (don't crash, return proper error codes, etc.). As for #3, I second your question. We "may" need another attribute to handle this. At the very least, your implementation should install a 0.0.0.0/0 entry in the table indicating you are leaking all L2 routes into L1 by default. Cheers, -don --- On Tue 10/15, Ganguly, Shamik wrote: From: Ganguly, Shamik [mailto: sganguly@celoxnetworks.com] To: isis-wg@ietf.org Date: Tue, 15 Oct 2002 15:07:10 -0400 Subject: [Isis-wg] Queries for ISIS-MIB draft9 > Jeff, > > I have a few queries regarding the newly released Draft 9 of ISIS-MIB. > > 1. Is there any special reason that the MIB has no table to read the LSP > database? I mean, tables to see LSPs in the database and some information > relating to them. > > 2. Why do you have separate tables for Reachable Addresses, namely > isisRATable and isisIPRATable? Can they be clubbed together? Also if we > do > not have any plans for deploying our implementations in OSI networks, can > the isisRATable be removed? Expanding the scope of the question, what > value > are you adding by both of these tables? > > 3. This query is regarding the table isisRedistributeAddrTable. In our > ISIS > implementation, if the global L2toL1Leaking flag is enabled, all L2 > routes > are leaked into L1. We can configure summary-filters to prevent certain > prefixes to get into L1. But isisRedistributeAddrTable in draft9 works > differently. Only those routes that match entries in this table are > leaked > into L1 by L2 routers. Could you explain the reasoning behind the design > of > this table? > > -Shamik > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ 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-admin@ietf.org Tue Oct 15 16:17:20 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14415 for ; Tue, 15 Oct 2002 16:17:20 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FKGjv05946; Tue, 15 Oct 2002 16:16:45 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FK5lv05058 for ; Tue, 15 Oct 2002 16:05:47 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13971 for ; Tue, 15 Oct 2002 16:03:26 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Ganguly, Shamik'" , isis-wg@ietf.org Subject: RE: [Isis-wg] Queries for ISIS-MIB draft9 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 16:05:26 -0400 > Don and Jeff, > > Thanx for the quick responses. > > For your response to #3. We can change the interpretation of the > isisRedistributeTable. The entries in this table are the ones > that are NOT > leaked to L1. Are there ISIS implementations that have a > behaviour as in > draft9 of this table? Take a look at draft 10. > Another question related to the same point. Draft9 does not > seem to have > something to regulate leaking of routes to L2 from L1. We can > either add a > new field to isisRedistributeTable to differentiate between the two or > create a separate table. > > -Shamik Shamik - draft 9 is dead: long live draft 10. I have sent you a copy. If you didn't get it, we can work out an off-line transport mechanism. I'll buy you a beer and slip you a paper copy. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 15 18:25:56 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA17587 for ; Tue, 15 Oct 2002 18:25:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FMMSv12709; Tue, 15 Oct 2002 18:22:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9FMJFv12600 for ; Tue, 15 Oct 2002 18:19:15 -0400 Received: from web20606.mail.yahoo.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA17250 for ; Tue, 15 Oct 2002 18:16:58 -0400 (EDT) Message-ID: <20021015221908.68710.qmail@web20606.mail.yahoo.com> Received: from [207.135.89.74] by web20606.mail.yahoo.com via HTTP; Tue, 15 Oct 2002 15:19:08 PDT From: Satish Dattatri Subject: RE: [Isis-wg] FW: IS-IS MIB (metric comments) To: dgoodspe@excite.com, sprevidi@cisco.com, jparker@axiowave.com, naiming@redback.com Cc: isis-wg@ietf.org In-Reply-To: <20021015184909.8205FE57E@xprdmailfe28.nwk.excite.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 15 Oct 2002 15:19:08 -0700 (PDT) Hi Don, --- Don Goodspeed wrote: > > Satish, > > The metric can still be zero in isisIPRATable for the subnet > that the passive interface belongs to. The attribute isisIPRAMetric > is also mapped to the textual convention DefaultMetric. So Currently it is like that but if the ranges are different ... > even if the configured value is maintained (for when the interface > is made non-passive), the cost to that interface in the isisIPRA > Table would still be zero in some implementations. > > Whether the software zeroes the isisCircLevelMetric is up to the > implementation. > By making a circuit passive, a get on that circuit must give the configured metric. I agree that internally an implementation can achieve this in many ways. Naiming corrected my logic that people do want passive circuits to have non-zero cost (configurable). What I am a bit concerned is allowing a cost of zero to be configured on the circuit. Of course the implementation can take care of *changing* (behind the back) the metric to a default value when a ciruit with metric of 0 and passive is made non-passive. MIB tools will not like this. Thanks, Satish __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 16 12:55:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05619 for ; Wed, 16 Oct 2002 12:55:09 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GGFEv12688; Wed, 16 Oct 2002 12:15:32 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GFw3v11730 for ; Wed, 16 Oct 2002 11:58:03 -0400 Received: from celox-ma1-ems1.celoxnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA04376 for ; Wed, 16 Oct 2002 11:55:49 -0400 (EDT) Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19) id <4LBT7ZXP>; Wed, 16 Oct 2002 11:57:58 -0400 Message-ID: <1117F7D44159934FB116E36F4ABF221B0102EA3C@celox-ma1-ems1.celoxnetworks.com> From: "Ganguly, Shamik" To: "'Don Goodspeed'" , Jeff Parker , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Oct 2002 11:57:55 -0400 Hi, Suggestion from Don about BITS-defined string is acceptable for isisLSPAttributes. On second thought, it is also okay to keep the field as it was originally defined by Jeff. This table will most likely be used by people who do not need any initiation to isis protocol and deciphering 8 bits of data is not a big deal. On the pros side it will keep the implementation simple. I have a few more questions regarding draft 10. 1. Can we have a counter in the system counters table to count the number of times spf algorithm was executed starting when the system came up. 2. isisPacketCountUnknown should not be required. Why will an non-ISIS packet reach inside isis stack. Number of non-ISIS packets that were received by the system should be inconsequential to isis, so it should not be there in ISIS-MIB. 3. I had asked this question about draft9 as well. Draft10 does not seem to have something to regulate leaking of routes to L2 from L1. We can either add a new field to isisRedistributeTable to differentiate between the two or create a separate table. -Shamik -----Original Message----- From: Don Goodspeed [mailto:dgoodspe68@yahoo.com] Sent: Tuesday, October 15, 2002 7:16 PM To: Jeff Parker; 'Ganguly, Shamik'; 'Manral, Vishwas'; 'Joyal, Daniel R (Daniel)'; 'satish_dattatri@yahoo.com' Cc: Bingzhang Zhao Subject: RE: [Isis-wg] isisLSPTable Jeff and Shamik, Regarding #2, I was typing up a comment to suggest we change this from an Unsigned8TC to a BITS-defined string which better represents what this field actually is. Since each bit is enumerated, when the attribute is walked, or gotten directly, it reads something like: isisLSPAttributes.1.2.18.0.0.0.0.1.0.0 : BITS 0b attached(3) l2(1) l1(0) In this case, instead of a value of 11, it lists the hex value and lists the enumerations on those bits that are set to 1. The only caveat is that ISO 10589 numbers its bits 8 thru 1 while the BITS strings is numbered 7 thru 0 (left to right). -don --- Jeff Parker wrote: > > > 2. isisLSPAttributes should be broken into > separate fields for > > > PartitionRepairBit, AttachedBit and OverloadBit. > > > > Could do this. More work to get and view, but > could do this. > > > > This definitely has some value to it. > Will make the > > flags more > > readable. > > If SNMP bits on the wire were free, I would feel > much better > about this. > > > > 4. isisLSPTLVType field should be in enumeration > of the > > list of types supported. > > > > The idea is not to limit ourselves - we expect > people to add > > more types. > > > > Can we not add new enumerations when they > become > > available? Having enumerations will make the mib > more readable. > > So what will happen when a new TLV is introduced? > We need > to rev the mib? > > - jdp > __________________________________________________ Do you Yahoo!? Faith Hill - Exclusive Performances, Videos & More http://faith.yahoo.com _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 16 13:12:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06126 for ; Wed, 16 Oct 2002 13:12:29 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GHC3v15866; Wed, 16 Oct 2002 13:12:03 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GGLFv12897 for ; Wed, 16 Oct 2002 12:21:15 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04688 for ; Wed, 16 Oct 2002 12:19:01 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Ganguly, Shamik'" , "'Don Goodspeed'" , Jeff Parker , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Oct 2002 12:12:15 -0400 > Hi, > > On second thought, it is also okay to keep > the field as it was originally defined Done > 1. Can we have a counter in the system counters Done isisSysSPFRuns OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of times we ran SPF at this level." ::= { isisSystemCounterEntry 13 } > 2. isisPacketCountUnknown should not be required. Why will an non-ISIS > packet reach inside isis stack. Number of non-ISIS packets that were > received by the system should be inconsequential to isis, so > it should not > be there in ISIS-MIB. The header may look like an ISIS packet, but it isn't one of the select (not a hello. Not an LSP. Not...). Think of it as another error counter. > 3. Draft10 does not seem to have something to regulate > leaking of routes to L2 from L1. We can either > add a new field to isisRedistributeTable to differentiate > between the two or create a separate table. > > -Shamik Shamik - We have isisSysL2toL1Leaking and isisRedistributeAddrTable. What else do we need? - jeff parker -- The Redistribution table defines addresses that should be leaked from -- L2 to L1 if isisSysL2toL1Leaking is enabled. isisRedistributeAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF IsisRedistributeAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides criteria to decide if a route should be leaked from L2 to L1 when Domain Wide Prefix leaking is enabled. Addresses that match the summary mask in the table will be announced at L1 by routers when isisSysL2toL1Leaking is enabled. Routes that fall into the ranges specified are are announced as is, without being summarized." _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 16 13:12:41 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06139 for ; Wed, 16 Oct 2002 13:12:41 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GH9xv15754; Wed, 16 Oct 2002 13:09:59 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GGIHv12757 for ; Wed, 16 Oct 2002 12:18:17 -0400 Received: from celox-ma1-ems1.celoxnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04593 for ; Wed, 16 Oct 2002 12:16:02 -0400 (EDT) Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19) id <4LBT7ZZX>; Wed, 16 Oct 2002 12:17:51 -0400 Message-ID: <1117F7D44159934FB116E36F4ABF221B0102EA3E@celox-ma1-ems1.celoxnetworks.com> From: "Ganguly, Shamik" To: "'Jeff Parker'" , "'Don Goodspeed'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Oct 2002 12:17:49 -0400 > 3. Draft10 does not seem to have something to regulate > leaking of routes to L2 from L1. We can either > add a new field to isisRedistributeTable to differentiate > between the two or create a separate table. > > -Shamik Shamik - We have isisSysL2toL1Leaking and isisRedistributeAddrTable. What else do we need? - jeff parker -- The Redistribution table defines addresses that should be leaked from -- L2 to L1 if isisSysL2toL1Leaking is enabled. isisRedistributeAddrTable OBJECT-TYPE SYNTAX SEQUENCE OF IsisRedistributeAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table provides criteria to decide if a route should be leaked from L2 to L1 when Domain Wide Prefix leaking is enabled. Addresses that match the summary mask in the table will be announced at L1 by routers when isisSysL2toL1Leaking is enabled. Routes that fall into the ranges specified are are announced as is, without being summarized." I am talking of routes leaking from L1 to L2. Our implementation can configure prefixes/mask pairs that are not leaked to L2 from L1. My suggestion was to handle both of the scenarios, L1->L2 and L2->L1 from the same redistribute table, we just need to add an extra field to differentiate between the two. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 16 13:14:55 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06207 for ; Wed, 16 Oct 2002 13:14:55 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GHE6v15987; Wed, 16 Oct 2002 13:14:06 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GGNmv12980 for ; Wed, 16 Oct 2002 12:23:48 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04716 for ; Wed, 16 Oct 2002 12:21:34 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Ganguly, Shamik'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Oct 2002 12:23:36 -0400 > > > 3. Draft10 does not seem to have something to > > > regulate leaking of routes to L2 from L1. > > > Shamik - > > We have isisSysL2toL1Leaking and > > isisRedistributeAddrTable. What else do we need? > > I am talking of routes leaking from L1 to L2. Sorry for my confusion. > Our implementation can configure prefixes/mask > pairs that are not leaked to L2 from L1. My > suggestion was to handle both of the scenarios, > L1->L2 and L2->L1 from the same redistribute table, > we just need to add an extra field to differentiate > between the two. We have the Summary Table to deal with L1 to L2 leaking. I can add some text to point out that this is it's function, but it is described in RFC 1195. The functions of the two tables are different, as we summarize going up, but not going down. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 16 13:19:57 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06465 for ; Wed, 16 Oct 2002 13:19:57 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GHJ4v16290; Wed, 16 Oct 2002 13:19:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GGRXv13058 for ; Wed, 16 Oct 2002 12:27:33 -0400 Received: from celox-ma1-ems1.celoxnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04850 for ; Wed, 16 Oct 2002 12:25:19 -0400 (EDT) Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19) id <4LBT7Z6N>; Wed, 16 Oct 2002 12:27:29 -0400 Message-ID: <1117F7D44159934FB116E36F4ABF221B0102EA3F@celox-ma1-ems1.celoxnetworks.com> From: "Ganguly, Shamik" To: "'Jeff Parker'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Oct 2002 12:27:21 -0400 > > > 3. Draft10 does not seem to have something to > > > regulate leaking of routes to L2 from L1. > > > Shamik - > > We have isisSysL2toL1Leaking and > > isisRedistributeAddrTable. What else do we need? > > I am talking of routes leaking from L1 to L2. Sorry for my confusion. > Our implementation can configure prefixes/mask > pairs that are not leaked to L2 from L1. My > suggestion was to handle both of the scenarios, > L1->L2 and L2->L1 from the same redistribute table, > we just need to add an extra field to differentiate > between the two. We have the Summary Table to deal with L1 to L2 leaking. I can add some text to point out that this is it's function, but it is described in RFC 1195. The functions of the two tables are different, as we summarize going up, but not going down. - jeff parker That sounds okay. We then need to add some text to description of the summary table to make that point more clear. Also the isisLSPAttributes field, that we were talking about earlier, you may like to update the description field to explain about different attributes and there positions in the bitmap. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 16 15:28:22 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10090 for ; Wed, 16 Oct 2002 15:28:22 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GJOFv24281; Wed, 16 Oct 2002 15:24:16 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GJJGv24107 for ; Wed, 16 Oct 2002 15:19:16 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09846 for ; Wed, 16 Oct 2002 15:16:58 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Don Goodspeed'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Oct 2002 15:19:04 -0400 > Jeff, > > On [SPF Runs counter], is this a system counter, or a > system-level counter? There is a table that keeps per instance/level counts. Here is the list of indices and the variable again isisSystemCounterEntry OBJECT-TYPE SYNTAX IsisSystemCounterEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "System-wide IS-IS counters." INDEX { isisSysInstance, isisSysStatLevel } ::= { isisSystemCounterTable 1 } IsisSystemCounterEntry ::= SEQUENCE { isisSysStatLevel INTEGER, .... isisSysSPFRuns Counter32 } > > Also, on #2 below, the intent of my suggestion was > to include unknown packets of any type. This includes > ES Hello's on a system that does not support > processing > of ES Hello's. > > Of course, we could always add separate counters for > ES Hello's and ISH Hello's. To me, if we count IIH > Hello's, we should count these other two separately. > > Cheers, > Don I will add ES hellos, and rename the hello counter. - jdp IsisPacketCounterEntry ::= SEQUENCE { isisPacketCountLevel INTEGER, isisPacketCountDirection INTEGER, isisPacketCountISHello Counter32, isisPacketCountESHello Counter32, isisPacketCountLSP Counter32, isisPacketCountCSNP Counter32, isisPacketCountPSNP Counter32, isisPacketCountUnknown Counter32 } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 16 16:17:18 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA10998 for ; Wed, 16 Oct 2002 16:17:18 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GKG8v27143; Wed, 16 Oct 2002 16:16:08 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GKDqv27081 for ; Wed, 16 Oct 2002 16:13:52 -0400 Received: from rchss001.chiaro.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA10789 for ; Wed, 16 Oct 2002 16:11:32 -0400 (EDT) Received: (qmail 4261 invoked from network); 16 Oct 2002 20:04:01 -0000 Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81) by rchss001.chiaro.com with SMTP; 16 Oct 2002 20:04:01 -0000 Received: by MAIL with Internet Mail Service (5.5.2653.19) id <49BYV94A>; Wed, 16 Oct 2002 15:13:04 -0500 Message-ID: From: Laura Liu To: "Ganguly, Shamik" , "'Jeff Parker'" , "'Don Goodspeed'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Oct 2002 15:13:03 -0500 --=_IS_MIME_Boundary Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: Ganguly, Shamik [mailto:sganguly@celoxnetworks.com] > Sent: Wednesday, October 16, 2002 11:18 AM > To: 'Jeff Parker'; 'Don Goodspeed'; 'isis-wg@ietf.org' > Subject: RE: [Isis-wg] isisLSPTable > > > > > > 3. Draft10 does not seem to have something to regulate > > leaking of routes to L2 from L1. We can either > > add a new field to isisRedistributeTable to differentiate > > between the two or create a separate table. > > > > -Shamik > > Shamik - > We have isisSysL2toL1Leaking and > isisRedistributeAddrTable. What else do we need? > > - jeff parker > > -- The Redistribution table defines addresses that should be > leaked from > -- L2 to L1 if isisSysL2toL1Leaking is enabled. > > isisRedistributeAddrTable OBJECT-TYPE > SYNTAX SEQUENCE OF IsisRedistributeAddrEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table provides criteria to decide if a route should > be leaked from L2 to L1 when Domain Wide Prefix > leaking is > enabled. > > Addresses that match the summary mask in the table will > be announced at L1 by routers when isisSysL2toL1Leaking > is enabled. Routes that fall into the ranges specified > are are announced as is, without being summarized." > > I am talking of routes leaking from L1 to L2. Our > implementation > can configure prefixes/mask pairs that are not leaked to L2 > from L1. My > suggestion was to handle both of the scenarios, L1->L2 and > L2->L1 from the > same redistribute table, we just need to add an extra field > to differentiate > between the two. I second the suggestion on adding an attribute in isisRedistributeAddrTable to address L1->L2 leaking. I got the impression that L1->L2 leaking was covered by isisSummAddrTable, but some vendors/customers view leaking as part of redistribute. I would like to have all the leaking handled in one redistribution table. Laura > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > --=_IS_MIME_Boundary Content-Type: text/plain;charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit ----------------------------------------- (on rchss001) This e-mail and any files transmitted with it are the property of Chiaro Networks, Ltd., and may contain confidential and privileged material for the sole use of the intended recipient(s) to whom this e-mail is addressed. If you are not one of the named recipient(s), or otherwise have reason to believe that you have received this message in error, please notify the sender and delete all copies from your system. Any other use, retention, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. --------------------------------------------------------- --=_IS_MIME_Boundary-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 16 16:48:20 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11821 for ; Wed, 16 Oct 2002 16:48:20 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GKjbv28841; Wed, 16 Oct 2002 16:45:38 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9GKgSv28772 for ; Wed, 16 Oct 2002 16:42:28 -0400 Received: from xprdmailfe28.nwk.excite.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11613 for ; Wed, 16 Oct 2002 16:40:11 -0400 (EDT) Received: by xprdmailfe28.nwk.excite.com (Postfix, from userid 110) id 7971AE520; Wed, 16 Oct 2002 16:42:18 -0400 (EDT) To: jparker@axiowave.com, isis-wg@ietf.org Subject: RE: [Isis-wg] isisLSPTable Received: from [63.104.212.252] by xprdmailfe28.nwk.excite.com via HTTP; Wed, 16 Oct 2002 16:42:18 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = b4f718530cf8af0dd8df25e0425ffee0 Reply-To: dgoodspe@excite.com 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: <20021016204218.7971AE520@xprdmailfe28.nwk.excite.com> Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 16 Oct 2002 16:42:18 -0400 (EDT) Content-Transfer-Encoding: 7bit Jeff, On #1, I was confused by the name of the table since it does not imply the indexing (which IS per-level). Thanks. On #2, does the renamed ISHello include both IIH and ISH hello's? Cheers, Don --- On Wed 10/16, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: dgoodspe68@yahoo.com, isis-wg@ietf.org Date: Wed, 16 Oct 2002 15:19:04 -0400 Subject: RE: [Isis-wg] isisLSPTable > > > Jeff, > > > > On [SPF Runs counter], is this a system counter, or a > > system-level counter? > > There is a table that keeps per instance/level > counts. Here is the list of indices and the > variable again > > isisSystemCounterEntry OBJECT-TYPE > SYNTAX IsisSystemCounterEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "System-wide IS-IS counters." > INDEX { isisSysInstance, > isisSysStatLevel } > ::= { isisSystemCounterTable 1 } > > IsisSystemCounterEntry ::= > SEQUENCE { > isisSysStatLevel > INTEGER, > .... > isisSysSPFRuns > Counter32 > } > > > > > Also, on #2 below, the intent of my suggestion was > > to include unknown packets of any type. This includes > > ES Hello's on a system that does not support > > processing > > of ES Hello's. > > > > Of course, we could always add separate counters for > > ES Hello's and ISH Hello's. To me, if we count IIH > > Hello's, we should count these other two separately. > > > > Cheers, > > Don > > I will add ES hellos, and rename the hello counter. > > - jdp > > IsisPacketCounterEntry ::= > SEQUENCE { > isisPacketCountLevel > INTEGER, > isisPacketCountDirection > INTEGER, > isisPacketCountISHello > Counter32, > isisPacketCountESHello > Counter32, > isisPacketCountLSP > Counter32, > isisPacketCountCSNP > Counter32, > isisPacketCountPSNP > Counter32, > isisPacketCountUnknown > Counter32 > } > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ 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-admin@ietf.org Thu Oct 17 14:03:28 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20100 for ; Thu, 17 Oct 2002 14:03:28 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9HI4Hv08878; Thu, 17 Oct 2002 14:04:17 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9HI1tv08817 for ; Thu, 17 Oct 2002 14:01:55 -0400 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19992 for ; Thu, 17 Oct 2002 13:59:39 -0400 (EDT) Message-ID: From: Jeff Parker To: "'Laura Liu'" , "Ganguly, Shamik" , "'Don Goodspeed'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 17 Oct 2002 14:01:04 -0400 > > Shamik - > > We have isisSysL2toL1Leaking and > > isisRedistributeAddrTable. What else do we need? > > > > - jeff parker > I second the suggestion on adding an attribute in > isisRedistributeAddrTable to address L1->L2 > leaking. I got the impression that L1->L2 leaking > was covered by isisSummAddrTable, but some > vendors/customers view leaking as part of > redistribute. I would like to have all the leaking > handled in one redistribution table. > > Laura Laura - While I'm not saying this can't be done, I'm on record as believing that leaking in the two directions is pretty different. Perhaps you could work up a proposal that we could discuss. I'm planning to submit the MIB this week, and I don't think I have time to redo this table. However, as soon as this is submitted, we can start working on the next version. But the MIB has changed enough since version 9 that I would like to have a public document for folks to comment on rather than to continue to work via samizdat. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu Oct 17 17:55:25 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27336 for ; Thu, 17 Oct 2002 17:55:25 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9HLrXv23510; Thu, 17 Oct 2002 17:53:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9HLoTv23457 for ; Thu, 17 Oct 2002 17:50:29 -0400 Received: from celox-ma1-ems1.celoxnetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA27067 for ; Thu, 17 Oct 2002 17:48:11 -0400 (EDT) Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19) id <4LBT8BBZ>; Thu, 17 Oct 2002 17:50:23 -0400 Message-ID: <1117F7D44159934FB116E36F4ABF221B0102EA47@celox-ma1-ems1.celoxnetworks.com> From: "Ganguly, Shamik" To: "'Jeff Parker'" Cc: "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] isisLSPTable MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 17 Oct 2002 17:50:13 -0400 Jeff, Some smaller naming issues before you finalise the mib. Could you name isisSystemLevelTable to isisSysLevelTable and also prepend all fields in this table with isisSysLevel. It is a cosmetic change but in line with SNMP naming conventions. -Shamik -----Original Message----- From: Jeff Parker [mailto:jparker@axiowave.com] Sent: Thursday, October 17, 2002 1:32 PM To: 'Ganguly, Shamik' Subject: RE: [Isis-wg] isisLSPTable I will probably send in something tomorrow. The version you have is pretty close to my current version, but I would be happy to send you a new copy - jdp > > Jeff, > > Comments to draft 10 seem to have died down. Do you plan to > come out with a > new draft or make changes to draft 10 itself? When do you > want to publish > it? I will like to have a copy of the version soon. > > -Shamik > > -----Original Message----- > From: Jeff Parker [mailto:jparker@axiowave.com] > Sent: Tuesday, October 15, 2002 5:56 PM > To: 'Ganguly, Shamik'; Jeff Parker; 'Don Goodspeed'; 'Manral, > Vishwas'; > 'Joyal, Daniel R (Daniel)'; 'satish_dattatri@yahoo.com' > Cc: Bingzhang Zhao > Subject: RE: [Isis-wg] isisLSPTable > > > > > 2. isisLSPAttributes should be broken into separate fields for > > > PartitionRepairBit, AttachedBit and OverloadBit. > > > > Could do this. More work to get and view, but could do this. > > > > This definitely has some value to it. Will make the > > flags more > > readable. > > If SNMP bits on the wire were free, I would feel much better > about this. > > > > 4. isisLSPTLVType field should be in enumeration of the > > list of types supported. > > > > The idea is not to limit ourselves - we expect people to add > > more types. > > > > Can we not add new enumerations when they become > > available? Having enumerations will make the mib more readable. > > So what will happen when a new TLV is introduced? We need > to rev the mib? > > - jdp > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 21 16:40:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14745 for ; Mon, 21 Oct 2002 16:40:44 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LKcvv22309; Mon, 21 Oct 2002 16:38:58 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LKNRv21208 for ; Mon, 21 Oct 2002 16:23:27 -0400 Received: from panda.host4u.net (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13872 for ; Mon, 21 Oct 2002 16:21:06 -0400 (EDT) Received: from coastin.com (pool-138-89-97-69.mad.east.verizon.net [138.89.97.69]) by panda.host4u.net (8.11.6/8.11.6) with ESMTP id g9LKN9c07233 for ; Mon, 21 Oct 2002 15:23:09 -0500 Message-ID: <3DB4620F.EBBE6E24@coastin.com> From: Tom Rutt Reply-To: tom@coastin.com X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: isis-wg@ietf.org Content-Type: multipart/mixed; boundary="------------C960925BB1D9DB1A9B13937F" Subject: [Isis-wg] [Fwd: Why is ISO IS-IS routing Version 2 not completed] Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 21 Oct 2002 16:22:39 -0400 This is a multi-part message in MIME format. --------------C960925BB1D9DB1A9B13937F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@fsw.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133 --------------C960925BB1D9DB1A9B13937F Content-Type: message/rfc822 Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <3DB461C9.1F51673D@coastin.com> Date: Mon, 21 Oct 2002 16:21:30 -0400 From: Tom Rutt Reply-To: tom@coastin.com X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: t3@mail-list.com, tli@procket.com, prz@xebeo.com, fenner@research.att.com, zinin@psg.com, tom@coastin.com Subject: Why is ISO IS-IS routing Version 2 not completed Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I am the US International Representative for INCITS/T3, which is the US tag for JTC1/SC6 WG7. This is where the IS-IS, and ES-IS routing standard projects are based. I have discovered that the IS-IS second edition (which Mica Bartel assembled and to through FDIS ballot) has not been finalized in ISO. This is perhaps due to the unfortunate fact that the US removed itself from SC6 as a National Body, for a year, as Mica was finalizing the text. Does anyone on this list know the whereabouts of Mica Bartel, the editor of the Is-Is routing ISO standard? Can anyone, or Mica himself, please send me a response email if they know anything about this. I have addressed this mail to the t3 mailing list and the relevant IETF chairs and area directors. I thought that the final text of version two was completed by Mica, what is the status of finalizing this text. The US is now part of SC6 of JTC1, so we can now respond to this ballot. It should be finalilized so the world has a definitive standard which incorporates the rats nest of amendments and corrigenda to the original ISO/IEC IS-IS routing standard. -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@fsw.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133 --------------C960925BB1D9DB1A9B13937F-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Oct 21 17:10:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15707 for ; Mon, 21 Oct 2002 17:10:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LLAMv24603; Mon, 21 Oct 2002 17:10:22 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9LL7cv24498 for ; Mon, 21 Oct 2002 17:07:38 -0400 Received: from sj-msg-core-3.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15596 for ; Mon, 21 Oct 2002 17:05:15 -0400 (EDT) Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.151]) by sj-msg-core-3.cisco.com (8.12.2/8.12.2) with ESMTP id g9LL7NxF003388; Mon, 21 Oct 2002 14:07:23 -0700 (PDT) Received: from nisser.cisco.com (localhost [127.0.0.1]) by sj-msg-av-1.cisco.com (8.12.2/8.12.2) with ESMTP id g9LL7ORk008648; Mon, 21 Oct 2002 14:07:24 -0700 (PDT) Received: from MBARTELL-W2K.cisco.com (mbartell-w2k.cisco.com [64.101.135.176]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id OAA07348; Mon, 21 Oct 2002 14:07:22 -0700 (PDT) Message-Id: <5.1.1.6.2.20021021160708.02e53c08@cactus.cisco.com> X-Sender: mbartell@cactus.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 5.1.1 To: tom@coastin.com From: Micah Bartell Subject: Re: [Isis-wg] [Fwd: Why is ISO IS-IS routing Version 2 not completed] Cc: isis-wg@ietf.org In-Reply-To: <3DB4620F.EBBE6E24@coastin.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 21 Oct 2002 16:07:23 -0500 Taking this off-line.... /mpb At 16:22 10/21/2002 -0400, Tom Rutt wrote: >-- >---------------------------------------------------- >Tom Rutt email: tom@coastin.com; trutt@fsw.fujitsu.com >Tel: +1 732 801 5744 Fax: +1 732 774 5133 > >X-Mozilla-Status2: 00000000 >Message-ID: <3DB461C9.1F51673D@coastin.com> >Date: Mon, 21 Oct 2002 16:21:30 -0400 >From: Tom Rutt >Reply-To: tom@coastin.com >X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U) >X-Accept-Language: en >MIME-Version: 1.0 >To: t3@mail-list.com, tli@procket.com, prz@xebeo.com, > fenner@research.att.com, zinin@psg.com, tom@coastin.com >Subject: Why is ISO IS-IS routing Version 2 not completed >Content-Type: text/plain; charset=us-ascii >Content-Transfer-Encoding: 7bit > >I am the US International Representative for INCITS/T3, which is the US >tag for JTC1/SC6 WG7. This is where the IS-IS, and ES-IS routing >standard projects >are based. > >I have discovered that the IS-IS second edition (which Mica Bartel >assembled and >to through FDIS ballot) has not been finalized in ISO. This is perhaps >due to the unfortunate >fact that the US removed itself from SC6 as a National Body, for a year, >as Mica was >finalizing the text. > >Does anyone on this list know the whereabouts of Mica Bartel, the editor >of >the Is-Is routing ISO standard? Can anyone, or Mica himself, please >send me >a response email if they know anything about this. > >I have addressed this mail to the t3 mailing list and the relevant IETF >chairs and area >directors. > >I thought that the final text of version two was completed by Mica, >what is the status of >finalizing this text. > >The US is now part of SC6 of JTC1, so we can now respond to this ballot. > >It should be finalilized so the world has a definitive standard which >incorporates the >rats nest of amendments and corrigenda to the original ISO/IEC IS-IS >routing standard. >-- >---------------------------------------------------- >Tom Rutt email: tom@coastin.com; trutt@fsw.fujitsu.com >Tel: +1 732 801 5744 Fax: +1 732 774 5133 _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 22 07:47:16 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12559 for ; Tue, 22 Oct 2002 07:47:16 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MBkTv08131; Tue, 22 Oct 2002 07:46:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MBgtv07994 for ; Tue, 22 Oct 2002 07:42:55 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12164; Tue, 22 Oct 2002 07:40:38 -0400 (EDT) Message-Id: <200210221140.HAA12164@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-mib-10.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 22 Oct 2002 07:40:37 -0400 --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-10.txt Pages : 90 Date : 2002-10-21 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-10.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-wg-mib-10.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-10.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: <2002-10-21143313.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-wg-mib-10.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-wg-mib-10.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2002-10-21143313.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 22 13:20:40 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27005 for ; Tue, 22 Oct 2002 13:20:40 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MHJOv26831; Tue, 22 Oct 2002 13:19:25 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9MHGPv26719 for ; Tue, 22 Oct 2002 13:16:25 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26707; Tue, 22 Oct 2002 13:14:04 -0400 (EDT) Message-Id: <200210221714.NAA26707@ietf.org> To: IETF-Announce: ; Cc: RFC Editor , Internet Architecture Board , isis-wg@ietf.org From: The IESG Subject: [Isis-wg] Document Action: Extending the Number of IS-IS LSP Fragments Beyond the 256 Limit to Informational Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 22 Oct 2002 13:14:03 -0400 The IESG has approved the Internet-Draft 'Extending the Number of IS-IS LSP Fragments Beyond the 256 Limit' as an Informational RFC. This document is the product of the IS-IS for IP Internets Working Group. The IESG contact persons are Bill Fenner and Alex Zinin. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 23 17:46:53 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06415 for ; Wed, 23 Oct 2002 17:46:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NLjfv26218; Wed, 23 Oct 2002 17:45:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NLgjv26152 for ; Wed, 23 Oct 2002 17:42:45 -0400 Received: from net4u.net4u.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06232 for ; Wed, 23 Oct 2002 17:40:20 -0400 (EDT) Received: from net4u.ch (zux006-013-072.adsl.green.ch [81.6.13.72]) by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g9NLga106876 for ; Wed, 23 Oct 2002 23:42:36 +0200 Message-ID: <3DB717C6.8060605@net4u.ch> From: Tony Przygienda Reply-To: prz@net4u.ch User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 X-Accept-Language: en-us, en MIME-Version: 1.0 To: isis-wg@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Isis-wg] last call on draft-ietf-isis-gmpls-extensions has ended ... Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 23 Oct 2002 23:42:30 +0200 Content-Transfer-Encoding: 7bit -- tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 23 17:54:14 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06603 for ; Wed, 23 Oct 2002 17:54:13 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NLs4v26466; Wed, 23 Oct 2002 17:54:04 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9NLp3v26374 for ; Wed, 23 Oct 2002 17:51:03 -0400 Received: from net4u.net4u.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06441 for ; Wed, 23 Oct 2002 17:48:38 -0400 (EDT) Received: from net4u.ch (zux006-013-072.adsl.green.ch [81.6.13.72]) by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g9NLos107710 for ; Wed, 23 Oct 2002 23:50:54 +0200 Message-ID: <3DB719B9.3040404@net4u.ch> From: Tony Przygienda Reply-To: prz@net4u.ch User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 X-Accept-Language: en-us, en MIME-Version: 1.0 To: isis-wg@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Isis-wg] last call on draft-ietf-isis-wg-multi-topology-05 Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 23 Oct 2002 23:50:49 +0200 Content-Transfer-Encoding: 7bit We are (re-)starting last call on draft-ietf-isis-wg-multi-topology-05. The last call will end 11/11/02 Please review carefully, some major changes have been incorporated ... thanks -- tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 06:26:36 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28720 for ; Tue, 29 Oct 2002 06:26:36 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TBPbv05357; Tue, 29 Oct 2002 06:25:38 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TBLYv05116 for ; Tue, 29 Oct 2002 06:21:34 -0500 Received: from ws1-8.us4.outblaze.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA28089 for ; Tue, 29 Oct 2002 06:19:10 -0500 (EST) Received: (qmail 63212 invoked by uid 1001); 29 Oct 2002 11:11:15 -0000 Message-ID: <20021029111115.63211.qmail@iname.com> Content-Type: text/plain; charset="iso-8859-15" Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-Mailer: MIME-tools 5.41 (Entity 5.404) Received: from [149.254.120.136] by ws1-8.us4.outblaze.com with http for philip.christian@iname.com; Tue, 29 Oct 2002 11:11:15 +0000 From: "Philip Christian" To: isis-wg@ietf.org X-Originating-Ip: 149.254.120.136 X-Originating-Server: ws1-8.us4.outblaze.com Content-Transfer-Encoding: 7bit Subject: [Isis-wg] draft-ietf-isis-ipv6-02.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 29 Oct 2002 11:11:15 +0000 Content-Transfer-Encoding: 7bit I just noticed that draft-ietf-isis-ipv6-02.txt is beyond its expiration date. Isn't this too important to just let it die ? Philip -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 09:21:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05043 for ; Tue, 29 Oct 2002 09:21:19 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TEHXv15208; Tue, 29 Oct 2002 09:17:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TEEuv15144 for ; Tue, 29 Oct 2002 09:14:56 -0500 Received: from tahoe.sj.allegronetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04697 for ; Tue, 29 Oct 2002 09:12:31 -0500 (EST) Received: by tahoe.allegronetworks.com with Internet Mail Service (5.5.2653.19) id ; Tue, 29 Oct 2002 06:14:51 -0800 Message-ID: From: Chris Hopps To: "'Philip Christian'" Cc: "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] draft-ietf-isis-ipv6-02.txt MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 29 Oct 2002 06:14:50 -0800 Yes. I am working with the ADs to iron out a couple details, after which I will publish an updated draft. Chris. -----Original Message----- From: Philip Christian [mailto:philip.christian@iname.com] Sent: Tuesday, October 29, 2002 3:11 AM To: isis-wg@ietf.org Subject: [Isis-wg] draft-ietf-isis-ipv6-02.txt I just noticed that draft-ietf-isis-ipv6-02.txt is beyond its expiration date. Isn't this too important to just let it die ? Philip -- __________________________________________________________ Sign-up for your own FREE Personalized E-mail at Mail.com http://www.mail.com/?sr=signup _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 17:26:09 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29683 for ; Tue, 29 Oct 2002 17:26:09 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TMLZv10701; Tue, 29 Oct 2002 17:21:36 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TMIqv10597 for ; Tue, 29 Oct 2002 17:18:52 -0500 Received: from titanium.ekay.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29270 for ; Tue, 29 Oct 2002 17:16:23 -0500 (EST) Received: from localhost ([127.0.0.1] helo=titanium.ekay.org) by titanium.ekay.org with esmtp (Exim 3.35 #1 (Debian)) id 186eiA-0001PU-00 for ; Tue, 29 Oct 2002 14:19:46 -0800 Message-ID: <87of9ckhvh.wl@titanium.ekay.org> From: Noguchi Kay To: isis-wg@ietf.org In-Reply-To: <20021008013559.590273E2D@xmxpita.excite.com> References: <20021008013559.590273E2D@xmxpita.excite.com> User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Subject: [Isis-wg] editorial comments to -10 mib draft Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 29 Oct 2002 14:19:46 -0800 Hi Jeff, Some tiny editorial comments to -10 draft. 1, isisRedistributeAddr and isisSysLevel info should be there in Section 4 like below - isisSummAddr This table holds summary addresses configured for each Level 2 instance of the IS-IS protocol running on a router. - isisRedistributeAddr This table holds redistributed addresses which is leaked from L2 to L1. - isisSysLevel This table contains information specific to a domain(Level-2) or an area(Level-1) of the IS-IS protocol. 2, isisSysLevelTable mibs should be placed after isisRedistributeAddrTable. 3, isisLSPTTLVType should be isisLSPTLVType 4, isisLSPId should be isisLSPID to sync with isisTrapLSPID, isisSysID, CircuitID... Thank you, kay _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 17:44:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00093 for ; Tue, 29 Oct 2002 17:44:04 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TMhfv11969; Tue, 29 Oct 2002 17:43:41 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TMeVv11867 for ; Tue, 29 Oct 2002 17:40:31 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29959 for ; Tue, 29 Oct 2002 17:38:02 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 186f27-0003gz-00 for isis-wg@ietf.org; Tue, 29 Oct 2002 14:40:23 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.51) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <4654850691.20021029144017@psg.com> To: "'isis-wg@ietf.org'" MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IETF and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 29 Oct 2002 14:40:17 -0800 Content-Transfer-Encoding: 7bit Folks- Below is the announcement of the IETF Last Call for the draft text of the agreement between IETF and ISO/IEC JTC1 on ISIS. The text is a product of a many-month process involved discussions with JTC1 SC6 management, IESG and IAB. The ISIS WG chairs were also asked to review the early versions of the document. The latest version of the text found in the document has been discussed at the SC6 UK meeting that happened this month. I've been informed that UK will support this agreement and will bring it to the SC6 plenary meeting in London in Feb. Please review the text of the agreement. Because of the complex coordination process with another standards development organization, which involves huge delays, I'd like to ask folks to bring up only really important issues, so that we minimize the changes to the text as much as possible. When sending comments, please cc iesg@ietf.org and iab@ietf.org. I would also like us to discuss this agreement at the ISIS WG meeting in Atlanta. Tonys, please allocate a time slot for this. Thank you! -- Alex This is a forwarded message From: The IESG To: Cc: Date: Tuesday, October 29, 2002, 1:49:02 PM Subject: Last Call: Draft of agreement between ISOC/IETF and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational ===8<==============Original message text=============== This Internet-Draft documents proposes text of an agreement between ISOC/IETF and ISO/IEC JTC1/SC6 regarding cooperative development of the IS-IS routing protocol extensions. For a long time there has been no guidelines on how the two organizations should work together and separate their IS-IS related work scopes. This resulted in a confusion where the IETF did not put Internet-related extensions of the protocol on its standards track, and there was no authority maintaining the IS-IS namespace. The agreement between the two organizations is an attempt to resolve this situation. This Internet-Draft does not propose any changes to IETF processes or priorities. It describes (among other things) how the IETF processes are applied to the IS-IS protocol extensions. The IESG is issuing this Last-Call for review by the IETF community to ensure that the community is comfortable with the description of the proposed collaboration between the two organizations. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by November 29, 2002. Files can be obtained via http://www.ietf.org/internet-drafts/draft-zinin-ietf-jtc1-aggr-00.txt ===8<===========End of original message text=========== _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 17:49:23 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00277 for ; Tue, 29 Oct 2002 17:49:23 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TMnAv12193; Tue, 29 Oct 2002 17:49:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TMkWv12114 for ; Tue, 29 Oct 2002 17:46:32 -0500 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00090 for ; Tue, 29 Oct 2002 17:44:03 -0500 (EST) Message-ID: From: Jeff Parker To: "'Noguchi Kay'" Cc: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] editorial comments to -10 mib draft MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 29 Oct 2002 17:46:15 -0500 > Some tiny editorial comments to -10 draft. Thanks > 1, isisRedistributeAddr and isisSysLevel info should be there > in Section 4 > like below Done > 3, isisLSPTTLVType should be isisLSPTLVType thanks > 4, isisLSPId should be isisLSPID to sync with isisTrapLSPID, > isisSysID, CircuitID... Done > 2, isisSysLevelTable mibs should be placed after > isisRedistributeAddrTable. I don't mind moving it, but I don't see the reason to do so. Why is that a better place for it? - jeff parker > Thank you, > > kay > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 18:00:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00548 for ; Tue, 29 Oct 2002 18:00:19 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TN0Cv12530; Tue, 29 Oct 2002 18:00:12 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TMvmv12481 for ; Tue, 29 Oct 2002 17:57:48 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00409 for ; Tue, 29 Oct 2002 17:55:19 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 186fIq-0004qx-00 for isis-wg@ietf.org; Tue, 29 Oct 2002 14:57:40 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.51) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <19055886650.20021029145732@psg.com> To: "'isis-wg@ietf.org'" Subject: Re: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IETF and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational In-Reply-To: <4654850691.20021029144017@psg.com> References: <4654850691.20021029144017@psg.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 29 Oct 2002 14:57:32 -0800 Content-Transfer-Encoding: 7bit A small clarification (thanks to Jeff for asking): positive result of the LC will not mean immediate publication of the agreement as an Info RFC, but that the community is comfortable with ISOC/IETF signing this agreement with JTC1. Once/if it is signed, the text will be published as Info RFC for information to the community. Again, we'll walk through the agreement in detail in Atlanta. -- Alex Tuesday, October 29, 2002, 2:40:17 PM, Alex Zinin wrote: > Folks- > Below is the announcement of the IETF Last Call for the draft > text of the agreement between IETF and ISO/IEC JTC1 on ISIS. > The text is a product of a many-month process involved discussions > with JTC1 SC6 management, IESG and IAB. The ISIS WG chairs were also > asked to review the early versions of the document. The latest > version of the text found in the document has been discussed at the > SC6 UK meeting that happened this month. I've been informed that > UK will support this agreement and will bring it to the SC6 plenary > meeting in London in Feb. > Please review the text of the agreement. Because of the complex > coordination process with another standards development organization, > which involves huge delays, I'd like to ask folks to bring up only > really important issues, so that we minimize the changes to the text > as much as possible. When sending comments, please cc iesg@ietf.org > and iab@ietf.org. > I would also like us to discuss this agreement at the ISIS WG > meeting in Atlanta. Tonys, please allocate a time slot for this. > Thank you! _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 18:12:44 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00991 for ; Tue, 29 Oct 2002 18:12:44 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TNCAv13642; Tue, 29 Oct 2002 18:12:10 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TN9Wv13548 for ; Tue, 29 Oct 2002 18:09:32 -0500 Received: from titanium.ekay.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00825 for ; Tue, 29 Oct 2002 18:07:03 -0500 (EST) Received: from localhost ([127.0.0.1] helo=titanium.ekay.org) by titanium.ekay.org with esmtp (Exim 3.35 #1 (Debian)) id 186fVG-0001iG-00 for ; Tue, 29 Oct 2002 15:10:30 -0800 Message-ID: <87n0owkfix.wl@titanium.ekay.org> From: Noguchi Kay To: "ISIS-WG (E-mail)" Subject: Re: [Isis-wg] editorial comments to -10 mib draft In-Reply-To: References: User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 29 Oct 2002 15:10:30 -0800 Hi Jeff, > > 2, isisSysLevelTable mibs should be placed after > > isisRedistributeAddrTable. > > I don't mind moving it, but I don't see the reason to do so. > Why is that a better place for it? From the mib point of view, isisSysLevelTable is after isisRedistributeTable shown below. .1.3.6.1.3.37.1.1.6: isisRedistributeTable .1.3.6.1.3.37.1.2.1: isisSysLevelTable Thank you, kay _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 18:30:40 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01506 for ; Tue, 29 Oct 2002 18:30:40 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TNUPv14313; Tue, 29 Oct 2002 18:30:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9TNRwv14239 for ; Tue, 29 Oct 2002 18:27:58 -0500 Received: from net4u.net4u.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA01340 for ; Tue, 29 Oct 2002 18:25:28 -0500 (EST) Received: from net4u.ch (zux006-013-072.adsl.green.ch [81.6.13.72]) by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g9TNRlh01831; Wed, 30 Oct 2002 00:27:47 +0100 Message-ID: <3DBF196E.8080101@net4u.ch> From: Tony Przygienda Reply-To: prz@net4u.ch User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Zinin CC: "'isis-wg@ietf.org'" Subject: Re: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IETF and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational References: <4654850691.20021029144017@psg.com> <19055886650.20021029145732@psg.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 00:27:42 +0100 Content-Transfer-Encoding: 7bit Alex Zinin wrote: >A small clarification (thanks to Jeff for asking): positive result of >the LC will not mean immediate publication of the agreement as an Info >RFC, but that the community is comfortable with ISOC/IETF signing this >agreement with JTC1. Once/if it is signed, the text will be published >as Info RFC for information to the community. > >Again, we'll walk through the agreement in detail in Atlanta. > actually, looks good to me and almost everything said in the doc makes sense. The only point would be the (if we ever decide to resurrect it) encapsulation into IP (or maybe even any other e.g. sub-IP stuff). That would be ISO work based on this document so maybe you want to think whether you want to give up control here. To be clear, saying that I am taking my draft author hat off here (hey, maybe I would even get to go to some swanky ISO meeting places if it gets submitted to ISO ;-) and thinking as IP biggot ... thanks -- tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Oct 29 21:36:19 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05497 for ; Tue, 29 Oct 2002 21:36:19 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9U2Zov23397; Tue, 29 Oct 2002 21:35:51 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9U2W5v23324 for ; Tue, 29 Oct 2002 21:32:05 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA05087 for ; Tue, 29 Oct 2002 21:29:35 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 186ie9-000It3-00; Tue, 29 Oct 2002 18:31:53 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.51) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <1459500320.20021029183146@psg.com> To: Tony Przygienda CC: "'isis-wg@ietf.org'" Subject: Re: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IETF and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational In-Reply-To: <3DBF196E.8080101@net4u.ch> References: <4654850691.20021029144017@psg.com> <19055886650.20021029145732@psg.com> <3DBF196E.8080101@net4u.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 29 Oct 2002 18:31:46 -0800 Content-Transfer-Encoding: 7bit Tony, Thanks for the comment! I think the case of IP encapsulation could potentially be mapped to 2.2 b) as a supplementary encapsulation technique, provided that we make it clear that the problem is Internet-specific, we're talking exclusively about IP-enabled implementations in specific deployment scenarios, and not trying to generally change IS-IS encapsulation, which would affect existing dual implementations. I don't think we could really provide perfect generic guidelines for this type of "on-the-border" cases where we step on each other's toes, as they will anyways need to be considered on a case-by-case basis, most probably involving both IETF and JTC SC6 management to eliminate possible misunderstanding. -- Alex Tuesday, October 29, 2002, 3:27:42 PM, Tony Przygienda wrote: > actually, looks good to me and almost everything said in the doc makes > sense. > The only point would be the (if we ever decide to > resurrect it) encapsulation into IP (or maybe even any other e.g. sub-IP > stuff). > That would be ISO work based on this document so > maybe you want to think whether you want to give up control here. To be > clear, > saying that I am taking my > draft author hat off here (hey, maybe I would even get to go to some swanky > ISO meeting places if it gets submitted to ISO ;-) and thinking as IP > biggot ... > thanks > -- tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 03:59:05 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA06201 for ; Wed, 30 Oct 2002 03:59:05 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9U8w3v18912; Wed, 30 Oct 2002 03:58:03 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9U8s0v18787 for ; Wed, 30 Oct 2002 03:54:00 -0500 Received: from net4u.net4u.ch (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA05989 for ; Wed, 30 Oct 2002 03:51:27 -0500 (EST) Received: from net4u.ch (zux006-013-072.adsl.green.ch [81.6.13.72]) by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g9U8rjh24418; Wed, 30 Oct 2002 09:53:45 +0100 Message-ID: <3DBF9E14.9080808@net4u.ch> From: Tony Przygienda Reply-To: prz@net4u.ch User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Alex Zinin CC: "'isis-wg@ietf.org'" Subject: Re: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IETF and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational References: <4654850691.20021029144017@psg.com> <19055886650.20021029145732@psg.com> <3DBF196E.8080101@net4u.ch> <1459500320.20021029183146@psg.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 09:53:40 +0100 Content-Transfer-Encoding: 7bit Alex Zinin wrote: >Tony, > > Thanks for the comment! > > I think the case of IP encapsulation could potentially be mapped to > 2.2 b) as a supplementary encapsulation technique, provided that we > make it clear that the problem is Internet-specific, we're talking > exclusively about IP-enabled implementations in specific deployment > scenarios, and not trying to generally change IS-IS encapsulation, > which would affect existing dual implementations. > ok, as long that's clear on both sides ... thanks -- tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 05:20:29 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07138 for ; Wed, 30 Oct 2002 05:20:28 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UAJrv23247; Wed, 30 Oct 2002 05:19:53 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UAHXv23196 for ; Wed, 30 Oct 2002 05:17:33 -0500 Received: from xover.netplane.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA07028 for ; Wed, 30 Oct 2002 05:15:09 -0500 (EST) Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19) id <4B0HP3DT>; Wed, 30 Oct 2002 05:17:31 -0500 Message-ID: From: "Jonnala, Nagi" To: "'Jeff Parker'" Cc: "ISIS-WG (E-mail)" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] Query on isisISAdjAreaAddrTable of ISIS-MIB. Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 05:19:46 -0500 Jeff, Can we remove isisISAdjAreaAddress from the list of indices? I believe isisISAdjAreaAddrIndex can index in the table. Thanks Nagi. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 10:32:24 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19837 for ; Wed, 30 Oct 2002 10:32:24 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UFQfv09633; Wed, 30 Oct 2002 10:26:42 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UFNFv09531 for ; Wed, 30 Oct 2002 10:23:15 -0500 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18930 for ; Wed, 30 Oct 2002 10:20:49 -0500 (EST) Message-ID: From: Jeff Parker To: "'Alex Zinin'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IET F and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 10:23:05 -0500 One of the first things I hope will come out of this new accord is a ruling on the spelling of the protocol. Is it ISIS or IS-IS? - jeff parker - axiowave networks - All those who believe in psychokinesis, raise my hand. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 10:41:21 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20730 for ; Wed, 30 Oct 2002 10:41:21 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UFZxv10368; Wed, 30 Oct 2002 10:35:59 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UFVNv10149 for ; Wed, 30 Oct 2002 10:31:23 -0500 Received: from tahoe.sj.allegronetworks.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19629 for ; Wed, 30 Oct 2002 10:28:57 -0500 (EST) Received: by tahoe.allegronetworks.com with Internet Mail Service (5.5.2653.19) id ; Wed, 30 Oct 2002 07:31:19 -0800 Message-ID: From: Chris Hopps To: "'Jeff Parker'" Cc: "'isis-wg@ietf.org'" , "'Alex Zinin'" Subject: RE: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IET F and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 07:31:13 -0800 Nah, it's ISISIDREPCPPCNS Chris. -----Original Message----- From: Jeff Parker [mailto:jparker@axiowave.com] Sent: Wednesday, October 30, 2002 7:23 AM To: 'Alex Zinin'; 'isis-wg@ietf.org' Subject: RE: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IET F and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational One of the first things I hope will come out of this new accord is a ruling on the spelling of the protocol. Is it ISIS or IS-IS? - jeff parker - axiowave networks - All those who believe in psychokinesis, raise my hand. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 10:48:26 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA21113 for ; Wed, 30 Oct 2002 10:48:26 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UFm8v11627; Wed, 30 Oct 2002 10:48:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UFj2v11519 for ; Wed, 30 Oct 2002 10:45:02 -0500 Received: from cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20787 for ; Wed, 30 Oct 2002 10:42:35 -0500 (EST) Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4178.cisco.com [10.50.16.81]) by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id PAA07758; Wed, 30 Oct 2002 15:44:22 GMT Message-Id: <4.3.2.7.2.20021030154147.04557d68@jaws.cisco.com> X-Sender: mshand@jaws.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: Chris Hopps From: mike shand Subject: RE: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IET F and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational Cc: "'Jeff Parker'" , "'isis-wg@ietf.org'" , "'Alex Zinin'" In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 15:44:21 +0000 At 07:31 30/10/2002 -0800, Chris Hopps wrote: >Nah, it's > >ISISIDREPCPPCNS But does R stand for Routing or Routeing? :-) and it's IS-IS definitely. Mike >Chris. > >-----Original Message----- >From: Jeff Parker [mailto:jparker@axiowave.com] >Sent: Wednesday, October 30, 2002 7:23 AM >To: 'Alex Zinin'; 'isis-wg@ietf.org' >Subject: RE: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IET F >and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational > >One of the first things I hope will come out of this >new accord is a ruling on the spelling of the protocol. >Is it ISIS or IS-IS? > >- jeff parker >- axiowave networks >- All those who believe in psychokinesis, raise my hand. > >_______________________________________________ >Isis-wg mailing list >Isis-wg@ietf.org >https://www1.ietf.org/mailman/listinfo/isis-wg >_______________________________________________ >Isis-wg mailing list >Isis-wg@ietf.org >https://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 11:43:49 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA24255 for ; Wed, 30 Oct 2002 11:43:48 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UGaLv14804; Wed, 30 Oct 2002 11:36:22 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UGXwv14714 for ; Wed, 30 Oct 2002 11:33:58 -0500 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23501 for ; Wed, 30 Oct 2002 11:31:31 -0500 (EST) Message-ID: From: Jeff Parker To: "'Jonnala, Nagi'" , Jeff Parker Cc: "ISIS-WG (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] RE: Query on isisISAdjAreaAddrTable of ISIS-MIB. Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 11:33:18 -0500 > Jeff, > > Can we remove isisISAdjAreaAddress from the list of indices? > I believe isisISAdjAreaAddrIndex can index in the table. > > Thanks > Nagi. Nagi - Are you working from version 10? I think someone has already had me pull the index. - jeff parker -- The IS Adjacency Area Address Table contains the set of -- Area Addresses of neighboring -- Intermediate Systems as reported in IIH PDUs. .... isisISAdjAreaAddrEntry OBJECT-TYPE SYNTAX IsisISAdjAreaAddrEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Each entry contains one Area Address reported by a neighboring Intermediate System in its IIH PDUs." INDEX { isisSysInstance, isisCircIndex, isisISAdjIndex, isisISAdjAreaAddrIndex } ::= { isisISAdjAreaAddrTable 1 } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 13:07:32 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA00094 for ; Wed, 30 Oct 2002 13:07:31 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UI7Jv22744; Wed, 30 Oct 2002 13:07:19 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UI4sv22162 for ; Wed, 30 Oct 2002 13:04:54 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29798 for ; Wed, 30 Oct 2002 13:02:26 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 186xCw-000FNC-00; Wed, 30 Oct 2002 10:04:46 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.51) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <15865473956.20021030100440@psg.com> To: Tony Przygienda CC: "'isis-wg@ietf.org'" Subject: Re: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IETF and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational In-Reply-To: <3DBF9E14.9080808@net4u.ch> References: <4654850691.20021029144017@psg.com> <19055886650.20021029145732@psg.com> <3DBF196E.8080101@net4u.ch> <1459500320.20021029183146@psg.com> <3DBF9E14.9080808@net4u.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 10:04:40 -0800 Content-Transfer-Encoding: 7bit Tony, >> I think the case of IP encapsulation could potentially be mapped to >> 2.2 b) as a supplementary encapsulation technique, provided that we >> make it clear that the problem is Internet-specific, we're talking >> exclusively about IP-enabled implementations in specific deployment >> scenarios, and not trying to generally change IS-IS encapsulation, >> which would affect existing dual implementations. >> > ok, as long that's clear on both sides ... As Jeff privately suggested, maybe we should have some words about such questionable situations. Alex _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 14:05:27 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04402 for ; Wed, 30 Oct 2002 14:05:27 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJ58v26112; Wed, 30 Oct 2002 14:05:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UJ2Tv25996 for ; Wed, 30 Oct 2002 14:02:29 -0500 Received: from psg.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA04158 for ; Wed, 30 Oct 2002 14:00:00 -0500 (EST) Received: from psg.com ([147.28.0.62] helo=127.0.0.1 ident=zinin) by psg.com with esmtp (Exim 3.36 #2) id 186y6f-000Ibt-00; Wed, 30 Oct 2002 11:02:21 -0800 From: Alex Zinin X-Mailer: The Bat! (v1.51) Personal Reply-To: Alex Zinin X-Priority: 3 (Normal) Message-ID: <15168926050.20021030110212@psg.com> To: Jeff Parker CC: "'isis-wg@ietf.org'" Subject: Re: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IET F and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 11:02:12 -0800 Content-Transfer-Encoding: 7bit Wednesday, October 30, 2002, 7:23:05 AM, Jeff Parker wrote: > One of the first things I hope will come out of this > new accord is a ruling on the spelling of the protocol. > Is it ISIS or IS-IS? I think this issue is important enough to warrant a joint ISIS WG & SC6 interim meeting for a couple of days somewhere in Hawaii ;-p _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 15:03:41 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07822 for ; Wed, 30 Oct 2002 15:03:41 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UK3Qv29954; Wed, 30 Oct 2002 15:03:26 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9UK09v29862 for ; Wed, 30 Oct 2002 15:00:09 -0500 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA07234 for ; Wed, 30 Oct 2002 14:57:39 -0500 (EST) Received: from redback.com (yoo-hoo.redback.com [155.53.12.43]) by prattle.redback.com (Postfix) with ESMTP id 19F222848A3; Wed, 30 Oct 2002 12:00:02 -0800 (PST) To: Alex Zinin Cc: Jeff Parker , "'isis-wg@ietf.org'" Subject: Re: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IET F and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational In-reply-to: Mail from Alex Zinin dated Wed, 30 Oct 2002 11:02:12 PST <15168926050.20021030110212@psg.com> From: Naiming Shen Message-Id: <20021030200002.19F222848A3@prattle.redback.com> Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 12:00:02 -0800 ] Wednesday, October 30, 2002, 7:23:05 AM, Jeff Parker wrote: ] > One of the first things I hope will come out of this ] > new accord is a ruling on the spelling of the protocol. ] > Is it ISIS or IS-IS? ] ] I think this issue is important enough to warrant ] a joint ISIS WG & SC6 interim meeting for a couple ] of days somewhere in Hawaii ;-p ] agreed. when you guys are at meeting, pls also consider the following by the beach: - isis - is-is - misis - m-isis - m-is-is - MISIS - M-ISIS - M-IS-IS many thanks:-) - Naiming _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Oct 30 23:36:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25724 for ; Wed, 30 Oct 2002 23:36:30 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V4Ybv26236; Wed, 30 Oct 2002 23:34:38 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9V4VEv26151 for ; Wed, 30 Oct 2002 23:31:14 -0500 Received: from xover.netplane.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA25602 for ; Wed, 30 Oct 2002 23:28:42 -0500 (EST) Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19) id <4B0HPQD2>; Wed, 30 Oct 2002 23:31:04 -0500 Message-ID: From: "Jonnala, Nagi" To: "'Jeff Parker'" Cc: "ISIS-WG (E-mail)" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] isisAreaAddrTable index Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 30 Oct 2002 23:33:15 -0500 Jeff, Thanks for the clarification on isisISAdjAreaAddrTable. I have another question on isisAreaAddrTable(The union of the sets of area addresses reported in all Level 1 LSPs). I noticed isisAreaAddr is one of the index into the table. Being the read-only object, Can't we consider having an isisAreaAddrIndex instead of direct object as the index. Notes: 1) We have the same kind of isisISAdjAreaAddrIndex for isisISAdjAreaAddrTable. 2) For isisManAreaAddrTable, it does make sense to have isisManAreaAddr as the index because we use it for SET operations also. Thanks Nagi. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu Oct 31 08:42:30 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA18694 for ; Thu, 31 Oct 2002 08:42:30 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VDfkv32123; Thu, 31 Oct 2002 08:41:47 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VDcjv32005 for ; Thu, 31 Oct 2002 08:38:45 -0500 Received: from rchss001.chiaro.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA18447 for ; Thu, 31 Oct 2002 08:36:18 -0500 (EST) Received: (qmail 28886 invoked from network); 31 Oct 2002 13:28:34 -0000 Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81) by rchss001.chiaro.com with SMTP; 31 Oct 2002 13:28:34 -0000 Received: by MAIL with Internet Mail Service (5.5.2653.19) id <49BYXNRN>; Thu, 31 Oct 2002 07:37:53 -0600 Message-ID: From: Laura Liu To: "Jonnala, Nagi" , "'Jeff Parker'" Cc: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] isisAreaAddrTable index MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 31 Oct 2002 07:37:52 -0600 --=_IS_MIME_Boundary Content-Type: text/plain; charset="iso-8859-1" > -----Original Message----- > From: Jonnala, Nagi [mailto:nagij@netplane.com] > Sent: Wednesday, October 30, 2002 10:33 PM > To: 'Jeff Parker' > Cc: ISIS-WG (E-mail) > Subject: [Isis-wg] isisAreaAddrTable index > > > > Jeff, > > Thanks for the clarification on isisISAdjAreaAddrTable. > > I have another question on isisAreaAddrTable(The union of the > sets of area > addresses reported in all Level 1 LSPs). I noticed > isisAreaAddr is one of > the index into the table. Being the read-only object, Can't > we consider > having an isisAreaAddrIndex instead > of direct object as the index. > There was a discussion on using IP address or area address as part of index, using area address will keep index permanent during neighbor configuration. The order of manual/union addresses could change when a new area address being added/deleted by a neighbor. I would like to see area address as part of index in isisAreaAddrTable and isisManAreaAddrTable. isisISAdjAreaAddrTable is ok to use isisISAdjAreaAddrIndex, since isisISAdjIndex is before isisISAdjAreaAddrIndex to point out which neighbor it refers to. regrads, Laura > Notes: > > 1) We have the same kind of isisISAdjAreaAddrIndex for > isisISAdjAreaAddrTable. > > 2) For isisManAreaAddrTable, it does make sense to have > isisManAreaAddr as the index because we use it for SET > operations also. > > Thanks > Nagi. > > > > > > _______________________________________________ > Isis-wg mailing list > Isis-wg@ietf.org > https://www1.ietf.org/mailman/listinfo/isis-wg > --=_IS_MIME_Boundary Content-Type: text/plain;charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: 7bit ----------------------------------------- (on rchss001) This e-mail and any files transmitted with it are the property of Chiaro Networks, Ltd., and may contain confidential and privileged material for the sole use of the intended recipient(s) to whom this e-mail is addressed. If you are not one of the named recipient(s), or otherwise have reason to believe that you have received this message in error, please notify the sender and delete all copies from your system. Any other use, retention, dissemination, forwarding, printing or copying of this e-mail is strictly prohibited. --------------------------------------------------------- --=_IS_MIME_Boundary-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu Oct 31 15:24:04 2002 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13050 for ; Thu, 31 Oct 2002 15:24:04 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VKMVv26859; Thu, 31 Oct 2002 15:22:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g9VKJwv26749 for ; Thu, 31 Oct 2002 15:19:58 -0500 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12874 for ; Thu, 31 Oct 2002 15:17:28 -0500 (EST) Message-ID: From: Jeff Parker To: "'Alex Zinin'" , "'isis-wg@ietf.org'" Subject: RE: [Isis-wg] Fwd: Last Call: Draft of agreement between ISOC/IET F and SO/IEC JTC1/SC6 on IS-IS protocol development to Informational MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 31 Oct 2002 15:19:41 -0500 First, let me say that I think this is a great step forward. Having said that, it is something we should consider pretty carefully in the very limited time a Last Call allows. I re-read this last night, and started going down the list of current Drafts, and tried to figure out where each would fall. I would be interested to see how others would sort the documents. Granted that we can still publish anything we like: the issue is simply the status of the document. But it is an interesting exercise. For example, where does the M-IS-IS work fall? Comments below marked with leading >>. > > This Internet-Draft documents proposes text of an > agreement between > ISOC/IETF and ISO/IEC JTC1/SC6 regarding cooperative > development of > the IS-IS routing protocol extensions. > Files can be obtained via > http://www.ietf.org/internet-drafts/draft-zinin-ietf-jtc1-aggr-00.txt >> So thinking out loud about the split 2. Definitions 2.1 Core IS-IS Mechanisms Core IS-S Mechanisms are subsystems with associated algorithms, data structures, and PDU formats as specified in (ISO/IEC 10589), constituting the core of the IS-IS protocol and including the following elements: a) Framework of PDU formats, including standard TLVs >> Standard means? Things defined in 10589, plus anything that JTCL adds? I'm a bit leary about this term, if only because it suggests that TLV 0x81 isn't 'standard'. Perhaps we could clarify, or call this something like "JTCL Standard". b) Encapsulation of PDUs >> Tony has spoken to this. c) Adjacency state machine and formation logic >> We have recently played in these waters when adding the clause about matching IP interface addresses on either side. d) DIS election algorithm e) Initial LSP synchronization via CSNP exchange f) Asynchronous LSP flooding (including DIS flooding behavior) >> The recent draft on flooding over multiple links applies g) LSP database maintenance including LSP origination, aging, and purging h) Standard topology abstraction >> What about "P2P over LANs"? 2.2 Internet-specific IS-IS Extensions: Internet-specific IS-IS Extensions are extensions to the IS-IS proto- col that are within the work scope of the IETF (including, but not limited to IPv4 or IPv6 unicast and multicast routing, MPLS, MPLS TE, GMPLS, or any other routing technology that the IETF decides to work on in future), and: >> That last clause "or any other routing technology that the IETF decides to work on in future)" is very vague. Would it apply to MPLS, where it not already grandfathered in? (I could argue that MPLS is a switching rather than routing technology) - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg