From dward@cisco.com Tue May 19 11:21:46 2009 Return-Path: X-Original-To: isis-wg@core3.amsl.com Delivered-To: isis-wg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF8FC28C1B0 for ; Tue, 19 May 2009 11:21:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -6.265 X-Spam-Level: X-Spam-Status: No, score=-6.265 tagged_above=-999 required=5 tests=[AWL=0.334, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EcX-Q+5VtFDP for ; Tue, 19 May 2009 11:21:46 -0700 (PDT) Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id D9B1B3A6927 for ; Tue, 19 May 2009 11:21:45 -0700 (PDT) X-IronPort-AV: E=Sophos;i="4.41,216,1241395200"; d="scan'208";a="44632193" Received: from rtp-dkim-2.cisco.com ([64.102.121.159]) by rtp-iport-2.cisco.com with ESMTP; 19 May 2009 18:23:21 +0000 Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by rtp-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id n4JINLlh011602; Tue, 19 May 2009 14:23:21 -0400 Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.13.8/8.13.8) with ESMTP id n4JINLDX008737; Tue, 19 May 2009 18:23:21 GMT Received: from xmb-rtp-202.amer.cisco.com ([64.102.31.52]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 May 2009 14:23:21 -0400 Received: from [127.0.0.1] ([171.68.225.134]) by xmb-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Tue, 19 May 2009 14:23:20 -0400 Message-Id: <4A4A704A-108A-4BCB-BEAB-5DED300E27A8@cisco.com> From: David Ward To: isis-wg@ietf.org Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Tue, 19 May 2009 13:23:19 -0500 X-Mailer: Apple Mail (2.935.3) X-OriginalArrivalTime: 19 May 2009 18:23:21.0078 (UTC) FILETIME=[E3939960:01C9D8AE] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=285; t=1242757401; x=1243621401; c=relaxed/simple; s=rtpdkim2001; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=dward@cisco.com; z=From:=20David=20Ward=20 |Subject:=20IETF=2075=20call=20for=20agenda=20items |Sender:=20 |To:=20isis-wg@ietf.org; bh=2T8ySkdDHWjtg5Ydb0uW52L+sH3EEiQT3eVR74fygmA=; b=U5qu4I9OsUiUQ9O4T/kwRdVjFx9wx44o9SnniE7XN4VqcWXcBYT5f7ufPl x68KaS3TJ6ypk6x4PprZ9a4rVgOK5s1G3Ruktcb0tmnDu/pw2ZgnpRm9hW8V hnXXYcBPFc; Authentication-Results: rtp-dkim-2; header.From=dward@cisco.com; dkim=pass ( sig from cisco.com/rtpdkim2001 verified; ); Cc: Christian Hopps Subject: [Isis-wg] IETF 75 call for agenda items X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 May 2009 18:21:47 -0000 All - I know it's early but, we are sending this request for agenda items at IETF 75 so we can determine if we are going to have a WG meeting and folks can set travel plans accordingly. Please reply if you would like to request an agenda slot. Thanks -DWard, Chopps From avinash@force10networks.com Fri May 22 22:56:52 2009 Return-Path: X-Original-To: isis-wg@core3.amsl.com Delivered-To: isis-wg@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6359A3A6959 for ; Fri, 22 May 2009 22:56:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.294 X-Spam-Level: X-Spam-Status: No, score=-4.294 tagged_above=-999 required=5 tests=[AWL=-0.110, BAYES_40=-0.185, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wGwvyOLRkYnP for ; Fri, 22 May 2009 22:56:49 -0700 (PDT) Received: from mx.force10networks.com (corp.force10networks.com [64.186.164.204]) by core3.amsl.com (Postfix) with ESMTP id 818D23A67B2 for ; Fri, 22 May 2009 22:56:49 -0700 (PDT) Received: from EXCH-CLUSTER-10.force10networks.com ([10.11.10.130]) by exch7-sjc-fe.force10networks.com ([10.11.0.87]) with mapi; Fri, 22 May 2009 22:58:28 -0700 From: Avinash Natarajan To: "'isis-wg@ietf.org'" Date: Fri, 22 May 2009 22:58:26 -0700 Thread-Topic: Query regarding Forwarding Adjacency (ISIS-TE) Thread-Index: Acnba3ybc5F9i4aeQT2YxTPvVKzcqA== Message-ID: <416CE5A986F9B84788C079EE163B21EA0255D15EF4@EXCH-CLUSTER-10.force10networks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_416CE5A986F9B84788C079EE163B21EA0255D15EF4EXCHCLUSTER10_" MIME-Version: 1.0 Subject: [Isis-wg] Query regarding Forwarding Adjacency (ISIS-TE) X-BeenThere: isis-wg@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IS-IS working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 May 2009 05:56:52 -0000 --_000_416CE5A986F9B84788C079EE163B21EA0255D15EF4EXCHCLUSTER10_ Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi I have a query regarding Forwarding adjacency behavior with ISIS. I have 3 routers as specified below: A <------>B----C A to B and B to A form Bidirectional TE tunnels Tu1 and Tu2 established = using RSVP-TE/ISIS-TE. If I enable 'forwarding-adjacency' on Tu1 and Tu2, A would be added as B= 's Extended IS Neighbor and B as A's Extended IS neighbor (even if there is= a router X, part of the tunnel path between A and B). That part is underst= ood. My query is, additionally, would A install Tu1 in it's routing table, = and B install Tu2 in it's routing table with the tunnel's IGP metric? (akin= to installing them with autoroute metric if autoroute were enabled on the = tunnels..in my use case autoroute is not enabled). Thanks. Regards Avinash --_000_416CE5A986F9B84788C079EE163B21EA0255D15EF4EXCHCLUSTER10_ Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi

=A0=A0=A0 I have a query regarding Forwarding adjacenc= y behavior with ISIS.

=A0=A0=A0 I have 3 routers as specified below:

 

A =DF--=E0B----C

 

=A0=A0 A to B and B to A form Bidirectional TE tunnels= Tu1 and Tu2 established using RSVP-TE/ISIS-TE.

=A0=A0 If I enable ‘forwarding-adjacency’ = on Tu1 and Tu2, A would be added as B’s Extended IS Neighbor and B as A’s Extended IS neighbor (even if there is a router X, part of the tunnel path between A and B). That part is understood. My query is, additionally, would= A install Tu1 in it’s routing table, and B install Tu2 in it’s routing ta= ble with the tunnel’s IGP metric? (akin to installing them with autoroute metric if autoroute were enabled on the tunnels..in my use case autoroute i= s not enabled).

 

=A0=A0=A0 Thanks.

 

Regards

Avinash

--_000_416CE5A986F9B84788C079EE163B21EA0255D15EF4EXCHCLUSTER10_--