From isis-wg-admin@ietf.org Thu Sep 4 10:41:47 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27665 for ; Thu, 4 Sep 2003 10:41:47 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uvHK-0005kK-TY; Thu, 04 Sep 2003 10:40:06 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19uvGR-0005hp-Sb for isis-wg@optimus.ietf.org; Thu, 04 Sep 2003 10:39:11 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27263; Thu, 4 Sep 2003 10:39:03 -0400 (EDT) Message-Id: <200309041439.KAA27263@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: isis-wg@ietf.org, ospf@peach.ease.lsoft.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-bhatia-manral-diff-isis-ospf-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: Thu, 04 Sep 2003 10:39:03 -0400 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : IS-IS and OSPF Difference Discussions Author(s) : V. Manral, M. Bhatia Filename : draft-bhatia-manral-diff-isis-ospf-00.txt Pages : 42 Date : 2003-9-4 The increasing popularity of IS-IS [IS-IS] and OSPF [OSPF] over the years has drawn significant attention to the relative merits and de-merits of one with respect to the other. This draft presents an elaborate comparison between the two routing protocols to explain how the features and functionalities of one differs from the other. Wherever applicable the differences between OSPFv2 and OSPFv3[OSPFv3] have also been pointed out. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-bhatia-manral-diff-isis-ospf-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-bhatia-manral-diff-isis-ospf-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-bhatia-manral-diff-isis-ospf-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-9-4095456.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-bhatia-manral-diff-isis-ospf-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-bhatia-manral-diff-isis-ospf-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-9-4095456.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 Sep 5 13:31:52 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07696 for ; Fri, 5 Sep 2003 13:31: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 19vKQN-0005vJ-HS; Fri, 05 Sep 2003 13:31:07 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19vKPz-0005sX-DL for isis-wg@optimus.ietf.org; Fri, 05 Sep 2003 13:30:43 -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 NAA07581 for ; Fri, 5 Sep 2003 13:30:37 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19vKPx-0003ys-00 for isis-wg@ietf.org; Fri, 05 Sep 2003 13:30:41 -0400 Received: from dmz1.procket.com ([65.174.124.36]) by ietf-mx with esmtp (Exim 4.12) id 19vKPw-0003vP-00 for isis-wg@ietf.org; Fri, 05 Sep 2003 13:30:40 -0400 Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60]) by dmz1.procket.com (Postfix) with ESMTP id 3BAE823C50 for ; Fri, 5 Sep 2003 09:39:31 -0700 (PDT) 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 h85HU5YB018070 for ; Fri, 5 Sep 2003 10:30:05 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6375.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Message-ID: Thread-Topic: Call for topics Thread-Index: AcNz01gBq2+esG/FRLeKhPOukQXsBg== From: "Tony Li" To: Content-Transfer-Encoding: quoted-printable Subject: [Isis-wg] Call for topics 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, 5 Sep 2003 10:30:04 -0700 Content-Transfer-Encoding: quoted-printable Hi all, Yes, it's that time again folks. If you have topics that you'd like to discuss face to face, please send me your suggestions. As always, if there aren't a sufficient number of important topics to warrant a meeting, we won't have one. Regards Tony + Tony _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg From isis-wg-admin@ietf.org Wed Sep 17 09:52:57 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11511 for ; Wed, 17 Sep 2003 09:52:57 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19zciv-0007CU-GB; Wed, 17 Sep 2003 09:52:01 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19zci3-000769-NS for isis-wg@optimus.ietf.org; Wed, 17 Sep 2003 09:51:07 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA11265; Wed, 17 Sep 2003 09:50:58 -0400 (EDT) Message-Id: <200309171350.JAA11265@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-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, 17 Sep 2003 09:50:57 -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 : 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-03.txt Pages : 8 Date : 2003-9-17 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-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-igp-p2p-over-lan-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-igp-p2p-over-lan-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-9-17093216.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-igp-p2p-over-lan-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-igp-p2p-over-lan-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-9-17093216.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 Sep 22 14:46:55 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00026 for ; Mon, 22 Sep 2003 14:46:54 -0400 (EDT) Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1VhC-0006EO-OV; Mon, 22 Sep 2003 14:46:02 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1Vh8-0006DT-Pd for isis-wg@optimus.ietf.org; Mon, 22 Sep 2003 14:45:58 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29882; Mon, 22 Sep 2003 14:45:49 -0400 (EDT) Message-Id: <200309221845.OAA29882@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-ip-interoperable-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: Mon, 22 Sep 2003 14:45:48 -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 : Recommendations for Interoperable IP Networks using IS-IS Author(s) : J. Parker Filename : draft-ietf-isis-ip-interoperable-01.txt Pages : 12 Date : 2003-9-22 This document discusses a number of differences between the 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. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-ip-interoperable-01.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-ip-interoperable-01.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-ip-interoperable-01.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-9-22141342.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-ip-interoperable-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-ip-interoperable-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-9-22141342.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 Sep 22 14:47:28 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00144 for ; Mon, 22 Sep 2003 14:47: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 1A1Vi8-0006aj-QX; Mon, 22 Sep 2003 14:47:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A1VhE-0006Ec-Fr for isis-wg@optimus.ietf.org; Mon, 22 Sep 2003 14:46:04 -0400 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29909; Mon, 22 Sep 2003 14:45:54 -0400 (EDT) Message-Id: <200309221845.OAA29909@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-iso-interoperable-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: Mon, 22 Sep 2003 14:45:54 -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 : Recommendations for Interoperable Networks using IS-IS Author(s) : J. Parker Filename : draft-ietf-isis-iso-interoperable-01.txt Pages : 15 Date : 2003-9-22 This document discusses a number of differences between the IS-IS protocol as described in ISO 10589 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. A companion document discusses differences between the protocol described in RFC 1195 and the protocol as it is deployed today for routing IP traffic. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-iso-interoperable-01.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-iso-interoperable-01.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-iso-interoperable-01.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-9-22141356.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-iso-interoperable-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-iso-interoperable-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2003-9-22141356.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 Sep 24 15:03:38 2003 Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01484 for ; Wed, 24 Sep 2003 15:03: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 1A2Eui-0001EH-Jz; Wed, 24 Sep 2003 15:03:00 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1A2Etl-0001C2-Jy for isis-wg@optimus.ietf.org; Wed, 24 Sep 2003 15:02: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 PAA01414 for ; Wed, 24 Sep 2003 15:01:52 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1A2Eti-00010n-00 for isis-wg@ietf.org; Wed, 24 Sep 2003 15:01:58 -0400 Received: from gwnj8.utstar.com ([65.200.123.8] helo=lxmail.xebeo.com) by ietf-mx with smtp (Exim 4.12) id 1A2Eth-00010W-00 for isis-wg@ietf.org; Wed, 24 Sep 2003 15:01:58 -0400 Received: (qmail 15384 invoked by uid 404); 24 Sep 2003 19:01:27 -0000 Received: from prz@xebeo.com by lxmail by uid 401 with qmail-scanner-1.20rc1 (clamscan: 0.60. spamassassin: 2.55. Clear:RC:1:. Processed in 1.746127 secs); 24 Sep 2003 19:01:27 -0000 Received: from unknown (HELO xebeo.com) (172.16.1.103) by lxmail.nj.us.utstar.com with SMTP; 24 Sep 2003 19:01:26 -0000 Message-ID: <3F71EA01.1070109@xebeo.com> From: Tony Przygienda User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030716 X-Accept-Language: en-us, en MIME-Version: 1.0 To: isis-wg@ietf.org X-Enigmail-Version: 0.75.1.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Meeting Minutes 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, 24 Sep 2003 21:01:21 +0200 Content-Transfer-Encoding: 7bit Thanks to Cengiz -- tony ISIS WG Minutes - Agenda Draft Status Capabilities - Draft Status: Tony P. gave the draft status and summarized the discussion from the mailing list. MIB (12) Ready for Last Call ? Cryptographic Authentication (05) Editors Queue GMPLS Extensions (16) Waiting for AD Comments TE Extensions (04) AD Comments IPv6 (05) Waiting for AD Comments M-ISIS (06) Was discussed again, AD Extended Ether Frame (01) Abandoned Restart (03) LC Passed, Mailing List P2P over LAN (01) External Party 256+ Fragments (02) Editors Queue Automatic Encapsulation (02) Under Discussion Administrative Tags (01) Mailing List, Expired Experimental TLVs (00) Ready for LC now ? Interoperable IP Networks (00) AD Comments Interoperable Networks (00) AD Comments Three-Way Handshake RFC 3373 Published No comments from the audience. - Optional Router Capabilities (Naiming Shen) Follow up to Yokohoma discussion. That document has been split into an OSPF and ISIS only documents. Draft proposes a new TLV to encode a router's capabilities. It is useful to encode this information for troubleshooting, figure out misconfigs and also to signal certain services, path computation server, location, etc. The TLV has its own encoding of the router id. An L1/L2 router verbatim copies these TLV's in its L1 area into its own L2 LSP. The flooding of these TLVs are controlled by using the following bits: F bit: flood to the whole domain T bit: to signal an external application Up/Down bit: to stop looping (see route leaking). The capabilities themselves are encoded as sub-tlv's. Paranta(sp?) from MCI: He is worried that the verbatim copying of these tlv's can spread effect of buggy routers in one L1 area into the whole domain. He would prefer if the L1/L2 router would first interpret these TLV's and later rewrote them, similar to route leaking. Kireetee: He wanted to know how the ambiguity is resolved if two L1/L2 routers were to summarize these TLVs differently. Or if the origin router was to incosistently send multiple of these tlvs. Naiming said you should pick the one you heard last, or you can adopt another scheme which is deterministic (e.g. of closest/farthest router to you based on metric). You can check for errors, length, etc, before making it your own lsp. Kireeti requested to make the length in bytes. Tony P. said 1. we cant do anything about faulty implementations. Tony favors copying verbatim, and thinks it might be buggier if the router regenerated it from what it interpreted. 2. providers have to determine for themselves what to leak and supress. 3. he said the scheme introduces redundancy in a nasty way, if a bit is set, the router has the capability and it is enabled, but there is no gurantee this tlv is heard before another LSP using the capabiltiy. Hence, he is not sure if the capability feature is really useful. As an example he gave: What happens when a router sends you wide metric and not set the corresponding capability bit. An IETFer from Juniper suggested router id to be made in a subtlv so that that subtlv can be used conveniently inside other tlvs in order to reduce number of encoding of the router id. He also said inside the same area this subtlv can be skippped. Stephan: Makes l1/l2 router's lsps big... Dave Ward: no requirement to set bits for your capabilities. the tlv is only adivisory. does the bit show how they are configured or does it actually imply the router is using the capability? (i.e. what is configured and what is actually being done can be different). Tony P: the bit has to be trusted, so it is not truely informational. There was a question of which LSP fragment this tlv should be inside. Naiming, any lsp number. When there is a change, and the tlv can come inside any lsp and the latest lsp always overrides the earlier one. Someone pointed out the tlv is limited to v4 router ids only. Tony gave the group 2 options and asked for show of hands: Options: 1. A per capabiltiy section has to be written, and one other iteration has to be done before becoming a WG document. 2. Make it a WG document now. 6 hands for option 1, 5 hands for option 2. Tony said too close to call and asked to take it to the WG mailing list. Dave Ward suggested an alternative: Lets split the document (and encoding) into two pieces, one for informational pieces and one for hard coded pieces. There was a clear concensus on this split. _______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg