From isis-wg-admin@ietf.org Mon Mar 3 10:52:03 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00456 for ; Mon, 3 Mar 2003 10:52:03 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23Ft3p28488; Mon, 3 Mar 2003 10:55:04 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23Frcp28366 for ; Mon, 3 Mar 2003 10:53:38 -0500 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00063 for ; Mon, 3 Mar 2003 10:43:04 -0500 (EST) Message-ID: From: Jeff Parker To: "'Manral, Vishwas'" Cc: "ISIS-WG (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-11.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: Mon, 3 Mar 2003 10:45:01 -0500 > Hi Jeff, > > What does a value of "none" mean for the > isisLSPLevel, shouldn't the valid > values be only L1 and L2? Or does this > mean irrespective of level? > > Thanks, > Vishwas Vishwas - Looking at the MIB, this TC is used a number of places where the level -is- well defined, but it is also used in Notifications. If, for example, you get a packet with a different version number, you don't really know the level of the packet, and would use "none" in the notification. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Mar 3 11:58:02 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02924 for ; Mon, 3 Mar 2003 11:58:02 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23GxOp02368; Mon, 3 Mar 2003 11:59:25 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23Gw8p02284 for ; Mon, 3 Mar 2003 11:58:08 -0500 Received: from ftpbox.mot.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA02523 for ; Mon, 3 Mar 2003 11:47:34 -0500 (EST) Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by ftpbox.mot.com (Motorola/Ftpbox) with ESMTP id h23Gn0Ti029539 for ; Mon, 3 Mar 2003 09:49:00 -0700 (MST) Received: [from xover.corp.mot.com (xover.corp.mot.com [10.1.148.18]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id JAA00869 for ; Mon, 3 Mar 2003 09:47:11 -0700 (MST)] Received: by xover.corp.mot.com with Internet Mail Service (5.5.2653.19) id ; Mon, 3 Mar 2003 11:48:58 -0500 Message-ID: From: "Manral, Vishwas" To: "'Jeff Parker'" Cc: "ISIS-WG (E-mail)" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-11.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: Mon, 3 Mar 2003 11:50:46 -0500 Jeff, Are you saying that a value of "none" would be wrong in this particular case? Thanks, Vishwas -----Original Message----- From: Jeff Parker [mailto:jparker@axiowave.com] Sent: Monday, March 03, 2003 9:15 PM To: 'Manral, Vishwas' Cc: ISIS-WG (E-mail) Subject: RE: draft-ietf-isis-wg-mib-11.txt > Hi Jeff, > > What does a value of "none" mean for the > isisLSPLevel, shouldn't the valid > values be only L1 and L2? Or does this > mean irrespective of level? > > Thanks, > Vishwas Vishwas - Looking at the MIB, this TC is used a number of places where the level -is- well defined, but it is also used in Notifications. If, for example, you get a packet with a different version number, you don't really know the level of the packet, and would use "none" in the notification. - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Mar 3 12:27:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA04016 for ; Mon, 3 Mar 2003 12:27:18 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23HV8p05913; Mon, 3 Mar 2003 12:31:08 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23HUrp05857 for ; Mon, 3 Mar 2003 12:30:53 -0500 Received: from sj-msg-core-4.cisco.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03750 for ; Mon, 3 Mar 2003 12:20:18 -0500 (EST) Received: from mira-sjc5-a.cisco.com (IDENT:mirapoint@mira-sjc5-a.cisco.com [171.71.163.34]) by sj-msg-core-4.cisco.com (8.12.2/8.12.6) with ESMTP id h23HMJ6N019349 for ; Mon, 3 Mar 2003 09:22:19 -0800 (PST) Received: from ginsberg-w2k.cisco.com (sjc-vpn3-374.cisco.com [10.21.65.118]) by mira-sjc5-a.cisco.com (Mirapoint Messaging Server MOS 3.2.1-GA) with ESMTP id AEM03936; Mon, 3 Mar 2003 09:04:58 -0800 (PST) Message-Id: <4.3.2.7.2.20030303090250.00b62920@mira-sjc5-3.cisco.com> X-Sender: ginsberg@mira-sjc5-3.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: isis-wg@ietf.org From: Les Ginsberg Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Subject: [Isis-wg] New Version of draft-ietf-isis-restart 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, 03 Mar 2003 09:22:17 -0800 Folks - Mike Shand and I have submitted V3 of draft-ietf-isis-restart (V2 was withdrawn from last call at our request). Since we submitted it close to the deadline, it may take a while for the official announcement to appear. In addition to making some clarifications based on review comments from the list, the new version includes the following changes: 1)We now make explicit that the LANID must be ignored in IIHs having the RR bit set. This is something that implementation experience shows is necessary. As it affects the bits on the wire (what is sent as LANID by neighbors of the restarting router) it seemed necessary to explicitly state this in the draft. 2)New functionality in the case of a starting (NOT restarting) router is defined to prevent the potential occurrence of transient blackholes due to the presence in the network of LSP fragments from a previous incarnation of the starting router. 3)The text in the draft has been restructured to more clearly show the commonalities and differences in behavior between the restarting and starting cases. Finally, and MOST IMPORTANT, implementations based on the old version(V2) of the draft will interoperate with versions based on the new draft, though of course the new functionality will not be supported. Cheers. Les _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Mon Mar 3 16:23:14 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13321 for ; Mon, 3 Mar 2003 16:23:14 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23LLXp27074; Mon, 3 Mar 2003 16:21:34 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h23LKDp27039 for ; Mon, 3 Mar 2003 16:20:13 -0500 Received: from dmz2.procket.com (dmz2.procket.com [65.174.124.37]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA13001 for ; Mon, 3 Mar 2003 16:09:33 -0500 (EST) Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60]) by dmz2.procket.com (Postfix) with ESMTP id ABF7434438 for ; Mon, 3 Mar 2003 12:23:45 -0800 (PST) Received: from EXCHANGE0-0.na.procket.com (exchange0b.na.procket.com [10.1.7.8]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id h23LB4Dw025065 for ; Mon, 3 Mar 2003 13:11:04 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Thread-Topic: IETF 56 Presentation Submissions Thread-Index: AcLhwJ4O8Hg/0f09ToK/B/vEnp21TAACLHfg From: "Tony Li" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h23LKDp27040 Subject: [Isis-wg] FW: IETF 56 Presentation Submissions 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 Mar 2003 13:11:04 -0800 Content-Transfer-Encoding: 8bit Would folks who are presenting, please make an effort to get their presentations in ahead of time? Thanks, Tony | -----Original Message----- | From: IETF Proceedings Administrator [mailto:minutes@ietf.org] | Sent: Monday, March 03, 2003 11:53 AM | To: wgchairs@ietf.org; bofchairs@ietf.org; Steve Coya | Subject: IETF 56 Presentation Submissions | | | This message is for all group chairs who will be meeting | in San Francisco. | | Presentations may be submitted for online viewing at IETF | 56 along with | any interim sessions since Atlanta (55). | | These materials may be sent in until Thursday, March 14th @ 5:00pm. | After this cutoff date materials may be submitted onsite at the | Registration Desk, however please allow at least 1 day for | new posts to | be listed online. | | Please see www.ietf.org/proceedings/03mar/ for | guidelines and the | group submission form. | | Thank you, | IETF Secretariat | | | | | | _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Tue Mar 4 05:45:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11845 for ; Tue, 4 Mar 2003 05:45:21 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24ArWp24615; Tue, 4 Mar 2003 05:53:32 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Aqfp24551 for ; Tue, 4 Mar 2003 05:52:41 -0500 Received: from motgate3.mot.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA11744 for ; Tue, 4 Mar 2003 05:41:43 -0500 (EST) Received: from pobox3.mot.com (pobox3.mot.com [10.64.251.242]) by motgate3.mot.com (Motorola/Motgate3) with ESMTP id h24AhJYk016271 for ; Tue, 4 Mar 2003 03:43:19 -0700 (MST) Received: [from xover.corp.mot.com (xover.corp.mot.com [10.1.148.18]) by pobox3.mot.com (MOT-pobox3 2.0) with ESMTP id DAA10343 for ; Tue, 4 Mar 2003 03:41:56 -0700 (MST)] Received: by xover.corp.mot.com with Internet Mail Service (5.5.2653.19) id ; Tue, 4 Mar 2003 05:43:44 -0500 Message-ID: From: "Manral, Vishwas" To: "'Jeff Parker'" Cc: "ISIS-WG (E-mail)" MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-11.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 4 Mar 2003 05:45:29 -0500 Hi Jeff, Some minor comments. Does the isisLSPTLVIndex mean the offset in bytes from the header or the TLV number(like the first/second/nth TLV) in the contents of the LSP? I think its the latter. It would be nice if this was clarified further in the "DESCRIPTION". Besides I am not sure if I have asked you for this, but can we change isisLSPTLVSeq to isisLSPTLVLSPSeq and isisLSPTLVChecksum to isisLSPTLVLSPChecksum. Also in isisLSPID description you can replace the "Fragment Number" as "LSP Number" in isisLSPSummaryTable. Thanks, Vishwas -----Original Message----- From: Jeff Parker [mailto:jparker@axiowave.com] Sent: Monday, March 03, 2003 9:15 PM To: 'Manral, Vishwas' Cc: ISIS-WG (E-mail) Subject: RE: draft-ietf-isis-wg-mib-11.txt > Hi Jeff, > > What does a value of "none" mean for the > isisLSPLevel, shouldn't the valid > values be only L1 and L2? Or does this > mean irrespective of level? > > Thanks, > Vishwas Vishwas - Looking at the MIB, this TC is used a number of places where the level -is- well defined, but it is also used in Notifications. If, for example, you get a packet with a different version number, you don't really know the level of the packet, and would use "none" in the notification. - 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 Mar 4 07:35:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15506 for ; Tue, 4 Mar 2003 07:35:42 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24CiMp32165; Tue, 4 Mar 2003 07:44:22 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h24Cdip31896 for ; Tue, 4 Mar 2003 07:39:44 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14703; Tue, 4 Mar 2003 07:28:46 -0500 (EST) Message-Id: <200303041228.HAA14703@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-experimental-tlv-00.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 04 Mar 2003 07:28:46 -0500 --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-00.txt Pages : 6 Date : 2003-3-3 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-00.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-experimental-tlv-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-isis-experimental-tlv-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-3-3144849.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-experimental-tlv-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-experimental-tlv-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-3-3144849.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 Mar 6 06:33:59 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04056 for ; Thu, 6 Mar 2003 06:33:59 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26Bg7O26837; Thu, 6 Mar 2003 06:42:07 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h26BdsO26556 for ; Thu, 6 Mar 2003 06:39:54 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA03200; Thu, 6 Mar 2003 06:28:24 -0500 (EST) Message-Id: <200303061128.GAA03200@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-restart-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: Thu, 06 Mar 2003 06:28:24 -0500 --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 : Restart signaling for IS-IS Author(s) : M. Shand, L. Ginsberg Filename : draft-ietf-isis-restart-03.txt Pages : 13 Date : 2003-3-5 The IS-IS routing protocol (RFC 1142 [2], ISO/IEC 10589 [3]) is a link state intra-domain routing protocol. Normally, when an IS-IS router is re-started, the neighboring routers detect the restart event and cycle their adjacencies with the restarting router through the down state. This is necessary in order to invoke the protocol mechanisms to ensure correct re-synchronization of the LSP database. However, the cycling of the adjacency state causes the neighbors to regenerate their LSPs describing the adjacency concerned. This in turn causes temporary disruption of routes passing through the restarting router. In certain scenarios such temporary disruption of the routes is highly undesirable. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-restart-03.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-restart-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-restart-03.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-3-5141114.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-restart-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-restart-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-3-5141114.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 Wed Mar 12 07:54:19 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02149 for ; Wed, 12 Mar 2003 07:54:19 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2CD5rO09311; Wed, 12 Mar 2003 08:05:54 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2CD4FO09226 for ; Wed, 12 Mar 2003 08:04:15 -0500 Received: from giga.kayz.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA02025 for ; Wed, 12 Mar 2003 07:49:47 -0500 (EST) Received: from localhost ([127.0.0.1] helo=giga.kayz.org) by giga.kayz.org with esmtp (Exim 3.35 #1 (Debian)) id 18t5i8-00008k-00; Wed, 12 Mar 2003 04:51:56 -0800 Message-ID: <87ptowagt3.wl@giga.kayz.org> From: Noguchi Kay To: isis-wg@ietf.org cc: kay@ipinfusion.com, toshiaki@ipinfusion.com X-Mailer: Wanderlust/2.8.1 MIME-Version: 1.0 (generated by SEMI 1.14.4 - "Hosorogi") Content-Type: text/plain; charset=US-ASCII Subject: [Isis-wg] draft-noguchi-isis-protocol-topology-01.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 Mar 2003 04:51:52 -0800 Hi all, This is Kay. I updated our draft, Protocol Topology Support for IS-IS. You can download it from the ietf site with this URL. http://ietf.org/internet-drafts/draft-noguchi-isis-protocol-topology-01.txt The change includes, - it makes clear the adjacency section as Jeff suggested. - it adds one section which discribes "Migration from Node Oriented to Interface Oriented Protocol Support". I'll make a presentation in the next IETF so hope you guys read the draft before the meeting. Thank you, kay _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Fri Mar 14 10:51:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00173 for ; Fri, 14 Mar 2003 10:51:49 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EG2aO19920; Fri, 14 Mar 2003 11:02:37 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EFuVO19614 for ; Fri, 14 Mar 2003 10:56:31 -0500 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29881 for ; Fri, 14 Mar 2003 10:41:01 -0500 (EST) Message-ID: From: Jeff Parker To: "'Manral, Vishwas'" Cc: "ISIS-WG (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] RE: draft-ietf-isis-wg-mib-11.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: Fri, 14 Mar 2003 10:43:07 -0500 Cleaning up unanswered mail > Sent 3/4/03 > > Hi Jeff, > > Some minor comments. Does the isisLSPTLVIndex mean the offset > in bytes from > the header or the TLV number(like the first/second/nth TLV) > in the contents > of the LSP? Good point. Is this clearer? isisLSPTLVIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS read-only STATUS current DESCRIPTION "The index of this TLV in the LSP. The first TLV has index 1, the Nth TLV has an index on N." ::= { isisLSPTLVEntry 1 } > Besides I am not sure if I have asked you for this, but can we change > isisLSPTLVSeq to isisLSPTLVLSPSeq and isisLSPTLVChecksum to > isisLSPTLVLSPChecksum. Remind me why is this a good idea. > Also in isisLSPID description you can replace the > "Fragment Number" as "LSP Number" in isisLSPSummaryTable. > > Thanks, > Vishwas I can only speak for myself, but I find "LSP Number" is ambiguous. There are many things that this term could refer to. In the context of the description (see below) I think "Frament Number" is clearer. isisLSPID OBJECT-TYPE SYNTAX LinkStatePDUID MAX-ACCESS not-accessible STATUS current DESCRIPTION "The 8 byte LSP ID, consisting of the SystemID, Circuit ID, and Fragment Number." ::= { isisLSPSummaryEntry 2 } - jeff parker _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Fri Mar 14 10:59:50 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00421 for ; Fri, 14 Mar 2003 10:59:50 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EGB4O21187; Fri, 14 Mar 2003 11:11:04 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2EG8VO21041 for ; Fri, 14 Mar 2003 11:08:31 -0500 Received: from bridge.axiowave.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00208 for ; Fri, 14 Mar 2003 10:53:00 -0500 (EST) Message-ID: From: Jeff Parker To: "'Jonnala, Nagi'" Cc: "ISIS-WG (E-mail)" MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: [Isis-wg] RE: Description of isisSysLevelOverloadState Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 14 Mar 2003 10:54:55 -0500 > Jeff, > > The description of isisSysLevelOverloadState contains the below. > > The administrator may set the state to 'waiting' when > the router is initializing by setting the object > > [But this is a read-only object. How can the administrator set it?] > > I think we need to modify the wording here. > > -Nagi. Nagi - Good point. I have modified the text of the Description clause, included below. The isisSysLevelSetOverload object remains read-create. It is also included below for reference. The LevelState TC includes both overloaded (natural causes) and waiting (set by administrator) so that a manager can tell why the system's overload bit is set. - jeff LevelState ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "States of the IS-IS protocol." SYNTAX INTEGER { off (1), on (2), waiting (3), overloaded(4) } isisSysLevelOverloadState OBJECT-TYPE SYNTAX LevelState MAX-ACCESS read-only STATUS current DESCRIPTION "The Overload state of the database at this level. The value 'overloaded' indicates a database that is low on an essential resource, such as memory. The administrator may indirectly force the state to 'waiting' when the router is initializing by setting the object isisSysLevelSetOverload. If the state is waiting or overloaded, we originate LSPs with the Overload bit set." REFERENCE "{ISIS.aoi l1State (17)}" ::= { isisSysLevelEntry 4 } isisSysLevelSetOverload OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-create STATUS current DESCRIPTION "Administratively set the overload bit for the level. The overload bit will continue to be set if the implementation runs out of memory, independent of this variable" DEFVAL { false } ::= { isisSysLevelEntry 5 } _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Mar 19 18:40:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16150 for ; Wed, 19 Mar 2003 18:40:33 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JNtdO19767; Wed, 19 Mar 2003 18:55:39 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2JNsIO19710 for ; Wed, 19 Mar 2003 18:54:18 -0500 Received: from dmz1.procket.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA16020 for ; Wed, 19 Mar 2003 18:36:11 -0500 (EST) Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60]) by dmz1.procket.com (Postfix) with ESMTP id 577B223C61 for ; Wed, 19 Mar 2003 16:01:56 -0800 (PST) Received: from EXCHANGE0-0.na.procket.com (exchange0a.na.procket.com [10.1.7.7]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id h2JNcPYB018431 for ; Wed, 19 Mar 2003 15:38:26 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: Thread-Topic: Blue sheets Thread-Index: AcLucKLGcobftwLkRgiiQ1EApBE1pQ== From: "Tony Li" To: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2JNsIO19711 Subject: [Isis-wg] Blue sheets 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, 19 Mar 2003 15:38:25 -0800 Content-Transfer-Encoding: 8bit If anyone picked up the blue sheets after last night's meeting, could you please get them to me. Thanks, Tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Mar 19 22:40:06 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA22589 for ; Wed, 19 Mar 2003 22:40:05 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K3tqO03815; Wed, 19 Mar 2003 22:55:52 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2K1taO28876 for ; Wed, 19 Mar 2003 20:55:36 -0500 Received: from presque.nexthop.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20081 for ; Wed, 19 Mar 2003 20:37:28 -0500 (EST) Received: (from root@localhost) by presque.nexthop.com (8.12.8/8.11.1) id h2K1df42073595; Wed, 19 Mar 2003 20:39:41 -0500 (EST) (envelope-from shares@nexthop.com) Received: from mail.corp.nexthop.com ([64.211.218.233]) by presque.nexthop.com (8.12.8/8.12.8) with ESMTP id h2K1dVNp073552 for ; Wed, 19 Mar 2003 20:39:32 -0500 (EST) (envelope-from shares@nexthop.com) content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 Subject: RE: [Isis-wg] Blue sheets Message-ID: Thread-Topic: Blue sheets Thread-Index: AcLucKLGcobftwLkRgiiQ1EApBE1pQAENQ5A From: "Susan Hares" To: "Tony Li" , X-Virus-Scanned: by AMaViS perl-11 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h2K1taO28877 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, 19 Mar 2003 20:39:26 -0500 Content-Transfer-Encoding: 8bit Tony: I picked them up and delivered them to the IETF folks. You can get a copy (if you wish from them). Sue Hares -----Original Message----- From: Tony Li [mailto:Tony.Li@procket.com] Sent: Wednesday, March 19, 2003 6:38 PM To: isis-wg@ietf.org Subject: [Isis-wg] Blue sheets If anyone picked up the blue sheets after last night's meeting, could you please get them to me. Thanks, Tony _______________________________________________ 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 Thu Mar 27 07:56:20 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26126 for ; Thu, 27 Mar 2003 07:56:20 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RDCFO14813; Thu, 27 Mar 2003 08:12:15 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RD81O14499 for ; Thu, 27 Mar 2003 08:08:01 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25460; Thu, 27 Mar 2003 07:46:14 -0500 (EST) Message-Id: <200303271246.HAA25460@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-multi-topology-06.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, 27 Mar 2003 07:46:14 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : M-ISIS: Multi Topology (MT)Routing in IS-IS Author(s) : T. Przygienda, N. Shen, N. Sheth Filename : draft-ietf-isis-wg-multi-topology-06.txt Pages : 11 Date : 2003-3-26 This draft describes an optional mechanism within ISIS used today by many ISPs for IGP routing within their clouds. This draft describes how to run within a single ISIS domain a set of independent IP topologies that we call Multi-Topologies (MTs). This MT extension can be used for variety of purposes such as an in-band management network ``on top'' of the original IGP topology, maintain separate IGP routing domains for isolated multicast or IPv6 islands within the backbone, or force a subset of an address space to follow a different topology. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-multi-topology-06.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-wg-multi-topology-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-isis-wg-multi-topology-06.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-3-26123003.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-wg-multi-topology-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-wg-multi-topology-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-3-26123003.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 Mar 27 07:58:16 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26201 for ; Thu, 27 Mar 2003 07:58:16 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RDERO14910; Thu, 27 Mar 2003 08:14:27 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2RD86O14511 for ; Thu, 27 Mar 2003 08:08:06 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA25478; Thu, 27 Mar 2003 07:46:19 -0500 (EST) Message-Id: <200303271246.HAA25478@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-igp-p2p-over-lan-02.txt Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 27 Mar 2003 07:46:19 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : Point-to-point operation over LAN in link-state routing protocols Author(s) : N. Shen et al. Filename : draft-ietf-isis-igp-p2p-over-lan-02.txt Pages : 8 Date : 2003-3-26 The two predominant circuit types used by link state routing protocols are point-to-point and broadcast. It is important to identify the correct circuit type when forming adjacencies, flooding link state database packets, and representing the circuit topologically. This document describes a simple mechanism to treat the broadcast network as a point-to-point connection from the standpoint of IP routing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-igp-p2p-over-lan-02.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-igp-p2p-over-lan-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-isis-igp-p2p-over-lan-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2003-3-26123015.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-igp-p2p-over-lan-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-igp-p2p-over-lan-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-3-26123015.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 Fri Mar 28 18:12:27 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24703 for ; Fri, 28 Mar 2003 18:12:27 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SNKbO16959; Fri, 28 Mar 2003 18:20:37 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2SN6oO15221 for ; Fri, 28 Mar 2003 18:06:50 -0500 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22531 for ; Fri, 28 Mar 2003 17:44:20 -0500 (EST) Received: from redback.com (yoo-hoo.redback.com [155.53.12.43]) by prattle.redback.com (Postfix) with ESMTP id 1BC86A5B7C5 for ; Fri, 28 Mar 2003 14:46:42 -0800 (PST) To: isis-wg@ietf.org From: Naiming Shen Message-Id: <20030328224642.1BC86A5B7C5@prattle.redback.com> Subject: [Isis-wg] changes in draft-ietf-isis-wg-multi-topology-06.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: Fri, 28 Mar 2003 14:46:42 -0800 A couple of minor changes made into version 06 of the draft after the LC and a small group discussion include authors, co-chairs and ADs and some vendors. Here is the list: 1) specify the OL bit in lsp header only control the 'normal' or ipv4 unicast topology. 2) specify the route leaking between the levels SHOULD be performed within the same MT. 3) specify a network SHOULD only run either v6 tlv type 236, or with M-ISIS using type 237. thus in one area/domain, we should not mix those together. there are ways to make them co-exist in some special network topology, but we don't think it's worth the effort. basically, we propose a network using ISIS v6 in a area/domain should either run 'normal' ipv6 or run M-ISIS ipv6, but not both at the same time. the M-ISIS compatibility is meant to be compatible with the 'normal' or ipv4 unicast topology. 4) specify in this paragraph: The generic approach of packet to multiple MT RIB mapping over the same inbound interface is outside the scope of this draft. in M-ISIS, multiple topologies can co-exist over the same physical or logical link with the peers. in the case more than one topology belong to the same address family, there needs some mechanism to demux the inbound data packets for different RIB/FIB for route lookups. for example, if those are the QoS topologies, dscp bits of the ip packet may be used to pick the right forwarding table; if its a customer service level related topologies, some packet filters may be used to identify the packets belonging to certain customers/hosts/protocols/applications, thus to pick the correct tables. we are saying that those exact mechanism is outside the scope of this document. 5) fixed some typos. thanks. - Naiming ------- Forwarded Message - --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. Title : M-ISIS: Multi Topology (MT)Routing in IS-IS Author(s) : T. Przygienda, N. Shen, N. Sheth Filename : draft-ietf-isis-wg-multi-topology-06.txt Pages : 11 Date : 2003-3-26 This draft describes an optional mechanism within ISIS used today by many ISPs for IGP routing within their clouds. This draft describes how to run within a single ISIS domain a set of independent IP topologies that we call Multi-Topologies (MTs). This MT extension can be used for variety of purposes such as an in-band management network ``on top'' of the original IGP topology, maintain separate IGP routing domains for isolated multicast or IPv6 islands within the backbone, or force a subset of an address space to follow a different topology. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-multi-topology-06.txt To remove yourself from the IETF Announcement list, send a message to ietf-announce-request with the word unsubscribe in the body of the message. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-isis-wg-multi-topology-06.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-isis-wg-multi-topology-06.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. ------- End of Forwarded Message _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Sat Mar 29 13:29:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26779 for ; Sat, 29 Mar 2003 13:29:52 -0500 (EST) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2TIeUO26173; Sat, 29 Mar 2003 13:40:31 -0500 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h2TIdMO26110 for ; Sat, 29 Mar 2003 13:39:22 -0500 Received: from prattle.redback.com (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26500 for ; Sat, 29 Mar 2003 13:16:26 -0500 (EST) Received: from redback.com (yoo-hoo.redback.com [155.53.12.43]) by prattle.redback.com (Postfix) with ESMTP id ABA15609B76 for ; Sat, 29 Mar 2003 10:18:50 -0800 (PST) To: isis-wg@ietf.org Subject: Re: [Isis-wg] changes in draft-ietf-isis-wg-multi-topology-06.txt In-reply-to: Mail from Naiming Shen dated Fri, 28 Mar 2003 14:46:42 PST <20030328224642.1BC86A5B7C5@prattle.redback.com> From: Naiming Shen Message-Id: <20030329181850.ABA15609B76@prattle.redback.com> Sender: isis-wg-admin@ietf.org Errors-To: isis-wg-admin@ietf.org X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: IETF IS-IS working group List-Post: List-Help: List-Subscribe: , List-Archive: Date: Sat, 29 Mar 2003 10:18:50 -0800 i forgot to mention one more change in this version: 6) made it clear that MT ID#0 can only be used in the MT TLV to announce the router/interface MT membership, it must be ignored if it shows up in the MT IS TLV or MT prefix TLV. this is to make sure the default or ipv4 unicast topology will all have a consistant view of the network. thanks. ] ] ] A couple of minor changes made into version 06 of the draft after ] the LC and a small group discussion include authors, co-chairs and ] ADs and some vendors. Here is the list: ] ] 1) specify the OL bit in lsp header only control the 'normal' or ipv4 ] unicast topology. ] 2) specify the route leaking between the levels SHOULD be performed within ] the same MT. ] 3) specify a network SHOULD only run either v6 tlv type 236, or with ] M-ISIS using type 237. thus in one area/domain, we should not mix ] those together. ] ] there are ways to make them co-exist in some special network topology, ] but we don't think it's worth the effort. basically, we propose a ] network using ISIS v6 in a area/domain should either run 'normal' ] ipv6 or run M-ISIS ipv6, but not both at the same time. ] ] the M-ISIS compatibility is meant to be compatible with the 'normal' ] or ipv4 unicast topology. ] 4) specify in this paragraph: ] ] The generic approach of packet to multiple MT RIB mapping over ] the same inbound interface is outside the scope of this draft. ] ] in M-ISIS, multiple topologies can co-exist over the same physical ] or logical link with the peers. in the case more than one topology ] belong to the same address family, there needs some mechanism to ] demux the inbound data packets for different RIB/FIB for route ] lookups. for example, if those are the QoS topologies, dscp bits ] of the ip packet may be used to pick the right forwarding table; ] if its a customer service level related topologies, some packet ] filters may be used to identify the packets belonging to certain ] customers/hosts/protocols/applications, thus to pick the correct ] tables. we are saying that those exact mechanism is outside the ] scope of this document. ] 5) fixed some typos. ] ] ] thanks. ] - Naiming ] ] ------- Forwarded Message ] ] ] - --NextPart ] ] A New Internet-Draft is available from the on-line Internet-Drafts directori es. ] This draft is a work item of the IS-IS for IP Internets Working Group of the IETF. ] ] Title : M-ISIS: Multi Topology (MT)Routing in IS-IS ] Author(s) : T. Przygienda, N. Shen, N. Sheth ] Filename : draft-ietf-isis-wg-multi-topology-06.txt ] Pages : 11 ] Date : 2003-3-26 ] ] This draft describes an optional mechanism within ISIS used today ] by many ISPs for IGP routing within their clouds. This draft ] describes how to run within a single ISIS domain a set of ] independent IP topologies that we call Multi-Topologies (MTs). ] This MT extension can be used for variety of purposes such as an ] in-band management network ``on top'' of the original IGP topology, ] maintain separate IGP routing domains for isolated multicast or ] IPv6 islands within the backbone, or force a subset of an address ] space to follow a different topology. ] ] A URL for this Internet-Draft is: ] http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-multi-topology-06.txt ] ] To remove yourself from the IETF Announcement list, send a message to ] ietf-announce-request with the word unsubscribe in the body of the message. ] ] Internet-Drafts are also available by anonymous FTP. Login with the username ] "anonymous" and a password of your e-mail address. After logging in, ] type "cd internet-drafts" and then ] "get draft-ietf-isis-wg-multi-topology-06.txt". ] ] A list of Internet-Drafts directories can be found in ] http://www.ietf.org/shadow.html ] or ftp://ftp.ietf.org/ietf/1shadow-sites.txt ] ] ] Internet-Drafts can also be obtained by e-mail. ] ] Send a message to: ] mailserv@ietf.org. ] In the body type: ] "FILE /internet-drafts/draft-ietf-isis-wg-multi-topology-06.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. ] ] ] ------- End of Forwarded Message ] ] _______________________________________________ ] Isis-wg mailing list ] Isis-wg@ietf.org ] https://www1.ietf.org/mailman/listinfo/isis-wg - Naiming _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg