From isis-wg-admin@spider.juniper.net  Thu Nov  1 12:58:21 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25698
	for <isis-archive@odin.ietf.org>; Thu, 1 Nov 2001 12:58:20 -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 KAA11151;
	Thu, 1 Nov 2001 10:13:43 -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 KAA11134
	for <isis-wg@spider.juniper.net>; Thu, 1 Nov 2001 10:12:03 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fA1HsPK67024
	for <isis-wg@juniper.net>; Thu, 1 Nov 2001 09:54:25 -0800 (PST)
X-JNPR-Received-From: outside
Received: from Thor.Adtech-Inc.COM ([63.165.80.10]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 1 Nov 2001 09:52:34 -0800
Received: from apollo.adtech-inc.com (apollo.adtech-inc.com [10.12.0.17])
	by Thor.Adtech-Inc.COM (8.10.2/8.10.2) with ESMTP id fA1HrYR28471
	for <isis-wg@juniper.net>; Thu, 1 Nov 2001 07:53:34 -1000 (HST)
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19)
	id <VWQH3YNP>; Thu, 1 Nov 2001 07:59:07 -1000
Message-ID: <8AC36D3167EED41184C800508BD9540501EE3B69@apollo.adtech-inc.com>
From: "Chan, Chung Ming" <Ming.Chan@spirentcom.com>
To: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 01 Nov 2001 17:52:34.0890 (UTC) FILETIME=[FCB2AAA0:01C162FD]
Subject: [Isis-wg] Simple questions on the use of Authentication TLVs
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 1 Nov 2001 07:59:07 -1000

All,
I'm new to ISIS and hope some one can answer me the following questions
regarding to the use of Authentication TLV.
Thank you in advance!

I'm working with ISO/IEC 10589:1992 and RFC 1195.

In both spec there is Authentication VLF defined with different Code points,
10 for ISO10589 and 133 for RFC1195.

The questions that I've:

1) If the router is supporting RFC 1195, SHALL it use 133 or 10?  What is
the guideline for using it?
2) Or should the router accept code point 10, if it supports RFC1195?


Thanks,


Ming Chan

_______________________________________________
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  1 13:01:50 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25842
	for <isis-archive@odin.ietf.org>; Thu, 1 Nov 2001 13:01: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 KAA11181;
	Thu, 1 Nov 2001 10:16:43 -0800 (PST)
Received: from Thor.Adtech-Inc.COM (Thor.Adtech-Inc.COM [63.165.80.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA11142
	for <isis-wg@spider.juniper.net>; Thu, 1 Nov 2001 10:13:19 -0800 (PST)
Received: from apollo.adtech-inc.com (apollo.adtech-inc.com [10.12.0.17])
	by Thor.Adtech-Inc.COM (8.10.2/8.10.2) with ESMTP id fA1HteR28630
	for <isis-wg@external.juniper.net>; Thu, 1 Nov 2001 07:55:40 -1000 (HST)
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19)
	id <VWQH3YN4>; Thu, 1 Nov 2001 08:01:13 -1000
Message-ID: <8AC36D3167EED41184C800508BD9540501EE3B6A@apollo.adtech-inc.com>
From: "Chan, Chung Ming" <Ming.Chan@SpirentCom.COM>
To: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Cc: "Chan, Chung Ming" <Ming.Chan@SpirentCom.COM>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Isis-wg] Simple questions on the use of Authentication TLVs
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 1 Nov 2001 08:01:13 -1000

All,
I'm new to ISIS and hope some one can answer me the following questions
regarding to the use of Authentication TLV.
Thank you in advance!

I'm working with ISO/IEC 10589:1992 and RFC 1195.

In both spec there is Authentication VLF defined with different Code points,
10 for ISO10589 and 133 for RFC1195.

The questions that I've:

1) If the router is supporting RFC 1195, SHALL it use 133 or 10?  What is
the guideline for using it?
2) Or should the router accept code point 10, if it supports RFC1195?


Thanks,


Ming Chan


_______________________________________________
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  2 12:57:52 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13365
	for <isis-archive@lists.ietf.org>; Fri, 2 Nov 2001 12:57: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 KAA16970;
	Fri, 2 Nov 2001 10:13:42 -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 KAA16958
	for <isis-wg@spider.juniper.net>; Fri, 2 Nov 2001 10:12:52 -0800 (PST)
Received: from pong.juniper.net (pong.juniper.net [207.17.137.102])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fA2Ht6K13426
	for <isis-wg@juniper.net>; Fri, 2 Nov 2001 09:55:07 -0800 (PST)
X-JNPR-Received-From: outside
Received: from [172.16.1.119] ([12.145.55.10]) by pong.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 2 Nov 2001 09:53:55 -0800
Received: from wtn10068 (unverified) by 
 (Content Technologies SMTPRS 4.2.1) with ESMTP id <T56f986b5f3ac1001131e0@> for <isis-wg@juniper.net>;
 Fri, 2 Nov 2001 12:52:22 -0500
Message-Id: <4.2.1.20011102124812.00b0ec80@mail.opnet.com>
X-Sender: azalani@mail.opnet.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 
To: isis-wg@juniper.net
From: Ashish Zalani <azalani@opnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 02 Nov 2001 17:53:55.0936 (UTC) FILETIME=[576B0E00:01C163C7]
Subject: [Isis-wg] Circuit ID field in IS-IS Hello PDUs
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 02 Nov 2001 12:54:55 -0500

Hi,

I am relatively new to IS-IS and am trying to understand how IS-IS PDUs are 
handled. Specifically, I am curious to know how the Circuit ID field in a 
Point-to-Point IIH (or the LAN ID field in a L1/L2 LAN IIH) is assigned.

 From what I understand, the circuit ID is a 1-byte field that uniquely 
identifies the interface on the system. That would allow for a maximum of 
255 interfaces. What happens if the number of (connected) interfaces on a 
router is more than 255? How is the circuit ID ensured to be unique among 
all interfaces?

Thanks,
-Ashish.
Ashish Zalani	
Modeling Engineer
OPNET Technologies, 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  Sun Nov  4 05:06:27 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10762
	for <isis-archive@odin.ietf.org>; Sun, 4 Nov 2001 05:06: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 CAA28311;
	Sun, 4 Nov 2001 02:20:42 -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 CAA28296
	for <isis-wg@spider.juniper.net>; Sun, 4 Nov 2001 02:19:06 -0800 (PST)
Received: from pong.juniper.net (pong.juniper.net [207.17.137.102])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fA4A19K53325
	for <isis-wg@juniper.net>; Sun, 4 Nov 2001 02:01:09 -0800 (PST)
X-JNPR-Received-From: outside
Received: from prattle.redback.com ([155.53.12.9]) by pong.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Sun, 4 Nov 2001 01:59:16 -0800
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 1BAB34BA21E; Sun,  4 Nov 2001 02:00:19 -0800 (PST)
To: Ashish Zalani <azalani@opnet.com>
Cc: isis-wg@juniper.net
Subject: Re: [Isis-wg] Circuit ID field in IS-IS Hello PDUs 
In-reply-to: Mail from Ashish Zalani <azalani@opnet.com> 
 dated Fri, 02 Nov 2001 12:54:55 EST
 <4.2.1.20011102124812.00b0ec80@mail.opnet.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011104100019.1BAB34BA21E@prattle.redback.com>
X-OriginalArrivalTime: 04 Nov 2001 09:59:16.0202 (UTC) FILETIME=[5D0004A0:01C16517]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 04 Nov 2001 02:00:19 -0800


For p2p isis interface, the best algorithm:

circuit_id =
  ( slot_id * 1 + port_id * 2 + channel_id * 3 + dlci_num + vci * vpi +
    vlan_cid * 4 + interface_dwdm_wave_length_in_nm * 5 +
    uniform_distributed_ramdom_number(0, 2**24 - 1) +
    max(1200, seconds_laps_since_January_3_1997) +
    cost_of_router_in_euros ) % 255;

For LAN isis interface, just make sure it's unique and not exceeding 255.
if more than 255 LAN intf on a router is needed, tricky mechanism is required.

thanks.

 ]Hi,
 ]
 ]I am relatively new to IS-IS and am trying to understand how IS-IS PDUs are 
 ]handled. Specifically, I am curious to know how the Circuit ID field in a 
 ]Point-to-Point IIH (or the LAN ID field in a L1/L2 LAN IIH) is assigned.
 ]
 ] From what I understand, the circuit ID is a 1-byte field that uniquely 
 ]identifies the interface on the system. That would allow for a maximum of 
 ]255 interfaces. What happens if the number of (connected) interfaces on a 
 ]router is more than 255? How is the circuit ID ensured to be unique among 
 ]all interfaces?
 ]
 ]Thanks,
 ]-Ashish.
 ]Ashish Zalani	
 ]Modeling Engineer
 ]OPNET Technologies, Inc.
 ]
 ]_______________________________________________
 ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ]http://external.juniper.net/mailman/listinfo/isis-wg

- Naiming
_______________________________________________
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  6 22:10:30 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA09929
	for <isis-archive@lists.ietf.org>; Tue, 6 Nov 2001 22:10: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 TAA43535;
	Tue, 6 Nov 2001 19:25:42 -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 TAA43520
	for <isis-wg@spider.juniper.net>; Tue, 6 Nov 2001 19:24:22 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fA7365K65824
	for <isis-wg@juniper.net>; Tue, 6 Nov 2001 19:06:06 -0800 (PST)
X-JNPR-Received-From: outside
Received: from smtp.huawei.com ([61.144.161.21]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 6 Nov 2001 19:04:28 -0800
Received: from Narendra ([10.110.49.167]) by smtp.huawei.com
          (Netscape Messaging Server 4.15) with ESMTP id GMET2200.R75;
          Wed, 7 Nov 2001 10:46:50 +0800 
Message-ID: <004c01c16736$2faac460$a7316e0a@huawei.com>
Reply-To: "Narendra" <eta_narengh@partner.huawei.com>
From: "Narendra" <eta_narengh@partner.huawei.com>
To: <isis-wg@juniper.net>
Cc: "Narendra" <eta_narengh@partner.huawei.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0049_01C16779.3D9408A0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2615.200
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
X-OriginalArrivalTime: 07 Nov 2001 03:04:28.0312 (UTC) FILETIME=[E9E6A180:01C16738]
Subject: [Isis-wg] Doubts regarding extending LSP fragments beyond 256
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 7 Nov 2001 10:44:56 +0800

This is a multi-part message in MIME format.

------=_NextPart_000_0049_01C16779.3D9408A0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi All,

Can anyone help me in clearing my doubts in =
<draft-hermelin-ext-lsp-frags-02.txt>
 for extending the number of IS-IS LSP fragments beyond 256 limit.
=20
1.While Generating extended LSP, whether to generate extended LSP as =
soon as extended   System-ID is configured or when the Original LSP =
fragments reaches its maximum limit of 256?.

2. Either in operation mode 1 or in operation mode 2, adjacency with =
`Virtual System` will be established only by `Originating System`. is =
this correct?.
if so why it is said in section "forming Adjacencies"  that "if  a =
neighbour is to be included in extended LSP S`, then S`should be used as =
the system-id in IS Hellos and IS-IS Hellos when forming an adjacency =
with that neighbour". Does this mean that the originating
System in Mode 2 will send As many hellos as the number of extended =
System Ids it
uses ?

3. If there is space in Original LSP due to purging of some original LSP =
fragments, then do we need to regenerate both original LSP and extended =
LSP with moving some of LSP`s content from extended LSP to Original LSP.

4. Is it correct that there will be no changes to the PsudonodeLSPs of =
the
originating system as the virtual Systems are assumed to be on P2P =
links?

5. Are there any vendors/ ISIS implementions that  has implemented this =
draft?=20


thanks in advance

Narendra G.H.


------=_NextPart_000_0049_01C16779.3D9408A0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>
<DIV><FONT face=3DArial size=3D2>Hi All,</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial><FONT size=3D2>Can anyone help me =
in&nbsp;clearing&nbsp;my=20
doubts&nbsp;in&nbsp;&lt;draft-hermelin-ext-lsp-frags-02.txt&gt;<BR>&nbsp;=
for=20
<FONT size=3D2>extending the number of IS-IS LSP fragments beyond 256=20
limit.</FONT></FONT></FONT><FONT face=3DArial size=3D2></FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>1.While Generating extended LSP, =
whether to=20
generate extended LSP as soon as extended&nbsp;&nbsp; System-ID is =
configured or=20
when the Original LSP fragments reaches&nbsp;its maximum limit of=20
256?.</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>2. Either in operation mode 1 or in =
operation mode=20
2, adjacency with `Virtual System` will be established only&nbsp;by =
`Originating=20
System`. is this correct?.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>if so why it is said in&nbsp;section =
"forming=20
Adjacencies"&nbsp; that&nbsp;"if&nbsp; a neighbour is to be included in =
extended=20
LSP S`, then S`should be used as the system-id in IS Hellos and IS-IS =
Hellos=20
when forming an adjacency with that neighbour". Does this mean that the=20
originating<BR>System in Mode 2 will send As many hellos as the number =
of=20
extended System Ids it<BR>uses ?<BR></FONT></DIV>
<DIV>
<P><FONT face=3DArial size=3D2>3. If there is space in Original LSP due =
to purging=20
of some original LSP fragments, then do we need to regenerate both =
original LSP=20
and extended LSP with moving some of LSP`s content from extended LSP to =
Original=20
LSP.</FONT></P>
<P>4. Is it correct that there will be no changes to the PsudonodeLSPs =
of=20
the<BR>originating system as the virtual Systems are assumed to be on =
P2P=20
links?</P>
<P>5. Are there any vendors/ ISIS implementions that&nbsp; has =
implemented this=20
draft? </P>
<P><BR><FONT face=3DArial size=3D2>thanks in advance</FONT></P>
<P><FONT face=3DArial size=3D2>Narendra=20
G.H.</FONT></P></DIV></FONT></DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0049_01C16779.3D9408A0--

_______________________________________________
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  8 03:13:41 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20764
	for <isis-archive@odin.ietf.org>; Thu, 8 Nov 2001 03:13:40 -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 AAA50504;
	Thu, 8 Nov 2001 00:29:42 -0800 (PST)
Received: from bart.cwnt.com ([192.116.246.129])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA50492
	for <isis-wg@spider.juniper.net>; Thu, 8 Nov 2001 00:28:12 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: RE: [Isis-wg] Doubts regarding extending LSP fragments beyond 256
Message-ID: <C7DF4400240AFB4095D98C7C6EC2A34A02BE79@bart.cwnt.com>
Thread-Topic: [Isis-wg] Doubts regarding extending LSP fragments beyond 256
Thread-Index: AcFnOsmIJp4kYbhvTmqjqOyJCCHTFwAlCsCgABcL8dA=
From: "Amir Hermelin" <amir@cwnt.com>
To: <eta_narengh@partner.huawei.com>
Cc: "ISIS-wg (E-mail)" <isis-wg@spider.juniper.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by external.juniper.net id AAA50493
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 8 Nov 2001 10:09:45 +0200
Content-Transfer-Encoding: 8bit

Narendra,
my answers inline. Also, a new version of the draft will be published
shortly.

--
Amir Hermelin                    <mailto:amir@cwnt.com>
Charlotte's Web Networks Inc.     <http://www.cwnt.com>


> -----Original Message-----
> From: Narendra [mailto:eta_narengh@partner.huawei.com]
> Sent: Wednesday, November 07, 2001 4:45 AM
> To: isis-wg@juniper.net
> Cc: Narendra
> Subject: [Isis-wg] Doubts regarding extending LSP fragments beyond 256
> 
> 
> Hi All,
> 
> Can anyone help me in clearing my doubts in 
> <draft-hermelin-ext-lsp-frags-02.txt>
>  for extending the number of IS-IS LSP fragments beyond 256 limit.
>  
> 1.While Generating extended LSP, whether to generate extended 
> LSP as soon as extended   System-ID is configured or when the 
> Original LSP fragments reaches its maximum limit of 256?.

IMO this is implementation-specific. While using extended LSPs before
the original LSP space is depleted, could result in cluttering the
network with un-needed 'virtual' systems, a vendor might choose to do
so, to reserve extra space in the original LSPs for whatever reason.
Furthermore, in Mode 2 this doesn't produce any additional overhead,
since the LS information has to be generated anyway.

> 2. Either in operation mode 1 or in operation mode 2, 
> adjacency with `Virtual System` will be established only by 
> `Originating System`. is this correct?.

That is not correct. Here's the text from section 7:
 " It should be noted, that an IS must use the system-id of the LSP that
   will include a neighbor, when forming an adjacency with that
   neighbor.  That is, if a neighbor is to be included in extended LSP
   S', then S' should be used as the system-id in IS Hellos [3] and IS-
   IS Hellos when forming an adjacency with that neighbor.  This is
   regardless of the Operational Mode.  Of course, in Mode 1 this means
   that only the original system-id will be used when sending hellos. "
What you said is correct for mode 1 - since only original LSPs include
ISN TLVs, then only original system-ids will be heard on hellos by the
other neighbors. However, in mode 2 it is possible to include ISNs in
Extended LSPs; say LSPs with Extended system-id S'. Then, this neighbor
must hear S' in the hellos, and not the original system-id (so it
advertises an adjacency to S', and bi-direct check will pass).> if so
why it is said in section "forming Adjacencies"  that 

> "if  a neighbour is to be included in extended LSP S`, then 
> S`should be used as the system-id in IS Hellos and IS-IS 
> Hellos when forming an adjacency with that neighbour". Does 
> this mean that the originating
> System in Mode 2 will send As many hellos as the number of 
> extended System Ids it
> uses ?

This does not affect the number of hellos - only what system-id is
advertised in them.

> 3. If there is space in Original LSP due to purging of some 
> original LSP fragments, then do we need to regenerate both 
> original LSP and extended LSP with moving some of LSP`s 
> content from extended LSP to Original LSP.

If I understand correctly, you're asking about whether to 'compact' the
number of LSP sets in use. I think the same answer to 1 applies here.

> 4. Is it correct that there will be no changes to the 
> PsudonodeLSPs of the
> originating system as the virtual Systems are assumed to be 
> on P2P links?

That depends. If your'e running mode 2, and advertising an extended
system-id on a broadcast network, and you're the DIS on that network,
you can advertise the extended system-id in the pseudonode as well - no
limitation here. What's assumed to be p2p links are the connections
between the original and virtual systems in Mode 1 only - in Mode 2
these connections don't exist (see 4.2 of draft). Besides, there's no
real limitation that the pseudonode and DIS share the same system-id -
it's just a convenience.

> 5. Are there any vendors/ ISIS implementions that  has 
> implemented this draft? 
 
I'm aware of only one.

> thanks in advance

welcome. HTH

> Narendra G.H.
> 
_______________________________________________
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  8 07:33:11 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23505
	for <isis-archive@odin.ietf.org>; Thu, 8 Nov 2001 07:33:10 -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 EAA51731;
	Thu, 8 Nov 2001 04:49:42 -0800 (PST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA51718
	for <isis-wg@spider.juniper.net>; Thu, 8 Nov 2001 04:48:36 -0800 (PST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001307263@fsnt.future.futsoft.com> for <isis-wg@spider.juniper.net>;
 Thu, 08 Nov 2001 18:12:32 +0530
Received: from aridamank (aridamank.future.futsoft.com [10.4.3.11])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id fA8CU3D28578
	for <isis-wg@external.juniper.net>; Thu, 8 Nov 2001 18:00:03 +0530
Reply-To: <aridamank@future.futsoft.com>
From: "Aridaman" <aridamank@future.futsoft.com>
To: <isis-wg@spider.juniper.net>
Message-Id: <000001c16850$6fc776e0$0b03040a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 8 Nov 2001 17:55:20 +0530
Content-Transfer-Encoding: 7bit

hi all,
       Can anyone help me in clearing my doubts in isis draft for ipv6.
1. As we are having different types of adddresses(site local, global...... )
in ipv6. Which address will be advertised in which LSP(L1/L2).
Also Pls tell about any document that elaborate routing for ipv6.
Thanks in advance
ari.




_______________________________________________
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  9 10:58:19 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16490
	for <isis-archive@odin.ietf.org>; Fri, 9 Nov 2001 10:58: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 IAA58364;
	Fri, 9 Nov 2001 08:13:42 -0800 (PST)
Received: from Thor.Adtech-Inc.COM (Thor.Adtech-Inc.COM [63.165.80.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id IAA58352
	for <isis-wg@spider.juniper.net>; Fri, 9 Nov 2001 08:12:28 -0800 (PST)
Received: from apollo.adtech-inc.com (apollo.adtech-inc.com [10.12.0.17])
	by Thor.Adtech-Inc.COM (8.10.2/8.10.2) with ESMTP id fA9Frl404617
	for <isis-wg@external.juniper.net>; Fri, 9 Nov 2001 05:53:48 -1000 (HST)
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19)
	id <VWQHPD54>; Fri, 9 Nov 2001 05:59:23 -1000
Message-ID: <8AC36D3167EED41184C800508BD9540501EE3BA9@apollo.adtech-inc.com>
From: "Chan, Chung Ming" <Ming.Chan@SpirentCom.COM>
To: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Cc: "Chan, Chung Ming" <Ming.Chan@SpirentCom.COM>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Isis-wg] AreaMisMatch Event
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Nov 2001 05:59:22 -1000

Hi,
	I've a question regarding to Area Address mismatch. Hope someone can
clarify that to me.

	According to ISO/IEC 10589, section 8.4.2.2, item a)
	
"If a match is not found between any pair (i.e. the local
and remote system have no area address in common), the
IS shall reject the adjacency"


My understanding of the phase  "reject the adjacency" means:
1) If the IS  is not already have an adjacency with the remote IS, then
don't form any adjacency using the received IIH (Essentially drops/discards
the IIH)
2) If the IS  is already have an adjacency with the remote IS, then the IS
shall "reset the adjacency with the remote IS." (i.e. the IS goes back to
Enabled state, sending IIH without the MAC address of the remote IS).  My
reasoning is that  if the remote IS's area address is changed and there is
not area address in common any more, there is no more reason for keeping the
adjacency.

I know #1 shall be TRUE; but not sure about #2.

Could anyone help to clarify that?



Thanks,



Ming Chan


_______________________________________________
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  9 12:37:17 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA20274
	for <isis-archive@odin.ietf.org>; Fri, 9 Nov 2001 12:37: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 JAA58848;
	Fri, 9 Nov 2001 09:53:42 -0800 (PST)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA58836
	for <isis-wg@spider.juniper.net>; Fri, 9 Nov 2001 09:52:26 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734290122FCE9@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Chan, Chung Ming'" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] AreaMisMatch Event
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Nov 2001 12:33:31 -0500

> 	According to ISO/IEC 10589, section 8.4.2.2, item a)
> 	
> "If a match is not found between any pair (i.e. the local
> and remote system have no area address in common), the
> IS shall reject the adjacency"
> 
> My understanding of the phase  "reject the adjacency" means:
> 1) If the IS  is not already have an adjacency with the 
> remote IS, then don't form any adjacency 
>
> 2) If the IS  is already have an adjacency with the remote 
> IS, then the IS shall "reset the adjacency with the remote 
> IS." 

Spot on.   
_______________________________________________
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  9 12:59:38 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21122
	for <isis-archive@odin.ietf.org>; Fri, 9 Nov 2001 12:59:37 -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 KAA58990;
	Fri, 9 Nov 2001 10:16:42 -0800 (PST)
Received: from viva1.vivacenetworks.com ([64.221.212.135])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA58978
	for <isis-wg@spider.juniper.net>; Fri, 9 Nov 2001 10:15:49 -0800 (PST)
Received: by viva1.vivacenetworks.com with Internet Mail Service (5.5.2653.19)
	id <V661LYF7>; Fri, 9 Nov 2001 09:57:05 -0800
Message-ID: <B7E68CA26CF93846B74B9305EE908AE61058A3@viva1.vivacenetworks.com>
From: Ravindra Sunkad <Ravindra.Sunkad@vivacenetworks.com>
To: "'Chan, Chung Ming'" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] AreaMisMatch Event
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Nov 2001 09:57:04 -0800

Yes. You should delete the adjacency in this case.

Ravi 

-----Original Message-----
From: Chan, Chung Ming [mailto:Ming.Chan@spirentcom.com] 
Sent: Friday, November 09, 2001 7:59 AM
To: 'isis-wg@external.juniper.net'
Cc: Chan, Chung Ming
Subject: [Isis-wg] AreaMisMatch Event


Hi,
	I've a question regarding to Area Address mismatch. Hope someone can
clarify that to me.

	According to ISO/IEC 10589, section 8.4.2.2, item a)
	
"If a match is not found between any pair (i.e. the local
and remote system have no area address in common), the
IS shall reject the adjacency"


My understanding of the phase  "reject the adjacency" means:
1) If the IS  is not already have an adjacency with the remote IS, then
don't form any adjacency using the received IIH (Essentially drops/discards
the IIH)
2) If the IS  is already have an adjacency with the remote IS, then the IS
shall "reset the adjacency with the remote IS." (i.e. the IS goes back to
Enabled state, sending IIH without the MAC address of the remote IS).  My
reasoning is that  if the remote IS's area address is changed and there is
not area address in common any more, there is no more reason for keeping the
adjacency.

I know #1 shall be TRUE; but not sure about #2.

Could anyone help to clarify that?



Thanks,



Ming Chan


_______________________________________________
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  9 13:03:36 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21321
	for <isis-archive@odin.ietf.org>; Fri, 9 Nov 2001 13:03:35 -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 KAA59054;
	Fri, 9 Nov 2001 10:20:44 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA59039
	for <isis-wg@spider.juniper.net>; Fri, 9 Nov 2001 10:19:47 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fA9I0G127019;
	Fri, 9 Nov 2001 13:00:16 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AFI17968;
	Fri, 9 Nov 2001 13:01:09 -0500 (EST)
Message-Id: <4.3.2.7.2.20011109111956.018f3890@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Chan, Chung Ming" <Ming.Chan@spirentcom.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] AreaMisMatch Event
Cc: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>,
        "Chan, Chung Ming" <Ming.Chan@spirentcom.com>
In-Reply-To: <8AC36D3167EED41184C800508BD9540501EE3BA9@apollo.adtech-inc
 .com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 09 Nov 2001 13:00:52 -0500


That would be my interpretation.  If you continue sending IIHs with
your MAC address in it, that would goof up DR election.

The intent is that you would have no L1 adjacency for this system
at all.  (If you're a L2 router, you'd form or retain a L2 adjacency.)

Regards,
Jeff

Disclaimer - I don't work in IS-IS at Cisco, so what I say has
nothing to do with Cisco's implementation.  Opinions expressed
are my own, and may not be those of my employer.  And when I
say something really wrong, Les Guinsberg usually disabuses
everyone ;-)


At 10:59 AM 11/9/2001, Chan, Chung Ming wrote:
>Hi,
>        I've a question regarding to Area Address mismatch. Hope someone can
>clarify that to me.
>
>        According to ISO/IEC 10589, section 8.4.2.2, item a)
>        
>"If a match is not found between any pair (i.e. the local
>and remote system have no area address in common), the
>IS shall reject the adjacency"
>
>
>My understanding of the phase  "reject the adjacency" means:
>1) If the IS  is not already have an adjacency with the remote IS, then
>don't form any adjacency using the received IIH (Essentially drops/discards
>the IIH)
>2) If the IS  is already have an adjacency with the remote IS, then the IS
>shall "reset the adjacency with the remote IS." (i.e. the IS goes back to
>Enabled state, sending IIH without the MAC address of the remote IS).  My
>reasoning is that  if the remote IS's area address is changed and there is
>not area address in common any more, there is no more reason for keeping the
>adjacency.
>
>I know #1 shall be TRUE; but not sure about #2.
>
>Could anyone help to clarify that?
>
>
>
>Thanks,
>
>
>
>Ming Chan
>
>
>_______________________________________________
>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  9 18:33:19 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00384
	for <isis-archive@odin.ietf.org>; Fri, 9 Nov 2001 18:33: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 PAA60454;
	Fri, 9 Nov 2001 15:49:43 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA60441
	for <isis-wg@spider.juniper.net>; Fri, 9 Nov 2001 15:48:13 -0800 (PST)
Received: from redd3174.procket.com (IDENT:root@redd3174.procket.com [10.1.3.174])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fA9NTY8A029498;
	Fri, 9 Nov 2001 15:29:34 -0800 (PST)
From: Henk Smit <henk@Procket.com>
Received: (from henk@localhost)
	by redd3174.procket.com (8.12.1/8.12.1) id fA9NTYQQ024143;
	Fri, 9 Nov 2001 15:29:34 -0800
Message-Id: <200111092329.fA9NTYQQ024143@redd3174.procket.com>
Subject: Re: [Isis-wg] AreaMisMatch Event
To: Ming.Chan@spirentcom.com (Chan, Chung Ming)
Cc: isis-wg@spider.juniper.net
In-Reply-To: <8AC36D3167EED41184C800508BD9540501EE3BA9@apollo.adtech-inc.com> from "Chan, Chung Ming" at Nov 09, 2001 05:59:22 AM
X-Mailer: ELM [version 2.5 PL3]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Nov 2001 15:29:34 -0800 (PST)
Content-Transfer-Encoding: 7bit


  Seems like I am the only one to disagree with the rest. :-)

  I would prefer my code to just ignore the incoming IIH and drop it.
 If the other router was really reconfigured with different area address(es)
 then the next few IIHs will be dropped too, causing the adjacency to time
 out eventually.

  This will take some time. And could be speed up by bringing down the
 adjacency immediately. What do you gain ? If a network admin really
 wants the adjacency to be reset quickly, he can clear it manually after
 the manual area address change.

  The downside of clearing the adjacency is that you are making your
 network less robust.
  Remember that IIHs have no layer3 checksum. So in case you are
 receiving a (partially) corrupted packet, this one corrupted packet
 can take down an adjacency immediately. If you just ignore the packet,
 and it was really an incidental corruption, the adjacency stays up.
  In a previous life I've seen this happen on ATM networks.

        Henk.




> Hi,
> 	I've a question regarding to Area Address mismatch. Hope someone can
> clarify that to me.
> 
> 	According to ISO/IEC 10589, section 8.4.2.2, item a)
> 	
> "If a match is not found between any pair (i.e. the local
> and remote system have no area address in common), the
> IS shall reject the adjacency"
> 
> 
> My understanding of the phase  "reject the adjacency" means:
> 1) If the IS  is not already have an adjacency with the remote IS, then
> don't form any adjacency using the received IIH (Essentially drops/discards
> the IIH)
> 2) If the IS  is already have an adjacency with the remote IS, then the IS
> shall "reset the adjacency with the remote IS." (i.e. the IS goes back to
> Enabled state, sending IIH without the MAC address of the remote IS).  My
> reasoning is that  if the remote IS's area address is changed and there is
> not area address in common any more, there is no more reason for keeping the
> adjacency.
> 
> I know #1 shall be TRUE; but not sure about #2.
> 
> Could anyone help to clarify that?
> 
> 
> 
> Thanks,
> 
> 
> 
> Ming Chan
> 
> 
> _______________________________________________
> 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  9 19:13:41 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01035
	for <isis-archive@odin.ietf.org>; Fri, 9 Nov 2001 19:13:40 -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 QAA60676;
	Fri, 9 Nov 2001 16:30:42 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA60661
	for <isis-wg@spider.juniper.net>; Fri, 9 Nov 2001 16:29:34 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id QAA27497;
	Fri, 9 Nov 2001 16:10:48 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <VMHLDKH3>; Fri, 9 Nov 2001 16:10:48 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F591@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Henk Smit '" <henk@procket.com>,
        "'Ming.Chan@spirentcom.com '"
	 <Ming.Chan@spirentcom.com>
Cc: "'isis-wg@spider.juniper.net '" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] AreaMisMatch Event
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Nov 2001 16:10:44 -0800

 
It is probably also worth mentioning that deliberately configuring routers
on a LAN which operate as L1 routers but are in different areas is a dubious
practice at best. This is the reason the spec calls for an AreaMismatch
event to be generated when such a condition is detected.

Using a LAN as an L2-only backbone - where none of the routers operate as L1
routers on that circuit - makes sense.

Having a mixture of routers, all in the same area, some of which are L2
capable, all connected to the same LAN also makes sense.

The case which sparked the original question, although certainly not unheard
of, should be discouraged.

  Les

-----Original Message-----
From: Henk Smit
To: Ming.Chan@spirentcom.com
Cc: isis-wg@spider.juniper.net
Sent: 11/9/01 3:29 PM
Subject: Re: [Isis-wg] AreaMisMatch Event


  Seems like I am the only one to disagree with the rest. :-)

  I would prefer my code to just ignore the incoming IIH and drop it.
 If the other router was really reconfigured with different area
address(es)
 then the next few IIHs will be dropped too, causing the adjacency to
time
 out eventually.

  This will take some time. And could be speed up by bringing down the
 adjacency immediately. What do you gain ? If a network admin really
 wants the adjacency to be reset quickly, he can clear it manually after
 the manual area address change.

  The downside of clearing the adjacency is that you are making your
 network less robust.
  Remember that IIHs have no layer3 checksum. So in case you are
 receiving a (partially) corrupted packet, this one corrupted packet
 can take down an adjacency immediately. If you just ignore the packet,
 and it was really an incidental corruption, the adjacency stays up.
  In a previous life I've seen this happen on ATM networks.

        Henk.




> Hi,
> 	I've a question regarding to Area Address mismatch. Hope someone
can
> clarify that to me.
> 
> 	According to ISO/IEC 10589, section 8.4.2.2, item a)
> 	
> "If a match is not found between any pair (i.e. the local
> and remote system have no area address in common), the
> IS shall reject the adjacency"
> 
> 
> My understanding of the phase  "reject the adjacency" means:
> 1) If the IS  is not already have an adjacency with the remote IS,
then
> don't form any adjacency using the received IIH (Essentially
drops/discards
> the IIH)
> 2) If the IS  is already have an adjacency with the remote IS, then
the IS
> shall "reset the adjacency with the remote IS." (i.e. the IS goes back
to
> Enabled state, sending IIH without the MAC address of the remote IS).
My
> reasoning is that  if the remote IS's area address is changed and
there is
> not area address in common any more, there is no more reason for
keeping the
> adjacency.
> 
> I know #1 shall be TRUE; but not sure about #2.
> 
> Could anyone help to clarify that?
> 
> 
> 
> Thanks,
> 
> 
> 
> Ming Chan
> 
> 
> _______________________________________________
> 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 10 20:31:40 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA02795
	for <isis-archive@lists.ietf.org>; Sat, 10 Nov 2001 20:31:39 -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 RAA68536;
	Sat, 10 Nov 2001 17:47:43 -0800 (PST)
Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id RAA68524
	for <isis-wg@spider.juniper.net>; Sat, 10 Nov 2001 17:46:45 -0800 (PST)
