From isis-wg-admin@ietf.org Mon May 3 11:58:53 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09631 for ; Mon, 3 May 2004 11:58:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKflZ-000461-N7; Mon, 03 May 2004 11:54:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BKfgT-00030G-8q for isis-wg@optimus.ietf.org; Mon, 03 May 2004 11:48:45 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09075 for ; Mon, 3 May 2004 11:48:42 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BKfgS-0002Fg-4t for isis-wg@ietf.org; Mon, 03 May 2004 11:48:44 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BKffV-0002Ci-00 for isis-wg@ietf.org; Mon, 03 May 2004 11:47:46 -0400 Received: from barao.cpqd.com.br ([200.231.0.47]) by ietf-mx with esmtp (Exim 4.12) id 1BKfey-00029e-00 for isis-wg@ietf.org; Mon, 03 May 2004 11:47:13 -0400 Received: from fw-cpqd (dmz-int.cpqd.com.br [200.231.0.35]) by barao.cpqd.com.br (8.11.6p2/8.11.6) with SMTP id i43Fl6K01647 for ; Mon, 3 May 2004 12:47:06 -0300 Received: from gandalf.cpqd.com.br ([10.202.128.110]) by fw-cpqd; Mon, 03 May 2004 12:46:22 -0300 (EST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6524.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Message-ID: <5BA4300ABA254E4CA8D3994568E52EE3808962@MAILSRV1.aquarius.cpqd.com.br> Thread-Topic: has ISIS MIB been standardized ? Thread-Index: AcQxJa2yjqTYm/A7QkOFf+CKzDZvYQ== From: =?iso-8859-1?Q?Lavoisier_Jos=E9_Leite_Farias?= To: X-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.6 required=5.0 tests=AWL,DEAR_SOMETHING autolearn=no version=2.60 Content-Transfer-Encoding: quoted-printable Subject: [Isis-wg] has ISIS MIB been standardized ? 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, 3 May 2004 12:45:37 -0300 Content-Transfer-Encoding: quoted-printable Dear Sir, I am knew in this list, so I apologize for any beginneers question. I took a look at IETF ISIS Workgroup and figure out that the ISIS MIB is = still a draft document. I also understand that this document will become = a standard only if there is an commercial implemmentation of that RFC. = So, Does anybody know what are current ISIS MIB commercial = implementations ?=20 If this kind of question is not proper for this list, please let me know = or answer directly to my e-maill. Thank you in advance, Regards,=20 Lavoisier J.L.Farias=20 Engenheiro de Sistemas de Telecomunica=E7=F5es CPqD Telecom & IT Solutions=20 Telefone : +55-19-3705-5758 / Fax +55-19-3705-663 =20 lfarias@cpqd.com.br =20 www.cpqd.com.br _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue May 4 14:50:00 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA20384 for ; Tue, 4 May 2004 14:50:00 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL4pz-0002pQ-Ov; Tue, 04 May 2004 14:40:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL4kg-0000oR-4S for isis-wg@optimus.ietf.org; Tue, 04 May 2004 14:34:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18953 for ; Tue, 4 May 2004 14:34:42 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL4kd-0005Yt-G9 for isis-wg@ietf.org; Tue, 04 May 2004 14:34:43 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL4jg-0005Rt-00 for isis-wg@ietf.org; Tue, 04 May 2004 14:33:45 -0400 Received: from smtp2.procket.com ([65.174.124.37]) by ietf-mx with esmtp (Exim 4.12) id 1BL4in-0005E5-00 for isis-wg@ietf.org; Tue, 04 May 2004 14:32:49 -0400 Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60]) by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i44KciAw063711; Tue, 4 May 2004 13:38:44 -0700 (PDT) Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id i44IUsd1006545; Tue, 4 May 2004 11:30:54 -0700 (PDT) Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 4 May 2004 11:30:54 -0700 In-Reply-To: <4.3.2.7.2.20040421082315.01b967b8@mira-sjc5-3.cisco.com> References: <4.3.2.7.2.20040420195526.02212da8@jaws.cisco.com> <98F04BA831360C4FB5F7FC0118D91828034A2782@pi.jnpr.net> <4.3.2.7.2.20040421082315.01b967b8@mira-sjc5-3.cisco.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <2F3832A5-9DF9-11D8-8941-00039303E9E2@procket.com> Content-Transfer-Encoding: 7bit Cc: Jeelani Syed , David Ward , "" , mike shand From: Christian Hopps Subject: Re: [Isis-wg] ISIS graceful restart... To: "Les Ginsberg" X-Mailer: Apple Mail (2.613) X-OriginalArrivalTime: 04 May 2004 18:30:54.0903 (UTC) FILETIME=[EF960C70:01C43205] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit 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, 4 May 2004 11:30:57 -0700 Content-Transfer-Encoding: 7bit On Apr 21, 2004, at 8:26 AM, Les Ginsberg wrote: > Here is the change proposed by Mike and myself to address this issue: > > Section 3.3.1 "Adjacency reacquisition during restart", page 10, para > 2: > > Current text: > "Once the timer T3 has expired or been cancelled, subsequent IIHs > are..." > > Revised text: > "Once the timer T1 has been cancelled, subsequent IIHs are ..." [...] > If this revision is acceptable, Alex has agreed to try to get this > into the > doc before the RFC is published. Given I've reviewed the change and the WG has had time to review it as well, I've sent mail to Alex requesting that this change be made, and that the draft continue forward towards RFC. Chris. > Les _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue May 4 16:28:25 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27282 for ; Tue, 4 May 2004 16:28:25 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL6Ra-0004Gx-Ox; Tue, 04 May 2004 16:23:10 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL6MQ-0002q9-EJ for isis-wg@optimus.ietf.org; Tue, 04 May 2004 16:17:50 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA26669 for ; Tue, 4 May 2004 16:17:45 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL6MM-00022s-GR for isis-wg@ietf.org; Tue, 04 May 2004 16:17:46 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL6LP-0001vY-00 for isis-wg@ietf.org; Tue, 04 May 2004 16:16:47 -0400 Received: from mailgate.pit.comms.marconi.com ([169.144.68.6]) by ietf-mx with esmtp (Exim 4.12) id 1BL6KV-0001jW-00 for isis-wg@ietf.org; Tue, 04 May 2004 16:15:51 -0400 Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id i44KDVQG012792; Tue, 4 May 2004 16:13:31 -0400 (EDT) Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id QAA00414; Tue, 4 May 2004 16:13:31 -0400 (EDT) Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19) id ; Tue, 4 May 2004 16:13:31 -0400 Message-ID: <313680C9A886D511A06000204840E1CF06DACD88@whq-msgusr-02.pit.comms.marconi.com> From: "Krishnan, Vijay G." To: "'Christian Hopps'" , Les Ginsberg , mike shand Cc: Jeelani Syed , David Ward , "" Subject: RE: [Isis-wg] ISIS graceful restart... MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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, 4 May 2004 16:13:30 -0400 Also, there are some incorrect cross references to sections 4.2.1 and 4.4 on page 10/11. These should be 3.2.1 and 3.4 respectively. -----Original Message----- From: Christian Hopps [mailto:chopps@procket.com] Sent: Tuesday, May 04, 2004 2:31 PM To: Les Ginsberg Cc: Jeelani Syed; David Ward; ; mike shand Subject: Re: [Isis-wg] ISIS graceful restart... On Apr 21, 2004, at 8:26 AM, Les Ginsberg wrote: > Here is the change proposed by Mike and myself to address this issue: > > Section 3.3.1 "Adjacency reacquisition during restart", page 10, para > 2: > > Current text: > "Once the timer T3 has expired or been cancelled, subsequent IIHs > are..." > > Revised text: > "Once the timer T1 has been cancelled, subsequent IIHs are ..." [...] > If this revision is acceptable, Alex has agreed to try to get this > into the > doc before the RFC is published. Given I've reviewed the change and the WG has had time to review it as well, I've sent mail to Alex requesting that this change be made, and that the draft continue forward towards RFC. Chris. > Les _______________________________________________ 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 May 4 17:09:52 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29418 for ; Tue, 4 May 2004 17:09:52 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL766-00062k-GE; Tue, 04 May 2004 17:05:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL6wb-0003vn-FH for isis-wg@optimus.ietf.org; Tue, 04 May 2004 16:55:13 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA28722 for ; Tue, 4 May 2004 16:55:10 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL6wZ-0006Xo-C8 for isis-wg@ietf.org; Tue, 04 May 2004 16:55:11 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL6vR-0006Pe-00 for isis-wg@ietf.org; Tue, 04 May 2004 16:54:02 -0400 Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx with esmtp (Exim 4.12) id 1BL6uw-0006Is-00 for isis-wg@ietf.org; Tue, 04 May 2004 16:53:30 -0400 Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Isis-wg] Mib Updates 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, 4 May 2004 16:52:18 -0400 I have sent version 14 of the ISIS MIB to the draft editors. The change list from the document is included below. At this point, I think we have the major functionality in place. The Notifications have been through a rev or two, and are starting to settle down. I hope that we can wrap things up and put it up for MIB doctor review. If you have functionality that you do not think is represented, this would be a good time to speak up. - jeff parker -- Changes in version 14 -- -- Set DEFVAL for isisCirc3WayEnabled to true -- Revised description for isisPacketCountIIHello -- Removed isisSysStatMaxAreaAddrMismatches as -- duplicating isisCircMaxAreaAddrMismatches -- Replaced isisManAreaAddrExistState with isisManAreaAddr -- in isisManualAddressDrops -- Drop isisSysLevelIndex in isisDatabaseOverload -- Drop restriction from isisCircIndex - SYNTAX Integer32 (1..2000000000) -- Change syntax of FullMetric to SYNTAX Unsigned32 -- Corrections to description of isisSysMaxLSPGenInt, isisSysMaxAge -- Change access levels of isisSysInstance and isisSysLevelIndex -- Fix references for isisCircPassiveCircuit, isisCircLevelCSNPInterval -- Fix description of isisISAdjIndex -- Replace level 1 with L2, level 2 with L2 -- Fix description of isisISAdjAreaAddrIndex -- Fix description of isisCircExtendedCircID -- Clarify description of isisCircLevelID -- Added isisSysStatLSPErrors to count LSPs with parse errors, -- and new Notification isisLSPErrorDetected -- Clarify domain of isisCircInitFails and isisCircRejAdjs -- Modified isisIPRATable for ECMP -- Removed RemoteRouterID from OwnLSPPurge _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue May 4 17:40:28 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01048 for ; Tue, 4 May 2004 17:40:28 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7Z9-0006ad-7y; Tue, 04 May 2004 17:35:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7SB-0003K0-Hx for isis-wg@optimus.ietf.org; Tue, 04 May 2004 17:27:51 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00406 for ; Tue, 4 May 2004 17:27:47 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL7S9-0002mt-6I for isis-wg@ietf.org; Tue, 04 May 2004 17:27:49 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL7RD-0002hj-00 for isis-wg@ietf.org; Tue, 04 May 2004 17:26:52 -0400 Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx with esmtp (Exim 4.12) id 1BL7QP-0002XA-00 for isis-wg@ietf.org; Tue, 04 May 2004 17:26:01 -0400 Message-ID: From: Jeff Parker To: =?iso-8859-1?Q?=27Lavoisier_Jos=E9_Leite_Farias=27?= Cc: "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] has ISIS MIB been standardized ? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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, 4 May 2004 17:25:16 -0400 > I took a look at IETF ISIS Workgroup and figure out that the > ISIS MIB is still a draft document. I also understand that > this document will become a standard only if there is an > commercial implemmentation of that RFC. So, Does anybody know > what are current ISIS MIB commercial implementations ? > > If this kind of question is not proper for this list, please > let me know or answer directly to my e-maill. > > Thank you in advance, > Regards, > > Lavoisier J.L.Farias Dear Mr. Lavoisier - There are still a few more hoops we need to jump through before we need to call for implementations. I believe that the next step is to get a review from the Mib Literati. There are a number of people who have sent me mail publicly and privately with MIB questions. I assume that they are working to some extent on implementations of the MIB. Others are waiting for the magic moment when they think the specification is cooked to implement. Alas, it is up to them to respond to your query. It would be a breach for me to mention their names or affiliations publicly or privately. - 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 May 4 18:05:09 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA02326 for ; Tue, 4 May 2004 18:05:09 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7xM-0004VO-6m; Tue, 04 May 2004 18:00:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL7sW-0003JR-LE for isis-wg@optimus.ietf.org; Tue, 04 May 2004 17:55:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01647 for ; Tue, 4 May 2004 17:55:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL7sU-0005od-09 for isis-wg@ietf.org; Tue, 04 May 2004 17:55:02 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL7ra-0005i0-00 for isis-wg@ietf.org; Tue, 04 May 2004 17:54:07 -0400 Received: from mailgate.pit.comms.marconi.com ([169.144.68.6]) by ietf-mx with esmtp (Exim 4.12) id 1BL7qv-0005ZX-00 for isis-wg@ietf.org; Tue, 04 May 2004 17:53:25 -0400 Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id i44LmnQG015276; Tue, 4 May 2004 17:48:49 -0400 (EDT) Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA15441; Tue, 4 May 2004 17:48:49 -0400 (EDT) Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19) id ; Tue, 4 May 2004 17:48:48 -0400 Message-ID: <313680C9A886D511A06000204840E1CF06DACD8A@whq-msgusr-02.pit.comms.marconi.com> From: "Krishnan, Vijay G." To: "'Jeff Parker'" , "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] Mib Updates MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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, 4 May 2004 17:48:48 -0400 Hi Jeff, Some implementations support a configurable SPF interval. Is there a reason why this is not included in the MIB? thanks Vijay -----Original Message----- From: Jeff Parker [mailto:jparker@axiowave.com] Sent: Tuesday, May 04, 2004 4:52 PM To: ISIS-WG (E-mail) Subject: [Isis-wg] Mib Updates I have sent version 14 of the ISIS MIB to the draft editors. The change list from the document is included below. At this point, I think we have the major functionality in place. The Notifications have been through a rev or two, and are starting to settle down. I hope that we can wrap things up and put it up for MIB doctor review. If you have functionality that you do not think is represented, this would be a good time to speak up. - jeff parker -- Changes in version 14 -- -- Set DEFVAL for isisCirc3WayEnabled to true -- Revised description for isisPacketCountIIHello -- Removed isisSysStatMaxAreaAddrMismatches as -- duplicating isisCircMaxAreaAddrMismatches -- Replaced isisManAreaAddrExistState with isisManAreaAddr -- in isisManualAddressDrops -- Drop isisSysLevelIndex in isisDatabaseOverload -- Drop restriction from isisCircIndex - SYNTAX Integer32 (1..2000000000) -- Change syntax of FullMetric to SYNTAX Unsigned32 -- Corrections to description of isisSysMaxLSPGenInt, isisSysMaxAge -- Change access levels of isisSysInstance and isisSysLevelIndex -- Fix references for isisCircPassiveCircuit, isisCircLevelCSNPInterval -- Fix description of isisISAdjIndex -- Replace level 1 with L2, level 2 with L2 -- Fix description of isisISAdjAreaAddrIndex -- Fix description of isisCircExtendedCircID -- Clarify description of isisCircLevelID -- Added isisSysStatLSPErrors to count LSPs with parse errors, -- and new Notification isisLSPErrorDetected -- Clarify domain of isisCircInitFails and isisCircRejAdjs -- Modified isisIPRATable for ECMP -- Removed RemoteRouterID from OwnLSPPurge _______________________________________________ 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 May 4 18:29:42 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04343 for ; Tue, 4 May 2004 18:29:42 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL8KY-0000Z2-12; Tue, 04 May 2004 18:24:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL8Hd-0007tI-4s for isis-wg@optimus.ietf.org; Tue, 04 May 2004 18:21:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA03953 for ; Tue, 4 May 2004 18:20:56 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL8Ha-00016r-8x for isis-wg@ietf.org; Tue, 04 May 2004 18:20:58 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL8Gh-00010J-00 for isis-wg@ietf.org; Tue, 04 May 2004 18:20:03 -0400 Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx with esmtp (Exim 4.12) id 1BL8G3-0000mB-00 for isis-wg@ietf.org; Tue, 04 May 2004 18:19:23 -0400 Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-2.cisco.com with ESMTP; 04 May 2004 14:31:48 +0000 Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id i44MIcW9009241; Tue, 4 May 2004 15:18:38 -0700 (PDT) Received: from ginsberg-w2k.cisco.com (dhcp-128-107-163-211.cisco.com [128.107.163.211]) by mira-sjc5-a.cisco.com (MOS 3.4.5-GR) with ESMTP id AQH28914; Tue, 4 May 2004 15:17:47 -0700 (PDT) Message-Id: <4.3.2.7.2.20040504151725.02636ac8@mira-sjc5-3.cisco.com> X-Sender: ginsberg@mira-sjc5-3.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: "Krishnan, Vijay G." From: Les Ginsberg Subject: RE: [Isis-wg] ISIS graceful restart... Cc: "'Christian Hopps'" , mike shand , Jeelani Syed , David Ward , "" In-Reply-To: <313680C9A886D511A06000204840E1CF06DACD88@whq-msgusr-02.pit .comms.marconi.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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, 04 May 2004 15:18:36 -0700 At 04:13 PM 5/4/2004 -0400, Krishnan, Vijay G. wrote: >Also, there are some incorrect cross references to sections 4.2.1 and 4.4 on >page 10/11. These should be 3.2.1 and 3.4 respectively. > Vijay - Thanx for catching these. Sigh... Les _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue May 4 18:37:36 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04748 for ; Tue, 4 May 2004 18:37:36 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL8UD-0002UQ-3U; Tue, 04 May 2004 18:34:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL8QN-0001sk-8l for isis-wg@optimus.ietf.org; Tue, 04 May 2004 18:30:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA04367 for ; Tue, 4 May 2004 18:29:58 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL8QK-000283-9q for isis-wg@ietf.org; Tue, 04 May 2004 18:30:00 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL8PN-00020s-00 for isis-wg@ietf.org; Tue, 04 May 2004 18:29:02 -0400 Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx with esmtp (Exim 4.12) id 1BL8Ox-0001tD-00 for isis-wg@ietf.org; Tue, 04 May 2004 18:28:35 -0400 Message-ID: From: Jeff Parker To: "'Krishnan, Vijay G.'" , "ISIS-WG (E-mail)" Subject: RE: [Isis-wg] Mib Updates MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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, 4 May 2004 18:27:53 -0400 > > If you have functionality that you do not think > > is represented... speak up. > Some implementations support a configurable SPF > interval.... > > Vijay Vijay - Indeed, and some have several configurable SPF intervals. I could have sworn that we did as well. Would a per level interval with text like "Minimal time between consecutive SPF runs at this level." do the trick for you? - 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 May 4 19:16:01 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06798 for ; Tue, 4 May 2004 19:16:01 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL95u-0003dZ-RT; Tue, 04 May 2004 19:12:58 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BL8wK-0000xT-KI for isis-wg@optimus.ietf.org; Tue, 04 May 2004 19:03:04 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06100 for ; Tue, 4 May 2004 19:02:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BL8wH-00066M-6b for isis-wg@ietf.org; Tue, 04 May 2004 19:03:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BL8vX-00060J-00 for isis-wg@ietf.org; Tue, 04 May 2004 19:02:16 -0400 Received: from nn1.excitenetwork.com ([207.159.120.55] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BL8uv-0005qk-00 for isis-wg@ietf.org; Tue, 04 May 2004 19:01:37 -0400 Received: by xprdmailfe20.nwk.excite.com (Postfix, from userid 110) id 9C7E4B6E1; Tue, 4 May 2004 19:01:03 -0400 (EDT) To: jparker@axiowave.com, Vijay.G.Krishnan@marconi.com, isis-wg@ietf.org Subject: RE: [Isis-wg] Mib Updates Received: from [64.47.48.10] by xprdmailfe20.nwk.excite.com via HTTP; Tue, 04 May 2004 19:01:03 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = ce00c10647f1b9e7db16a67db0936ee4 Reply-To: dgoodspe@excite.com From: "Don Goodspeed" MIME-Version: 1.0 X-Sender: dgoodspe@excite.com X-Mailer: PHP Content-Type: multipart/alternative; boundary="EXCITEBOUNDARY_000__4b33b8529222535e8ad4dc4bdf0eba9f"; Content-Transfer-Encoding: 7bit Message-Id: <20040504230103.9C7E4B6E1@xprdmailfe20.nwk.excite.com> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL,HTML_MESSAGE autolearn=no version=2.60 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, 4 May 2004 19:01:03 -0400 (EDT) --EXCITEBOUNDARY_000__4b33b8529222535e8ad4dc4bdf0eba9f Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Jeff, Vijay, And if an implementation does not support per-level SPF intervals, which one should be set? My other comment is that some vendors support an inter-SPF interval as well as an initial SPF holddown. And let's not forget others who implement the inter-SFP interval with an exponential backoff. In other words, I don't know how simple this will be to make everyone happy. This might be best left to the implementors in their proprietary MIBs. I think the ISIS MIB should be better left to those items that are defined in the ITU or the IETF documents and I do not recall seeing this defined in any of those documents. My 2 cents, Don --- On Tue 05/04, Jeff Parker wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: Vijay.G.Krishnan@marconi.com, isis-wg@ietf.org Date: Tue, 4 May 2004 18:27:53 -0400 Subject: RE: [Isis-wg] Mib Updates > > If you have functionality that you do not think> > is represented... speak up. > Some implementations support a configurable SPF > interval....>> VijayVijay - Indeed, and some have several configurableSPF intervals. I could have sworn that we did as well. Would a per level interval with text like "Minimal time between consecutive SPF runs at this level."do the trick for you? - jeff parker_______________________________________________Isis-wg mailing listIsis-wg@ietf.orghttps://www1.ietf.org/mailman/listinfo/isis-wg _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! --EXCITEBOUNDARY_000__4b33b8529222535e8ad4dc4bdf0eba9f Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 7bit Jeff, Vijay, And if an implementation does not support per-level SPF intervals, which one should be set? My other comment is that some vendors support an inter-SPF interval as well as an initial SPF holddown. And let's not forget others who implement the inter-SFP interval with an exponential backoff. In other words, I don't know how simple this will be to make everyone happy. This might be best left to the implementors in their proprietary MIBs. I think the ISIS MIB should be better left to those items that are defined in the ITU or the IETF documents and I do not recall seeing this defined in any of those documents. My 2 cents, Don --- On Tue 05/04, Jeff Parker < jparker@axiowave.com > wrote: From: Jeff Parker [mailto: jparker@axiowave.com] To: Vijay.G.Krishnan@marconi.com, isis-wg@ietf.org Date: Tue, 4 May 2004 18:27:53 -0400 Subject: RE: [Isis-wg] Mib Updates
> > If you have functionality that you do not think
> > is represented... speak up.

> Some implementations support a configurable SPF
> interval....
>
> Vijay

Vijay -
Indeed, and some have several configurable
SPF intervals.
I could have sworn that we did as well.
Would a per level interval with text like

"Minimal time between consecutive SPF runs
at this level."

do the trick for you?

- 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! --EXCITEBOUNDARY_000__4b33b8529222535e8ad4dc4bdf0eba9f-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue May 4 21:07:18 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12192 for ; Tue, 4 May 2004 21:07:18 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLApM-0005pY-Sr; Tue, 04 May 2004 21:04:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLAmU-0005C7-3r for isis-wg@optimus.ietf.org; Tue, 04 May 2004 21:01:02 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA11903 for ; Tue, 4 May 2004 21:00:59 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLAmR-0005ir-Ii for isis-wg@ietf.org; Tue, 04 May 2004 21:00:59 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLAld-0005bq-00 for isis-wg@ietf.org; Tue, 04 May 2004 21:00:10 -0400 Received: from nn4.excitenetwork.com ([207.159.120.58] helo=excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BLAkx-0005Kc-00 for isis-wg@ietf.org; Tue, 04 May 2004 20:59:27 -0400 Received: by xprdmailfe15.nwk.excite.com (Postfix, from userid 110) id 9FA9AB704; Tue, 4 May 2004 20:58:48 -0400 (EDT) To: jparker@axiowave.com, Vijay.G.Krishnan@marconi.com, isis-wg@ietf.org Subject: RE: [Isis-wg] Mib Updates Received: from [64.47.48.10] by xprdmailfe15.nwk.excite.com via HTTP; Tue, 04 May 2004 20:58:48 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = ce00c10647f1b9e7db16a67db0936ee4 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: <20040505005848.9FA9AB704@xprdmailfe15.nwk.excite.com> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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, 4 May 2004 20:58:48 -0400 (EDT) Content-Transfer-Encoding: 7bit OK, that should be.... ----------------------- Jeff, Vijay, And if an implementation does not support per-level SPF intervals, which one should be set? My other comment is that some vendors support an inter-SPF interval as well as an initial SPF holddown. And let's not forget others who implement the inter-SFP interval with an exponential backoff. In other words, I don't know how simple this will be to make everyone happy. This might be best left to the implementors in their proprietary MIBs. I think the ISIS MIB should be better left to those items that are defined in the ITU or the IETF documents and I do not recall seeing this defined in any of those documents. My 2 cents, Don --- On Tue 05/04, Jeff Parker < jparker@axiowave.com > wrote:From: Jeff Parker [mailto: jparker@axiowave.com]To: Vijay.G.Krishnan@marconi.com, isis-wg@ietf.orgDate: Tue, 4 May 2004 18:27:53 -0400Subject: RE: [Isis-wg] Mib Updates > > If you have functionality that you do not think > > is represented... speak up. > Some implementations support a configurable SPF > interval.... > > Vijay Vijay - Indeed, and some have several configurable SPF intervals. I could have sworn that we did as well. Would a per level interval with text like "Minimal time between consecutive SPF runs at this level." do the trick for you? - jeff parker _______________________________________________ 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 May 4 23:20:38 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17860 for ; Tue, 4 May 2004 23:20:38 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLCrC-0004CO-Bk; Tue, 04 May 2004 23:14:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLCl4-00022f-HB for isis-wg@optimus.ietf.org; Tue, 04 May 2004 23:07:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17257 for ; Tue, 4 May 2004 23:07:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLCl0-00000Z-C4 for isis-wg@ietf.org; Tue, 04 May 2004 23:07:38 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLCk4-0007g4-00 for isis-wg@ietf.org; Tue, 04 May 2004 23:06:41 -0400 Received: from smtp2.procket.com ([65.174.124.37]) by ietf-mx with esmtp (Exim 4.12) id 1BLCjO-0007XR-00 for isis-wg@ietf.org; Tue, 04 May 2004 23:05:58 -0400 Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60]) by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i455DDAw068478 for ; Tue, 4 May 2004 22:13:13 -0700 (PDT) Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4535Nd1027393 for ; Tue, 4 May 2004 20:05:23 -0700 (PDT) Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 4 May 2004 20:05:23 -0700 Mime-Version: 1.0 (Apple Message framework v613) Content-Transfer-Encoding: 7bit Message-Id: <0C5C2C4A-9E41-11D8-B3C2-00039303E9E2@procket.com> Content-Type: text/plain; charset=US-ASCII; format=flowed To: isis-wg@ietf.org From: Christian Hopps X-Mailer: Apple Mail (2.613) X-OriginalArrivalTime: 05 May 2004 03:05:23.0543 (UTC) FILETIME=[CEBAB670:01C4324D] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Subject: [Isis-wg] IS-IS MIB and multiple protocol instances. 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, 4 May 2004 20:05:22 -0700 Content-Transfer-Encoding: 7bit The current IS-IS MIB supports multiple protocol instances on a router by adding an index to every table in the MIB. This seems messy to me. The OSPF MIB deals with multiple instances by using a feature of SNMPv3 (contexts). This seems like a very nice solution to me. I think its very important to also consider how many people actually use multiple IS-IS protocol instances on a single router when we make our decision. I'd prefer to not complicate the MIB as it currently is if we don't have to. Given that many more people use multiple OSPF instances I suspect this will put pressure on the context solution being deployed and thus quite usable for us. In any case I don't want to spend a large amount of time on this issue. It is my hope that we can get the MIB to last call by or before the next IETF meeting. Chris. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed May 5 07:48:38 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08719 for ; Wed, 5 May 2004 07:48:37 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLKok-0001Cd-G2; Wed, 05 May 2004 07:44:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLKlM-0000EJ-Rt for isis-wg@optimus.ietf.org; Wed, 05 May 2004 07:40:32 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08313 for ; Wed, 5 May 2004 07:40:31 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLKlM-00004S-1c for isis-wg@ietf.org; Wed, 05 May 2004 07:40:32 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLKkW-0007f1-00 for isis-wg@ietf.org; Wed, 05 May 2004 07:39:41 -0400 Received: from mailgate.pit.comms.marconi.com ([169.144.68.6]) by ietf-mx with esmtp (Exim 4.12) id 1BLKjk-0007EC-00 for isis-wg@ietf.org; Wed, 05 May 2004 07:38:52 -0400 Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id i45BcAQG024660; Wed, 5 May 2004 07:38:10 -0400 (EDT) Received: from uspitsmsgrtr01.pit.comms.marconi.com (uspitsmsgrtr01.pit.comms.marconi.com [169.144.2.221]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id HAA22248; Wed, 5 May 2004 07:38:10 -0400 (EDT) Received: by uspitsmsgrtr01.pit.comms.marconi.com with Internet Mail Service (5.5.2653.19) id ; Wed, 5 May 2004 07:38:09 -0400 Message-ID: <313680C9A886D511A06000204840E1CF06DACD8B@whq-msgusr-02.pit.comms.marconi.com> From: "Krishnan, Vijay G." To: "'Don Goodspeed '" , "'jparker@axiowave.com '" , "Krishnan, Vijay G." , "'isis-wg@ietf.org '" Subject: RE: [Isis-wg] Mib Updates MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 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, 5 May 2004 07:38:08 -0400 Don, Jeff, Since there is no standard way of implementing the timers, the implementations have done their own way. Maybe having the per-level timers in the MIB would help standardize this. I don't think we need an IETF document for SPF timers. The MIB would be the right place. But if others in the WG is not happy with this, I can live with my private MIB. regards Vijay -----Original Message----- From: Don Goodspeed To: jparker@axiowave.com; Vijay.G.Krishnan@marconi.com; isis-wg@ietf.org Sent: 5/4/04 8:58 PM Subject: RE: [Isis-wg] Mib Updates OK, that should be.... ----------------------- Jeff, Vijay, And if an implementation does not support per-level SPF intervals, which one should be set? My other comment is that some vendors support an inter-SPF interval as well as an initial SPF holddown. And let's not forget others who implement the inter-SFP interval with an exponential backoff. In other words, I don't know how simple this will be to make everyone happy. This might be best left to the implementors in their proprietary MIBs. I think the ISIS MIB should be better left to those items that are defined in the ITU or the IETF documents and I do not recall seeing this defined in any of those documents. My 2 cents, Don --- On Tue 05/04, Jeff Parker < jparker@axiowave.com > wrote:From: Jeff Parker [mailto: jparker@axiowave.com]To: Vijay.G.Krishnan@marconi.com, isis-wg@ietf.orgDate: Tue, 4 May 2004 18:27:53 -0400Subject: RE: [Isis-wg] Mib Updates > > If you have functionality that you do not think > > is represented... speak up. > Some implementations support a configurable SPF > interval.... > > Vijay Vijay - Indeed, and some have several configurable SPF intervals. I could have sworn that we did as well. Would a per level interval with text like "Minimal time between consecutive SPF runs at this level." do the trick for you? - jeff parker _______________________________________________ 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 _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed May 5 09:22:20 2004 Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12042 for ; Wed, 5 May 2004 09:22:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLMHh-0003fw-H3; Wed, 05 May 2004 09:18:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLMDT-0002ac-C8 for isis-wg@optimus.ietf.org; Wed, 05 May 2004 09:13:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11613 for ; Wed, 5 May 2004 09:13:36 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLMDR-0005KJ-Pe for isis-wg@ietf.org; Wed, 05 May 2004 09:13:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLMCP-00054q-00 for isis-wg@ietf.org; Wed, 05 May 2004 09:12:34 -0400 Received: from smtp1.procket.com ([65.174.124.36]) by ietf-mx with esmtp (Exim 4.12) id 1BLMBO-0004dX-00 for isis-wg@ietf.org; Wed, 05 May 2004 09:11:31 -0400 Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60]) by smtp1.procket.com (8.12.8p1/8.12.1) with ESMTP id i45FLqpL076599; Wed, 5 May 2004 08:21:53 -0700 (PDT) Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id i45DAbd1021501; Wed, 5 May 2004 06:10:37 -0700 (PDT) Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 5 May 2004 06:10:36 -0700 In-Reply-To: <313680C9A886D511A06000204840E1CF06DACD8B@whq-msgusr-02.pit.comms.marconi.com> References: <313680C9A886D511A06000204840E1CF06DACD8B@whq-msgusr-02.pit.comms.marconi.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <99045270-9E95-11D8-BF51-00039303E9E2@procket.com> Content-Transfer-Encoding: 7bit Cc: "Don Goodspeed " , , From: Christian Hopps Subject: Re: [Isis-wg] Mib Updates To: "Krishnan, Vijay G." X-Mailer: Apple Mail (2.613) X-OriginalArrivalTime: 05 May 2004 13:10:37.0024 (UTC) FILETIME=[5B402E00:01C432A2] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit 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, 5 May 2004 06:10:36 -0700 Content-Transfer-Encoding: 7bit The implementations have done it their own way because its an implementation issue. We should not be trying to standardize things by fiat using the MIB. If someone wants to do research on why the SPF interval options should be standardized that should happen elsewhere (and shouldn't be IS-IS specific). Chris. On May 5, 2004, at 4:38 AM, Krishnan, Vijay G. wrote: > Don, Jeff, > > Since there is no standard way of implementing the timers, the > implementations have done their own way. Maybe having the per-level > timers > in the MIB would help standardize this. I don't think we need an IETF > document for SPF timers. The MIB would be the right place. But if > others in > the WG is not happy with this, I can live with my private MIB. > > regards > Vijay _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed May 5 09:44:09 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13002 for ; Wed, 5 May 2004 09:44:09 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLMb5-0001D2-Cz; Wed, 05 May 2004 09:38:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLMYs-0000GB-NY for isis-wg@optimus.ietf.org; Wed, 05 May 2004 09:35:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12660 for ; Wed, 5 May 2004 09:35:43 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BLMYq-0002rg-SM for isis-wg@ietf.org; Wed, 05 May 2004 09:35:44 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BLMY6-0002dO-00 for isis-wg@ietf.org; Wed, 05 May 2004 09:34:58 -0400 Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx with esmtp (Exim 4.12) id 1BLMXR-0002Lc-00 for isis-wg@ietf.org; Wed, 05 May 2004 09:34:17 -0400 Message-ID: From: Jeff Parker To: "'Christian Hopps'" , "Krishnan, Vijay G." Cc: Don Goodspeed , isis-wg@ietf.org, Jeff Parker Subject: RE: [Isis-wg] Mib Updates MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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, 5 May 2004 09:33:21 -0400 Chris's post reminds me that we have been over this territory in the past. There are implementations that perform continuous incremental SPF, and thus do not need any timers. Other implementations have multiple timers, as discussed. The last time we hashed this out, we agreed to leave SPF values out. - jeff parker -----Original Message----- From: Christian Hopps [mailto:chopps@procket.com] Sent: Wednesday, May 05, 2004 9:11 AM To: Krishnan, Vijay G. Cc: Don Goodspeed ; isis-wg@ietf.org; jparker@axiowave.com Subject: Re: [Isis-wg] Mib Updates The implementations have done it their own way because its an implementation issue. We should not be trying to standardize things by fiat using the MIB. If someone wants to do research on why the SPF interval options should be standardized that should happen elsewhere (and shouldn't be IS-IS specific). Chris. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu May 6 12:30:45 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27032 for ; Thu, 6 May 2004 12:30:45 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLl2a-0004H0-4q; Thu, 06 May 2004 11:44:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BLko9-0004X5-OP for isis-wg@optimus.ietf.org; Thu, 06 May 2004 11:29:09 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA20176; Thu, 6 May 2004 11:29:07 -0400 (EDT) Message-Id: <200405061529.LAA20176@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-mib-14.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, 06 May 2004 11:29:06 -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-14.txt Pages : 94 Date : 2004-5-5 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-14.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-wg-mib-14.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-14.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-5-6113448.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-wg-mib-14.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-wg-mib-14.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-5-6113448.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 May 10 20:21:44 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18100 for ; Mon, 10 May 2004 20:21:44 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNKrQ-0000lH-L8; Mon, 10 May 2004 20:11:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNKjq-0007Gc-EL for isis-wg@optimus.ietf.org; Mon, 10 May 2004 20:03:14 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA17563 for ; Mon, 10 May 2004 20:03:12 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNKjo-0005o2-EQ for isis-wg@ietf.org; Mon, 10 May 2004 20:03:12 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNKit-0005UY-00 for isis-wg@ietf.org; Mon, 10 May 2004 20:02:16 -0400 Received: from nn8.excitenetwork.com ([207.159.120.62] helo=xprdmailfe3.nwk.excite.com) by ietf-mx with esmtp (Exim 4.12) id 1BNKi1-0004qf-00 for isis-wg@ietf.org; Mon, 10 May 2004 20:01:21 -0400 Received: by xprdmailfe3.nwk.excite.com (Postfix, from userid 110) id 80723197358; Mon, 10 May 2004 20:00:52 -0400 (EDT) To: isis-wg@ietf.org Subject: RE: [Isis-wg] IS-IS MIB and multiple protocol instances. Received: from [64.47.48.10] by xprdmailfe3.nwk.excite.com via HTTP; Mon, 10 May 2004 20:00:52 EST X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: ID = ce00c10647f1b9e7db16a67db0936ee4 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: jparker@axiowave.com, chopps@procket.com Message-Id: <20040511000052.80723197358@xprdmailfe3.nwk.excite.com> X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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, 10 May 2004 20:00:52 -0400 (EDT) Content-Transfer-Encoding: 7bit All, Being a user of SNMP contexts and also being a protocols tester, while having the index in the tables is nice, as Chris points out, it is not required. Not only does OSPF use contexts for multiple instances, but so do BGP, RIP, etc. In fact some vendors support many of the standard IP MIB tables in this manner as well. I haven't yet spoken with Jeff on this issue but if it helps to move the MIB forward by removing these extra indices, then I would tend to favor making this change. Take care, Don ============================================== The current IS-IS MIB supports multiple protocol instances on a router by adding an index to every table in the MIB. This seems messy to me. The OSPF MIB deals with multiple instances by using a feature of SNMPv3 (contexts). This seems like a very nice solution to me. I think its very important to also consider how many people actually use multiple IS-IS protocol instances on a single router when we make our decision. I'd prefer to not complicate the MIB as it currently is if we don't have to. Given that many more people use multiple OSPF instances I suspect this will put pressure on the context solution being deployed and thus quite usable for us. In any case I don't want to spend a large amount of time on this issue. It is my hope that we can get the MIB to last call by or before the next IETF meeting. Chris. _______________________________________________ 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 May 11 14:12:45 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13267 for ; Tue, 11 May 2004 14:12:45 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNbfe-00044n-Fo; Tue, 11 May 2004 14:08:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNbas-0002tI-Gd for isis-wg@optimus.ietf.org; Tue, 11 May 2004 14:03:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12809 for ; Tue, 11 May 2004 14:03:03 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNbaq-0003D7-5M for isis-wg@ietf.org; Tue, 11 May 2004 14:03:04 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNbZv-0002mX-00 for isis-wg@ietf.org; Tue, 11 May 2004 14:02:08 -0400 Received: from smtp2.procket.com ([65.174.124.37]) by ietf-mx with esmtp (Exim 4.12) id 1BNbYx-0001wH-00 for isis-wg@ietf.org; Tue, 11 May 2004 14:01:07 -0400 Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60]) by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i4BK8GAw042020; Tue, 11 May 2004 13:08:17 -0700 (PDT) Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4BI0Kd1007485; Tue, 11 May 2004 11:00:20 -0700 (PDT) Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 11 May 2004 11:00:20 -0700 In-Reply-To: <20040511000052.80723197358@xprdmailfe3.nwk.excite.com> References: <20040511000052.80723197358@xprdmailfe3.nwk.excite.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <15471C0C-A375-11D8-8ECF-00039303E9E2@procket.com> Content-Transfer-Encoding: 7bit Cc: , From: Christian Hopps Subject: Re: [Isis-wg] IS-IS MIB and multiple protocol instances. To: X-Mailer: Apple Mail (2.613) X-OriginalArrivalTime: 11 May 2004 18:00:20.0543 (UTC) FILETIME=[D31D2CF0:01C43781] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit 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, 11 May 2004 11:00:27 -0700 Content-Transfer-Encoding: 7bit On May 10, 2004, at 5:00 PM, Don Goodspeed wrote: > All, > > Being a user of SNMP contexts and also being a protocols tester, > while having the index in the tables is nice, as Chris points out, > it is not required. Not only does OSPF use contexts for multiple > instances, but so do BGP, RIP, etc. In fact some vendors support > many of the standard IP MIB tables in this manner as well. > > I haven't yet spoken with Jeff on this issue but if it helps to > move the MIB forward by removing these extra indices, then I would > tend to favor making this change. Jeff expressed to me in private mail that he is willing to remove the instance index from the MIB. I've also communicated with Dave and he's in agreement that we should remove the instance index. I'll let this sit until the end of the week to allow for dissenting opinions, but after that I will request Jeff remove the instance index and add some text on the use of contexts. Thanks, Chris. > Take care, > Don > > ============================================== > The current IS-IS MIB supports multiple protocol instances on a router > by adding an index to every table in the MIB. This seems messy to me. > The OSPF MIB deals with multiple instances by using a feature of SNMPv3 > (contexts). This seems like a very nice solution to me. > > I think its very important to also consider how many people actually > use multiple IS-IS protocol instances on a single router when we make > our decision. I'd prefer to not complicate the MIB as it currently is > if we don't have to. Given that many more people use multiple OSPF > instances I suspect this will put pressure on the context solution > being deployed and thus quite usable for us. > > In any case I don't want to spend a large amount of time on this issue. > It is my hope that we can get the MIB to last call by or before the > next IETF meeting. > > Chris. > > _______________________________________________ > 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 May 11 14:44:03 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15279 for ; Tue, 11 May 2004 14:44:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNc1u-0000h7-ID; Tue, 11 May 2004 14:31:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNbgl-0004NH-3F for isis-wg@optimus.ietf.org; Tue, 11 May 2004 14:09:11 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13166 for ; Tue, 11 May 2004 14:09:08 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNbgi-0005nF-LX for isis-wg@ietf.org; Tue, 11 May 2004 14:09:08 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNbfo-0005N0-00 for isis-wg@ietf.org; Tue, 11 May 2004 14:08:12 -0400 Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx with esmtp (Exim 4.12) id 1BNbf9-0004v8-00 for isis-wg@ietf.org; Tue, 11 May 2004 14:07:31 -0400 Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Subject: [Isis-wg] IS-IS MIB and multiple protocol instances. MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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, 11 May 2004 14:06:25 -0400 This is about the initial index, sysInstance, in every table of the IS-IS MIB. Chris Gunner included this in the version I inherited. The rational is to provide access on systems with multiple Virtual Routers. There are other ways to do this: the standard is to use SNMP proxies. As best I understand it, that requires a distinct identity, including a distinct IP address, for each virtual router. This has been seen as a burden by others, including folks working on the OSPF MIB. I will take a look in my archives and see if I can find any old threads on the subject. - 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 May 11 14:59:12 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16461 for ; Tue, 11 May 2004 14:59:12 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNcIN-00057d-M2; Tue, 11 May 2004 14:48:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNc9x-000271-MF for isis-wg@optimus.ietf.org; Tue, 11 May 2004 14:39:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15037 for ; Tue, 11 May 2004 14:39:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNc9v-0003EV-09 for isis-wg@ietf.org; Tue, 11 May 2004 14:39:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNc8i-0002n3-00 for isis-wg@ietf.org; Tue, 11 May 2004 14:38:05 -0400 Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx with esmtp (Exim 4.12) id 1BNc81-00024p-00 for isis-wg@ietf.org; Tue, 11 May 2004 14:37:21 -0400 Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Cc: "'jonathan.sadler@tellabs.com'" , "Daniel Joyal (E-mail)" Subject: FW: [Isis-wg] RE: OSPF MIB support for multiple OSPF processes MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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, 11 May 2004 14:36:43 -0400 Here is one note from my mail files: I remember more discussions, but haven't stumbled across it. It does seem to come up every year or so. Periodic, with jitter applied. This is really more to the point that a virtual router is an important concept than a statement of how best to do this. - jeff parker > -----Original Message----- > From: Jonathan Sadler [mailto:jonathan.sadler@tellabs.com] > Sent: Tuesday, January 28, 2003 5:06 AM > To: Jeff Parker > Subject: Re: [Isis-wg] RE: OSPF MIB support for multiple OSPF > processes > > > Jeff - > > I do have use for this in SONET/SDH environments -- > specifically this index > allows for support of multiple logical IS-IS instances on one physical > platform. This is needed for: > - more than one Area per physical platform > - separation of IS-IS routing for the DCN from separate IS-IS > routing for other layer networks (i.e. GMPLS) > > Jeff Parker wrote: > > > > > > Jeff, > > > > > > Given the comments below, where did you get the > > > requirement to explicitly support multiple IS-IS > > > instances in the IS-IS MIB? > > > > > > -Dan > > > > Dan - > > You are refering to the SysInstance index in > > the IS-IS MIB. Use of this was not a requirement: > > it came with the original version of the MIB I inherited. > > > > I would be interested to hear from any users > > that find this useful. While it seems to offer > > a solution, I don't know of any other MIB that supports > > this, so people will have to design an alternative > > anyway. > > > > It isn't too late to rip this out if it has > > no utility. > > > > - jeff parker > > > > > -----Original Message----- > > > From: Tom Petch [mailto:nwnetworks@DIAL.PIPEX.COM] > > > Sent: Monday, January 20, 2003 1:16 PM > > > To: OSPF@DISCUSS.MICROSOFT.COM > > > Subject: Re: OSPF MIB support for multiple OSPF processes > > > > > > > > > Yes. > > > In SNMPv1, this can be done by having multiple 'agents' > identified by > > > different community names or different IP addresses, each > accessing a > > > distinct incarnation of MIB II and its subordinate branches. > > > In SNMPv3, there is a more sophisticated mechanism of > contexts which > > > formalises the techniques given above. > > > I do not think you should ever return more than one instance of a > > > given object in GET or GETNEXT. > > > > > > Tom Petch > > > nwnetworks@dial.pipex.com > > > > > > -----Original Message----- > > > From: Roy Jose > > > To: OSPF@DISCUSS.MICROSOFT.COM > > > Date: 20 January 2003 16:04 > > > Subject: OSPF MIB support for multiple OSPF processes > > > > > > > > > >Hi, > > > > > > > >Rfc1850 doesn't talk about what to be done regarding the > > > retrieval(GET) of > > > >MIB values when multiple OSPF processes exist on a > router. Out first > > > >impression is to return details about all the processes. > The problem > > > is > > > >while selecting values for MIB objects like > > > >ospfRouterId,ospfAreaBdrRtrStatus, ospfASBdrRtrStatus > etc. They may > > > differ > > > >in separate processes. The Qn is, can we really support multiple > > > processes > > > >with rfc1850? > > > > > > > >Thanks, > > > >Roy > > > > > _______________________________________________ > > Isis-wg mailing list > > Isis-wg@ietf.org > > https://www1.ietf.org/mailman/listinfo/isis-wg > > ============================================================ > The information contained in this message may be privileged > and confidential and protected from disclosure. If the > reader of this message is not the intended recipient, or an > employee or agent responsible for delivering this message to > the intended recipient, you are hereby notified that any > reproduction, dissemination or distribution of this > communication is strictly prohibited. If you have received > this communication in error, please notify us immediately by > replying to the message and deleting it from your computer. > > Thank you. > Tellabs > ============================================================ > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue May 11 15:51:20 2004 Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20954 for ; Tue, 11 May 2004 15:51:20 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNd6t-0000iW-4Z; Tue, 11 May 2004 15:40:15 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNd01-00071M-8M for isis-wg@optimus.ietf.org; Tue, 11 May 2004 15:33:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19865 for ; Tue, 11 May 2004 15:33:06 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNczz-0003cq-DJ for isis-wg@ietf.org; Tue, 11 May 2004 15:33:07 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNcyz-0003BH-00 for isis-wg@ietf.org; Tue, 11 May 2004 15:32:05 -0400 Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com) by ietf-mx with esmtp (Exim 4.12) id 1BNcxz-0002Lg-00 for isis-wg@ietf.org; Tue, 11 May 2004 15:31:04 -0400 Received: from mail-blue.research.att.com (H-135-207-30-102.research.att.com [135.207.30.102]) by mail-white.research.att.com (Postfix) with ESMTP id 67F3466404B; Tue, 11 May 2004 15:30:34 -0400 (EDT) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by mail-blue.research.att.com (Postfix) with ESMTP id 58BCAF3AFC; Tue, 11 May 2004 15:30:34 -0400 (EDT) Received: (from fenner@localhost) by windsor.research.att.com (8.11.6+Sun/8.8.5) id i4BJUXo21567; Tue, 11 May 2004 15:30:33 -0400 (EDT) Message-Id: <200405111930.i4BJUXo21567@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jparker@axiowave.com Subject: Re: [Isis-wg] IS-IS MIB and multiple protocol instances. Cc: isis-wg@ietf.org From: Bill Fenner Versions: dmail (solaris) 2.6d/makemail 2.10 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 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, 11 May 2004 15:30:32 -0400 >There are other ways to do this: the standard is to use SNMP proxies. As >best I understand it, that requires a distinct identity, including a >distinct IP address, for each virtual router. This has been seen as a >burden by others, including folks working on the OSPF MIB. My understanding is that the usual way to do this is to use the Entity MIB, RFC 2737, which can give you a mapping of logical entity to either an SNMPv1 community or SNMPv3 EngineID + Context. This does not require distinct IP addresses. Bill _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed May 12 11:45:53 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA19147 for ; Wed, 12 May 2004 11:45:53 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNvP3-0003Xz-Bv; Wed, 12 May 2004 11:12:13 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNuTN-0003Ya-CB for isis-wg@optimus.ietf.org; Wed, 12 May 2004 10:12:37 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06827; Wed, 12 May 2004 10:12:34 -0400 (EDT) Message-Id: <200405121412.KAA06827@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-experimental-tlv-03.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: Wed, 12 May 2004 10:12:34 -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 : TLV for Experimental Use Author(s) : P. Christian Filename : draft-ietf-isis-experimental-tlv-03.txt Pages : 6 Date : 2004-5-6 This document defines a TLV that may be used by any individual, company or other organisation for experimental extensions to the IS-IS routing protocol, and defines the format of the TLV. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-experimental-tlv-03.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-experimental-tlv-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-isis-experimental-tlv-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-5-12103604.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-experimental-tlv-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-experimental-tlv-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-5-12103604.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 Thu May 13 09:12:26 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10312 for ; Thu, 13 May 2004 09:12:26 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOFtX-00056R-QR; Thu, 13 May 2004 09:05:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BNebs-0007GU-Jm for isis-wg@optimus.ietf.org; Tue, 11 May 2004 17:16:20 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA26354 for ; Tue, 11 May 2004 17:16:16 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BNebq-0001xF-9x for isis-wg@ietf.org; Tue, 11 May 2004 17:16:18 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BNeaw-0001Ws-00 for isis-wg@ietf.org; Tue, 11 May 2004 17:15:24 -0400 Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx with esmtp (Exim 4.12) id 1BNeaE-0000wJ-00 for isis-wg@ietf.org; Tue, 11 May 2004 17:14:38 -0400 Received: from zbl6c012.us.nortel.com (zbl6c012.corpeast.baynetworks.com [132.245.205.62]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id i4BLDpH19176; Tue, 11 May 2004 17:13:52 -0400 (EDT) Received: by zbl6c012.corpeast.baynetworks.com with Internet Mail Service (5.5.2653.19) id ; Tue, 11 May 2004 17:13:51 -0400 Message-ID: <6204FDDE129D364D8040A98BCCB290EF0951CE56@zbl6c004.corpeast.baynetworks.com> From: "Daniel Joyal" To: "'Jeff Parker'" , "ISIS-WG (E-mail)" Cc: "'jonathan.sadler@tellabs.com'" Subject: RE: [Isis-wg] RE: OSPF MIB support for multiple OSPF processes MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4379C.DB404668" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,HTML_30_40,HTML_MESSAGE autolearn=no version=2.60 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, 11 May 2004 17:13:50 -0400 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4379C.DB404668 Content-Type: text/plain I don't have a problem with the ISIS MIB supporting multiple instances. Has the OAM directorate issued any policy statements as to the preferred way to support MIBs in virtual routers? -Dan > -----Original Message----- > From: Jeff Parker [mailto:jparker@axiowave.com] > Sent: Tuesday, May 11, 2004 2:37 PM > To: ISIS-WG (E-mail) > Cc: 'jonathan.sadler@tellabs.com'; Joyal, Daniel [BL60:NP31:EXCH] > Subject: FW: [Isis-wg] RE: OSPF MIB support for multiple OSPF > processes > > > Here is one note from my mail files: I remember more > discussions, but haven't stumbled across it. It does seem to > come up every year or so. Periodic, with jitter applied. > > This is really more to the point that a virtual router is an > important concept than a statement of how best to do this. > > - jeff parker > > > > -----Original Message----- > > From: Jonathan Sadler [mailto:jonathan.sadler@tellabs.com] > > Sent: Tuesday, January 28, 2003 5:06 AM > > To: Jeff Parker > > Subject: Re: [Isis-wg] RE: OSPF MIB support for multiple OSPF > > processes > > > > > > Jeff - > > > > I do have use for this in SONET/SDH environments -- > > specifically this index > > allows for support of multiple logical IS-IS instances on > one physical > > platform. This is needed for: > > - more than one Area per physical platform > > - separation of IS-IS routing for the DCN from separate IS-IS > > routing for other layer networks (i.e. GMPLS) > > > > Jeff Parker wrote: > > > > > > > > > Jeff, > > > > > > > > Given the comments below, where did you get the requirement to > > > > explicitly support multiple IS-IS instances in the IS-IS MIB? > > > > > > > > -Dan > > > > > > Dan - > > > You are refering to the SysInstance index in > > > the IS-IS MIB. Use of this was not a requirement: > > > it came with the original version of the MIB I inherited. > > > > > > I would be interested to hear from any users > > > that find this useful. While it seems to offer > > > a solution, I don't know of any other MIB that supports this, so > > > people will have to design an alternative anyway. > > > > > > It isn't too late to rip this out if it has > > > no utility. > > > > > > - jeff parker > > > > > > > -----Original Message----- > > > > From: Tom Petch [mailto:nwnetworks@DIAL.PIPEX.COM] > > > > Sent: Monday, January 20, 2003 1:16 PM > > > > To: OSPF@DISCUSS.MICROSOFT.COM > > > > Subject: Re: OSPF MIB support for multiple OSPF processes > > > > > > > > > > > > Yes. > > > > In SNMPv1, this can be done by having multiple 'agents' > > identified by > > > > different community names or different IP addresses, each > > accessing a > > > > distinct incarnation of MIB II and its subordinate branches. In > > > > SNMPv3, there is a more sophisticated mechanism of > > contexts which > > > > formalises the techniques given above. > > > > I do not think you should ever return more than one > instance of a > > > > given object in GET or GETNEXT. > > > > > > > > Tom Petch > > > > nwnetworks@dial.pipex.com > > > > > > > > -----Original Message----- > > > > From: Roy Jose > > > > To: OSPF@DISCUSS.MICROSOFT.COM > > > > Date: 20 January 2003 16:04 > > > > Subject: OSPF MIB support for multiple OSPF processes > > > > > > > > > > > > >Hi, > > > > > > > > > >Rfc1850 doesn't talk about what to be done regarding the > > > > retrieval(GET) of > > > > >MIB values when multiple OSPF processes exist on a > > router. Out first > > > > >impression is to return details about all the processes. > > The problem > > > > is > > > > >while selecting values for MIB objects like > > > > >ospfRouterId,ospfAreaBdrRtrStatus, ospfASBdrRtrStatus > > etc. They may > > > > differ > > > > >in separate processes. The Qn is, can we really > support multiple > > > > processes > > > > >with rfc1850? > > > > > > > > > >Thanks, > > > > >Roy > > > > > > > _______________________________________________ > > > Isis-wg mailing list > > > Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg > > > > ============================================================ > > The information contained in this message may be privileged > > and confidential and protected from disclosure. If the > > reader of this message is not the intended recipient, or an > > employee or agent responsible for delivering this message to > > the intended recipient, you are hereby notified that any > > reproduction, dissemination or distribution of this > > communication is strictly prohibited. If you have received > > this communication in error, please notify us immediately by > > replying to the message and deleting it from your computer. > > > > Thank you. > > Tellabs ============================================================ > > > ------_=_NextPart_001_01C4379C.DB404668 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [Isis-wg] RE: OSPF MIB support for multiple OSPF = processes

I don't have a problem with the ISIS MIB = supporting
multiple instances. Has the OAM directorate = issued
any policy statements as to the preferred way to = support
MIBs in virtual routers?

-Dan

> -----Original Message-----
> From: Jeff Parker [mailto:jparker@axiowave.com] =
> Sent: Tuesday, May 11, 2004 2:37 PM
> To: ISIS-WG (E-mail)
> Cc: 'jonathan.sadler@tellabs.com'; Joyal, = Daniel [BL60:NP31:EXCH]
> Subject: FW: [Isis-wg] RE: OSPF MIB support for = multiple OSPF
> processes
>
>
> Here is one note from my mail files: I remember = more
> discussions, but haven't stumbled across = it.  It does seem to
> come up every year or so. Periodic, with jitter = applied. 
>
> This is really more to the point that a virtual = router is an
> important concept than a statement of how best = to do this. 
>
> - jeff parker
>
>
> > -----Original Message-----
> > From: Jonathan Sadler [mailto:jonathan.sadler@tella= bs.com]
> > Sent: Tuesday, January 28, 2003 5:06 = AM
> > To: Jeff Parker
> > Subject: Re: [Isis-wg] RE: OSPF MIB = support for multiple OSPF
> > processes
> >
> >
> > Jeff -
> >
> > I do have use for this in SONET/SDH = environments --
> > specifically this index
> > allows for support of multiple logical = IS-IS instances on
> one physical
> > platform.  This is needed for:
> >  - more than one Area per physical = platform
> >  - separation of IS-IS routing for = the DCN from separate IS-IS
> >    routing for other layer = networks (i.e. GMPLS)
> >
> > Jeff Parker wrote:
> >
> > >
> > > > Jeff,
> > > >
> > > >  Given the comments below, = where did you get the requirement to
> > > > explicitly support multiple = IS-IS instances in the IS-IS MIB?
> > > >
> > > > -Dan
> > >
> > > Dan -
> > = >         You are refering = to the SysInstance index in
> > > the IS-IS MIB.  Use of this was = not a requirement:
> > > it came with the original version of = the MIB I inherited.
> > >
> > = >         I would be = interested to hear from any users
> > > that find this useful.  While it = seems to offer
> > > a solution, I don't know of any other = MIB that supports this, so
> > > people will have to design an = alternative anyway.
> > >
> > = >         It isn't too late = to rip this out if it has
> > > no utility.
> > >
> > > - jeff parker
> > >
> > > > -----Original = Message-----
> > > > From: Tom Petch [mailto:nwnetworks@DIAL.PIPEX.C= OM]
> > > > Sent: Monday, January 20, 2003 = 1:16 PM
> > > > To: = OSPF@DISCUSS.MICROSOFT.COM
> > > > Subject: Re: OSPF MIB support = for multiple OSPF processes
> > > >
> > > >
> > > > Yes.
> > > > In SNMPv1, this can be done by = having multiple 'agents'
> > identified by
> > > > different community names or = different IP addresses, each
> > accessing a
> > > > distinct incarnation of MIB II = and its subordinate branches. In
> > > > SNMPv3, there is a more = sophisticated mechanism of
> > contexts which
> > > > formalises the techniques given = above.
> > > > I do not think you should ever = return more than one
> instance of a
> > > > given object in GET or = GETNEXT.
> > > >
> > > > Tom Petch
> > > > nwnetworks@dial.pipex.com
> > > >
> > > > -----Original = Message-----
> > > > From: Roy Jose = <rojose@CISCO.COM>
> > > > To: OSPF@DISCUSS.MICROSOFT.COM = <OSPF@DISCUSS.MICROSOFT.COM>
> > > > Date: 20 January 2003 = 16:04
> > > > Subject: OSPF MIB support for = multiple OSPF processes
> > > >
> > > >
> > > > >Hi,
> > > > >
> > > > >Rfc1850 doesn't talk about = what to be done regarding the
> > > > retrieval(GET) of
> > > > >MIB values when multiple = OSPF processes exist on a
> > router. Out first
> > > > >impression is to return = details about all the processes.
> > The problem
> > > > is
> > > > >while selecting values for = MIB objects like
> > > > >ospfRouterId,ospfAreaBdrRtrSt= atus, ospfASBdrRtrStatus
> > etc. They may
> > > > differ
> > > > >in separate processes. The = Qn is, can we really
> support multiple
> > > > processes
> > > > >with rfc1850?
> > > > >
> > > > >Thanks,
> > > > >Roy
> > > >
> > > = _______________________________________________
> > > Isis-wg mailing list
> > > Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg
> >
> > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > The information contained in this message = may be privileged
> > and confidential and protected from = disclosure.  If the
> > reader of this message is not the intended = recipient, or an
> > employee or agent responsible for = delivering this message to
> > the intended recipient, you are hereby = notified that any
> > reproduction, dissemination or = distribution of this
> > communication is strictly prohibited. If = you have received
> > this communication in error, please notify = us immediately by
> > replying to the message and deleting it = from your computer.
> >
> > Thank you.
> > Tellabs = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >
>

