From isis-wg-admin@spider.juniper.net Wed Nov 1 01:10:18 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA18700 for ; Wed, 1 Nov 2000 01:10:17 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id WAA20602; Tue, 31 Oct 2000 22:27:03 -0800 (PST) Received: from red.juniper.net (red.juniper.net [172.17.28.10]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id WAA20590 for ; Tue, 31 Oct 2000 22:26:27 -0800 (PST) Received: from cirrus.juniper.net (cirrus.juniper.net [172.17.20.57]) by red.juniper.net (8.9.3/8.9.3) with ESMTP id WAA07965; Tue, 31 Oct 2000 22:06:18 -0800 (PST) Received: (from dkatz@localhost) by cirrus.juniper.net (8.8.7/8.7.3) id WAA12129; Tue, 31 Oct 2000 22:06:18 -0800 (PST) Message-Id: <200011010606.WAA12129@cirrus.juniper.net> From: Dave Katz To: cmj@3Com.com CC: isis-wg@spider.juniper.net In-reply-to: <3.0.6.32.20001031175035.00942100@mailhost.ewd.3com.com> (message from Cyndi Jung on Tue, 31 Oct 2000 17:50:35 -0800) Subject: Re: [Isis-wg] Choice of encapsulation on ATM Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Tue, 31 Oct 2000 22:06:18 -0800 (PST) We support NLPID and SNAP by configuration. It's got to be the same as the IP encapsulation, of course. Henk's very fine NLPID hack (treating 0x40-0x4f as IP, and 0x83 as ISIS) means that VCMUX could be used as well (taking most of the wind out of the sails of ISIS-over-IP). I suspect that most folks use SNAP encaps as it is the default (and the cell tax has already been paid for the small packets in any case.) X-Sender: cmj@mailhost.ewd.3com.com (Unverified) X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) From: Cyndi Jung Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Tue, 31 Oct 2000 17:50:35 -0800 Hi, We've been brushing off 3Com's old IS-IS implementation, making it support IPv6, and have noticed that it was never (in our system) made to run over ATM, so we're doing that too. The problem is that in RFC1483 it describes two encapsulations for OSI packets over ATM - the LLC encapsulation FE-FE-03 and the NLPID encapsulation, which for IS-IS would simply be the IS-IS frame (NLPID is the first octet, er, byte). So, which of these encapsulations ever got used? I know that CLNP was quite dead by the time everybody was implementing ATM (the reason I don't already know the answer), but IS-IS was certainly used over ATM to support IPv4 routing ala RFC1195. Does anybody out there know? Do we need to do both? Is there any reason one might be preferred? Thanks, Cyndi _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Thu Nov 2 14:11:06 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA21621 for ; Thu, 2 Nov 2000 14:11:06 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA29338; Thu, 2 Nov 2000 11:27:03 -0800 (PST) Received: from presque.djinesys.com ([198.108.6.10]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA28849 for ; Thu, 2 Nov 2000 09:22:35 -0800 (PST) Received: from q.nexthop.com ([141.211.130.163]) by presque.djinesys.com (8.9.3/8.9.3) with ESMTP id LAA07880 for ; Thu, 2 Nov 2000 11:56:32 -0500 (EST) (envelope-from chopps@q.nexthop.com) Received: (from chopps@localhost) by q.nexthop.com (8.11.0/8.11.0) id eA2H2E509771 for isis-wg@spider.juniper.net; Thu, 2 Nov 2000 12:02:14 -0500 (EST) From: "Christian E. Hopps" To: isis-wg@spider.juniper.net Message-ID: <20001102120214.F7048@nexthop.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Subject: [Isis-wg] IPv6 question from last IETF Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Thu, 2 Nov 2000 12:02:14 -0500 Hi, At the previous IETF IS-IS WG meeting someone questioned whether the IPv6 draft was aligned with regard to metric size with the TE draft. I've double checked and it is aligned. The question was regarding wether TE draft specified 24 bit metrics whereas the IPv6 draft specified 32 bit metrics. The confusion arose becuase the TE draft specifies 24 bit metrics for _IS_ reachability (i.e., link advertisements). The IPv6 draft does not define any new TLVs for IS reachability. Both the TE draft and the IPv6 draft specify 32 bit metrics for IP reachability. Thanks, Chris. _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Thu Nov 2 14:46:20 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA01234 for ; Thu, 2 Nov 2000 14:46:18 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA29513; Thu, 2 Nov 2000 12:03:02 -0800 (PST) Received: from lobster.baynetworks.com (ns3.BayNetworks.COM [192.32.253.3]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA29501 for ; Thu, 2 Nov 2000 12:02:22 -0800 (PST) Received: from mailhost.BayNetworks.COM (ns4.baynetworks.com [132.245.135.84]) by lobster.baynetworks.com (8.9.1/8.9.1) with ESMTP id OAA10823; Thu, 2 Nov 2000 14:46:49 -0500 (EST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id OAA17315; Thu, 2 Nov 2000 14:41:54 -0500 (EST) Received: from lead.engeast (lead [192.32.148.52]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with SMTP id OAA22744; Thu, 2 Nov 2000 14:41:54 -0500 for Received: from nortelnetworks.com by lead.engeast (SMI-8.6/SMI-SVR4) id OAA23780; Thu, 2 Nov 2000 14:41:46 -0500 Message-ID: <3A01C379.4553C76B@nortelnetworks.com> From: Rajesh Saluja X-Mailer: Mozilla 4.61 [en] (X11; U; SunOS 5.5.1 sun4u) X-Accept-Language: en MIME-Version: 1.0 To: "Christian E. Hopps" CC: isis-wg@spider.juniper.net Subject: Re: [Isis-wg] IPv6 question from last IETF References: <20001102120214.F7048@nexthop.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Thu, 02 Nov 2000 14:41:46 -0500 Content-Transfer-Encoding: 7bit Hi, I think that you are talking about my question in last IETF. My question was not about the metric size, it was about the type of metric. TE draft eliminates any distinction between internal and external metric type but IPv6 draft IP reachability TLV contains 1 bit to identify external metric type. This is the inconsistency I was pointing. Thanks, Rajesh "Christian E. Hopps" wrote: > Hi, > > At the previous IETF IS-IS WG meeting someone questioned whether > the IPv6 draft was aligned with regard to metric size with the > TE draft. I've double checked and it is aligned. > > The question was regarding wether TE draft specified 24 bit metrics > whereas the IPv6 draft specified 32 bit metrics. The confusion arose > becuase the TE draft specifies 24 bit metrics for _IS_ reachability > (i.e., link advertisements). The IPv6 draft does not define any new > TLVs for IS reachability. Both the TE draft and the IPv6 draft > specify 32 bit metrics for IP reachability. > > Thanks, > Chris. > _______________________________________________ > Isis-wg mailing list - Isis-wg@external.juniper.net > http://external.juniper.net/mailman/listinfo/isis-wg -- ------------------------------------------------------------- Rajesh Saluja Nortel Networks Inc 600 Technology Park Billerica, MA 01821 Ph: (978) 288-7791 Fax: (978) 670-8760 -------------------------------------------------------------- _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Fri Nov 3 14:28:15 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19634 for ; Fri, 3 Nov 2000 14:28:15 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA39145; Fri, 3 Nov 2000 11:43:03 -0800 (PST) Received: from presque.djinesys.com ([198.108.6.10]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id IAA34330 for ; Fri, 3 Nov 2000 08:19:52 -0800 (PST) Received: from q.nexthop.com ([141.211.130.163]) by presque.djinesys.com (8.9.3/8.9.3) with ESMTP id KAA39536; Fri, 3 Nov 2000 10:53:40 -0500 (EST) (envelope-from chopps@q.nexthop.com) Received: (from chopps@localhost) by q.nexthop.com (8.11.0/8.11.0) id eA3FxKL12294; Fri, 3 Nov 2000 10:59:20 -0500 (EST) From: "Christian E. Hopps" To: Rajesh Saluja Cc: isis-wg@spider.juniper.net Subject: Re: [Isis-wg] IPv6 question from last IETF Message-ID: <20001103105920.J7048@nexthop.com> References: <20001102120214.F7048@nexthop.com> <3A01C379.4553C76B@nortelnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <3A01C379.4553C76B@nortelnetworks.com>; from rsaluja@nortelnetworks.com on Thu, Nov 02, 2000 at 02:41:46PM -0500 Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Fri, 3 Nov 2000 10:59:20 -0500 On Thu, Nov 02, 2000 at 02:41:46PM -0500, Rajesh Saluja wrote: > Hi, > I think that you are talking about my question in last IETF. My > question was not about the metric size, it was about the type of metric. > TE draft eliminates any distinction between internal and external metric > type but IPv6 draft IP reachability TLV contains 1 bit to identify > external metric type. This is the inconsistency I was pointing. There were a couple questions. I believe your question was "answered" in the meeting (at least I didn't keep it as an open item to look into). Perhaps you didn't feel the same way :) To avoid confusion I'd like to point out that the IPv6 draft like the TE draft has only one metric type (i.e., there is no external metric). What the IPv6 draft did keep from the original RFC was some indication that the reachability was from another routing protocol. The reachability type does not affect the SPF. Its main use is to avoid redistribution loops (e.g., bgp->isis->bgp). My personal opinion is that the TE draft should have some way of indicating the "externalness" of the reachability. I believe the answer to this opinion in the past was "use a sub-tlv" to color the reachbility. This is a fine solution but seems overly complex for most scenerios. I'm not sure why 2 TLV types weren't used to carry forward the old RFC semantics (I used a bit because I had one available which isn't the case with the TE TLVs). In any case because the IPv6 draft implements sub-tlvs the TE solution of using a color sub-tlv is available, if people decide this is the better route to take. Thanks, Chris. > "Christian E. Hopps" wrote: > > > Hi, > > > > At the previous IETF IS-IS WG meeting someone questioned whether > > the IPv6 draft was aligned with regard to metric size with the > > TE draft. I've double checked and it is aligned. > > > > The question was regarding wether TE draft specified 24 bit metrics > > whereas the IPv6 draft specified 32 bit metrics. The confusion arose > > becuase the TE draft specifies 24 bit metrics for _IS_ reachability > > (i.e., link advertisements). The IPv6 draft does not define any new > > TLVs for IS reachability. Both the TE draft and the IPv6 draft > > specify 32 bit metrics for IP reachability. > > > > Thanks, > > Chris. > > _______________________________________________ > > Isis-wg mailing list - Isis-wg@external.juniper.net > > http://external.juniper.net/mailman/listinfo/isis-wg > > -- > > ------------------------------------------------------------- > Rajesh Saluja > Nortel Networks Inc 600 Technology Park Billerica, MA 01821 > Ph: (978) 288-7791 Fax: (978) 670-8760 > -------------------------------------------------------------- > > > > _______________________________________________ > Isis-wg mailing list - Isis-wg@external.juniper.net > http://external.juniper.net/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Fri Nov 3 17:29:47 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA15495 for ; Fri, 3 Nov 2000 17:29:46 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA39864; Fri, 3 Nov 2000 14:46:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA39852 for ; Fri, 3 Nov 2000 14:45:21 -0800 (PST) Received: from net4u.net4u.ch (net4u.net4u.ch [194.191.0.1]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id OAA22799 for ; Fri, 3 Nov 2000 14:24:52 -0800 (PST) (envelope-from prz@net4u.net4u.ch) Received: (from prz@localhost) by net4u.net4u.ch (8.9.3/8.9.3) id XAA19727; Fri, 3 Nov 2000 23:23:51 +0100 From: Tony Przygienda Message-Id: <200011032223.XAA19727@net4u.net4u.ch> Subject: Re: [Isis-wg] do we need a session this time ? In-Reply-To: <14765.001030@cisco.com> from Alex Zinin at "Oct 30, 2000 6:22:54 pm" To: azinin@cisco.com Cc: prz@net4u.ch, isis-wg@juniper.net X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Fri, 3 Nov 2000 23:23:50 +0100 (MET) Content-Transfer-Encoding: 7bit > We asked to accept the flooding optimization draft > as the WG item. If the answer is positive and there's > enough interest I could present it. Now that you asked often enough, let's make it a work-group item ;-) I would expect the thing to hang in draft until 1) we got some implemenation experience 2) the flooding optimization discussion clicks into place since that can prove to be a subset, incompatible 3) competing proposals show up (if any) and are resolved BTW, requested a slot today & will start to compile agenda one of these days --- tony _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Sat Nov 4 11:54:30 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA05161 for ; Sat, 4 Nov 2000 11:54:29 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA46141; Sat, 4 Nov 2000 09:11:03 -0800 (PST) Received: from miata.procket.com (miata.procket.com [205.253.146.45]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA46129 for ; Sat, 4 Nov 2000 09:10:10 -0800 (PST) Received: from kraak.procket.com (miata.procket.com [10.1.1.1]) by miata.procket.com (8.9.3/8.8.7) with ESMTP id IAA15250; Sat, 4 Nov 2000 08:49:24 -0800 From: Henk Smit X-Confidential: Procket Confidential/Need to know Received: (from henk@localhost) by kraak.procket.com (8.9.3/8.9.3) id RAA26674; Sat, 4 Nov 2000 17:54:31 +0100 Message-Id: <200011041654.RAA26674@kraak.procket.com> Subject: Re: [Isis-wg] IPv6 question from last IETF To: chopps@nexthop.com (Christian E. Hopps) Cc: rsaluja@nortelnetworks.com (Rajesh Saluja), isis-wg@spider.juniper.net In-Reply-To: <20001103105920.J7048@nexthop.com> from "Christian E. Hopps" at Nov 03, 2000 10:59:20 AM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Sat, 4 Nov 2000 17:54:31 +0100 (MET) Content-Transfer-Encoding: 7bit > To avoid confusion I'd like to point out that the IPv6 draft like the > TE draft has only one metric type (i.e., there is no external metric). > What the IPv6 draft did keep from the original RFC was some indication > that the reachability was from another routing protocol. The reachability > type does not affect the SPF. Its main use is to avoid redistribution > loops (e.g., bgp->isis->bgp). And it does a bad job of that. When I used to work in support, I saw that most cases of redistribution were in a scenario where a network operator tried to redistribute multiple islands of routing protocol X into/from a central backbone running protocol Y. Example: an ISIS backbone with multiple RIP worlds around it. Note that there might be more than one redistributing router between the ISIS backbone and a specific RIP domain. In fact,common sense would encourage you to design a network with redundancy. ---rtr1--- central ---rtr3--- RIPv2 world A IS-IS RIPv2 world B ---rtr2--- backbone ---rtr4--- If you use only the route type to decide whether to redistribute or not, you will find out that routes from RIP world A will be marked as external in the IS-IS world, and thus these routes will not be redistributed into RIP world B. The IS-IS backbone needs a way to distinguish between routes originated in world A and in world B. Internal/external route-type is not enough. IMHO if you wanna build something new, better build it good. So lets forget about a half-baked solution like internal/external route-types, and fix this right. > My personal opinion is that the TE draft should have some way of > indicating the "externalness" of the reachability. I believe the > answer to this opinion in the past was "use a sub-tlv" to color > the reachbility. Yes, that is what we have suggested before. > This is a fine solution but seems overly complex > for most scenerios. That depends how more complex you think a bit is versus a byte. :-) All implementation have to deal with sub-TLVs anyway. Even if they don't support any sub-TLVs, they still have to be able to parse them, just so they can ignore them. Adding a sub-TLV should not be too much work. > I'm not sure why 2 TLV types weren't used > to carry forward the old RFC semantics Why waste another TLV for a solution that doesn't solve the problem ? We have only 255 TLVs to spare. > (I used a bit because I had one > available which isn't the case with the TE TLVs). > > In any case because the IPv6 draft implements sub-tlvs the TE solution > of using a color sub-tlv is available, if people decide this is > the better route to take. Using sub-TLVs would be compatible with the traffic-eng extensions draft. Using bits would be more like RFC1195. I would suggest using sub-TLVs, and reserving your bits for more useful use in the future. I am sure people will come up with suggestions later ... Hope this helps, Henk. > Thanks, > Chris. > > > "Christian E. Hopps" wrote: > > > > > Hi, > > > > > > At the previous IETF IS-IS WG meeting someone questioned whether > > > the IPv6 draft was aligned with regard to metric size with the > > > TE draft. I've double checked and it is aligned. > > > > > > The question was regarding wether TE draft specified 24 bit metrics > > > whereas the IPv6 draft specified 32 bit metrics. The confusion arose > > > becuase the TE draft specifies 24 bit metrics for _IS_ reachability > > > (i.e., link advertisements). The IPv6 draft does not define any new > > > TLVs for IS reachability. Both the TE draft and the IPv6 draft > > > specify 32 bit metrics for IP reachability. > > > > > > Thanks, > > > Chris. > > > _______________________________________________ > > > Isis-wg mailing list - Isis-wg@external.juniper.net > > > http://external.juniper.net/mailman/listinfo/isis-wg > > > > -- > > > > ------------------------------------------------------------- > > Rajesh Saluja > > Nortel Networks Inc 600 Technology Park Billerica, MA 01821 > > Ph: (978) 288-7791 Fax: (978) 670-8760 > > -------------------------------------------------------------- > > > > > > > > _______________________________________________ > > Isis-wg mailing list - Isis-wg@external.juniper.net > > http://external.juniper.net/mailman/listinfo/isis-wg > _______________________________________________ > Isis-wg mailing list - Isis-wg@external.juniper.net > http://external.juniper.net/mailman/listinfo/isis-wg > _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Sat Nov 4 15:23:18 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA23214 for ; Sat, 4 Nov 2000 15:23:17 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA47006; Sat, 4 Nov 2000 12:39:02 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA46994 for ; Sat, 4 Nov 2000 12:38:12 -0800 (PST) Received: from ce-nfs-1.cisco.com (ce-nfs-1.cisco.com [171.68.202.251]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id MAA36086 for ; Sat, 4 Nov 2000 12:17:37 -0800 (PST) (envelope-from azinin@cisco.com) Received: from vjorge-dsl1.cisco.com (vjorge-dsl1.cisco.com [10.21.134.162]) by ce-nfs-1.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id MAA08439; Sat, 4 Nov 2000 12:16:59 -0800 (PST) From: Alex Zinin X-Mailer: The Bat! (v1.41) REG'D / CD5BF9353B3B7091 Reply-To: Alex Zinin Organization: Cisco Systems X-Priority: 3 (Normal) Message-ID: <19507.001104@cisco.com> To: Tony Przygienda CC: isis-wg@juniper.net Subject: Re: [Isis-wg] do we need a session this time ? In-reply-To: <200011032223.XAA19727@net4u.net4u.ch> References: <200011032223.XAA19727@net4u.net4u.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Sat, 4 Nov 2000 12:10:36 -0800 Content-Transfer-Encoding: 7bit Tony, >> We asked to accept the flooding optimization draft >> as the WG item. If the answer is positive and there's >> enough interest I could present it. > Now that you asked often enough, let's make it a work-group > item ;-) ;) Great, I will resubmit the draft as such. > I would expect the thing to hang in draft until > 1) we got some implemenation experience Another approach would be to make it experimental to encourage ppl implement it. > 2) the flooding optimization discussion clicks into > place since that can prove to be a subset, incompatible > 3) competing proposals show up (if any) and are resolved Agree. I would suggest setting a deadline for the last 2 items. Alex. > BTW, requested a slot today & will start to compile agenda > one of these days > --- tony _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Sat Nov 4 16:52:53 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA12374 for ; Sat, 4 Nov 2000 16:52:52 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA47374; Sat, 4 Nov 2000 14:08:02 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA47362 for ; Sat, 4 Nov 2000 14:07:15 -0800 (PST) Received: from net4u.net4u.ch (net4u.net4u.ch [194.191.0.1]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id NAA36570 for ; Sat, 4 Nov 2000 13:46:38 -0800 (PST) (envelope-from prz@net4u.net4u.ch) Received: (from prz@localhost) by net4u.net4u.ch (8.9.3/8.9.3) id WAA31784; Sat, 4 Nov 2000 22:40:22 +0100 From: Tony Przygienda Message-Id: <200011042140.WAA31784@net4u.net4u.ch> Subject: Re: [Isis-wg] do we need a session this time ? In-Reply-To: <19507.001104@cisco.com> from Alex Zinin at "Nov 4, 2000 12:10:36 pm" To: azinin@cisco.com Cc: prz@net4u.ch, isis-wg@juniper.net X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Sat, 4 Nov 2000 22:40:22 +0100 (MET) Content-Transfer-Encoding: 7bit > > Tony, > > >> We asked to accept the flooding optimization draft > >> as the WG item. If the answer is positive and there's > >> enough interest I could present it. > > > Now that you asked often enough, let's make it a work-group > > item ;-) > > ;) > Great, I will resubmit the draft as such. > > > I would expect the thing to hang in draft until > > > 1) we got some implemenation experience > > Another approach would be to make it experimental to > encourage ppl implement it. nope, implementation experience first, this is too critical to put it into experimental if it's broken anywhere. You're toying with flooding here and flooding is bastardly hard to get right just "thinking through" stuff. Don't even try for the "it's optional" argument, even optional proposed broken extensions to flooding procedures can cause havoc easily since it just takes one young cookie to implement the stuff withouh questioning the quality of the RFC. > > 2) the flooding optimization discussion clicks into > > place since that can prove to be a subset, incompatible > > 3) competing proposals show up (if any) and are resolved > > Agree. I would suggest setting a deadline for the last 2 items. We're tuned into ongoing discussions on both of the items and Tony & me will decide when these things are in a reasonable shape or fizzled out. no dates ... -- tony _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Sat Nov 4 17:06:11 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA15231 for ; Sat, 4 Nov 2000 17:06:11 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA47463; Sat, 4 Nov 2000 14:21:03 -0800 (PST) Received: from net4u.net4u.ch (net4u.net4u.ch [194.191.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA47451 for ; Sat, 4 Nov 2000 14:20:55 -0800 (PST) Received: (from prz@localhost) by net4u.net4u.ch (8.9.3/8.9.3) id WAA31925; Sat, 4 Nov 2000 22:52:06 +0100 From: Tony Przygienda Message-Id: <200011042152.WAA31925@net4u.net4u.ch> Subject: Re: [Isis-wg] IPv6 question from last IETF In-Reply-To: <200011041654.RAA26674@kraak.procket.com> from Henk Smit at "Nov 4, 2000 5:54:31 pm" To: henk@procket.com (Henk Smit) Cc: chopps@nexthop.com, rsaluja@nortelnetworks.com, isis-wg@spider.juniper.net X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Sat, 4 Nov 2000 22:52:06 +0100 (MET) Content-Transfer-Encoding: 7bit > > > To avoid confusion I'd like to point out that the IPv6 draft like the > > TE draft has only one metric type (i.e., there is no external metric). > > What the IPv6 draft did keep from the original RFC was some indication > > that the reachability was from another routing protocol. The reachability > > type does not affect the SPF. Its main use is to avoid redistribution > > loops (e.g., bgp->isis->bgp). > > And it does a bad job of that. > When I used to work in support, I saw that most cases of redistribution > were in a scenario where a network operator tried to redistribute > multiple islands of routing protocol X into/from a central backbone > running protocol Y. > > Example: an ISIS backbone with multiple RIP worlds around it. > Note that there might be more than one redistributing router between > the ISIS backbone and a specific RIP domain. In fact,common sense > would encourage you to design a network with redundancy. > > ---rtr1--- central ---rtr3--- > RIPv2 world A IS-IS RIPv2 world B > ---rtr2--- backbone ---rtr4--- > > If you use only the route type to decide whether to redistribute > or not, you will find out that routes from RIP world A will be > marked as external in the IS-IS world, and thus these routes > will not be redistributed into RIP world B. The IS-IS backbone > needs a way to distinguish between routes originated in world A > and in world B. Internal/external route-type is not enough. We could tackle that problem of course, but is anyone willing to put in the cycles ? As well, how realistic is the scenario for ISIS ? Customers I know didn't try to do that with ISIS (ISP comments welcome here of course). Complicated IGP mechanisms have been devised (OSPF tags) and ignored and there is a danger that same would happen here. On the other hand, one vendor has route coloring and I heard that people are playing with it ;-)) So what I'm trying to say here I guess is that it would make sense to come up with a proposal for a full solution (route tags, tag sets, colors, whatever else) and in absence of such having external tag on the route is well understood and solves some of the problem so it's better than nothing. -- tony _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Sat Nov 4 19:24:04 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id TAA14637 for ; Sat, 4 Nov 2000 19:24:03 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA48024; Sat, 4 Nov 2000 16:41:03 -0800 (PST) Received: from presque.djinesys.com ([198.108.6.10]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA46305 for ; Sat, 4 Nov 2000 09:49:21 -0800 (PST) Received: from q.nexthop.com ([141.211.130.163]) by presque.djinesys.com (8.9.3/8.9.3) with ESMTP id MAA75472; Sat, 4 Nov 2000 12:22:59 -0500 (EST) (envelope-from chopps@q.nexthop.com) Received: (from chopps@localhost) by q.nexthop.com (8.11.0/8.11.0) id eA4HSjp14775; Sat, 4 Nov 2000 12:28:45 -0500 (EST) From: "Christian E. Hopps" To: Henk Smit Cc: Rajesh Saluja , isis-wg@spider.juniper.net Subject: Re: [Isis-wg] IPv6 question from last IETF Message-ID: <20001104122845.A14473@nexthop.com> References: <20001103105920.J7048@nexthop.com> <200011041654.RAA26674@kraak.procket.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200011041654.RAA26674@kraak.procket.com>; from henk@procket.com on Sat, Nov 04, 2000 at 05:54:31PM +0100 Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Sat, 4 Nov 2000 12:28:45 -0500 On Sat, Nov 04, 2000 at 05:54:31PM +0100, Henk Smit wrote: > > > To avoid confusion I'd like to point out that the IPv6 draft like the > > TE draft has only one metric type (i.e., there is no external metric). > > What the IPv6 draft did keep from the original RFC was some indication > > that the reachability was from another routing protocol. The reachability > > type does not affect the SPF. Its main use is to avoid redistribution > > loops (e.g., bgp->isis->bgp). > > And it does a bad job of that. [... example scenario when a single bit of information is not enough ...] Indeed coloring with a byte is more powerful than with a bit. I'm not sure thats a strong argument against supporting both methods though. The IPv6 draft, while supporting the TE sub-tlv and thus being compatible with that direction of extension of the protocol, is not a TE extension. When I designed it I wished to support the possiblity of a router vendor implementing IPv4 and IPv6 regardless of whether the TE extensions were also implemented. One way I achieved this was by not requiring the sub-tlv be understood (beyond parsing) for proper functioning. This also carries over to deployment, a user familiar with the standard behavoir may not yet be familiar with the proposed sub-tlv coloring scheme, and may have no need to learn it. Given this goal it seemed obvious to me that I should support the full set of features from RFC1195 that were in current use today (i.e., basically everything but external metrics because of "the bug" :), and that this should not require supporting or understanding the new TE extensions. I do think that the sub-tlv for coloring redistributed routes is a good idea, but I am not sure I like the idea of requiring it to support even the non-TE RFC1195 behavoir with IPv6. If indeed this goal is unimportant then we can remove the bit; however, I am not convinced I see the problem in supporting both the old and the new, as yet to be defined, methods. Chris. _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Sun Nov 5 12:29:38 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA13710 for ; Sun, 5 Nov 2000 12:29:38 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA52114; Sun, 5 Nov 2000 09:46:03 -0800 (PST) Received: from miata.procket.com (miata.procket.com [205.253.146.45]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA52102 for ; Sun, 5 Nov 2000 09:45:23 -0800 (PST) Received: from kraak.procket.com (miata.procket.com [10.1.1.1]) by miata.procket.com (8.9.3/8.8.7) with ESMTP id JAA16718; Sun, 5 Nov 2000 09:24:24 -0800 From: Henk Smit X-Confidential: Procket Confidential/Need to know Received: (from henk@localhost) by kraak.procket.com (8.9.3/8.9.3) id SAA32026; Sun, 5 Nov 2000 18:29:17 +0100 Message-Id: <200011051729.SAA32026@kraak.procket.com> Subject: Re: [Isis-wg] IPv6 question from last IETF To: prz@net4u.ch (Tony Przygienda) Cc: henk@procket.com (Henk Smit), chopps@nexthop.com, rsaluja@nortelnetworks.com, isis-wg@spider.juniper.net In-Reply-To: <200011042152.WAA31925@net4u.net4u.ch> from "Tony Przygienda" at Nov 04, 2000 10:52:06 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Sun, 5 Nov 2000 18:29:17 +0100 (MET) Content-Transfer-Encoding: 7bit > > > To avoid confusion I'd like to point out that the IPv6 draft like the > > > TE draft has only one metric type (i.e., there is no external metric). > > > What the IPv6 draft did keep from the original RFC was some indication > > > that the reachability was from another routing protocol. The reachability > > > type does not affect the SPF. Its main use is to avoid redistribution > > > loops (e.g., bgp->isis->bgp). > > > > And it does a bad job of that. > > When I used to work in support, I saw that most cases of redistribution > > were in a scenario where a network operator tried to redistribute > > multiple islands of routing protocol X into/from a central backbone > > running protocol Y. > > > > Example: an ISIS backbone with multiple RIP worlds around it. > > Note that there might be more than one redistributing router between > > the ISIS backbone and a specific RIP domain. In fact,common sense > > would encourage you to design a network with redundancy. > > > > ---rtr1--- central ---rtr3--- > > RIPv2 world A IS-IS RIPv2 world B > > ---rtr2--- backbone ---rtr4--- > > > > If you use only the route type to decide whether to redistribute > > or not, you will find out that routes from RIP world A will be > > marked as external in the IS-IS world, and thus these routes > > will not be redistributed into RIP world B. The IS-IS backbone > > needs a way to distinguish between routes originated in world A > > and in world B. Internal/external route-type is not enough. > > > We could tackle that problem of course, Either you solve the problem (using sub-TLVs to indicate the origine of a prefix) or you don't solve it. Using the binary mechanism from rfc1195 will not solve the problem. So I see no reason to copy that mechanism. > but is anyone willing to put in the cycles ? Route redistribution is not rocket science. Besides that, IMHO most RFC talk about routing inside one IGP domain. There are no standards on how to deal with redistributing between IGPs. And IMHO there is no need for that. Redistrubution is something that is done inside a router, and thus is vendor specific. There must be some regions where vendors can show that they can solve problems without just imlementing what is in the RFCs. :-) The IGP must give a means to carry a tag, that is all. How to deal with it is up to each router vendor. > As well, how realistic is the scenario for ISIS ? Customers I know > didn't try to do that with ISIS (ISP comments welcome here of course). I suspect that those customers you are talking about don't do any redistribution of other IGPs into IS-IS. :-) > So what I'm trying to say here I guess is that it would make sense > to come up with a proposal for a full solution (route tags, tag sets, > colors, whatever else) and in absence of such > having external tag on the route is well understood and solves some of > the problem so it's better than nothing. I disagree here. I rather see a bad solution not implemented at all, in the hope that a good solution will be implemented later. Henk. _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Mon Nov 6 09:55:25 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA15309 for ; Mon, 6 Nov 2000 09:55:24 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA57163; Mon, 6 Nov 2000 07:11:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA57151 for ; Mon, 6 Nov 2000 07:10:14 -0800 (PST) Received: from dfw-smtpout4.email.verio.net (dfw-smtpout4.email.verio.net [129.250.36.44]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id GAA54358 for ; Mon, 6 Nov 2000 06:49:26 -0800 (PST) (envelope-from cwk@verio.net) Received: from [129.250.38.56] (helo=dfw-corpmmp1.email.verio.net) by dfw-smtpout4.email.verio.net with esmtp (Exim 3.12 #7) id 13snaP-0001nG-00; Mon, 06 Nov 2000 14:49:25 +0000 Received: from [206.176.136.115] (helo=cwk) by dfw-corpmmp1.email.verio.net with smtp id 13snaP-0004Lp-00; Mon, 06 Nov 2000 14:49:25 +0000 From: "Carl W. Kalbfleisch" To: "Alex Zinin" , "Tony Przygienda" Cc: Subject: RE: [Isis-wg] do we need a session this time ? Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <19507.001104@cisco.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Mon, 6 Nov 2000 08:52:25 -0600 Content-Transfer-Encoding: 7bit Whatever happened to the ISIS MIB? Carl > -----Original Message----- > From: isis-wg-admin@external.juniper.net > [mailto:isis-wg-admin@external.juniper.net]On Behalf Of Alex Zinin > Sent: Saturday, November 04, 2000 2:11 PM > To: Tony Przygienda > Cc: isis-wg@juniper.net > Subject: Re: [Isis-wg] do we need a session this time ? > > > > Tony, > > >> We asked to accept the flooding optimization draft > >> as the WG item. If the answer is positive and there's > >> enough interest I could present it. > > > Now that you asked often enough, let's make it a work-group > > item ;-) > > ;) > Great, I will resubmit the draft as such. > > > I would expect the thing to hang in draft until > > > 1) we got some implemenation experience > > Another approach would be to make it experimental to > encourage ppl implement it. > > > 2) the flooding optimization discussion clicks into > > place since that can prove to be a subset, incompatible > > 3) competing proposals show up (if any) and are resolved > > Agree. I would suggest setting a deadline for the last 2 items. > > Alex. > > > BTW, requested a slot today & will start to compile agenda > > one of these days > > > --- tony > > > _______________________________________________ > Isis-wg mailing list - Isis-wg@external.juniper.net > http://external.juniper.net/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Mon Nov 6 10:37:49 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA27138 for ; Mon, 6 Nov 2000 10:37:48 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA57387; Mon, 6 Nov 2000 07:54:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA57375 for ; Mon, 6 Nov 2000 07:53:27 -0800 (PST) Received: from bridge.axiowave.com ([209.6.34.2]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id HAA55338 for ; Mon, 6 Nov 2000 07:32:38 -0800 (PST) (envelope-from jparker@axiowave.com) Message-ID: From: Jeff Parker To: "'Carl W. Kalbfleisch'" , Alex Zinin , Tony Przygienda Cc: isis-wg@juniper.net Subject: RE: [Isis-wg] do we need a session this time ? MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Mon, 6 Nov 2000 10:32:24 -0500 Carl - There was a revision before the last IETF, and I sent out a list of "todo" items. I have seen a couple of comments on it since then, but have not rev'd the doc. - jeff parker > -----Original Message----- > From: Carl W. Kalbfleisch [mailto:cwk@verio.net] > Sent: Monday, November 06, 2000 9:52 AM > To: Alex Zinin; Tony Przygienda > Cc: isis-wg@juniper.net > Subject: RE: [Isis-wg] do we need a session this time ? > > Whatever happened to the ISIS MIB? > > Carl _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Mon Nov 6 14:24:38 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA01313 for ; Mon, 6 Nov 2000 14:24:36 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA58272; Mon, 6 Nov 2000 11:41:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA58260 for ; Mon, 6 Nov 2000 11:40:43 -0800 (PST) Received: from ce-nfs-1.cisco.com (ce-nfs-1.cisco.com [171.68.202.251]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id LAA62419 for ; Mon, 6 Nov 2000 11:19:53 -0800 (PST) (envelope-from azinin@cisco.com) Received: from vjorge-dsl1.cisco.com (vjorge-dsl1.cisco.com [10.21.134.162]) by ce-nfs-1.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id LAA24014; Mon, 6 Nov 2000 11:19:14 -0800 (PST) From: Alex Zinin X-Mailer: The Bat! (v1.41) REG'D / CD5BF9353B3B7091 Reply-To: Alex Zinin Organization: Cisco Systems X-Priority: 3 (Normal) Message-ID: <3467.001106@cisco.com> To: Tony Przygienda CC: isis-wg@juniper.net Subject: Re: [Isis-wg] do we need a session this time ? In-reply-To: <200011042140.WAA31784@net4u.net4u.ch> References: <200011042140.WAA31784@net4u.net4u.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Mon, 6 Nov 2000 11:12:43 -0800 Content-Transfer-Encoding: 7bit Tony, OK. Let's start from there. -- Alex Zinin Saturday, November 04, 2000, 1:40 PM, Tony Przygienda wrote: >> >> Tony, >> >> >> We asked to accept the flooding optimization draft >> >> as the WG item. If the answer is positive and there's >> >> enough interest I could present it. >> >> > Now that you asked often enough, let's make it a work-group >> > item ;-) >> >> ;) >> Great, I will resubmit the draft as such. >> >> > I would expect the thing to hang in draft until >> >> > 1) we got some implemenation experience >> >> Another approach would be to make it experimental to >> encourage ppl implement it. > nope, implementation experience first, this is too critical > to put it into experimental if it's broken anywhere. You're > toying with flooding here and flooding is bastardly hard to > get right just "thinking through" stuff. Don't even try for the > "it's optional" argument, even optional proposed broken extensions > to flooding procedures can cause havoc easily since it just takes > one young cookie to implement the stuff withouh questioning > the quality of the RFC. >> > 2) the flooding optimization discussion clicks into >> > place since that can prove to be a subset, incompatible >> > 3) competing proposals show up (if any) and are resolved >> >> Agree. I would suggest setting a deadline for the last 2 items. > We're tuned into ongoing discussions on both of the items and > Tony & me will decide when these things are in a reasonable > shape or fizzled out. no dates ... > -- tony > _______________________________________________ > Isis-wg mailing list - Isis-wg@external.juniper.net > http://external.juniper.net/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Wed Nov 8 06:03:55 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA23522 for ; Wed, 8 Nov 2000 06:03:54 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA67630; Wed, 8 Nov 2000 03:21:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA67618 for ; Wed, 8 Nov 2000 03:20:32 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id CAA08616 for ; Wed, 8 Nov 2000 02:59:31 -0800 (PST) (envelope-from nsyracus@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA21195; Wed, 8 Nov 2000 05:59:27 -0500 (EST) Message-Id: <200011081059.FAA21195@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: mpls@uu.net, te-wg@uu.net, ospf@discuss.microsoft.com, isis-wg@juniper.net From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-dharanikota-interarea-mpls-te-ext-01.txt Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Wed, 08 Nov 2000 05:59:27 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : OSPF, IS-IS, RSVP, CR-LDP Extensions to Support inter-Area Traffic Engineering Using MPLS TE Author(s) : S. Dharanikota, S. Venkatachalam Filename : draft-dharanikota-interarea-mpls-te-ext-01.txt Pages : 20 Date : 07-Nov-00 In this draft, we propose the extensions required to the routing protocols, signaling protocols, and the MIB to support the idea of inter-area LSPs. A companion document [INTER_AREA_FWK] provides the architectural requirements for such a concept. This document also provides the signaling extensions to support the crankback as defined in the architecture document [INTER_AREA_FWK]. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-dharanikota-interarea-mpls-te-ext-01.txt 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-dharanikota-interarea-mpls-te-ext-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-dharanikota-interarea-mpls-te-ext-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: <20001107081312.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-dharanikota-interarea-mpls-te-ext-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-dharanikota-interarea-mpls-te-ext-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001107081312.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Thu Nov 9 06:28:19 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA13717 for ; Thu, 9 Nov 2000 06:28:18 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA73353; Thu, 9 Nov 2000 03:44:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA73341 for ; Thu, 9 Nov 2000 03:43:14 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id DAA35990 for ; Thu, 9 Nov 2000 03:22:05 -0800 (PST) (envelope-from nsyracus@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA11620; Thu, 9 Nov 2000 06:22:04 -0500 (EST) Message-Id: <200011091122.GAA11620@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: isis-wg@juniper.net From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-kini-isis-lsp-restoration-00.txt Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Thu, 09 Nov 2000 06:22:04 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Intermediate System to Intermediate System (IS-IS) protocol extensions for Label Switched Path restoration Author(s) : S. Kini, M. Kodialam, T. Lakshman, C. Villamizar Filename : draft-kini-isis-lsp-restoration-00.txt Pages : 4 Date : 08-Nov-00 Traffic engineering using MPLS involves the setting up of label switched paths (LSP) possibly with explicit routing and with bandwidth guarantees (for label switched paths). The reliability of these LSPs can be increased by providing a backup LSP onto which traffic can be switched upon failure of an element in the path of the active LSP. Backup LSPs can be routed in a way that bandwidth can be shared between backup links of more than one active path while still guaranteeing recoverability for a set of failures. This sharing greatly increases the network efficiency thereby increasing the number of LSPs that can be carried while maintaining guarantees. Algorithms which can route such recoverable LSPs while using only aggregate network usage information are being developed. To route the active LSP and the (possibly shared) backup LSP, the topology information of the network is needed and this can be provided by a link state routing protocol like IS-IS. This document describes the encoding of the additional information within the link state protocol data unit (LSPdu) of IS-IS to enable routing of shared backup paths. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-kini-isis-lsp-restoration-00.txt 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-kini-isis-lsp-restoration-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-kini-isis-lsp-restoration-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: <20001108150709.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-kini-isis-lsp-restoration-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-kini-isis-lsp-restoration-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001108150709.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Fri Nov 10 10:31:12 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA07648 for ; Fri, 10 Nov 2000 10:31:12 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA79929; Fri, 10 Nov 2000 07:46:07 -0800 (PST) Received: from ironbridgenetworks.com (helios.ironbridgenetworks.com [146.115.140.2]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA79917 for ; Fri, 10 Nov 2000 07:45:24 -0800 (PST) Received: from ibnets.com (IDENT:rhan@lampry.ironbridgenetworks.com [192.168.5.169]) by ironbridgenetworks.com (8.9.3/8.9.3) with ESMTP id KAA11912 for ; Fri, 10 Nov 2000 10:24:01 -0500 (EST) Message-ID: <3A0C15A2.2EF31230@ibnets.com> From: Rick Han X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.0.31 i686) X-Accept-Language: en MIME-Version: 1.0 To: isis-wg@spider.juniper.net References: <200011010606.WAA12129@cirrus.juniper.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: [Isis-wg] I/E bit in TLV-135 Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Fri, 10 Nov 2000 15:34:58 +0000 Content-Transfer-Encoding: 7bit Hi, I have a question about TLV-135 (described in draft-ietf-isis-traffic-02.txt). How does TLV-135 indicate the metric type (internal/external)? Is there a bit in the 4-byte metric field reserved for metric-type? Thanks Rick _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Fri Nov 10 14:54:56 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA12666 for ; Fri, 10 Nov 2000 14:54:56 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA81095; Fri, 10 Nov 2000 12:12:04 -0800 (PST) Received: from sj-msg-core-crit.cisco.com (sj-msg-core-crit.cisco.com [171.71.163.10]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id IAA80077 for ; Fri, 10 Nov 2000 08:12:49 -0800 (PST) Received: from brussels.cisco.com (brussels.cisco.com [144.254.15.68]) by sj-msg-core-crit.cisco.com (8.9.3/8.9.1) with ESMTP id HAA21206; Fri, 10 Nov 2000 07:51:31 -0800 (PST) Received: from sprevidi-8kcdt.cisco.com (bru-pegas2-vl34-dhcp22.cisco.com [144.254.13.96]) by brussels.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id QAA10054; Fri, 10 Nov 2000 16:51:29 +0100 (MET) Message-Id: <4.3.2.7.2.20001110163615.00bb7a80@brussels.cisco.com> X-Sender: sprevidi@brussels.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: Rick Han , isis-wg@spider.juniper.net From: stefano previdi Subject: Re: [Isis-wg] I/E bit in TLV-135 In-Reply-To: <3A0C15A2.2EF31230@ibnets.com> References: <200011010606.WAA12129@cirrus.juniper.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Fri, 10 Nov 2000 16:50:05 +0100 At 16:34 10/11/2000, Rick Han wrote: >Hi, I have a question about TLV-135 (described in >draft-ietf-isis-traffic-02.txt). How does TLV-135 indicate the metric >type (internal/external)? it doesn't. If you refer to the use of I/E bit in draft-ietf-isis-domain-wide, keep in mind that we have the up/down bit for that. > Is there a bit in the 4-byte metric field >reserved for metric-type? no. Note that to my knowledge thare are no implementations that really use I/E bit in TLV-128/130. Therefore the interest of having similar bit in TLV-135 was quite limited.... s. _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Wed Nov 15 06:48:33 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA05089 for ; Wed, 15 Nov 2000 06:48:33 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA09030; Wed, 15 Nov 2000 04:05:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA09015 for ; Wed, 15 Nov 2000 04:04:12 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id DAA73846 for ; Wed, 15 Nov 2000 03:42:19 -0800 (PST) (envelope-from nsyracus@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA01901; Wed, 15 Nov 2000 06:42:14 -0500 (EST) Message-Id: <200011151142.GAA01901@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: ospf@discuss.microsoft.com, isis-wg@juniper.net From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-ospf-isis-flood-opt-00.txt Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Wed, 15 Nov 2000 06:42:14 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Open Shortest Path First IGP Working Group of the IETF. Title : Flooding optimizations in link-state routing protocols Author(s) : A. Zinin, M. Shand Filename : draft-ietf-ospf-isis-flood-opt-00.txt Pages : 12 Date : 06-Nov-00 The flooding algorithm is one of the most important parts of any link state routing protocol. It ensures that all routers within a link state domain converge on the same topological information within a finite period of time. To ensure reliability, typical implementations of the flooding algorithm send new information via all interfaces other than the one the new piece of information was received on. This redundancy is necessary to guarantee that flooding is performed reliably, but implies considerable overhead of utilized bandwidth and CPU time if neighboring routers are connected with more than one link. This document describes a method that reduces this overhead. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-ospf-isis-flood-opt-00.txt 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-ospf-isis-flood-opt-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-ospf-isis-flood-opt-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: <20001114065550.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-ospf-isis-flood-opt-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-ospf-isis-flood-opt-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001114065550.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Wed Nov 15 15:59:49 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA20701 for ; Wed, 15 Nov 2000 15:59:47 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA11388; Wed, 15 Nov 2000 13:18:03 -0800 (PST) Received: from ogma.cisco.com (ogma.cisco.com [144.254.74.39]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA11373 for ; Wed, 15 Nov 2000 13:16:59 -0800 (PST) Received: from brussels.cisco.com (brussels.cisco.com [144.254.15.68]) by ogma.cisco.com (Postfix) with ESMTP id 07D41A2; Wed, 15 Nov 2000 21:55:04 +0100 (MET) Received: from sprevidi-8kcdt.cisco.com (sprevidi-isdn-home.cisco.com [10.49.0.58]) by brussels.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id VAA23415; Wed, 15 Nov 2000 21:54:58 +0100 (MET) Message-Id: <4.3.2.7.2.20001115214435.00abe940@brussels.cisco.com> X-Sender: sprevidi@brussels.cisco.com X-Mailer: QUALCOMM Windows Eudora Version 4.3.2 To: vze252px@verizon.net, Rick Han , isis-wg@spider.juniper.net From: stefano previdi Subject: Re: [Isis-wg] I/E bit in TLV-135 In-Reply-To: <5.0.0.25.0.20001113202455.00a1b810@mail.verizon.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Wed, 15 Nov 2000 21:53:33 +0100 At 05:14 14/11/2000, vze252px@verizon.net wrote: >Still don't understand. By reading the draft, up/down bit indicates a route >has traversed from L2 to L1. more precisely it indicates that the prefix went from a upper level to a lower level. > But how a router distinguish internal/external >routes? it doesn't. TLV-135 doesn't have any I/E bit. >If a router leaned both internal and external routes to same >destination with same up/down bit, how does it select one? Just >based on metric? Again: TLV-135 doesn't make any difference between "internal" and "external". s. >Bob > >At 04:50 PM 11/10/2000 +0100, stefano previdi wrote: >At 16:34 10/11/2000, Rick Han wrote: >>Hi, I have a question about TLV-135 (described in >>draft-ietf-isis-traffic-02.txt). How does TLV-135 indicate the metric >>type (internal/external)? > >it doesn't. > >If you refer to the use of I/E bit in draft-ietf-isis-domain-wide, >keep in mind that we have the up/down bit for that. > >> Is there a bit in the 4-byte metric field >>reserved for metric-type? > >no. > >Note that to my knowledge thare are no implementations that really use >I/E bit in TLV-128/130. Therefore the interest of having similar bit >in TLV-135 was quite limited.... > >s. > >_______________________________________________ >Isis-wg mailing list - Isis-wg@external.juniper.net >http://external.juniper.net/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Mon Nov 20 06:17:50 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA05354 for ; Mon, 20 Nov 2000 06:17:50 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA39002; Mon, 20 Nov 2000 03:37:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA38990 for ; Mon, 20 Nov 2000 03:36:48 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id DAA85282 for ; Mon, 20 Nov 2000 03:14:19 -0800 (PST) (envelope-from nsyracus@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA04455; Mon, 20 Nov 2000 06:14:19 -0500 (EST) Message-Id: <200011201114.GAA04455@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; Cc: isis-wg@juniper.net From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-gmpls-extensions-01.txt Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Mon, 20 Nov 2000 06:14: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 : IS-IS Extensions in Support of Generalized MPLS Author(s) : K. Kompella, Y. Rekhter, A. Banerjee, J. Drake, G. Bernstein, D. Fedyk, E. Mannie, D. Saha, V. Sharma Filename : draft-ietf-isis-gmpls-extensions-01.txt Pages : 12 Date : 17-Nov-00 This document specifies extensions to the IS-IS routing protocol in support of Generalized Multi-Protocol Label Switching (previously known as Multi-Protocol Lambda Switching). A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-isis-gmpls-extensions-01.txt 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-gmpls-extensions-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-gmpls-extensions-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: <20001117145203.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-isis-gmpls-extensions-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-isis-gmpls-extensions-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001117145203.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Wed Nov 22 06:16:11 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA21924 for ; Wed, 22 Nov 2000 06:16:11 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA50172; Wed, 22 Nov 2000 03:35:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA50157 for ; Wed, 22 Nov 2000 03:34:08 -0800 (PST) Received: from ietf.org (odin.ietf.org [132.151.1.176]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id DAA46289 for ; Wed, 22 Nov 2000 03:11:26 -0800 (PST) (envelope-from nsyracus@cnri.reston.va.us) Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20837; Wed, 22 Nov 2000 06:11:22 -0500 (EST) Message-Id: <200011221111.GAA20837@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce: ; CC: isis-wg@juniper.net, ospf@discuss.microsoft.com From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: [Isis-wg] I-D ACTION:draft-fedyk-isis-ospf-te-metrics-01.txt Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Wed, 22 Nov 2000 06:11:22 -0500 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Multiple Metrics for Traffic Engineering with IS-IS and OSPF Author(s) : D. Fedyk, A. Ghanwani, R. Balay, J. Ash, A. Vedrenne Filename : draft-fedyk-isis-ospf-te-metrics-01.txt Pages : 8 Date : 21-Nov-00 This draft describes optional sub-TLVs that can be used to extend IGPs to support multiple metrics for use with traffic engineering. These optional extensions are an addendum to the existing work on traffic engineering extensions to OSPF and ISIS. While the current specifications allow advertising only one metric, the ability to advertise multiple metrics has proven to be very useful in similar systems. The encoding for the proposed optional sub-TLVs is also specified. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-fedyk-isis-ospf-te-metrics-01.txt 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-fedyk-isis-ospf-te-metrics-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-fedyk-isis-ospf-te-metrics-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: <20001121111107.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-fedyk-isis-ospf-te-metrics-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-fedyk-isis-ospf-te-metrics-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <20001121111107.I-D@ietf.org> --OtherAccess-- --NextPart-- _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Mon Nov 27 03:11:27 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA18729 for ; Mon, 27 Nov 2000 03:11:26 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA78937; Mon, 27 Nov 2000 00:30:13 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA78922 for ; Mon, 27 Nov 2000 00:29:30 -0800 (PST) Received: from net4u.net4u.ch (net4u.net4u.ch [194.191.0.1]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id AAA11994 for ; Mon, 27 Nov 2000 00:06:12 -0800 (PST) (envelope-from prz@net4u.net4u.ch) Received: (from prz@localhost) by net4u.net4u.ch (8.9.3/8.9.3) id JAA17769 for isis-wg@juniper.net; Mon, 27 Nov 2000 09:03:37 +0100 From: Tony Przygienda Message-Id: <200011270803.JAA17769@net4u.net4u.ch> To: isis-wg@juniper.net X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Compiling ISIS agenda ... Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Mon, 27 Nov 2000 09:03:37 +0100 (MET) Content-Transfer-Encoding: 7bit That's the things I have so far on the agenda. Anyone missing ? Topic Presenter --------------------------------------------------------- Administrativa Tony x Last Call for IPv6 Ballot Deane? Flooding Optimizations Alex Update on Diffserv-MPLS Francois Packet-Design presentation Cengiz I didn't see request for "draft-ietf-isis-gmpls-extensions" ? Anyone else missing ? -- tony _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Mon Nov 27 13:23:48 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA15055 for ; Mon, 27 Nov 2000 13:23:45 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA81552; Mon, 27 Nov 2000 10:43:03 -0800 (PST) Received: from smtp-out1.bellatlantic.net (smtp-out1.bellatlantic.net [199.45.39.156]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id UAA01640 for ; Mon, 13 Nov 2000 20:37:06 -0800 (PST) From: vze252px@verizon.net Received: from bzws401.verizon.net (adsl-151-203-78-93.bostma.adsl.bellatlantic.net [151.203.78.93]) by smtp-out1.bellatlantic.net (8.9.1/8.9.1) with ESMTP id XAA17796; Mon, 13 Nov 2000 23:14:40 -0500 (EST) Message-Id: <5.0.0.25.0.20001113202455.00a1b810@mail.verizon.net> X-Sender: vze252px@verizon.net@mail.verizon.net X-Mailer: QUALCOMM Windows Eudora Version 5.0 To: stefano previdi , Rick Han , isis-wg@spider.juniper.net Subject: Re: [Isis-wg] I/E bit in TLV-135 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Mon, 13 Nov 2000 23:14:46 -0500 Still don't understand. By reading the draft, up/down bit indicates a route has traversed from L2 to L1. But how a router distinguish internal/external routes? If a router leaned both internal and external routes to same destination with same up/down bit, how does it select one? Just based on metric? Bob At 04:50 PM 11/10/2000 +0100, stefano previdi wrote: At 16:34 10/11/2000, Rick Han wrote: >Hi, I have a question about TLV-135 (described in >draft-ietf-isis-traffic-02.txt). How does TLV-135 indicate the metric >type (internal/external)? it doesn't. If you refer to the use of I/E bit in draft-ietf-isis-domain-wide, keep in mind that we have the up/down bit for that. > Is there a bit in the 4-byte metric field >reserved for metric-type? no. Note that to my knowledge thare are no implementations that really use I/E bit in TLV-128/130. Therefore the interest of having similar bit in TLV-135 was quite limited.... s. _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Mon Nov 27 14:08:35 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA01932 for ; Mon, 27 Nov 2000 14:08:33 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA81763; Mon, 27 Nov 2000 11:28:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA81751 for ; Mon, 27 Nov 2000 11:27:40 -0800 (PST) Received: from mailman.packetdesign.com (dns.PACKETDESIGN.NET [216.15.46.10]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id LAA25273 for ; Mon, 27 Nov 2000 11:04:19 -0800 (PST) (envelope-from cengiz@packetdesign.com) Received: from localhost.localdomain.packetdesign.com (main-fw-eth1.packetdesign.com [192.168.0.254]) by mailman.packetdesign.com (8.11.0/8.11.0) with SMTP id eARJ4GQ76995; Mon, 27 Nov 2000 11:04:16 -0800 (PST) (envelope-from cengiz@packetdesign.com) From: Cengiz Alaettinoglu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14882.45057.96900.820250@localhost.localdomain> To: Tony Przygienda Cc: isis-wg@juniper.net Subject: Re: [Isis-wg] Compiling ISIS agenda ... In-Reply-To: <200011270803.JAA17769@net4u.net4u.ch> References: <200011270803.JAA17769@net4u.net4u.ch> X-Mailer: VM 6.72 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid Reply-to: cengiz@packetdesign.com X-Organisation: USC / Information Sciences Institute X-Phone: +1 (310) 448 8219 X-Fax: +1 (310) 823 6714 Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Mon, 27 Nov 2000 11:03:29 -0800 (PST) Content-Transfer-Encoding: 7bit Tony Przygienda (prz@net4u.ch) on November 27: > That's the things I have so far on the agenda. Anyone > missing ? > > Topic Presenter > --------------------------------------------------------- > Administrativa Tony > x Last Call for IPv6 > Ballot Deane? > Flooding Optimizations Alex > Update on Diffserv-MPLS Francois > Packet-Design presentation Cengiz This is a presentation on ISIS convergence. Please see: draft-alaettinoglu-ISIS-convergence-00.ps We are soliciting feedback/comments on this document. see you in San Diego. > > I didn't see request for "draft-ietf-isis-gmpls-extensions" ? > Anyone else missing ? > > -- tony > _______________________________________________ > Isis-wg mailing list - Isis-wg@external.juniper.net > http://external.juniper.net/mailman/listinfo/isis-wg Cengiz -- Cengiz Alaettinoglu Packet Design Inc. _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Tue Nov 28 14:02:02 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA08776 for ; Tue, 28 Nov 2000 14:02:00 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA87347; Tue, 28 Nov 2000 11:19:04 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA87335 for ; Tue, 28 Nov 2000 11:18:27 -0800 (PST) Received: from lobster.baynetworks.com (ns3.BayNetworks.COM [192.32.253.3]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id KAA55119 for ; Tue, 28 Nov 2000 10:54:59 -0800 (PST) (envelope-from dwfedyk@nortelnetworks.com) Received: from mailhost.BayNetworks.COM (ns4.baynetworks.com [132.245.135.84]) by lobster.baynetworks.com (8.9.1/8.9.1) with ESMTP id NAA05338; Tue, 28 Nov 2000 13:59:58 -0500 (EST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id NAA19518; Tue, 28 Nov 2000 13:54:49 -0500 (EST) Received: from dfedyk-new.corpeast.baynetworks.com (dhcp235-110 [192.32.235.110]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with SMTP id NAA23779; Tue, 28 Nov 2000 13:54:48 -0500 for Message-Id: <3.0.1.32.20001128135639.00728c38@pobox.engeast.baynetworks.com> X-Sender: dwfedyk@pobox.engeast.baynetworks.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) To: Tony.Przygienda[prz@net4u.ch]; From: Don Fedyk Cc: isis-wg@juniper.net Mime-Version: 1.0 Content-Type: text/enriched; charset="us-ascii" Subject: [Isis-wg] (no subject) Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Tue, 28 Nov 2000 13:56:39 -0500 Tony We have updated and resubmitted: draft-fedyk-isis-ospf-te-metrics-01.txt 0000,0000,ffff The action items I had was to make sure customers supported this feature for it to become a WG document. I have discussed with a several customers and some are now co-authors. Other than splitting out OSPF I think the document is ready to be a WG document. Can you allocate an appropriate time slot to discuss? Thanks, Don >>>> That's the things I have so far on the agenda. Anyone missing ? Topic Presenter --------------------------------------------------------- Administrativa Tony x Last Call for IPv6 Ballot Deane? Flooding Optimizations Alex Update on Diffserv-MPLS Francois Packet-Design presentation Cengiz I didn't see request for "draft-ietf-isis-gmpls-extensions" ? Anyone else missing ? -- tony _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net 0000,0000,ffffhttp://external.juniper.net/mailman/listinfo/isis-wg 0000,0000,ffff<<<<<<<< _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg From isis-wg-admin@spider.juniper.net Tue Nov 28 14:35:40 2000 Received: from external.juniper.net (spider.juniper.net [207.17.137.40]) by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA18344 for ; Tue, 28 Nov 2000 14:35:38 -0500 (EST) Received: from spider.juniper.net (localhost [127.0.0.1]) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA87538; Tue, 28 Nov 2000 11:55:03 -0800 (PST) Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged)) by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA87523 for ; Tue, 28 Nov 2000 11:54:51 -0800 (PST) Received: from net4u.net4u.ch (net4u.net4u.ch [194.191.0.1]) by colo-rojo.jnpr.net (8.9.3/8.9.3) with ESMTP id LAA56172 for ; Tue, 28 Nov 2000 11:31:23 -0800 (PST) (envelope-from prz@net4u.net4u.ch) Received: (from prz@localhost) by net4u.net4u.ch (8.9.3/8.9.3) id UAA24316 for isis-wg@juniper.net; Tue, 28 Nov 2000 20:28:41 +0100 From: Tony Przygienda Message-Id: <200011281928.UAA24316@net4u.net4u.ch> To: isis-wg@juniper.net X-Mailer: ELM [version 2.4ME+ PL47 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: [Isis-wg] Iteration 2, Agenda Sender: isis-wg-admin@spider.juniper.net Errors-To: isis-wg-admin@spider.juniper.net X-BeenThere: isis-wg@external.juniper.net X-Mailman-Version: 2.0rc1 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: Date: Tue, 28 Nov 2000 20:28:41 +0100 (MET) Content-Transfer-Encoding: 7bit Next iteration: Topic Presenter --------------------------------------------------------- Administrativa Either Tony x Last Call for IPv6 Ballot Deane? draft-dharanikota-interarea-mpls-te-ext-01.txt Sudheer draft-ietf-ospf-isis-flood-opt-00.txt Alex draft-fedyk-isis-ospf-te-metrics-01.txt Don draft-lefaucheur-diff-te-isis-00.txt Francois draft-alaettinoglu-ISIS-convergence-00.ps Cengiz We're getting a bit full so slots will be pretty short. Everybody reads the drafts pls so the amount and cluefullness of questions remains at the usual ISIS working group level ;-) TW, none of the numerous authors of draft-ietf-isis-gmpls-extensions-01.txt asked for a slot. -- tony _______________________________________________ Isis-wg mailing list - Isis-wg@external.juniper.net http://external.juniper.net/mailman/listinfo/isis-wg