Received: from bcn.East.Sun.COM ([129.148.75.4])
	by mercury.Sun.COM (8.9.3+Sun/8.9.3) with ESMTP id RAA10709;
	Sat, 10 Nov 2001 17:27:59 -0800 (PST)
Received: from bcn (bcn [129.148.75.4])
	by bcn.East.Sun.COM (8.9.3+Sun/8.9.3/ENSMAIL,v2.1p1) with SMTP id UAA15877;
	Sat, 10 Nov 2001 20:27:59 -0500 (EST)
Message-Id: <200111110127.UAA15877@bcn.East.Sun.COM>
From: Radia Perlman - Boston Center for Networking <Radia.Perlman@Sun.COM>
Reply-To: Radia Perlman - Boston Center for Networking <Radia.Perlman@Sun.COM>
Subject: Re: [Isis-wg] AreaMisMatch Event
To: Ming.Chan@spirentcom.com, henk@procket.com
Cc: isis-wg@spider.juniper.net
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: cciJw5bLpgzwZw8dwfyy7Q==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.3.5 SunOS 5.7 sun4u sparc 
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 10 Nov 2001 20:27:59 -0500 (EST)

I'd agree with Henk. Henks's suggested behavior (throwing away and
perhaps logging the IIH) will eventually bring down the adjacency,
where "eventually" is no longer than it would take to notice a dead
router neighbor.
And the other behavior (bringing it down immediately) would make it
easier, when no authentication is being used...how often is
authentication used these days?...to disrupt a network by sending bogus
packets. Though I could imagine the argument that if someone can
send bogus IS-IS packets and there's no authentication, you're pretty
much gonna lose anyway.

Radia

_______________________________________________
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 12 01:54:45 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA13426
	for <isis-archive@odin.ietf.org>; Mon, 12 Nov 2001 01:54:43 -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 XAA75705;
	Sun, 11 Nov 2001 23:09:44 -0800 (PST)
Received: from hotmail.com (f5.law3.hotmail.com [209.185.241.5])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id XAA75693
	for <isis-wg@external.juniper.net>; Sun, 11 Nov 2001 23:08:29 -0800 (PST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sun, 11 Nov 2001 22:49:35 -0800
Received: from 203.197.188.194 by lw3fd.law3.hotmail.msn.com with HTTP;
	Mon, 12 Nov 2001 06:49:34 GMT
X-Originating-IP: [203.197.188.194]
From: "Sachidananda K" <sachidananda_k@hotmail.com>
To: isis-wg@spider.juniper.net
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F5HQEliT6iBSp6KeCwf00011ed8@hotmail.com>
X-OriginalArrivalTime: 12 Nov 2001 06:49:35.0444 (UTC) FILETIME=[30D82940:01C16B46]
Subject: [Isis-wg] Doubts on SPF execution on DUAL ISIS
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 12 Nov 2001 06:49:34 +0000

Hello,

In a dual ISIS implementation, is it required to execute the SPF algorithm 
twice (once for IP network topology and second for OSI network topolgy)? Or 
should it be executed without taking into consideration the protocol 
supported?

Although, I was told that this is very much specific to implementation, I 
would like to bring out the example and get myself clarified.

This question arised to me basically for the below example.

+--+	2	+--+	3      +--+
|c |------------| b|-----------| a |
+--+		+--+	       +-- +
  \			      /
   \	8		     / 4
    \			    /
   +---+	7	+---+
   | d | ---------------| e |
   +---+		+---+


If IS 'c', 'd', and 'e' are IP enabled and 'b' and 'a' are OSI only. If we 
donot consider the protocol supported then from 'c' to 'e' we have the route 
that doesnot suport IP at all. Therefore, with this for 'c', destination 'e' 
is not reachable in IP topology. Whereas there exists the route via 'd' 
(though expensive).

Please clarify me in this regards.
Thanks in advance.

Sachi.

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

_______________________________________________
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 12 03:51:57 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA23338
	for <isis-archive@odin.ietf.org>; Mon, 12 Nov 2001 03:51:57 -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 BAA76228;
	Mon, 12 Nov 2001 01:08:44 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id BAA76216
	for <isis-wg@spider.juniper.net>; Mon, 12 Nov 2001 01:07:52 -0800 (PST)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp86.cisco.com [10.50.0.85])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id IAA12118;
	Mon, 12 Nov 2001 08:48:45 GMT
Message-Id: <4.3.2.7.2.20011112084716.034d21f8@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Henk Smit <henk@procket.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] AreaMisMatch Event
Cc: Ming.Chan@spirentcom.com (Chan, Chung Ming), isis-wg@spider.juniper.net
In-Reply-To: <200111092329.fA9NTYQQ024143@redd3174.procket.com>
References: <8AC36D3167EED41184C800508BD9540501EE3BA9@apollo.adtech-inc.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 12 Nov 2001 08:48:47 +0000

At 15:29 09/11/2001 -0800, Henk Smit wrote:

>   Seems like I am the only one to disagree with the rest. :-)

Good point Henk, I agree (although I suspect this wasn't what we meant when 
we wrote 10589).

         Mike


>   I would prefer my code to just ignore the incoming IIH and drop it.
>  If the other router was really reconfigured with different area address(es)
>  then the next few IIHs will be dropped too, causing the adjacency to time
>  out eventually.
>
>   This will take some time. And could be speed up by bringing down the
>  adjacency immediately. What do you gain ? If a network admin really
>  wants the adjacency to be reset quickly, he can clear it manually after
>  the manual area address change.
>
>   The downside of clearing the adjacency is that you are making your
>  network less robust.
>   Remember that IIHs have no layer3 checksum. So in case you are
>  receiving a (partially) corrupted packet, this one corrupted packet
>  can take down an adjacency immediately. If you just ignore the packet,
>  and it was really an incidental corruption, the adjacency stays up.
>   In a previous life I've seen this happen on ATM networks.
>
>         Henk.
>
>
>
>
> > Hi,
> >       I've a question regarding to Area Address mismatch. Hope someone can
> > clarify that to me.
> >
> >       According to ISO/IEC 10589, section 8.4.2.2, item a)
> >
> > "If a match is not found between any pair (i.e. the local
> > and remote system have no area address in common), the
> > IS shall reject the adjacency"
> >
> >
> > My understanding of the phase  "reject the adjacency" means:
> > 1) If the IS  is not already have an adjacency with the remote IS, then
> > don't form any adjacency using the received IIH (Essentially drops/discards
> > the IIH)
> > 2) If the IS  is already have an adjacency with the remote IS, then the IS
> > shall "reset the adjacency with the remote IS." (i.e. the IS goes back to
> > Enabled state, sending IIH without the MAC address of the remote IS).  My
> > reasoning is that  if the remote IS's area address is changed and there is
> > not area address in common any more, there is no more reason for 
> keeping the
> > adjacency.
> >
> > I know #1 shall be TRUE; but not sure about #2.
> >
> > Could anyone help to clarify that?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Ming Chan
> >
> >
> > _______________________________________________
> > 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  Mon Nov 12 04:10:28 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23653
	for <isis-archive@odin.ietf.org>; Mon, 12 Nov 2001 04:10:27 -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 BAA76342;
	Mon, 12 Nov 2001 01:27:43 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id BAA76330
	for <isis-wg@spider.juniper.net>; Mon, 12 Nov 2001 01:26:13 -0800 (PST)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 8866E1DCC64; Mon, 12 Nov 2001 01:07:18 -0800 (PST)
To: "Sachidananda K" <sachidananda_k@hotmail.com>
Cc: isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] Doubts on SPF execution on DUAL ISIS 
In-reply-to: Mail from "Sachidananda K" <sachidananda_k@hotmail.com> 
 dated Mon, 12 Nov 2001 06:49:34 GMT
 <F5HQEliT6iBSp6KeCwf00011ed8@hotmail.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011112090718.8866E1DCC64@prattle.redback.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 12 Nov 2001 01:07:18 -0800

 ]Hello,
 ]
 ]In a dual ISIS implementation, is it required to execute the SPF algorithm 
 ]twice (once for IP network topology and second for OSI network topolgy)? Or 
 ]should it be executed without taking into consideration the protocol 
 ]supported?
 ]
 ]Although, I was told that this is very much specific to implementation, I 
 ]would like to bring out the example and get myself clarified.

yes, it's an implementation issue.

but regardless of running spf once or 10 times in this case, the
algorithm should not put an IP-only router onto the TENT while
using an OSI-only router as its nexthop.

also, mix clns and ip like this in the network is asking for trouble.
according to rfc1195, all the links of a router should announce the
identical set of NLPIDs. if not, routing loop may be formed.
a simple example:

                             2(clns)
          1              -------------
  A(ip) ----- B(ip,clns)               C(ip,clns)
  |                      ------------- |
  |                         25(ip)     |
  |                                    |
  +------------------------------------+
             12(ip)

  B has two parallel links to C, one has cost of 2 for clns circuit, the
  other has cost of 25 for ip only circuit.

  To reach C: A knows the cost is 3 (it does not know that link of 2
  is for clns only); B knows its 13. then the routing loop to reach C:

  A -> B -> C
  B -> A -> C

there must be some reason people want to try M-ISIS :-)

- Naiming

 ]
 ]This question arised to me basically for the below example.
 ]
 ]+--+	2	+--+	3      +--+
 ]|c |----------| b|-----------|a |
 ]+--+		+--+	       +--+
 ]  \			      /
 ]   \	8		     / 4
 ]    \			    /
 ]   +---+	7	+---+
 ]   | d | -------------| e |
 ]   +---+		+---+
 ]
 ]
 ]If IS 'c', 'd', and 'e' are IP enabled and 'b' and 'a' are OSI only. If we 
 ]donot consider the protocol supported then from 'c' to 'e' we have the route 
 ]that doesnot suport IP at all. Therefore, with this for 'c', destination 'e' 
 ]is not reachable in IP topology. Whereas there exists the route via 'd' 
 ](though expensive).
 ]
 ]Please clarify me in this regards.
 ]Thanks in advance.
 ]
 ]Sachi.
 ]
_______________________________________________
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 12 10:16:05 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05563
	for <isis-archive@odin.ietf.org>; Mon, 12 Nov 2001 10:16:05 -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 HAA77984;
	Mon, 12 Nov 2001 07:32:43 -0800 (PST)
Received: from bart.cwnt.com ([192.116.246.129])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA77972
	for <isis-wg@spider.juniper.net>; Mon, 12 Nov 2001 07:31:45 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Message-ID: <C7DF4400240AFB4095D98C7C6EC2A34A03C591@bart.cwnt.com>
Thread-Topic: Overload & Attached bits
Thread-Index: AcFrjIIR01Gun9ZqEdWMygDQt44akQ==
From: "Erez Morabia" <erez@cwnt.com>
To: <isis-wg@spider.juniper.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by external.juniper.net id HAA77973
Subject: [Isis-wg] Overload & Attached bits
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 12 Nov 2001 17:12:36 +0200
Content-Transfer-Encoding: 8bit

Hi all,
I have some questions regarding the 'overload bit' and the 'attached
bit' 
and their possible relations.

1. Can a router have both bits set at the same time?

2. Should we consider overloaded routers in our search 
   for the nearest attached level-2 intermediate system? 
   (if we do, we might insert a default route with a next-hop 
    to the overloaded router to the forwarding database...)

3. When we want to check if we are 'attached', we check if we can
   reach at least one intermediate system which resides in
   another area. Should we consider overloaded routers in our
   search?

Thanks,
Erez 


_______________________________________________
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 12 12:48:00 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12870
	for <isis-archive@odin.ietf.org>; Mon, 12 Nov 2001 12:47:58 -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 KAA78625;
	Mon, 12 Nov 2001 10:04:43 -0800 (PST)
Received: from viva1.vivacenetworks.com ([64.221.212.135])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA78613
	for <isis-wg@spider.juniper.net>; Mon, 12 Nov 2001 10:03:08 -0800 (PST)
Received: by viva1.vivacenetworks.com with Internet Mail Service (5.5.2653.19)
	id <V661L8X2>; Mon, 12 Nov 2001 09:44:00 -0800
Message-ID: <B7E68CA26CF93846B74B9305EE908AE61058AD@viva1.vivacenetworks.com>
From: Ravindra Sunkad <Ravindra.Sunkad@vivacenetworks.com>
To: "'Erez Morabia'" <erez@cwnt.com>, isis-wg@spider.juniper.net
Subject: RE: [Isis-wg] Overload & Attached bits
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 12 Nov 2001 09:43:59 -0800



-----Original Message-----
From: Erez Morabia [mailto:erez@cwnt.com] 
Sent: Monday, November 12, 2001 7:13 AM
To: isis-wg@spider.juniper.net
Subject: [Isis-wg] Overload & Attached bits


Hi all,
I have some questions regarding the 'overload bit' and the 'attached bit' 
and their possible relations.

1. Can a router have both bits set at the same time?

Yes. 

2. Should we consider overloaded routers in our search 
   for the nearest attached level-2 intermediate system? 
   (if we do, we might insert a default route with a next-hop 
    to the overloaded router to the forwarding database...)

No. You do not want any traffic (except destined for the local subnets of
the overloaded IS) to be forwarded to the overloaded IS.  

3. When we want to check if we are 'attached', we check if we can
   reach at least one intermediate system which resides in
   another area. Should we consider overloaded routers in our
   search?

I think so. If you don't, the local subnets of the overloaded IS will not be
reachable by networks in other L1 areas.

Thanks,
Erez 


_______________________________________________
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 12 18:03:40 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22322
	for <isis-archive@lists.ietf.org>; Mon, 12 Nov 2001 18:03:39 -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 PAA79924;
	Mon, 12 Nov 2001 15:20:43 -0800 (PST)
Received: from cisco.com (brussels.cisco.com [144.254.15.68])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA79909
	for <isis-wg@spider.juniper.net>; Mon, 12 Nov 2001 15:19:50 -0800 (PST)
Received: from SPREVIDI-W2K.cisco.com (pholland-w2k.cisco.com [128.107.163.43])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id AAA14397;
	Tue, 13 Nov 2001 00:00:41 +0100 (MET)
Message-Id: <4.3.2.7.2.20011112223806.01c36ea8@brussels.cisco.com>
X-Sender: sprevidi@brussels.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Ravindra Sunkad <Ravindra.Sunkad@vivacenetworks.com>
From: stefano previdi <sprevidi@cisco.com>
Subject: RE: [Isis-wg] Overload & Attached bits
Cc: "'Erez Morabia'" <erez@cwnt.com>, isis-wg@spider.juniper.net
In-Reply-To: <B7E68CA26CF93846B74B9305EE908AE61058AD@viva1.vivacenetwork
 s.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 12 Nov 2001 23:50:20 +0100

At 18:43 12/11/2001, Ravindra Sunkad wrote:


>-----Original Message-----
>From: Erez Morabia [mailto:erez@cwnt.com]
>Sent: Monday, November 12, 2001 7:13 AM
>To: isis-wg@spider.juniper.net
>Subject: [Isis-wg] Overload & Attached bits
>
>
>Hi all,
>I have some questions regarding the 'overload bit' and the 'attached bit'
>and their possible relations.
>
>1. Can a router have both bits set at the same time?
>
>Yes.
>
>2. Should we consider overloaded routers in our search
>    for the nearest attached level-2 intermediate system?
>    (if we do, we might insert a default route with a next-hop
>     to the overloaded router to the forwarding database...)
>
>No. You do not want any traffic (except destined for the local subnets of
>the overloaded IS) to be forwarded to the overloaded IS.

In some cases you would prefer not to make such "exception". I
think it depends on the reason why you did set the overload bit:
if the overloaded router is also one of the iBGP next-hops in your
network, you may not want to forward traffic to it....unless the
router is not "overloaded" enough to re-route internet traffic...

Now of course, I'm not sure if a router is ever used as L1L2 _and_
peering point...

s.

>3. When we want to check if we are 'attached', we check if we can
>    reach at least one intermediate system which resides in
>    another area. Should we consider overloaded routers in our
>    search?
>
>I think so. If you don't, the local subnets of the overloaded IS will not be
>reachable by networks in other L1 areas.
>
>Thanks,
>Erez

_______________________________________________
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 13 10:02:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28067
	for <isis-archive@lists.ietf.org>; Tue, 13 Nov 2001 10:02:41 -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 HAA83956;
	Tue, 13 Nov 2001 07:19:44 -0800 (PST)
Received: from bart.cwnt.com ([192.116.246.129])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA83943
	for <isis-wg@spider.juniper.net>; Tue, 13 Nov 2001 07:18:07 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: FW: [Isis-wg] Overload & Attached bits
Message-ID: <C7DF4400240AFB4095D98C7C6EC2A34A0A327E@bart.cwnt.com>
Thread-Topic: [Isis-wg] Overload & Attached bits
Thread-Index: AcFrzd/VwJaQtwPQQC6+M1EsmN0zCAAhCZuQ
From: "Erez Morabia" <erez@cwnt.com>
To: "Ravindra Sunkad" <Ravindra.Sunkad@vivacenetworks.com>,
        <sprevidi@cisco.com>
Cc: <isis-wg@spider.juniper.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by external.juniper.net id HAA83944
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 13 Nov 2001 16:59:02 +0200
Content-Transfer-Encoding: 8bit

Hi,
Thanks for the useful replys.
I added some questions/thoughts inline.

> -----Original Message-----
> From: stefano previdi [mailto:sprevidi@cisco.com]
> Sent: Tuesday, November 13, 2001 12:50 AM
> To: Ravindra Sunkad
> Cc: Erez Morabia; isis-wg@spider.juniper.net
> Subject: RE: [Isis-wg] Overload & Attached bits
> 
> 
> At 18:43 12/11/2001, Ravindra Sunkad wrote:
> 
> 
> >-----Original Message-----
> >From: Erez Morabia [mailto:erez@cwnt.com]
> >Sent: Monday, November 12, 2001 7:13 AM
> >To: isis-wg@spider.juniper.net
> >Subject: [Isis-wg] Overload & Attached bits
> >
> >
> >Hi all,
> >I have some questions regarding the 'overload bit' and the 
> 'attached bit'
> >and their possible relations.
> >
> >1. Can a router have both bits set at the same time?
> >
> >Yes.
> >
> >2. Should we consider overloaded routers in our search
> >    for the nearest attached level-2 intermediate system?
> >    (if we do, we might insert a default route with a next-hop
> >     to the overloaded router to the forwarding database...)
> >
> >No. You do not want any traffic (except destined for the 
> local subnets of
> >the overloaded IS) to be forwarded to the overloaded IS.
> 
> In some cases you would prefer not to make such "exception". I
> think it depends on the reason why you did set the overload bit:
> if the overloaded router is also one of the iBGP next-hops in your
> network, you may not want to forward traffic to it....unless the
> router is not "overloaded" enough to re-route internet traffic...
> 
> Now of course, I'm not sure if a router is ever used as L1L2 _and_
> peering point...
> 
> s.
> 

I agree with Ravindra.

> >3. When we want to check if we are 'attached', we check if we can
> >    reach at least one intermediate system which resides in
> >    another area. Should we consider overloaded routers in our
> >    search?
> >
> >I think so. If you don't, the local subnets of the 
> overloaded IS will not be
> >reachable by networks in other L1 areas.

That's a good argument, but on the other hand, we might
end up with default route towards L1/2 router which can't
really reach another area (except for directly connected info
on the overloaded router).
I hope the following example will clearify this:

 L1RtrA(AreaX)------L1/2RtrB(AreaX)------L2RtrC(AreaY,Overloded)- - -
(AreaY/Backbone) 

 Note: 
  RtrA and RtrB have L1 connection
  RtrB and RtrC have L2 connection

RtrA will insert a default route towards RtrB although RtrB doesn't
really know any
other area because RtrC is overloaded (and shouldn't be used as a
"transient" IS).

A more problematic case can be when we have another "real" attached
router which we
won't choose as our nearest L2 as a result of metric considerations.
example:

 
L1/2RtrB(AreaX)--------L2RtrC(AreaY,Overload)--------1/2RtrD(AreaX)- - -
(L2 backbone)
        |
|
 
+-----------+----------------------------------------------------------+
                     |
                   RtrA(AreaX)

 Note: 
  RtrA and RtrB have L1 connection
  RtrA and RtrD have L1 connection
  RtrB, RtrC and RtrD have L2 connection

Suppose RtrA-RtrB is a low cost connection and RtrA-RtrD is a high cost
connection.
If we consider overloaded routers in our attached algorithm, RtrB will
be considered as
attached.  As a result, RtrA will insert a default route towards RtrB
and this will 
cause a loss of data because RtrC separates RtrB from the backbone.
If we won't consider overloaded routers in our attached algorithm, a
default route will
be inserted towards RtrD...

It seems to me that avoiding the above presented case may be more
important than 
avoiding a situation where local subnets of overloaded IS will not be
reachable by 
networks in other L1 areas.
But I might be wrong... :-)

> >
> >Thanks,
> >Erez
> 
> 

Thanks again,
Erez
_______________________________________________
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 13 10:06:12 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28352
	for <isis-archive@lists.ietf.org>; Tue, 13 Nov 2001 10: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 HAA83907;
	Tue, 13 Nov 2001 07:11:44 -0800 (PST)
Received: from hotmail.com (f76.law3.hotmail.com [209.185.241.76])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA83895
	for <isis-wg@external.juniper.net>; Tue, 13 Nov 2001 07:10:42 -0800 (PST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 13 Nov 2001 06:51:38 -0800
Received: from 202.142.64.180 by lw3fd.law3.hotmail.msn.com with HTTP;
	Tue, 13 Nov 2001 14:51:38 GMT
X-Originating-IP: [202.142.64.180]
From: "Sachidananda K" <sachidananda_k@hotmail.com>
To: isis-wg@spider.juniper.net
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F76hPdHfKsp3MSi6xzm0000d61c@hotmail.com>
X-OriginalArrivalTime: 13 Nov 2001 14:51:38.0830 (UTC) FILETIME=[B2F05EE0:01C16C52]
Subject: [Isis-wg] Partition repair for IP Only ISIS
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 13 Nov 2001 14:51:38 +0000

Hello,

I had some doubts regarding the partition repair. In an IP only ISIS type of 
implementation (according to the RFC 1195) can the partition repair be 
supported.

Please clarify my doubt in this regard.

Thanking you in advance for all the responses.
Sachi

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

_______________________________________________
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 13 17:42:31 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20015
	for <isis-archive@lists.ietf.org>; Tue, 13 Nov 2001 17:42: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 OAA86042;
	Tue, 13 Nov 2001 14:59:43 -0800 (PST)
Received: from viva1.vivacenetworks.com ([64.221.212.135])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA86030
	for <isis-wg@spider.juniper.net>; Tue, 13 Nov 2001 14:58:27 -0800 (PST)
Received: by viva1.vivacenetworks.com with Internet Mail Service (5.5.2653.19)
	id <V661MC7A>; Tue, 13 Nov 2001 14:39:19 -0800
Message-ID: <B7E68CA26CF93846B74B9305EE908AE61058B3@viva1.vivacenetworks.com>
From: Ravindra Sunkad <Ravindra.Sunkad@vivacenetworks.com>
To: "'Erez Morabia'" <erez@cwnt.com>, sprevidi@cisco.com
Cc: isis-wg@spider.juniper.net
Subject: RE: [Isis-wg] Overload & Attached bits
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 13 Nov 2001 14:39:18 -0800

Erez,

My comments are inline.

Ravi

> -----Original Message-----
> From: Erez Morabia [mailto:erez@cwnt.com] 
> Sent: Tuesday, November 13, 2001 6:59 AM
> To: Ravindra Sunkad; sprevidi@cisco.com
> Cc: isis-wg@spider.juniper.net
> Subject: FW: [Isis-wg] Overload & Attached bits
> 
> 
> Hi,
> Thanks for the useful replys.
> I added some questions/thoughts inline.
> 
> > -----Original Message-----
> > From: stefano previdi [mailto:sprevidi@cisco.com]
> > Sent: Tuesday, November 13, 2001 12:50 AM
> > To: Ravindra Sunkad
> > Cc: Erez Morabia; isis-wg@spider.juniper.net
> > Subject: RE: [Isis-wg] Overload & Attached bits
> > 
> > 
> > At 18:43 12/11/2001, Ravindra Sunkad wrote:
> > 
> > 
> > >-----Original Message-----
> > >From: Erez Morabia [mailto:erez@cwnt.com]
> > >Sent: Monday, November 12, 2001 7:13 AM
> > >To: isis-wg@spider.juniper.net
> > >Subject: [Isis-wg] Overload & Attached bits
> > >
> > >
> > >Hi all,
> > >I have some questions regarding the 'overload bit' and the
> > 'attached bit'
> > >and their possible relations.
> > >
> > >1. Can a router have both bits set at the same time?
> > >
> > >Yes.
> > >
> > >2. Should we consider overloaded routers in our search
> > >    for the nearest attached level-2 intermediate system?
> > >    (if we do, we might insert a default route with a next-hop
> > >     to the overloaded router to the forwarding database...)
> > >
> > >No. You do not want any traffic (except destined for the
> > local subnets of
> > >the overloaded IS) to be forwarded to the overloaded IS.
> > 
> > In some cases you would prefer not to make such 
> "exception". I think 
> > it depends on the reason why you did set the overload bit: if the 
> > overloaded router is also one of the iBGP next-hops in your 
> network, 
> > you may not want to forward traffic to it....unless the 
> router is not 
> > "overloaded" enough to re-route internet traffic...
> > 
> > Now of course, I'm not sure if a router is ever used as L1L2 _and_ 
> > peering point...
> > 
> > s.
> > 
> 
> I agree with Ravindra.
> 
> > >3. When we want to check if we are 'attached', we check if we can
> > >    reach at least one intermediate system which resides in
> > >    another area. Should we consider overloaded routers in our
> > >    search?
> > >
> > >I think so. If you don't, the local subnets of the
> > overloaded IS will not be
> > >reachable by networks in other L1 areas.
> 
> That's a good argument, but on the other hand, we might
> end up with default route towards L1/2 router which can't 
> really reach another area (except for directly connected info 
> on the overloaded router). I hope the following example will 
> clearify this:
> 
>  L1RtrA(AreaX)------L1/2RtrB(AreaX)------L2RtrC(AreaY,Overloded)- - -
> (AreaY/Backbone) 
> 
>  Note: 
>   RtrA and RtrB have L1 connection
>   RtrB and RtrC have L2 connection
> 
> RtrA will insert a default route towards RtrB although RtrB 
> doesn't really know any other area because RtrC is overloaded 
> (and shouldn't be used as a "transient" IS).
> 

Since RtrC is overloaded, RtrB will not install routes for networks in L1
areas other than AreaY. So, RtrC will not get transit traffic destined to
networks in other L1 areas.

> A more problematic case can be when we have another "real" 
> attached router which we won't choose as our nearest L2 as a 
> result of metric considerations.
> example:
> 
>  
> L1/2RtrB(AreaX)--------L2RtrC(AreaY,Overload)--------1/2RtrD(A
> reaX)- - - (L2 backbone)
>         |
> |
>  
> +-----------+-------------------------------------------------
> ---------+
>                      |
>                    RtrA(AreaX)
> 
>  Note: 
>   RtrA and RtrB have L1 connection
>   RtrA and RtrD have L1 connection
>   RtrB, RtrC and RtrD have L2 connection
> 
> Suppose RtrA-RtrB is a low cost connection and RtrA-RtrD is a 
> high cost connection. If we consider overloaded routers in 
> our attached algorithm, RtrB will be considered as attached.  
> As a result, RtrA will insert a default route towards RtrB 
> and this will 
> cause a loss of data because RtrC separates RtrB from the 
> backbone. If we won't consider overloaded routers in our 
> attached algorithm, a default route will be inserted towards RtrD...
> 
> It seems to me that avoiding the above presented case may be 
> more important than 
> avoiding a situation where local subnets of overloaded IS 
> will not be reachable by 
> networks in other L1 areas.
> But I might be wrong... :-)
 
This is a trivial case of the overloaded IS creating a disconnected
backbone. If RtrB was also connected to say 
L2RtrE(AreaZ) then RtrB would have been attached but still disconnected from
the rest of the backbone.

> > >
> > >Thanks,
> > >Erez
> > 
> > 
> 
> Thanks again,
> Erez
> 
_______________________________________________
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 14 03:57:24 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16386
	for <isis-archive@odin.ietf.org>; Wed, 14 Nov 2001 03:57: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 BAA88545;
	Wed, 14 Nov 2001 01:13:44 -0800 (PST)
Received: from web21109.mail.yahoo.com (web21109.mail.yahoo.com [216.136.227.111])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id BAA88523
	for <isis-wg@spider.juniper.net>; Wed, 14 Nov 2001 01:12:25 -0800 (PST)
Message-ID: <20011114085317.59801.qmail@web21109.mail.yahoo.com>
Received: from [212.25.110.131] by web21109.mail.yahoo.com via HTTP; Wed, 14 Nov 2001 00:53:17 PST
From: Nagasta Bagamba <nagastabagamba@yahoo.com>
Subject: FW: [Isis-wg] Overload & Attached bits
To: isis-wg@spider.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 14 Nov 2001 00:53:17 -0800 (PST)

Hello Erez and WG,
I want to make some comments about the 2 first issues
you brought up.

1. Can a router have both bits set at the same time?

I understand you agree the answer for that is Yes.
But, I know of at least one major vendor which doesn't
allow to set this 2 bits at the same time. The reason
for that is a kind of a mystery to me...
Does anyone have an idea what the reason for that may
be?

2. Should we consider overloaded routers in our search
for the nearest attached level-2 intermediate system?

You decided that the answer is No. But, I know of at
least 2 major vendors which consider overloaded
routers in the search for the nearest attached level-2
IS.
If vendors-mixture ISIS topology will be built,
routing loops may occure. Does anyone have an idea how
to avoid routing loops in such a topology?

10x,
Nagasta




__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
_______________________________________________
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 14 06:43:19 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17915
	for <isis-archive@odin.ietf.org>; Wed, 14 Nov 2001 06:43:19 -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 EAA89438;
	Wed, 14 Nov 2001 04:00:44 -0800 (PST)
Received: from hotmail.com (f25.law3.hotmail.com [209.185.241.25])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA89420
	for <isis-wg@external.juniper.net>; Wed, 14 Nov 2001 03:59:19 -0800 (PST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 14 Nov 2001 03:40:09 -0800
Received: from 202.142.64.180 by lw3fd.law3.hotmail.msn.com with HTTP;
	Wed, 14 Nov 2001 11:40:09 GMT
X-Originating-IP: [202.142.64.180]
From: "Sachidananda K" <sachidananda_k@hotmail.com>
To: isis-wg@spider.juniper.net
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F25HXwj8eTL2ZvbddIJ0000583f@hotmail.com>
X-OriginalArrivalTime: 14 Nov 2001 11:40:09.0910 (UTC) FILETIME=[1D6C0D60:01C16D01]
Subject: [Isis-wg] interaction with other IGP
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 14 Nov 2001 11:40:09 +0000

Hello,

I'm not very familiar with ISIS. I have some doubts on dual ISIS.
If an intermediate system running other IGP (like ISOF, RIP) along with 
ISIS, receive a new route from the other routing protocols, then how do we 
advertise this routes to adjacent ISIS system.
Do we advertise them at all or not?
If we do how frequently and how?

Please clarify my doubts.

Thanking you in advance for all responses.
Sachi.

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

_______________________________________________
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 14 08:39:46 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA22013
	for <isis-archive@odin.ietf.org>; Wed, 14 Nov 2001 08:39: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 FAA89943;
	Wed, 14 Nov 2001 05:54:43 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id FAA89931
	for <isis-wg@spider.juniper.net>; Wed, 14 Nov 2001 05:53:43 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fAEDXa116761;
	Wed, 14 Nov 2001 08:33:36 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (sjc-vpn2-358.cisco.com [10.21.113.102])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AFI92905;
	Wed, 14 Nov 2001 08:34:31 -0500 (EST)
Message-Id: <4.3.2.7.2.20011114082801.018d5ea8@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Sachidananda K" <sachidananda_k@hotmail.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] interaction with other IGP
Cc: isis-wg@spider.juniper.net
In-Reply-To: <F25HXwj8eTL2ZvbddIJ0000583f@hotmail.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 14 Nov 2001 08:31:41 -0500


There may be practical answers that contradict this, but the
academic answer is that you use only one routing protocol as
your IGP in a routing domain.  That's part of what makes it
a routing domain -- consistent routing policy & protocol.

There are likely to be a lot of exceptions that will work,
especially stub networks.  I would be very hesitant to use
any other IGP to represent a transit subnetwork (a path between
two parts of the area/domain that use IS-IS).

Regards,
Jeff

At 06:40 AM 11/14/2001, Sachidananda K wrote:
>Hello,
>
>I'm not very familiar with ISIS. I have some doubts on dual ISIS.
>If an intermediate system running other IGP (like ISOF, RIP) along with ISIS, receive a new route from the other routing protocols, then how do we advertise this routes to adjacent ISIS system.
>Do we advertise them at all or not?
>If we do how frequently and how?
>
>Please clarify my doubts.
>
>Thanking you in advance for all responses.
>Sachi.
>
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>_______________________________________________
>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 14 14:31:23 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13070
	for <isis-archive@odin.ietf.org>; Wed, 14 Nov 2001 14:31:22 -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 LAA91321;
	Wed, 14 Nov 2001 11:46:43 -0800 (PST)
Received: from auemail2.firewall.lucent.com (auemail2.lucent.com [192.11.223.163])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA91309
	for <isis-wg@spider.juniper.net>; Wed, 14 Nov 2001 11:45:09 -0800 (PST)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by auemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fAEJPuW11051
	for <isis-wg@spider.juniper.net>; Wed, 14 Nov 2001 14:25:56 -0500 (EST)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id UAA11193; Wed, 14 Nov 2001 20:25:55 +0100 (MET)
Cc: isis-wg@spider.juniper.net
Received: from lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id UAA11157; Wed, 14 Nov 2001 20:25:53 +0100 (MET)
Message-ID: <3BF2C541.C5C5C9D4@lucent.com>
From: Erik Hietbrink <ehietbrink@lucent.com>
Organization: Lucent Technologies, Huizen, The Netherlands
X-Mailer: Mozilla 4.73C-CCK-MCD EMS-1.5/4.72 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Nagasta Bagamba <nagastabagamba@yahoo.com>
Original-CC: isis-wg@spider.juniper.net
Subject: Re: FW: [Isis-wg] Overload & Attached bits
References: <20011114085317.59801.qmail@web21109.mail.yahoo.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 14 Nov 2001 20:25:53 +0100
Content-Transfer-Encoding: 7bit

Nagasta Bagamba wrote:
> 
> 2. Should we consider overloaded routers in our search
> for the nearest attached level-2 intermediate system?
> 
> You decided that the answer is No. But, I know of at
> least 2 major vendors which consider overloaded
> routers in the search for the nearest attached level-2
> IS.
> If vendors-mixture ISIS topology will be built,
> routing loops may occure. Does anyone have an idea how
> to avoid routing loops in such a topology?

Hi,

ISO10589-2001, section 9.8, says about the Overload bit:
"An LSP with this bit set will not be used by any decision process to
calculate routes to another IS through the originating system".

I would interpret this statement so that no default level 2 IS
route may be calculated to an IS with the overload bit set.

Regards,
Erik
_______________________________________________
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 14 15:18:10 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14726
	for <isis-archive@odin.ietf.org>; Wed, 14 Nov 2001 15:18:09 -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 MAA91596;
	Wed, 14 Nov 2001 12:35:44 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA91581
	for <isis-wg@spider.juniper.net>; Wed, 14 Nov 2001 12:34:04 -0800 (PST)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id E5F5AF2C4C; Wed, 14 Nov 2001 12:14:51 -0800 (PST)
To: Erik Hietbrink <ehietbrink@lucent.com>
Cc: Nagasta Bagamba <nagastabagamba@yahoo.com>, isis-wg@spider.juniper.net
Subject: Re: FW: [Isis-wg] Overload & Attached bits 
In-reply-to: Mail from Erik Hietbrink <ehietbrink@lucent.com> 
 dated Wed, 14 Nov 2001 20:25:53 +0100
 <3BF2C541.C5C5C9D4@lucent.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011114201451.E5F5AF2C4C@prattle.redback.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 14 Nov 2001 12:14:51 -0800


I would try to avoid picking the router with OL bit set if there are
multiple gateways available. But if all the L2/L1 gateways have the OL
bit set, then pick them anyway and send default traffic to them. Since
if not, those traffic will be dropped on the local L1 routers. Often
the OL bit these days indicate the BGP is not converged yet, at least
a subset of the traffic can still be delivered through the gateways
which is better than drop all of them. In the old days, routing and
forwarding compete for the same resource on routers, so doing the above
suggestion would not be a good behaviour, its hardly this case now.

 ]Nagasta Bagamba wrote:
 ]> 
 ]> 2. Should we consider overloaded routers in our search
 ]> for the nearest attached level-2 intermediate system?
 ]> 
 ]> You decided that the answer is No. But, I know of at
 ]> least 2 major vendors which consider overloaded
 ]> routers in the search for the nearest attached level-2
 ]> IS.
 ]> If vendors-mixture ISIS topology will be built,
 ]> routing loops may occure. Does anyone have an idea how
 ]> to avoid routing loops in such a topology?
 ]
 ]Hi,
 ]
 ]ISO10589-2001, section 9.8, says about the Overload bit:
 ]"An LSP with this bit set will not be used by any decision process to
 ]calculate routes to another IS through the originating system".
 ]
 ]I would interpret this statement so that no default level 2 IS
 ]route may be calculated to an IS with the overload bit set.
 ]
 ]Regards,
 ]Erik
 ]_______________________________________________
 ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ]http://external.juniper.net/mailman/listinfo/isis-wg

- Naiming
_______________________________________________
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 14 17:36:16 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA19770
	for <isis-archive@odin.ietf.org>; Wed, 14 Nov 2001 17:36:16 -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 OAA92163;
	Wed, 14 Nov 2001 14:53:44 -0800 (PST)
Received: from jenna.mindvision.com (jenna.mindvision.com [216.170.22.4])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA92151
	for <isis-wg@spider.juniper.net>; Wed, 14 Nov 2001 14:52:17 -0800 (PST)
Received: (from alan@localhost)
	by jenna.mindvision.com (8.11.1/8.11.1) id fAELW6217658;
	Wed, 14 Nov 2001 15:32:06 -0600
From: Alan Hannan <alan@routingloop.com>
To: Naiming Shen <naiming@redback.com>, Erik Hietbrink <ehietbrink@lucent.com>,
        Nagasta Bagamba <nagastabagamba@yahoo.com>, isis-wg@spider.juniper.net
Subject: Re: FW: [Isis-wg] Overload & Attached bits
Message-ID: <20011114153206.E16841@routingloop.com>
References: <ehietbrink@lucent.com> <20011114201451.E5F5AF2C4C@prattle.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 1.0pre3i
In-Reply-To: <20011114201451.E5F5AF2C4C@prattle.redback.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 14 Nov 2001 15:32:06 -0600


  FWIW, in ISP routing topology design, often times a box with the
  IS-IS OL-bit set is used for carrying traffic.

  There are two situtaions where this occurs, and they are usually
  both where the router in question is used as part of an auxilliary or
  out-of-band networks.

  The first is where the router in question is used only as a gateway of last
  resort for certain kinds of traffic, with a default route back towards the 
  NMS or NOC area, only for the purpose of carrying a subset of
  traffic.  Note that typically this router is not meant to carry
  production traffic.

  The second is where the router in question is using other routing
  protocols to carry certain types of traffic/destinations.  i.e.
  Ships in the Night kind of stuff.  Also, this router is not meant to
  carry production traffic in this context, rather stats and
  management traffic (telnet to boxes, SNMP, etc..).

  I assert that common ISP usage of IS-IS OL-bit does not comply with
  ISO10589-2001, section 9.8, yet it does comply with the wording if
  the phrase "any decision process' is changed to 'the IS-IS routing
  algorithm".

  -alan

Thus spake Naiming Shen (naiming@redback.com)
 on or about Wed, Nov 14, 2001 at 12:14:51PM -0800:
> 
> I would try to avoid picking the router with OL bit set if there are
> multiple gateways available. But if all the L2/L1 gateways have the OL
> bit set, then pick them anyway and send default traffic to them. Since
> if not, those traffic will be dropped on the local L1 routers. Often
> the OL bit these days indicate the BGP is not converged yet, at least
> a subset of the traffic can still be delivered through the gateways
> which is better than drop all of them. In the old days, routing and
> forwarding compete for the same resource on routers, so doing the above
> suggestion would not be a good behaviour, its hardly this case now.
> 
>  ]Nagasta Bagamba wrote:
>  ]> 
>  ]> 2. Should we consider overloaded routers in our search
>  ]> for the nearest attached level-2 intermediate system?
>  ]> 
>  ]> You decided that the answer is No. But, I know of at
>  ]> least 2 major vendors which consider overloaded
>  ]> routers in the search for the nearest attached level-2
>  ]> IS.
>  ]> If vendors-mixture ISIS topology will be built,
>  ]> routing loops may occure. Does anyone have an idea how
>  ]> to avoid routing loops in such a topology?
>  ]
>  ]Hi,
>  ]
>  ]ISO10589-2001, section 9.8, says about the Overload bit:
>  ]"An LSP with this bit set will not be used by any decision process to
>  ]calculate routes to another IS through the originating system".
>  ]
>  ]I would interpret this statement so that no default level 2 IS
>  ]route may be calculated to an IS with the overload bit set.
>  ]
>  ]Regards,
>  ]Erik
>  ]_______________________________________________
>  ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
>  ]http://external.juniper.net/mailman/listinfo/isis-wg
> 
> - Naiming
> _______________________________________________
> 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 14 18:22:23 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21147
	for <isis-archive@odin.ietf.org>; Wed, 14 Nov 2001 18:22:22 -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 PAA92393;
	Wed, 14 Nov 2001 15:39:44 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA92381
	for <isis-wg@spider.juniper.net>; Wed, 14 Nov 2001 15:38:09 -0800 (PST)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id AAA85F2C42; Wed, 14 Nov 2001 15:18:52 -0800 (PST)
To: Alan Hannan <alan@routingloop.com>
Cc: Erik Hietbrink <ehietbrink@lucent.com>,
        Nagasta Bagamba <nagastabagamba@yahoo.com>, isis-wg@spider.juniper.net
Subject: Re: FW: [Isis-wg] Overload & Attached bits 
In-reply-to: Mail from Alan Hannan <alan@routingloop.com> 
 dated Wed, 14 Nov 2001 15:32:06 CST
 <20011114153206.E16841@routingloop.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011114231852.AAA85F2C42@prattle.redback.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 14 Nov 2001 15:18:52 -0800


Hi, Alan,
	Great to hear all the 10589 "vialations":-)
	I had personal experience of the similar vialation: routerA
and routerB were in a webfarm connected by GigEs running IS-IS, and
each had a OCx link to the backbone. It was nice to set OL bit on
both routerA and routerB so that those two routers didn't carry
transit traffic through the webfarm. My previous posting just
responded to the case when OL and ATT bits are both set in a L1 area.

 ]
 ]  FWIW, in ISP routing topology design, often times a box with the
 ]  IS-IS OL-bit set is used for carrying traffic.
 ]
 ]  There are two situtaions where this occurs, and they are usually
 ]  both where the router in question is used as part of an auxilliary or
 ]  out-of-band networks.
 ]
 ]  The first is where the router in question is used only as a gateway of last
 ]  resort for certain kinds of traffic, with a default route back towards the 
 ]  NMS or NOC area, only for the purpose of carrying a subset of
 ]  traffic.  Note that typically this router is not meant to carry
 ]  production traffic.
 ]
 ]  The second is where the router in question is using other routing
 ]  protocols to carry certain types of traffic/destinations.  i.e.
 ]  Ships in the Night kind of stuff.  Also, this router is not meant to
 ]  carry production traffic in this context, rather stats and
 ]  management traffic (telnet to boxes, SNMP, etc..).
 ]
 ]  I assert that common ISP usage of IS-IS OL-bit does not comply with
 ]  ISO10589-2001, section 9.8, yet it does comply with the wording if
 ]  the phrase "any decision process' is changed to 'the IS-IS routing
 ]  algorithm".
 ]
 ]  -alan
 ]
 ]Thus spake Naiming Shen (naiming@redback.com)
 ] on or about Wed, Nov 14, 2001 at 12:14:51PM -0800:
 ]> 
 ]> I would try to avoid picking the router with OL bit set if there are
 ]> multiple gateways available. But if all the L2/L1 gateways have the OL
 ]> bit set, then pick them anyway and send default traffic to them. Since
 ]> if not, those traffic will be dropped on the local L1 routers. Often
 ]> the OL bit these days indicate the BGP is not converged yet, at least
 ]> a subset of the traffic can still be delivered through the gateways
 ]> which is better than drop all of them. In the old days, routing and
 ]> forwarding compete for the same resource on routers, so doing the above
 ]> suggestion would not be a good behaviour, its hardly this case now.
 ]> 
 ]>  ]Nagasta Bagamba wrote:
 ]>  ]> 
 ]>  ]> 2. Should we consider overloaded routers in our search
 ]>  ]> for the nearest attached level-2 intermediate system?
 >  ]> 
 ]>  ]> You decided that the answer is No. But, I know of at
 ]>  ]> least 2 major vendors which consider overloaded
 ]>  ]> routers in the search for the nearest attached level-2
 ]>  ]> IS.
 ]>  ]> If vendors-mixture ISIS topology will be built,
 ]>  ]> routing loops may occure. Does anyone have an idea how
 ]>  ]> to avoid routing loops in such a topology?
 ]>  ]
 ]>  ]Hi,
 ]>  ]
 ]>  ]ISO10589-2001, section 9.8, says about the Overload bit:
 ]>  ]"An LSP with this bit set will not be used by any decision process to
 ]>  ]calculate routes to another IS through the originating system".
 ]>  ]
 ]>  ]I would interpret this statement so that no default level 2 IS
 ]>  ]route may be calculated to an IS with the overload bit set.
 ]>  ]
 ]>  ]Regards,
 ]>  ]Erik
 ]>  ]_______________________________________________
 ]>  ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ]>  ]http://external.juniper.net/mailman/listinfo/isis-wg
 ]> 
 ]> - Naiming
 ]> _______________________________________________
 ]> Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ]> http://external.juniper.net/mailman/listinfo/isis-wg

- Naiming
_______________________________________________
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 15 06:18:16 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA17281
	for <isis-archive@lists.ietf.org>; Thu, 15 Nov 2001 06:18: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 DAA95301;
	Thu, 15 Nov 2001 03:35:45 -0800 (PST)
Received: from hotmail.com (f136.law3.hotmail.com [209.185.241.136])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA95286
	for <isis-wg@external.juniper.net>; Thu, 15 Nov 2001 03:34:16 -0800 (PST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Thu, 15 Nov 2001 03:14:59 -0800
Received: from 202.142.64.180 by lw3fd.law3.hotmail.msn.com with HTTP;
	Thu, 15 Nov 2001 11:14:59 GMT
X-Originating-IP: [202.142.64.180]
From: "Sachidananda K" <sachidananda_k@hotmail.com>
To: isis-wg@spider.juniper.net
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F136xkAApEER47DeQWX00009314@hotmail.com>
X-OriginalArrivalTime: 15 Nov 2001 11:14:59.0617 (UTC) FILETIME=[C3A16110:01C16DC6]
Subject: [Isis-wg] LAN ID field in LAN IIH
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 15 Nov 2001 11:14:59 +0000

Hello,

I've a question related to the values to be filled in packet format for the 
L1 LAN ISH. As soon as the IS comes up, what value do we fill in the LAN ID 
field. Is it supposed to be left blank ( filled with all 0's). I'm refering 
to the first Hello packet sent on the broadcast interface.

Please help me clarify this doubt.
Thanking you in advance for all the response.
Sachi

_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

_______________________________________________
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 15 08:57:12 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA23355
	for <isis-archive@odin.ietf.org>; Thu, 15 Nov 2001 08:57: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 GAA95965;
	Thu, 15 Nov 2001 06:14:44 -0800 (PST)
Received: from mail12.speakeasy.net (mail12.speakeasy.net [216.254.0.212])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA95953
	for <isis-wg@spider.juniper.net>; Thu, 15 Nov 2001 06:13:29 -0800 (PST)
Received: (qmail 45023 invoked from network); 15 Nov 2001 13:54:11 -0000
Received: from unknown (HELO NEIL) ([66.92.83.66]) (envelope-sender <Larmer@CommSense.Net>)
          by mail12.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <isis-wg@spider.juniper.net>; 15 Nov 2001 13:54:11 -0000
From: "Ken Larmer" <Larmer@commsense.net>
To: <isis-wg@spider.juniper.net>,
        "Sachidananda K" <sachidananda_k@hotmail.com>
Cc: "Ken Larmer" <larmer@commsense.net>
Subject: RE: [Isis-wg] LAN ID field in LAN IIH
Message-ID: <FFEPKFEJDGEONDOGKAHCEEMDCEAA.Larmer@CommSense.Net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <F136xkAApEER47DeQWX00009314@hotmail.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 15 Nov 2001 08:57:54 -0500
Content-Transfer-Encoding: 8bit

Hi Sachi,

> I've a question related to the values to be filled in packet
> format for the
> L1 LAN ISH. As soon as the IS comes up, what value do we fill in
> the LAN ID
> field. Is it supposed to be left blank ( filled with all 0's).
> I'm refering
> to the first Hello packet sent on the broadcast interface.

	Do you mean L1 LAN IIH PDU? An ISH is sent on a broadcast interface if you
are running IS-IS and/or DECnet Phase V. The ISH is meant to inform OSI ES
or DECnet Phase V ES of the routers available on a given LAN. However, in
Integrated IS-IS (IP-Only) there is no need to send an ISH on a broadcast
circuit (Int IS-IS does not care about ESs).

	With reference to a LAN IIH PDU, when a broadcast circuit is first enabled,
the LAN ID portion is set in accordance with the following ISO-10589
reference:

 8.4.1 Enabling of broadcast circuits

When the broadcast circuit is enabled on an Intermediate system the IS shall
perform the following actions.

a)	Commence sending IIH PDUs with the LAN ID field set to the concatenation
of its own systemID and its locally assigned one octet Local Circuit ID.
...
d)	After waiting iSISHelloTimer × 2 seconds, run the Level 1 and or the
level 2 designated intermediate system election process depending on the
Intermediate system type.

8.4.5 LAN designated intermediate systems

The LAN ID field in the LAN IIH PDUs transmitted by this system shall be set
to the value of the LAN ID field reported in the LAN IIH PDU (for the
appropriate level) received from the system which this system considers to
be the Designated Intermediate System. This value shall also be passed to
the Update Process, as the pseudonode ID, to enable Link State PDUs to be
issued for this system claiming connectivity to the pseudonode.

If this system, as a result of the Designated Intermediate System election
process, considers itself to be designated Intermediate System, the LAN ID
field shall be set to the concatenation of this system’s own system ID and
the locally assigned one octet Local Circuit ID.

_______________________________________________
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 15 15:25:12 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17525
	for <isis-archive@odin.ietf.org>; Thu, 15 Nov 2001 15:25: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 MAA97471;
	Thu, 15 Nov 2001 12:41:44 -0800 (PST)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA97459
	for <isis-wg@spider.juniper.net>; Thu, 15 Nov 2001 12:40:27 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734290122FDA6@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: isis-wg@spider.juniper.net
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] Revised MIB
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 15 Nov 2001 15:21:02 -0500

I've just sent in revision .06 of the ISIS MIB to
the ietf.  Most changes were made to accommodate
SMICng.  Some edits were made to comments.  The
list of major changes is below.  

-- Changes in version 06.
--      Updates for clean SMICng compile
--              Remove unused IMPORTed types
--              Removed restrictions on InetAddressType (pity)
--              Conformance section added

The next effort will be to add Notifications
(aka Traps) to the mix.  I have started off with
the 10589 list of alarms, but would be happy to
add any events that the community would find 
useful.  

I will also be looking at traffic engineering
knobs that need adding.  

Comments always welcome.  

This is a busy week at the IETF, so it may be 
awhile before the draft appears.  If you wish to
see an early version, drop me a line: the reflector
will not relay a document this big.  

- jeff parker
- axiowave networks
- There's many a man hath more hair than wit.
_______________________________________________
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 16 07:45:04 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28557
	for <isis-archive@lists.ietf.org>; Fri, 16 Nov 2001 07:45: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 EAA01790;
	Fri, 16 Nov 2001 04:56:45 -0800 (PST)
Received: from web21102.mail.yahoo.com (web21102.mail.yahoo.com [216.136.227.104])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id EAA01778
	for <isis-wg@spider.juniper.net>; Fri, 16 Nov 2001 04:55:24 -0800 (PST)
Message-ID: <20011116123600.46330.qmail@web21102.mail.yahoo.com>
Received: from [62.0.92.148] by web21102.mail.yahoo.com via HTTP; Fri, 16 Nov 2001 04:36:00 PST
From: Nagasta Bagamba <nagastabagamba@yahoo.com>
Subject: [Isis-wg] Overload & Attached bits 
To: ehietbrink@lucent.com, erez@cwnt.com, alan@routingloop.com,
        naiming@redback.com
Cc: isis-wg@spider.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 16 Nov 2001 04:36:00 -0800 (PST)

Hi,
It seems to me that we all want the overload bit to
have a different meaning depends on the cause of the
overloading situation:
Erik, you want to go by the book (in this case the ISO
10589). I don't think anyone can argue with your
interpretation.
Shen, in your example you prefer to send traffic to
any IS than not sending at all. I suppose in most
cases the traffic will go through the overloaded IS
and reach the destination safely. But as you said, you
suppose that in most cases the overload bit indicates
the BGP is not converged yet. 
Erez, you gave an example why not using the the
overloaded IS in the nearest attached algo.
Alan, you gave an example for why not using the
overloaded IS as transient.

It looks like there should be a different behavior
depends on the cause of the overloading (on-startup,
'real' database overload, new tested router...).
As I see it, we have 2 problems:
1. There is only ONE bit, so other routers have no
idea what was the reason for setting it.
2. We can't 'violate' the ISO/RFC standards just
because we think there are better ways to do things. 
Standards are what the protocol is all about...

In a multi-vendors isis topology, the system
administrator will have a really hard job trying to
figure out the behavior in an overloaded situation.

Regards,
Nagi

--- Naiming Shen <naiming@redback.com> wrote:
> To: Alan Hannan <alan@routingloop.com>
> CC: Erik Hietbrink <ehietbrink@lucent.com>,
> 	Nagasta Bagamba <nagastabagamba@yahoo.com>,
> 	isis-wg@spider.juniper.net
> Subject: Re: FW: [Isis-wg] Overload & Attached bits 
> Date: Wed, 14 Nov 2001 15:18:52 -0800
> From: Naiming Shen <naiming@redback.com>
> 
> 
> Hi, Alan,
> 	Great to hear all the 10589 "vialations":-)
> 	I had personal experience of the similar vialation:
> routerA
> and routerB were in a webfarm connected by GigEs
> running IS-IS, and
> each had a OCx link to the backbone. It was nice to
> set OL bit on
> both routerA and routerB so that those two routers
> didn't carry
> transit traffic through the webfarm. My previous
> posting just
> responded to the case when OL and ATT bits are both
> set in a L1 area.
> 
>  ]
>  ]  FWIW, in ISP routing topology design, often
> times a box with the
>  ]  IS-IS OL-bit set is used for carrying traffic.
>  ]
>  ]  There are two situtaions where this occurs, and
> they are usually
>  ]  both where the router in question is used as
> part of an auxilliary or
>  ]  out-of-band networks.
>  ]
>  ]  The first is where the router in question is
> used only as a gateway of last
>  ]  resort for certain kinds of traffic, with a
> default route back towards the 
>  ]  NMS or NOC area, only for the purpose of
> carrying a subset of
>  ]  traffic.  Note that typically this router is not
> meant to carry
>  ]  production traffic.
>  ]
>  ]  The second is where the router in question is
> using other routing
>  ]  protocols to carry certain types of
> traffic/destinations.  i.e.
>  ]  Ships in the Night kind of stuff.  Also, this
> router is not meant to
>  ]  carry production traffic in this context, rather
> stats and
>  ]  management traffic (telnet to boxes, SNMP,
> etc..).
>  ]
>  ]  I assert that common ISP usage of IS-IS OL-bit
> does not comply with
>  ]  ISO10589-2001, section 9.8, yet it does comply
> with the wording if
>  ]  the phrase "any decision process' is changed to
> 'the IS-IS routing
>  ]  algorithm".
>  ]
>  ]  -alan
>  ]
>  ]Thus spake Naiming Shen (naiming@redback.com)
>  ] on or about Wed, Nov 14, 2001 at 12:14:51PM
> -0800:
>  ]> 
>  ]> I would try to avoid picking the router with OL
> bit set if there are
>  ]> multiple gateways available. But if all the
> L2/L1 gateways have the OL
>  ]> bit set, then pick them anyway and send default
> traffic to them. Since
>  ]> if not, those traffic will be dropped on the
> local L1 routers. Often
>  ]> the OL bit these days indicate the BGP is not
> converged yet, at least
>  ]> a subset of the traffic can still be delivered
> through the gateways
>  ]> which is better than drop all of them. In the
> old days, routing and
>  ]> forwarding compete for the same resource on
> routers, so doing the above
>  ]> suggestion would not be a good behaviour, its
> hardly this case now.
>  ]> 
>  ]>  ]Nagasta Bagamba wrote:
>  ]>  ]> 
>  ]>  ]> 2. Should we consider overloaded routers in
> our search
>  ]>  ]> for the nearest attached level-2
> intermediate system?
>  >  ]> 
>  ]>  ]> You decided that the answer is No. But, I
> know of at
>  ]>  ]> least 2 major vendors which consider
> overloaded
>  ]>  ]> routers in the search for the nearest
> attached level-2
>  ]>  ]> IS.
>  ]>  ]> If vendors-mixture ISIS topology will be
> built,
>  ]>  ]> routing loops may occure. Does anyone have
> an idea how
>  ]>  ]> to avoid routing loops in such a topology?
>  ]>  ]
>  ]>  ]Hi,
>  ]>  ]
>  ]>  ]ISO10589-2001, section 9.8, says about the
> Overload bit:
>  ]>  ]"An LSP with this bit set will not be used by
> any decision process to
>  ]>  ]calculate routes to another IS through the
> originating system".
>  ]>  ]
>  ]>  ]I would interpret this statement so that no
> default level 2 IS
>  ]>  ]route may be calculated to an IS with the
> overload bit set.
>  ]>  ]
>  ]>  ]Regards,
>  ]>  ]Erik
>  ]> 
> ]_______________________________________________
>  ]>  ]Isis-wg mailing list  - 
> Isis-wg@external.juniper.net
>  ]> 
>
]http://external.juniper.net/mailman/listinfo/isis-wg
>  ]> 
>  ]> - Naiming
>  ]> _______________________________________________
>  ]> Isis-wg mailing list  - 
> Isis-wg@external.juniper.net
>  ]>
> http://external.juniper.net/mailman/listinfo/isis-wg
> 
> - Naiming




__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
_______________________________________________
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 16 09:57:37 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04120
	for <isis-archive@lists.ietf.org>; Fri, 16 Nov 2001 09:57: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 HAA02368;
	Fri, 16 Nov 2001 07:12:46 -0800 (PST)
Received: from ihemail1.firewall.lucent.com (ihemail1.lucent.com [192.11.222.161])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA02356
	for <isis-wg@spider.juniper.net>; Fri, 16 Nov 2001 07:11:13 -0800 (PST)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by ihemail1.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fAGEph002093
	for <isis-wg@spider.juniper.net>; Fri, 16 Nov 2001 09:51:47 -0500 (EST)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id PAA17669; Fri, 16 Nov 2001 15:51:42 +0100 (MET)
Cc: erez@cwnt.com, alan@routingloop.com, naiming@redback.com,
        isis-wg@spider.juniper.net
Received: from lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id PAA17585; Fri, 16 Nov 2001 15:51:37 +0100 (MET)
Message-ID: <3BF527F9.F7B64731@lucent.com>
From: Erik Hietbrink <ehietbrink@lucent.com>
Organization: Lucent Technologies, Huizen, The Netherlands
X-Mailer: Mozilla 4.73C-CCK-MCD EMS-1.5/4.72 [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Nagasta Bagamba <nagastabagamba@yahoo.com>
Original-CC: erez@cwnt.com, alan@routingloop.com, naiming@redback.com,
        isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] Overload & Attached bits
References: <20011116123600.46330.qmail@web21102.mail.yahoo.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 16 Nov 2001 15:51:37 +0100
Content-Transfer-Encoding: 7bit

Nagasta Bagamba wrote:
> 
> It looks like there should be a different behavior
> depends on the cause of the overloading (on-startup,
> 'real' database overload, new tested router...).
> As I see it, we have 2 problems:
> 1. There is only ONE bit, so other routers have no
> idea what was the reason for setting it.
> 2. We can't 'violate' the ISO/RFC standards just
> because we think there are better ways to do things.
> Standards are what the protocol is all about...
> 
> In a multi-vendors isis topology, the system
> administrator will have a really hard job trying to
> figure out the behavior in an overloaded situation.

Good summary. My major concern is what to do in a dual-ISIS stack 
(NE supports ISIS for OSI and I-ISIS for IP), when this overload
bit is interpreted differently.
My personal choice for conveying information retrieved from other
routing processes (like BGP convergence) would be to put it in a TLV.
We should avoid having multi-interpretable fields in PDUs.

Regards,
Erik
_______________________________________________
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 16 13:00:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14457
	for <isis-archive@lists.ietf.org>; Fri, 16 Nov 2001 13:00:57 -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 KAA03126;
	Fri, 16 Nov 2001 10:14:45 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA03114
	for <isis-wg@spider.juniper.net>; Fri, 16 Nov 2001 10:13:18 -0800 (PST)
Received: from redd3174.procket.com (IDENT:root@redd3174.procket.com [10.1.3.174])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fAGHqs8A009681;
	Fri, 16 Nov 2001 09:52:55 -0800 (PST)
From: Henk Smit <henk@Procket.com>
Received: (from henk@localhost)
	by redd3174.procket.com (8.12.1/8.12.1) id fAGHqsfM010674;
	Fri, 16 Nov 2001 09:52:54 -0800
Message-Id: <200111161752.fAGHqsfM010674@redd3174.procket.com>
Subject: Re: [Isis-wg] Overload & Attached bits
To: nagastabagamba@yahoo.com (Nagasta Bagamba)
Cc: ehietbrink@lucent.com, erez@cwnt.com, alan@routingloop.com,
        naiming@redback.com, isis-wg@spider.juniper.net
In-Reply-To: <20011116123600.46330.qmail@web21102.mail.yahoo.com> from "Nagasta Bagamba" at Nov 16, 2001 04:36:00 AM
X-Mailer: ELM [version 2.5 PL3]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 16 Nov 2001 09:52:54 -0800 (PST)
Content-Transfer-Encoding: 7bit


> In a multi-vendors isis topology, the system
> administrator will have a really hard job trying to
> figure out the behavior in an overloaded situation.

  The problem is this:
  Right now we are discussing how L1-only routers should interpret the
 overload-bit and the attached-bit. IMHO this is not open for discussion.
 10589 clearly says how a router is supposed to compute routes when it
 sees LSPs with either the attached bit (ATT) set, or the overload
 bit (OVL) set. As noted, when you change this, you will run into
 compatability issues. So: don't change the interpretation of the OVL
 and ATT bits.

  What is not clearly defined is when a router must, could or should
 set the ATT bit and/or OVL bit. So implementators are free to play
 with algorithms when to set or not set those bits. Setting one of
 these bits means that the router either invites or discourages other
 routers to send traffic through it. Regardless of what algorithms
 implementors use for their L1L2 routers to decide to set the ATT
 bit and OVL bit, if all routers interpret these bits the same way,
 this should never cause routing loops.

  Let's look at the problem of a L1L2 router setting the OVL bit.
 It means it doesn't want to attract intra-area transit traffic.
 If the implementor also meant that he didn't want to attract L1->L2
 inter-area traffic, then the implementor should make sure that his
 router also does not set the ATT bit. Simple as that. If a router
 sets both ATT and OVL, that means it does not want to forward intra-area
 traffic, but it does want to forward L1->L2 inter-area traffic.

  The same is through for inter-area traffic in the other direction.
 If a L1L2 router sets the OVL bit in its L2 LSP, but it also advertises
 all L1 prefixes learned via L1 routing, then it must forward traffic
 to those L1 destinations. If it doesn't want to forward that L2->L1
 traffic, then it must not advertise those L1 prefixes in its L2 LSP.

  Last remaining problem. Suppose a L1L2 router is the only router that
 supplies connectivity between two parts of the network. Setting the OVL
 bit will make those two parts effectively disconnected. This might not
 always be the behaviour you want.
  If you want to solve this problem by making routers interpret the OVL
 in a different way, then you run into compatability problems again. So
 don't try to solve this problem by chaning the interpretation on the
 other routers. Solve it by changing the behaviour of the advertising router.
 A solution would be to not use the OVL bit to discourage other routers
 to compute a path through this router. In stead, the router could
 advertise all its links with a very high metric. That would cause paths
 through this router to be the least preferred, but in case there are no
 other paths, it would still be used. And thus the network will not become
 partitioned. (Granted, this will probably work better with the newer
 TLVs with wider metrics).

  So it might not be enough to just set or not set the OVL bit.
 A router should also adjust the ATT bit.
 And it should consider which L1->L2 and L2->L1 prefixes to advertise.
 And it should make a decision wether to use the OVL bit trick or the
 trick where it set its link metrics to a high value.

  All this can be done in the advertising router. It is easy to solve
 problems by changing semantics of existing protocols. Unfortunately
 usually that won't work in the real world. Useful solutions should
 work in a backward compatible way. Putting all intelligence in the
 advertising router should ensure backward compatibility.

  Hope this helps,

       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 19 17:08:41 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29124
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 17:08: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 OAA22728;
	Mon, 19 Nov 2001 14:25:36 -0800 (PST)
Received: from ghostrider.gredler.at (ghostrider.gredler.at [193.83.223.228])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA99079
	for <isis-wg@spider.juniper.net>; Mon, 10 Sep 2001 12:07:14 -0700 (PDT)
Received: (from hannes@localhost)
	by ghostrider.gredler.at (8.9.3/8.9.3) id UAA18914;
	Mon, 10 Sep 2001 20:55:43 +0200
From: Hannes Gredler <hannes@juniper.net>
To: Swati Rastogi <swatirstogi@yahoo.com>
Cc: isis-wg <isis-wg@spider.juniper.net>
Subject: Re: [Isis-wg] draft-ietf-isis-traffic-04.txt
Message-ID: <20010910205543.B18900@juniper.net>
References: <00be01c13a04$66da0950$b4036c6b@Manav>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <00be01c13a04$66da0950$b4036c6b@Manav>; from swatirstogi@yahoo.com on Mon, Sep 10, 2001 at 07:55:08PM +0530
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 10 Sep 2001 20:55:43 +0200

[chaos] theory tells .. the best scheme is to use _no_ scheme as
you cannot maintain it anyway ;-)

/hannes

On Mon, Sep 10, 2001 at 07:55:08PM +0530, Swati Rastogi wrote:
| Hi,
| I was just going through the above stated draft. I have a very elementary
| doubt. Why aren't the sub TLVs numbered as 1,2,3,4,5 etc. Why are they
| numbered as 3,6,8,9,etc. This is the draft that i presume introduced these
| additional subTLVs, so why aren't the numbers really ordered ?
| 
| This is indeed a very foolish doubt .. but am just curious.
| 
| Thanks,
| Swati
| 
| 
| _________________________________________________________
| Do You Yahoo!?
| Get your free @yahoo.com address at http://mail.yahoo.com
| 
| _______________________________________________
| 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 19 17:11:05 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29299
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 17:11: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 OAA22902;
	Mon, 19 Nov 2001 14:29:11 -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 LAA58401
	for <isis-wg@spider.juniper.net>; Thu, 20 Sep 2001 11:05:50 -0700 (PDT)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f8KHrCn43227
	for <isis-wg@juniper.net>; Thu, 20 Sep 2001 10:53:13 -0700 (PDT)
X-JNPR-Received-From: outside
Received: from uniwest1.redstonecom.com ([65.194.140.130]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 20 Sep 2001 10:52:52 -0700
Received: by mailwest.unispherenetworks.com with Internet Mail Service (5.5.2653.19)
	id <TGHM86KS>; Thu, 20 Sep 2001 13:53:10 -0400
Message-ID: <49FF5C6DDBD8D311BBBD009027DE980C031F4291@mailwest.unispherenetworks.com>
From: "Chapman, Ken" <KChapman@unispherenetworks.com>
To: "'jparker@axiowave.com'" <jparker@axiowave.com>,
        "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Cc: "Kwong, Ambrose" <AKwong@unispherenetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 20 Sep 2001 17:52:52.0406 (UTC) FILETIME=[11C9E560:01C141FD]
Subject: [Isis-wg] draft-ietf-isis-wg-mib-05.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 20 Sep 2001 13:53:10 -0400

Hi,
Could someone please explain to me the third sentance of the following
object definition?

     isisManAreaAddrExistState OBJECT-TYPE
         SYNTAX RowStatus
         MAX-ACCESS read-create
         STATUS current
         DESCRIPTION
             "The state of the isisManAreaAddrEntry. This object
             follows the Row Status behaviour. If an attempt is
             made to set this object to the value off when the
             corresponding isisManAreaAddrEntry is the only valid
             entry for this instance and when the corresponding ISIS
             instance has isisSysAdminState set to On then the attempt
             is rejected."
         DEFVAL { active }
     ::= { isisManAreaAddrEntry 2 }

Thanks,
	Ken
ps. Please e-mail me direct; I'm not a member of your list.  (I just do a
lot of SNMP stuff.)
++++++++++++++++++++++++++++++++++++++++++++++
Ken Chapman           Unisphere Networks, Inc.
                      M/S 2056
Tel: +1 978 589 0288  10 Technology Park Drive
Fax: +1 978 589 0800  Westford, MA 01886
Email: KChapman@UnisphereNetworks.com
++++++++++++++++++++++++++++++++++++++++++++++


_______________________________________________
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 19 17:11:54 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29339
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 17:11:53 -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 OAA22953;
	Mon, 19 Nov 2001 14:30:17 -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 CAA68010
	for <isis-wg@spider.juniper.net>; Sat, 22 Sep 2001 02:39:02 -0700 (PDT)
Received: from pong.juniper.net (pong.juniper.net [207.17.137.102])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f8M9QAn00556
	for <isis-wg@juniper.net>; Sat, 22 Sep 2001 02:26:13 -0700 (PDT)
X-JNPR-Received-From: outside
Received: from mail2.zte.com.cn ([202.103.147.144]) by pong.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Sat, 22 Sep 2001 02:25:32 -0700
To: isis-wg@juniper.net
X-Mailer: Lotus Notes Release 5.0.1 (Intl) 16 July 1999
Message-ID: <OF82B4ED7D.9B659A37-ON48256ACF.002BB969@zte.com.cn>
From: 0xLJC0EED2EEz/0xLJC4CFBEA9D1D0BEBFCBF9z/0xLJBDBBBBBBB2FAC6B7CAC2D2B5B2BFz/zte_ltd <0xLJC0EED2EEz/0xLJC4CFBEA9D1D0BEBFCBF9z/0xLJBDBBBBBBB2FAC6B7CAC2D2B5B2BFz/zte_ltd@mail.zte.com.cn>
X-MIMETrack: Serialize by Router on notes_svr7_1/zte_ltd(Release 5.0.8 |June 18, 2001) at
 2001-09-22 17:29:04
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 22 Sep 2001 09:25:34.0671 (UTC) FILETIME=[884F9DF0:01C14348]
Subject: [Isis-wg] how to transfer isis pdu in p2p link?
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 22 Sep 2001 16:03:05 +0800

In Lan , isis pdu is transmitted using 802.3. Who knows what link protocol
is used when isis pdu transmitted in p2p network?

thx advance

_______________________________________________
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 19 17:16:48 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29583
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 17:16: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 OAA23404;
	Mon, 19 Nov 2001 14:34:47 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA58274
	for <isis-wg@spider.juniper.net>; Mon, 3 Sep 2001 18:50:22 -0700 (PDT)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id f841dii32473
	for <isis-wg@juniper.net>; Mon, 3 Sep 2001 18:39:45 -0700 (PDT)
X-JNPR-Received-From: outside
Received: from cms1.etri.re.kr ([129.254.16.11]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 3 Sep 2001 18:39:39 -0700
Received: from ns (mjyang.etri.re.kr [129.254.194.55]) by cms1.etri.re.kr with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id RJB3F146; Tue, 4 Sep 2001 10:36:08 +0900
Message-ID: <000f01c134e5$fd8cc1e0$37c2fe81@etri.re.kr>
From: "Mijung Yang" <mjyang@etri.re.kr>
To: <isis-wg-request@spider.juniper.net>, <isis-wg@juniper.net>,
        <isis@merit.edu>
Organization: ETRI
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_000C_01C13531.6D49B060"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2919.6600
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600
X-OriginalArrivalTime: 04 Sep 2001 01:39:40.0132 (UTC) FILETIME=[76ABFA40:01C134E2]
Subject: [Isis-wg] Question about Internet Draft of IS-IS TE extension
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Sep 2001 11:04:54 +0900

This is a multi-part message in MIME format.

------=_NextPart_000_000C_01C13531.6D49B060
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

DQpEZWFyLi4NCg0KSSBoYXZlIHNvbWUgcXVlc3Rpb25zIGFib3V0IGRyYWZ0LWlldGYtaXNpcy10
cmFmZmljLTA0LnR4dC4NCiANCkZpcnN0LA0KSSBkb24ndCBrbm93IGV4YWN0IG1lYW5pbmcgcHJl
Zml4IGxlbmd0aCBmaWVsZCg2Yml0cykgYW5kIElQdjQgcHJlZml4IGZpZWxkKDB+NG9jdGV0cykN
CmluIHRoZSBleHRlbmRlZCBJUCByZWFjaGFiaWxpdHkgVExWLg0KSSB0aGluayB0aGF0IHRoZSBt
ZWFuaW5nIG9mIHR3byBmaWVsZHMgaXMgc2FtZS4NCkFuZCwgSG93IGNhbiBJIGtub3cgdGhlIHJl
YWNoYWJsZSBuZXR3b3JrPw0KUGxlYXNlLCBsZXQgbWUgaW5mb3JtIHRoZSBleGFjdCBtZWFuaW5n
IGFuZCB1c2FnZSBvZiB0aGUgdHdvIGZpZWxkcyANCiANClNlY29uZCwNCkkgd2FudCB0byBjb25m
aXJtIHRoYXQgc3ViLVRMViA2IGFuZCBzdWItVExWIDggaW4gdGhlIGV4dGVuZGVkIElTIHJlYWNo
YWJpbGl0eSBUTFYgDQppbmRpY2F0ZSB0d28gZW5kIGFkZHJlc3Mgb2YgdGhlIGxpbmsgYW5kIHRo
aXMgYWRkcmVzcyBpcyByb3V0ZXIgSUQgYWRkcmVzcyBvciBub3QuDQoNCkF3YWl0aW5nIHRoZSBw
bGVhc3VyZSBvZiB5b3VyIHJlcGx5LiANClJlZ2FyZHMsDQoNCi0tLS0tLS0tLS0tLS0tLS0tDQpN
aWp1bmcgWWFuZyAvIEVUUkkgDQpURUw6ICs4Mi00Mi04NjAtNDkyMiANCkZBWDogKzgyLTQyLTg2
MC01NDQwIA0KRS1tYWlsOiBtanlhbmdAZXRyaS5yZS5rciANCg0K

------=_NextPart_000_000C_01C13531.6D49B060
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: base64

PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgY29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PWtz
X2NfNTYwMS0xOTg3IiBodHRwLWVxdWl2PUNvbnRlbnQtVHlwZT4NCjxNRVRBIGNvbnRlbnQ9Ik1T
SFRNTCA1LjAwLjI5MTkuNjMwNyIgbmFtZT1HRU5FUkFUT1I+DQo8U1RZTEU+PC9TVFlMRT4NCjwv
SEVBRD4NCjxCT0RZIGJnQ29sb3I9I2ZmZmZmZj4NCjxESVY+Jm5ic3A7PC9ESVY+DQo8RElWPjxG
T05UIHNpemU9Mj5EZWFyLi48L0ZPTlQ+PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj48
Rk9OVCBzaXplPTI+SSBoYXZlIHNvbWUgcXVlc3Rpb25zIGFib3V0IA0KZHJhZnQtaWV0Zi1pc2lz
LXRyYWZmaWMtMDQudHh0LjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4m
bmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkZpcnN0LDwvRk9OVD48L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPkkgZG9uJ3Qga25vdyBleGFjdCBtZWFuaW5nIHByZWZpeCBsZW5ndGggZmll
bGQoNmJpdHMpIGFuZCBJUHY0IA0KcHJlZml4IGZpZWxkKDB+NG9jdGV0cyk8L0ZPTlQ+PC9ESVY+
DQo8RElWPjxGT05UIHNpemU9Mj5pbiB0aGUgZXh0ZW5kZWQgSVAgcmVhY2hhYmlsaXR5IFRMVi48
L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5JIHRoaW5rIHRoYXQgdGhlIG1lYW5pbmcg
b2YgdHdvIGZpZWxkcyBpcyBzYW1lLjwvRk9OVD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPkFu
ZCwgSG93IGNhbiZuYnNwO0kga25vdyB0aGUmbmJzcDtyZWFjaGFibGUgDQpuZXR3b3JrPzwvRk9O
VD48L0RJVj4NCjxESVY+PEZPTlQgc2l6ZT0yPlBsZWFzZSwgbGV0IG1lIGluZm9ybSB0aGUgZXhh
Y3QgbWVhbmluZyBhbmQgdXNhZ2Ugb2YgdGhlIHR3byANCmZpZWxkczwvRk9OVD4mbmJzcDs8L0RJ
Vj4NCjxESVY+PEZPTlQgc2l6ZT0yPjwvRk9OVD4mbmJzcDs8L0RJVj4NCjxESVY+PEZPTlQgc2l6
ZT0yPlNlY29uZCw8L0ZPTlQ+PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj5JIHdhbnQgdG8gY29u
ZmlybSB0aGF0IHN1Yi1UTFYgNiBhbmQgc3ViLVRMViA4IGluIHRoZSBleHRlbmRlZCANCklTIHJl
YWNoYWJpbGl0eSBUTFYgPC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+aW5kaWNhdGUg
dHdvIGVuZCBhZGRyZXNzIG9mIHRoZSBsaW5rIGFuZCB0aGlzIGFkZHJlc3MgaXMgDQpyb3V0ZXIg
SUQgYWRkcmVzcyBvciBub3QuPC9GT05UPjwvRElWPg0KPERJVj4mbmJzcDs8L0RJVj4NCjxESVY+
PEZPTlQgc2l6ZT0yPjxGT05UIHNpemU9Mj5Bd2FpdGluZyB0aGUgcGxlYXN1cmUgb2YgeW91ciBy
ZXBseS48L0ZPTlQ+IA0KPERJVj48Rk9OVCBzaXplPTI+UmVnYXJkcyw8QlI+PC9GT05UPjwvRk9O
VD48Rk9OVCBzaXplPTI+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+LS0tLS0tLS0t
LS0tLS0tLS08QlI+TWlqdW5nIFlhbmcgLyBFVFJJIDxCUj5URUw6IA0KKzgyLTQyLTg2MC00OTIy
IDxCUj5GQVg6ICs4Mi00Mi04NjAtNTQ0MCA8QlI+RS1tYWlsOiA8QSANCmhyZWY9Im1haWx0bzpt
anlhbmdAZXRyaS5yZS5rciI+bWp5YW5nQGV0cmkucmUua3I8L0E+IA0KPEJSPjwvRElWPjwvRElW
PjwvRk9OVD48L0JPRFk+PC9IVE1MPg0K

------=_NextPart_000_000C_01C13531.6D49B060--

_______________________________________________
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 19 17:39:35 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA00966
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 17:39: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 OAA23675;
	Mon, 19 Nov 2001 14:53:45 -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 OAA23663
	for <isis-wg@spider.juniper.net>; Mon, 19 Nov 2001 14:52:10 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fAJMWMK72663
	for <isis-wg@juniper.net>; Mon, 19 Nov 2001 14:32:22 -0800 (PST)
X-JNPR-Received-From: outside
Received: from bridge.axiowave.com ([216.49.69.50]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 19 Nov 2001 14:30:28 -0800
Message-ID: <EB5FFC72F183D411B3820006295734290122FDF8@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Chapman, Ken'" <KChapman@unispherenetworks.com>
Cc: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Subject: RE: [Isis-wg] draft-ietf-isis-wg-mib-05.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 19 Nov 2001 22:30:28.0734 (UTC) FILETIME=[CA84D9E0:01C17149]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Nov 2001 17:31:36 -0500

> Hi,
> Could someone please explain to me the third sentance of the following
> object definition?
> 
>      isisManAreaAddrExistState OBJECT-TYPE
>          SYNTAX RowStatus
>          MAX-ACCESS read-create
>          STATUS current
>          DESCRIPTION
>              "The state of the isisManAreaAddrEntry. This object
>              follows the Row Status behaviour. If an attempt is
>              made to set this object to the value off when the
>              corresponding isisManAreaAddrEntry is the only valid
>              entry for this instance and when the corresponding ISIS
>              instance has isisSysAdminState set to On then the attempt
>              is rejected."
>          DEFVAL { active }
>      ::= { isisManAreaAddrEntry 2 }

Ken -

RowStatus is something I didn't create.  See Dave Perkins book for
a discussion of this.  Briefly it is used to disambiguate creation
and deletion.  

"If an attempt is made to set this object to the value 
off when the corresponding isisManAreaAddrEntry is 
the only valid entry for this instance and when the 
corresponding ISIS instance has isisSysAdminState 
set to On then the attempt is rejected."

If someone wants to remove an Area Address, at it is the 
only configured address left, you should not allow this to
happen, as the protocol needs to have at least one defined.  

You -can- do this if you turn off the protocol, and then 
remove the Address.    

Suggestions on how to make this clearer are welcome.

- jeff parker
- axiowave networks

_______________________________________________
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 19 21:03:24 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06280
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 21:03:22 -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 QAA24280;
	Mon, 19 Nov 2001 16:37:46 -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 QAA24268
	for <isis-wg@spider.juniper.net>; Mon, 19 Nov 2001 16:36:34 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fAK0GiK77837
	for <isis-wg@juniper.net>; Mon, 19 Nov 2001 16:16:44 -0800 (PST)
X-JNPR-Received-From: outside
Received: from miata.procket.com ([209.140.237.2]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 19 Nov 2001 16:06:51 -0800
Received: from redd3174.procket.com (IDENT:root@redd3174.procket.com [10.1.3.174])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fAK05g8A022420;
	Mon, 19 Nov 2001 16:05:42 -0800 (PST)
From: Henk Smit <henk@procket.com>
Received: (from henk@localhost)
	by redd3174.procket.com (8.12.1/8.12.1) id fAK05gMr011090;
	Mon, 19 Nov 2001 16:05:42 -0800
Message-Id: <200111200005.fAK05gMr011090@redd3174.procket.com>
Subject: Re: [Isis-wg] how to transfer isis pdu in p2p link?
To: 0xLJC0EED2EEz/0xLJC4CFBEA9D1D0BEBFCBF9z/0xLJBDBBBBBBB2FAC6B7CAC2D2B5B2BFz/zte_ltd@mail.zte.com.cn (0xLJC0EED2EEz/0xLJC4CFBEA9D1D0BEBFCBF9z/0xLJBDBBBBBBB2FAC6B7CAC2D2B5B2BFz/zte_ltd)
Cc: isis-wg@juniper.net
In-Reply-To: <OF82B4ED7D.9B659A37-ON48256ACF.002BB969@zte.com.cn> from "0xLJC0EED2EEz/0xLJC4CFBEA9D1D0BEBFCBF9z/0xLJBDBBBBBBB2FAC6B7CAC2D2B5B2BFz/zte_ltd" at Sep 22, 2001 04:03:05 PM
X-Mailer: ELM [version 2.5 PL3]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 20 Nov 2001 00:06:51.0296 (UTC) FILETIME=[4131CA00:01C17157]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Nov 2001 16:05:42 -0800 (PST)
Content-Transfer-Encoding: 7bit


> In Lan , isis pdu is transmitted using 802.3. Who knows what link protocol
> is used when isis pdu transmitted in p2p network?

  Whatever you want. Whatever you are running on the p2p link.
 So if you use PPP, ISIS will be inside a PPP frame. If you wanna run
 cisco's HDLC, the ISIS packet will be inside a HDLC frame.
 Unlike ethernet, where you can run 4 different encapsulations at the
 same time, on a p2p link you can run only one encapsulation at the
 same time

     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 19 21:32:55 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08541
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 21:32: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 SAA24775;
	Mon, 19 Nov 2001 18:17:45 -0800 (PST)
Received: from rly-ip02.mx.aol.com (rly-ip02.mx.aol.com [152.163.225.160])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA24763
	for <isis-wg@spider.juniper.net>; Mon, 19 Nov 2001 18:16:02 -0800 (PST)
Received: from logs-wk.proxy.aol.com (logs-wk.proxy.aol.com [205.188.198.135])
	  by rly-ip02.mx.aol.com (8.8.8/8.8.8/AOL-5.0.0)
	  with ESMTP id UAA12111;
	  Mon, 19 Nov 2001 20:53:06 -0500 (EST)
Received: from ma.ultranet.com (AC860384.ipt.aol.com [172.134.3.132])
	by logs-wk.proxy.aol.com (8.10.0/8.10.0) with ESMTP id fAK1lfr38594;
	Mon, 19 Nov 2001 20:47:41 -0500 (EST)
Message-ID: <3BF9B6CB.C8C1439F@ma.ultranet.com>
From: David Hudek <dhudek@ma.ultranet.com>
X-Mailer: Mozilla 4.77 [en] (Win95; U)
X-Accept-Language: en
MIME-Version: 1.0
To: isis-wg@spider.juniper.net
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Apparently-From: Hudeks@aol.com
Subject: [Isis-wg] Question about subTLVs 6 & 8 of TLV 22
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Nov 2001 20:50:03 -0500
Content-Transfer-Encoding: 7bit


hi all,

I was starting to look more closely at the draft
ISIS Extensions for Traffic Engineering rfc, and of course,
found myself looking at an old out-of-date copy :-)
I quickly switched to the latest, but then noticed
a change I have a question about.

Back in version 02, when discussing subTLVs 6 and 8
of the Extended IS Reachability TLV (22),
there was a proposed scheme for encoding IP addresses
when the interface in question essentially had none... 
when it was an unnumbered point-to-point link
(although it would only seem to work if the interfaceID
of the unnumbered interface would fit into 16 bits?)
[basically, put the advertising rtrID in the iface addr
subTlv(6), and the low 16 bits of the interface id in 
the nbr addr subTlv(8)]

In the latest version (04, I believe), that text seems to have 
been removed, which begs the question, why?  and how ought one 
encode address info for unnumbered point-to-points?

I skimmed the old mails and didn't notice discussion
about it... if I missed it and this is a boring rehash :-),
can someone just point me to the subject lines
and/or dates?  If not, can anyone shed light on
the rationale for the change and how unnumbered
p2p's should be treated?

Thanks in advance,
dave h
dhudek@ma.ultranet.com
_______________________________________________
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 19 21:55:21 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06296
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 21:03: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 PAA24031;
	Mon, 19 Nov 2001 15:57:45 -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 PAA24019
	for <isis-wg@spider.juniper.net>; Mon, 19 Nov 2001 15:56:15 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fAJNaPK75607
	for <isis-wg@juniper.net>; Mon, 19 Nov 2001 15:36:26 -0800 (PST)
X-JNPR-Received-From: outside
Received: from bridge.axiowave.com ([216.49.69.50]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 19 Nov 2001 15:23:30 -0800
Message-ID: <EB5FFC72F183D411B3820006295734290122FDFC@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Chapman, Ken'" <KChapman@unispherenetworks.com>
Cc: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Subject: RE: [Isis-wg] draft-ietf-isis-wg-mib-05.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 19 Nov 2001 23:23:30.0656 (UTC) FILETIME=[33179E00:01C17151]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Nov 2001 18:24:34 -0500


> RowSatus has no value named "off".
> Do you mean "destroy" or do you mean "notInService" or do you 
> mean both?
> I suspect that both should return inconsistentValue.  
> You really need to make sure you explain the exact expected 
> behaviour for a varbind as complex as RowStatus.
> 	Ken

> > RowStatus is something I didn't create.  See Dave Perkins book for
> > a discussion of this.  Briefly it is used to disambiguate creation
> > and deletion.  

Clearly RowStatus is something I didn't create -or- understand.  

I think you are right: an attempt to take an active entry 
to destroy or notInService should generate inconsistentValue.

     isisManAreaAddrExistState OBJECT-TYPE
         SYNTAX RowStatus
         MAX-ACCESS read-create
         STATUS current
         DESCRIPTION
             "The state of the isisManAreaAddrEntry. This object
             follows the Row Status behavior. If the isisSysAdminState
             for this instance is 'on', and an attempt is made to set
             this object to the value 'destroy' or 'notInService' when
             this is the only isisManAreaAddrEntry for this instance
             in state 'active', then the set should return
inconsistentValue."

         DEFVAL { active }
     ::= { isisManAreaAddrEntry 2 }

- jeff parker
- axiowave networks
_______________________________________________
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 19 21:55:21 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06288
	for <isis-archive@lists.ietf.org>; Mon, 19 Nov 2001 21:03: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 QAA24204;
	Mon, 19 Nov 2001 16:28:46 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA24192
	for <isis-wg@spider.juniper.net>; Mon, 19 Nov 2001 16:27:58 -0800 (PST)
Received: from redd3174.procket.com (IDENT:root@redd3174.procket.com [10.1.3.174])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fAK0878A022985;
	Mon, 19 Nov 2001 16:08:07 -0800 (PST)
From: Henk Smit <henk@procket.com>
Received: (from henk@localhost)
	by redd3174.procket.com (8.12.1/8.12.1) id fAK086DD011110;
	Mon, 19 Nov 2001 16:08:06 -0800
Message-Id: <200111200008.fAK086DD011110@redd3174.procket.com>
Subject: Re: [Isis-wg] draft-ietf-isis-traffic-04.txt
To: hannes@juniper.net (Hannes Gredler)
Cc: swatirstogi@yahoo.com (Swati Rastogi),
        isis-wg@spider.juniper.net (isis-wg)
In-Reply-To: <20010910205543.B18900@juniper.net> from "Hannes Gredler" at Sep 10, 2001 08:55:43 PM
X-Mailer: ELM [version 2.5 PL3]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Nov 2001 16:08:06 -0800 (PST)
Content-Transfer-Encoding: 7bit


  They started with 1,2,3,4,5 .....
 Then people found out that some sub-TLVs were actually not needed, and
 stopped using them in their implementations. But others kept being used.
 We kept those in the draft. And why change the numbers later ? This stuff
 is already deployed, so changing the number is gonna be painful, and serves
 no real purposes.

     Henk.


> [chaos] theory tells .. the best scheme is to use _no_ scheme as
> you cannot maintain it anyway ;-)
> 
> /hannes
> 
> On Mon, Sep 10, 2001 at 07:55:08PM +0530, Swati Rastogi wrote:
> | Hi,
> | I was just going through the above stated draft. I have a very elementary
> | doubt. Why aren't the sub TLVs numbered as 1,2,3,4,5 etc. Why are they
> | numbered as 3,6,8,9,etc. This is the draft that i presume introduced these
> | additional subTLVs, so why aren't the numbers really ordered ?
> | 
> | This is indeed a very foolish doubt .. but am just curious.
> | 
> | Thanks,
> | Swati
> | 
> | 
> | _________________________________________________________
> | Do You Yahoo!?
> | Get your free @yahoo.com address at http://mail.yahoo.com
> | 
> | _______________________________________________
> | 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  Tue Nov 20 10:53:47 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16170
	for <isis-archive@lists.ietf.org>; Tue, 20 Nov 2001 10:53: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 IAA28189;
	Tue, 20 Nov 2001 08:11:45 -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 IAA28177
	for <isis-wg@spider.juniper.net>; Tue, 20 Nov 2001 08:10:36 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fAKFogK03147
	for <isis-wg@juniper.net>; Tue, 20 Nov 2001 07:50:42 -0800 (PST)
X-JNPR-Received-From: outside
Received: from bridge.axiowave.com ([216.49.69.50]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 20 Nov 2001 07:48:56 -0800
Message-ID: <EB5FFC72F183D411B3820006295734290122FE04@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Chapman, Ken'" <KChapman@unispherenetworks.com>
Cc: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Subject: RE: [Isis-wg] draft-ietf-isis-wg-mib-05.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 20 Nov 2001 15:48:57.0468 (UTC) FILETIME=[DD6B23C0:01C171DA]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 20 Nov 2001 10:50:05 -0500

 
> Jeff,
> ...
> The term "instance" is overloaded in the SNMP world (e.g. row 
> instance, object instance), so it might be clearer (to people 
> like me who understand SNMP much better than IS-IS) if you 
> qualified it with something like "protocol instance".
>
> 	Ken

Replaced throughout with the term "instantiation".  

After sending draft 06 to the IESG, I found I had time
to add Notifications (Traps) to the document.  I have
a version of the draft (07) that I am trying to get
reviewed by the SNMP-irati.   The IESG would like to
find a MIB-expert with IS-IS domain knowledge.  If
there is a lurker on this list that this description
fits, perhaps we can discuss what would be needed to
move this closer to something closer to what the 
IESG is looking for.  

- jeff parker
- axiowave networks
_______________________________________________
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 22 00:14:12 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA22102
	for <isis-archive@odin.ietf.org>; Thu, 22 Nov 2001 00:14: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 VAA37069;
	Wed, 21 Nov 2001 21:30:46 -0800 (PST)
Received: from fsnt.future.futsoft.com ([203.197.140.35])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id VAA37054
	for <isis-wg@spider.juniper.net>; Wed, 21 Nov 2001 21:29:45 -0800 (PST)
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001387123@fsnt.future.futsoft.com> for <isis-wg@spider.juniper.net>;
 Thu, 22 Nov 2001 10:52:11 +0530
Received: from ramanann (ramanann.future.futsoft.com [10.20.6.44])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id fAM58wB07287
	for <isis-wg@external.juniper.net>; Thu, 22 Nov 2001 10:38:58 +0530
From: "Ramanan" <ramanann@future.futsoft.com>
To: <isis-wg@spider.juniper.net>
Message-Id: <NFBBLGOAENHGMAPHMHGOGEIDCGAA.ramanann@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Subject: [Isis-wg] Removal of Excess Paths
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 22 Nov 2001 10:46:40 +0530
Content-Transfer-Encoding: 8bit

Hi
Please clarify me regarding the Removal of excess paths.
As per Pg. 15, (Sec. 7.2.7) of ISO 10589 - ver 1992,
~~~~
"When there are more than maximumPathSplits legal paths to a destination,
this set shall be pruned until only maximum-Path Splits remain. The
Intermediate system shall discriminate
based upon:
....
circuit ID: where two or more paths are associated with adjacencies of the
same type, and same neighbour ID, an adjacency with a lower circuit ID is
retained in preference to an adjacency with a higher circuit ID, where
cir-cuit
ID is the value of
· ptPtCircuitID for non-broadcast circuits,
· l1CircuitID for broadcast circuits when running the
Level 1 Decision Process, and
· l2CircuitID for broadcast circuits when running the
Level 2 Decision Process."
~~~~
here I believe isisCircPttoPtCircID (isisCircEntry 22) (Circuit Table MIB
Object) is to be used as the
ptPtCircuitID for non-broadcast circuits to do the removal of excess paths,
...,
(Incidentally this isisCircPttoPtCircID is filled after the negotiation of
the Hello PDUs, hope I'm right here!!!)

BUT,
which MIB object is to be used for the l1CircuitID & l2CircuitID for the
Broadcast Circuits.

correct me if I'm wrong.

Thanks
Regards'
Ramanan

_______________________________________________
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 23 14:24:31 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22259
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 14:24:30 -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 LAA46454;
	Fri, 23 Nov 2001 11:41:15 -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 JAA32606
	for <isis-wg@spider.juniper.net>; Fri, 19 Oct 2001 09:20:35 -0700 (PDT)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f9JG4Vt24632
	for <isis-wg@juniper.net>; Fri, 19 Oct 2001 09:04:31 -0700 (PDT)
X-JNPR-Received-From: outside
Received: from uniwest1.redstonecom.com ([65.194.140.130]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 19 Oct 2001 09:03:42 -0700
Received: by mailwest.unispherenetworks.com with Internet Mail Service (5.5.2653.19)
	id <TGHM0YXH>; Fri, 19 Oct 2001 12:03:58 -0400
Message-ID: <49FF5C6DDBD8D311BBBD009027DE980C031F4368@mailwest.unispherenetworks.com>
From: "Chapman, Ken" <KChapman@unispherenetworks.com>
To: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 19 Oct 2001 16:03:42.0921 (UTC) FILETIME=[9FF88B90:01C158B7]
Subject: [Isis-wg] draft-ietf-isis-wg-mib-05.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 19 Oct 2001 12:03:46 -0400

I'm looking at the ISIS-MIB and think that it would be nice to include UNITS
for many of the time-related objects.
Most of them have the information in the descriptions, but
rsIsisSysIshHoldTime and rsIsisSysIshConfigTimer do not.
Are they in milliseconds?
Thanks.
	Ken
++++++++++++++++++++++++++++++++++++++++++++++
Ken Chapman           Unisphere Networks, Inc.
                      M/S 2056
Tel: +1 978 589 0288  10 Technology Park Drive
Fax: +1 978 589 0800  Westford, MA 01886
Email: KChapman@UnisphereNetworks.com
++++++++++++++++++++++++++++++++++++++++++++++


_______________________________________________
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 23 14:29:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22286
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 14:29:57 -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 LAA46539;
	Fri, 23 Nov 2001 11:48:52 -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 JAA51720
	for <isis-wg@spider.juniper.net>; Mon, 22 Oct 2001 09:41:10 -0700 (PDT)
Received: from pong.juniper.net (pong.juniper.net [207.17.137.102])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f9MGOht05058
	for <isis-wg@juniper.net>; Mon, 22 Oct 2001 09:24:44 -0700 (PDT)
X-JNPR-Received-From: outside
Received: from tcb.net ([205.168.100.1]) by pong.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 22 Oct 2001 09:23:26 -0700
Received: from dog.tcb.net (danny@localhost)
	by tcb.net (8.11.6/8.11.4) with ESMTP id f9MGGwV12786
	for <isis-wg@JUNIPER.NET>; Mon, 22 Oct 2001 10:16:58 -0600
Message-Id: <200110221616.f9MGGwV12786@tcb.net>
X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4
To: isis-wg@juniper.net
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-OriginalArrivalTime: 22 Oct 2001 16:23:26.0843 (UTC) FILETIME=[E0E1F4B0:01C15B15]
Subject: [Isis-wg] FW: draft-ietf-isis-transient-02.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 22 Oct 2001 10:16:58 -0600


FYI...  Only resubmitted to address expiry.  No content 
changes...


danny@dog% diff draft-ietf-isis-transient-01.txt draft-ietf-isis-transient-02.txt
7,8c7,8
< INTERNET DRAFT                                      Amber Networks, Inc.
< July 2001
---
> INTERNET DRAFT                                                       TCB
> October 2001
13c13
<                    <draft-ietf-isis-transient-01.txt>
---
>                    <draft-ietf-isis-transient-02.txt>
58c58
< INTERNET DRAFT                                                 July 2001
---
> INTERNET DRAFT                                              October 2001
114c114
< INTERNET DRAFT                                                 July 2001
---
> INTERNET DRAFT                                              October 2001
170c170
< INTERNET DRAFT                                                 July 2001
---
> INTERNET DRAFT                                              October 2001
226c226
< INTERNET DRAFT                                                 July 2001
---
> INTERNET DRAFT                                              October 2001
282c282
< INTERNET DRAFT                                                 July 2001
---
> INTERNET DRAFT                                              October 2001
322,326c322,326
<    Amber Networks, Inc.
<    48664 Milmont Drive
<    Fremont, CA  94538
<    Phone: 510.687.5226
<    Email: danny@ambernetworks.com
---
>    TCB
>    Phone: 303.470.9257
>    Email: danny@tcb.net

------- Forwarded Message

To: internet-drafts@ietf.org
From: Danny McPherson <danny@tcb.net>
Reply-To: danny@tcb.net
Subject: draft-ietf-isis-transient-02.txt 
Content-Transfer-Encoding: quoted-printable
Date: Mon, 22 Oct 2001 10:14:32 -0600
Sender: danny@dog.tcb.net




Network Working Group                                    Danny McPherson
INTERNET DRAFT                                                       TCB
October 2001



                  IS-IS Transient Blackhole Avoidance
                   <draft-ietf-isis-transient-02.txt>


1. Status of this Memo

   This document is an Internet-Draft and is in full conformance with
   all provisions of Section 10 of RFC 2026.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet- Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt

   The list of Internet-Draft Shadow Directories can be accessed at
        http://www.ietf.org/shadow.html.


2. Abstract

   This document describes a simple, interoperable mechanism that can be
   employed in IS-IS networks in order to decrease data loss associated
   with deterministic blackholing of packets during transient network
   conditions.  The mechanism proposed here requires no IS-IS protocol
   changes and is completely interoperable with the existing IS-IS
   specification.










McPherson, D.                                          	[Page 1]
=0C
INTERNET DRAFT                                              October 2001


3. Introduction

   When an IS-IS router that was previously a transit router becomes
   unavailable as a result of some transient condition such as a reboot,
   other routers within the routing domain must select an alternative
   path to reach destinations which had previously transited the failed
   router.  Presumably, the newly selected router(s) comprising the path
   have been available for some time and, as a result, have complete
   forwarding information bases (FIBs) which contain a full set of
   reachability information for both internal and external (e.g., BGP)
   destination networks.

   When the previously failed router becomes available again, in only a
   few seconds paths that had previously transited the router are again
   selected as the optimal path by the IGP.  As a result, forwarding
   tables are updated and packets are once again forwarded along the
   path.  Unfortunately, external destination reachability information
   (e.g., learned via BGP) is not yet available to the router, and as a
   result, packets bound for destinations not learned via the IGP are
   unnecessarily discarded.

   A simple interoperable mechanism to alleviate the offshoot associated
   with this deterministic behavior is discussed below.


4. Discussion

   This document describes a simple, interoperable mechanism that can be
   employed in IS-IS [1, 2] networks in order to avoid transition to a
   newly available path until other associated routing protocols such as
   BGP have had sufficient time to converge.

   The benefits of such a mechanism can realized when considering the
   following scenario depicted in Figure 1.

















McPherson, D.                                          	[Page 2]
=0C
INTERNET DRAFT                                              October 2001


                     D.1
                      |
                  +-------+
                  | RtrD  |
                  +-------+
                  /      \
                 /        \
            +-------+    +-------+
            | RtrB  |    | RtrC  |
            +-------+    +-------+
                 \        /
                  \      /
                  +-------+
                  | RtrA  |
                  +-------+
                       |
                      S.1

     Figure 1: Example Network Topology



Host S.1 is transmitting data to destination D.1 via a primary path of
RtrA->RtrB->RtrD.  Routers A, B and C learn of reachability to destina=AD=

tion D.1 via BGP from RtrD.  RtrA's primary path to D.1 is selected
because when calculating the path to BGP NEXT_HOP of RtrD the sum of the
IS-IS link metrics on the RtrA-RtrB-RtrD path is less than the sum of
the metrics of the RtrA-RtrC-RtrD path.

Assume RtrB becomes unavailable and as a result the RtrC path to RtrD is
used.  Once RtrA's FIB is updated and it begins forwarding packets to
RtrC everything should behave properly as RtrC has existing forwarding
information regarding destination D.1's availability via BGP NEXT_HOP
RtrD.

Assume now that RtrB comes back online.  In only a few seconds IS-IS
neighbor state has been established with RtrA and RtrD and database syn=AD=

chronization has occurred.  RtrA now realizes that the best path to des=AD=

tination D.1 is via RtrB, and therefore updates it FIB appropriately.
RtrA begins to forward packets destined to D.1 to RtrB.  Though, because
RtrB has yet to establish and synchronization it's BGP neighbor rela=AD
tionship and routing information with RtrD, RtrB has no knowledge
regarding reachability of destination D.1, and therefore discards the
packets received from RtrA destined to D.1.

If RtrB were to temporarily set it's LSP Overload bit while synchroniz=AD=

ing BGP tables with it's neighbors, RtrA would continue to use the work=AD=

ing RtrA->RtrC->RtrD path, and the LSP should only be used to obtain



McPherson, D.                                          	[Page 3]
=0C
INTERNET DRAFT                                              October 2001


reachability to locally connected networks (rather than for calculating
transit paths through the router, as defined in [1]).

However, it should be noted that when RtrB goes away its LSP is still
present in the IS-IS databases of all other routers in the routing
domain. When RtrB comes back it establishes adjacencies. As soon as its
neighbors have an adjacency with RtrB, they will advertise their new
adjacency in their new LSP. The result is that all the other routers
will receive new LSPs from RtrA and RtrD containing the RtrB adjacency,
even though RtrB is still completing its synchronization and therefore
has not yet sent it's new LSP yet.

At this time SPF is computed and everyone will include RtrB in their
tree since they will use the old version of RtrB LSP (the new one has
not yet arrived). Once RtrB has finished establishing all its adjacen=AD
cies, it will then regenerate its LSP and flood it. Then all other
routers within the domain will finally compute SPF with the correct
information.  Only at that time will the Overload bit be taken into
account.

As such, it is recommended that each time a router establishes an adja=AD=

cency, it will update its LSP and flood it immediately, even before
beginning database synchronization. This will allow for the Overload bit
setting to propagate immediately, and remove the potential for an older
version of the reloaded routers LSP to be used.

After synchronization of BGP tables with neighboring routers (or expiry
of some other timer or trigger), RtrB would generate a new LSP, clearing
the Overload bit, and RtrA could again begin using the optimal path via
RtrB.

Typically, in service provider networks IBGP connections are done via
peerings with 'loopback' addresses.  As such, the newly available router
must advertise it's own loopback (or similar) IP address, as well as
associated adjacencies, in order to make the loopbacks accessible to
other routers within the routing domain.  It's because of this that sim=AD=

ply flooding an empty LSP is not sufficient.














McPherson, D.                                          	[Page 4]
=0C
INTERNET DRAFT                                              October 2001


5. Deployment Considerations

   Such a mechanism increases overall network availability and allows
   network operators to alleviate the deterministic blackholing behavior
   introduced in this scenario.  Similar mechanisms [3] have been
   defined for OSPF, though only after realizing the usefulness obtained
   from that of the IS-IS Overload bit technique.

   This mechanism has been deployed in several large IS-IS networks for
   a number of years.

   Triggers for setting the Overload bit as described are left to the
   implementer.  Some potential triggers could perhaps include "N sec=AD
   onds after booting", or "N number of BGP prefixes in the BGP Loc-
   RIB".

   Unlike similar mechanisms employed in [3], if the Overload bit is set
   in a router's LSP, NO transit paths are calculated through the
   router.  As such, if no alternative paths are available to the desti=AD=

   nation network, employing such a mechanism may actually have a nega=AD=

   tive impact on convergence (i.e., the router maintains the only
   available path to reach downstream routers, but the Overload bit dis=AD=

   allows other nodes in the network from calculating paths via the
   router, and as such, no feasible path exists to the routers).

   Finally, if all systems within an IS-IS routing domain haven't imple=AD=

   mented the Overload bit correctly, forwarding loops may occur.


6. Potential Alternatives

   Alternatively, it may be considered more appealing to employ some=AD
   thing more akin to [3] for this purpose.  With this model, during
   transient conditions a node advertises excessively high link metrics
   to serve as an indication to other nodes in the network that paths
   transiting the router are "less desirable" than existing paths.

   The advantage of a metric-based mechanism over the Overload bit mech=AD=

   anism proposed here model is that transit paths may still be calcu=AD
   lated through the router.  Another advantage is that a metric- based
   mechanism does not require that all nodes in the IS-IS domain cor=AD
   rectly implement the Overload bit.

   However, as currently deployed, IS-IS provides for only 6 bits of
   space for link metric allocation, and 10 bits aggregate path metric.
   Though extensions proposed in [4] remove this limitation, they've not
   yet been widely deployed.  As such, there's currently little flexi=AD
   bility when using link metrics for this purpose.  Of course, both



McPherson, D.                                          	[Page 5]
=0C
INTERNET DRAFT                                              October 2001


   methods proposed in this document are backwards-compatible.


7. Security Considerations

   The mechanisms specified in this memo introduces no new security
   issues to IS-IS.


8. Acknowledgements

   The author of this document makes no claim to the originality of the
   idea.  Thanks to Stefano Previdi for valuable feedback on the mecha=AD=

   nism discussed in this document.


9. References

   [1]  ISO, "Intermediate system to Intermediate system routeing
        information exchange protocol for use in conjunction with the
        Protocol for providing the Connectionless-mode Network Service
        (ISO 8473)," ISO/IEC 10589:1992.

   [2]  Callon, R., "OSI IS-IS for IP and Dual Environment," RFC 1195,
        December 1990.

   [3]  Retana et al., "OSPF Stub Router Advertisement", RFC 3137, June
        2001.

   [4] Li, T., Smit, H., "IS-IS extensions for Traffic Engineering",
       Work in Progress.



10. Author's Address

   Danny McPherson
   TCB
   Phone: 303.470.9257
   Email: danny@tcb.net











McPherson, D.                                          	[Page 6]
=0C



------- End of Forwarded Message



_______________________________________________
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 23 14:36:53 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22344
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 14:36:51 -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 LAA46699;
	Fri, 23 Nov 2001 11:54:45 -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 RAA01132
	for <isis-wg@spider.juniper.net>; Tue, 30 Oct 2001 17:32:58 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f9V1FWK88857
	for <isis-wg@juniper.net>; Tue, 30 Oct 2001 17:15:32 -0800 (PST)
X-JNPR-Received-From: outside
Received: from Thor.Adtech-Inc.COM ([63.165.80.10]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 30 Oct 2001 17:14:05 -0800
Received: from apollo.adtech-inc.com (apollo.adtech-inc.com [10.12.0.17])
	by Thor.Adtech-Inc.COM (8.10.2/8.10.2) with ESMTP id f9V1F3R19965
	for <isis-wg@juniper.net>; Tue, 30 Oct 2001 15:15:03 -1000 (HST)
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19)
	id <VWQH3VVK>; Tue, 30 Oct 2001 15:20:36 -1000
Message-ID: <8AC36D3167EED41184C800508BD9540501EE3B53@apollo.adtech-inc.com>
From: "Chan, Chung Ming" <Ming.Chan@spirentcom.com>
To: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Cc: "Chan, Chung Ming" <Ming.Chan@spirentcom.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
X-OriginalArrivalTime: 31 Oct 2001 01:14:05.0156 (UTC) FILETIME=[554CFA40:01C161A9]
Subject: [Isis-wg] Simple questions on the use of Authentication TLVs
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 30 Oct 2001 15:20:35 -1000

All,
I'm new to ISIS and hope some one can answer me the following questions
regarding to the use of Authentication TLV.
Thank you in advance!

I'm working with ISO/IEC 10589:1992 and RFC 1195.

In both spec there is Authentication VLF defined with different Code points,
10 for ISO10589 and 133 for RFC1195.

The questions that I've:

1) If the router is supporting RFC 1195, SHALL it use 133 or 10?  What is
the guideline for using it?
2) Or should the router accept code point 10, if it supports RFC1195?


Thanks,


Ming Chan
_______________________________________________
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 23 14:42:48 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22388
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 14:42: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 LAA46738;
	Fri, 23 Nov 2001 11:59:47 -0800 (PST)
Received: from ghostrider.gredler.at (ghostrider.gredler.at [193.83.223.228])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA71337
	for <isis-wg@spider.juniper.net>; Tue, 9 Oct 2001 02:24:25 -0700 (PDT)
Received: (from hannes@localhost)
	by ghostrider.gredler.at (8.9.3/8.9.3) id LAA19967;
	Tue, 9 Oct 2001 11:09:28 +0200
From: Hannes Gredler <hannes@juniper.net>
To: Chris Sherwin <sherwin@torrentnet.com>
Cc: isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] Status of some drafts
Message-ID: <20011009110928.A19958@juniper.net>
References: <200110082028.f98KSGJ04443@malibu.torrentnet.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <200110082028.f98KSGJ04443@malibu.torrentnet.com>; from sherwin@torrentnet.com on Mon, Oct 08, 2001 at 04:28:16PM -0400
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 9 Oct 2001 11:09:28 +0200

On Mon, Oct 08, 2001 at 04:28:16PM -0400, Chris Sherwin wrote:
| Hi, 
| 
| I am interested in knowing what the status of some work in this group
| is. In particular, I have been browsing the workgroup's mail archive
| and various proceedings trying to figure out what happened to 
| the IS-IS over IPv4 and 3-way handshake efforts. 
| It seems they have expired? They are listed as submitted for RFC status,
| but I cannot find any RFCs, although I can pick up old copies of the
| drafts.

chris,

IS-IS over IP was considered to be uninteresting,
the 3-way draft (at least v2 of the draft) is widely deployed.

/hannes
_______________________________________________
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 23 14:47:18 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22446
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 14:47: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 MAA46883;
	Fri, 23 Nov 2001 12:05:02 -0800 (PST)
Received: from WS0005.indiatimes.com ([203.199.93.15])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA40048
	for <isis-wg@external.juniper.net>; Tue, 6 Nov 2001 03:55:58 -0800 (PST)
Received: from 192.168.57.15 (a2 [192.168.57.22])
	by WS0005.indiatimes.com (8.9.3/8.9.3) with SMTP id QAA11540;
	Tue, 6 Nov 2001 16:56:59 +0530
From: "ramanann" <ramanann@indiatimes.com>
Message-Id: <200111061126.QAA11540@WS0005.indiatimes.com>
To: <isis-wg@spider.juniper.net>, <Radia.Perlman@East.Sun.COM>
CC: <jparker@axiowave.com>
Reply-To: "ramanann"<ramanann@indiatimes.com>
X-URL: http://indiatimes.com
Content-Type: text/plain; charset=us-ascii
Subject: [Isis-wg] Excess Paths Removal in ISIS
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 06 Nov 2001 16:59:01 +0530

Hi 
Please clarify me regarding the Removal of excess paths.
As per Pg. 15, (Sec. 7.2.7) of ISO 10589 - ver 1992,
~~~~
"When there are more than maximumPathSplits legal paths to a destination, this set shall be pruned until only maximum-PathSplits remain. The Intermediate system shall discriminate
based upon:
..
circuit ID: where two or more paths are associated with adjacencies of the same type, and same neighbour ID, an adjacency with a lower circuit ID is retained in prefer-ence to an adjacency with a higher circuit ID, where circuit
ID is the value of
· ptPtCircuitID for non-broadcast circuits,
· l1CircuitID for broadcast circuits when running the
Level 1 Decision Process, and
· l2CircuitID for broadcast circuits when running the
Level 2 Decision Process."
~~~~
here I beleive isisCircPttoPtCircID (isisCircEntry 22) (Circuit Table MIB Object) is to be used as the 
ptPtCircuitID for non-broadcast circuits to do the removal of excess paths, ..., 
(Incidentally this isisCircPttoPtCircID is filled after the negotiation of the Hello PDUs, hope i'm right here!!!)

BUT,
which MIB object is to be used for the l1CircuitID & l2CircuitID for the Broadcast Circuits.

correct me if i'm wrong.

P.S.:- This mail, when sent to the isis-wg is bouncing back as "host not found" !!!

Thanks
Rgds'
Ramanan



Get Your Private, Free E-mail from Indiatimes at http://email.indiatimes.com

 Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from http://www.planetm.co.in

_______________________________________________
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 23 14:53:09 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22565
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 14:53:09 -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 MAA46981;
	Fri, 23 Nov 2001 12:09:41 -0800 (PST)
Received: from venus.postmark.net (venus.postmark.net [207.244.122.71])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id XAA44682
	for <isis-wg@spider.juniper.net>; Tue, 6 Nov 2001 23:55:58 -0800 (PST)
Received: (qmail 22917 invoked by uid 501); 7 Nov 2001 07:13:25 -0000
Message-ID: <20011107071325.22916.qmail@venus.postmark.net>
Received: from 203.197.138.201 by www.postmark.net with HTTP;
	07 Nov 2001 07:13:25 -0000
Mime-Version: 1.0
From: aridaman kaushik <kaushik_ari@postmark.net>
To: isis-wg@spider.juniper.net
Content-Type: text/plain; charset="iso-8859-1"
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 07 Nov 2001 07:13:25 +0000



aridaman kaushik
kaushik_ari@postmark.net
Hi all
    Can anyone help me in clearing my doubt for
draft-ietf-isis-ipv6-02.txt

1. Interface address TLVs in LSP's will contain nonlinklocal
addresses. What are these addresses?
2. How site local adddress will be supported ?

thanks in advance
aridaman


_______________________________________________
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 23 14:58:08 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA22600
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 14:58:08 -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 MAA47134;
	Fri, 23 Nov 2001 12:14:40 -0800 (PST)
Received: from web21104.mail.yahoo.com (web21104.mail.yahoo.com [216.136.227.106])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id XAA88016
	for <isis-wg@spider.juniper.net>; Tue, 13 Nov 2001 23:16:37 -0800 (PST)
Message-ID: <20011114065729.76011.qmail@web21104.mail.yahoo.com>
Received: from [212.25.110.131] by web21104.mail.yahoo.com via HTTP; Tue, 13 Nov 2001 22:57:29 PST
From: Nagasta Bagamba <nagastabagamba@yahoo.com>
Subject: Fwd: FW: [Isis-wg] Overload & Attached bits
To: isis-wg@spider.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 13 Nov 2001 22:57:29 -0800 (PST)

Hello Erez and WG,
I want to make some comments about the 2 first issues
you brought up.

1. Can a router have both bits set at the same time?

I understand you agree the answer for that is Yes.
But, I know at least one major vendor which doesn't
allow to set this 2 bits at the same time. The reason
for that is a kind of a mystery to me...
Does anyone have an idea what that reason might be?

2. Should we consider overloaded routers in our search
for the nearest attached level-2 intermediate system?

You decided that the answer is No. But, I know of at
least 2 major vendors which consider overloaded
routers in the search for the nearest attached level-2
IS.
If vendors-mixture ISIS topology will be built,
routing loops may occure. Does anyone have an idea how
to avoid routing loops in such a topology?

10x,
Nagasta


__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
_______________________________________________
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 23 15:02:20 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA22663
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 15:02:19 -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 MAA47214;
	Fri, 23 Nov 2001 12:19:57 -0800 (PST)
Received: from web21102.mail.yahoo.com (web21102.mail.yahoo.com [216.136.227.104])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id AAA88400
	for <isis-wg@spider.juniper.net>; Wed, 14 Nov 2001 00:53:06 -0800 (PST)
Message-ID: <20011114083357.37226.qmail@web21102.mail.yahoo.com>
Received: from [212.25.110.131] by web21102.mail.yahoo.com via HTTP; Wed, 14 Nov 2001 00:33:57 PST
From: Nagasta Bagamba <nagastabagamba@yahoo.com>
Subject: FW: [Isis-wg] Overload & Attached bits
To: isis-wg@spider.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 14 Nov 2001 00:33:57 -0800 (PST)


Hello Erez and WG,
I want to make some comments about the 2 first issues
you brought up.

1. Can a router have both bits set at the same time?

I understand you agree the answer for that is Yes.
But, I know of at least one major vendor which doesn't
allow to set this 2 bits at the same time. The reason
for that is a kind of a mystery to me...
Does anyone have an idea what the reason for that may
be?

2. Should we consider overloaded routers in our search
for the nearest attached level-2 intermediate system?

You decided that the answer is No. But, I know of at
least 2 major vendors which consider overloaded
routers in the search for the nearest attached level-2
IS.
If vendors-mixture ISIS topology will be built,
routing loops may occure. Does anyone have an idea how
to avoid routing loops in such a topology?

10x,
Nagasta



__________________________________________________
Do You Yahoo!?
Find the one for you at Yahoo! Personals
http://personals.yahoo.com
_______________________________________________
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 23 15:32:05 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23072
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 15:32:05 -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 MAA47569;
	Fri, 23 Nov 2001 12:48:48 -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 GAA27731
	for <isis-wg@spider.juniper.net>; Tue, 20 Nov 2001 06:15:59 -0800 (PST)
Received: from pong.juniper.net (pong.juniper.net [207.17.137.102])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fAKDu6K98522
	for <isis-wg@juniper.net>; Tue, 20 Nov 2001 05:56:06 -0800 (PST)
X-JNPR-Received-From: outside
Received: from uniwest1.redstonecom.com ([65.194.140.130]) by pong.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Tue, 20 Nov 2001 05:54:40 -0800
Received: by mailwest.unispherenetworks.com with Internet Mail Service (5.5.2653.19)
	id <TGHNB5NR>; Tue, 20 Nov 2001 08:55:59 -0500
Message-ID: <49FF5C6DDBD8D311BBBD009027DE980C031F442C@mailwest.unispherenetworks.com>
From: "Chapman, Ken" <KChapman@unispherenetworks.com>
To: "'Jeff Parker'" <jparker@axiowave.com>
Cc: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Subject: RE: [Isis-wg] draft-ietf-isis-wg-mib-05.txt
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 20 Nov 2001 13:54:40.0858 (UTC) FILETIME=[E68F7BA0:01C171CA]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 20 Nov 2001 08:55:17 -0500

Jeff,
That is much clearer, thanks.  
I have one more little nit.
The term "instance" is overloaded in the SNMP world (e.g. row instance,
object instance), so it might be clearer (to people like me who understand
SNMP much better than IS-IS) if you qualified it with something like
"protocol instance".
I realize that it is made clear in the comment section just before the
table, but there has been a lot of "push" in the SNMP standards area to make
sure that the DESCRIPTION clauses contain complete and accurate description,
since the comments sections are not "tied" to any object and therefore are
not considered to be "normative".
Also, this may not be the only object that suffers from this problem; it
just happens to be the one I noticed. :^)
Thanks.
	Ken

> -----Original Message-----
> From: Jeff Parker [mailto:jparker@axiowave.com]
> Sent: Monday, November 19, 2001 6:25 PM
> To: Chapman, Ken
> Cc: 'isis-wg@juniper.net'
> Subject: RE: [Isis-wg] draft-ietf-isis-wg-mib-05.txt
> 
> 
> 
> > RowSatus has no value named "off".
> > Do you mean "destroy" or do you mean "notInService" or do you 
> > mean both?
> > I suspect that both should return inconsistentValue.  
> > You really need to make sure you explain the exact expected 
> > behaviour for a varbind as complex as RowStatus.
> > 	Ken
> 
> > > RowStatus is something I didn't create.  See Dave Perkins book for
> > > a discussion of this.  Briefly it is used to disambiguate creation
> > > and deletion.  
> 
> Clearly RowStatus is something I didn't create -or- understand.  
> 
> I think you are right: an attempt to take an active entry 
> to destroy or notInService should generate inconsistentValue.
> 
>      isisManAreaAddrExistState OBJECT-TYPE
>          SYNTAX RowStatus
>          MAX-ACCESS read-create
>          STATUS current
>          DESCRIPTION
>              "The state of the isisManAreaAddrEntry. This object
>              follows the Row Status behavior. If the isisSysAdminState
>              for this instance is 'on', and an attempt is made to set
>              this object to the value 'destroy' or 'notInService' when
>              this is the only isisManAreaAddrEntry for this instance
>              in state 'active', then the set should return
> inconsistentValue."
> 
>          DEFVAL { active }
>      ::= { isisManAreaAddrEntry 2 }
> 
> - jeff parker
> - axiowave networks
> 
_______________________________________________
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 23 23:55:18 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA29231
	for <isis-archive@odin.ietf.org>; Fri, 23 Nov 2001 23:55: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 VAA49632;
	Fri, 23 Nov 2001 21:08:48 -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 VAA49620
	for <isis-wg@spider.juniper.net>; Fri, 23 Nov 2001 21:07:39 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fAO4lKK29529
	for <isis-wg@juniper.net>; Fri, 23 Nov 2001 20:47:20 -0800 (PST)
X-JNPR-Received-From: outside
Received: from smtp015.mail.yahoo.com ([216.136.173.59]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 23 Nov 2001 20:38:37 -0800
Received: from unknown (HELO firewall) (203.200.20.224)
  by smtp.mail.vip.sc5.yahoo.com with SMTP; 24 Nov 2001 04:39:56 -0000
Message-ID: <021b01c174a2$4cfdccf0$b4036c6b@Manav>
From: "Swati Rastogi" <swatirstogi@yahoo.com>
To: "Mijung Yang" <mjyang@etri.re.kr>, <isis-wg@juniper.net>, <isis@merit.edu>,
        <isis-wg-request@spider.juniper.net>
References: <000f01c134e5$fd8cc1e0$37c2fe81@etri.re.kr>
Subject: Re: [Isis-wg] Question about Internet Draft of IS-IS TE extension
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0218_01C174D0.66A3B970"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-OriginalArrivalTime: 24 Nov 2001 04:38:37.0390 (UTC) FILETIME=[E20946E0:01C174A1]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 24 Nov 2001 10:11:36 +0530

This is a multi-part message in MIME format.

------=_NextPart_000_0218_01C174D0.66A3B970
Content-Type: text/plain;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

Hi Yang,
The prefix length tells us of the network mask which has a value between =
0 and 32. Thus 6 bits have been reserved for it.=20
0-4 octets are reserved for the actual IP prefix which will be =
considered till the value of the prefix length specified in the prefix =
length.

I hope this helps.

Regards,
Manav


  ----- Original Message -----=20
  From: Mijung Yang=20
  To: isis-wg-request@spider.juniper.net ; isis-wg@juniper.net ; =
isis@merit.edu=20
  Sent: Tuesday, September 04, 2001 7:34 AM
  Subject: [Isis-wg] Question about Internet Draft of IS-IS TE extension



  Dear..

  I have some questions about draft-ietf-isis-traffic-04.txt.
  =20
  First,
  I don't know exact meaning prefix length field(6bits) and IPv4 prefix =
field(0~4octets)
  in the extended IP reachability TLV.
  I think that the meaning of two fields is same.
  And, How can I know the reachable network?
  Please, let me inform the exact meaning and usage of the two fields=20
  =20
  Second,
  I want to confirm that sub-TLV 6 and sub-TLV 8 in the extended IS =
reachability TLV=20
  indicate two end address of the link and this address is router ID =
address or not.

  Awaiting the pleasure of your reply.=20
  Regards,

  -----------------
  Mijung Yang / ETRI=20
  TEL: +82-42-860-4922=20
  FAX: +82-42-860-5440=20
  E-mail: mjyang@etri.re.kr=20


------=_NextPart_000_0218_01C174D0.66A3B970
Content-Type: text/html;
	charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dks_c_5601-1987" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3103.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2><EM>Hi Yang,</EM></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><EM>The prefix length tells us of the =
network mask=20
which has a value between 0 and 32. Thus 6 bits have been reserved for =
it.=20
</EM></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><EM>0-4 octets are reserved for the =
actual IP=20
prefix which will be considered till the value of the prefix length =
specified in=20
the prefix length.</EM></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><EM>I hope this =
helps.</EM></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2><EM>Regards,</EM></FONT></DIV>
<DIV><FONT face=3DArial size=3D2><EM>Manav</EM></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp;</DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
  <DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
  <DIV=20
  style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
  <A href=3D"mailto:mjyang@etri.re.kr" title=3Dmjyang@etri.re.kr>Mijung =
Yang</A>=20
  </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
  href=3D"mailto:isis-wg-request@spider.juniper.net"=20
  =
title=3Disis-wg-request@spider.juniper.net>isis-wg-request@spider.juniper=
.net</A>=20
  ; <A href=3D"mailto:isis-wg@juniper.net"=20
  title=3Disis-wg@juniper.net>isis-wg@juniper.net</A> ; <A=20
  href=3D"mailto:isis@merit.edu" =
title=3Disis@merit.edu>isis@merit.edu</A> </DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Tuesday, September 04, =
2001 7:34=20
  AM</DIV>
  <DIV style=3D"FONT: 10pt arial"><B>Subject:</B> [Isis-wg] Question =
about=20
  Internet Draft of IS-IS TE extension</DIV>
  <DIV><BR></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT size=3D2>Dear..</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT size=3D2>I have some questions about=20
  draft-ietf-isis-traffic-04.txt.</FONT></DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>First,</FONT></DIV>
  <DIV><FONT size=3D2>I don't know exact meaning prefix length =
field(6bits) and=20
  IPv4 prefix field(0~4octets)</FONT></DIV>
  <DIV><FONT size=3D2>in the extended IP reachability TLV.</FONT></DIV>
  <DIV><FONT size=3D2>I think that the meaning of two fields is =
same.</FONT></DIV>
  <DIV><FONT size=3D2>And, How can&nbsp;I know the&nbsp;reachable=20
  network?</FONT></DIV>
  <DIV><FONT size=3D2>Please, let me inform the exact meaning and usage =
of the two=20
  fields</FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2></FONT>&nbsp;</DIV>
  <DIV><FONT size=3D2>Second,</FONT></DIV>
  <DIV><FONT size=3D2>I want to confirm that sub-TLV 6 and sub-TLV 8 in =
the=20
  extended IS reachability TLV </FONT></DIV>
  <DIV><FONT size=3D2>indicate two end address of the link and this =
address is=20
  router ID address or not.</FONT></DIV>
  <DIV>&nbsp;</DIV>
  <DIV><FONT size=3D2><FONT size=3D2>Awaiting the pleasure of your =
reply.</FONT>=20
  <DIV><FONT size=3D2>Regards,<BR></FONT></FONT><FONT =
size=3D2></FONT></DIV>
  <DIV><FONT size=3D2>-----------------<BR>Mijung Yang / ETRI <BR>TEL:=20
  +82-42-860-4922 <BR>FAX: +82-42-860-5440 <BR>E-mail: <A=20
  href=3D"mailto:mjyang@etri.re.kr">mjyang@etri.re.kr</A>=20
<BR></DIV></DIV></BLOCKQUOTE></FONT></BODY></HTML>

------=_NextPart_000_0218_01C174D0.66A3B970--


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com

_______________________________________________
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 24 17:22:29 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25608
	for <isis-archive@odin.ietf.org>; Sat, 24 Nov 2001 17:22:28 -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 OAA55833;
	Sat, 24 Nov 2001 14:32:47 -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 OAA55819
	for <isis-wg@spider.juniper.net>; Sat, 24 Nov 2001 14:31:11 -0800 (PST)
Received: from pong.juniper.net (pong.juniper.net [207.17.137.102])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fAOMAlK43661
	for <isis-wg@juniper.net>; Sat, 24 Nov 2001 14:10:47 -0800 (PST)
X-JNPR-Received-From: outside
Received: from cisco.com ([144.254.15.68]) by pong.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Sat, 24 Nov 2001 14:08:27 -0800
Received: from SPREVIDI-W2K1.cisco.com (sprevidi-isdn-home.cisco.com [10.49.0.58])
	by cisco.com (8.8.8+Sun/8.8.8) with ESMTP id XAA14592;
	Sat, 24 Nov 2001 23:09:39 +0100 (MET)
Message-Id: <4.3.2.7.2.20011124230705.03844e60@brussels.cisco.com>
X-Sender: sprevidi@brussels.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: prz@net4u.ch, isis-wg@juniper.net
From: stefano previdi <sprevidi@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-OriginalArrivalTime: 24 Nov 2001 22:08:27.0342 (UTC) FILETIME=[8AF92EE0:01C17534]
Subject: [Isis-wg] IETF meeting ?
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 24 Nov 2001 23:09:40 +0100

Hi,

are we going to have an isis-wg meeting in SLC ?

thanks.

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  Sun Nov 25 04:40:57 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA18668
	for <isis-archive@odin.ietf.org>; Sun, 25 Nov 2001 04:40: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 BAA58536;
	Sun, 25 Nov 2001 01:57:47 -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 BAA58524
	for <isis-wg@spider.juniper.net>; Sun, 25 Nov 2001 01:56:07 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fAP9ZeK50719
	for <isis-wg@juniper.net>; Sun, 25 Nov 2001 01:35:40 -0800 (PST)
X-JNPR-Received-From: outside
Received: from miata.procket.com ([209.140.237.2]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Sun, 25 Nov 2001 00:34:06 -0800
Received: from alpha-tli.procket.com (IDENT:root@alpha-tli.procket.com [10.2.3.1])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fAP8Ym8A004758;
	Sun, 25 Nov 2001 00:34:49 -0800 (PST)
Received: (from tli@localhost)
	by alpha-tli.procket.com (8.12.1/8.12.1) id fAP8YhfL028180;
	Sun, 25 Nov 2001 00:34:43 -0800
From: Tony Li <tli@procket.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15360.44323.591982.976648@alpha-tli.procket.com>
To: stefano previdi <sprevidi@cisco.com>
Cc: prz@net4u.ch, isis-wg@juniper.net
Subject: [Isis-wg] IETF meeting ?
In-Reply-To: <4.3.2.7.2.20011124230705.03844e60@brussels.cisco.com>
References: <4.3.2.7.2.20011124230705.03844e60@brussels.cisco.com>
X-Mailer: VM 6.92 under Emacs 20.5.1
X-OriginalArrivalTime: 25 Nov 2001 08:34:06.0843 (UTC) FILETIME=[F24274B0:01C1758B]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 25 Nov 2001 00:34:43 -0800
Content-Transfer-Encoding: 7bit


 | are we going to have an isis-wg meeting in SLC ?


Not planning on it.

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  Sun Nov 25 18:21:26 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA25621
	for <isis-archive@lists.ietf.org>; Sun, 25 Nov 2001 18:21:25 -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 PAA61799;
	Sun, 25 Nov 2001 15:31:48 -0800 (PST)
Received: from Thor.Adtech-Inc.COM (Thor.Adtech-Inc.COM [63.165.80.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA61787
	for <isis-wg@spider.juniper.net>; Sun, 25 Nov 2001 15:30:02 -0800 (PST)
Received: from apollo.adtech-inc.com (apollo.adtech-inc.com [10.12.0.17])
	by Thor.Adtech-Inc.COM (8.11.6/8.11.6) with ESMTP id fAPN9T510330
	for <isis-wg@external.juniper.net>; Sun, 25 Nov 2001 13:09:30 -1000 (HST)
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19)
	id <W87397WR>; Sun, 25 Nov 2001 13:15:09 -1000
Message-ID: <8AC36D3167EED41184C800508BD9540501EE3BEB@apollo.adtech-inc.com>
From: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@SpirentCom.COM>
To: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Cc: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@SpirentCom.COM>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Isis-wg] Protocols Supported field in pseudonode LSP
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 25 Nov 2001 13:15:08 -1000

Hi,

I found out that in one vendor's pseudonode LSPs, there is no "Protocols
Supported" field included; but it includes the field in the non-pseudonode
LSPs.

Shall the Protocols Supported field MUST be included in pseudonode LSP
according to RFC 1195?

Not sure if there is any reason for that particular vender for doing it.

Could someone please verify this ?

RFC 1195 Section 3.1, paragraph 3:
"IP-capable (i.e., all IP-only and dual) routers need to know what network
layer protocols are sup-ported
by other routers in their area. This information is made available by
inclusion of a "proto-cols
supported" field in all IS-IS Hello and Link State Packets. This field makes
use of the NL-PID
(Network Layer Protocol Identifier), which is a one-octet value assigned by
ISO to identify
network level protocols. NLPID values have been assigned to ISO 8473 and to
IP."


Thanks,


Ming Chan
_______________________________________________
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 25 20:13:23 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA26548
	for <isis-archive@lists.ietf.org>; Sun, 25 Nov 2001 20:13:21 -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 RAA62322;
	Sun, 25 Nov 2001 17:28:46 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id RAA62310
	for <isis-wg@spider.juniper.net>; Sun, 25 Nov 2001 17:27:22 -0800 (PST)
Received: from alpha-tli.procket.com (IDENT:root@alpha-tli.procket.com [10.2.3.1])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fAQ16m8A015333;
	Sun, 25 Nov 2001 17:06:48 -0800 (PST)
Received: (from tli@localhost)
	by alpha-tli.procket.com (8.12.1/8.12.1) id fAQ16mRU005171;
	Sun, 25 Nov 2001 17:06:48 -0800
From: Tony Li <tli@Procket.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15361.38312.708556.117236@alpha-tli.procket.com>
To: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>
Cc: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Subject: [Isis-wg] Protocols Supported field in pseudonode LSP
In-Reply-To: <8AC36D3167EED41184C800508BD9540501EE3BEB@apollo.adtech-inc.com>
References: <8AC36D3167EED41184C800508BD9540501EE3BEB@apollo.adtech-inc.com>
X-Mailer: VM 6.92 under Emacs 20.5.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 25 Nov 2001 17:06:48 -0800
Content-Transfer-Encoding: 7bit


 | I found out that in one vendor's pseudonode LSPs, there is no "Protocols
 | Supported" field included; but it includes the field in the non-pseudonode
 | LSPs.
 | 
 | Shall the Protocols Supported field MUST be included in pseudonode LSP
 | according to RFC 1195?
 | 
 | Not sure if there is any reason for that particular vender for doing it.
 | 
 | Could someone please verify this ?
 | 
 | RFC 1195 Section 3.1, paragraph 3:
 | "IP-capable (i.e., all IP-only and dual) routers need to know what network
 | layer protocols are sup-ported
 | by other routers in their area. This information is made available by
 | inclusion of a "proto-cols
 | supported" field in all IS-IS Hello and Link State Packets. This field makes
 | use of the NL-PID
 | (Network Layer Protocol Identifier), which is a one-octet value assigned by
 | ISO to identify
 | network level protocols. NLPID values have been assigned to ISO 8473 and to
 | IP."


Interesting question.

Well, the pseudonode LSP is really there to represent the broadcast medium,
not any particular router.  And since the broadcast medium is presumably
protocol independent, it doesn't seem like it actually conveys any useful
information.

Thus, IMHO, it would make sense if implementations ignored the Procotols
Supported TLV in a pseudonode LSP and not require it be present.

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  Sun Nov 25 21:28:43 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA26905
	for <isis-archive@lists.ietf.org>; Sun, 25 Nov 2001 21:28:43 -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 SAA62662;
	Sun, 25 Nov 2001 18:42:47 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA62650
	for <isis-wg@spider.juniper.net>; Sun, 25 Nov 2001 18:41:44 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fAQ2L7T27330;
	Sun, 25 Nov 2001 21:21:08 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (rtp-vpn2-245.cisco.com [10.82.240.245])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGD09278;
	Sun, 25 Nov 2001 21:21:03 -0500 (EST)
Message-Id: <4.3.2.7.2.20011125210113.019c4e20@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Tony Li <tli@procket.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
In-Reply-To: <15361.38312.708556.117236@alpha-tli.procket.com>
References: <8AC36D3167EED41184C800508BD9540501EE3BEB@apollo.adtech-inc.com>
 <8AC36D3167EED41184C800508BD9540501EE3BEB@apollo.adtech-inc.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 25 Nov 2001 21:20:50 -0500


I agree with Tony.  There are some additional things to consider,
though.

In accordance with RFC 1195, an implementation doesn't need
to consult an LSP's supported protocols option when running SPF
except for links to end systems, and a pseudonode LSP should have
only links between intermediate systems.  (Rather than relying on
the protos supported option, RFC 1195 relies on the deployment
rules.)

My understanding is that some routers do take the protos-supported
option when running SPF.  This allows some relaxation of the deployment
rules.  There is no interoperability problem, because any strict
implementation won't work anyway, in situations where this modification
helps.

However, in networks where this modification is being used, and
mixed networks don't meet the deployment requirements in 1195,
will it be important to make sure the designated router is a dual
router?  I can't find anything in 1195 that says to check protos-
supported when bringing up an adjacency.  If for any reason a
system would not form an adjacency with a router with which it
shared no protocols, that would cause a problem in the pseudonode
LSPs.  Hopefully this isn't a problem.

Regards,
Jeff

PS:  I don't work in IS-IS at Cisco.  My comments do not necessarily
reflect Cisco's opinions and I have no detailed knowledge of the Cisco
IS-IS implementation.




At 08:06 PM 11/25/2001, Tony Li wrote:

> | I found out that in one vendor's pseudonode LSPs, there is no "Protocols
> | Supported" field included; but it includes the field in the non-pseudonode
> | LSPs.
> | 
> | Shall the Protocols Supported field MUST be included in pseudonode LSP
> | according to RFC 1195?
> | 
> | Not sure if there is any reason for that particular vender for doing it.
> | 
> | Could someone please verify this ?
> | 
> | RFC 1195 Section 3.1, paragraph 3:
> | "IP-capable (i.e., all IP-only and dual) routers need to know what network
> | layer protocols are sup-ported
> | by other routers in their area. This information is made available by
> | inclusion of a "proto-cols
> | supported" field in all IS-IS Hello and Link State Packets. This field makes
> | use of the NL-PID
> | (Network Layer Protocol Identifier), which is a one-octet value assigned by
> | ISO to identify
> | network level protocols. NLPID values have been assigned to ISO 8473 and to
> | IP."
>
>
>Interesting question.
>
>Well, the pseudonode LSP is really there to represent the broadcast medium,
>not any particular router.  And since the broadcast medium is presumably
>protocol independent, it doesn't seem like it actually conveys any useful
>information.
>
>Thus, IMHO, it would make sense if implementations ignored the Procotols
>Supported TLV in a pseudonode LSP and not require it be present.
>
>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 26 06:18:49 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19677
	for <isis-archive@lists.ietf.org>; Mon, 26 Nov 2001 06:18:49 -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 DAA64953;
	Mon, 26 Nov 2001 03:36:47 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA64941
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 03:35:27 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fAQBEl227401
	for <isis-wg@juniper.net>; Mon, 26 Nov 2001 03:14:52 -0800 (PST)
X-JNPR-Received-From: outside
Received: from ietf.org ([132.151.1.176]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 26 Nov 2001 03:13:12 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA19023;
	Mon, 26 Nov 2001 06:14:30 -0500 (EST)
Message-Id: <200111261114.GAA19023@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
X-OriginalArrivalTime: 26 Nov 2001 11:13:12.0125 (UTC) FILETIME=[561AA6D0:01C1766B]
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-mib-06.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 06:14:30 -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		: Management Information Base for IS-IS
	Author(s)	: J. Parker
	Filename	: draft-ietf-isis-wg-mib-06.txt
	Pages		: 65
	Date		: 21-Nov-01
	
This document describes a management information base for the IS-IS
Routing protocol, as described in ISO 10589 [2], when it is used to
construct routing tables for IP networks, as described in RFC 1195
[RFC1195].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-wg-mib-06.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-isis-wg-mib-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-isis-wg-mib-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<20011121141056.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-isis-wg-mib-06.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-isis-wg-mib-06.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20011121141056.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 26 12:04:47 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12473
	for <isis-archive@lists.ietf.org>; Mon, 26 Nov 2001 12:04: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 JAA66386;
	Mon, 26 Nov 2001 09:17:48 -0800 (PST)
Received: from Thor.Adtech-Inc.COM (Thor.Adtech-Inc.COM [63.165.80.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA66374
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 09:16:55 -0800 (PST)
Received: from apollo.adtech-inc.com (apollo.adtech-inc.com [10.12.0.17])
	by Thor.Adtech-Inc.COM (8.11.6/8.11.6) with ESMTP id fAQGuG502859;
	Mon, 26 Nov 2001 06:56:17 -1000 (HST)
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19)
	id <W87398JW>; Mon, 26 Nov 2001 07:01:56 -1000
Message-ID: <8AC36D3167EED41184C800508BD9540501EE3BED@apollo.adtech-inc.com>
From: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@SpirentCom.COM>
To: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Cc: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@SpirentCom.COM>,
        "'Les  Ginsberg'" <ginsberg@pluris.com>,
        "'Jeff Learman'"
	 <jlearman@cisco.com>, Tony Li <tli@procket.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 07:01:52 -1000

All,

	Another role for the inclusion of "Protocols Supported" field is to
signal the other routers that the router originated the LSP is IP capable (
As I understood it from RFC 1195 Section 5.2, paragraph 2.) 
	Would it be from this point of view that the "Protocols Supported"
field is necessary since "logically" pseudo-node LSP is from the
Designated-Router to all of its neighbors?
The field tells all of its neighbors that it is IP capable.

	Thanks,


Ming Chan


-----Original Message-----
From: Les Ginsberg [mailto:ginsberg@pluris.com]
Sent: Monday, November 26, 2001 2:23 AM
To: 'Jeff Learman'; Tony Li
Cc: Chan, Chung Ming (Adtech ENG); 'isis-wg@external.juniper.net'
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP


It is true that RFC 1195 does not explicitly direct ISs to reject
adjacencies with neighbors who do not match protocols supported. In most
cases we would be better off w/o such a neighbor - it would prevent needless
flooding of LSPs which contained no useable routing information. However, on
a "misconfigured" LAN, if some combination of IP only and OSI-only routers
exist - the fact that all routers will form adjacencies is a benefit in that
only a single DIS will be elected. The unfortunate part is that LSPs from
OSI-only routers will take up resources in IP-only routers and vice-versa.

This makes it important to check the protocols supported option in
non-pseudo-node LSPs so as to avoid using an OSI-only router as a transit
router for IP traffic (and vice versa...). LSPs from a router which does not
advertise support for a particular protocol should be ignored during SPF.

The same check in pseudo-node LSPs, as Tony has pointed out, is not
important since the pseudo-node LSP only has information about routers
connected to the LAN, not what destinations are reachable via those routers.

This raises the point that an alarm associated with the formation of an
adjacency with a protocol-wise incompatible neighbor as well as an alarm
associated with reception of a non-pseudo-node LSP with incompatible
protocols would be helpful. (Jeff Parker - are you listening?)

   Les

> -----Original Message-----
> From: Jeff Learman [mailto:jlearman@cisco.com]
> Sent: Sunday, November 25, 2001 6:21 PM
> To: Tony Li
> Cc: Chan, Chung Ming (Adtech ENG); 'isis-wg@external.juniper.net'
> Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
>
>
>
> I agree with Tony.  There are some additional things to consider,
> though.
>
> In accordance with RFC 1195, an implementation doesn't need
> to consult an LSP's supported protocols option when running SPF
> except for links to end systems, and a pseudonode LSP should have
> only links between intermediate systems.  (Rather than relying on
> the protos supported option, RFC 1195 relies on the deployment
> rules.)
>
> My understanding is that some routers do take the protos-supported
> option when running SPF.  This allows some relaxation of the
> deployment
> rules.  There is no interoperability problem, because any strict
> implementation won't work anyway, in situations where this
> modification
> helps.
>
> However, in networks where this modification is being used, and
> mixed networks don't meet the deployment requirements in 1195,
> will it be important to make sure the designated router is a dual
> router?  I can't find anything in 1195 that says to check protos-
> supported when bringing up an adjacency.  If for any reason a
> system would not form an adjacency with a router with which it
> shared no protocols, that would cause a problem in the pseudonode
> LSPs.  Hopefully this isn't a problem.
>
> Regards,
> Jeff
>
> PS:  I don't work in IS-IS at Cisco.  My comments do not necessarily
> reflect Cisco's opinions and I have no detailed knowledge of the Cisco
> IS-IS implementation.
>
>
>
>
> At 08:06 PM 11/25/2001, Tony Li wrote:
>
> > | I found out that in one vendor's pseudonode LSPs, there
> is no "Protocols
> > | Supported" field included; but it includes the field in
> the non-pseudonode
> > | LSPs.
> > |
> > | Shall the Protocols Supported field MUST be included in
> pseudonode LSP
> > | according to RFC 1195?
> > |
> > | Not sure if there is any reason for that particular
> vender for doing it.
> > |
> > | Could someone please verify this ?
> > |
> > | RFC 1195 Section 3.1, paragraph 3:
> > | "IP-capable (i.e., all IP-only and dual) routers need to
> know what network
> > | layer protocols are sup-ported
> > | by other routers in their area. This information is made
> available by
> > | inclusion of a "proto-cols
> > | supported" field in all IS-IS Hello and Link State
> Packets. This field makes
> > | use of the NL-PID
> > | (Network Layer Protocol Identifier), which is a one-octet
> value assigned by
> > | ISO to identify
> > | network level protocols. NLPID values have been assigned
> to ISO 8473 and to
> > | IP."
> >
> >
> >Interesting question.
> >
> >Well, the pseudonode LSP is really there to represent the
> broadcast medium,
> >not any particular router.  And since the broadcast medium
> is presumably
> >protocol independent, it doesn't seem like it actually
> conveys any useful
> >information.
> >
> >Thus, IMHO, it would make sense if implementations ignored
> the Procotols
> >Supported TLV in a pseudonode LSP and not require it be present.
> >
> >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
>
_______________________________________________
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 26 13:20:16 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18189
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 13:20:14 -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 KAA66768;
	Mon, 26 Nov 2001 10:37:48 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA66756
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 10:36:09 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fAQIFS233318
	for <isis-wg@juniper.net>; Mon, 26 Nov 2001 10:15:32 -0800 (PST)
X-JNPR-Received-From: outside
Received: from bridge.axiowave.com ([216.49.69.50]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 26 Nov 2001 10:13:50 -0800
Message-ID: <EB5FFC72F183D411B3820006295734290122FE3C@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Chapman, Ken'" <KChapman@unispherenetworks.com>,
        "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Subject: RE: [Isis-wg] draft-ietf-isis-wg-mib-05.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 26 Nov 2001 18:13:51.0156 (UTC) FILETIME=[19BD2740:01C176A6]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 13:15:00 -0500

> I'm looking at the ISIS-MIB and think that it would be nice 
> to include UNITS
> for many of the time-related objects.
> Most of them have the information in the descriptions, but
> rsIsisSysIshHoldTime and rsIsisSysIshConfigTimer do not.
> Are they in milliseconds?
> Thanks.

> Ken Chapman           Unisphere Networks, Inc.


Ken -
	Thanks - I have updated the description of 
isisISAdjHoldTimer.  However, I can't find anything 
close to rsIsisSysIshConfigTimer.  Come again?

- jeff parker


     isisISAdjHoldTimer OBJECT-TYPE
         SYNTAX Integer32 (1..65535)
         MAX-ACCESS read-only
         STATUS current
         DESCRIPTION
             "The holding time in seconds for this adjacency.
              This value is based on received IIH PDUs and
              the elapsed time since receipt.
         REFERENCE "{ISIS.aoi holdingTimer (85)}"
     ::= { isisISAdjEntry 7 }

     
_______________________________________________
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 26 13:28:26 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18756
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 13:28:25 -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 KAA66818;
	Mon, 26 Nov 2001 10:44:47 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA66789
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 10:41:05 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fAQIKR233414
	for <isis-wg@juniper.net>; Mon, 26 Nov 2001 10:20:27 -0800 (PST)
X-JNPR-Received-From: outside
Received: from bridge.axiowave.com ([216.49.69.50]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 26 Nov 2001 10:18:42 -0800
Message-ID: <EB5FFC72F183D411B3820006295734290122FE3D@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Chan, Chung Ming'" <Ming.Chan@spirentcom.com>,
        "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Subject: RE: [Isis-wg] Simple questions on the use of Authentication TLVs
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-OriginalArrivalTime: 26 Nov 2001 18:18:43.0718 (UTC) FILETIME=[C81E9260:01C176A6]
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 13:19:55 -0500

> All,
> I'm new to ISIS and hope some one can answer me the following 
> questions
> regarding to the use of Authentication TLV.
> Thank you in advance!
> 
> I'm working with ISO/IEC 10589:1992 and RFC 1195.
> 
> In both spec there is Authentication VLF defined with 
> different Code points,
> 10 for ISO10589 and 133 for RFC1195.
> 
> The questions that I've:
> 
> 1) If the router is supporting RFC 1195, SHALL it use 133 or 
> 10?  What is
> the guideline for using it?
> 2) Or should the router accept code point 10, if it supports RFC1195?
> 
> 
> Thanks,
> 
> 
> Ming Chan

Ming -
	You may have received a private reply, but I don't see
a response with this subject to the list.  
	Have you had a look at the Internet Draft 
"IS-IS Cryptographic Authentication"?  You will find
a reference to this below, and also off the following
ietf page for the IS-IS workgroup.  

http://ietf.org/html.charters/isis-charter.html

http://ietf.org/internet-drafts/draft-ietf-isis-hmac-03.txt

- jeff parker
- axiowave networks
_______________________________________________
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 26 14:56:43 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25404
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 14:56:40 -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 LAA67190;
	Mon, 26 Nov 2001 11:57:47 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA67178
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 11:56:35 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id XAA25132;
	Sun, 25 Nov 2001 23:23:29 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <VMHL138V>; Sun, 25 Nov 2001 23:23:29 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F5E6@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Jeff Learman'" <jlearman@cisco.com>, Tony Li <tli@procket.com>
Cc: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 25 Nov 2001 23:23:19 -0800


It is true that RFC 1195 does not explicitly direct ISs to reject
adjacencies with neighbors who do not match protocols supported. In most
cases we would be better off w/o such a neighbor - it would prevent needless
flooding of LSPs which contained no useable routing information. However, on
a "misconfigured" LAN, if some combination of IP only and OSI-only routers
exist - the fact that all routers will form adjacencies is a benefit in that
only a single DIS will be elected. The unfortunate part is that LSPs from
OSI-only routers will take up resources in IP-only routers and vice-versa.

This makes it important to check the protocols supported option in
non-pseudo-node LSPs so as to avoid using an OSI-only router as a transit
router for IP traffic (and vice versa...). LSPs from a router which does not
advertise support for a particular protocol should be ignored during SPF.

The same check in pseudo-node LSPs, as Tony has pointed out, is not
important since the pseudo-node LSP only has information about routers
connected to the LAN, not what destinations are reachable via those routers.

This raises the point that an alarm associated with the formation of an
adjacency with a protocol-wise incompatible neighbor as well as an alarm
associated with reception of a non-pseudo-node LSP with incompatible
protocols would be helpful. (Jeff Parker - are you listening?)

   Les

> -----Original Message-----
> From: Jeff Learman [mailto:jlearman@cisco.com]
> Sent: Sunday, November 25, 2001 6:21 PM
> To: Tony Li
> Cc: Chan, Chung Ming (Adtech ENG); 'isis-wg@external.juniper.net'
> Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
> 
> 
> 
> I agree with Tony.  There are some additional things to consider,
> though.
> 
> In accordance with RFC 1195, an implementation doesn't need
> to consult an LSP's supported protocols option when running SPF
> except for links to end systems, and a pseudonode LSP should have
> only links between intermediate systems.  (Rather than relying on
> the protos supported option, RFC 1195 relies on the deployment
> rules.)
> 
> My understanding is that some routers do take the protos-supported
> option when running SPF.  This allows some relaxation of the 
> deployment
> rules.  There is no interoperability problem, because any strict
> implementation won't work anyway, in situations where this 
> modification
> helps.
> 
> However, in networks where this modification is being used, and
> mixed networks don't meet the deployment requirements in 1195,
> will it be important to make sure the designated router is a dual
> router?  I can't find anything in 1195 that says to check protos-
> supported when bringing up an adjacency.  If for any reason a
> system would not form an adjacency with a router with which it
> shared no protocols, that would cause a problem in the pseudonode
> LSPs.  Hopefully this isn't a problem.
> 
> Regards,
> Jeff
> 
> PS:  I don't work in IS-IS at Cisco.  My comments do not necessarily
> reflect Cisco's opinions and I have no detailed knowledge of the Cisco
> IS-IS implementation.
> 
> 
> 
> 
> At 08:06 PM 11/25/2001, Tony Li wrote:
> 
> > | I found out that in one vendor's pseudonode LSPs, there 
> is no "Protocols
> > | Supported" field included; but it includes the field in 
> the non-pseudonode
> > | LSPs.
> > | 
> > | Shall the Protocols Supported field MUST be included in 
> pseudonode LSP
> > | according to RFC 1195?
> > | 
> > | Not sure if there is any reason for that particular 
> vender for doing it.
> > | 
> > | Could someone please verify this ?
> > | 
> > | RFC 1195 Section 3.1, paragraph 3:
> > | "IP-capable (i.e., all IP-only and dual) routers need to 
> know what network
> > | layer protocols are sup-ported
> > | by other routers in their area. This information is made 
> available by
> > | inclusion of a "proto-cols
> > | supported" field in all IS-IS Hello and Link State 
> Packets. This field makes
> > | use of the NL-PID
> > | (Network Layer Protocol Identifier), which is a one-octet 
> value assigned by
> > | ISO to identify
> > | network level protocols. NLPID values have been assigned 
> to ISO 8473 and to
> > | IP."
> >
> >
> >Interesting question.
> >
> >Well, the pseudonode LSP is really there to represent the 
> broadcast medium,
> >not any particular router.  And since the broadcast medium 
> is presumably
> >protocol independent, it doesn't seem like it actually 
> conveys any useful
> >information.
> >
> >Thus, IMHO, it would make sense if implementations ignored 
> the Procotols
> >Supported TLV in a pseudonode LSP and not require it be present.
> >
> >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
> 
_______________________________________________
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 26 14:59:11 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25707
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 14:59:10 -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 MAA67291;
	Mon, 26 Nov 2001 12:10:48 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA67276
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 12:09:48 -0800 (PST)
Received: from alpha-tli.procket.com (IDENT:root@alpha-tli.procket.com [10.2.3.1])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fAQJmt8A002201;
	Mon, 26 Nov 2001 11:48:55 -0800 (PST)
Received: (from tli@localhost)
	by alpha-tli.procket.com (8.12.1/8.12.1) id fAQJmtwZ006714;
	Mon, 26 Nov 2001 11:48:55 -0800
From: Tony Li <tli@Procket.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15362.40098.114535.697045@alpha-tli.procket.com>
To: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@SpirentCom.COM>
Cc: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>,
        "'Les  Ginsberg'" <ginsberg@pluris.com>,
        "'Jeff Learman'"
	 <jlearman@cisco.com>, Tony Li <tli@Procket.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
In-Reply-To: <8AC36D3167EED41184C800508BD9540501EE3BED@apollo.adtech-inc.com>
References: <8AC36D3167EED41184C800508BD9540501EE3BED@apollo.adtech-inc.com>
X-Mailer: VM 6.92 under Emacs 20.5.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 11:48:50 -0800
Content-Transfer-Encoding: 7bit


 | 	Another role for the inclusion of "Protocols Supported" field is to
 | signal the other routers that the router originated the LSP is IP capable (
 | As I understood it from RFC 1195 Section 5.2, paragraph 2.) 
 | 	Would it be from this point of view that the "Protocols Supported"
 | field is necessary since "logically" pseudo-node LSP is from the
 | Designated-Router to all of its neighbors?
 | The field tells all of its neighbors that it is IP capable.


Well, that would certainly be one interpretation of the spec.  However,
that would seem to be less interoperable.

     "Be strict in what you send and liberal in what you receive."
				     - Jon Postel

Accordingly, putting a Protocols Supported field in the pseudonode LSP is
not something that I interpret as being required by the spec.

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 26 15:28:07 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28149
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 15:28:07 -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 MAA67471;
	Mon, 26 Nov 2001 12:41:48 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA67459
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 12:40:37 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fAQKJlT13998;
	Mon, 26 Nov 2001 15:19:47 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGJ06519;
	Mon, 26 Nov 2001 15:19:43 -0500 (EST)
Message-Id: <4.3.2.7.2.20011126144755.019b7008@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@SpirentCom.COM>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>,
        "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@SpirentCom.COM>,
        "'Les  Ginsberg'" <ginsberg@pluris.com>, Tony Li <tli@procket.com>
In-Reply-To: <8AC36D3167EED41184C800508BD9540501EE3BED@apollo.adtech-inc
 .com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 15:03:36 -0500


First of all, a pseudonode represents the media, not a real router,
as Tony pointed out.  For that reason, it can be assumed to support
all protocols that are supportable on that media type, and the LSP
options are not necessary for this purpose.

Furthermore, we cannot require OSI-only routers that do not support
1195 to include a "protocols supported" option identifying
IP in their pseudonode LSPs.

We should figure out whether an IP-capable router "should" include the
IP protocol-supported option.  However, there are (allegedly)
implementations that are IP-capable which don't put the option in
their pseudonode LSPs.  Therefore, it's good idea to treat pseudonode
LSPs without the option as supporting both IP and OSI.

Once again, this would only be an issue in a network that doesn't
meet the deployment requirements (e.g., in a mixed area, all L1 routers
must be dual-capable).  As I understand it, in networks that follow
the deployment rules, there is no need to check the protocols-supported
option in LSPs when running SPF.  Checking it is an optimization: if
an LSP doesn't support IP, then there's no need to look for IP
addressing info in the LSP, because it won't be there.

Regards,
Jeff

At 12:01 PM 11/26/2001, Chan, Chung Ming (Adtech ENG) wrote:
>All,
>
>        Another role for the inclusion of "Protocols Supported" field is to
>signal the other routers that the router originated the LSP is IP capable (
>As I understood it from RFC 1195 Section 5.2, paragraph 2.) 
>        Would it be from this point of view that the "Protocols Supported"
>field is necessary since "logically" pseudo-node LSP is from the
>Designated-Router to all of its neighbors?
>The field tells all of its neighbors that it is IP capable.
>
>        Thanks,
>
>
>Ming Chan
>
>
>-----Original Message-----
>From: Les Ginsberg [mailto:ginsberg@pluris.com]
>Sent: Monday, November 26, 2001 2:23 AM
>To: 'Jeff Learman'; Tony Li
>Cc: Chan, Chung Ming (Adtech ENG); 'isis-wg@external.juniper.net'
>Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
>
>
>It is true that RFC 1195 does not explicitly direct ISs to reject
>adjacencies with neighbors who do not match protocols supported. In most
>cases we would be better off w/o such a neighbor - it would prevent needless
>flooding of LSPs which contained no useable routing information. However, on
>a "misconfigured" LAN, if some combination of IP only and OSI-only routers
>exist - the fact that all routers will form adjacencies is a benefit in that
>only a single DIS will be elected. The unfortunate part is that LSPs from
>OSI-only routers will take up resources in IP-only routers and vice-versa.
>
>This makes it important to check the protocols supported option in
>non-pseudo-node LSPs so as to avoid using an OSI-only router as a transit
>router for IP traffic (and vice versa...). LSPs from a router which does not
>advertise support for a particular protocol should be ignored during SPF.
>
>The same check in pseudo-node LSPs, as Tony has pointed out, is not
>important since the pseudo-node LSP only has information about routers
>connected to the LAN, not what destinations are reachable via those routers.
>
>This raises the point that an alarm associated with the formation of an
>adjacency with a protocol-wise incompatible neighbor as well as an alarm
>associated with reception of a non-pseudo-node LSP with incompatible
>protocols would be helpful. (Jeff Parker - are you listening?)
>
>   Les
>
>> -----Original Message-----
>> From: Jeff Learman [mailto:jlearman@cisco.com]
>> Sent: Sunday, November 25, 2001 6:21 PM
>> To: Tony Li
>> Cc: Chan, Chung Ming (Adtech ENG); 'isis-wg@external.juniper.net'
>> Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
>>
>>
>>
>> I agree with Tony.  There are some additional things to consider,
>> though.
>>
>> In accordance with RFC 1195, an implementation doesn't need
>> to consult an LSP's supported protocols option when running SPF
>> except for links to end systems, and a pseudonode LSP should have
>> only links between intermediate systems.  (Rather than relying on
>> the protos supported option, RFC 1195 relies on the deployment
>> rules.)
>>
>> My understanding is that some routers do take the protos-supported
>> option when running SPF.  This allows some relaxation of the
>> deployment
>> rules.  There is no interoperability problem, because any strict
>> implementation won't work anyway, in situations where this
>> modification
>> helps.
>>
>> However, in networks where this modification is being used, and
>> mixed networks don't meet the deployment requirements in 1195,
>> will it be important to make sure the designated router is a dual
>> router?  I can't find anything in 1195 that says to check protos-
>> supported when bringing up an adjacency.  If for any reason a
>> system would not form an adjacency with a router with which it
>> shared no protocols, that would cause a problem in the pseudonode
>> LSPs.  Hopefully this isn't a problem.
>>
>> Regards,
>> Jeff
>>
>> PS:  I don't work in IS-IS at Cisco.  My comments do not necessarily
>> reflect Cisco's opinions and I have no detailed knowledge of the Cisco
>> IS-IS implementation.
>>
>>
>>
>>
>> At 08:06 PM 11/25/2001, Tony Li wrote:
>>
>> > | I found out that in one vendor's pseudonode LSPs, there
>> is no "Protocols
>> > | Supported" field included; but it includes the field in
>> the non-pseudonode
>> > | LSPs.
>> > |
>> > | Shall the Protocols Supported field MUST be included in
>> pseudonode LSP
>> > | according to RFC 1195?
>> > |
>> > | Not sure if there is any reason for that particular
>> vender for doing it.
>> > |
>> > | Could someone please verify this ?
>> > |
>> > | RFC 1195 Section 3.1, paragraph 3:
>> > | "IP-capable (i.e., all IP-only and dual) routers need to
>> know what network
>> > | layer protocols are sup-ported
>> > | by other routers in their area. This information is made
>> available by
>> > | inclusion of a "proto-cols
>> > | supported" field in all IS-IS Hello and Link State
>> Packets. This field makes
>> > | use of the NL-PID
>> > | (Network Layer Protocol Identifier), which is a one-octet
>> value assigned by
>> > | ISO to identify
>> > | network level protocols. NLPID values have been assigned
>> to ISO 8473 and to
>> > | IP."
>> >
>> >
>> >Interesting question.
>> >
>> >Well, the pseudonode LSP is really there to represent the
>> broadcast medium,
>> >not any particular router.  And since the broadcast medium
>> is presumably
>> >protocol independent, it doesn't seem like it actually
>> conveys any useful
>> >information.
>> >
>> >Thus, IMHO, it would make sense if implementations ignored
>> the Procotols
>> >Supported TLV in a pseudonode LSP and not require it be present.
>> >
>> >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
>>

_______________________________________________
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 26 15:28:54 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28204
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 15:28: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 MAA67527;
	Mon, 26 Nov 2001 12:46:49 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA67483
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 12:43:43 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id MAA16876;
	Mon, 26 Nov 2001 12:22:57 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <VMHL1Q6M>; Mon, 26 Nov 2001 12:22:57 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F5EB@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Tony Li'" <tli@Procket.com>,
        "Chan, Chung Ming (Adtech ENG)"
	 <Ming.Chan@SpirentCom.COM>
Cc: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>,
        Les  Ginsberg <ginsberg@pluris.com>,
        "'Jeff Learman'" <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 12:22:56 -0800

In addition, the information about protocols supported is available from the
non-pseudo-node LSP originated by the system which is DIS. Including such
information in a pseudo-node LSP, while certainly not invalid, is at best
redundant. (Remembering of course that a router must operate in the same
fashion in terms of protocols supported on all links.)

   Les


> -----Original Message-----
> From: Tony Li [mailto:tli@Procket.com]
> Sent: Monday, November 26, 2001 11:49 AM
> To: Chan, Chung Ming (Adtech ENG)
> Cc: 'isis-wg@external.juniper.net'; 'Les Ginsberg'; 'Jeff 
> Learman'; Tony
> Li
> Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
> 
> 
> 
>  | 	Another role for the inclusion of "Protocols Supported" 
> field is to
>  | signal the other routers that the router originated the 
> LSP is IP capable (
>  | As I understood it from RFC 1195 Section 5.2, paragraph 2.) 
>  | 	Would it be from this point of view that the "Protocols 
> Supported"
>  | field is necessary since "logically" pseudo-node LSP is from the
>  | Designated-Router to all of its neighbors?
>  | The field tells all of its neighbors that it is IP capable.
> 
> 
> Well, that would certainly be one interpretation of the spec. 
>  However,
> that would seem to be less interoperable.
> 
>      "Be strict in what you send and liberal in what you receive."
> 				     - Jon Postel
> 
> Accordingly, putting a Protocols Supported field in the 
> pseudonode LSP is
> not something that I interpret as being required by the spec.
> 
> 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 26 15:34:22 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28623
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 15:34:21 -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 MAA67582;
	Mon, 26 Nov 2001 12:51:50 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA67544
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 12:48:07 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fAQKRUT15000;
	Mon, 26 Nov 2001 15:27:30 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGJ06772;
	Mon, 26 Nov 2001 15:27:25 -0500 (EST)
Message-Id: <4.3.2.7.2.20011126152244.019934e0@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Les  Ginsberg <ginsberg@pluris.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: Tony Li <tli@procket.com>,
        "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
In-Reply-To: <17C81AD1F1FED411991E006008F6D1CA01B3F5E6@avalon.pluris.com
 >
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 15:27:23 -0500


Les,

At 02:23 AM 11/26/2001, Les  Ginsberg wrote:
>router for IP traffic (and vice versa...). LSPs from a router which does not
>advertise support for a particular protocol should be ignored during SPF.

Is this required by 1195?  As I understand it, it isn't, as the check
would be superfluous in any network that meets the deployment
requirements.  I think it's unfortunate that 1195 was written this
way, but wouldn't it be a mistake to assume any router does this
check?

If some routers do this and others don't, then there will be routing
loops.  Of course, if some routers don't do this in a network that
doesn't meet the deployment requirements, that network won't work
anyway.



_______________________________________________
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 26 15:52:19 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA00295
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 15:52:19 -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 NAA67743;
	Mon, 26 Nov 2001 13:05:48 -0800 (PST)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA67685
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 13:04:34 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734290122FE54@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Jeff Learman'" <jlearman@cisco.com>
Cc: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 15:43:46 -0500

> As I understand it, in networks that follow
> the deployment rules, there is no need to check the 
> protocols-supported option in LSPs when running SPF.  
> Checking it is an optimization: if an LSP doesn't 
> support IP, then there's no need to look for IP
> addressing info in the LSP, because it won't be there.
> 
> Jeff [L]

Jeff -
	I thought this was an issue, due to transitive
closure.  You don't have any IP addresses, but you 
present an attractive route to a router that does
have IP addresses.  If I don't check your protocols
supported, I might use you on a path.  Since
you don't forward IP packets, we have a black hole
if all routers ignore protocol supported in SPF, or 
a routing loop if some check and some do not.  

- jeff parker  
_______________________________________________
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 26 16:18:34 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02470
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 16:18:34 -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 NAA67929;
	Mon, 26 Nov 2001 13:33:48 -0800 (PST)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA67908
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 13:31:31 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734290122FE55@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Les  Ginsberg'" <ginsberg@pluris.com>
Cc: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 16:10:39 -0500

> This raises the point that an alarm associated with the 
> formation of an adjacency with a protocol-wise incompatible 
> neighbor as well as an alarm associated with reception of 
> a non-pseudo-node LSP with incompatible
> protocols would be helpful. (Jeff Parker - are you listening?)
> 
> Les

Les -
	Yes, I am listening. 
 
	To recap MIBstory, version .06 of the MIB is on the IETF 
site.  I have been circulating a draft version of version .07, 
which includes Traps, to those who have expressed interest.

	The two events above seem like natural additions to
the list of Traps (Notifications).  Will add and send your way.    

	Most of the traps have a "edge triggered" text suggesting
that we send one of these traps the -first- time we see the
event so the manager doesn't get flooded.  

- jeff parker
- axiowave networks
_______________________________________________
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 26 16:25:36 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02982
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 16:25: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 NAA67890;
	Mon, 26 Nov 2001 13:28:48 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA67878
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 13:27:45 -0800 (PST)
Received: from alpha-tli.procket.com (IDENT:root@alpha-tli.procket.com [10.2.3.1])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fAQL6j8A020901;
	Mon, 26 Nov 2001 13:06:45 -0800 (PST)
Received: (from tli@localhost)
	by alpha-tli.procket.com (8.12.1/8.12.1) id fAQL6j3W006837;
	Mon, 26 Nov 2001 13:06:45 -0800
From: Tony Li <tli@Procket.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15362.44773.326896.768305@alpha-tli.procket.com>
To: Jeff Learman <jlearman@cisco.com>
Cc: Les  Ginsberg <ginsberg@pluris.com>, Tony Li <tli@Procket.com>,
        "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
In-Reply-To: <4.3.2.7.2.20011126152244.019934e0@dingdong.cisco.com>
References: <17C81AD1F1FED411991E006008F6D1CA01B3F5E6@avalon.pluris.com>
	<4.3.2.7.2.20011126152244.019934e0@dingdong.cisco.com>
X-Mailer: VM 6.92 under Emacs 20.5.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 13:06:45 -0800
Content-Transfer-Encoding: 7bit


 | At 02:23 AM 11/26/2001, Les  Ginsberg wrote:
 | >router for IP traffic (and vice versa...). LSPs from a router which
 | >does not advertise support for a particular protocol should be ignored
 | >during SPF. 
 | 
 | Is this required by 1195?  As I understand it, it isn't, as the check
 | would be superfluous in any network that meets the deployment
 | requirements.  I think it's unfortunate that 1195 was written this
 | way, but wouldn't it be a mistake to assume any router does this
 | check?


1195 specifically says that this check is not necessary.  However, that's
also making the grand assumption that the domain is following the
deployement requirements.  Unfortunately, humans make mistakes, so simply
assuming that the deployment requirements are met is likely to get an
implementor into a conflict with users.  Far better to be careful in the
computations and forward the traffic along a best effort path.

As an aside, one has to wonder if the authors of 1195 didn't expect such a
check.  If one does make the assumption that the deployment rules are being
followed, what is the point in the Protocols Supported TLV in the first
place? 

IMHO, doing the check is a trivial amount of overhead and seems to be well
worth the additional security.


 | If some routers do this and others don't, then there will be routing
 | loops.  Of course, if some routers don't do this in a network that
 | doesn't meet the deployment requirements, that network won't work
 | anyway.


If some routers do not make this check and are deployed in a dual
environment where the deployment rules are not followed, then those routers
may make an incorrect forwarding decision.  If the next hop is not protocol
capable, then the decision will be a black hole.  However, if the next hop
is a router that does make the SPF check, then there is the possibility of
a forwarding loop.

While forwarding loops are in many ways more painful than black holes, I
suspect that the benefits incurred by making this check and forwarding
along the best available path far outweigh the additional danger.

Of course, the cost for dual implementations that choose to support this is
a separate SPF per protocol type.

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 26 17:11:07 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06129
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 17:11:07 -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 OAA68274;
	Mon, 26 Nov 2001 14:17:49 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA68262
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 14:16:48 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fAQLuAT22157;
	Mon, 26 Nov 2001 16:56:10 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGJ09311;
	Mon, 26 Nov 2001 16:56:05 -0500 (EST)
Message-Id: <4.3.2.7.2.20011126163743.019c27c0@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Tony Li <tli@Procket.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: Les  Ginsberg <ginsberg@pluris.com>, Tony Li <tli@Procket.com>,
        "Chan, Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
In-Reply-To: <15362.44773.326896.768305@alpha-tli.procket.com>
References: <4.3.2.7.2.20011126152244.019934e0@dingdong.cisco.com>
 <17C81AD1F1FED411991E006008F6D1CA01B3F5E6@avalon.pluris.com>
 <4.3.2.7.2.20011126152244.019934e0@dingdong.cisco.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 16:55:32 -0500

At 04:06 PM 11/26/2001, Tony Li wrote:

> | At 02:23 AM 11/26/2001, Les  Ginsberg wrote:
> | >router for IP traffic (and vice versa...). LSPs from a router which
> | >does not advertise support for a particular protocol should be ignored
> | >during SPF. 
> | 
> | Is this required by 1195?  As I understand it, it isn't, as the check
> | would be superfluous in any network that meets the deployment
> | requirements.  I think it's unfortunate that 1195 was written this
> | way, but wouldn't it be a mistake to assume any router does this
> | check?
>
>
>1195 specifically says that this check is not necessary.  However, that's
>also making the grand assumption that the domain is following the
>deployement requirements.  Unfortunately, humans make mistakes, so simply
>assuming that the deployment requirements are met is likely to get an
>implementor into a conflict with users.  Far better to be careful in the
>computations and forward the traffic along a best effort path.
>
>As an aside, one has to wonder if the authors of 1195 didn't expect such a
>check.  If one does make the assumption that the deployment rules are being
>followed, what is the point in the Protocols Supported TLV in the first
>place? 
>
>IMHO, doing the check is a trivial amount of overhead and seems to be well
>worth the additional security.

I agree wholeheartedly.

> | If some routers do this and others don't, then there will be routing
> | loops.  Of course, if some routers don't do this in a network that
> | doesn't meet the deployment requirements, that network won't work
> | anyway.
>
>
>If some routers do not make this check and are deployed in a dual
>environment where the deployment rules are not followed, then those routers
>may make an incorrect forwarding decision.

Incorrect?  Well, it's operating according to the RFC.  The RFC
is incorrect or the network is incorrect, not those routers.
(Yes, I know I'm being pedantic ;-)  I agree that those routers
forward the packets where we don't want them to go!

My point is simply that we must not assume that other systems make
the check.  Or, if we find that all known implementations do make the
check, then we could dramatically improve 1195 and make it mandatory,
and explain the new (relaxed) deployment rules.

Regards,
Jeff


>If the next hop is not protocol
>capable, then the decision will be a black hole.  However, if the next hop
>is a router that does make the SPF check, then there is the possibility of
>a forwarding loop.
>
>While forwarding loops are in many ways more painful than black holes, I
>suspect that the benefits incurred by making this check and forwarding
>along the best available path far outweigh the additional danger.
>
>Of course, the cost for dual implementations that choose to support this is
>a separate SPF per protocol type.


_______________________________________________
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 26 17:26:23 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07210
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 17:26:23 -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 OAA68446;
	Mon, 26 Nov 2001 14:41:49 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA68434
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 14:40:57 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fAQMKKT24039;
	Mon, 26 Nov 2001 17:20:20 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGJ10184;
	Mon, 26 Nov 2001 17:20:16 -0500 (EST)
Message-Id: <4.3.2.7.2.20011126171558.019c2960@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Naiming Shen <naiming@redback.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP 
Cc: Les Ginsberg <ginsberg@pluris.com>, "'Tony Li'" <tli@procket.com>,
        "Chan,     Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
In-Reply-To: <20011126221343.93D554BA219@prattle.redback.com>
References: <Mail from Les Ginsberg <ginsberg@pluris.com>
 <17C81AD1F1FED411991E006008F6D1CA01B3F5EB@avalon.pluris.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 17:20:11 -0500


The protocols-supported option on an LSP only indicates the
status of the issuing router, not of any of the links, etc.
Therefore, it is reasonable to assume that a pseudonode LSP,
as it represents the media, supports all protocols.  The most
the issuing system could do is include all the protocols it
supports, or perhaps all the protocols that are defined at
the time of writing (since the DIS is not involved in relaying
packets between other routers on the LAN).

I think it's best to omit the option in pseudonodes, since it has
incomplete information anyway, and to ignore it in pseudonodes
during SPF.

Note that a dual router could be included in an IP-only area, and
would naturally include OSI as a supported protocol in its LSPs.
Placing that information in the pseudonode LSP is meaningless.

Regards,
Jeff

At 05:13 PM 11/26/2001, Naiming Shen wrote:

>Even if the DIS wants to stuff a Protocol-Supported field in its
>pseudo-node LSP, what should it say? should it say "some of my adjacencies
>are OSI-only, some are IP only and some are dual"? this certainly does not
>help; then it probably should say: my neighbor listed below from 1 through
>23 is IP only, 24 through 28 is dual and rest is OSI-only? in either case
>rfc1195 does not support such a protocol supported description in LSPs.
>
>Thus the DIS should just shutup and say nothing.
>
> ]In addition, the information about protocols supported is available from the
> ]non-pseudo-node LSP originated by the system which is DIS. Including such
> ]information in a pseudo-node LSP, while certainly not invalid, is at best
> ]redundant. (Remembering of course that a router must operate in the same
> ]fashion in terms of protocols supported on all links.)
> ]
> ]   Les
> ]
> ]
> ]> -----Original Message-----
> ]> From: Tony Li [mailto:tli@Procket.com]
> ]> Sent: Monday, November 26, 2001 11:49 AM
> ]> To: Chan, Chung Ming (Adtech ENG)
> ]> Cc: 'isis-wg@external.juniper.net'; 'Les Ginsberg'; 'Jeff 
> ]> Learman'; Tony
> ]> Li
> ]> Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
> ]> 
> ]> 
> ]> 
> ]>  |  Another role for the inclusion of "Protocols Supported" 
> ]> field is to
> ]>  | signal the other routers that the router originated the 
> ]> LSP is IP capable (
> ]>  | As I understood it from RFC 1195 Section 5.2, paragraph 2.) 
> ]>  |  Would it be from this point of view that the "Protocols 
> ]> Supported"
> ]>  | field is necessary since "logically" pseudo-node LSP is from the
> ]>  | Designated-Router to all of its neighbors?
> ]>  | The field tells all of its neighbors that it is IP capable.
> ]> 
> ]> 
> ]> Well, that would certainly be one interpretation of the spec. 
> ]>  However,
> ]> that would seem to be less interoperable.
> ]> 
> ]>      "Be strict in what you send and liberal in what you receive."
> ]>                                  - Jon Postel
> ]> 
> ]> Accordingly, putting a Protocols Supported field in the 
> ]> pseudonode LSP is
> ]> not something that I interpret as being required by the spec.
> ]> 
> ]> Tony
> ]> 
> ]_______________________________________________
> ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
> ]http://external.juniper.net/mailman/listinfo/isis-wg
>
>- Naiming

_______________________________________________
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 26 17:30:00 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07600
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 17:30: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 OAA68388;
	Mon, 26 Nov 2001 14:35:49 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA68373
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 14:34:22 -0800 (PST)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 93D554BA219; Mon, 26 Nov 2001 14:13:43 -0800 (PST)
To: Les Ginsberg <ginsberg@pluris.com>
Cc: "'Tony Li'" <tli@procket.com>,
        "Chan,     Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>,
        "'Jeff Learman'" <jlearman@cisco.com>
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP 
In-reply-to: Mail from Les Ginsberg <ginsberg@pluris.com> 
 dated Mon, 26 Nov 2001 12:22:56 PST
 <17C81AD1F1FED411991E006008F6D1CA01B3F5EB@avalon.pluris.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011126221343.93D554BA219@prattle.redback.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 14:13:43 -0800


Even if the DIS wants to stuff a Protocol-Supported field in its
pseudo-node LSP, what should it say? should it say "some of my adjacencies
are OSI-only, some are IP only and some are dual"? this certainly does not
help; then it probably should say: my neighbor listed below from 1 through
23 is IP only, 24 through 28 is dual and rest is OSI-only? in either case
rfc1195 does not support such a protocol supported description in LSPs.

Thus the DIS should just shutup and say nothing.

 ]In addition, the information about protocols supported is available from the
 ]non-pseudo-node LSP originated by the system which is DIS. Including such
 ]information in a pseudo-node LSP, while certainly not invalid, is at best
 ]redundant. (Remembering of course that a router must operate in the same
 ]fashion in terms of protocols supported on all links.)
 ]
 ]   Les
 ]
 ]
 ]> -----Original Message-----
 ]> From: Tony Li [mailto:tli@Procket.com]
 ]> Sent: Monday, November 26, 2001 11:49 AM
 ]> To: Chan, Chung Ming (Adtech ENG)
 ]> Cc: 'isis-wg@external.juniper.net'; 'Les Ginsberg'; 'Jeff 
 ]> Learman'; Tony
 ]> Li
 ]> Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
 ]> 
 ]> 
 ]> 
 ]>  | 	Another role for the inclusion of "Protocols Supported" 
 ]> field is to
 ]>  | signal the other routers that the router originated the 
 ]> LSP is IP capable (
 ]>  | As I understood it from RFC 1195 Section 5.2, paragraph 2.) 
 ]>  | 	Would it be from this point of view that the "Protocols 
 ]> Supported"
 ]>  | field is necessary since "logically" pseudo-node LSP is from the
 ]>  | Designated-Router to all of its neighbors?
 ]>  | The field tells all of its neighbors that it is IP capable.
 ]> 
 ]> 
 ]> Well, that would certainly be one interpretation of the spec. 
 ]>  However,
 ]> that would seem to be less interoperable.
 ]> 
 ]>      "Be strict in what you send and liberal in what you receive."
 ]> 				     - Jon Postel
 ]> 
 ]> Accordingly, putting a Protocols Supported field in the 
 ]> pseudonode LSP is
 ]> not something that I interpret as being required by the spec.
 ]> 
 ]> Tony
 ]> 
 ]_______________________________________________
 ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ]http://external.juniper.net/mailman/listinfo/isis-wg

- Naiming
_______________________________________________
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 26 17:35:36 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07955
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 17:35:35 -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 NAA68020;
	Mon, 26 Nov 2001 13:46:48 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA68008
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 13:45:03 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fAQLOQT19977;
	Mon, 26 Nov 2001 16:24:26 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGJ08446;
	Mon, 26 Nov 2001 16:24:22 -0500 (EST)
Message-Id: <4.3.2.7.2.20011126160107.01a20b00@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Jeff Parker <jparker@axiowave.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
In-Reply-To: <EB5FFC72F183D411B3820006295734290122FE54@r2d2.axiowave.com
 >
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 16:05:24 -0500

At 03:43 PM 11/26/2001, Jeff Parker wrote:
>> As I understand it, in networks that follow
>> the deployment rules, there is no need to check the 
>> protocols-supported option in LSPs when running SPF.  
>> Checking it is an optimization: if an LSP doesn't 
>> support IP, then there's no need to look for IP
>> addressing info in the LSP, because it won't be there.
>> 
>> Jeff [L]
>
>Jeff -
>        I thought this was an issue, due to transitive
>closure.  You don't have any IP addresses, but you 
>present an attractive route to a router that does
>have IP addresses.  If I don't check your protocols
>supported, I might use you on a path.  Since
>you don't forward IP packets, we have a black hole
>if all routers ignore protocol supported in SPF, or 
>a routing loop if some check and some do not.  

But this only happens in networks that don't follow the deployment rules.
SO: Do people follow the rules?

Are the rules really correct, if all routers in the subdomain check the
protocols supported option?  I think they could be relaxed to "sufficient
connectivity" for each protocol within each subdomain.

Regards,
Jeff



>- jeff parker  

_______________________________________________
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 26 17:56:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA09288
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 17:56:42 -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 PAA68694;
	Mon, 26 Nov 2001 15:14:48 -0800 (PST)
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA68682
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 15:13:22 -0800 (PST)
Received: from cirrus.juniper.net (cirrus.juniper.net [172.17.20.57])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id fAQMqB084442;
	Mon, 26 Nov 2001 14:52:11 -0800 (PST)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost) by cirrus.juniper.net (8.8.7/8.7.3) id OAA28798; Mon, 26 Nov 2001 14:52:11 -0800 (PST)
Message-Id: <200111262252.OAA28798@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: jlearman@cisco.com
CC: jparker@axiowave.com, isis-wg@spider.juniper.net
In-reply-to: <4.3.2.7.2.20011126160107.01a20b00@dingdong.cisco.com> (message
	from Jeff Learman on Mon, 26 Nov 2001 16:05:24 -0500)
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 14:52:11 -0800 (PST)

   But this only happens in networks that don't follow the deployment rules.
   SO: Do people follow the rules?

I guess this begs the question, are there any OSI-only routers out there?
There are the goofy ADMs, I suppose

There are plenty of IP-only routers running ISIS, which leads one to 
believe that mixed networks are extremely rare.
_______________________________________________
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 26 18:17:31 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11018
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 18:17: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 PAA68852;
	Mon, 26 Nov 2001 15:32:49 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA68840
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 15:31:45 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fAQNB8T26906;
	Mon, 26 Nov 2001 18:11:08 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGJ11511;
	Mon, 26 Nov 2001 18:11:04 -0500 (EST)
Message-Id: <4.3.2.7.2.20011126180801.0194fc80@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Dave Katz <dkatz@juniper.net>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: jparker@axiowave.com, isis-wg@spider.juniper.net
In-Reply-To: <200111262252.OAA28798@cirrus.juniper.net>
References: <4.3.2.7.2.20011126160107.01a20b00@dingdong.cisco.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 18:11:00 -0500


Dave,

SONET network management uses OSI with ISIS, and are planning (last I
heard) to use integrated IP & OSI networks using RFC 1195.  For more
information, please contact T1.X1.

But we better work out these rules anyway, because IPV6 will raise
them yet again.

Regards,
Jeff

At 05:52 PM 11/26/2001, Dave Katz wrote:
>   But this only happens in networks that don't follow the deployment rules.
>   SO: Do people follow the rules?
>
>I guess this begs the question, are there any OSI-only routers out there?
>There are the goofy ADMs, I suppose
>
>There are plenty of IP-only routers running ISIS, which leads one to 
>believe that mixed networks are extremely rare.

_______________________________________________
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 26 18:48:48 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13289
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 18:48: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 QAA69093;
	Mon, 26 Nov 2001 16:06:49 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA69079
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 16:05:18 -0800 (PST)
Received: from redback.com (prz-laptop.redback.com [155.53.36.102])
	by prattle.redback.com (Postfix) with ESMTP
	id CEF98CAB6D; Mon, 26 Nov 2001 15:44:38 -0800 (PST)
Message-ID: <3C02C0F5.72CF0928@redback.com>
From: Tony Przygienda <prz@redback.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; NetBSD 1.4.1 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Katz <dkatz@juniper.net>
Cc: jlearman@cisco.com, jparker@axiowave.com, isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
References: <200111262252.OAA28798@cirrus.juniper.net>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 14:23:50 -0800
Content-Transfer-Encoding: 7bit

Dave Katz wrote:

>    But this only happens in networks that don't follow the deployment rules.
>    SO: Do people follow the rules?
>
> I guess this begs the question, are there any OSI-only routers out there?
> There are the goofy ADMs, I suppose

Well, the "goofy" ADMs still generate serious amounts of money so anybody
on this list runs some danger to possibly working on a goofy ADM one of these
days. So no point in ticking the TDM folks off ;-)

> There are plenty of IP-only routers running ISIS, which leads one to
> believe that mixed networks are extremely rare.

with GMPLS and IP generally vying to control TDM networks and possibly
toasters in the future, I would say it is thinkable ....

My take on the protocols-supported field: If you have to stick something in,
stick the superset of all protocols supported by all the routers on the LAN.
This is
because a pseudo-node is not 'belonging' to the DIS, it is representation of
the
LAN as a shared resource by a chosen member ...

In this way, anybody checking for the field in pseudo-node will be happy and it

will not hurt anybody who doesn't  ...

    thanks

    -- 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 26 19:01:20 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14183
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 19:01:20 -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 QAA69177;
	Mon, 26 Nov 2001 16:19:49 -0800 (PST)
Received: from mx4.tellabs.com (mx4.tellabs.com [204.68.180.54])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA69164
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 16:18:09 -0800 (PST)
Received: from mailw02.hq.tellabs.com (mailw02.bb.tellabs.com [138.111.51.101])
	by mx4.tellabs.com (Mirapoint)
	with ESMTP id ABP49094;
	Mon, 26 Nov 2001 17:57:30 -0600 (CST)
Received: from tellabs.com (dhcp-172-17-44-86.lisle.tellabs.com [172.17.44.86]) by mailw02.hq.tellabs.com with ESMTP (8.8.6 (PHNE_17190)/8.7.1) id RAA12367; Mon, 26 Nov 2001 17:57:31 -0600 (CST)
Message-ID: <3C02D6E8.8E213049@tellabs.com>
From: Jonathan Sadler <jonathan.sadler@tellabs.com>
Reply-To: jonathan.sadler@tellabs.com
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Jeff Learman <jlearman@cisco.com>
CC: Dave Katz <dkatz@juniper.net>, jparker@axiowave.com,
        isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
References: <H0000c080324833e.1006816747.mailw02@MHS>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 17:57:28 -0600
Content-Transfer-Encoding: 7bit

Jeff, et al. -

ITU-T SG15 recently consented G.7712/Y.1703 (nee G.dcn) which defines
DCN requirements.  A good amount of this document includes requirements
for IP in the DCC/DCN.

The document includes IS-IS related requirements, including the
"mandatory" support for IS-IS (see sec 7.1.10) for both IP and OSI and
the requirement that an adjacency not be established when the Protocols
Supported field does not match in an IIH (see sec. 7.1.10.1).

What is not included in the document, but remains under consideration in
Q14 of SG15, is a submission from the United Kingdom (UK) to use the
Protocols Supported field when running SPF to automatically determine if
a tunnel should be established to pass packets between 2 OSI-only
islands that are connected via an IP-only network.  (Of course
dual-nodes are used at the points where the OSI and IP networks meet.) 
This is specifically designed to allow more liberal node deployments
than specified in RFC 1195.

The UK submission further requires support for separate IP and OSI DISes
(similar to the separate DISes required for L1 and L2) on LANs to
eliminate implied adjacencies between OSI-only and IP-only nodes on the
LAN.

It should be noted that the approach contained in the UK submission is
general enough so that it can be applied to any network that has islands
of X-protocol to be connected through an Y-protocol based network, where
X and Y could be IPv4, IPv6, or OSI.

The following message was sent through formal Liaison channels from
ITU-T to the IETF and provides a pointer to the consented document. 
Unfortunately, the UK submission is only available to ITU members at
this time.

Jonathan Sadler

-------------- Forwarded Mail ----------------

Scott, Kireeti, and Lyndon,
I am pleased to inform you that we finally have some concensus
within ITU-T that gives us a way to share the files related to
the Study Group 15 communications statements with IETF participants.
This mechanism will likely evolve in the future (more about this
below), but at least for now we have a way to share these files
with IETF participants.

The relevant communications include two to ccamp:
- SDH Signal and Group Structures
- New Recommendations for Automatically Switched Optical Netorks
and one to sigtran:
- Draft Recommendation G.799.1 on interconnecting GSTN and IP Networks

The information may be accessed via a web browser using the following
URL (from an ITU-T ftp server):

ftp://sg15opticalt:otxchange@ftp.itu.int/tsg15opticaltransport/COMMUNICATIONS/index.html

In the future, the Telecommunications Standardization Bureau will likely
provide a way for IETF participants who wish to collaborate with ITU-T
to request their own logins and passwords to access this site, but for
now, all can access the information using the common ID and password
that
you see embedded in the URL.

The structure of the information is as follows:

Main Page
   |
   |-->ccamp-->copyright---->Communication on SDH Signal Structures
   |                      |
   |                      -->Communication on ASON Recs
   |                                |
   |                                |-->G.8080_Y.1304.pdf
   |                                |-->G.7713_Y.1704.pdf
   |                                |-->G.7714_Y.1705.pdf
   |                                --->G.7712_Y.1703.pdf
   |
   --->sigtran-->copyright-->Communication on G.799.1 (GSTN and IP)
                                    |
                                    --->G.799-1-DRAFT-V6.pdf

Please request that your members enter at the main page - this will
help insure that those who access the documents will be aware of the
ITU-T copyright restrictions.

Jeff Learman wrote:
> 
> Dave,
> 
> SONET network management uses OSI with ISIS, and are planning (last I
> heard) to use integrated IP & OSI networks using RFC 1195.  For more
> information, please contact T1.X1.
> 
> But we better work out these rules anyway, because IPV6 will raise
> them yet again.
> 
> Regards,
> Jeff
> 
> At 05:52 PM 11/26/2001, Dave Katz wrote:
> >   But this only happens in networks that don't follow the deployment rules.
> >   SO: Do people follow the rules?
> >
> >I guess this begs the question, are there any OSI-only routers out there?
> >There are the goofy ADMs, I suppose
> >
> >There are plenty of IP-only routers running ISIS, which leads one to
> >believe that mixed networks are extremely rare.
> 
> _______________________________________________
> 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 26 19:14:10 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15014
	for <isis-archive@odin.ietf.org>; Mon, 26 Nov 2001 19:14:09 -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 PAA68804;
	Mon, 26 Nov 2001 15:25:48 -0800 (PST)
Received: from mx4.tellabs.com (mx4.tellabs.com [204.68.180.54])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA68789
	for <isis-wg@spider.juniper.net>; Mon, 26 Nov 2001 15:24:40 -0800 (PST)
Received: from mailw02.hq.tellabs.com (mailw02.bb.tellabs.com [138.111.51.101])
	by mx4.tellabs.com (Mirapoint)
	with ESMTP id ABP48829;
	Mon, 26 Nov 2001 17:04:01 -0600 (CST)
Received: from tellabs.com (dhcp-172-17-44-86.lisle.tellabs.com [172.17.44.86]) by mailw02.hq.tellabs.com with ESMTP (8.8.6 (PHNE_17190)/8.7.1) id RAA01999; Mon, 26 Nov 2001 17:04:02 -0600 (CST)
Message-ID: <3C02CA60.C0C2F525@tellabs.com>
From: Jonathan Sadler <jonathan.sadler@tellabs.com>
Reply-To: jonathan.sadler@tellabs.com
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Katz <dkatz@juniper.net>
CC: jlearman@cisco.com, jparker@axiowave.com, isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP
References: <H0000c080324833c.1006815746.mailw02@MHS>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 26 Nov 2001 17:04:00 -0600
Content-Transfer-Encoding: 7bit

Though mixed networks are likely to come with the new focus on GMPLS
functionality...

Dave Katz wrote:
> 
>    But this only happens in networks that don't follow the deployment rules.
>    SO: Do people follow the rules?
> 
> I guess this begs the question, are there any OSI-only routers out there?
> There are the goofy ADMs, I suppose
> 
> There are plenty of IP-only routers running ISIS, which leads one to
> believe that mixed networks are extremely rare.
> _______________________________________________
> 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  Tue Nov 27 03:41:38 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16743
	for <isis-archive@lists.ietf.org>; Tue, 27 Nov 2001 03:41:37 -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 AAA71594;
	Tue, 27 Nov 2001 00:59:50 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA71565
	for <isis-wg@spider.juniper.net>; Tue, 27 Nov 2001 00:58:56 -0800 (PST)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4100.cisco.com [10.50.16.3])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id IAA12290;
	Tue, 27 Nov 2001 08:37:51 GMT
Message-Id: <4.3.2.7.2.20011127083446.00b82258@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Jeff Learman <jlearman@cisco.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] Protocols Supported field in pseudonode LSP 
Cc: Naiming Shen <naiming@redback.com>, Les Ginsberg <ginsberg@pluris.com>,
        "'Tony Li'" <tli@procket.com>,
        "Chan,     Chung Ming (Adtech ENG)" <Ming.Chan@spirentcom.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
In-Reply-To: <4.3.2.7.2.20011126171558.019c2960@dingdong.cisco.com>
References: <20011126221343.93D554BA219@prattle.redback.com>
 <Mail from Les Ginsberg <ginsberg@pluris.com>
 <17C81AD1F1FED411991E006008F6D1CA01B3F5EB@avalon.pluris.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 27 Nov 2001 08:38:19 +0000

I agree. The pseudonode information is not specific to any one router on 
the LAN (and especially not the DR). Of the two options (include ALL 
protocols, or include NO protocols and treat that as ALL), I think I prefer 
the latter. Clearly the former would work, but seems more error prone 
UNLESS there already exist implementations which check protocols supported 
in the pseudonode LSP.

         Mike


At 17:20 26/11/2001 -0500, Jeff Learman wrote:

>The protocols-supported option on an LSP only indicates the
>status of the issuing router, not of any of the links, etc.
>Therefore, it is reasonable to assume that a pseudonode LSP,
>as it represents the media, supports all protocols.  The most
>the issuing system could do is include all the protocols it
>supports, or perhaps all the protocols that are defined at
>the time of writing (since the DIS is not involved in relaying
>packets between other routers on the LAN).
>
>I think it's best to omit the option in pseudonodes, since it has
>incomplete information anyway, and to ignore it in pseudonodes
>during SPF.
>
>Note that a dual router could be included in an IP-only area, and
>would naturally include OSI as a supported protocol in its LSPs.
>Placing that information in the pseudonode LSP is meaningless.
>
>Regards,
>Jeff
>
>At 05:13 PM 11/26/2001, Naiming Shen wrote:
>
> >Even if the DIS wants to stuff a Protocol-Supported field in its
> >pseudo-node LSP, what should it say? should it say "some of my adjacencies
> >are OSI-only, some are IP only and some are dual"? this certainly does not
> >help; then it probably should say: my neighbor listed below from 1 through
> >23 is IP only, 24 through 28 is dual and rest is OSI-only? in either case
> >rfc1195 does not support such a protocol supported description in LSPs.
> >
> >Thus the DIS should just shutup and say nothing.
> >
> > ]In addition, the information about protocols supported is available 
> from the
> > ]non-pseudo-node LSP originated by the system which is DIS. Including such
> > ]information in a pseudo-node LSP, while certainly not invalid, is at best
> > ]redundant. (Remembering of course that a router must operate in the same
> > ]fashion in terms of protocols supported on all links.)
> > ]
> > ]   Les
> > ]
> > ]
> > ]> -----Original Message-----
> > ]> From: Tony Li [mailto:tli@Procket.com]
> > ]> Sent: Monday, November 26, 2001 11:49 AM
> > ]> To: Chan, Chung Ming (Adtech ENG)
> > ]> Cc: 'isis-wg@external.juniper.net'; 'Les Ginsberg'; 'Jeff
> > ]> Learman'; Tony
> > ]> Li
> > ]> Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
> > ]>
> > ]>
> > ]>
> > ]>  |  Another role for the inclusion of "Protocols Supported"
> > ]> field is to
> > ]>  | signal the other routers that the router originated the
> > ]> LSP is IP capable (
> > ]>  | As I understood it from RFC 1195 Section 5.2, paragraph 2.)
> > ]>  |  Would it be from this point of view that the "Protocols
> > ]> Supported"
> > ]>  | field is necessary since "logically" pseudo-node LSP is from the
> > ]>  | Designated-Router to all of its neighbors?
> > ]>  | The field tells all of its neighbors that it is IP capable.
> > ]>
> > ]>
> > ]> Well, that would certainly be one interpretation of the spec.
> > ]>  However,
> > ]> that would seem to be less interoperable.
> > ]>
> > ]>      "Be strict in what you send and liberal in what you receive."
> > ]>                                  - Jon Postel
> > ]>
> > ]> Accordingly, putting a Protocols Supported field in the
> > ]> pseudonode LSP is
> > ]> not something that I interpret as being required by the spec.
> > ]>
> > ]> Tony
> > ]>
> > ]_______________________________________________
> > ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
> > ]http://external.juniper.net/mailman/listinfo/isis-wg
> >
> >- Naiming
>
>_______________________________________________
>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  Tue Nov 27 10:32:09 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03803
	for <isis-archive@lists.ietf.org>; Tue, 27 Nov 2001 10:32:07 -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 HAA73424;
	Tue, 27 Nov 2001 07:49:48 -0800 (PST)
Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA73411
	for <isis-wg@spider.juniper.net>; Tue, 27 Nov 2001 07:48:14 -0800 (PST)
Received: (qmail 6369 invoked from network); 27 Nov 2001 15:27:30 -0000
Received: from unknown (HELO NEIL) ([66.92.83.66]) (envelope-sender <Larmer@CommSense.Net>)
          by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <jonathan.sadler@tellabs.com>; 27 Nov 2001 15:27:30 -0000
From: "Ken Larmer" <Larmer@commsense.net>
To: <jonathan.sadler@tellabs.com>, "Jeff Learman" <jlearman@cisco.com>
Cc: "Dave Katz" <dkatz@juniper.net>, <jparker@axiowave.com>,
        <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Message-ID: <FFEPKFEJDGEONDOGKAHCMEAOCFAA.Larmer@CommSense.Net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
In-Reply-To: <3C02D6E8.8E213049@tellabs.com>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 27 Nov 2001 10:31:30 -0500
Content-Transfer-Encoding: 7bit


> The UK submission further requires support for separate IP and OSI DISes
> (similar to the separate DISes required for L1 and L2) on LANs to
> eliminate implied adjacencies between OSI-only and IP-only nodes on the
> LAN.

	Is there a need for separate DISes at this point or is there a need for
separate Pseudonode LSPs from a single DIS? If we generate separate
Pseudonode LSPs with the Protocols Supported field advertising the types of
protocols supported for the LAN adjacencies contained within the associated
LSP, won't that resolve this issue?

	I.e. only build an OSI SPF tree for OSI adjacencies advertised in
Pseudonode LSPs without a Protocols Supported field versus only build an IP
SPF tree for IP adjacencies advertised in the Pseudonode LSP (LSP Number =
0) possessing a Protocols Supported field = 0xcc. The draw back as I see it
to implementing multiple Pseudonode LSPs is that, when we support more
protocols within IS-IS, other than OSI and IP, this mechanism will break
because we only check for the presence of the Protocols Supported field in
LSPs with LSP number = 0. Of course, the RFC could be amended in this area
to resolve this issue?

Cheers,
Ken Larmer

_______________________________________________
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 29 06:10:45 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21086
	for <isis-archive@lists.ietf.org>; Thu, 29 Nov 2001 06:10: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 DAA84100;
	Thu, 29 Nov 2001 03:28:49 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA84088
	for <isis-wg@spider.juniper.net>; Thu, 29 Nov 2001 03:27:49 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fATB6q255158
	for <isis-wg@juniper.net>; Thu, 29 Nov 2001 03:06:52 -0800 (PST)
X-JNPR-Received-From: outside
Received: from ietf.org ([132.151.1.176]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 29 Nov 2001 03:05:11 -0800
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20406;
	Thu, 29 Nov 2001 06:06:33 -0500 (EST)
Message-Id: <200111291106.GAA20406@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
X-OriginalArrivalTime: 29 Nov 2001 11:05:11.0531 (UTC) FILETIME=[B6E313B0:01C178C5]
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-gmpls-extensions-05.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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 29 Nov 2001 06:06:33 -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-05.txt
	Pages		: 9
	Date		: 28-Nov-01
	
This document specifies encoding of extensions to the IS-IS routing
protocol in support of Generalized Multi-Protocol Label Switching
(GMPLS).  The description of the extensions is specified in [GMPLS-
ROUTING].

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-gmpls-extensions-05.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-isis-gmpls-extensions-05.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-05.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:	<20011128143718.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-isis-gmpls-extensions-05.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-isis-gmpls-extensions-05.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<20011128143718.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 29 07:23:47 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24497
	for <isis-archive@odin.ietf.org>; Thu, 29 Nov 2001 07:23: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 EAA84746;
	Thu, 29 Nov 2001 04:42:50 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA84734
	for <isis-wg@spider.juniper.net>; Thu, 29 Nov 2001 04:41:08 -0800 (PST)
Received: from mshand-w2k.cisco.com (rtp-vpn1-195.cisco.com [10.82.224.195])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA08112;
	Thu, 29 Nov 2001 12:19:12 GMT
Message-Id: <4.3.2.7.2.20011129111325.00ba2bc0@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Ken Larmer" <Larmer@commsense.net>
From: mike shand <mshand@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: <jonathan.sadler@tellabs.com>, "Jeff Learman" <jlearman@cisco.com>,
        "Dave Katz" <dkatz@juniper.net>, <jparker@axiowave.com>,
        <isis-wg@spider.juniper.net>
In-Reply-To: <FFEPKFEJDGEONDOGKAHCMEAOCFAA.Larmer@CommSense.Net>
References: <3C02D6E8.8E213049@tellabs.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 29 Nov 2001 11:42:24 +0000

It seems to me that it is a VERY bad idea to have multiple DRs on a LAN at 
the same level. This is not just a pseudonode issue, but also affects the 
role of the DR in providing error recovery for the flooding (update) 
process. Unlike the level 1/2 case, there are NOT distinct sets of LSPs 
carrying protocol A and protocol B information (indeed a single LSP can 
carry both sets of information). SO there is no sense in which the update 
process is partitioned between the two DRs.

Or is the intention here that one of the DRs does the normal DR functions 
and generates a pseudonode for protocol A, while the other ONLY generates a 
pseudonode for protocol B?

But in any case, I don't see the need for separate pseudonodes. If we are 
running separate SPFs for protocol A and B, then the pseudonode is simply 
treated as a node which is both A and B capable. A protocol A (only) 
capable Node will not use a link to a protocol B (only) capable node even 
though it passes via the pseudonode which appears to be protocol A and B 
capable.

So why don't we just form adjacencies on the LAN irrespective of the 
protocols supported? And then use multiple SPFs to sort out the mess. i.e. 
if you  only have single SPF capable routers you MUST follow the deployment 
rules. If you want mixed A,AB,B capable routers, then you MUST run multiple 
SPFs for A and B.

The only issue I can see is the case where the SPF indicates a node on the 
LAN as a next hop, but the first node doesn't (currently) have an adjacency 
to that node. The 10589 required behaviour in that case is to forward that 
packet to the DR (since the DR MUST have an adjacency otherwise it wouldn't 
have advertised it in its pseudonode). Clearly, this could fail if the DR 
wasn't in fact capable of forwarding the protocol in question.

But this is an obscure case (and was really only there for the case of OSI 
end-systems, which because of their relatively long ES-IS timers may take a 
while to form adjacencies with all routers in the face of packet loss).

A simple work around would be to give preference in the DR election to 
routers which were all protocol capable (either algorithmically, or by the 
simple expedient of giving them the highest priority).

But in any case this should only be a transient condition.

I don't think it warrants the complexity of multiple DR elections.

or am I missing something?


         Mik
At 10:31 27/11/2001 -0500, Ken Larmer wrote:

> > The UK submission further requires support for separate IP and OSI DISes
> > (similar to the separate DISes required for L1 and L2) on LANs to
> > eliminate implied adjacencies between OSI-only and IP-only nodes on the
> > LAN.
>
>         Is there a need for separate DISes at this point or is there a 
> need for
>separate Pseudonode LSPs from a single DIS? If we generate separate
>Pseudonode LSPs with the Protocols Supported field advertising the types of
>protocols supported for the LAN adjacencies contained within the associated
>LSP, won't that resolve this issue?
>
>         I.e. only build an OSI SPF tree for OSI adjacencies advertised in
>Pseudonode LSPs without a Protocols Supported field versus only build an IP
>SPF tree for IP adjacencies advertised in the Pseudonode LSP (LSP Number =
>0) possessing a Protocols Supported field = 0xcc. The draw back as I see it
>to implementing multiple Pseudonode LSPs is that, when we support more
>protocols within IS-IS, other than OSI and IP, this mechanism will break
>because we only check for the presence of the Protocols Supported field in
>LSPs with LSP number = 0. Of course, the RFC could be amended in this area
>to resolve this issue?
>
>Cheers,
>Ken Larmer
>
>_______________________________________________
>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 29 10:36:47 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14024
	for <isis-archive@odin.ietf.org>; Thu, 29 Nov 2001 10:36: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 HAA85524;
	Thu, 29 Nov 2001 07:55:49 -0800 (PST)
Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA85509
	for <isis-wg@spider.juniper.net>; Thu, 29 Nov 2001 07:54:26 -0800 (PST)
Received: (qmail 14042 invoked from network); 29 Nov 2001 15:33:27 -0000
Received: from unknown (HELO NEIL) ([66.92.83.66]) (envelope-sender <Larmer@CommSense.Net>)
          by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <mshand@cisco.com>; 29 Nov 2001 15:33:27 -0000
From: "Ken Larmer" <Larmer@commsense.net>
To: "mike shand" <mshand@cisco.com>
Cc: <jonathan.sadler@tellabs.com>, "Jeff Learman" <jlearman@cisco.com>,
        "Dave Katz" <dkatz@juniper.net>, <jparker@axiowave.com>,
        <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Message-ID: <FFEPKFEJDGEONDOGKAHCGECNCFAA.Larmer@CommSense.Net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <4.3.2.7.2.20011129111325.00ba2bc0@jaws.cisco.com>
Importance: Normal
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 29 Nov 2001 10:37:30 -0500
Content-Transfer-Encoding: 7bit

Hi Mike,

	Very good point about the election possibilities of a DR which does not
support both OSI and IP protocols on the same LAN! I agree with your
proposed resolution for this issue by giving DR election preference to ISs
which support both OSI and IP protocols. The only problem I see is that the
Protocols Supported field is not present in an OSI-only node's PDUs. So if
you have a Dual-OSI/IP IS versus an IP-Only IS, we will not be able to
differentiate between them from their LAN IIH PDUs. One resolution would be
to define the Protocols Supported field (which is currently defined in
RFC-1195) in ISO-10589 and provide a value for OSI.

	Am I out to lunch or will your recommendation with the above modifications,
along with the separate Pseudonode LSPs for OSI versus IP adjacencies
resolve this issue?

Cheers,
Ken Larmer
CommSense Networks

> It seems to me that it is a VERY bad idea to have multiple DRs on
> a LAN at
> the same level. This is not just a pseudonode issue, but also affects the
> role of the DR in providing error recovery for the flooding (update)
> process. Unlike the level 1/2 case, there are NOT distinct sets of LSPs
> carrying protocol A and protocol B information (indeed a single LSP can
> carry both sets of information). SO there is no sense in which the update
> process is partitioned between the two DRs.
>
> Or is the intention here that one of the DRs does the normal DR functions
> and generates a pseudonode for protocol A, while the other ONLY
> generates a
> pseudonode for protocol B?
>
> But in any case, I don't see the need for separate pseudonodes. If we are
> running separate SPFs for protocol A and B, then the pseudonode is simply
> treated as a node which is both A and B capable. A protocol A (only)
> capable Node will not use a link to a protocol B (only) capable node even
> though it passes via the pseudonode which appears to be protocol A and B
> capable.
>
> So why don't we just form adjacencies on the LAN irrespective of the
> protocols supported? And then use multiple SPFs to sort out the
> mess. i.e.
> if you  only have single SPF capable routers you MUST follow the
> deployment
> rules. If you want mixed A,AB,B capable routers, then you MUST
> run multiple
> SPFs for A and B.
>
> The only issue I can see is the case where the SPF indicates a
> node on the
> LAN as a next hop, but the first node doesn't (currently) have an
> adjacency
> to that node. The 10589 required behaviour in that case is to
> forward that
> packet to the DR (since the DR MUST have an adjacency otherwise
> it wouldn't
> have advertised it in its pseudonode). Clearly, this could fail if the DR
> wasn't in fact capable of forwarding the protocol in question.
>
> But this is an obscure case (and was really only there for the
> case of OSI
> end-systems, which because of their relatively long ES-IS timers
> may take a
> while to form adjacencies with all routers in the face of packet loss).
>
> A simple work around would be to give preference in the DR election to
> routers which were all protocol capable (either algorithmically,
> or by the
> simple expedient of giving them the highest priority).
>
> But in any case this should only be a transient condition.
>
> I don't think it warrants the complexity of multiple DR elections.
>
> or am I missing something?
>
>
>          Mik
> At 10:31 27/11/2001 -0500, Ken Larmer wrote:
>
> > > The UK submission further requires support for separate IP
> and OSI DISes
> > > (similar to the separate DISes required for L1 and L2) on LANs to
> > > eliminate implied adjacencies between OSI-only and IP-only
> nodes on the
> > > LAN.
> >
> >         Is there a need for separate DISes at this point or is there a
> > need for
> >separate Pseudonode LSPs from a single DIS? If we generate separate
> >Pseudonode LSPs with the Protocols Supported field advertising
> the types of
> >protocols supported for the LAN adjacencies contained within the
> associated
> >LSP, won't that resolve this issue?
> >
> >         I.e. only build an OSI SPF tree for OSI adjacencies
> advertised in
> >Pseudonode LSPs without a Protocols Supported field versus only
> build an IP
> >SPF tree for IP adjacencies advertised in the Pseudonode LSP
> (LSP Number =
> >0) possessing a Protocols Supported field = 0xcc. The draw back
> as I see it
> >to implementing multiple Pseudonode LSPs is that, when we support more
> >protocols within IS-IS, other than OSI and IP, this mechanism will break
> >because we only check for the presence of the Protocols
> Supported field in
> >LSPs with LSP number = 0. Of course, the RFC could be amended in
> this area
> >to resolve this issue?
> >
> >Cheers,
> >Ken Larmer
> >
> >_______________________________________________
> >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  Thu Nov 29 11:05:24 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16454
	for <isis-archive@odin.ietf.org>; Thu, 29 Nov 2001 11:05:23 -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 IAA85671;
	Thu, 29 Nov 2001 08:24:50 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id IAA85659
	for <isis-wg@spider.juniper.net>; Thu, 29 Nov 2001 08:23:29 -0800 (PST)
Received: from mshand-w2k.cisco.com (rtp-vpn1-195.cisco.com [10.82.224.195])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id QAA18644;
	Thu, 29 Nov 2001 16:01:43 GMT
Message-Id: <4.3.2.7.2.20011129155633.0375d9e0@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Ken Larmer" <Larmer@commsense.net>
From: mike shand <mshand@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: <jonathan.sadler@tellabs.com>, "Jeff Learman" <jlearman@cisco.com>,
        "Dave Katz" <dkatz@juniper.net>, <jparker@axiowave.com>,
        <isis-wg@spider.juniper.net>
In-Reply-To: <FFEPKFEJDGEONDOGKAHCGECNCFAA.Larmer@CommSense.Net>
References: <4.3.2.7.2.20011129111325.00ba2bc0@jaws.cisco.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 29 Nov 2001 16:02:01 +0000

At 10:37 29/11/2001 -0500, Ken Larmer wrote:
>Hi Mike,
>
>         Very good point about the election possibilities of a DR which 
> does not
>support both OSI and IP protocols on the same LAN! I agree with your
>proposed resolution for this issue by giving DR election preference to ISs
>which support both OSI and IP protocols. The only problem I see is that the
>Protocols Supported field is not present in an OSI-only node's PDUs. So if
>you have a Dual-OSI/IP IS versus an IP-Only IS, we will not be able to
>differentiate between them from their LAN IIH PDUs. One resolution would be
>to define the Protocols Supported field (which is currently defined in
>RFC-1195) in ISO-10589 and provide a value for OSI.

I don't care about the hellos, I do care about the LSPs. But either way I 
THOUGHT that it was permissible to put any value of NLPID (as defined by 
ISO TR 9577) in the protocols supported field,  and hence we could put one 
for OSI. So

No protocols supported = OSI only
IP + OSI protocols supported = dual
IP protocols supported = IP only

or is my memory failing me?

Of course there are backwards compatibility issues in all this.

         Mike



>         Am I out to lunch or will your recommendation with the above 
> modifications,
>along with the separate Pseudonode LSPs for OSI versus IP adjacencies
>resolve this issue?
>
>Cheers,
>Ken Larmer
>CommSense Networks
>
> > It seems to me that it is a VERY bad idea to have multiple DRs on
> > a LAN at
> > the same level. This is not just a pseudonode issue, but also affects the
> > role of the DR in providing error recovery for the flooding (update)
> > process. Unlike the level 1/2 case, there are NOT distinct sets of LSPs
> > carrying protocol A and protocol B information (indeed a single LSP can
> > carry both sets of information). SO there is no sense in which the update
> > process is partitioned between the two DRs.
> >
> > Or is the intention here that one of the DRs does the normal DR functions
> > and generates a pseudonode for protocol A, while the other ONLY
> > generates a
> > pseudonode for protocol B?
> >
> > But in any case, I don't see the need for separate pseudonodes. If we are
> > running separate SPFs for protocol A and B, then the pseudonode is simply
> > treated as a node which is both A and B capable. A protocol A (only)
> > capable Node will not use a link to a protocol B (only) capable node even
> > though it passes via the pseudonode which appears to be protocol A and B
> > capable.
> >
> > So why don't we just form adjacencies on the LAN irrespective of the
> > protocols supported? And then use multiple SPFs to sort out the
> > mess. i.e.
> > if you  only have single SPF capable routers you MUST follow the
> > deployment
> > rules. If you want mixed A,AB,B capable routers, then you MUST
> > run multiple
> > SPFs for A and B.
> >
> > The only issue I can see is the case where the SPF indicates a
> > node on the
> > LAN as a next hop, but the first node doesn't (currently) have an
> > adjacency
> > to that node. The 10589 required behaviour in that case is to
> > forward that
> > packet to the DR (since the DR MUST have an adjacency otherwise
> > it wouldn't
> > have advertised it in its pseudonode). Clearly, this could fail if the DR
> > wasn't in fact capable of forwarding the protocol in question.
> >
> > But this is an obscure case (and was really only there for the
> > case of OSI
> > end-systems, which because of their relatively long ES-IS timers
> > may take a
> > while to form adjacencies with all routers in the face of packet loss).
> >
> > A simple work around would be to give preference in the DR election to
> > routers which were all protocol capable (either algorithmically,
> > or by the
> > simple expedient of giving them the highest priority).
> >
> > But in any case this should only be a transient condition.
> >
> > I don't think it warrants the complexity of multiple DR elections.
> >
> > or am I missing something?
> >
> >
> >          Mik
> > At 10:31 27/11/2001 -0500, Ken Larmer wrote:
> >
> > > > The UK submission further requires support for separate IP
> > and OSI DISes
> > > > (similar to the separate DISes required for L1 and L2) on LANs to
> > > > eliminate implied adjacencies between OSI-only and IP-only
> > nodes on the
> > > > LAN.
> > >
> > >         Is there a need for separate DISes at this point or is there a
> > > need for
> > >separate Pseudonode LSPs from a single DIS? If we generate separate
> > >Pseudonode LSPs with the Protocols Supported field advertising
> > the types of
> > >protocols supported for the LAN adjacencies contained within the
> > associated
> > >LSP, won't that resolve this issue?
> > >
> > >         I.e. only build an OSI SPF tree for OSI adjacencies
> > advertised in
> > >Pseudonode LSPs without a Protocols Supported field versus only
> > build an IP
> > >SPF tree for IP adjacencies advertised in the Pseudonode LSP
> > (LSP Number =
> > >0) possessing a Protocols Supported field = 0xcc. The draw back
> > as I see it
> > >to implementing multiple Pseudonode LSPs is that, when we support more
> > >protocols within IS-IS, other than OSI and IP, this mechanism will break
> > >because we only check for the presence of the Protocols
> > Supported field in
> > >LSPs with LSP number = 0. Of course, the RFC could be amended in
> > this area
> > >to resolve this issue?
> > >
> > >Cheers,
> > >Ken Larmer
> > >
> > >_______________________________________________
> > >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

_______________________________________________
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 29 12:08:43 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA22381
	for <isis-archive@odin.ietf.org>; Thu, 29 Nov 2001 12:08:42 -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 JAA85937;
	Thu, 29 Nov 2001 09:27:50 -0800 (PST)
Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA85925
	for <isis-wg@spider.juniper.net>; Thu, 29 Nov 2001 09:26:43 -0800 (PST)
Received: (qmail 12309 invoked from network); 29 Nov 2001 17:05:44 -0000
Received: from unknown (HELO NEIL) ([66.92.83.66]) (envelope-sender <Larmer@CommSense.Net>)
          by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <mshand@cisco.com>; 29 Nov 2001 17:05:44 -0000
From: "Ken Larmer" <Larmer@commsense.net>
To: "mike shand" <mshand@cisco.com>
Cc: <jonathan.sadler@tellabs.com>, "Jeff Learman" <jlearman@cisco.com>,
        "Dave Katz" <dkatz@juniper.net>, <jparker@axiowave.com>,
        <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Message-ID: <FFEPKFEJDGEONDOGKAHCOECPCFAA.Larmer@CommSense.Net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <4.3.2.7.2.20011129155633.0375d9e0@jaws.cisco.com>
Importance: Normal
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 29 Nov 2001 12:09:46 -0500
Content-Transfer-Encoding: 7bit

Hi Mike,

> I don't care about the hellos, I do care about the LSPs.

I mentioned the hellos for 2 reasons, first we can not differentiate between
the protocols which are running on an IS unless there is an entry in the
Protocols Supported field of a LAN IIH PDU. Consequently, when running the
DR election process, we could not give proper preference to those ISes which
support Dual routing (i.e. there is currently no method for differentiating
between a Dual IS and an IP-Only IS). So, this field in a hello also needs
to possess the correct value advertising it as a Dual IS versus an IP-Only
IS.

Secondly to stay in compliance with RFC-1195, we must abide by the following
statement extracted from RFC-1195:

Dual routers must operate in a dual fashion on every link in the routing
domain over which they are running IS-IS. Thus, the value of the "protocols
supported" field must be identical on every link (i.e., for any one router
running IS-IS, all of the Hellos and LSPs transmitted by it must contain the
same "protocols supported" values).

> But either way I THOUGHT that it was permissible to put any value of NLPID
(as defined by
> ISO TR 9577) in the protocols supported field,  and hence we
> could put one
> for OSI. So
>
> No protocols supported = OSI only
> IP + OSI protocols supported = dual
> IP protocols supported = IP only

This makes a great deal of sense and I agree completely!

Cheers,
Ken Larmer
CommSense Networks

_______________________________________________
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 29 12:22:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA23600
	for <isis-archive@odin.ietf.org>; Thu, 29 Nov 2001 12:22:41 -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 JAA86015;
	Thu, 29 Nov 2001 09:41:49 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA86003
	for <isis-wg@spider.juniper.net>; Thu, 29 Nov 2001 09:40:36 -0800 (PST)
Received: from mshand-w2k.cisco.com (rtp-vpn1-195.cisco.com [10.82.224.195])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id RAA23032;
	Thu, 29 Nov 2001 17:18:46 GMT
Message-Id: <4.3.2.7.2.20011129171235.03712c30@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Ken Larmer" <Larmer@commsense.net>
From: mike shand <mshand@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Cc: <jonathan.sadler@tellabs.com>, "Jeff Learman" <jlearman@cisco.com>,
        "Dave Katz" <dkatz@juniper.net>, <jparker@axiowave.com>,
        <isis-wg@spider.juniper.net>
In-Reply-To: <FFEPKFEJDGEONDOGKAHCOECPCFAA.Larmer@CommSense.Net>
References: <4.3.2.7.2.20011129155633.0375d9e0@jaws.cisco.com>
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 29 Nov 2001 17:19:05 +0000

At 12:09 29/11/2001 -0500, Ken Larmer wrote:
>Hi Mike,
>
> > I don't care about the hellos, I do care about the LSPs.
>
>I mentioned the hellos for 2 reasons, first we can not differentiate between
>the protocols which are running on an IS unless there is an entry in the
>Protocols Supported field of a LAN IIH PDU. Consequently, when running the
>DR election process, we could not give proper preference to those ISes which
>support Dual routing (i.e. there is currently no method for differentiating
>between a Dual IS and an IP-Only IS). So, this field in a hello also needs
>to possess the correct value advertising it as a Dual IS versus an IP-Only
>IS.

Yes, you are right - you do need it to give dual capable nodes preference 
in an election. And maybe that is what you have to do for backwards 
compatibility reasons, but what I was saying (and this is completely off 
the wall) is that you could simply ignore the protocols supportedness in 
the hellos and always form an adjacency. In that case there would be no 
need to do anything special with the DR election, since by definition the 
DR (and hence the pseudonode) would have adjacencies to all routers on the 
LAN even if it didn't itself support the required protocol.

Then we would just leave it to the (separate) SPFs to actually figure out 
which W"next hops" to use (either natively, or doing some kind of 
autotunnel if necessary).

But maybe I've got this all wrong. I don't think what I'm "proposing" (and 
I use the word very loosely) has very good backwards compatibility 
properties in any case.

         Mike



>Secondly to stay in compliance with RFC-1195, we must abide by the following
>statement extracted from RFC-1195:
>
>Dual routers must operate in a dual fashion on every link in the routing
>domain over which they are running IS-IS. Thus, the value of the "protocols
>supported" field must be identical on every link (i.e., for any one router
>running IS-IS, all of the Hellos and LSPs transmitted by it must contain the
>same "protocols supported" values).
>
> > But either way I THOUGHT that it was permissible to put any value of NLPID
>(as defined by
> > ISO TR 9577) in the protocols supported field,  and hence we
> > could put one
> > for OSI. So
> >
> > No protocols supported = OSI only
> > IP + OSI protocols supported = dual
> > IP protocols supported = IP only
>
>This makes a great deal of sense and I agree completely!
>
>Cheers,
>Ken Larmer
>CommSense Networks

_______________________________________________
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 29 15:34:35 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09580
	for <isis-archive@odin.ietf.org>; Thu, 29 Nov 2001 15:34:35 -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 MAA86751;
	Thu, 29 Nov 2001 12:51:50 -0800 (PST)
Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA86733
	for <isis-wg@spider.juniper.net>; Thu, 29 Nov 2001 12:49:59 -0800 (PST)
Received: (qmail 20011 invoked from network); 29 Nov 2001 20:28:55 -0000
Received: from unknown (HELO NEIL) ([66.92.83.66]) (envelope-sender <Larmer@CommSense.Net>)
          by mail5.speakeasy.net (qmail-ldap-1.03) with SMTP
          for <mshand@cisco.com>; 29 Nov 2001 20:28:55 -0000
From: "Ken Larmer" <Larmer@commsense.net>
To: "mike shand" <mshand@cisco.com>
Cc: <jonathan.sadler@tellabs.com>, "Jeff Learman" <jlearman@cisco.com>,
        "Dave Katz" <dkatz@juniper.net>, <jparker@axiowave.com>,
        <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Protocols Supported field in pseudonode LSP
Message-ID: <FFEPKFEJDGEONDOGKAHCEEDECFAA.Larmer@CommSense.Net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
In-Reply-To: <4.3.2.7.2.20011129171235.03712c30@jaws.cisco.com>
Importance: Normal
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 29 Nov 2001 15:32:58 -0500
Content-Transfer-Encoding: 7bit


> Yes, you are right - you do need it to give dual capable nodes preference
> in an election. And maybe that is what you have to do for backwards
> compatibility reasons, but what I was saying (and this is completely off
> the wall) is that you could simply ignore the protocols supportedness in
> the hellos and always form an adjacency. In that case there would be no
> need to do anything special with the DR election, since by definition the
> DR (and hence the pseudonode) would have adjacencies to all
> routers on the
> LAN even if it didn't itself support the required protocol.
>
> Then we would just leave it to the (separate) SPFs to actually figure out
> which W"next hops" to use (either natively, or doing some kind of
> autotunnel if necessary).
>
> But maybe I've got this all wrong. I don't think what I'm
> "proposing" (and
> I use the word very loosely) has very good backwards compatibility
> properties in any case.

Doesn't the fact that most vendors do not support forming adjacencies with
an IS who possesses a different IP subnet (even though RFC-1195 clearly
states to form an adjacency with such an IS and forward between subnets) and
the following statement extracted from the Dijkstra Calculation and
forwarding section of RFC-1195, create some problems?

What if the DR is an OSI-Only IS?

C.1.4 The Algorithm
...
8) Now add systems to which the local router does not have adjacencies, but
which are mentioned in neighboring pseudonode LSPs. The adjacency for such
systems is set to that of the designated router...


	In order to relax the configuration rules, I believe the following MAY work
fine?

1. Give the DR Election preference to ISes which serve as a Dual-IS.

2. Place the NLPID in the Pseudonode LSP for the supported entries contain
within (i.e. 0xcc = IP capable neighbors).

3. DR generation of multiple Pseudonode LSPs for each protocol supported.

4. Creation of additional definitions for future NLPIDs. (IPv6, toaster
protocol...)

5. Relax the restriction on checking for the NLPID in LSP #0 only LSPs.

	The only problem I can see with this scenario is when you have a mixed LAN
and there are IP-Only or OSI-Only ISes which can serve as the DR. Though, I
suppose you could really break any protocol if it were miss configured
sufficiently?

Cheers,
Ken Larmer
CommSense Networks

_______________________________________________
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 29 17:35:35 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18155
	for <isis-archive@odin.ietf.org>; Thu, 29 Nov 2001 17:35:34 -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 OAA87304;
	Thu, 29 Nov 2001 14:52:50 -0800 (PST)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA87292
	for <isis-wg@spider.juniper.net>; Thu, 29 Nov 2001 14:51:08 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734290122FEB6@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
Cc: "Bert Wijnen (Bert) (E-mail)" <bwijnen@lucent.com>,
        "'KChapman@unispherenetworks.com'" <KChapman@unispherenetworks.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] Aligning MIB values with Implementation values
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 29 Nov 2001 17:29:55 -0500

I've received the following request to align MIB values with
implementation values.  

As Neal notes, I had been following an admonition to avoid the
use of 0 as the value of an enumeration.  However, I don't
think this is a prohibition.  

There are two things we could do:
	Make the mapping be the identity (so that Up becomes 0, etc)
	Make the mapping be addition (subtraction) by 1

Any objections to doing the first?

- jeff parker
- axiowave networks

///////////////////////////////////////////////////

Jeff,

The isisISAdjState values are inconsistent with the those in the 3-way
handshake draft.  Because of this, my code must translate between the two.

The MIB has values:

           Initializing 1
           Up           2
           Down         4

Whereas the 3-way handshake draft has these different values for adjacency
state:

           Initializing 1
           Up           0
           Down         2

Any chance the MIB values could be made to be consistent?  I note that in
the MIB there appears to be a desire to avoid the use of the number "0" as a
value for an entry, and so in this case giving values such as Up 1,
Initializing 2, Down 3, would be pretty good since there is an easy function
to map between the two values.

Secondly, the fields for Adjacency usage are inconsistent with those values
that one might use to index into the 10589 state tables for received hellos
(8.2.4.2).  Looking at table 6, which contains all the indecis, the ideal
index values for adjusage would be:


             None:          0
             L1:            1
             L1andL2:       2
             L2-only        3

The mib has values:
             Undefined:     1
             level1         2
             level2         3
             level1and2     4

As before, if 0 is being avoided values such as none: 1 l1: 2, l1andl2 3
l2-only 4, would be preferable.

I realize this isn't terribly important, but there is some confusing code
that maps between the table indices and the MIB values that makes this part
of the code a little more difficult to read.  No translation would improve
this bit of code's readability.

Thanks for your attention,

  --Neal
_______________________________________________
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 30 05:33:43 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA01498
	for <isis-archive@lists.ietf.org>; Fri, 30 Nov 2001 05:33:42 -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 CAA90201;
	Fri, 30 Nov 2001 02:51:51 -0800 (PST)
Received: from web11207.mail.yahoo.com (web11207.mail.yahoo.com [216.136.131.189])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id CAA90189
	for <Isis-wg@spider.juniper.net>; Fri, 30 Nov 2001 02:50:52 -0800 (PST)
Message-ID: <20011130102947.76302.qmail@web11207.mail.yahoo.com>
Received: from [203.196.145.150] by web11207.mail.yahoo.com via HTTP; Fri, 30 Nov 2001 02:29:47 PST
From: Aravind Ravikumar <aravindravikumar@yahoo.com>
To: Isis-wg@spider.juniper.net
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-1820195145-1007116187=:76279"
Subject: [Isis-wg] doubt regarding manual area addresses
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: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 30 Nov 2001 02:29:47 -0800 (PST)

--0-1820195145-1007116187=:76279
Content-Type: text/plain; charset=us-ascii


Hi,

Can any body please clarify the following doubts regarding manual area address
What is difference in the information included in manual area address option in the following packets hello packets(level1 ,level2, point to point)level1 lsp number 0,level2 lsp number 0 Is there any difference in the way  a router uses the configured area addresses and the area addresses which it learns from other routers Thanking in advance,Aravind 


---------------------------------
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
--0-1820195145-1007116187=:76279
Content-Type: text/html; charset=us-ascii

<P>Hi,</P>
<P>Can any body please clarify the following doubts regarding manual area address</P>
<DIV><FONT face=Arial size=2>What is difference in the&nbsp;information included in manual area address option in the following packets</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT>&nbsp;</DIV>
<DIV>hello packets(level1 ,level2, point to point)</DIV>
<DIV><FONT face=Arial size=2>level1 lsp number 0,</FONT></DIV>
<DIV><FONT face=Arial size=2>level2 lsp number 0</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=Arial size=2>Is there any difference in the way&nbsp; a router uses the configured area addresses and the area addresses which&nbsp;it learns from other routers</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>Thanking in advance,</DIV>
<DIV>Aravind</DIV>
<DIV>&nbsp;</DIV><p><br><hr size=1><b>Do You Yahoo!?</b><br>
<a href="http://geocities.yahoo.com/ps/info1">Yahoo! GeoCities</a> - quick and easy web site hosting, just $8.95/month.
--0-1820195145-1007116187=:76279--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