------_=_NextPart_001_01C4379C.DB404668-- _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Thu May 13 09:40:03 2004 Received: from optimus.ietf.org (iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA12328 for ; Thu, 13 May 2004 09:40:03 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOGOV-0002es-NK; Thu, 13 May 2004 09:37:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BOGJf-0001Rp-8a for isis-wg@optimus.ietf.org; Thu, 13 May 2004 09:32:03 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11709 for ; Thu, 13 May 2004 09:32:00 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BOGJd-0002it-FN for isis-wg@ietf.org; Thu, 13 May 2004 09:32:01 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BOGHp-0001wl-00 for isis-wg@ietf.org; Thu, 13 May 2004 09:30:11 -0400 Received: from smtp1.procket.com ([65.174.124.36]) by ietf-mx with esmtp (Exim 4.12) id 1BOGG7-0000rn-00 for isis-wg@ietf.org; Thu, 13 May 2004 09:28:23 -0400 Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60]) by smtp1.procket.com (8.12.8p1/8.12.1) with ESMTP id i4DFd2pL075109; Thu, 13 May 2004 08:39:02 -0700 (PDT) Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4DDRZd1000437; Thu, 13 May 2004 06:27:35 -0700 (PDT) Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 13 May 2004 06:27:34 -0700 In-Reply-To: <6204FDDE129D364D8040A98BCCB290EF0951CE56@zbl6c004.corpeast.baynetworks.com> References: <6204FDDE129D364D8040A98BCCB290EF0951CE56@zbl6c004.corpeast.baynetworks.com> Mime-Version: 1.0 (Apple Message framework v613) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <4B0AB6F8-A4E1-11D8-8ECF-00039303E9E2@procket.com> Content-Transfer-Encoding: 7bit Cc: "Jeff Parker" , "ISIS-WG (E-mail)" , From: Christian Hopps Subject: Re: [Isis-wg] RE: OSPF MIB support for multiple OSPF processes To: "Daniel Joyal" X-Mailer: Apple Mail (2.613) X-OriginalArrivalTime: 13 May 2004 13:27:35.0205 (UTC) FILETIME=[0D704550:01C438EE] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit 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, 13 May 2004 06:27:34 -0700 Content-Transfer-Encoding: 7bit I'm interested in why we *should* support multiple instances (not virtual routers) directly in the MIB with an index in every table. Currently I see no good reason for this complexity. IS-IS doesn't use multiple instances anywhere near as much as OSPF in the field, and the OSPF MIB uses the context mechanism. I think we need a real good reason to differ from OSPF (and frankly a more simple MIB), otherwise we shouldn't. The only thing I've heard so far is OSPF has maybe hit bumps in the road in using contexts. I don't think thats a good enough reason, given the level of usage of multiple IS-IS instances, and the fact that OSPF will smooth the way for us here. Chris. On May 11, 2004, at 2:13 PM, Daniel Joyal wrote: > I don't have a problem with the ISIS MIB supporting > multiple instances. Has the OAM directorate issued > any policy statements as to the preferred way to support > MIBs in virtual routers? > > -Dan > >> -----Original Message----- >> From: Jeff Parker [mailto:jparker@axiowave.com] >> Sent: Tuesday, May 11, 2004 2:37 PM >> To: ISIS-WG (E-mail) >> Cc: 'jonathan.sadler@tellabs.com'; Joyal, Daniel [BL60:NP31:EXCH] >> Subject: FW: [Isis-wg] RE: OSPF MIB support for multiple OSPF >> processes >> >> >> Here is one note from my mail files: I remember more >> discussions, but haven't stumbled across it. It does seem to >> come up every year or so. Periodic, with jitter applied. >> >> This is really more to the point that a virtual router is an >> important concept than a statement of how best to do this. >> >> - jeff parker >> >> >>> -----Original Message----- >>> From: Jonathan Sadler [mailto:jonathan.sadler@tellabs.com] >>> Sent: Tuesday, January 28, 2003 5:06 AM >>> To: Jeff Parker >>> Subject: Re: [Isis-wg] RE: OSPF MIB support for multiple OSPF >>> processes >>> >>> >>> Jeff - >>> >>> I do have use for this in SONET/SDH environments -- >>> specifically this index >>> allows for support of multiple logical IS-IS instances on >> one physical >>> platform. This is needed for: >>> - more than one Area per physical platform >>> - separation of IS-IS routing for the DCN from separate IS-IS >>> routing for other layer networks (i.e. GMPLS) >>> >>> Jeff Parker wrote: >>> >>>> >>>>> Jeff, >>>>> >>>>> Given the comments below, where did you get the requirement to >>>>> explicitly support multiple IS-IS instances in the IS-IS MIB? >>>>> >>>>> -Dan >>>> >>>> Dan - >>>> You are refering to the SysInstance index in >>>> the IS-IS MIB. Use of this was not a requirement: >>>> it came with the original version of the MIB I inherited. >>>> >>>> I would be interested to hear from any users >>>> that find this useful. While it seems to offer >>>> a solution, I don't know of any other MIB that supports this, so >>>> people will have to design an alternative anyway. >>>> >>>> It isn't too late to rip this out if it has >>>> no utility. >>>> >>>> - jeff parker >>>> >>>>> -----Original Message----- >>>>> From: Tom Petch [mailto:nwnetworks@DIAL.PIPEX.COM] >>>>> Sent: Monday, January 20, 2003 1:16 PM >>>>> To: OSPF@DISCUSS.MICROSOFT.COM >>>>> Subject: Re: OSPF MIB support for multiple OSPF processes >>>>> >>>>> >>>>> Yes. >>>>> In SNMPv1, this can be done by having multiple 'agents' >>> identified by >>>>> different community names or different IP addresses, each >>> accessing a >>>>> distinct incarnation of MIB II and its subordinate branches. In >>>>> SNMPv3, there is a more sophisticated mechanism of >>> contexts which >>>>> formalises the techniques given above. >>>>> I do not think you should ever return more than one >> instance of a >>>>> given object in GET or GETNEXT. >>>>> >>>>> Tom Petch >>>>> nwnetworks@dial.pipex.com >>>>> >>>>> -----Original Message----- >>>>> From: Roy Jose >>>>> To: OSPF@DISCUSS.MICROSOFT.COM >>>>> Date: 20 January 2003 16:04 >>>>> Subject: OSPF MIB support for multiple OSPF processes >>>>> >>>>> >>>>>> Hi, >>>>>> >>>>>> Rfc1850 doesn't talk about what to be done regarding the >>>>> retrieval(GET) of >>>>>> MIB values when multiple OSPF processes exist on a >>> router. Out first >>>>>> impression is to return details about all the processes. >>> The problem >>>>> is >>>>>> while selecting values for MIB objects like >>>>>> ospfRouterId,ospfAreaBdrRtrStatus, ospfASBdrRtrStatus >>> etc. They may >>>>> differ >>>>>> in separate processes. The Qn is, can we really >> support multiple >>>>> processes >>>>>> with rfc1850? >>>>>> >>>>>> Thanks, >>>>>> Roy >>>>> >>>> _______________________________________________ >>>> Isis-wg mailing list >>>> Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg >>> >>> ============================================================ >>> The information contained in this message may be privileged >>> and confidential and protected from disclosure. If the >>> reader of this message is not the intended recipient, or an >>> employee or agent responsible for delivering this message to >>> the intended recipient, you are hereby notified that any >>> reproduction, dissemination or distribution of this >>> communication is strictly prohibited. If you have received >>> this communication in error, please notify us immediately by >>> replying to the message and deleting it from your computer. >>> >>> Thank you. >>> Tellabs ============================================================ >>> >> > > X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 > Received: from exchangefe2.na.procket.com ([10.1.7.252]) by > exchange0-0.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, > 13 May 2004 06:09:14 -0700 > MIME-Version: 1.0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > Received: from miata.procket.com ([10.1.1.1]) by > exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, > 13 May 2004 06:09:13 -0700 > Received: from smtp2.procket.com (smtp2.procket.com [65.174.124.37]) > by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4DD9Cd1029908; > Thu, 13 May 2004 06:09:12 -0700 (PDT) > Received: from optimus.ietf.org (datatracker.ietf.org [132.151.6.22]) > by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i4DFGtAw063099; > Thu, 13 May 2004 08:16:56 -0700 (PDT) > Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) > by optimus.ietf.org with esmtp (Exim 4.20) id 1BOFtV-00056H-Gr; Thu, > 13 May 2004 09:05:01 -0400 > Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by > optimus.ietf.org with esmtp (Exim 4.20) id 1BNebs-0007GU-Jm for > isis-wg@optimus.ietf.org; Tue, 11 May 2004 17:16:20 -0400 > Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org > (8.9.1a/8.9.1a) with ESMTP id RAA26354 for ; Tue, 11 > May 2004 17:16:16 -0400 (EDT) > Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by > ietf-mx with esmtp (Exim 4.32) id 1BNebq-0001xF-9x for > isis-wg@ietf.org; Tue, 11 May 2004 17:16:18 -0400 > Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id > 1BNeaw-0001Ws-00 for isis-wg@ietf.org; Tue, 11 May 2004 17:15:24 -0400 > Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by > ietf-mx with esmtp (Exim 4.12) id 1BNeaE-0000wJ-00 for > isis-wg@ietf.org; Tue, 11 May 2004 17:14:38 -0400 > Received: from zbl6c012.us.nortel.com > (zbl6c012.corpeast.baynetworks.com [132.245.205.62]) by > zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id > i4BLDpH19176; Tue, 11 May 2004 17:13:52 -0400 (EDT) > Received: by zbl6c012.corpeast.baynetworks.com with Internet Mail > Service (5.5.2653.19) id ; Tue, 11 May 2004 17:13:51 -0400 > Return-Path: > X-Mailer: Internet Mail Service (5.5.2653.19) > X-OriginalArrivalTime: 13 May 2004 13:09:14.0076 (UTC) > FILETIME=[7D1D51C0:01C438EB] > Errors-To: isis-wg-admin@ietf.org > X-BeenThere: isis-wg@ietf.org > X-Mailman-Version: 2.0.12 > List-Post: > List-Id: IETF IS-IS working group > List-Archive: > > X-Spam-Status: No, hits=0.5 required=5.0 > tests=AWL,HTML_30_40,HTML_MESSAGE autolearn=no version=2.60 > X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on > ietf-mx.ietf.org > Content-class: urn:content-classes:message > Subject: RE: [Isis-wg] RE: OSPF MIB support for multiple OSPF processes > Date: Tue, 11 May 2004 14:13:50 -0700 > Message-ID: > <6204FDDE129D364D8040A98BCCB290EF0951CE56@zbl6c004.corpeast.baynetworks > .com> > X-MS-Has-Attach: > X-MS-TNEF-Correlator: > Thread-Topic: [Isis-wg] RE: OSPF MIB support for multiple OSPF > processes > Thread-Index: AcQ4631ns1msUsdDQdeFUp5iJ6nRHw== > List-Help: > List-Subscribe: > , request@ietf.org?subject=subscribe> > List-Unsubscribe: > , request@ietf.org?subject=unsubscribe> > From: "Daniel Joyal" > Sender: > To: "Jeff Parker" , > "ISIS-WG (E-mail)" > Cc: > > I don't have a problem with the ISIS MIB supporting > multiple instances. Has the OAM directorate issued > any policy statements as to the preferred way to support > MIBs in virtual routers? > > -Dan > >> -----Original Message----- >> From: Jeff Parker [mailto:jparker@axiowave.com] >> Sent: Tuesday, May 11, 2004 2:37 PM >> To: ISIS-WG (E-mail) >> Cc: 'jonathan.sadler@tellabs.com'; Joyal, Daniel [BL60:NP31:EXCH] >> Subject: FW: [Isis-wg] RE: OSPF MIB support for multiple OSPF >> processes >> >> >> Here is one note from my mail files: I remember more >> discussions, but haven't stumbled across it. It does seem to >> come up every year or so. Periodic, with jitter applied. >> >> This is really more to the point that a virtual router is an >> important concept than a statement of how best to do this. >> >> - jeff parker >> >> >>> -----Original Message----- >>> From: Jonathan Sadler [mailto:jonathan.sadler@tellabs.com] >>> Sent: Tuesday, January 28, 2003 5:06 AM >>> To: Jeff Parker >>> Subject: Re: [Isis-wg] RE: OSPF MIB support for multiple OSPF >>> processes >>> >>> >>> Jeff - >>> >>> I do have use for this in SONET/SDH environments -- >>> specifically this index >>> allows for support of multiple logical IS-IS instances on >> one physical >>> platform. This is needed for: >>> - more than one Area per physical platform >>> - separation of IS-IS routing for the DCN from separate IS-IS >>> routing for other layer networks (i.e. GMPLS) >>> >>> Jeff Parker wrote: >>> >>>> >>>>> Jeff, >>>>> >>>>> Given the comments below, where did you get the requirement to >>>>> explicitly support multiple IS-IS instances in the IS-IS MIB? >>>>> >>>>> -Dan >>>> >>>> Dan - >>>> You are refering to the SysInstance index in >>>> the IS-IS MIB. Use of this was not a requirement: >>>> it came with the original version of the MIB I inherited. >>>> >>>> I would be interested to hear from any users >>>> that find this useful. While it seems to offer >>>> a solution, I don't know of any other MIB that supports this, so >>>> people will have to design an alternative anyway. >>>> >>>> It isn't too late to rip this out if it has >>>> no utility. >>>> >>>> - jeff parker >>>> >>>>> -----Original Message----- >>>>> From: Tom Petch [mailto:nwnetworks@DIAL.PIPEX.COM] >>>>> Sent: Monday, January 20, 2003 1:16 PM >>>>> To: OSPF@DISCUSS.MICROSOFT.COM >>>>> Subject: Re: OSPF MIB support for multiple OSPF processes >>>>> >>>>> >>>>> Yes. >>>>> In SNMPv1, this can be done by having multiple 'agents' >>> identified by >>>>> different community names or different IP addresses, each >>> accessing a >>>>> distinct incarnation of MIB II and its subordinate branches. In >>>>> SNMPv3, there is a more sophisticated mechanism of >>> contexts which >>>>> formalises the techniques given above. >>>>> I do not think you should ever return more than one >> instance of a >>>>> given object in GET or GETNEXT. >>>>> >>>>> Tom Petch >>>>> nwnetworks@dial.pipex.com >>>>> >>>>> -----Original Message----- >>>>> From: Roy Jose >>>>> To: OSPF@DISCUSS.MICROSOFT.COM >>>>> Date: 20 January 2003 16:04 >>>>> Subject: OSPF MIB support for multiple OSPF processes >>>>> >>>>> >>>>>> Hi, >>>>>> >>>>>> Rfc1850 doesn't talk about what to be done regarding the >>>>> retrieval(GET) of >>>>>> MIB values when multiple OSPF processes exist on a >>> router. Out first >>>>>> impression is to return details about all the processes. >>> The problem >>>>> is >>>>>> while selecting values for MIB objects like >>>>>> ospfRouterId,ospfAreaBdrRtrStatus, ospfASBdrRtrStatus >>> etc. They may >>>>> differ >>>>>> in separate processes. The Qn is, can we really >> support multiple >>>>> processes >>>>>> with rfc1850? >>>>>> >>>>>> Thanks, >>>>>> Roy >>>>> >>>> _______________________________________________ >>>> Isis-wg mailing list >>>> Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg >>> >>> ============================================================ >>> The information contained in this message may be privileged >>> and confidential and protected from disclosure. If the >>> reader of this message is not the intended recipient, or an >>> employee or agent responsible for delivering this message to >>> the intended recipient, you are hereby notified that any >>> reproduction, dissemination or distribution of this >>> communication is strictly prohibited. If you have received >>> this communication in error, please notify us immediately by >>> replying to the message and deleting it from your computer. >>> >>> Thank you. >>> Tellabs ============================================================ >>> >> > > X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 > Received: from exchangefe2.na.procket.com ([10.1.7.252]) by > exchange0-0.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, > 13 May 2004 06:09:14 -0700 > MIME-Version: 1.0 > Content-Type: text/plain; > charset="iso-8859-1" > Content-Transfer-Encoding: quoted-printable > Received: from miata.procket.com ([10.1.1.1]) by > exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, > 13 May 2004 06:09:13 -0700 > Received: from smtp2.procket.com (smtp2.procket.com [65.174.124.37]) > by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4DD9Cd1029908; > Thu, 13 May 2004 06:09:12 -0700 (PDT) > Received: from optimus.ietf.org (datatracker.ietf.org [132.151.6.22]) > by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i4DFGtAw063099; > Thu, 13 May 2004 08:16:56 -0700 (PDT) > Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) > by optimus.ietf.org with esmtp (Exim 4.20) id 1BOFtV-00056H-Gr; Thu, > 13 May 2004 09:05:01 -0400 > Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by > optimus.ietf.org with esmtp (Exim 4.20) id 1BNebs-0007GU-Jm for > isis-wg@optimus.ietf.org; Tue, 11 May 2004 17:16:20 -0400 > Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org > (8.9.1a/8.9.1a) with ESMTP id RAA26354 for ; Tue, 11 > May 2004 17:16:16 -0400 (EDT) > Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by > ietf-mx with esmtp (Exim 4.32) id 1BNebq-0001xF-9x for > isis-wg@ietf.org; Tue, 11 May 2004 17:16:18 -0400 > Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id > 1BNeaw-0001Ws-00 for isis-wg@ietf.org; Tue, 11 May 2004 17:15:24 -0400 > Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by > ietf-mx with esmtp (Exim 4.12) id 1BNeaE-0000wJ-00 for > isis-wg@ietf.org; Tue, 11 May 2004 17:14:38 -0400 > Received: from zbl6c012.us.nortel.com > (zbl6c012.corpeast.baynetworks.com [132.245.205.62]) by > zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id > i4BLDpH19176; Tue, 11 May 2004 17:13:52 -0400 (EDT) > Received: by zbl6c012.corpeast.baynetworks.com with Internet Mail > Service (5.5.2653.19) id ; Tue, 11 May 2004 17:13:51 -0400 > Return-Path: > X-Mailer: Internet Mail Service (5.5.2653.19) > X-OriginalArrivalTime: 13 May 2004 13:09:14.0076 (UTC) > FILETIME=[7D1D51C0:01C438EB] > Errors-To: isis-wg-admin@ietf.org > X-BeenThere: isis-wg@ietf.org > X-Mailman-Version: 2.0.12 > List-Post: > List-Id: IETF IS-IS working group > List-Archive: > > X-Spam-Status: No, hits=0.5 required=5.0 > tests=AWL,HTML_30_40,HTML_MESSAGE autolearn=no version=2.60 > X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on > ietf-mx.ietf.org > Content-class: urn:content-classes:message > Subject: RE: [Isis-wg] RE: OSPF MIB support for multiple OSPF processes > Date: Tue, 11 May 2004 14:13:50 -0700 > Message-ID: > <6204FDDE129D364D8040A98BCCB290EF0951CE56@zbl6c004.corpeast.baynetworks > .com> > X-MS-Has-Attach: > X-MS-TNEF-Correlator: > Thread-Topic: [Isis-wg] RE: OSPF MIB support for multiple OSPF > processes > Thread-Index: AcQ4631ns1msUsdDQdeFUp5iJ6nRHw== > List-Help: > List-Subscribe: > , request@ietf.org?subject=subscribe> > List-Unsubscribe: > , request@ietf.org?subject=unsubscribe> > From: "Daniel Joyal" > Sender: > To: "Jeff Parker" , > "ISIS-WG (E-mail)" > Cc: > > I don't have a problem with the ISIS MIB supporting > multiple instances. Has the OAM directorate issued > any policy statements as to the preferred way to support > MIBs in virtual routers? > > -Dan > >> -----Original Message----- >> From: Jeff Parker [mailto:jparker@axiowave.com] >> Sent: Tuesday, May 11, 2004 2:37 PM >> To: ISIS-WG (E-mail) >> Cc: 'jonathan.sadler@tellabs.com'; Joyal, Daniel [BL60:NP31:EXCH] >> Subject: FW: [Isis-wg] RE: OSPF MIB support for multiple OSPF >> processes >> >> >> Here is one note from my mail files: I remember more >> discussions, but haven't stumbled across it. It does seem to >> come up every year or so. Periodic, with jitter applied. >> >> This is really more to the point that a virtual router is an >> important concept than a statement of how best to do this. >> >> - jeff parker >> >> >>> -----Original Message----- >>> From: Jonathan Sadler [mailto:jonathan.sadler@tellabs.com] >>> Sent: Tuesday, January 28, 2003 5:06 AM >>> To: Jeff Parker >>> Subject: Re: [Isis-wg] RE: OSPF MIB support for multiple OSPF >>> processes >>> >>> >>> Jeff - >>> >>> I do have use for this in SONET/SDH environments -- >>> specifically this index >>> allows for support of multiple logical IS-IS instances on >> one physical >>> platform. This is needed for: >>> - more than one Area per physical platform >>> - separation of IS-IS routing for the DCN from separate IS-IS >>> routing for other layer networks (i.e. GMPLS) >>> >>> Jeff Parker wrote: >>> >>>> >>>>> Jeff, >>>>> >>>>> Given the comments below, where did you get the requirement to >>>>> explicitly support multiple IS-IS instances in the IS-IS MIB? >>>>> >>>>> -Dan >>>> >>>> Dan - >>>> You are refering to the SysInstance index in >>>> the IS-IS MIB. Use of this was not a requirement: >>>> it came with the original version of the MIB I inherited. >>>> >>>> I would be interested to hear from any users >>>> that find this useful. While it seems to offer >>>> a solution, I don't know of any other MIB that supports this, so >>>> people will have to design an alternative anyway. >>>> >>>> It isn't too late to rip this out if it has >>>> no utility. >>>> >>>> - jeff parker >>>> >>>>> -----Original Message----- >>>>> From: Tom Petch [mailto:nwnetworks@DIAL.PIPEX.COM] >>>>> Sent: Monday, January 20, 2003 1:16 PM >>>>> To: OSPF@DISCUSS.MICROSOFT.COM >>>>> Subject: Re: OSPF MIB support for multiple OSPF processes >>>>> >>>>> >>>>> Yes. >>>>> In SNMPv1, this can be done by having multiple 'agents' >>> identified by >>>>> different community names or different IP addresses, each >>> accessing a >>>>> distinct incarnation of MIB II and its subordinate branches. In >>>>> SNMPv3, there is a more sophisticated mechanism of >>> contexts which >>>>> formalises the techniques given above. >>>>> I do not think you should ever return more than one >> instance of a >>>>> given object in GET or GETNEXT. >>>>> >>>>> Tom Petch >>>>> nwnetworks@dial.pipex.com >>>>> >>>>> -----Original Message----- >>>>> From: Roy Jose >>>>> To: OSPF@DISCUSS.MICROSOFT.COM >>>>> Date: 20 January 2003 16:04 >>>>> Subject: OSPF MIB support for multiple OSPF processes >>>>> >>>>> >>>>>> Hi, >>>>>> >>>>>> Rfc1850 doesn't talk about what to be done regarding the >>>>> retrieval(GET) of >>>>>> MIB values when multiple OSPF processes exist on a >>> router. Out first >>>>>> impression is to return details about all the processes. >>> The problem >>>>> is >>>>>> while selecting values for MIB objects like >>>>>> ospfRouterId,ospfAreaBdrRtrStatus, ospfASBdrRtrStatus >>> etc. They may >>>>> differ >>>>>> in separate processes. The Qn is, can we really >> support multiple >>>>> processes >>>>>> with rfc1850? >>>>>> >>>>>> Thanks, >>>>>> Roy >>>>> >>>> _______________________________________________ >>>> Isis-wg mailing list >>>> Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg >>> >>> ============================================================ >>> The information contained in this message may be privileged >>> and confidential and protected from disclosure. If the >>> reader of this message is not the intended recipient, or an >>> employee or agent responsible for delivering this message to >>> the intended recipient, you are hereby notified that any >>> reproduction, dissemination or distribution of this >>> communication is strictly prohibited. If you have received >>> this communication in error, please notify us immediately by >>> replying to the message and deleting it from your computer. >>> >>> Thank you. >>> Tellabs ============================================================ >>> >> > _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Thu May 27 20:02:29 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06079 for ; Thu, 27 May 2004 20:02:29 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTUVR-00021z-Ij; Thu, 27 May 2004 19:41:49 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTU2I-0003k1-CJ for isis-wg@megatron.ietf.org; Thu, 27 May 2004 19:11:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03903 for ; Thu, 27 May 2004 19:11:31 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BTU28-00077U-P7 for isis-wg@ietf.org; Thu, 27 May 2004 19:11:32 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BTU0x-0006qo-00 for isis-wg@ietf.org; Thu, 27 May 2004 19:10:20 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BTU0K-0006YX-00; Thu, 27 May 2004 19:09:40 -0400 Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i4RN7kJ26545; Thu, 27 May 2004 16:07:46 -0700 (PDT) Message-Id: <200405272307.i4RN7kJ26545@boreas.isi.edu> To: IETF-Announce: ; From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 27 May 2004 16:07:46 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 Cc: isis-wg@ietf.org, rfc-editor@rfc-editor.org Subject: [Isis-wg] RFC 3786 on Extending the Number of Intermediate System to Intermediate System (IS-IS) Link State PDU (LSP) Fragments Beyond the 256 Limit X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3786 Title: Extending the Number of Intermediate System to Intermediate System (IS-IS) Link State PDU (LSP) Fragments Beyond the 256 Limit Author(s): A. Hermelin, S. Previdi, M. Shand Status: Montilio Inc., Cisco Systems, Cisco Systems Date: May 2004 Mailbox: amir@montilio.com, sprevidi@cisco.com, mshand@cisco.com Pages: 14 Characters: 29164 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-ext-lsp-frags-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3786.txt This document describes a mechanism that allows a system to originate more than 256 Link State PDU (LSP) fragments, a limit set by the original Intermediate System to Intermediate System (IS-IS) Routing protocol, as described in ISO/IEC 10589. This mechanism can be used in IP-only, OSI-only, and dual routers. This document is a product of the IS-IS for IP Internets Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040527160629.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3786 --OtherAccess Content-Type: Message/External-body; name="rfc3786.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040527160629.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Thu May 27 20:02:30 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06096 for ; Thu, 27 May 2004 20:02:30 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTUVT-00022h-1U; Thu, 27 May 2004 19:41:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTU3k-0004Ok-SF for isis-wg@megatron.ietf.org; Thu, 27 May 2004 19:13:12 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03967 for ; Thu, 27 May 2004 19:13:01 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BTU3b-0007eW-5g for isis-wg@ietf.org; Thu, 27 May 2004 19:13:03 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BTU2c-0007O5-00 for isis-wg@ietf.org; Thu, 27 May 2004 19:12:03 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BTU1t-0006rT-00; Thu, 27 May 2004 19:11:17 -0400 Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i4RN9lJ27155; Thu, 27 May 2004 16:09:47 -0700 (PDT) Message-Id: <200405272309.i4RN9lJ27155@boreas.isi.edu> To: IETF-Announce: ; From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Thu, 27 May 2004 16:09:47 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.1 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 Cc: isis-wg@ietf.org, rfc-editor@rfc-editor.org Subject: [Isis-wg] RFC 3787 on Recommendations for Interoperable IP Networks using Intermediate System to Intermediate System (IS-IS) X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3787 Title: Recommendations for Interoperable IP Networks using Intermediate System to Intermediate System (IS-IS) Author(s): J. Parker, Ed. Status: Informational Date: May 2004 Mailbox: jparker@axiowave.com Pages: 11 Characters: 25426 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-ip-interoperable-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3787.txt This document discusses a number of differences between the Intermediate System to Intermediate System (IS-IS) protocol used to route IP traffic as described in RFC 1195 and the protocol as it is deployed today. These differences are discussed as a service to those implementing, testing, and deploying the IS-IS Protocol to route IP traffic. A companion document describes the differences between the protocol described in ISO 10589 and current practice. This document is a product of the IS-IS for IP Internets Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040527160801.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3787 --OtherAccess Content-Type: Message/External-body; name="rfc3787.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040527160801.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Fri May 28 03:07:58 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08637 for ; Fri, 28 May 2004 03:07:58 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTbKB-0005EY-3f; Fri, 28 May 2004 02:58:39 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTbIF-0004sg-Vh for isis-wg@megatron.ietf.org; Fri, 28 May 2004 02:56:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA08005 for ; Fri, 28 May 2004 02:56:37 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BTbID-0002Ur-Kz for isis-wg@ietf.org; Fri, 28 May 2004 02:56:37 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BTbHS-00029n-00 for isis-wg@ietf.org; Fri, 28 May 2004 02:55:51 -0400 Received: from mail.axiowave.com ([64.115.125.242] helo=bridge.axiowave.com) by ietf-mx with esmtp (Exim 4.12) id 1BTbGd-0001m1-00 for isis-wg@ietf.org; Fri, 28 May 2004 02:54:59 -0400 Message-ID: From: Jeff Parker To: "ISIS-WG (E-mail)" Date: Fri, 28 May 2004 02:54:28 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60 Subject: [Isis-wg] Draft Update X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org I have forwarded version 15 of the IS-IS Mib to the IETF. There were two spelling corrections, and isisSysInstance has been removed from all tables. There has been a request for instrumentation of the MT draft, and we should probably consider modifications to support control of alternative SPFs using TE shortcuts, following the recent draft. Suggestions welcome, or I can get creative. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-bounces@ietf.org Fri May 28 17:53:59 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10165 for ; Fri, 28 May 2004 17:53:59 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BTotN-0004wE-T5; Fri, 28 May 2004 17:27:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BToK0-0003WM-VS for isis-wg@megatron.ietf.org; Fri, 28 May 2004 16:51:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04070 for ; Fri, 28 May 2004 16:51:18 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BToJz-0001D6-Lb for isis-wg@ietf.org; Fri, 28 May 2004 16:51:19 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BToJ8-0000lz-00 for isis-wg@ietf.org; Fri, 28 May 2004 16:50:26 -0400 Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BToI7-0007fZ-00; Fri, 28 May 2004 16:49:23 -0400 Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i4SKm5J24176; Fri, 28 May 2004 13:48:05 -0700 (PDT) Message-Id: <200405282048.i4SKm5J24176@boreas.isi.edu> To: IETF-Announce: ; From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Fri, 28 May 2004 13:48:05 -0700 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=-9.0 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME,USER_IN_DEF_WHITELIST autolearn=no version=2.60 Cc: isis-wg@ietf.org, rfc-editor@rfc-editor.org Subject: [Isis-wg] Correction: RFC 3786 on Extending the Number of Intermediate System to Intermediate System (IS-IS) Link State PDU (LSP) Fragments Beyond the 256 Limit X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3786 Title: Extending the Number of Intermediate System to Intermediate System (IS-IS) Link State PDU (LSP) Fragments Beyond the 256 Limit Author(s): A. Hermelin, S. Previdi, M. Shand Status: Informational Date: May 2004 Mailbox: amir@montilio.com, sprevidi@cisco.com, mshand@cisco.com Pages: 14 Characters: 29164 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-isis-ext-lsp-frags-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3786.txt This document describes a mechanism that allows a system to originate more than 256 Link State PDU (LSP) fragments, a limit set by the original Intermediate System to Intermediate System (IS-IS) Routing protocol, as described in ISO/IEC 10589. This mechanism can be used in IP-only, OSI-only, and dual routers. This document is a product of the IS-IS for IP Internets Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <040528134547.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3786 --OtherAccess Content-Type: Message/External-body; name="rfc3786.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <040528134547.RFC@RFC-EDITOR.ORG> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg --NextPart-- From isis-wg-bounces@ietf.org Sat May 29 11:13:32 2004 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08112 for ; Sat, 29 May 2004 11:13:32 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BU5UG-0000PX-CJ; Sat, 29 May 2004 11:11:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BU5RH-0008My-Kn for isis-wg@megatron.ietf.org; Sat, 29 May 2004 11:07:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07955 for ; Sat, 29 May 2004 11:07:57 -0400 (EDT) Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BU5RG-0007YP-Nm for isis-wg@ietf.org; Sat, 29 May 2004 11:07:58 -0400 Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BU5QH-0007A3-00 for isis-wg@ietf.org; Sat, 29 May 2004 11:06:57 -0400 Received: from smtp2.procket.com ([65.174.124.37]) by ietf-mx with esmtp (Exim 4.12) id 1BU5PN-0006Qk-00 for isis-wg@ietf.org; Sat, 29 May 2004 11:06:01 -0400 Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60]) by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i4THDUAw046786; Sat, 29 May 2004 10:13:30 -0700 (PDT) Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id i4TF5Hd1006484; Sat, 29 May 2004 08:05:17 -0700 (PDT) Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713); Sat, 29 May 2004 08:05:16 -0700 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v618) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <97DEEE0E-B181-11D8-A39B-00039303E9E2@procket.com> Content-Transfer-Encoding: 7bit From: Christian Hopps Subject: Re: [Isis-wg] Draft Update Date: Sat, 29 May 2004 08:05:16 -0700 To: "Jeff Parker" X-Mailer: Apple Mail (2.618) X-OriginalArrivalTime: 29 May 2004 15:05:17.0010 (UTC) FILETIME=[59F4BB20:01C4458E] X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 Content-Transfer-Encoding: 7bit Cc: "ISIS-WG \(E-mail\)" X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: isis-wg-bounces@ietf.org Errors-To: isis-wg-bounces@ietf.org Content-Transfer-Encoding: 7bit On May 27, 2004, at 11:54 PM, Jeff Parker wrote: > I have forwarded version 15 of the IS-IS Mib to the IETF. > There were two spelling corrections, and isisSysInstance has been > removed > from all tables. Thanks. > There has been a request for instrumentation of the MT draft, and we > should > probably consider modifications to support control of alternative SPFs > using > TE shortcuts, following the recent draft. We *really* need to "finish" this MIB, i.e., get a standard MIB defined. At some point I think we as a WG need to pull the trigger. If the MT people are willing to suggest the needed changes we probably should consider adding them; however, I do not think we should wait very long at all (i.e., maybe 2 weeks) for this to occur. Chris. > Suggestions welcome, or I can get creative. > > - jeff parker > > _______________________________________________ > 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