From isis-wg-admin@ietf.org  Thu Sep  5 13:00:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25414
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:00:12 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Gv2p10466;
	Thu, 5 Sep 2002 12:57:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by optimus.ietf.org (8.11.6/8.11.6) with ESMTP id g7M1gLW19746
	for <isis-wg@optimus.ietf.org>; Wed, 21 Aug 2002 21:42:21 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA02134
	for <isis-wg@ietf.org>; Wed, 21 Aug 2002 21:40:48 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17hgyo-0000HL-00; Wed, 21 Aug 2002 18:41:46 -0700
Message-ID: <87r8gry8it.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: jparker@axiowave.com, isis-wg@ietf.org
Cc: kay@ipinfusion.com
In-Reply-To: <87adnhf0rq.wl@ipinfusion.com>
References: <87adnhf0rq.wl@ipinfusion.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] Re: index of isisISAdjIPAddrEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 21 Aug 2002 18:41:46 -0700

Hi Jeff,

# I didn't receive previous mail and those mail is not in the archive itself.
# Do you know what's going on in the mailing list itself? ;P

> This time is the index of isisISAdjIPAddrEntry.
> 
> Like other entries, isisSummAddrEntry and isisRedistributeEntry, let's
> use isisISAdjIPAddressType and isisISAdjIPAddress instead of
> isisISAdjIPAddrIndex as the index of isisISAdjIPAddrEntry.

	I saw the mailing list archive and I'm the guy who suggested to
	remove the isisISAdjIPAddress itself. Sorry for the back and
	forth comments.

	But the point is the consistency between those three entries.

	- isisSummAddrEntry
	- isisRedistributeEntry
	- isisISAdjIPAddrEntry

	Top two have the InetAddress type index and the bottom one doesn't.
	This makes a confusion to me.

	Could you clarify that point, Jeff?

    isisSummAddrEntry OBJECT-TYPE
        SYNTAX IsisSummAddrEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry contains one IP summary address."

        INDEX { isisSysInstance,
                isisSummAddressType,
                isisSummAddress,
                isisSummAddrPrefixLen }
    ::= { isisSummAddrTable 1 }

    isisRedistributeAddrEntry OBJECT-TYPE
        SYNTAX IsisRedistributeAddrEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry contains one IP summary address to
             manage leaking L2 addresses into L1."
        INDEX { isisSysInstance,
                isisRedistributeAddrType,
                isisRedistributeAddrAddress,
                isisRedistributeAddrPrefixLen }
    ::= { isisRedistributeAddrTable 1 }

    isisISAdjIPAddrEntry OBJECT-TYPE
        SYNTAX IsisISAdjIPAddrEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry contains one IP Address reported by a
             neighboring Intermediate System in its IIH PDUs."
        INDEX { isisSysInstance,
                isisCircIndex,
                isisISAdjIndex,
                isisISAdjIPAddrIndex
                }
    ::= { isisISAdjIPAddrTable 1 }

> And let's omit isisISAdjIPAddrIndex itself like below.
> 
>     isisISAdjIPAddrEntry OBJECT-TYPE
>         SYNTAX IsisISAdjIPAddrEntry
>         MAX-ACCESS not-accessible
>         STATUS current
>         DESCRIPTION
>             "Each entry contains one IP Address reported by a
>              neighboring Intermediate System in its IIH PDUs."
>         INDEX { isisSysInstance,
>                 isisCircIndex,
>                 isisISAdjIndex,
>                 isisISAdjIPAddressType
>                 isisISAdjIPAddress }
>     ::= { isisISAdjIPAddrTable 1 }
> 
>     IsisISAdjIPAddrEntry ::=
>         SEQUENCE {
>             isisISAdjIPAddressType
>                  InetAddressType,
>             isisISAdjIPAddress
>                 InetAddress
>         }
> 
> Thank you,
> 
> 								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:01:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25471
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:01:07 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85GxBp10646;
	Thu, 5 Sep 2002 12:59:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7MKPso16401
	for <isis-wg@optimus.ietf.org>; Thu, 22 Aug 2002 16:25:54 -0400
Received: from dmz1.procket.com (dmz1.procket.com [65.174.124.36])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA09433
	for <isis-wg@ietf.org>; Thu, 22 Aug 2002 16:24:24 -0400 (EDT)
Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60])
	by dmz1.procket.com (Postfix) with ESMTP id C8DA623C3A
	for <isis-wg@ietf.org>; Thu, 22 Aug 2002 14:09:53 -0700 (PDT)
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 g7MKPJiI018947
	for <isis-wg@ietf.org>; Thu, 22 Aug 2002 13:25:19 -0700 (PDT)
Received: (from tli@localhost)
	by alpha-tli.procket.com (8.12.1/8.12.1) id g7MKPIpM017823;
	Thu, 22 Aug 2002 13:25:18 -0700
From: Tony Li <tli@procket.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15717.18606.765620.39339@alpha-tli.procket.com>
To: isis-wg@ietf.org
X-Mailer: VM 6.92 under Emacs 20.5.1
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] Test message
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 22 Aug 2002 13:25:18 -0700
Content-Transfer-Encoding: 7bit


This message is only a test.  No TLVs are
included.  Do not trigger SPF.

Tony


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:03:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25572
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:03:05 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85H1Dp10846;
	Thu, 5 Sep 2002 13:01:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QKYeo20217
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 16:34:40 -0400
Received: from rchss001.chiaro.com (rchss001.chiaro.com [63.88.196.81])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA21548
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 16:33:05 -0400 (EDT)
Received: (qmail 1254 invoked from network); 26 Aug 2002 20:18:37 -0000
Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81)
  by rchss001.chiaro.com with SMTP; 26 Aug 2002 20:18:37 -0000
Received: by MAIL with Internet Mail Service (5.5.2653.19)
	id <RP756FJA>; Mon, 26 Aug 2002 15:26:48 -0500
Message-ID: <F69EB380D594D611BBEA00065B3F14B403297B@MAIL>
From: May Lu <mlu@chiaro.com>
To: "'mshand@cisco.com'" <mshand@cisco.com>,
        "'isis-wg@ietf.org'"
	 <isis-wg@ietf.org>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary"
Subject: [Isis-wg] Questions about "restart signaling for ISIS"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 15:26:47 -0500

--=_IS_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"

Hi Mike,

I have some questions about draft-ietf-isis-restart-01.txt (May 2002)
version. 

1. Can the restarting router changes its extended local circuit id during
restart?
The extended local circuit id is included in the "Point-to-Point Adjacency
State" TLV. If the restarting router sends an IIH with RR bit set but with a
different circuit id, should the receiving routers drop the IIH or accept
the IIH and update the adjacency information to store the new neighbor
extended circuit id?

2. Based on the draft, on LAN circuit, the receiving router with the highest
LnRouterPriority (with highest source MAC address breaking ties) among those
routers supporting the graceful restart, initiate the CSNPs/LSPs
transmission when a restarting router asks for help. If the receiving router
with highest priority goes offline when an IIH with RR bit set arrives,
should another router initiates the CSNPs/LSPs transmission or the
restarting router gets t1 expiry on this interface and fails the graceful
restart?

Thanks,
Xiaomei







--=_IS_MIME_Boundary
Content-Type: text/plain;charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

----------------------------------------- (on rchss001)

This e-mail and any files transmitted with it are the property
of Chiaro Networks, Ltd., and may contain confidential and 
privileged material for the sole use of the intended recipient(s)
to whom this e-mail is addressed. If you are not one of the named
recipient(s), or otherwise have reason to believe that you have 
received this message in error, please notify the sender and 
delete all copies from your system.  Any other use, retention, 
dissemination, forwarding, printing or copying of this e-mail is 
strictly prohibited.


---------------------------------------------------------

--=_IS_MIME_Boundary--
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:05:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25761
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:05:18 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85H3Hp11011;
	Thu, 5 Sep 2002 13:03:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7MElxo29176
	for <isis-wg@optimus.ietf.org>; Thu, 22 Aug 2002 10:47:59 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27773
	for <isis-wg@ietf.org>; Thu, 22 Aug 2002 10:46:29 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H1900H7B2G4TA@mta2.huawei.com> for isis-wg@ietf.org;
 Thu, 22 Aug 2002 22:48:04 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H1900I6X2G20V@mta2.huawei.com> for isis-wg@ietf.org;
 Thu, 22 Aug 2002 22:48:03 +0800 (CST)
Received: from huaweisarav ([10.18.4.64])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H192HC00.I1H for <isis-wg@ietf.org>; Thu,
 22 Aug 2002 22:48:48 +0800
From: Saravana Kumar <saravanak@huawei.com>
To: isis <isis-wg@ietf.org>
Message-id: <001501c249eb$04af8870$4004120a@huaweisarav>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [Isis-wg] Questions on IS-IS Restart Signalling
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 22 Aug 2002 20:18:46 +0530
Content-Transfer-Encoding: 7BIT

Hello There,

I have a few questions on the IS-IS Restart Signaling draft
 draft-ietf-isis-restart-01.txt ), My understanding of IS-IS and this draft
is still a bit patchy and i hope to clear them up before i start
implementing it. Here goes...

- Is it necessary that the 3-way handshake be implemented on the system for
the restart signaling work ? I guess this draft is written keeping in mind
the extra processing we have to do incase the 3-way handshake is implemented
on the system. Otherwise it is not really mandatory is it ?

 - In section "4.2 Adjacent re-acquisition" : The following clause is not
very clear to me.

   "DO NOT refresh the timer on the adjacency, but leave the
     adjacency in state "Up","

  I assume the timer being referred to here is the Adjacency Hold Timer for
the particular adjacency. What does "DO NOT refresh the timer on the
adjacency" mean here ? If we don't reset it ( im assuming refresh = reset )
the timer is gonna sooner rather than later, which is not what we wanted in
the first place.

- In section "4.3.1.2 Restarting" :
    Do we have to store the sequence numbers of the routers 'own' LSP's in
some non-volatile memory before the router restarts and use the stored
sequence numbers to generate the LSP's ? or do have to first purge all our
'own' LSP's by setting its remaining lifetime to zero and flooding it and
then after the zero-age timer expires, re-originate the LSPs again freshly.

This is it for now.. Thanks,
Sarav

PS : I would also appreciate it if someone answered my question on MTU
changes in the IS-IS router, which i posted to this list yesterday.




_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:07:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA25965
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:07:12 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85H5Jp11155;
	Thu, 5 Sep 2002 13:05:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by optimus.ietf.org (8.11.6/8.11.6) with ESMTP id g7LGdxW25766
	for <isis-wg@optimus.ietf.org>; Wed, 21 Aug 2002 12:39:59 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11721
	for <isis-wg@ietf.org>; Wed, 21 Aug 2002 10:45:50 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA06556
	for <isis-wg@ietf.org>; Wed, 21 Aug 2002 10:46:42 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA24669
	for <isis-wg@ietf.org>; Wed, 21 Aug 2002 10:46:43 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <RHFQ5137>; Wed, 21 Aug 2002 10:46:42 -0400
Message-ID: <313680C9A886D511A06000204840E1CF529CD2@whq-msgusr-02.pit.comms.marconi.com>
From: "Harwani, Sanjay" <Sanjay.Harwani@marconi.com>
To: isis-wg@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] Question about router id
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 21 Aug 2002 10:46:39 -0400

Hi All,

I would like to know how IS-IS should handle (convey) router_address
which is an important piece of information for creating tunnels.

Is there a mechanism defined to carry this information?

Thanks
Sanjay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:09:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26205
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:09:26 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85H7Mp11307;
	Thu, 5 Sep 2002 13:07:22 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QMwHo26700
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 18:58:17 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24899
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 18:56:42 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74115@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Ramalingam, Swaminathan'" <swaminathanr@netplane.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: ISIS MIB: Circuit & Level Table
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 18:57:29 -0400

> Jeff -
> 
> I am little bit concerned about Granularity of Hello Timer 
> and LSPThrottle timer. Why the reason it is in 
> "milliseconds"?, why it can't be in seconds?..

Replying to the group list.

The Hello timer used to be in seconds, but there was interest 
in working on "fast hellos" to allow faster detection of link 
failure.  While 1/1000 of a second is too small, milliseconds
are a common unit of measure.  

It has been common to send multiple LSPs per second for some
time.  Of course, other units of measure are possible.  

> Even if it is in milliseconds, i feel 1000 is the MINIMUM 
> reasonable value instead of 10. This not only affect the 
> protocol, but complicates the implementation.
> 
> Swami

Your implementation can enforce a range of > 1000 for hellos, 
or > 3000 if you like.  Does this really complicate your
implementation?  

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:11:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26372
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:11:41 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85H9Qp11480;
	Thu, 5 Sep 2002 13:09:26 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QMiso26353
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 18:44:54 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24643
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 18:43:19 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74114@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Noguchi Kay'" <kay@ipinfusion.com>, isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: index of isisISAdjIPAddrEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 18:43:39 -0400

Kay -
	Could you take a look at the current version of
the MIB and rephrase your question?  The 09 version
has a different index, which may alter your request.  

- jeff parker

> Hi Jeff,
> 
> This time is the index of isisISAdjIPAddrEntry.
> 
> Like other entries, isisSummAddrEntry and isisRedistributeEntry, let's
> use isisISAdjIPAddressType and isisISAdjIPAddress instead of
> isisISAdjIPAddrIndex as the index of isisISAdjIPAddrEntry.
> 
> And let's omit isisISAdjIPAddrIndex itself like below.
> 
>     isisISAdjIPAddrEntry OBJECT-TYPE
>         SYNTAX IsisISAdjIPAddrEntry
>         MAX-ACCESS not-accessible
>         STATUS current
>         DESCRIPTION
>             "Each entry contains one IP Address reported by a
>              neighboring Intermediate System in its IIH PDUs."
>         INDEX { isisSysInstance,
>                 isisCircIndex,
>                 isisISAdjIndex,
>                 isisISAdjIPAddressType
>                 isisISAdjIPAddress }
>     ::= { isisISAdjIPAddrTable 1 }
> 
>     IsisISAdjIPAddrEntry ::=
>         SEQUENCE {
>             isisISAdjIPAddressType
>                  InetAddressType,
>             isisISAdjIPAddress
>                 InetAddress
>         }
> 
> Thank you,
> 
> 								kay
> 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:13:50 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26534
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:13:50 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HC3p11649;
	Thu, 5 Sep 2002 13:12:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QNUGo28192
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 19:30:16 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25691
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 19:28:40 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74116@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Noguchi Kay'" <kay@ipinfusion.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: index of isisISAdjEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 19:29:29 -0400

> I have a question about isisISAdjIndex in isisISAdjEntry.
> 
> You discribed isisISAdjIndex like below but I don't understand what
> the adjacencies itself.
> 
>     isisISAdjIndex OBJECT-TYPE
>         SYNTAX Integer32 (1..2000000000)
>         MAX-ACCESS not-accessible
>         STATUS current
>         DESCRIPTION
>             "A unique value identifying the IS adjacency from all
>              other such adjacencies on this circuit. This value is
>              assigned by the system when the adjacency is created
>              automatically."
>     ::= { isisISAdjEntry 1 }
> 
> Okay, I'm gonna use the example. If you have one L1L2 
> neighbor instance,
> how many adjacencies do you have?
> 
> 	a) Only one adjacency.
> 	b) Two adjacencies, one for L1 adjacency and one for L2 
> adjacency.

On P2P circuits, there would be one adjacency.
On a LAN there would be two.  

> I think you mean b) because we have some entries which have 
> different value
> for L1 and L2 adjacencies in the isisISAdjEntry shown below.
> 
> 	isisISAdjState
> 	isisISAdjHoldTimer
> 	isisISAdjNeighPriority
> 	isisISAdjUpTime

I agree in the case of a LAN.
On a p2p, we create the adjacency at one instant,
so these would be the same for the two levels.  
 
>     isisISAdjEntry OBJECT-TYPE
>         SYNTAX IsisISAdjEntry
>         MAX-ACCESS not-accessible
>         STATUS current
>         DESCRIPTION
>             "Each entry corresponds to one adjacency to an
>              Intermediate System on this system."
>         INDEX { isisSysInstance,
>                 isisCircIndex,
>                 isisISAdjIndex
>                 isisISAdjLevelIndex }
>     ::= { isisISAdjTable 1 }
 
I think this is taken from a prior version.  Take a look 
at the 09 version of the MIB and see if your issue remains.  
There are certainly issues that arrise with the two 
formats of adjacency.  

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:15:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26697
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:15:59 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HE6p11827;
	Thu, 5 Sep 2002 13:14:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QNhMo28983
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 19:43:22 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25934
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 19:41:46 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17jTVK-0000YC-00; Mon, 26 Aug 2002 16:42:42 -0700
Message-ID: <877kidjifw.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: Jeff Parker <jparker@axiowave.com>
Cc: "'Noguchi Kay'" <kay@ipinfusion.com>, isis-wg@ietf.org
In-Reply-To: <EB5FFC72F183D411B38200062957342902A74114@r2d2.axiowave.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: multipart/mixed;
 boundary="Multipart_Mon_Aug_26_16:42:27_2002-1"
Subject: [Isis-wg] Re: index of isisISAdjIPAddrEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 16:42:27 -0700

--Multipart_Mon_Aug_26_16:42:27_2002-1
Content-Type: text/plain; charset=US-ASCII

Hi Jeff,

> 	Could you take a look at the current version of
> the MIB and rephrase your question?  The 09 version
> has a different index, which may alter your request.  

	I only referencing -09 draft. I totaly forgat about -08 version. :p
	If you have -10 draft, please send it to me. ;P

	And I sent another mail that corrected my point regarding
	isisISAdjIPAddrEntry. I've attached that mail.

	My point is the consistency between those three.

	- isisSummAddrEntry
	- isisRedistributeEntry
	- isisISAdjIPAddrEntry

	The Upper two use *AddressType, *Address and *AddrPrefixlen as an
	index and the last one uses *IPAddrIndex.

	So then I sent a mail to sync isisISAdjIPAddrEntry back again
	to the other two.

Thank you,

								kay

> 
> > Hi Jeff,
> > 
> > This time is the index of isisISAdjIPAddrEntry.
> > 
> > Like other entries, isisSummAddrEntry and isisRedistributeEntry, let's
> > use isisISAdjIPAddressType and isisISAdjIPAddress instead of
> > isisISAdjIPAddrIndex as the index of isisISAdjIPAddrEntry.
> > 
> > And let's omit isisISAdjIPAddrIndex itself like below.
> > 
> >     isisISAdjIPAddrEntry OBJECT-TYPE
> >         SYNTAX IsisISAdjIPAddrEntry
> >         MAX-ACCESS not-accessible
> >         STATUS current
> >         DESCRIPTION
> >             "Each entry contains one IP Address reported by a
> >              neighboring Intermediate System in its IIH PDUs."
> >         INDEX { isisSysInstance,
> >                 isisCircIndex,
> >                 isisISAdjIndex,
> >                 isisISAdjIPAddressType
> >                 isisISAdjIPAddress }
> >     ::= { isisISAdjIPAddrTable 1 }
> > 
> >     IsisISAdjIPAddrEntry ::=
> >         SEQUENCE {
> >             isisISAdjIPAddressType
> >                  InetAddressType,
> >             isisISAdjIPAddress
> >                 InetAddress
> >         }
> > 
> > Thank you,
> > 
> > 								kay
> > 

--Multipart_Mon_Aug_26_16:42:27_2002-1
Content-Type: message/rfc822

Date: Wed, 21 Aug 2002 18:41:46 -0700
Message-ID: <87r8gry8it.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: jparker@axiowave.com, isis-wg@ietf.org
Cc: kay@ipinfusion.com
Subject: Re: index of isisISAdjIPAddrEntry
In-Reply-To: <87adnhf0rq.wl@ipinfusion.com>
References: <87adnhf0rq.wl@ipinfusion.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII

Hi Jeff,

# I didn't receive previous mail and those mail is not in the archive itself.
# Do you know what's going on in the mailing list itself? ;P

> This time is the index of isisISAdjIPAddrEntry.
> 
> Like other entries, isisSummAddrEntry and isisRedistributeEntry, let's
> use isisISAdjIPAddressType and isisISAdjIPAddress instead of
> isisISAdjIPAddrIndex as the index of isisISAdjIPAddrEntry.

	I saw the mailing list archive and I'm the guy who suggested to
	remove the isisISAdjIPAddress itself. Sorry for the back and
	forth comments.

	But the point is the consistency between those three entries.

	- isisSummAddrEntry
	- isisRedistributeEntry
	- isisISAdjIPAddrEntry

	Top two have the InetAddress type index and the bottom one doesn't.
	This makes a confusion to me.

	Could you clarify that point, Jeff?

    isisSummAddrEntry OBJECT-TYPE
        SYNTAX IsisSummAddrEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry contains one IP summary address."

        INDEX { isisSysInstance,
                isisSummAddressType,
                isisSummAddress,
                isisSummAddrPrefixLen }
    ::= { isisSummAddrTable 1 }

    isisRedistributeAddrEntry OBJECT-TYPE
        SYNTAX IsisRedistributeAddrEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry contains one IP summary address to
             manage leaking L2 addresses into L1."
        INDEX { isisSysInstance,
                isisRedistributeAddrType,
                isisRedistributeAddrAddress,
                isisRedistributeAddrPrefixLen }
    ::= { isisRedistributeAddrTable 1 }

    isisISAdjIPAddrEntry OBJECT-TYPE
        SYNTAX IsisISAdjIPAddrEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry contains one IP Address reported by a
             neighboring Intermediate System in its IIH PDUs."
        INDEX { isisSysInstance,
                isisCircIndex,
                isisISAdjIndex,
                isisISAdjIPAddrIndex
                }
    ::= { isisISAdjIPAddrTable 1 }

> And let's omit isisISAdjIPAddrIndex itself like below.
> 
>     isisISAdjIPAddrEntry OBJECT-TYPE
>         SYNTAX IsisISAdjIPAddrEntry
>         MAX-ACCESS not-accessible
>         STATUS current
>         DESCRIPTION
>             "Each entry contains one IP Address reported by a
>              neighboring Intermediate System in its IIH PDUs."
>         INDEX { isisSysInstance,
>                 isisCircIndex,
>                 isisISAdjIndex,
>                 isisISAdjIPAddressType
>                 isisISAdjIPAddress }
>     ::= { isisISAdjIPAddrTable 1 }
> 
>     IsisISAdjIPAddrEntry ::=
>         SEQUENCE {
>             isisISAdjIPAddressType
>                  InetAddressType,
>             isisISAdjIPAddress
>                 InetAddress
>         }
> 
> Thank you,
> 
> 								kay

--Multipart_Mon_Aug_26_16:42:27_2002-1--
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:18:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26889
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:18:12 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HGAp12049;
	Thu, 5 Sep 2002 13:16:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QNtMo29354
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 19:55:22 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26163
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 19:53:46 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17jTh5-0000YH-00; Mon, 26 Aug 2002 16:54:52 -0700
Message-ID: <8765xxjhvc.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: Jeff Parker <jparker@axiowave.com>
Cc: "'Noguchi Kay'" <kay@ipinfusion.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
In-Reply-To: <EB5FFC72F183D411B38200062957342902A74116@r2d2.axiowave.com>
References: <EB5FFC72F183D411B38200062957342902A74116@r2d2.axiowave.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] Re: index of isisISAdjEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 16:54:47 -0700

Hi Jeff,

> > Okay, I'm gonna use the example. If you have one L1L2 
> > neighbor instance,
> > how many adjacencies do you have?
> > 
> > 	a) Only one adjacency.
> > 	b) Two adjacencies, one for L1 adjacency and one for L2 
> > adjacency.
> 
> On P2P circuits, there would be one adjacency.
> On a LAN there would be two.  
> 
> > I think you mean b) because we have some entries which have 
> > different value
> > for L1 and L2 adjacencies in the isisISAdjEntry shown below.
> > 
> > 	isisISAdjState
> > 	isisISAdjHoldTimer
> > 	isisISAdjNeighPriority
> > 	isisISAdjUpTime
> 
> I agree in the case of a LAN.
> On a p2p, we create the adjacency at one instant,
> so these would be the same for the two levels.  

	Then, how about to use isisCircuitType in the isisCircuitCounterEntry
	as the isisISAdjLevelIndex like below.

    isisISAdjEntry OBJECT-TYPE
        SYNTAX IsisISAdjEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry corresponds to one adjacency to an
             Intermediate System on this system."
        INDEX { isisSysInstance,
                isisCircIndex,
                isisISAdjIndex
                isisISAdjLevelIndex }
    ::= { isisISAdjTable 1 }

    isisISAdjLevelIndex OBJECT-TYPE
        SYNTAX INTEGER
            {
                lanlevel1(1),
                lanlevel2(2),
                p2pcircuit(3)
            }
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "What type of level these adjacency is?

             The point to point Hello PDU includes
             both L1 and L2, and ISs form a single
             adjacency on point to point links.
             Thus we combine counts on
             point to point links into one group."
    ::= { isisISAdjEntry 2 }

> I think this is taken from a prior version.  Take a look 
> at the 09 version of the MIB and see if your issue remains.  
> There are certainly issues that arrise with the two 
> formats of adjacency.  

	I didn't see any old draft instead of -08 so that maight exist
	in the previous draft or not. But based on the current -09 draft,
	we have a problem to express the adjacent neighbor in the
	isisAdj*Entry.

	Here is the current -09 version's isisAdjEntry which doesn't have
	level information in the index.

    isisISAdjEntry OBJECT-TYPE
        SYNTAX IsisISAdjEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry corresponds to one adjacency to an
             Intermediate System on this system."
        INDEX { isisSysInstance,
                isisCircIndex,
                isisISAdjIndex }
    ::= { isisISAdjTable 1 }


								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:20:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26977
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:20:14 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HICp12213;
	Thu, 5 Sep 2002 13:18:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7R013o29493
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 20:01:03 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA26252
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 19:59:27 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74118@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Noguchi Kay'" <kay@ipinfusion.com>, Jeff Parker <jparker@axiowave.com>
Cc: isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: index of isisISAdjIPAddrEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 20:00:12 -0400

> 	My point is the consistency between those three.
> 
> 	- isisSummAddrEntry
> 	- isisRedistributeEntry
> 	- isisISAdjIPAddrEntry
> 
> 	The Upper two use *AddressType, *Address and 
> *AddrPrefixlen as an index and the last one uses *IPAddrIndex.
> 
> > > 
> > > And let's omit isisISAdjIPAddrIndex itself like below.

Kay -
	You have a good point.  In the first two tables, the
index is an IP address.  In the third, an index was
introduced to spare the user from having to deal with
an IP address as an index.  
	In the third table there are multiple indexes, 
while in the first two the address is (almost) the only
index.  I've had more than one request to avoid using
addresses as indicies.  Using an IP address as an index
seems more difficult to deal with with when there are many
indicies.  
	I will file your request away for the next version.

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:22:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27067
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:22:12 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HKFp12417;
	Thu, 5 Sep 2002 13:20:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7R1Bdo00467
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 21:11:39 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27667
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 21:10:02 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17jUsy-0000ZZ-00; Mon, 26 Aug 2002 18:11:12 -0700
Message-ID: <87znv9hzrk.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: Jeff Parker <jparker@axiowave.com>
Cc: "'Noguchi Kay'" <kay@ipinfusion.com>, isis-wg@ietf.org
In-Reply-To: <EB5FFC72F183D411B38200062957342902A7411C@r2d2.axiowave.com>
References: <EB5FFC72F183D411B38200062957342902A7411C@r2d2.axiowave.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] Re: index of isisISAdjEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 18:11:11 -0700

Hi Jeff,

At Mon, 26 Aug 2002 20:19:50 -0400,
Jeff Parker wrote:
> 
> >     isisISAdjLevelIndex OBJECT-TYPE
> > 
> > > I think this is taken from a prior version.  
> 
> Again, this -is- from a prior version.  

	Oh, then that's in the prior to the -08 version.
	I'm new so I don't have drafts prior to the -08. :p

	Sorry for the duplicate discussion but this is needed for
	our implementation, and also yours.

> > But based on the current -09 draft,
> > 	we have a problem to express the adjacent neighbor in the
> > 	isisAdj*Entry.
> > 
> > 	Here is the current -09 version's isisAdjEntry which 
> > doesn't have level information in the index.
> > 
> >     isisISAdjEntry OBJECT-TYPE
> >         SYNTAX IsisISAdjEntry
> >         MAX-ACCESS not-accessible
> >         STATUS current
> >         DESCRIPTION
> >             "Each entry corresponds to one adjacency to an
> >              Intermediate System on this system."
> >         INDEX { isisSysInstance,
> >                 isisCircIndex,
> >                 isisISAdjIndex }
> >     ::= { isisISAdjTable 1 }
> > 
> > 
> > 								kay
> 
> I can well believe that we have a problem.  But can you
> tell me what the problem is?  What are you trying to
> do that you cannot do?  

	Okay, I can show you one example. 

	You have two IS L1/L2 routers(IS1, IS2) on the LAN and those two
	are L1L2 adjacent.

	We can assign isisISAdjIndex one for L1 adjacency and two for
	L2 adjacency and vice versa because there is no information for
	level in the isisAdjEntry indexes.

	Then if IS2's priority is set differently for L1 and L2, say
	63 and 64, then how do you know which one is for which level?

	You can get

titanium$ snmpget localhost hoge .1.3.6.1.3.37.1.5.1.1.8.1.1.1
37.1.5.1.1.8.1.1.1 = 63
titanium$ snmpget localhost hoge .1.3.6.1.3.37.1.5.1.1.8.1.1.2
37.1.5.1.1.8.1.1.2 = 64

	or 

titanium$ snmpget localhost hoge .1.3.6.1.3.37.1.5.1.1.8.1.1.1
37.1.5.1.1.8.1.1.1 = 64
titanium$ snmpget localhost hoge .1.3.6.1.3.37.1.5.1.1.8.1.1.2
37.1.5.1.1.8.1.1.2 = 63

	And there is no entry for the level information in the isisISAdjEntry
	ieself.

	isisISAdjNeighSysType and isisISAdjNeighUsage just returns "3",
	l1L2IntermediateSystem for isisISAdjNeighSysType and level1and2 for
	isisISAdjNeighUsage, in this case.

Thank you,

								kay

> This table treats a L1/L2 neighbor as two adjacencies
> (matching the spec) and a p2p neighbor as one.  As
> a result, we duplicate some information about SysId
> and SNPA.  
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:24:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27198
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:24:27 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HMJp12638;
	Thu, 5 Sep 2002 13:22:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7R21oo02096
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 22:01:50 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA28777
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 22:00:12 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17jVfZ-0001JL-00; Mon, 26 Aug 2002 19:01:25 -0700
Message-ID: <87y9athxfv.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: Jeff Parker <jparker@axiowave.com>
Cc: "'Noguchi Kay'" <kay@ipinfusion.com>, isis-wg@ietf.org
In-Reply-To: <EB5FFC72F183D411B38200062957342902A74118@r2d2.axiowave.com>
References: <EB5FFC72F183D411B38200062957342902A74118@r2d2.axiowave.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] Re: index of isisISAdjIPAddrEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 26 Aug 2002 19:01:24 -0700

Hi Jeff,

# I didn't read the old mail that pointed out the difficulties
# to use the IP address as an index, but...

> > 	My point is the consistency between those three.
> > 
> > 	- isisSummAddrEntry
> > 	- isisRedistributeEntry
> > 	- isisISAdjIPAddrEntry
> > 
> > 	The Upper two use *AddressType, *Address and 
> > *AddrPrefixlen as an index and the last one uses *IPAddrIndex.
> > 
> > > > 
> > > > And let's omit isisISAdjIPAddrIndex itself like below.
> 
> Kay -
> 	You have a good point.  In the first two tables, the
> index is an IP address.  In the third, an index was
> introduced to spare the user from having to deal with
> an IP address as an index.  

	I prefer to use IP address or area address for the index because
	those indexes are permanent for the configure/unconfigure event.

	It's a little bit hard to make the special index value, in this case,
	isisISAdjIPAddrIndex, permanent during the IP address add, delete and
	add event.

# I know it's depend on the generation and reception process for the
# IP Interface Address TLV but that's different topic.

> 	In the third table there are multiple indexes, 
> while in the first two the address is (almost) the only
> index.  I've had more than one request to avoid using
> addresses as indicies.  Using an IP address as an index
> seems more difficult to deal with with when there are many
> indicies.  

	Again I don't agree this point that the differencies between
	one to three another indexes, isisSummAddrEntry has one another
	index and isisISAdjIPaddrEntry has three other indexes.

# I've attached draft-ietf-isis-wg-mib-09.txt's isisSummAddrEntry and
# isisISAdjIPAddrEntry for reference.

> 	I will file your request away for the next version.
> 
> - jeff parker

	Okay, I prefer to use IP address as an index but I more prefer
	to the consistency between those three entries.

	So if you want to keep isisISAdjIPAddrIndex, then you can pick
	isisSummAddrIndex and isisRedistributeIndex as the index for
	other two entries, I don't like this though. ;P

	So please make a good decision.

Thank you,

								kay
    isisSummAddrEntry OBJECT-TYPE
        SYNTAX IsisSummAddrEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry contains one IP summary address."

        INDEX { isisSysInstance,
                isisSummAddressType,
                isisSummAddress,
                isisSummAddrPrefixLen }
    ::= { isisSummAddrTable 1 }

   isisISAdjIPAddrEntry OBJECT-TYPE
        SYNTAX IsisISAdjIPAddrEntry
        MAX-ACCESS not-accessible
        STATUS current
        DESCRIPTION
            "Each entry contains one IP Address reported by a
             neighboring Intermediate System in its IIH PDUs."
        INDEX { isisSysInstance,
                isisCircIndex,
                isisISAdjIndex,
                isisISAdjIPAddrIndex
                }
    ::= { isisISAdjIPAddrTable 1 }

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:25:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27315
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:25:56 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HOAp12790;
	Thu, 5 Sep 2002 13:24:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7SBx2o22969
	for <isis-wg@optimus.ietf.org>; Wed, 28 Aug 2002 07:59:02 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24985;
	Wed, 28 Aug 2002 07:57:29 -0400 (EDT)
Message-Id: <200208281157.HAA24985@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: isis-wg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-admin-tags-01.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 28 Aug 2002 07:57:29 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title		: A Policy Control Mechanism is IS-IS Using 
                          Administrative Tags
	Author(s)	: C. Martin, B. Neal, S. Previdi
	Filename	: draft-ietf-isis-admin-tags-01.txt
	Pages		: 6
	Date		: 2002-8-27
	
This document describes an extension to the IS-IS protocol to add
operational capabilities that allow for ease of management and
control over IP prefix distribution within an IS-IS domain.  The IS-
IS protocol is specified in [1], with extensions for supporting IPv4
specified in [2] and further enhancements for Traffic Engineering [4]
in [3] and [6].
This document enhances the IS-IS protocol by extending the
information that a Intermediate System (IS) [router] can place in
Link State Protocol Data Units (LSPs) as specified in [2].  This
extension will provide operators with a mechanism to control IP
prefix distribution throughout multi-level IS-IS domains.
Additionally, the information can be placed in LSPs that have TLVs as
yet undefined, if this information is used to convey the same meaning
in these future TLVs as it is used in the currently defined TLVs.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-admin-tags-01.txt

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-isis-admin-tags-01.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:28:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27425
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:28:14 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HQCp13038;
	Thu, 5 Sep 2002 13:26:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7RHZBo22468
	for <isis-wg@optimus.ietf.org>; Tue, 27 Aug 2002 13:35:11 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03202
	for <isis-wg@ietf.org>; Tue, 27 Aug 2002 13:33:38 -0400 (EDT)
Received: from net4u.ch (gw.xebeo.com [204.192.44.242])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g7RHYvG03319;
	Tue, 27 Aug 2002 19:34:57 +0200
Message-ID: <3D6BB2D0.40006@net4u.ch>
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Christian <philip.christian@iname.com>
CC: isis-wg@ietf.org
Subject: Re: [Isis-wg] new potential issue with Proprietary / Private TLV
    numbers?
References: <20020827122817.74388.qmail@iname.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 27 Aug 2002 10:11:44 -0700
Content-Transfer-Encoding: 7bit

Philip Christian wrote:

>Tony,
>
>I have been made redundant, got another job, and been on holiday...
>
Philip,

sorry but not surprised to hear that, industry been in better shape 
already. This too shall pass ...

>Anyway I'm back on duty now and so I'll have a go this week.
>
thanks ...

    -- tony


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:31:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27628
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:31:15 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HT5p13230;
	Thu, 5 Sep 2002 13:29:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7SHt3o12168
	for <isis-wg@optimus.ietf.org>; Wed, 28 Aug 2002 13:55:03 -0400
Received: from titanium (adsl-63-198-41-106.dsl.snfc21.pacbell.net [63.198.41.106])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11751
	for <isis-wg@ietf.org>; Wed, 28 Aug 2002 13:53:29 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17k71o-0002A4-00; Wed, 28 Aug 2002 10:54:52 -0700
Message-ID: <877kiaj2c4.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: Jeff Parker <jparker@axiowave.com>
Cc: "'Noguchi Kay'" <kay@ipinfusion.com>, isis-wg@ietf.org
In-Reply-To: <EB5FFC72F183D411B38200062957342902A7412A@r2d2.axiowave.com>
References: <EB5FFC72F183D411B38200062957342902A7412A@r2d2.axiowave.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] Re: index of isisISAdjEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 28 Aug 2002 10:54:51 -0700

Hi Jeff,

> Kay -
> 	The isisISAdjUsage should tell you what you need
> to know here: it would be 3 for a L1L2 p2p adjacency, 
> and 1 or 2 for L1 or L2 adjacencies on a LAN.

	Cool, thank you for your clarification.

> 	If the Description clause is unclear let's fix it.

	Then why don't you put "L1L2(3) is for p2p L1L2 adjacency only"
	clause like you said. That makes more clear to me that "3" is only
	for p2p, not for broadcast adjacency.
 
	As you can see, I thought we should use "3" for broadcast L1/L2
	adjacecy also and that made me confused and I thought we need
	isisISAdjLevelIndex.

Thank you,

								kay

> 	If the Description clause is unclear let's fix it.
> 
> - jeff parker
>  
>      isisISAdjUsage OBJECT-TYPE
>         SYNTAX INTEGER
>             {
>                 level1(1),
>                 level2(2),
>                 level1and2(3)
>             }
>         MAX-ACCESS read-only
>         STATUS current
>         DESCRIPTION
>             "An adjacency of type level1 is used for level 1
>              traffic only. An adjacency of type level2 is used
>              for level 2 traffic only. An adjacency of type level1and2
>              is used for both level 1 and level 2 traffic. There
>              may be two adjacencies (of types level1 and level2)
>              between the same pair of Intermediate Systems."
>         REFERENCE "{ISIS.aoi adjacencyUsage (82)}"
>     ::= { isisISAdjEntry 6 } 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:33:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27798
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:33:15 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HVAp13433;
	Thu, 5 Sep 2002 13:31:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7SHlLo11833
	for <isis-wg@optimus.ietf.org>; Wed, 28 Aug 2002 13:47:21 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11326
	for <isis-wg@ietf.org>; Wed, 28 Aug 2002 13:45:46 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A7412B@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Noguchi Kay'" <kay@ipinfusion.com>
Cc: isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: index of isisISAdjIPAddrEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 28 Aug 2002 13:46:30 -0400

> > > 	My point is the consistency between those three.
> > > 
> > > 	- isisSummAddrEntry
> > > 	- isisRedistributeEntry
> > > 	- isisISAdjIPAddrEntry
> >
> > Kay -
> > 	You have a good point.  In the first two tables, the
> > index is an IP address.  In the third, an index was
> > introduced to spare the user from having to deal with
> > an IP address as an index.  
> 
> 	I prefer to use IP address or area address for the index because
> 	those indexes are permanent for the configure/unconfigure event.
> 
> 	It's a little bit hard to make the special index value, 
>     in this case, isisISAdjIPAddrIndex, permanent during 
>     the IP address add, delete and add event.

Kay -
	Excellent point: thanks for bringing this up.

	However, does this apply to the case you bring
up, the isisISAdjIPAddrEntry?  This is the IP address
advertised by a neighbor.  We should not need to 
configure or unconfigure these items.  
 
> > 	In the third table there are multiple indexes, 
> > while in the first two the address is (almost) the only
> > index.  I've had more than one request to avoid using
> > addresses as indicies.  Using an IP address as an index
> > seems more difficult to deal with with when there are many
> > indicies.  
> 
> 	Again I don't agree this point that the differencies between
> 	one to three another indexes, isisSummAddrEntry has one another
> 	index and isisISAdjIPaddrEntry has three other indexes.

There is a system instance, but it has never been clear
to me how much this will vary.  It seems to provide 
for virtual routers, but within an implementation,
sysInstance may well be a virtual constant.  This 
is the only MIB I know with this variable, which 
suggests that it never caught on as a useful idea.  

To restate my point, the third table is different because
it has multiple non-trivial indicies, making a traverse
more onerous with a multi-part index such as an IP address.
 
> 	So if you want to keep isisISAdjIPAddrIndex, then you can pick
> 	isisSummAddrIndex and isisRedistributeIndex as the index for
> 	other two entries, I don't like this though. ;P
> 
> 	So please make a good decision.
 
I think Emerson said something about foolish 
consistency, but that probably just proves 
that he wasn't a programmer.

Any opinions from the list?  Is dealing with 
Addresses routine enough that we can drop the
index from isisISAdjIPAddrEntry?  Or difficult
enough that we should add it to the other two?
Or is the current version with both in place
reasonable.  

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:35:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA27921
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:35:03 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HXDp13619;
	Thu, 5 Sep 2002 13:33:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7SHhCo11620
	for <isis-wg@optimus.ietf.org>; Wed, 28 Aug 2002 13:43:12 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA11079
	for <isis-wg@ietf.org>; Wed, 28 Aug 2002 13:41:36 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A7412A@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Noguchi Kay'" <kay@ipinfusion.com>, Jeff Parker <jparker@axiowave.com>
Cc: isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: index of isisISAdjEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 28 Aug 2002 13:42:19 -0400

 
> > >     isisISAdjEntry OBJECT-TYPE
> > >         SYNTAX IsisISAdjEntry
> > >         MAX-ACCESS not-accessible
> > >         STATUS current
> > >         DESCRIPTION
> > >             "Each entry corresponds to one adjacency to an
> > >              Intermediate System on this system."
> > >         INDEX { isisSysInstance,
> > >                 isisCircIndex,
> > >                 isisISAdjIndex }
> > >     ::= { isisISAdjTable 1 }
> 
> 	You have two IS L1/L2 routers(IS1, IS2) on the LAN and those two
> 	are L1L2 adjacent.
> 
> 	We can assign isisISAdjIndex one for L1 adjacency and two for
> 	L2 adjacency and vice versa because there is no information for
> 	level in the isisAdjEntry indexes.
> 
> 	Then if IS2's priority is set differently for L1 and L2, say
> 	63 and 64, then how do you know which one is for which level?
> 
> 	And there is no entry for the level information in the 
>     isisISAdjEntry ieself.
> 
> 	isisISAdjNeighSysType and isisISAdjNeighUsage just returns "3",
> 	l1L2IntermediateSystem for isisISAdjNeighSysType and 
>     level1and2 for isisISAdjNeighUsage, in this case.
> 
> Thank you,
> 
> 								kay

Kay -
	The isisISAdjUsage should tell you what you need
to know here: it would be 3 for a L1L2 p2p adjacency, 
and 1 or 2 for L1 or L2 adjacencies on a LAN.

	If the Description clause is unclear let's fix it.

- jeff parker
 
     isisISAdjUsage OBJECT-TYPE
        SYNTAX INTEGER
            {
                level1(1),
                level2(2),
                level1and2(3)
            }
        MAX-ACCESS read-only
        STATUS current
        DESCRIPTION
            "An adjacency of type level1 is used for level 1
             traffic only. An adjacency of type level2 is used
             for level 2 traffic only. An adjacency of type level1and2
             is used for both level 1 and level 2 traffic. There
             may be two adjacencies (of types level1 and level2)
             between the same pair of Intermediate Systems."
        REFERENCE "{ISIS.aoi adjacencyUsage (82)}"
    ::= { isisISAdjEntry 6 } 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:37:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28069
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:37:04 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HZDp13806;
	Thu, 5 Sep 2002 13:35:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7SI9ao13250
	for <isis-wg@optimus.ietf.org>; Wed, 28 Aug 2002 14:09:36 -0400
Received: from titanium (adsl-63-198-41-106.dsl.snfc21.pacbell.net [63.198.41.106])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12313
	for <isis-wg@ietf.org>; Wed, 28 Aug 2002 14:08:01 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17k7Ft-0002AF-00; Wed, 28 Aug 2002 11:09:25 -0700
Message-ID: <8765xuj1of.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: Jeff Parker <jparker@axiowave.com>
Cc: "'Noguchi Kay'" <kay@ipinfusion.com>, isis-wg@ietf.org, tli@procket.com,
        prz@xebeo.com
In-Reply-To: <EB5FFC72F183D411B38200062957342902A7412B@r2d2.axiowave.com>
References: <EB5FFC72F183D411B38200062957342902A7412B@r2d2.axiowave.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] Re: index of isisISAdjIPAddrEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 28 Aug 2002 11:09:04 -0700

Hi Jeff, Tony and Tony,

# I added the working group chairs, Tony and Tony, to report ml problem.

At Wed, 28 Aug 2002 13:46:30 -0400,
Jeff Parker wrote:
> 
> Any opinions from the list?  Is dealing with 
> Addresses routine enough that we can drop the
> index from isisISAdjIPAddrEntry?  Or difficult
> enough that we should add it to the other two?
> Or is the current version with both in place
> reasonable.  

	Yes, I want to know other guys opinions and, of course, I vote
	for the change of isisISAdjIPAddrIndex to isisISAdjIPAddress.

	But right now, we have a problem with isis-wg@ietf.org mailing list
	so nobody except me and Jeff receives this discussions.

	Tony, could you check and fix the isis-wg@ietf.org mailing list
	configuration? As I reported before to Tony Przygienda, my
	MTA, exim, claims no errors in the transactions show below.

2002-08-28 10:54:52 17k71o-0002A4-00 <= kay@ipinfusion.com H=titanium (titanium.
ipinfusion.com) [127.0.0.1] P=esmtp S=2186 id=877kiaj2c4.wl@ipinfusion.com
2002-08-28 10:54:58 17k71o-0002A4-00 => jparker@axiowave.com R=lookuphost T=remo
te_smtp H=mail.axiowave.com [64.115.125.242]
2002-08-28 10:54:58 17k71o-0002A4-00 => kay@ipinfusion.com R=lookuphost T=remote
_smtp H=mail.ipinfusion.com [65.223.109.2]
2002-08-28 10:55:00 17k71o-0002A4-00 => isis-wg@ietf.org R=lookuphost T=remote_s
mtp H=odin.ietf.org [132.151.1.176]
2002-08-28 10:55:00 17k71o-0002A4-00 Completed

	And we can't see any discussion after Aug. 04 in the archive. 

http://www1.ietf.org/mail-archive/working-groups/isis-wg/current/threads.html

Thank you,

> - jeff parker
> - axiowave networks
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:38:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28224
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:38:56 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Hb2p13971;
	Thu, 5 Sep 2002 13:37:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7T9tmo02233
	for <isis-wg@optimus.ietf.org>; Thu, 29 Aug 2002 05:55:48 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14353
	for <isis-wg@ietf.org>; Thu, 29 Aug 2002 05:54:17 -0400 (EDT)
Received: from mshand-w2k.cisco.com (lon-sto4-lan-vlan133-dhcp14.cisco.com [144.254.108.81])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA24507;
	Thu, 29 Aug 2002 10:55:05 +0100 (BST)
Message-Id: <4.3.2.7.2.20020829104400.04229cd0@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: May Lu <mlu@chiaro.com>
From: mike shand <mshand@cisco.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
In-Reply-To: <F69EB380D594D611BBEA00065B3F14B403297B@MAIL>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Isis-wg] Re: Questions about "restart signaling for ISIS"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 29 Aug 2002 10:55:03 +0100

At 15:26 26/08/2002 -0500, May Lu wrote:
>Hi Mike,
>
>I have some questions about draft-ietf-isis-restart-01.txt (May 2002)
>version.
>
>1. Can the restarting router changes its extended local circuit id during
>restart?
>The extended local circuit id is included in the "Point-to-Point Adjacency
>State" TLV. If the restarting router sends an IIH with RR bit set but with a
>different circuit id, should the receiving routers drop the IIH or accept
>the IIH and update the adjacency information to store the new neighbor
>extended circuit id?

Accept it. See 4.2 b)
which says
..... having updated the "point-to-point Advacency State" option to reflect 
any new values received from the re-starting router






>2. Based on the draft, on LAN circuit, the receiving router with the highest
>LnRouterPriority (with highest source MAC address breaking ties) among those
>routers supporting the graceful restart, initiate the CSNPs/LSPs
>transmission when a restarting router asks for help. If the receiving router
>with highest priority goes offline when an IIH with RR bit set arrives,
>should another router initiates the CSNPs/LSPs transmission or the
>restarting router gets t1 expiry on this interface and fails the graceful
>restart?

Hmmm. I'm not quite sure what you mean here. At the time the RR is 
received, the highest priority router responds. Are you suggesting that the 
other routers should monitor what it does, and if it doesn't respond they 
should assume it is dead and the NEXT highest router should take over?

That sounds overly complex. If there is no response from the highest 
priority router, then things are probably broken anyway. I don't think 
there is any need to handle this as a special case.

>Thanks,
>Xiaomei
>
>
>
>
>
>
>----------------------------------------- (on rchss001)
>
>This e-mail and any files transmitted with it are the property
>of Chiaro Networks, Ltd., and may contain confidential and
>privileged material for the sole use of the intended recipient(s)
>to whom this e-mail is addressed. If you are not one of the named
>recipient(s), or otherwise have reason to believe that you have
>received this message in error, please notify the sender and
>delete all copies from your system.  Any other use, retention,
>dissemination, forwarding, printing or copying of this e-mail is
>strictly prohibited.
>
>
>---------------------------------------------------------

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:41:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28370
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:41:04 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Hd5p14125;
	Thu, 5 Sep 2002 13:39:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7TBkIo07315
	for <isis-wg@optimus.ietf.org>; Thu, 29 Aug 2002 07:46:18 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16695;
	Thu, 29 Aug 2002 07:44:42 -0400 (EDT)
Message-Id: <200208291144.HAA16695@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: isis-wg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-ext-lsp-frags-02.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 29 Aug 2002 07:44:41 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title		: Extending the Number of IS-IS LSP Fragments Beyond the
                          256 Limit
	Author(s)	: A. Hermelin, S. Previdi, M. Shand
	Filename	: draft-ietf-isis-ext-lsp-frags-02.txt
	Pages		: 13
	Date		: 2002-8-28
	
This document describes a mechanism that allows a system to originate
more than 256 LSP fragments, a limit set by the original Intermediate
System to Intermediate System (IS-IS) Routing protocol, as described
in ISO 10589.  This mechanism can be used in IP-only, OSI-only, and
dual routers.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-ext-lsp-frags-02.txt

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-isis-ext-lsp-frags-02.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-isis-ext-lsp-frags-02.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:43:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28540
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:43:05 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Hf9p14353;
	Thu, 5 Sep 2002 13:41:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7TBkJo07320
	for <isis-wg@optimus.ietf.org>; Thu, 29 Aug 2002 07:46:19 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16712;
	Thu, 29 Aug 2002 07:44:46 -0400 (EDT)
Message-Id: <200208291144.HAA16712@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: isis-wg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-gmpls-extensions-14.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 29 Aug 2002 07:44:46 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title		: IS-IS Extensions in Support of Generalized MPLS
	Author(s)	: K. Kompella, Y. Rekhter
	Filename	: draft-ietf-isis-gmpls-extensions-14.txt
	Pages		: 12
	Date		: 2002-8-28
	
This document specifies encoding of extensions to the IS-IS routing
protocol in support of Generalized Multi-Protocol Label Switching.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-gmpls-extensions-14.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-14.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-14.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:	<2002-8-28160347.I-D@ietf.org>

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

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

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

--OtherAccess--

--NextPart--


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:45:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28654
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:45:18 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HhBp14501;
	Thu, 5 Sep 2002 13:43:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83HXuo07865
	for <isis-wg@optimus.ietf.org>; Tue, 3 Sep 2002 13:33:56 -0400
Received: from spyserver.y-w-s.de (server20.yourwebstart.com [81.2.136.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06139
	for <isis-wg@ietf.org>; Tue, 3 Sep 2002 13:32:17 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=spyserver.yourwebstart.com)
	by spyserver.y-w-s.de with esmtp (Exim 3.35 #1 (Debian))
	id 17mHZB-0007Fs-00; Tue, 03 Sep 2002 11:34:17 -0600
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
From: Saravana Kumar <sarav_k@spymac.com>
To: isis-wg@ietf.org
Reply-To: sarav_k@spymac.com
Content-Type: text/plain
X-Mailer: AtMail Corp 3.4 - http://webbasedemail.com/
X-Uidl: 1031074456150941726
X-Origin: 210.210.49.40
Message-Id: <E17mHZB-0007Fs-00@spyserver.y-w-s.de>
Content-Transfer-Encoding: binary
Subject: [Isis-wg] up/down bit question..
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 03 Sep 2002 11:34:17 -0600
Content-Transfer-Encoding: binary

Hi Everyone,

I have a little doubt on the section about the up/down bit in the 
ISIS IPV6 draft, which goes like this..

  "As is described in [2], "the up/down bit is set to 0 when a 
   prefix is first injected into IS-IS.  If a prefix is 
   redistributed from a higher level to a lower level (e.g., 
   level two to level one), the bit shall be set to 1 to indicate
   that the prefix has travelled down the hierarchy.  If a prefix
   is redistributed from an area to another area at the same level
   then the up/down bit shall be set to 1."

I can understand the first two cases, but i cant put my finger on the
third. In which cases do we re-distribute from one area to another 
area 'at the same level' ?

If we re-distribute the routes from one area 'A' into another area 'B',
my guess is that it will be done by the L1L2 router in area 'B',which
would actually do a selective L2->L1 prefix distribution ( i.e 
distributing all the prefixes that it learns from the L2 LSP's coming 
from area 'A') This is again a case of redistributing routes from a 
higher level to a lower level. When do we redistribute from an area to
another area at the same level ?

Thanks,
Sarav


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:48:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28781
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:48:00 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Hk3p14774;
	Thu, 5 Sep 2002 13:46:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7UIepo16057
	for <isis-wg@optimus.ietf.org>; Fri, 30 Aug 2002 14:40:51 -0400
Received: from nwkea-mail-1.sun.com (nwkea-mail-1.sun.com [192.18.42.13])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00192
	for <isis-wg@ietf.org>; Fri, 30 Aug 2002 14:39:13 -0400 (EDT)
Received: from sydney.East.Sun.COM ([129.148.9.16])
	by nwkea-mail-1.sun.com (8.9.3+Sun/8.9.3) with ESMTP id LAA17470
	for <isis-wg@ietf.org>; Fri, 30 Aug 2002 11:40:15 -0700 (PDT)
Received: from sr1-ubur-01 (sr1-ubur-01 [129.148.9.80])
	by sydney.East.Sun.COM (8.11.6+Sun/8.11.6/ENSMAIL,v2.2) with SMTP id g7UIeEL16556
	for <isis-wg@ietf.org>; Fri, 30 Aug 2002 14:40:14 -0400 (EDT)
Message-Id: <200208301840.g7UIeEL16556@sydney.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>
To: isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: F8w0C0WdXC3J2Lv38U5d6w==
X-Mailer: dtmail 1.3.0 @(#)CDE Version 1.4.6_06 SunOS 5.8 sun4u sparc 
Subject: [Isis-wg] What is the largest MTU we can assume that won't get fragmented?
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 30 Aug 2002 14:40:14 -0400 (EDT)

I vaguely remember in the dark ages it was 576, not necessarily because
of link technology that required <576, but because of not wanting to
require routers to have such large buffers perhaps?

And I vaguely remember that more recently than the dark ages, people decided
that all links can handle at least 1500, minus fudge factors for various
headers (802.3, then VLANs, etc.)

Anyway, I thought IS-IS had LSP fragments of 1500 because it was assumed
that would be safely carried on all links. (Do I remember correctly?).

And if I remember correctly, can we assume 1500 for data as well?

Thanks,

Radia

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:50:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA28965
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:50:05 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Hm6p14889;
	Thu, 5 Sep 2002 13:48:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84Av6o11905
	for <isis-wg@optimus.ietf.org>; Wed, 4 Sep 2002 06:57:06 -0400
Received: from xover.netplane.com (fwout.maker.com [12.27.183.253] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22203
	for <isis-wg@ietf.org>; Wed, 4 Sep 2002 06:55:30 -0400 (EDT)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0AQ2V>; Wed, 4 Sep 2002 06:56:34 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328791541@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] Paper comparing OSPF and ISIS
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 4 Sep 2002 06:58:56 -0400

Hi folks,

The topic of differences between OSPF and ISIS has been raised more than
once. The topic has been covered in a few presentations before as well as a
lot of internal documents. It would however be helpful to "compare both
specs and put down the differences and pros and cons of the differences" for
the benefit of people.

I intend to make a group of people who would be interested in the effort. So
anyone willing to help can mail me and I will add them to the group, from
where we can take this further on.

I do have a preliminary list of things to start off.

Thanks,
Vishwas

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:51:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29107
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:51:59 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Ho9p15029;
	Thu, 5 Sep 2002 13:50:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g83F8Mo17368
	for <isis-wg@optimus.ietf.org>; Tue, 3 Sep 2002 11:08:22 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00037
	for <isis-wg@ietf.org>; Tue, 3 Sep 2002 11:06:42 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A7419C@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "ISIS-WG (E-mail)" <isis-wg@ietf.org>
Cc: "'zinin@psg.com'" <zinin@psg.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] Updates to "Interoperability" draft
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 3 Sep 2002 11:07:41 -0400

In a judgment worthy of Solomon, our ADs have suggested that the best way to
move the draft-ietf-isis-interoperable document forward is to cut it in two:
one part that deals with the features described in ISO 10589, and one that
deal with the features described in RFC 1195.  We can then make the ISO half
informational, and the IP half normative.  

After looking at the contents, this seems quite possible.  With the
exception of the a few items (such as the impact of L2 to L1 leaking on the
meaning of the S bit in the Default Metric), the document splits cleanly
into the two halves.   I will be circulating the new documents for review on
the original mailing list formed for the document, but would be happy to
share the current state with any interested party on the full ISIS WG list.


- jeff parker
- axiowave networks
 

 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:54:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29221
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:54:03 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HqCp15173;
	Thu, 5 Sep 2002 13:52:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84Ip9o09060
	for <isis-wg@optimus.ietf.org>; Wed, 4 Sep 2002 14:51:09 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15555
	for <isis-wg@ietf.org>; Wed, 4 Sep 2002 14:49:28 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17mfEM-0000DR-00; Wed, 04 Sep 2002 11:50:22 -0700
Message-ID: <87heh5y4h7.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: Tony Przygienda <prz@xebeo.com>
Cc: Noguchi Kay <kay@ipinfusion.com>, Jeff Parker <jparker@axiowave.com>,
        isis-wg@ietf.org, tli@procket.com, Alex Zinin <zinin@psg.com>
In-Reply-To: <3D6D1783.2030305@xebeo.com>
References: <EB5FFC72F183D411B38200062957342902A7412B@r2d2.axiowave.com>
	<8765xuj1of.wl@ipinfusion.com>
	<3D6D1783.2030305@xebeo.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] Re: index of isisISAdjIPAddrEntry
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 04 Sep 2002 11:49:56 -0700

Hi Tony,

> >	Tony, could you check and fix the isis-wg@ietf.org mailing list
> >	configuration? As I reported before to Tony Przygienda, my
> >	MTA, exim, claims no errors in the transactions show below.
> >
> We're at it

	Was that fixed already?
	I didn't see any update in the mailing list archive, though.

https://www1.ietf.org/mail-archive/working-groups/isis-wg/current/maillist.html

Thank you,

								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:56:04 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29347
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:56:04 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HsFp15352;
	Thu, 5 Sep 2002 13:54:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84Bwpo14972
	for <isis-wg@optimus.ietf.org>; Wed, 4 Sep 2002 07:58:51 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA23553;
	Wed, 4 Sep 2002 07:57:07 -0400 (EDT)
Message-Id: <200209041157.HAA23553@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: isis-wg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-proprietary-tlv-00.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 04 Sep 2002 07:57:06 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title		: TLV for Proprietary Use
	Author(s)	: P. Christian
	Filename	: draft-ietf-isis-proprietary-tlv-00.txt
	Pages		: 5
	Date		: 2002-9-3
	
This document defines a TLV that may be used by any individual, 
company or other organisation for vendor specific or experimental 
extensions to the IS-IS routing protocol, and defines the format of 
the TLV.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-proprietary-tlv-00.txt

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-isis-proprietary-tlv-00.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 13:58:06 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29497
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 13:58:06 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HuKp15512;
	Thu, 5 Sep 2002 13:56:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g84D2go19059
	for <isis-wg@optimus.ietf.org>; Wed, 4 Sep 2002 09:02:42 -0400
Received: from ws1-6.us4.outblaze.com (205-158-62-53.outblaze.com [205.158.62.53])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA26317
	for <isis-wg@ietf.org>; Wed, 4 Sep 2002 09:01:03 -0400 (EDT)
Received: (qmail 37261 invoked by uid 1001); 4 Sep 2002 13:01:54 -0000
Message-ID: <20020904130154.37260.qmail@iname.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-6.us4.outblaze.com with http for
    philip.christian@iname.com; Wed, 04 Sep 2002 13:01:54 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: isis-wg@ietf.org
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-6.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] Proprietary TLV draft
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 04 Sep 2002 13:01:54 +0000
Content-Transfer-Encoding: 7bit

draft-ietf-isis-proprietary-tlv-00.txt is now on the server at http://www.ietf.org/internet-drafts/draft-ietf-isis-proprietary-tlv-00.txt

I have already noticed a typo in the last sentence on page two (replace "should" with "shown").

Any other comments gladly received.

Thanks, Philip


-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 14:04:40 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29899
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 14:04:40 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85I2Op16137;
	Thu, 5 Sep 2002 14:02:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7RG1Io17527
	for <isis-wg@optimus.ietf.org>; Tue, 27 Aug 2002 12:01:18 -0400
Received: from ws1-10.us4.outblaze.com (205-158-62-111.outblaze.com [205.158.62.111])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA29319
	for <isis-wg@ietf.org>; Tue, 27 Aug 2002 11:59:46 -0400 (EDT)
Received: (qmail 74389 invoked by uid 1001); 27 Aug 2002 12:28:17 -0000
Message-ID: <20020827122817.74388.qmail@iname.com>
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-10.us4.outblaze.com with http for
    philip.christian@iname.com; Tue, 27 Aug 2002 07:28:17 -0500
From: "Philip Christian" <philip.christian@iname.com>
To: prz@net4u.ch
Cc: isis-wg@ietf.org
Subject: Re: [Isis-wg] new potential issue with Proprietary / Private TLV
    numbers?
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-10.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 27 Aug 2002 07:28:17 -0500
Content-Transfer-Encoding: 7bit

Tony,

I have been made redundant, got another job, and been on holiday...
Anyway I'm back on duty now and so I'll have a go this week.

Thanks, Philip

> 
> So given this addition, are the authors of the draft (Philip) ready to 
> submit it. I think
> it would be usefull in couple of respects ...
> 
>     --- tony
> 
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> 

-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 14:20:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00635
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 14:20:37 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IJBp17876;
	Thu, 5 Sep 2002 14:19:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85I99p16950
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 14:09:09 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA29994
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 14:07:28 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA07207;
	Thu, 5 Sep 2002 14:08:31 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id OAA08270;
	Thu, 5 Sep 2002 14:08:32 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <R68QMX6Q>; Thu, 5 Sep 2002 14:08:31 -0400
Message-ID: <313680C9A886D511A06000204840E1CF529D0C@whq-msgusr-02.pit.comms.marconi.com>
From: "Harwani, Sanjay" <Sanjay.Harwani@marconi.com>
To: "'Mihir Shah'" <mshah@avici.com>, isis-wg@ietf.org
Subject: RE: [Isis-wg] Question about router id
Date: Thu, 5 Sep 2002 14:08:31 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

Hi All,

Thanks for the response. Following up on the same, 
what if isis doesn't gets the router id tlv from its neighbour ?
does it means that although the link to this neighbout is te capable,
if this neighbor doesn't sends a router id then we cannot use it to create
tunnels ?

What is ISIS supposed to do if its own router id changes. ?
Ospf depends upon the router id, hence if the router id of the router
changes
then I believe Ospf toggles its state. 

Thanks
Sanjay

-----Original Message-----
From: Mihir Shah [mailto:mshah@avici.com]
Sent: Thursday, September 05, 2002 2:03 PM
To: Harwani, Sanjay; isis-wg@ietf.org
Subject: Re: [Isis-wg] Question about router id


Sanjay,
Router ID TLV was introduced in isis-te extensions draft to carry router id
information. Refer to section 6.0 of draft-ietf-isis-traffic-04.txt.
Mihir.

----- Original Message -----
From: "Harwani, Sanjay" <Sanjay.Harwani@marconi.com>
To: <isis-wg@ietf.org>
Sent: Wednesday, August 21, 2002 10:46 AM
Subject: [Isis-wg] Question about router id


> Hi All,
>
> I would like to know how IS-IS should handle (convey) router_address
> which is an important piece of information for creating tunnels.
>
> Is there a mechanism defined to carry this information?
>
> Thanks
> Sanjay
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
>
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 14:43:30 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01984
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 14:43:30 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Ifkp20637;
	Thu, 5 Sep 2002 14:41:46 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85HJIp12352
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 13:19:18 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA26845
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 13:17:36 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A741EB@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Harwani, Sanjay'" <Sanjay.Harwani@marconi.com>, isis-wg@ietf.org
Subject: RE: [Isis-wg] Question about router id
Date: Thu, 5 Sep 2002 13:18:35 -0400 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

> Hi All,
> 
> I would like to know how IS-IS should handle (convey) router_address
> which is an important piece of information for creating tunnels.
> 
> Is there a mechanism defined to carry this information?
> 
> Thanks
> Sanjay

Looks like the list is back in action.  

   "The Traffic Engineering router ID TLV is TLV type 134."
   <draft-ietf-isis-traffic-04.txt>

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 14:48:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02359
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 14:48:43 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IlFp21556;
	Thu, 5 Sep 2002 14:47:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85IZBp19547
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 14:35:11 -0400
Received: from tahoe.sj.allegronetworks.com (tahoe.allegronetworks.com [63.115.58.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01418
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 14:33:31 -0400 (EDT)
Received: by tahoe.allegronetworks.com with Internet Mail Service (5.5.2653.19)
	id <SHRJFV6C>; Thu, 5 Sep 2002 11:34:32 -0700
Message-ID: <B4DFCB7CDE2DD4118F690008C786941604D78460@tahoe.allegronetworks.com>
From: Chris Hopps <chopps@allegronetworks.com>
To: "'sarav_k@spymac.com'" <sarav_k@spymac.com>
Cc: isis-wg@ietf.org
Subject: RE: [Isis-wg] up/down bit question..
Date: Thu, 5 Sep 2002 11:34:31 -0700 
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@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

Perhaps I didn't quote enough from [2] :)

If you look at the referenced document you'll find:

   "If a prefix is advertised from an area to another area at the same
   level, then the up/down bit shall be set to 1. This situation can
   arise when a router implements multiple virtual routers at the same
   level, but in different areas."

Chris.

-----Original Message-----
From: Saravana Kumar [mailto:sarav_k@spymac.com]
Sent: Tuesday, September 03, 2002 10:34 AM
To: isis-wg@ietf.org
Subject: [Isis-wg] up/down bit question..


Hi Everyone,

I have a little doubt on the section about the up/down bit in the 
ISIS IPV6 draft, which goes like this..

  "As is described in [2], "the up/down bit is set to 0 when a 
   prefix is first injected into IS-IS.  If a prefix is 
   redistributed from a higher level to a lower level (e.g., 
   level two to level one), the bit shall be set to 1 to indicate
   that the prefix has travelled down the hierarchy.  If a prefix
   is redistributed from an area to another area at the same level
   then the up/down bit shall be set to 1."

I can understand the first two cases, but i cant put my finger on the
third. In which cases do we re-distribute from one area to another 
area 'at the same level' ?

If we re-distribute the routes from one area 'A' into another area 'B',
my guess is that it will be done by the L1L2 router in area 'B',which
would actually do a selective L2->L1 prefix distribution ( i.e 
distributing all the prefixes that it learns from the L2 LSP's coming 
from area 'A') This is again a case of redistributing routes from a 
higher level to a lower level. When do we redistribute from an area to
another area at the same level ?

Thanks,
Sarav


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 14:56:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02869
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 14:56:08 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Isop23040;
	Thu, 5 Sep 2002 14:54:50 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Hw3p15687
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 13:58:03 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29377
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 13:56:23 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A741F0@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Radia Perlman - Boston Center for Networking'" <Radia.Perlman@sun.com>,
        isis-wg@ietf.org
Subject: RE: [Isis-wg] What is the largest MTU we can assume that won't ge
	t fragmented?
Date: Thu, 5 Sep 2002 13:57:14 -0400 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

 
> Anyway, I thought IS-IS had LSP fragments of 1500 because it 
> was assumed that would be safely carried on all links. 
> (Do I remember correctly?).
> 
> Radia

Radia -
	When we were doing the standards archeology for the
interoperability draft, someone (mike shand?) pointed out
that while 1492 was an upper bound, there were provisions
to -lower- that MTU in a network, using the management 
parameters originatingL1LSPBufferSize and 
originatingL2LSPBufferSize.  The details of how that would
work in practice are in the draft.  

	So you didn't make that assumption.

- jeff parker   
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep  5 14:58:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02981
	for <isis-archive@lists.ietf.org>; Thu, 5 Sep 2002 14:58:17 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Iv0p23362;
	Thu, 5 Sep 2002 14:57:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Hxtp15847
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 13:59:55 -0400
Received: from mlsrv1.avici.com (host128.avici.com [208.246.215.128] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29517
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 13:58:15 -0400 (EDT)
Received: from mshahpc2 (mshah-pc2.avici.com [10.2.20.54])
	by mlsrv1.avici.com (8.11.0/8.11.0) with SMTP id g85HxD710668;
	Thu, 5 Sep 2002 13:59:13 -0400 (EDT)
Message-ID: <020501c25506$793f9510$3614020a@avici.com>
From: "Mihir Shah" <mshah@avici.com>
To: "Harwani, Sanjay" <Sanjay.Harwani@marconi.com>, <isis-wg@ietf.org>
References: <313680C9A886D511A06000204840E1CF529CD2@whq-msgusr-02.pit.comms.marconi.com>
Subject: Re: [Isis-wg] Question about router id
Date: Thu, 5 Sep 2002 14:03:00 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Sanjay,
Router ID TLV was introduced in isis-te extensions draft to carry router id
information. Refer to section 6.0 of draft-ietf-isis-traffic-04.txt.
Mihir.

----- Original Message -----
From: "Harwani, Sanjay" <Sanjay.Harwani@marconi.com>
To: <isis-wg@ietf.org>
Sent: Wednesday, August 21, 2002 10:46 AM
Subject: [Isis-wg] Question about router id


> Hi All,
>
> I would like to know how IS-IS should handle (convey) router_address
> which is an important piece of information for creating tunnels.
>
> Is there a mechanism defined to carry this information?
>
> Thanks
> Sanjay
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
>

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 11:21:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06733
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 11:21:00 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FHgX13203;
	Fri, 6 Sep 2002 11:17:43 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85M2Pt01773
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 18:02:25 -0400
Received: from psg.com (smmsp@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09349
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 18:00:41 -0400 (EDT)
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 17n4hd-000GNM-00
	for isis-wg@ietf.org; Thu, 05 Sep 2002 15:02:18 -0700
Date: Fri, 6 Sep 2002 00:00:34 +0200
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <1222569122.20020906000034@psg.com>
To: isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] List problems
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Folks-

 Apologies for the problems with the mailing list,
 they were caused by some bugs during the massive
 list migration on the ietf.org server. The issue has
 been solved and we should be ok now. Thanks for
 understanding.
 
-- 
Alex


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 11:30:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07333
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 11:30:39 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FPOX14065;
	Fri, 6 Sep 2002 11:25:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85J6Dp24813
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 15:06:13 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03259
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 15:04:32 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g85J5aot016429;
	Thu, 5 Sep 2002 15:05:44 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-146.cisco.com [64.102.83.146])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id ACH77303;
	Thu, 5 Sep 2002 15:05:19 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020905142006.09221360@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Thu, 05 Sep 2002 15:05:01 -0400
To: Radia Perlman - Boston Center for Networking <Radia.Perlman@sun.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] What is the largest MTU we can assume that won't
  get fragmented?
Cc: isis-wg@ietf.org
In-Reply-To: <200208301840.g7UIeEL16556@sydney.East.Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>


WAY back in the dark ages, 512 bytes (layer 3) was a minimum, because
that's the minimum "max LSDU size" required by CLNP specs.  576 rings
a faint bell, but I'm not sure why or what the extra 64 would be about.

Support for mixed MTU sizes was never handled properly by ISIS, and
that's discussed in the interop draft.

But unfortunately (IMHO) Bellcore in GR-253-CORE mandated 512
(or was it 576?) as the default LSDU size for SONET SDCC, where
CLNP & ISIS are used to provide an embedded management channel.
(SDCC, or Section Data Communications Channel, is a 192 kbit/s
channel in the SONET frame overhead.)  This was deployed and
used in some telco SP's networks, and is probably still in use
and needs to be supported.

To complicate matters, the SONET community is working towards specs
to allow IP-based management communications on these same channels,
using IS-IS.  I don't know whether the default max LSDU size was
raised to 1500 as a part of this effort, but I suspect not.

Not important for mainstream IP, but something to keep in mind.

Regards,
Jeff

At 02:40 PM 8/30/2002, Radia Perlman - Boston Center for Networking wrote:
>I vaguely remember in the dark ages it was 576, not necessarily because
>of link technology that required <576, but because of not wanting to
>require routers to have such large buffers perhaps?
>
>And I vaguely remember that more recently than the dark ages, people decided
>that all links can handle at least 1500, minus fudge factors for various
>headers (802.3, then VLANs, etc.)
>
>Anyway, I thought IS-IS had LSP fragments of 1500 because it was assumed
>that would be safely carried on all links. (Do I remember correctly?).
>
>And if I remember correctly, can we assume 1500 for data as well?
>
>Thanks,
>
>Radia
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 11:35:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07664
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 11:35:44 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FRTX14223;
	Fri, 6 Sep 2002 11:27:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85J7up24980
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 15:07:56 -0400
Received: from spyserver.y-w-s.de (server20.yourwebstart.com [81.2.136.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03345
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 15:06:15 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=spyserver.yourwebstart.com)
	by spyserver.y-w-s.de with esmtp (Exim 3.35 #1 (Debian))
	id 17n1zG-0000yH-00; Thu, 05 Sep 2002 13:08:18 -0600
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
From: Saravana Kumar <sarav_k@spymac.com>
To: isis-wg@ietf.org, Chris Hopps <chopps@allegronetworks.com>
Subject: RE: [Isis-wg] up/down bit question..
Reply-To: sarav_k@spymac.com
Content-Type: text/plain
X-Mailer: AtMail Corp 3.4 - http://webbasedemail.com/
X-Uidl: 1031250976820
X-Origin: 210.210.51.28
Message-Id: <E17n1zG-0000yH-00@spyserver.y-w-s.de>
Date: Thu, 05 Sep 2002 13:08:18 -0600
Content-Transfer-Encoding: binary
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: binary



On Thu, 5 Sep 2002 11:34 , Chris Hopps <chopps@allegronetworks.com> sent:

>Perhaps I didn't quote enough from [2] :)
>
>If you look at the referenced document you'll find:
>
>   "If a prefix is advertised from an area to another area at the same
>   level, then the up/down bit shall be set to 1. This situation can
>   arise when a router implements multiple virtual routers at the same
>   level, but in different areas."

Ah well.. that makes sense !! Thanks Chris..
Sarav

>Chris.
>

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 11:37:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07801
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 11:37:57 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FTZX14496;
	Fri, 6 Sep 2002 11:29:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85JHQt25876
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 15:17:26 -0400
Received: from rchss001.chiaro.com (rchss001.chiaro.com [63.88.196.81])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA03658
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 15:15:44 -0400 (EDT)
Received: (qmail 8335 invoked from network); 5 Sep 2002 19:08:10 -0000
Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81)
  by rchss001.chiaro.com with SMTP; 5 Sep 2002 19:08:10 -0000
Received: by MAIL with Internet Mail Service (5.5.2653.19)
	id <R65HFAP2>; Thu, 5 Sep 2002 14:16:30 -0500
Message-ID: <F69EB380D594D611BBEA00065B3F14B43FF43D@MAIL>
From: Laura Liu <lliu@chiaro.com>
To: Noguchi Kay <kay@ipinfusion.com>, Jeff Parker <jparker@axiowave.com>
Cc: isis-wg@ietf.org, tli@procket.com, prz@xebeo.com
Subject: RE: [Isis-wg] Re: index of isisISAdjIPAddrEntry
Date: Thu, 5 Sep 2002 14:16:29 -0500 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

--=_IS_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"

I agree with Kay on "use IP address or area address for the index because
those indexes are permanent for the configure/unconfigure event". 

Laura

-----Original Message-----
From: Noguchi Kay [mailto:kay@ipinfusion.com]
Sent: Wednesday, August 28, 2002 1:09 PM
To: Jeff Parker
Cc: 'Noguchi Kay'; isis-wg@ietf.org; tli@procket.com; prz@xebeo.com
Subject: [Isis-wg] Re: index of isisISAdjIPAddrEntry


Hi Jeff, Tony and Tony,

# I added the working group chairs, Tony and Tony, to report ml problem.

At Wed, 28 Aug 2002 13:46:30 -0400,
Jeff Parker wrote:
> 
> Any opinions from the list?  Is dealing with 
> Addresses routine enough that we can drop the
> index from isisISAdjIPAddrEntry?  Or difficult
> enough that we should add it to the other two?
> Or is the current version with both in place
> reasonable.  

	Yes, I want to know other guys opinions and, of course, I vote
	for the change of isisISAdjIPAddrIndex to isisISAdjIPAddress.

	But right now, we have a problem with isis-wg@ietf.org mailing list
	so nobody except me and Jeff receives this discussions.

	Tony, could you check and fix the isis-wg@ietf.org mailing list
	configuration? As I reported before to Tony Przygienda, my
	MTA, exim, claims no errors in the transactions show below.

2002-08-28 10:54:52 17k71o-0002A4-00 <= kay@ipinfusion.com H=titanium
(titanium.
ipinfusion.com) [127.0.0.1] P=esmtp S=2186 id=877kiaj2c4.wl@ipinfusion.com
2002-08-28 10:54:58 17k71o-0002A4-00 => jparker@axiowave.com R=lookuphost
T=remo
te_smtp H=mail.axiowave.com [64.115.125.242]
2002-08-28 10:54:58 17k71o-0002A4-00 => kay@ipinfusion.com R=lookuphost
T=remote
_smtp H=mail.ipinfusion.com [65.223.109.2]
2002-08-28 10:55:00 17k71o-0002A4-00 => isis-wg@ietf.org R=lookuphost
T=remote_s
mtp H=odin.ietf.org [132.151.1.176]
2002-08-28 10:55:00 17k71o-0002A4-00 Completed

	And we can't see any discussion after Aug. 04 in the archive. 

http://www1.ietf.org/mail-archive/working-groups/isis-wg/current/threads.htm
l

Thank you,

> - jeff parker
> - axiowave networks
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg
--=_IS_MIME_Boundary
Content-Type: text/plain;charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

----------------------------------------- (on rchss001)

This e-mail and any files transmitted with it are the property
of Chiaro Networks, Ltd., and may contain confidential and 
privileged material for the sole use of the intended recipient(s)
to whom this e-mail is addressed. If you are not one of the named
recipient(s), or otherwise have reason to believe that you have 
received this message in error, please notify the sender and 
delete all copies from your system.  Any other use, retention, 
dissemination, forwarding, printing or copying of this e-mail is 
strictly prohibited.


---------------------------------------------------------

--=_IS_MIME_Boundary--
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 11:39:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07976
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 11:39:44 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FVkX14922;
	Fri, 6 Sep 2002 11:31:46 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g85Jn9t27593
	for <isis-wg@optimus.ietf.org>; Thu, 5 Sep 2002 15:49:09 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04400
	for <isis-wg@ietf.org>; Thu, 5 Sep 2002 15:47:27 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA13885;
	Thu, 5 Sep 2002 15:48:31 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id PAA00783;
	Thu, 5 Sep 2002 15:48:32 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <R68QM9FD>; Thu, 5 Sep 2002 15:48:32 -0400
Message-ID: <39469E08BD83D411A3D900204840EC55BC2DC7@vie-msgusr-01.dc.fore.com>
From: "Abarbanel, Benjamin" <Benjamin.Abarbanel@Marconi.com>
To: "'Chris Hopps'" <chopps@allegronetworks.com>,
        "'sarav_k@spymac.com'"
	 <sarav_k@spymac.com>
Cc: isis-wg@ietf.org
Subject: RE: [Isis-wg] up/down bit question..
Date: Thu, 5 Sep 2002 15:48:31 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

Hi Chris:

Got a general but basic question for you. Can you leak IPv4 L1L2 addresses
into IPv6 L1L2 LSP database and vice versa? 

Do you keep one LSP database containing both IP address families; or two LSP
databases one for each IP address family?

Ben

> -----Original Message-----
> From: Chris Hopps [mailto:chopps@allegronetworks.com]
> Sent: Thursday, September 05, 2002 2:35 PM
> To: 'sarav_k@spymac.com'
> Cc: isis-wg@ietf.org
> Subject: RE: [Isis-wg] up/down bit question..
> 
> 
> Perhaps I didn't quote enough from [2] :)
> 
> If you look at the referenced document you'll find:
> 
>    "If a prefix is advertised from an area to another area at the same
>    level, then the up/down bit shall be set to 1. This situation can
>    arise when a router implements multiple virtual routers at the same
>    level, but in different areas."
> 
> Chris.
> 
> -----Original Message-----
> From: Saravana Kumar [mailto:sarav_k@spymac.com]
> Sent: Tuesday, September 03, 2002 10:34 AM
> To: isis-wg@ietf.org
> Subject: [Isis-wg] up/down bit question..
> 
> 
> Hi Everyone,
> 
> I have a little doubt on the section about the up/down bit in the 
> ISIS IPV6 draft, which goes like this..
> 
>   "As is described in [2], "the up/down bit is set to 0 when a 
>    prefix is first injected into IS-IS.  If a prefix is 
>    redistributed from a higher level to a lower level (e.g., 
>    level two to level one), the bit shall be set to 1 to indicate
>    that the prefix has travelled down the hierarchy.  If a prefix
>    is redistributed from an area to another area at the same level
>    then the up/down bit shall be set to 1."
> 
> I can understand the first two cases, but i cant put my finger on the
> third. In which cases do we re-distribute from one area to another 
> area 'at the same level' ?
> 
> If we re-distribute the routes from one area 'A' into another 
> area 'B',
> my guess is that it will be done by the L1L2 router in area 'B',which
> would actually do a selective L2->L1 prefix distribution ( i.e 
> distributing all the prefixes that it learns from the L2 LSP's coming 
> from area 'A') This is again a case of redistributing routes from a 
> higher level to a lower level. When do we redistribute from an area to
> another area at the same level ?
> 
> Thanks,
> Sarav
> 
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 11:54:43 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08932
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 11:54:42 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FkVX16767;
	Fri, 6 Sep 2002 11:46:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86FI6X13237
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 11:18:06 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA06520
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 11:16:25 -0400 (EDT)
Received: from net4u.ch (gw.xebeo.com [204.192.44.242])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g86FI1J03302
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 17:18:02 +0200
Message-ID: <3D78C169.5080007@net4u.ch>
Date: Fri, 06 Sep 2002 07:53:29 -0700
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] Atlanta meeting ...
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I intend to be 3 days or so in Atlanta and wanted to ask for a slot 
given there are enough things on
the agenda (which I think there will). Requests to me or Tony Li pls

    thanks

    -- tony przygienda



_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 12:13:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10667
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 12:13:21 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86GC4X21980;
	Fri, 6 Sep 2002 12:12:04 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8699Pt04472
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 05:09:25 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28429
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 05:07:48 -0400 (EDT)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp189.cisco.com [10.50.0.188])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA04060;
	Fri, 6 Sep 2002 10:08:33 +0100 (BST)
Message-Id: <4.3.2.7.2.20020906095803.04434a50@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 06 Sep 2002 10:08:30 +0100
To: Saravana Kumar <saravanak@huawei.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
Cc: isis <isis-wg@ietf.org>
In-Reply-To: <001501c249eb$04af8870$4004120a@huaweisarav>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

At 20:18 22/08/2002 +0530, Saravana Kumar wrote:
>Hello There,
>
>I have a few questions on the IS-IS Restart Signaling draft
>  draft-ietf-isis-restart-01.txt ), My understanding of IS-IS and this draft
>is still a bit patchy and i hope to clear them up before i start
>implementing it. Here goes...
>
>- Is it necessary that the 3-way handshake be implemented on the system for
>the restart signaling work ? I guess this draft is written keeping in mind
>the extra processing we have to do incase the 3-way handshake is implemented
>on the system. Otherwise it is not really mandatory is it ?

No I'd say it was mandatory. You really need the assurance the 3WH gives you.


>  - In section "4.2 Adjacent re-acquisition" : The following clause is not
>very clear to me.
>
>    "DO NOT refresh the timer on the adjacency, but leave the
>      adjacency in state "Up","
>
>   I assume the timer being referred to here is the Adjacency Hold Timer for
>the particular adjacency. What does "DO NOT refresh the timer on the
>adjacency" mean here ? If we don't reset it ( im assuming refresh = reset )
>the timer is gonna sooner rather than later, which is not what we wanted in
>the first place.

Yes it is. The idea is that the restart stuff doesn't delay the expiration 
of the adjacency holding timer, so that if something goes wrong it will 
fail (and correct routes around the problem will be calculated) no later 
than it would have done had we not done the re-start stuff. I.e. it doesn't 
make things worse.

There are those (Naiming?) who believe this is a bad idea, and I have some 
sympathy with that viewpoint. This says that since we have committed to 
doing restart, we ought to be able to extend the adjacency holding timer to 
give ourselves a bit more time to get it all done. So the spec now permits 
you to do this if you want to.

So to summarise, the text your referred to says don't refresh, but you MAY 
refresh if you want to.

>- In section "4.3.1.2 Restarting" :
>     Do we have to store the sequence numbers of the routers 'own' LSP's in
>some non-volatile memory before the router restarts and use the stored
>sequence numbers to generate the LSP's ?

No. There is no need to do that.

>or do have to first purge all our
>'own' LSP's by setting its remaining lifetime to zero and flooding it and
>then after the zero-age timer expires, re-originate the LSPs again freshly.

No. Don't have to do that either.



         Mike


>This is it for now.. Thanks,
>Sarav
>
>PS : I would also appreciate it if someone answered my question on MTU
>changes in the IS-IS router, which i posted to this list yesterday.
>
>
>
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 12:15:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10777
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 12:15:15 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86GE8X22136;
	Fri, 6 Sep 2002 12:14:08 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g869IBt04663
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 05:18:11 -0400
Received: from ws1-10.us4.outblaze.com (205-158-62-111.outblaze.com [205.158.62.111])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA28530
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 05:16:33 -0400 (EDT)
Received: (qmail 94296 invoked by uid 1001); 6 Sep 2002 09:07:36 -0000
Message-ID: <20020906090736.94295.qmail@iname.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-10.us4.outblaze.com with http for
    philip.christian@iname.com; Fri, 06 Sep 2002 09:07:36 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: "Manral, Vishwas" <VishwasM@netplane.com>
Cc: isis-wg@ietf.org
Date: Fri, 06 Sep 2002 09:07:36 +0000
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-10.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I would be glad to help and would like to be on the list.

In a single protocol environment the differences between OSPF and IS-IS are small, although the extensibility of IS-IS is one notable exception (they had to do opaque LSAs to get this in OSPF, and not all implementations support it).

The differences in a multiprotocol environment are enormous though.  With the demise of CLNP everyone has forgot about the "Integrated" part of Integrated IS-IS, but with IPv6 coming onto the scene it will get important again.

You cannot do this with OSPF
http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-01.txt (shameless plug for my own work :)

On the other hand OSPF is probably more idiot proof.  You don't have to worry about topological restrictions so much.  Also IS-IS doesn't have a virtual link capability, although the forgotten IS-IS over IP draft would allow virtual links.

Philip
----- Original Message -----
From: "Manral, Vishwas" <VishwasM@netplane.com>
Date: Wed, 4 Sep 2002 06:58:56 -0400 
To: "''isis-wg@ietf.org''" <isis-wg@ietf.org>
Subject: [Isis-wg] Paper comparing OSPF and ISIS


> Hi folks,
> 
> The topic of differences between OSPF and ISIS has been raised more than
> once. The topic has been covered in a few presentations before as well as a
> lot of internal documents. It would however be helpful to "compare both
> specs and put down the differences and pros and cons of the differences" for
> the benefit of people.
> 
> I intend to make a group of people who would be interested in the effort. So
> anyone willing to help can mail me and I will add them to the group, from
> where we can take this further on.
> 
> I do have a preliminary list of things to start off.
> 
> Thanks,
> Vishwas
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> 

-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 12:17:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA10940
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 12:17:53 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86G9oX21710;
	Fri, 6 Sep 2002 12:09:50 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86919t04267
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 05:01:09 -0400
Received: from ws1-10.us4.outblaze.com (205-158-62-111.outblaze.com [205.158.62.111])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA28321
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 04:59:32 -0400 (EDT)
Received: (qmail 62875 invoked by uid 1001); 6 Sep 2002 08:47:39 -0000
Message-ID: <20020906084739.62874.qmail@iname.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-10.us4.outblaze.com with http for
    philip.christian@iname.com; Fri, 06 Sep 2002 08:47:39 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: jparker@axiowave.com,
        "'Radia Perlman - Boston Center for Networking'" <Radia.Perlman@sun.com>,
        isis-wg@ietf.org
Date: Fri, 06 Sep 2002 08:47:39 +0000
Subject: RE: [Isis-wg] What is the largest MTU we can assume that won't ge
    t fragmented?
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-10.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

If you want to interwork with SONET/SDH DCN IS-IS networks that have any LAPD links then you are limited to a lower number (576 I think).

In the new IP standard we went for PPP and 1500, but I think that most multiplexers, even being sold / installed today will be the old LAPD and OSI standards, and of course you only need one of the old ones somewhere in the domain and you are limited to the old number...

Philip

----- Original Message -----
From: Jeff Parker <jparker@axiowave.com>
Date: Thu, 5 Sep 2002 13:57:14 -0400 
To: "''Radia Perlman - Boston Center for Networking''" <Radia.Perlman@sun.com>, isis-wg@ietf.org
Subject: RE: [Isis-wg] What is the largest MTU we can assume that won't ge t fragmented?


>  
> > Anyway, I thought IS-IS had LSP fragments of 1500 because it 
> > was assumed that would be safely carried on all links. 
> > (Do I remember correctly?).
> > 
> > Radia
> 
> Radia -
> 	When we were doing the standards archeology for the
> interoperability draft, someone (mike shand?) pointed out
> that while 1492 was an upper bound, there were provisions
> to -lower- that MTU in a network, using the management 
> parameters originatingL1LSPBufferSize and 
> originatingL2LSPBufferSize.  The details of how that would
> work in practice are in the draft.  
> 
> 	So you didn't make that assumption.
> 
> - jeff parker   
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> 

-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 12:23:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11414
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 12:23:33 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86GG1X22294;
	Fri, 6 Sep 2002 12:16:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g869OYt04834
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 05:24:34 -0400
Received: from xover.netplane.com (fwout.maker.com [12.27.183.253] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28622
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 05:22:57 -0400 (EDT)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0A4ZG>; Fri, 6 Sep 2002 05:24:04 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328791577@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'Philip Christian'" <philip.christian@iname.com>
Cc: isis-wg@ietf.org
Subject: RE: [Isis-wg] Paper comparing OSPF and ISIS
Date: Fri, 6 Sep 2002 05:26:06 -0400 
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@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

Hi Philip,

We have the points you mentioned on our radar already,;-) besides many more.

I will add you to the list.

Thanks,
Vishwas

-----Original Message-----
From: Philip Christian [mailto:philip.christian@iname.com]
Sent: Friday, September 06, 2002 2:38 PM
To: Manral, Vishwas
Cc: isis-wg@ietf.org
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS


I would be glad to help and would like to be on the list.

In a single protocol environment the differences between OSPF and IS-IS are
small, although the extensibility of IS-IS is one notable exception (they
had to do opaque LSAs to get this in OSPF, and not all implementations
support it).

The differences in a multiprotocol environment are enormous though.  With
the demise of CLNP everyone has forgot about the "Integrated" part of
Integrated IS-IS, but with IPv6 coming onto the scene it will get important
again.

You cannot do this with OSPF
http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-01.txt
(shameless plug for my own work :)

On the other hand OSPF is probably more idiot proof.  You don't have to
worry about topological restrictions so much.  Also IS-IS doesn't have a
virtual link capability, although the forgotten IS-IS over IP draft would
allow virtual links.

Philip
----- Original Message -----
From: "Manral, Vishwas" <VishwasM@netplane.com>
Date: Wed, 4 Sep 2002 06:58:56 -0400 
To: "''isis-wg@ietf.org''" <isis-wg@ietf.org>
Subject: [Isis-wg] Paper comparing OSPF and ISIS


> Hi folks,
> 
> The topic of differences between OSPF and ISIS has been raised more than
> once. The topic has been covered in a few presentations before as well as
a
> lot of internal documents. It would however be helpful to "compare both
> specs and put down the differences and pros and cons of the differences"
for
> the benefit of people.
> 
> I intend to make a group of people who would be interested in the effort.
So
> anyone willing to help can mail me and I will add them to the group, from
> where we can take this further on.
> 
> I do have a preliminary list of things to start off.
> 
> Thanks,
> Vishwas
> 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 12:26:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11584
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 12:26:23 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86GKlX22872;
	Fri, 6 Sep 2002 12:20:47 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86A0ht05549
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 06:00:43 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29012
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 05:59:03 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2000710H59XR@mta2.huawei.com> for isis-wg@ietf.org;
 Fri, 06 Sep 2002 18:00:46 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H20008TOH58BJ@mta2.huawei.com> for isis-wg@ietf.org;
 Fri, 06 Sep 2002 18:00:45 +0800 (CST)
Received: from huaweisarav ([10.18.4.64])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H20H6O00.U13; Fri, 06 Sep 2002 18:01:36 +0800
Date: Fri, 06 Sep 2002 15:31:30 +0530
From: Saravana Kumar <saravanak@huawei.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
To: mike shand <mshand@cisco.com>
Cc: isis <isis-wg@ietf.org>
Message-id: <01ad01c2558c$5f53b920$4004120a@huaweisarav>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4.3.2.7.2.20020906095803.04434a50@jaws.cisco.com>
Content-Transfer-Encoding: 7BIT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT

Hi Mike,

Thanks for your clarifications, i have some more questions/comments on the
draft.

> So to summarise, the text your referred to says don't refresh, but you MAY
> refresh if you want to.

Just to make sure that i got this right. I'am assuming that it is the
restarting routers responsibility to refresh the neighbors adjacency timer,
if it wants to, by sending out a "normal" IIH to the neighbor. Is this right
?

There are conflicting statements regarding running SPF in section 4.3.1.2.
First it says that the SPF should not be run to update the forwarding tables
when timer T3 is running. And then a couple of paragraphs later it says that
When timer T2 expires or is cancelled the SPF is run to update the RIB and
FIB. Which is true then ?

Since currently. almost everyone supports both L1->L2 & L2->L1 route
distribution, we can never really run SPF for one level and generate LSPs
for that level, before the other levels database is synchronized. So I guess
it will be better to put off SPF computation till all the levels databases
are synchronized. Now when T3 expires prematurely here, we should first run
SPF for all the levels which have completed their database synchronization
and then transmit LSPs for those levels. For the other levels whose database
is not yet synchronized we generate the LSPs with the overloadbit set.

Finally... before timer T3 is cancelled, should the re-starting router (in
the case of a warm restart) run the DR election whenever it re-acquires
adjacencies with its neighbors ?  If it is allowed to do so, can it generate
its 'own' pseudonode LSPs for the LAN ?  It is not mentioned anywhere in the
draft.

Thanks,
Sarav

> At 20:18 22/08/2002 +0530, Saravana Kumar wrote:
> >Hello There,
> >
> >I have a few questions on the IS-IS Restart Signaling draft
> >  draft-ietf-isis-restart-01.txt ), My understanding of IS-IS and this
draft
> >is still a bit patchy and i hope to clear them up before i start
> >implementing it. Here goes...
> >
> >- Is it necessary that the 3-way handshake be implemented on the system
for
> >the restart signaling work ? I guess this draft is written keeping in
mind
> >the extra processing we have to do incase the 3-way handshake is
implemented
> >on the system. Otherwise it is not really mandatory is it ?
>
> No I'd say it was mandatory. You really need the assurance the 3WH gives
you.
>
>
> >  - In section "4.2 Adjacent re-acquisition" : The following clause is
not
> >very clear to me.
> >
> >    "DO NOT refresh the timer on the adjacency, but leave the
> >      adjacency in state "Up","
> >
> >   I assume the timer being referred to here is the Adjacency Hold Timer
for
> >the particular adjacency. What does "DO NOT refresh the timer on the
> >adjacency" mean here ? If we don't reset it ( im assuming refresh =
reset )
> >the timer is gonna sooner rather than later, which is not what we wanted
in
> >the first place.
>
> Yes it is. The idea is that the restart stuff doesn't delay the expiration
> of the adjacency holding timer, so that if something goes wrong it will
> fail (and correct routes around the problem will be calculated) no later
> than it would have done had we not done the re-start stuff. I.e. it
doesn't
> make things worse.
>
> There are those (Naiming?) who believe this is a bad idea, and I have some
> sympathy with that viewpoint. This says that since we have committed to
> doing restart, we ought to be able to extend the adjacency holding timer
to
> give ourselves a bit more time to get it all done. So the spec now permits
> you to do this if you want to.
>
> So to summarise, the text your referred to says don't refresh, but you MAY
> refresh if you want to.
>
> >- In section "4.3.1.2 Restarting" :
> >     Do we have to store the sequence numbers of the routers 'own' LSP's
in
> >some non-volatile memory before the router restarts and use the stored
> >sequence numbers to generate the LSP's ?
>
> No. There is no need to do that.
>
> >or do have to first purge all our
> >'own' LSP's by setting its remaining lifetime to zero and flooding it and
> >then after the zero-age timer expires, re-originate the LSPs again
freshly.
>
> No. Don't have to do that either.
>
>
>
>          Mike
>
>
> >This is it for now.. Thanks,
> >Sarav
> >
> >PS : I would also appreciate it if someone answered my question on MTU
> >changes in the IS-IS router, which i posted to this list yesterday.
> >
> >
> >
> >
> >_______________________________________________
> >Isis-wg mailing list
> >Isis-wg@ietf.org
> >https://www1.ietf.org/mailman/listinfo/isis-wg
>

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 12:38:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12489
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 12:38:25 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86GUvX24367;
	Fri, 6 Sep 2002 12:30:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86Bndt07653
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 07:49:39 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00317
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 07:47:59 -0400 (EDT)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp189.cisco.com [10.50.0.188])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA08140;
	Fri, 6 Sep 2002 12:49:02 +0100 (BST)
Message-Id: <4.3.2.7.2.20020906121408.044d32a0@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 06 Sep 2002 12:48:57 +0100
To: Saravana Kumar <saravanak@huawei.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
Cc: isis <isis-wg@ietf.org>
In-Reply-To: <01ad01c2558c$5f53b920$4004120a@huaweisarav>
References: <4.3.2.7.2.20020906095803.04434a50@jaws.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

At 15:31 06/09/2002 +0530, Saravana Kumar wrote:
>Hi Mike,
>
>Thanks for your clarifications, i have some more questions/comments on the
>draft.
>
> > So to summarise, the text your referred to says don't refresh, but you MAY
> > refresh if you want to.
>
>Just to make sure that i got this right. I'am assuming that it is the
>restarting routers responsibility to refresh the neighbors adjacency timer,
>if it wants to, by sending out a "normal" IIH to the neighbor. Is this right
>?

Yes.


>There are conflicting statements regarding running SPF in section 4.3.1.2.
>First it says that the SPF should not be run to update the forwarding tables
>when timer T3 is running. And then a couple of paragraphs later it says that
>When timer T2 expires or is cancelled the SPF is run to update the RIB and
>FIB. Which is true then ?

As I recall, the intention is that you don't update the FIB or regenerate 
LSPs until you are completely re-synchronized on both levels, but when each 
level completes synchronization you can run the SPF for that level in order 
to get the information you need to propagate into the other level.


>Since currently. almost everyone supports both L1->L2 & L2->L1 route
>distribution, we can never really run SPF for one level and generate LSPs
>for that level, before the other levels database is synchronized. So I guess
>it will be better to put off SPF computation till all the levels databases
>are synchronized. Now when T3 expires prematurely here, we should first run
>SPF for all the levels which have completed their database synchronization
>and then transmit LSPs for those levels. For the other levels whose database
>is not yet synchronized we generate the LSPs with the overloadbit set.

Perhaps, but it might be safer just to set the bit for both levels.


>Finally... before timer T3 is cancelled, should the re-starting router (in
>the case of a warm restart) run the DR election whenever it re-acquires
>adjacencies with its neighbors ?

Yes.

>  If it is allowed to do so, can it generate
>its 'own' pseudonode LSPs for the LAN ?  It is not mentioned anywhere in the
>draft.


You mean if it becomes the DR as a result of the election, when previously 
it wasn't? That means that it LOST an adjacency during this period (or 
someone fiddled with the priorities), which is a bit odd.

If something has REALLY changed, then there is little point in trying to 
hide it from the rest of the network. It will find out soon enough. It is 
only transient "changes" which we would eventually put back to how they 
were, that we want to suppress.


The whole assumption of the draft is that nothing else changed. If it does 
change then you might as well give up on the re-start mechanism.

We certainly don't want to have to describe all the nuances of what might 
happen, its just too complicated.






>Thanks,
>Sarav
>
> > At 20:18 22/08/2002 +0530, Saravana Kumar wrote:
> > >Hello There,
> > >
> > >I have a few questions on the IS-IS Restart Signaling draft
> > >  draft-ietf-isis-restart-01.txt ), My understanding of IS-IS and this
>draft
> > >is still a bit patchy and i hope to clear them up before i start
> > >implementing it. Here goes...
> > >
> > >- Is it necessary that the 3-way handshake be implemented on the system
>for
> > >the restart signaling work ? I guess this draft is written keeping in
>mind
> > >the extra processing we have to do incase the 3-way handshake is
>implemented
> > >on the system. Otherwise it is not really mandatory is it ?
> >
> > No I'd say it was mandatory. You really need the assurance the 3WH gives
>you.
> >
> >
> > >  - In section "4.2 Adjacent re-acquisition" : The following clause is
>not
> > >very clear to me.
> > >
> > >    "DO NOT refresh the timer on the adjacency, but leave the
> > >      adjacency in state "Up","
> > >
> > >   I assume the timer being referred to here is the Adjacency Hold Timer
>for
> > >the particular adjacency. What does "DO NOT refresh the timer on the
> > >adjacency" mean here ? If we don't reset it ( im assuming refresh =
>reset )
> > >the timer is gonna sooner rather than later, which is not what we wanted
>in
> > >the first place.
> >
> > Yes it is. The idea is that the restart stuff doesn't delay the expiration
> > of the adjacency holding timer, so that if something goes wrong it will
> > fail (and correct routes around the problem will be calculated) no later
> > than it would have done had we not done the re-start stuff. I.e. it
>doesn't
> > make things worse.
> >
> > There are those (Naiming?) who believe this is a bad idea, and I have some
> > sympathy with that viewpoint. This says that since we have committed to
> > doing restart, we ought to be able to extend the adjacency holding timer
>to
> > give ourselves a bit more time to get it all done. So the spec now permits
> > you to do this if you want to.
> >
> > So to summarise, the text your referred to says don't refresh, but you MAY
> > refresh if you want to.
> >
> > >- In section "4.3.1.2 Restarting" :
> > >     Do we have to store the sequence numbers of the routers 'own' LSP's
>in
> > >some non-volatile memory before the router restarts and use the stored
> > >sequence numbers to generate the LSP's ?
> >
> > No. There is no need to do that.
> >
> > >or do have to first purge all our
> > >'own' LSP's by setting its remaining lifetime to zero and flooding it and
> > >then after the zero-age timer expires, re-originate the LSPs again
>freshly.
> >
> > No. Don't have to do that either.
> >
> >
> >
> >          Mike
> >
> >
> > >This is it for now.. Thanks,
> > >Sarav
> > >
> > >PS : I would also appreciate it if someone answered my question on MTU
> > >changes in the IS-IS router, which i posted to this list yesterday.
> > >
> > >
> > >
> > >
> > >_______________________________________________
> > >Isis-wg mailing list
> > >Isis-wg@ietf.org
> > >https://www1.ietf.org/mailman/listinfo/isis-wg
> >

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 12:40:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12761
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 12:40:37 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86Ga1X25029;
	Fri, 6 Sep 2002 12:36:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86D85t09291
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 09:08:05 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02235
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 09:06:25 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H20007WPPTIXR@mta2.huawei.com> for isis-wg@ietf.org;
 Fri, 06 Sep 2002 21:08:06 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H20008DLPTHBJ@mta2.huawei.com> for isis-wg@ietf.org;
 Fri, 06 Sep 2002 21:08:06 +0800 (CST)
Received: from huaweisarav ([10.18.4.64])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H20PUX00.U1A; Fri, 06 Sep 2002 21:08:57 +0800
Date: Fri, 06 Sep 2002 18:38:50 +0530
From: Saravana Kumar <saravanak@huawei.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
To: mike shand <mshand@cisco.com>
Cc: isis <isis-wg@ietf.org>
Message-id: <021701c255a6$8b445ac0$4004120a@huaweisarav>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <4.3.2.7.2.20020906095803.04434a50@jaws.cisco.com>
 <4.3.2.7.2.20020906121408.044d32a0@jaws.cisco.com>
Content-Transfer-Encoding: 7BIT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7BIT


> >There are conflicting statements regarding running SPF in section
4.3.1.2.
> >First it says that the SPF should not be run to update the forwarding
tables
> >when timer T3 is running. And then a couple of paragraphs later it says
that
> >When timer T2 expires or is cancelled the SPF is run to update the RIB
and
> >FIB. Which is true then ?
>
> As I recall, the intention is that you don't update the FIB or regenerate
> LSPs until you are completely re-synchronized on both levels, but when
each
> level completes synchronization you can run the SPF for that level in
order
> to get the information you need to propagate into the other level.

Again, what you are saying is different from the statement in the draft. The
meaning of forwarding table and RIB (& FIB) seems to be interchanged there.
IMHO the statements in the draft can be changed as follows...

  "When the timer T2 expires, or is cancelled, the SPF is run to update
   the RIB and FIB."

   be changed to..


   "When the timer T2 expires, or is cancelled, the SPF is run to update
   the forwarding table of the corresponding level."

  And the statement..

   "In the case of a re-starting router, none of the router's own non-
    pseudonode LSPs are transmitted, nor is the SPF run to update the
    forwarding tables while the timer T3 is running."

  be changed to..

  "In the case of a re-starting router, none of the router's own non-
   pseudonode LSPs are transmitted, nor is the SPF run to update the
   RIB and FIB while the timer T3 is running. "

> >Finally... before timer T3 is cancelled, should the re-starting router
(in
> >the case of a warm restart) run the DR election whenever it re-acquires
> >adjacencies with its neighbors ?
>
> Yes.
>
> >  If it is allowed to do so, can it generate
> >its 'own' pseudonode LSPs for the LAN ?  It is not mentioned anywhere in
the
> >draft.
>
> You mean if it becomes the DR as a result of the election, when previously
> it wasn't? That means that it LOST an adjacency during this period (or
> someone fiddled with the priorities), which is a bit odd.

No, i was referring to the simple case :). What if the restarting router
determines that it is the DR for the LAN (it has been the DR previously).
Then should it generate pseudonode LSPs for the LAN ?  I guess there is no
harm in generating a pseudonode LSP in this case ( then again there is no
harm in not generating the pseudonode LSP also )

Thanks,
Sarav

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 12:48:10 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13278
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 12:48:10 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86GeIX25683;
	Fri, 6 Sep 2002 12:40:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86ElFt11661
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 10:47:15 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05765
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 10:45:35 -0400 (EDT)
Received: from net4u.ch (gw.xebeo.com [204.192.44.242])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g86El7J31480;
	Fri, 6 Sep 2002 16:47:08 +0200
Message-ID: <3D78BA2B.5010402@net4u.ch>
Date: Fri, 06 Sep 2002 07:22:35 -0700
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Manral, Vishwas" <VishwasM@netplane.com>
CC: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
References: <E7E13AAF2F3ED41197C100508BD6A328791541@india_exch.hyderabad.mindspeed.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Manral, Vishwas wrote:

>Hi folks,
>
>The topic of differences between OSPF and ISIS has been raised more than
>once. The topic has been covered in a few presentations before as well as a
>lot of internal documents. It would however be helpful to "compare both
>specs and put down the differences and pros and cons of the differences" for
>the benefit of people.
>
>I intend to make a group of people who would be interested in the effort. So
>anyone willing to help can mail me and I will add them to the group, from
>where we can take this further on.
>
>I do have a preliminary list of things to start off.
>
Manral, please do not use this list for this purpose if you choose to 
pursuit it. It is outside the scope
of this workgroup for sure and on top, I am not entirely sure anything 
really new comes out of it.
Dave K.'s presentation pretty well covered the issues IMHO.

    -- tony przygienda


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 13:25:01 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14642
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 13:25:01 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86HGOX28751;
	Fri, 6 Sep 2002 13:16:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86HDqX28652
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 13:13:52 -0400
Received: from xover.netplane.com (fwout.maker.com [12.27.183.253] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14246
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 13:12:11 -0400 (EDT)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0AVTZ>; Fri, 6 Sep 2002 13:13:15 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328791586@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'prz@net4u.ch'" <prz@net4u.ch>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] Paper comparing OSPF and ISIS
Date: Fri, 6 Sep 2002 13:15:38 -0400 
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@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

Hi Tony,

I am sorry about that. Did not realize I couldn't do this, I however did
know this was not in the charter.

Thanks,
Vishwas

-----Original Message-----
From: Tony Przygienda [mailto:prz@net4u.ch]
Sent: Friday, September 06, 2002 7:53 PM
To: Manral, Vishwas
Cc: 'isis-wg@ietf.org'
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS


Manral, Vishwas wrote:

>Hi folks,
>
>The topic of differences between OSPF and ISIS has been raised more than
>once. The topic has been covered in a few presentations before as well as a
>lot of internal documents. It would however be helpful to "compare both
>specs and put down the differences and pros and cons of the differences"
for
>the benefit of people.
>
>I intend to make a group of people who would be interested in the effort.
So
>anyone willing to help can mail me and I will add them to the group, from
>where we can take this further on.
>
>I do have a preliminary list of things to start off.
>
Manral, please do not use this list for this purpose if you choose to 
pursuit it. It is outside the scope
of this workgroup for sure and on top, I am not entirely sure anything 
really new comes out of it.
Dave K.'s presentation pretty well covered the issues IMHO.

    -- tony przygienda

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 14:07:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA16057
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 14:07:23 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86I5NX30780;
	Fri, 6 Sep 2002 14:05:23 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86I1VX30629
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 14:01:31 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15706
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 13:59:48 -0400 (EDT)
Received: from net4u.ch (gw.xebeo.com [204.192.44.242])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g86I1MJ25538;
	Fri, 6 Sep 2002 20:01:22 +0200
Message-ID: <3D78E7AC.9030908@net4u.ch>
Date: Fri, 06 Sep 2002 10:36:44 -0700
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Manral, Vishwas" <VishwasM@netplane.com>
CC: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
References: <E7E13AAF2F3ED41197C100508BD6A328791586@india_exch.hyderabad.mindspeed.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Manral, Vishwas wrote:

>Hi Tony,
>
>I am sorry about that. Did not realize I couldn't do this, I however did
>know this was not in the charter.
>
Manral,

To be perfectly frank, I am not sure what productive use the effort 
would have and I see a lot
of possible shrapnel flying with innocent bystanders being hit. OSPF 
will unlikely adopt ISIS 'goodies'
since they have a large deployed base, very good documentation and 
frankly, a very understandable,
'symmetric' protocol. On the ISIS side, there is a strong justification 
with a different set of customers
for what we're doing and how we're doing it so I have a hard time to see 
ISIS adopting OSPF 'goodies'.
And even if, most of the 'goodies' are nice to haves and more of 
philosophical design-tradeoff differences
than 'this-one's-clearly-better-solution' issues and even more if, they 
will probably break deployed base for
small incremental gain .  As for the shrapnel, the issue has the 
capability of  re-'create' yet another religious war.

    So I guess my point being, as always with explosives, handle with 
care unless
    you're interested in a Darwin award  ;-)

    -- tony

>
>
>Thanks,
>Vishwas
>
>-----Original Message-----
>From: Tony Przygienda [mailto:prz@net4u.ch]
>Sent: Friday, September 06, 2002 7:53 PM
>To: Manral, Vishwas
>Cc: 'isis-wg@ietf.org'
>Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
>
>
>Manral, Vishwas wrote:
>
>>Hi folks,
>>
>>The topic of differences between OSPF and ISIS has been raised more than
>>once. The topic has been covered in a few presentations before as well as a
>>lot of internal documents. It would however be helpful to "compare both
>>specs and put down the differences and pros and cons of the differences"
>>
>for
>
>>the benefit of people.
>>
>>I intend to make a group of people who would be interested in the effort.
>>
>So
>
>>anyone willing to help can mail me and I will add them to the group, from
>>where we can take this further on.
>>
>>I do have a preliminary list of things to start off.
>>
>Manral, please do not use this list for this purpose if you choose to 
>pursuit it. It is outside the scope
>of this workgroup for sure and on top, I am not entirely sure anything 
>really new comes out of it.
>Dave K.'s presentation pretty well covered the issues IMHO.
>
>    -- tony przygienda
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg
>
>



_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 14:48:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17486
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 14:48:59 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86IcCX32411;
	Fri, 6 Sep 2002 14:38:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86IZMX32300
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 14:35:22 -0400
Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17069
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 14:33:40 -0400 (EDT)
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 g86IYjm19031;
	Fri, 6 Sep 2002 11:34:45 -0700 (PDT)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost)
	by cirrus.juniper.net (8.11.6/8.11.6) id g86IYjC36854;
	Fri, 6 Sep 2002 11:34:45 -0700 (PDT)
	(envelope-from dkatz@cirrus.juniper.net)
Date: Fri, 6 Sep 2002 11:34:45 -0700 (PDT)
Message-Id: <200209061834.g86IYjC36854@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: paragj@cisco.com
CC: isis-wg@ietf.org
In-reply-to: <3D78F10B.3C62A293@cisco.com> (message from Parag Jain on Fri, 06
	Sep 2002 14:16:43 -0400)
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
References: <E7E13AAF2F3ED41197C100508BD6A328791541@india_exch.hyderabad.mindspeed.com> <3D78BA2B.5010402@net4u.ch> <3D78F10B.3C62A293@cisco.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

I suspect this won't be the only request I get, so please excuse the spam:

http://www.nanog.org/mtg-0006/katz.html

--Dave


   Could you send me pointer to your presentation comaparing OSPF and ISIS.
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 15:22:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18356
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 15:22:00 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86JIfX01726;
	Fri, 6 Sep 2002 15:18:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86JFBX01555
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 15:15:11 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18086
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 15:13:29 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 6BA1E1DCC6B; Fri,  6 Sep 2002 12:15:04 -0700 (PDT)
To: prz@net4u.ch
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>, OSPF@DISCUSS.MICROSOFT.COM,
        riw@cisco.com
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS 
In-reply-to: Mail from Tony Przygienda <prz@net4u.ch> 
 dated Fri, 06 Sep 2002 07:22:35 PDT
 <3D78BA2B.5010402@net4u.ch> 
Date: Fri, 06 Sep 2002 12:15:04 -0700
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020906191504.6BA1E1DCC6B@prattle.redback.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>


Once Russ told me he was going to write a book on this subject:
"The differences between OSPF and ISIS", and he said there were only
three sentences in that book. Here is the electronic version of that
interesting book if I remember it correctly:

  ISIS is simple.

  OSPF is complicated.

  Otherwise they are the same.

thanks.
(hopefully i didn't violate his publisher's copyright issues)

 ] It is outside the scope
 ] of this workgroup for sure and on top, I am not entirely sure anything 
 ] really new comes out of it.
 ] Dave K.'s presentation pretty well covered the issues IMHO.
 ] 
 ]     -- tony przygienda

- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 16:17:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20191
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 16:17:07 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86KCVX03471;
	Fri, 6 Sep 2002 16:12:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86K93X03368
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 16:09:03 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19818
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 16:07:20 -0400 (EDT)
Received: from net4u.ch (gw.xebeo.com [204.192.44.242])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g86K8qJ11183;
	Fri, 6 Sep 2002 22:08:52 +0200
Message-ID: <3D79058D.6070704@net4u.ch>
Date: Fri, 06 Sep 2002 12:44:13 -0700
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Naiming Shen <naiming@redback.com>
CC: "'isis-wg@ietf.org'" <isis-wg@ietf.org>, OSPF@DISCUSS.MICROSOFT.COM,
        riw@cisco.com
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
References: <20020906191504.6BA1E1DCC6B@prattle.redback.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

Naiming Shen wrote:

>Once Russ told me he was going to write a book on this subject:
>"The differences between OSPF and ISIS", and he said there were only
>three sentences in that book. Here is the electronic version of that
>interesting book if I remember it correctly:
>
>  ISIS is simple.
>
>  OSPF is complicated.
>
>  Otherwise they are the same.
>
so, as you see, it's already starting :-(  

    sigh

    -- tony


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 17:09:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21584
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 17:09:02 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86L4sX06948;
	Fri, 6 Sep 2002 17:04:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86L1pX06864
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 17:01:51 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21259
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 17:00:07 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA10795;
	Fri, 6 Sep 2002 17:00:59 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA11186;
	Fri, 6 Sep 2002 17:01:01 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <R68Q3SM2>; Fri, 6 Sep 2002 17:01:00 -0400
Message-ID: <39469E08BD83D411A3D900204840EC55BC2DEE@vie-msgusr-01.dc.fore.com>
From: "Abarbanel, Benjamin" <Benjamin.Abarbanel@Marconi.com>
To: "'prz@net4u.ch'" <prz@net4u.ch>, Naiming Shen <naiming@redback.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>, OSPF@DISCUSS.MICROSOFT.COM,
        riw@cisco.com
Subject: RE: [Isis-wg] Paper comparing OSPF and ISIS
Date: Fri, 6 Sep 2002 17:00:59 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

I want to add.


> -----Original Message-----
> From: Tony Przygienda [mailto:prz@net4u.ch]
> Sent: Friday, September 06, 2002 3:44 PM
> To: Naiming Shen
> Cc: 'isis-wg@ietf.org'; OSPF@DISCUSS.MICROSOFT.COM; riw@cisco.com
> Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
> 
> 
> Naiming Shen wrote:
> 
> >Once Russ told me he was going to write a book on this subject:
> >"The differences between OSPF and ISIS", and he said there were only
> >three sentences in that book. Here is the electronic version of that
> >interesting book if I remember it correctly:

  "ISIS is simple but older.

   OSPF is complicated and younger.

   Otherwise they are the same.

   Imitation is the best form of flattery."

   Ben
 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 17:20:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21906
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 17:20:41 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86LBBX07801;
	Fri, 6 Sep 2002 17:11:11 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86L62X06993
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 17:06:02 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21427
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 17:04:18 -0400 (EDT)
Received: from net4u.ch (gw.xebeo.com [204.192.44.242])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g86L5nJ18225;
	Fri, 6 Sep 2002 23:05:49 +0200
Message-ID: <3D7912E6.3060909@net4u.ch>
Date: Fri, 06 Sep 2002 13:41:10 -0700
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: "Abarbanel, Benjamin" <Benjamin.Abarbanel@Marconi.com>
CC: Naiming Shen <naiming@redback.com>,
        "'isis-wg@ietf.org'"
 <isis-wg@ietf.org>, OSPF@DISCUSS.MICROSOFT.COM,
        riw@cisco.com
Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
References: <39469E08BD83D411A3D900204840EC55BC2DEE@vie-msgusr-01.dc.fore.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

I would encourage this 'technical-content-free' "discussion" to die. And 
if it cannot
die, I would encourage the removal of the ospf-mailing list from the 
list of recipients
from anybody who doesn't have enough usefull work to do and keeps up 
this thread

    -- tony


Abarbanel, Benjamin wrote:

>I want to add.
>
>
>>-----Original Message-----
>>From: Tony Przygienda [mailto:prz@net4u.ch]
>>Sent: Friday, September 06, 2002 3:44 PM
>>To: Naiming Shen
>>Cc: 'isis-wg@ietf.org'; OSPF@DISCUSS.MICROSOFT.COM; riw@cisco.com
>>Subject: Re: [Isis-wg] Paper comparing OSPF and ISIS
>>
>>
>>Naiming Shen wrote:
>>
>>>Once Russ told me he was going to write a book on this subject:
>>>"The differences between OSPF and ISIS", and he said there were only
>>>three sentences in that book. Here is the electronic version of that
>>>interesting book if I remember it correctly:
>>>
>
>  "ISIS is simple but older.
>
>   OSPF is complicated and younger.
>
>   Otherwise they are the same.
>
>   Imitation is the best form of flattery."
>
>   Ben
> 
>
>



_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep  6 17:55:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22866
	for <isis-archive@lists.ietf.org>; Fri, 6 Sep 2002 17:55:00 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86LrIX09824;
	Fri, 6 Sep 2002 17:53:18 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g86LouX09728
	for <isis-wg@optimus.ietf.org>; Fri, 6 Sep 2002 17:50:56 -0400
Received: from tahoe.sj.allegronetworks.com (tahoe.allegronetworks.com [63.115.58.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22657
	for <isis-wg@ietf.org>; Fri, 6 Sep 2002 17:49:12 -0400 (EDT)
Received: by tahoe.allegronetworks.com with Internet Mail Service (5.5.2653.19)
	id <SHRJFZK5>; Fri, 6 Sep 2002 14:50:15 -0700
Message-ID: <B4DFCB7CDE2DD4118F690008C78694160365BCA3@tahoe.allegronetworks.com>
From: Neal Castagnoli <cast@allegronetworks.com>
To: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Date: Fri, 6 Sep 2002 14:50:14 -0700 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] 10 m.s. Throttle interval?
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>


Does anyone know the origin of the 10 m.s. default throttle interval in the
MIB?  I've measured 30m.s. on some implementations.  At 10 m.s., the worse
case offered LSP load is about 100 LSPs/circuit second, which seems a bit
high.

  --Neal

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep  7 08:13:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11744
	for <isis-archive@lists.ietf.org>; Sat, 7 Sep 2002 08:13:56 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87C92X18725;
	Sat, 7 Sep 2002 08:09:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g87C6cX18140
	for <isis-wg@optimus.ietf.org>; Sat, 7 Sep 2002 08:06:38 -0400
Received: from cisco.com (uzura.cisco.com [64.102.17.77])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11646
	for <isis-wg@ietf.org>; Sat, 7 Sep 2002 08:04:57 -0400 (EDT)
Received: from ruwhite-u10.cisco.com (ruwhite-u10.cisco.com [64.102.48.251])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id IAA00994;
	Sat, 7 Sep 2002 08:06:04 -0400 (EDT)
Date: Sat, 7 Sep 2002 08:06:04 -0400 (EDT)
From: Russ White <ruwhite@cisco.com>
Reply-To: Russ White <riw@cisco.com>
To: Neal Castagnoli <cast@allegronetworks.com>
cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] 10 m.s. Throttle interval?
In-Reply-To: <B4DFCB7CDE2DD4118F690008C78694160365BCA3@tahoe.allegronetworks.com>
Message-ID: <Pine.GSO.4.21.0209070803180.804-100000@ruwhite-u10.cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>


If I remember right, I've bene told this number was picked out of
the air, a good guess for the types of circuits and hardware
available at the time of writing. I think most implementations
have played around with this number, at one point or another--the
problem would seem to be finding a good number for all possible
link types, processor types, etc., etc.... to use as a
default.

Russ

On Fri, 6 Sep 2002, Neal Castagnoli wrote:

> 
> Does anyone know the origin of the 10 m.s. default throttle interval in the
> MIB?  I've measured 30m.s. on some implementations.  At 10 m.s., the worse
> case offered LSP load is about 100 LSPs/circuit second, which seems a bit
> high.
> 
>   --Neal
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> 

__________________________________
riw@cisco.com CCIE <>< Grace Alone


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 10:53:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA04744
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 10:53:28 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89Eovv04651;
	Mon, 9 Sep 2002 10:50:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89EQfv02158
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 10:26:41 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26209
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 03:40:41 -0400 (EDT)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4260.cisco.com [10.50.16.163])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id IAA05451;
	Mon, 9 Sep 2002 08:41:42 +0100 (BST)
Message-Id: <4.3.2.7.2.20020909083842.0454fa20@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 09 Sep 2002 08:41:29 +0100
To: Russ White <riw@cisco.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] 10 m.s. Throttle interval?
Cc: Neal Castagnoli <cast@allegronetworks.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
In-Reply-To: <Pine.GSO.4.21.0209070803180.804-100000@ruwhite-u10.cisco.c
 om>
References: <B4DFCB7CDE2DD4118F690008C78694160365BCA3@tahoe.allegronetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

The 30mS number came from the capabilities of a DEC "Microserver" on 
Ethernet. We actually did quite a detailed analysis, but of course it only 
applied to that specific hardware.

I've no idea where the 10mS figure came from.

         Mike

At 08:06 07/09/2002 -0400, Russ White wrote:

>If I remember right, I've bene told this number was picked out of
>the air, a good guess for the types of circuits and hardware
>available at the time of writing. I think most implementations
>have played around with this number, at one point or another--the
>problem would seem to be finding a good number for all possible
>link types, processor types, etc., etc.... to use as a
>default.
>
>Russ
>
>On Fri, 6 Sep 2002, Neal Castagnoli wrote:
>
> >
> > Does anyone know the origin of the 10 m.s. default throttle interval in the
> > MIB?  I've measured 30m.s. on some implementations.  At 10 m.s., the worse
> > case offered LSP load is about 100 LSPs/circuit second, which seems a bit
> > high.
> >
> >   --Neal
> >
> > _______________________________________________
> > Isis-wg mailing list
> > Isis-wg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/isis-wg
> >
>
>__________________________________
>riw@cisco.com CCIE <>< Grace Alone
>
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 11:30:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07443
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 11:30:54 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89FTKv11781;
	Mon, 9 Sep 2002 11:29:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89FORv11558
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 11:24:27 -0400
Received: from auemail2.firewall.lucent.com ([192.11.223.163])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07100
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 11:22:50 -0400 (EDT)
Received: from hzsms01.nl.lucent.com (h135-85-32-31.lucent.com [135.85.32.31])
	by auemail2.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id g89FNtb08381
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 11:23:55 -0400 (EDT)
Received: by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id RAA24886; Mon, 9 Sep 2002 17:23:52 +0200 (MET DST)
Cc: nvbolhuis@lucent.com
Received: from hzsc076.nl.lucent.com by hzsms01.nl.lucent.com (8.8.8+Sun/EMS-1.5 sol2)
	id RAA24883; Mon, 9 Sep 2002 17:23:52 +0200 (MET DST)
Message-Id: <200209091523.RAA24883@hzsms01.nl.lucent.com>
Date: Mon, 9 Sep 2002 17:23:52 +0200 (MET DST)
From: "Norbert v. Bolhuis" <nvbolhuis@lucent.com>
Reply-To: "Norbert v. Bolhuis" <nvbolhuis@lucent.com>
Subject: RE: [Isis-wg] What is the largest MTU we can assume that won't get fragmented?
To: isis-wg@ietf.org
Original-Cc: nvbolhu@hzsms01.nl.lucent.com
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
Content-MD5: jnaKbwul46gwLD8Ck/l07g==
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>


> 
> If you want to interwork with SONET/SDH DCN IS-IS networks that have any LAPD links then you are limited to a lower 
number (576 I think).
> 


No, it's 512 bytes.


> In the new IP standard we went for PPP and 1500, but I think that most multiplexers, even being sold / installed today 
will be the old LAPD and OSI standards, and of course you only need one of the old ones somewhere in the domain and you 
are limited to the old number...
> 


> 


True.


-------------------
Norbert van Bolhuis
Lucent Technologies

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 14:13:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11827
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 14:13:37 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89EDr715538;
	Mon, 9 Sep 2002 10:13:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89E9k714151
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 10:09:46 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02489
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 10:07:54 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74220@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Neal Castagnoli'" <cast@allegronetworks.com>,
        "'isis-wg@ietf.org'"
	 <isis-wg@ietf.org>
Subject: RE: [Isis-wg] 10 m.s. Throttle interval?
Date: Mon, 9 Sep 2002 10:08:58 -0400 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

> Does anyone know the origin of the 10 m.s. default throttle 
> interval in the
> MIB?  I've measured 30m.s. on some implementations.  At 10 
> m.s., the worse
> case offered LSP load is about 100 LSPs/circuit second, which 
> seems a bit
> high.
> 
>   --Neal

Neal -
	I've updated the doc to read 30ms.  

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 16:49:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15939
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 16:49:21 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89KlPv30674;
	Mon, 9 Sep 2002 16:47:26 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7QIiIo15652
	for <isis-wg@optimus.ietf.org>; Mon, 26 Aug 2002 14:44:18 -0400
Received: from spyserver.y-w-s.de (server20.yourwebstart.com [81.2.136.20])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA18341
	for <isis-wg@ietf.org>; Mon, 26 Aug 2002 14:42:45 -0400 (EDT)
Received: from www-data by spyserver.y-w-s.de with local (Exim 3.35 #1 (Debian))
	id 17jOqx-00046j-00; Mon, 26 Aug 2002 12:44:43 -0600
Content-Disposition: inline
Content-Transfer-Encoding: binary
Mime-Version: 1.0
From: <sarav_k@spymac.com>
To: isis-wg@ietf.org
Date: Mon, 26 Aug 2002 12:44:42 -0000
Reply-To: sarav_k@spymac.com
Content-Type: text/plain
X-Mailer: AtMail Pro 3.01 - http://webbasedemail.com/
X-Uidl: 1030387482157874133
X-Origin: 210.210.50.162
Cc: sarav_k@spymac.com
Message-Id: <E17jOqx-00046j-00@spyserver.y-w-s.de>
Content-Transfer-Encoding: binary
Subject: [Isis-wg] MTU lowering in IS-IS
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: binary

Hello Everyone,

I have a question regarding how IS-IS should handle MTU changes in the System. If i decrease the MTU size on a interface to a value which will lower the current LSP buffer size, then how should IS-IS handle this case ?

 Also how do we inform the IS's neighbours that the Buffer Size in the Local IS has been lowered ? Does the padding of the IIH packets help in this case?

Thanks,
Sarav




_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 16:53:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16097
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 16:53:38 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89Kpjv30838;
	Mon, 9 Sep 2002 16:51:45 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7T6W9o24708
	for <isis-wg@optimus.ietf.org>; Thu, 29 Aug 2002 02:32:09 -0400
Received: from blooper.utfors.se (mail.utfors.se [195.58.103.125])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA11697
	for <isis-wg@ietf.org>; Thu, 29 Aug 2002 02:30:29 -0400 (EDT)
Received: from utfors.se (nat-sto.utfors.se [212.73.0.237])
	by blooper.utfors.se (8.12.6/8.12.6) with ESMTP id g7T6VQtA018469;
	Thu, 29 Aug 2002 08:31:26 +0200 (MEST)
Message-ID: <3D6DBFBE.4050603@utfors.se>
Date: Thu, 29 Aug 2002 08:31:26 +0200
From: Loa Andersson <loa.andersson@utfors.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: ospf wg <OSPF@DISCUSS.MICROSOFT.COM>, isis-wg <isis-wg@ietf.org>
CC: MPLS wg <mpls@uu.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Isis-wg] LAst Call: draft-ietf-mpls-bundle-04.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

OSPF and IS-IS working groups, (mpls wg for info)

the iesg has started the review of the mpls working group draft
draft-ietf-mpls-bundle-04.txt. The immediate response from the iesg
is that the draft contains OSPF and ISIS related details (see
the included mail). After discussing with the wg chairs for ospf
and is-is working groups, there is a feeling that the two weeks
the iesg allocated for this last call might not be enough, since the
draft has not been widely circulated in the routing working groups.

Therefore:

This is to initiate a last call for the

<draft-ietf-mpls-bundle-04.txt>

by the ospf and is-is working groups.
The last call ends September 22nd at 12PM CET


Please include the mpls mailing list (mpls@uu.net) in your responses.

/Loa (co-chair of the mpls wg)

-------- Original Message --------
Subject: draft-ietf-mpls-bundle-04.txt
Date: Tue, 27 Aug 2002 15:06:48 -0400 (EDT)
From: Scott Bradner
To: loa.andersson@utfors.se, swallow@cisco.com


The IESG discussed this ID last week during its teleconference
one issue was raised during the discussion

"the draft contains OSPF & ISIS
related details and I don't remember it being LC'ed or reviewed
in the corresponding WGs."

can you start a 2 week last call on the IS-IS and OSPF mailing
lists for this document?

Scott

-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     Råsundavägen 12
     Box 525, 169 29 Solna
     Office          +46 8 5270 2000
     Office direct   +46 8 5270 5038
     Mobile          +46 70 848 5038
     Email           loa.andersson@utfors.se
     WWW             www.utfors.se


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 16:57:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16188
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 16:57:17 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89Ktwv31015;
	Mon, 9 Sep 2002 16:55:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g7TNB7o12539
	for <isis-wg@optimus.ietf.org>; Thu, 29 Aug 2002 19:11:07 -0400
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14737
	for <isis-wg@ietf.org>; Thu, 29 Aug 2002 19:09:29 -0400 (EDT)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA04117;
	Thu, 29 Aug 2002 19:10:27 -0400 (EDT)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id TAA18561;
	Thu, 29 Aug 2002 19:10:21 -0400 (EDT)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <R68QG51M>; Thu, 29 Aug 2002 19:10:21 -0400
Message-ID: <39469E08BD83D411A3D900204840EC55763306@vie-msgusr-01.dc.fore.com>
From: "Naidu, Venkata" <Venkata.Naidu@Marconi.com>
To: "'Loa Andersson'" <loa.andersson@utfors.se>,
        ospf wg
	 <OSPF@DISCUSS.MICROSOFT.COM>, isis-wg <isis-wg@ietf.org>
Cc: MPLS wg <mpls@uu.net>
Date: Thu, 29 Aug 2002 19:10:18 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: LAst Call: draft-ietf-mpls-bundle-04.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

Link Bundling comments:

-> This is to initiate a last call for the
-> 
-> <draft-ietf-mpls-bundle-04.txt>


   All component links in a bundle must begin and end on the same pair
   of LSRs, have the same Link Type (i.e., point-to-point or multi-
   access), the same Traffic Engineering metric, and the same set of
   resource classes at each end of the links.

   A Forwarding Adjacency may be a component link; in fact, a bundle can
   consist of a mix of point-to-point links and FAs.

Link Types Restriction
----------------------
*** Only beginning & ending of the link types are restricted or
*** all the links along the path (from beginning router to end router)
*** are restricted to the same link type?

*** I didn't not understand why we need same link type at the 
*** beginning and at the end of the link? Link Type TLV will cover 
*** whatever link type at the advertising router side of the link. 
*** I didn't see any issue if we have different link types at each 
*** side of the link.

*** I request to elaborate these restriction a little bit with
*** a single appropriate diagram (if possible).

*** The use of bundling has very large scope. For example, one can
*** bundle all the VCs in a VP (where each VC is viewed as a different
*** link with its own resources). All such VPs can be bundled/unbundled 
*** (depending on the requirements). Still all those VPs will have 
*** a same risk-factor (i.e. SRLG). I think, it will be
*** better to mention few example of such uses of link bundling.


Metric Restriction
------------------
*** Why is the same metric restriction? Can a router have
*** the flexibility to decide a different metric for the bundled
*** link (may be independent of all the component links)?

*** For example, a router chooses the largest metric of all
*** component links (just like OSPF area aggregation). Just a
*** a matter of flexibility. If the metrics are different and
*** if we bundle those links did you see any problem?

*** Let is explain an example scenario, where router starts
*** advertising the largest of all links metric as bundled
*** link metric. One the largest component link resources (bw)
*** are completely consumed (crossed some threshold ) then
*** bundled link metric will become the next highest component
*** link metric.


Link Protection consideration
-----------------------------
*** There is no mention about link protection type of the bundled
*** link when component links are of different type?


SRLG consideration
------------------
*** There is no mention about SRLGs of bundled link w.r.t component
*** links. In some situations, failure of one component link may or
*** may not affect other component links. I think, it will be better
*** to mention something about SRLG - that is, all component links
*** in bundled link must have same SRLG (in order to benefit most
*** from bundling). Even if the component links risk factor is independent
*** from each other (ie. different SRLGs) still we can use bundling.
*** Please mention something like that...


Switching Capability consideration
----------------------------------
*** I think the switching capability should be same for all component
*** links in order to use bundling?! Please mention.


DiffServ consideration
----------------------
*** There is no mention about BCs and TE Classes applicability
*** to Link bundling? Do you see any issues w.r.t to the recent
*** diffserv draft (esp interpretation of unserverved bws etc)?

  Thank You.

--
Venkata.
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 17:01:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16481
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 17:01:28 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89L0Cv31390;
	Mon, 9 Sep 2002 17:00:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89GJgv15568
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 12:19:42 -0400
Received: from blooper.utfors.se (mail.utfors.se [195.58.103.125])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09097
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 12:18:05 -0400 (EDT)
Received: from utfors.se (nat-sto.utfors.se [212.73.0.237])
	by blooper.utfors.se (8.12.6/8.12.6) with ESMTP id g89GJBtA015969;
	Mon, 9 Sep 2002 18:19:11 +0200 (MEST)
Message-ID: <3D7CC9FF.6010509@utfors.se>
Date: Mon, 09 Sep 2002 18:19:11 +0200
From: Loa Andersson <loa.andersson@utfors.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:0.9.4.1) Gecko/20020508 Netscape6/6.2.3
X-Accept-Language: en-us
MIME-Version: 1.0
To: ospf wg <OSPF@DISCUSS.MICROSOFT.COM>, isis-wg <isis-wg@ietf.org>
CC: Loa Andersson <loa.andersson@utfors.se>, MPLS wg <mpls@uu.net>
References: <3D6DBFBE.4050603@utfors.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Isis-wg] Re: LAst Call: draft-ietf-mpls-bundle-04.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 8bit

All,

it is my understanding that there has been some hick-ups on
the is-is list, so I'm re-issueing this last call and extending
the time to September 29th. At the same time I would like point out
that there is an acompanying mib draft-ietf-mpls-bundle-mib-03.txt.

Also comments on the mib is welcome.

BTW, thanks to those of you who already sent us comments :)

The wg last call on

  <draft-ietf-mpls-bundle-04.txt>
  <draft-ietf-mpls-bundle-mib-03.txt>

has been extended to September 29.

/Loa

Loa Andersson wrote:

> OSPF and IS-IS working groups, (mpls wg for info)
> 
> the iesg has started the review of the mpls working group draft
> draft-ietf-mpls-bundle-04.txt. The immediate response from the iesg
> is that the draft contains OSPF and ISIS related details (see
> the included mail). After discussing with the wg chairs for ospf
> and is-is working groups, there is a feeling that the two weeks
> the iesg allocated for this last call might not be enough, since the
> draft has not been widely circulated in the routing working groups.
> 
> Therefore:
> 
> This is to initiate a last call for the
> 
> <draft-ietf-mpls-bundle-04.txt>
> 
> by the ospf and is-is working groups.
> The last call ends September 22nd at 12PM CET
> 
> 
> Please include the mpls mailing list (mpls@uu.net) in your responses.
> 
> /Loa (co-chair of the mpls wg)
> 
> -------- Original Message --------
> Subject: draft-ietf-mpls-bundle-04.txt
> Date: Tue, 27 Aug 2002 15:06:48 -0400 (EDT)
> From: Scott Bradner
> To: loa.andersson@utfors.se, swallow@cisco.com
> 
> 
> The IESG discussed this ID last week during its teleconference
> one issue was raised during the discussion
> 
> "the draft contains OSPF & ISIS
> related details and I don't remember it being LC'ed or reviewed
> in the corresponding WGs."
> 
> can you start a 2 week last call on the IS-IS and OSPF mailing
> lists for this document?
> 
> Scott
> 


-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     Råsundavägen 12
     Box 525, 169 29 Solna
     Office          +46 8 5270 2000
     Office direct   +46 8 5270 5038
     Mobile          +46 70 848 5038
     Email           loa.andersson@utfors.se
     WWW             www.utfors.se


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 17:06:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA16649
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 17:06:51 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89L5Hv31838;
	Mon, 9 Sep 2002 17:05:17 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89Ksov30973
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 16:54:50 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA16072
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 16:53:10 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74237@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'sarav_k@spymac.com'" <sarav_k@spymac.com>, isis-wg@ietf.org
Subject: RE: [Isis-wg] MTU lowering in IS-IS
Date: Mon, 9 Sep 2002 16:54:04 -0400 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

 
> Hello Everyone,
> 
> I have a question regarding how IS-IS should handle MTU 
> changes in the System. If i decrease the MTU size on a 
> interface to a value which will lower the current LSP buffer 
> size, then how should IS-IS handle this case ?
> 
>  Also how do we inform the IS's neighbours that the Buffer 
> Size in the Local IS has been lowered ? Does the padding of 
> the IIH packets help in this case?
> 
> Thanks,
> Sarav

Sarav -
	This is covered in the draft on interoperability.
There is a version of that draft at 
http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt
Take a look and let me know if that doesn't answer your questions:
it isn't too late to change it.  

	An updated version which splits this into 2 should appear
before long: this issue will be addressed in the pure ISO half.

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 19:21:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19188
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 19:21:05 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89NJcv06938;
	Mon, 9 Sep 2002 19:19:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89NECv06772
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 19:14:12 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19030
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 19:12:31 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17oXj6-00036B-00
	for <isis-wg@ietf.org>; Mon, 09 Sep 2002 16:13:52 -0700
Date: Mon, 09 Sep 2002 16:13:52 -0700
Message-ID: <87fzwiu573.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: isis-wg@ietf.org
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] isisISAdjState
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

Hi Jeff,

One question about isisISAdjState.

What is the intention of '0' as 'up' state like below in -09 draft.

    isisISAdjState OBJECT-TYPE
        SYNTAX INTEGER
            {
                 up (0),
                 initializing (1),
                 down (2),
                 failed (3)
            }
        MAX-ACCESS read-only
        STATUS current
        DESCRIPTION
            "The state of the adjacency"
        REFERENCE "{ISIS.aoi adjacencyState (78)}"
    ::= { isisISAdjEntry 2 }

For me, '0' as down is reasonable because usually the state is changing
from down(0), initializing(1) and then up(2).

    isisISAdjState OBJECT-TYPE
        SYNTAX INTEGER
            {
                 down (0),
                 initializing (1),
                 up (2),
                 failed (3)
            }
        MAX-ACCESS read-only
        STATUS current
        DESCRIPTION
            "The state of the adjacency"
        REFERENCE "{ISIS.aoi adjacencyState (78)}"
    ::= { isisISAdjEntry 2 }

Thank you,

								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 19:59:45 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19782
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 19:59:45 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89Nw6v08559;
	Mon, 9 Sep 2002 19:58:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g89NqZv08436
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 19:52:35 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA19655
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 19:50:54 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74243@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Noguchi Kay'" <kay@ipinfusion.com>, isis-wg@ietf.org
Subject: RE: [Isis-wg] isisISAdjState
Date: Mon, 9 Sep 2002 19:51:45 -0400 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

> Hi Jeff,
> 
> One question about isisISAdjState.
> 
> What is the intention of '0' as 'up' state like below in -09 draft.
> 
>     isisISAdjState OBJECT-TYPE
>         SYNTAX INTEGER
>             {
>                  up (0),
>                  initializing (1),
>                  down (2),
>                  failed (3)
>             }
....
>     ::= { isisISAdjEntry 2 }
> 
> For me, '0' as down is reasonable because usually the state 
> is changing
> from down(0), initializing(1) and then up(2).

Kay -
	That would seem like a natural order.  I recently
(two or three drafts ago) changed the values to match 
those in <draft-ietf-isis-3way>, shown below.  It was
thought that that would make it simpler for implementors
and observers to match the bits on the wire with the bits
in the MIB.

- jeff parker
- axiowave networks

   Adjacency Three-Way State
      The adjacency three-way state of the point-to-point adjacency. The
      following values are defined:
            0  - Up
            1 -  Initializing
            2 -  Down
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 20:14:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20091
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 20:14:20 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A0Cnv09697;
	Mon, 9 Sep 2002 20:12:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A07Yv09505
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 20:07:34 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19885
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 20:05:53 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17oYYs-00037o-00
	for <isis-wg@ietf.org>; Mon, 09 Sep 2002 17:07:22 -0700
Date: Mon, 09 Sep 2002 17:07:22 -0700
Message-ID: <87d6rmu2px.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: isis-wg@ietf.org
Subject: Re: [Isis-wg] isisISAdjState
In-Reply-To: <EB5FFC72F183D411B38200062957342902A74243@r2d2.axiowave.com>
References: <EB5FFC72F183D411B38200062957342902A74243@r2d2.axiowave.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>

Hi Dave and Jeff,

> > Hi Jeff,
> > 
> > One question about isisISAdjState.
> > 
> > What is the intention of '0' as 'up' state like below in -09 draft.
> > 
> >     isisISAdjState OBJECT-TYPE
> >         SYNTAX INTEGER
> >             {
> >                  up (0),
> >                  initializing (1),
> >                  down (2),
> >                  failed (3)
> >             }
> ....
> >     ::= { isisISAdjEntry 2 }
> > 
> > For me, '0' as down is reasonable because usually the state 
> > is changing
> > from down(0), initializing(1) and then up(2).
> 
> Kay -
> 	That would seem like a natural order.  I recently
> (two or three drafts ago) changed the values to match 
> those in <draft-ietf-isis-3way>, shown below.  It was
> thought that that would make it simpler for implementors
> and observers to match the bits on the wire with the bits
> in the MIB.

>    Adjacency Three-Way State
>       The adjacency three-way state of the point-to-point adjacency. The
>       following values are defined:
>             0  - Up
>             1 -  Initializing
>             2 -  Down

	Okay, then Dave, what is the intention of the '0' as 'up' state
	in the Adjacency three-way state?

	Maybe we can't change this point because of backward compatibility
	but please tell me the intention.

								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 20:40:32 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20730
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 20:40:32 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A0WYv10666;
	Mon, 9 Sep 2002 20:32:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A0Rdv10451
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 20:27:39 -0400
Received: from ghostrider.gredler.at (ghostrider.gredler.at [193.83.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA20275
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 20:25:56 -0400 (EDT)
Received: (from hannes@localhost)
	by ghostrider.gredler.at (8.11.6/8.11.6) id g8A0QpE07337;
	Tue, 10 Sep 2002 02:26:51 +0200
From: Hannes Gredler <hannes@juniper.net>
To: Noguchi Kay <kay@ipinfusion.com>
Cc: isis-wg@ietf.org
Subject: Re: [Isis-wg] isisISAdjState
Message-ID: <20020910002651.GA7322@juniper.net>
References: <87fzwiu573.wl@ipinfusion.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87fzwiu573.wl@ipinfusion.com>
User-Agent: Mutt/1.3.28i
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 10 Sep 2002 02:26:51 +0200

noguchi,

the MIB reflects the adjacency states that are
conveyed in TLV #240; [see 3-way handshaking draft]

/hannes

On Mon, Sep 09, 2002 at 04:13:52PM -0700, Noguchi Kay wrote:
| Hi Jeff,
| 
| One question about isisISAdjState.
| 
| What is the intention of '0' as 'up' state like below in -09 draft.
| 
|     isisISAdjState OBJECT-TYPE
|         SYNTAX INTEGER
|             {
|                  up (0),
|                  initializing (1),
|                  down (2),
|                  failed (3)
|             }
|         MAX-ACCESS read-only
|         STATUS current
|         DESCRIPTION
|             "The state of the adjacency"
|         REFERENCE "{ISIS.aoi adjacencyState (78)}"
|     ::= { isisISAdjEntry 2 }
| 
| For me, '0' as down is reasonable because usually the state is changing
| from down(0), initializing(1) and then up(2).
| 
|     isisISAdjState OBJECT-TYPE
|         SYNTAX INTEGER
|             {
|                  down (0),
|                  initializing (1),
|                  up (2),
|                  failed (3)
|             }
|         MAX-ACCESS read-only
|         STATUS current
|         DESCRIPTION
|             "The state of the adjacency"
|         REFERENCE "{ISIS.aoi adjacencyState (78)}"
|     ::= { isisISAdjEntry 2 }
| 
| Thank you,

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep  9 22:55:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23366
	for <isis-archive@lists.ietf.org>; Mon, 9 Sep 2002 22:55:24 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A2mZv17882;
	Mon, 9 Sep 2002 22:48:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8A2hJv17734
	for <isis-wg@optimus.ietf.org>; Mon, 9 Sep 2002 22:43:19 -0400
Received: from merlot.juniper.net (natint.juniper.net [207.17.136.129])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA23146
	for <isis-wg@ietf.org>; Mon, 9 Sep 2002 22:41:36 -0400 (EDT)
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 g8A2gkm25138;
	Mon, 9 Sep 2002 19:42:46 -0700 (PDT)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost)
	by cirrus.juniper.net (8.11.6/8.11.6) id g8A2gk547646;
	Mon, 9 Sep 2002 19:42:46 -0700 (PDT)
	(envelope-from dkatz@cirrus.juniper.net)
Message-Id: <200209100242.g8A2gk547646@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: kay@ipinfusion.com
CC: isis-wg@ietf.org
In-reply-to: <87d6rmu2px.wl@ipinfusion.com> (message from Noguchi Kay on Mon,
	09 Sep 2002 17:07:22 -0700)
Subject: Re: [Isis-wg] isisISAdjState
References: <EB5FFC72F183D411B38200062957342902A74243@r2d2.axiowave.com> <87d6rmu2px.wl@ipinfusion.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 9 Sep 2002 19:42:46 -0700 (PDT)

	   Okay, then Dave, what is the intention of the '0' as 'up' state
	   in the Adjacency three-way state?

The choice of 0 as "up" is lost in the haze;  I think this goes back to
when I was at my previous employer, so it's probably close to six years
now (!).

My suspicion is that I used these code points because it was compatible
with NLSP (the IPX ISIS lookalike) from which the three-way handshake was
stolen in the first place.  NLSP in turn used these code points because
(if memory serves) Neal used a couple of unused bits in the IIH header
and making 0 = up provided backward compatibility.  Such are the twisted
paths of protocol history.

(A much better one is why IPX delays are in units of 55 msec, but you
have to be of a certain age to know the answer.)

	   Maybe we can't change this point because of backward compatibility
	   but please tell me the intention.

See the "six years" comment above.  Can't exactly change it now.

--Dave
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 10 07:58:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09935
	for <isis-archive@lists.ietf.org>; Tue, 10 Sep 2002 07:58:49 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ABv2v19040;
	Tue, 10 Sep 2002 07:57:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ABpmv18866
	for <isis-wg@optimus.ietf.org>; Tue, 10 Sep 2002 07:51:48 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09779
	for <isis-wg@ietf.org>; Tue, 10 Sep 2002 07:50:05 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2800K9Y0YKDZ@mta2.huawei.com> for isis-wg@ietf.org;
 Tue, 10 Sep 2002 19:51:56 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2800KGW0YJMM@mta2.huawei.com> for isis-wg@ietf.org;
 Tue, 10 Sep 2002 19:51:56 +0800 (CST)
Received: from huaweisarav ([10.18.4.64])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H280ZZ00.80O for <isis-wg@ietf.org>; Tue,
 10 Sep 2002 19:52:47 +0800
From: Saravana Kumar <saravanak@huawei.com>
To: isis <isis-wg@ietf.org>
Message-id: <035701c258c0$8f1ad260$4004120a@huaweisarav>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
Content-Transfer-Encoding: 7BIT
Subject: [Isis-wg] Selectively Ignoring Hello PDU's
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 10 Sep 2002 17:22:37 +0530
Content-Transfer-Encoding: 7BIT

Hi Everyone,

Is there a way for a router(A) to send out Hello PDU's such that they are
processed by only a subset of its neighbors who support a particular new
feature ( restart, for instance) and the rest of its neighbors just ignore
the Hello PDU and do not refresh/re-initialize the adjacency with the
router(A)

One easy way i can think of is to change the value in the protocols
supported TLV to some new value which is recognized only by the routers
supporting the new feature and not by the older generation routers.

Is this feasible (if so, what value of NLPID should be used ?) or is there
any other way in which i can acheive the selective ignoring of hello PDU's.

Thanks,
Sarav

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 10 09:39:31 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13471
	for <isis-archive@lists.ietf.org>; Tue, 10 Sep 2002 09:39:31 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ADbYv24595;
	Tue, 10 Sep 2002 09:37:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ADWCv23899
	for <isis-wg@optimus.ietf.org>; Tue, 10 Sep 2002 09:32:12 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA13133
	for <isis-wg@ietf.org>; Tue, 10 Sep 2002 09:30:28 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2800K9T5LUDZ@mta2.huawei.com> for isis-wg@ietf.org;
 Tue, 10 Sep 2002 21:32:19 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2800KVO5LTMM@mta2.huawei.com> for isis-wg@ietf.org;
 Tue, 10 Sep 2002 21:32:18 +0800 (CST)
Received: from huaweisarav ([10.18.4.64])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H285NA01.B0M; Tue, 10 Sep 2002 21:33:10 +0800
From: Saravana Kumar <saravanak@huawei.com>
Subject: Re: [Isis-wg] MTU lowering in IS-IS
To: Jeff Parker <jparker@axiowave.com>, sarav_k@spymac.com, isis-wg@ietf.org
Message-id: <03b501c258ce$94bda900$4004120a@huaweisarav>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <EB5FFC72F183D411B38200062957342902A74237@r2d2.axiowave.com>
Content-Transfer-Encoding: 7BIT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 10 Sep 2002 19:03:00 +0530
Content-Transfer-Encoding: 7BIT

Hi Jeff,

After looking into the draft, i've got one basic question, should'nt
ReceiveLSPBufferSize be less than ( or equal to ) the minimum of the Link
MTUs of all the circuitsin the router ?  Otherwise how will the router
receive LSPs through a circuit whose MTU is smaller than the LSP size.

Thanks,
Sarav

----- Original Message -----
From: "Jeff Parker" <jparker@axiowave.com>
To: <sarav_k@spymac.com>; <isis-wg@ietf.org>
Sent: Tuesday, September 10, 2002 2:24 AM
Subject: RE: [Isis-wg] MTU lowering in IS-IS


>
> > Hello Everyone,
> >
> > I have a question regarding how IS-IS should handle MTU
> > changes in the System. If i decrease the MTU size on a
> > interface to a value which will lower the current LSP buffer
> > size, then how should IS-IS handle this case ?
> >
> >  Also how do we inform the IS's neighbours that the Buffer
> > Size in the Local IS has been lowered ? Does the padding of
> > the IIH packets help in this case?
> >
> > Thanks,
> > Sarav
>
> Sarav -
> This is covered in the draft on interoperability.
> There is a version of that draft at
> http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt
> Take a look and let me know if that doesn't answer your questions:
> it isn't too late to change it.
>
> An updated version which splits this into 2 should appear
> before long: this issue will be addressed in the pure ISO half.
>
> - jeff parker
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 10 10:03:38 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14653
	for <isis-archive@lists.ietf.org>; Tue, 10 Sep 2002 10:03:37 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ADxEv25309;
	Tue, 10 Sep 2002 09:59:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ADsCv25156
	for <isis-wg@optimus.ietf.org>; Tue, 10 Sep 2002 09:54:12 -0400
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14209
	for <isis-wg@ietf.org>; Tue, 10 Sep 2002 09:52:29 -0400 (EDT)
Received: (truskows@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id GAA26106; Tue, 10 Sep 2002 06:52:17 -0700 (PDT)
From: Mike Truskowski <truskows@cisco.com>
Message-Id: <200209101352.GAA26106@wells.cisco.com>
Subject: Re: [Isis-wg] MTU lowering in IS-IS
To: saravanak@huawei.com
Cc: jparker@axiowave.com, sarav_k@spymac.com, isis-wg@ietf.org
In-Reply-To: <03b501c258ce$94bda900$4004120a@huaweisarav> from Saravana Kumar at Sep "10," 2002 "07:03:00" pm
X-Mailer: ELM []
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 10 Sep 2002 06:52:17 -0700 (PDT)
Content-Transfer-Encoding: 7bit

How will it receive the largest MTU size if it's less than or equal
to the smallest?

Are we bit fiddling with  something that works or trying to fix
something that does not work?

Mike

> Hi Jeff,
> 
> After looking into the draft, i've got one basic question, should'nt
> ReceiveLSPBufferSize be less than ( or equal to ) the minimum of the Link
> MTUs of all the circuitsin the router ?  Otherwise how will the router
> receive LSPs through a circuit whose MTU is smaller than the LSP size.
> 
> Thanks,
> Sarav
> 
> ----- Original Message -----
> From: "Jeff Parker" <jparker@axiowave.com>
> To: <sarav_k@spymac.com>; <isis-wg@ietf.org>
> Sent: Tuesday, September 10, 2002 2:24 AM
> Subject: RE: [Isis-wg] MTU lowering in IS-IS
> 
> 
> >
> > > Hello Everyone,
> > >
> > > I have a question regarding how IS-IS should handle MTU
> > > changes in the System. If i decrease the MTU size on a
> > > interface to a value which will lower the current LSP buffer
> > > size, then how should IS-IS handle this case ?
> > >
> > >  Also how do we inform the IS's neighbours that the Buffer
> > > Size in the Local IS has been lowered ? Does the padding of
> > > the IIH packets help in this case?
> > >
> > > Thanks,
> > > Sarav
> >
> > Sarav -
> > This is covered in the draft on interoperability.
> > There is a version of that draft at
> > http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt
> > Take a look and let me know if that doesn't answer your questions:
> > it isn't too late to change it.
> >
> > An updated version which splits this into 2 should appear
> > before long: this issue will be addressed in the pure ISO half.
> >
> > - jeff parker
> > _______________________________________________
> > Isis-wg mailing list
> > Isis-wg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/isis-wg
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> 

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 10 10:47:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16356
	for <isis-archive@lists.ietf.org>; Tue, 10 Sep 2002 10:47:55 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8AEjcv28208;
	Tue, 10 Sep 2002 10:45:38 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8AEcqv27953
	for <isis-wg@optimus.ietf.org>; Tue, 10 Sep 2002 10:38:52 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15897
	for <isis-wg@ietf.org>; Tue, 10 Sep 2002 10:37:09 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A7424B@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Saravana Kumar'" <saravanak@huawei.com>,
        Jeff Parker
	 <jparker@axiowave.com>, sarav_k@spymac.com,
        isis-wg@ietf.org
Subject: RE: [Isis-wg] MTU lowering in IS-IS
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 10 Sep 2002 10:38:00 -0400

> Hi Jeff,
> 
> After looking into the draft, i've got one basic question, should'nt
> ReceiveLSPBufferSize be less than ( or equal to ) the minimum 
> of the Link
> MTUs of all the circuitsin the router ?  Otherwise how will the router
> receive LSPs through a circuit whose MTU is smaller than the LSP size.
> 
> Thanks,
> Sarav

Sarav -
	Did you mean the maximum rather than the minimum?  

	Do you mean the maximum of your current interfaces/  How
do you deal with migrating a configuration to deal with new 
interfaces that support a larger MTU?

	The area is rich with possibilities of missconfiguration,
leading to odd behavior and generalized frustration.  I think
the steps outlined in the draft provide one algorithm to deal
with this.  Please let me know if you see a flaw.

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 10 23:54:52 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04157
	for <isis-archive@lists.ietf.org>; Tue, 10 Sep 2002 23:54:51 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B3oev09596;
	Tue, 10 Sep 2002 23:50:41 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8B3lIv09513
	for <isis-wg@optimus.ietf.org>; Tue, 10 Sep 2002 23:47:18 -0400
Received: from ghostrider.gredler.at (ghostrider.gredler.at [193.83.223.228])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04061
	for <isis-wg@ietf.org>; Tue, 10 Sep 2002 23:45:27 -0400 (EDT)
Received: (from hannes@localhost)
	by ghostrider.gredler.at (8.11.6/8.11.6) id g8B3kSa21641;
	Wed, 11 Sep 2002 05:46:28 +0200
From: Hannes Gredler <hannes@juniper.net>
To: Saravana Kumar <saravanak@huawei.com>
Cc: isis <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Selectively Ignoring Hello PDU's
Message-ID: <20020911034628.GA21628@juniper.net>
References: <035701c258c0$8f1ad260$4004120a@huaweisarav>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <035701c258c0$8f1ad260$4004120a@huaweisarav>
User-Agent: Mutt/1.3.28i
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 11 Sep 2002 05:46:28 +0200

On Tue, Sep 10, 2002 at 05:22:37PM +0530, Saravana Kumar wrote:
| Hi Everyone,
| 
| Is there a way for a router(A) to send out Hello PDU's such that they are
| processed by only a subset of its neighbors who support a particular new
| feature ( restart, for instance) and the rest of its neighbors just ignore
| the Hello PDU and do not refresh/re-initialize the adjacency with the
| router(A)
| 
| One easy way i can think of is to change the value in the protocols
| supported TLV to some new value which is recognized only by the routers
| supporting the new feature and not by the older generation routers.
| 
| Is this feasible (if so, what value of NLPID should be used ?) or is there
| any other way in which i can acheive the selective ignoring of hello PDU's.

sarav,

you may want look into the multi-topology draft to see if it fits
your purpose; - squeezing tlv 129 is clearly the wrong place for
your "application";

/hannes
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 11 13:46:13 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18598
	for <isis-archive@lists.ietf.org>; Wed, 11 Sep 2002 13:46:13 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHgav31745;
	Wed, 11 Sep 2002 13:42:37 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8BHdDv31591
	for <isis-wg@optimus.ietf.org>; Wed, 11 Sep 2002 13:39:13 -0400
Received: from titanium (mail.ipinfusion.com [65.223.109.2])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18134
	for <isis-wg@ietf.org>; Wed, 11 Sep 2002 13:37:28 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17pBRl-0001PA-00; Wed, 11 Sep 2002 10:38:37 -0700
Message-ID: <87it1cv337.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: isis-wg@ietf.org
cc: kay@ipinfusion.com
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Subject: [Isis-wg] isisCircLevelID
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 11 Sep 2002 10:38:36 -0700

Hi Jeff,

Just let me clarify about isisCircLevelID.

As REFERENCE suggested, ptPtCircuitID, is this mib, isisCircLevelID,
only for point-to-point circuit only?

If so, why don't you put some comments like,
"This object is point to point only." in DESCRIPTION?

Thank you,

    isisCircLevelID OBJECT-TYPE
        SYNTAX CircuitID
        MAX-ACCESS read-only
        STATUS current
        DESCRIPTION
            "The ID of the circuit allocated during initialization.
             If no value has been negotiated (either because the
             adjacency is to an End System, or because initialization
             has not yet successfully completed), this object has the
             value which would be proposed for this circuit (i.e. the
             concatenation of the local system ID and the one byte
             isisCircLevelIDOctet for this circuit."
        REFERENCE "{ISIS.aoi ptPtCircuitID (51)}"
    ::= { isisCircLevelEntry 6 }

								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 12 01:29:34 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04208
	for <isis-archive@lists.ietf.org>; Thu, 12 Sep 2002 01:29:34 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8C5Nnv03216;
	Thu, 12 Sep 2002 01:23:49 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8C5Kxv03146
	for <isis-wg@optimus.ietf.org>; Thu, 12 Sep 2002 01:20:59 -0400
Received: from xover.netplane.com (fwout.maker.com [12.27.183.253] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA04049
	for <isis-wg@ietf.org>; Thu, 12 Sep 2002 01:19:07 -0400 (EDT)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <S1D0A9VP>; Thu, 12 Sep 2002 01:20:19 -0400
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328560E81@india_exch.hyderabad.mindspeed.com>
From: "Ramalingam, Swaminathan" <swaminathanr@netplane.com>
To: "'Noguchi Kay'" <kay@ipinfusion.com>, isis-wg@ietf.org
Subject: RE: [Isis-wg] isisCircLevelID
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@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 12 Sep 2002 01:22:18 -0400

Noguchi,
Though the reference is PTP ciruit ID, it can be used for both bcast and
PTP.
In broadcast case , it will be (DIS sys ID + one octet DIS Psuedonode ID)
and in PTP case, it should be used as described in section 8.2.4.2 IIH PDU
PROCESSING (92 version spec).

Swami

>-----Original Message-----
>From: Noguchi Kay [mailto:kay@ipinfusion.com]
>Sent: Wednesday, September 11, 2002 11:09 PM
>To: isis-wg@ietf.org
>Cc: kay@ipinfusion.com
>Subject: [Isis-wg] isisCircLevelID
>
>
>Hi Jeff,
>
>Just let me clarify about isisCircLevelID.
>
>As REFERENCE suggested, ptPtCircuitID, is this mib, isisCircLevelID,
>only for point-to-point circuit only?
>
>If so, why don't you put some comments like,
>"This object is point to point only." in DESCRIPTION?
>
>Thank you,
>
>    isisCircLevelID OBJECT-TYPE
>        SYNTAX CircuitID
>        MAX-ACCESS read-only
>        STATUS current
>        DESCRIPTION
>            "The ID of the circuit allocated during initialization.
>             If no value has been negotiated (either because the
>             adjacency is to an End System, or because initialization
>             has not yet successfully completed), this object has the
>             value which would be proposed for this circuit (i.e. the
>             concatenation of the local system ID and the one byte
>             isisCircLevelIDOctet for this circuit."
>        REFERENCE "{ISIS.aoi ptPtCircuitID (51)}"
>    ::= { isisCircLevelEntry 6 }
>
>								kay
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg
>
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 16 05:25:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29059
	for <isis-archive@lists.ietf.org>; Mon, 16 Sep 2002 05:25:27 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8G9JSv18379;
	Mon, 16 Sep 2002 05:19:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8G9FIv18273
	for <isis-wg@optimus.ietf.org>; Mon, 16 Sep 2002 05:15:18 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28855
	for <isis-wg@ietf.org>; Mon, 16 Sep 2002 05:13:26 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2I00I4TXPM42@mta2.huawei.com> for isis-wg@ietf.org;
 Mon, 16 Sep 2002 17:15:23 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2I00IXTXPLC7@mta2.huawei.com> for isis-wg@ietf.org;
 Mon, 16 Sep 2002 17:15:22 +0800 (CST)
Received: from huaweisarav ([10.18.4.81])
 by mailin.huawei.com (Netscape Messaging Server 4.15)
 with ESMTP id H2IXR201.D0X; Mon, 16 Sep 2002 17:16:14 +0800
From: Saravana Kumar <saravanak@huawei.com>
Subject: Re: [Isis-wg] Selectively Ignoring Hello PDU's
To: Hannes Gredler <hannes@juniper.net>
Cc: isis <isis-wg@ietf.org>, mshand@cisco.com
Message-id: <003401c25d61$af410500$5104120a@huaweisarav>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
X-Mailer: Microsoft Outlook Express 5.00.2919.6700
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <035701c258c0$8f1ad260$4004120a@huaweisarav>
 <20020911034628.GA21628@juniper.net>
Content-Transfer-Encoding: 7BIT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 16 Sep 2002 14:46:04 +0530
Content-Transfer-Encoding: 7BIT

Hannes, Everyone..

First of all, sorry for the late reply, been away from my mail for a while.
Going back to the business at hand, I dont think that the muti-topology
draft is the place to find answers to the requirements for my "application".

Guess i should explain the "application" first and ask questions later. One
of the big challenges for a restarting router is to successfully re-acquire
all its adjacencies without disturbing the area. If any one of the
restarting routers neighbors does not support the restart signalling
feature, then it will re-intializse its adjacency with the restarting router
and flood new LSPs throught the area/domain.

If the restarting router can somehow backup information about its
adjacencies with one of its neighbors, it can later use that information to
re-acquire all its adjacencies without disturbing the network.

So, now when the restarting router comes up, the first step is to retrive
the adjacency information from its neighbor. It doesnt know to which
neighbor it has given the information to, so the restarting router should
send a special hello PDU (with RR bit set) and the neighbor should reply
with a hello PDU (RA bit set) containing the backup information (by
including sub-TLL's in the restart TLV) . All the other neighbor routers
which do not support the restart feature should ignore the hello PDU (so
that they dont reset the adjacency and flood new LSPs through the domain).
The restarting router can now use the adjacency information to generate
hello PDU's on each circuit which are exactly similar to the Hello PDU's
that it generated over the circuit before it restarted.

so, now going back to the original question, how do i ensure that the old
routers which do not support the restart feature would ignore the hello PDU
and not re-initialize the adjacency. Squeezing TLV 129 is one way i can
think of right now. Let me know what problems you foresee in that mechanism
and if there are any alternatives.

Thanks,
Sarav

> On Tue, Sep 10, 2002 at 05:22:37PM +0530, Saravana Kumar wrote:
> | Hi Everyone,
> |
> | Is there a way for a router(A) to send out Hello PDU's such that they
are
> | processed by only a subset of its neighbors who support a particular new
> | feature ( restart, for instance) and the rest of its neighbors just
ignore
> | the Hello PDU and do not refresh/re-initialize the adjacency with the
> | router(A)
> |
> | One easy way i can think of is to change the value in the protocols
> | supported TLV to some new value which is recognized only by the routers
> | supporting the new feature and not by the older generation routers.
> |
> | Is this feasible (if so, what value of NLPID should be used ?) or is
there
> | any other way in which i can acheive the selective ignoring of hello
PDU's.
>
> sarav,
>
> you may want look into the multi-topology draft to see if it fits
> your purpose; - squeezing tlv 129 is clearly the wrong place for
> your "application";
>
> /hannes
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 16 05:34:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29181
	for <isis-archive@lists.ietf.org>; Mon, 16 Sep 2002 05:34:53 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8G9UFv19043;
	Mon, 16 Sep 2002 05:30:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8G9RFv18959
	for <isis-wg@optimus.ietf.org>; Mon, 16 Sep 2002 05:27:15 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA29073
	for <isis-wg@ietf.org>; Mon, 16 Sep 2002 05:25:28 -0400 (EDT)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp195.cisco.com [10.50.0.194])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA07507;
	Mon, 16 Sep 2002 10:26:27 +0100 (BST)
Message-Id: <4.3.2.7.2.20020916102222.0478ce50@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Saravana Kumar <saravanak@huawei.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] Selectively Ignoring Hello PDU's
Cc: Hannes Gredler <hannes@juniper.net>, isis <isis-wg@ietf.org>
In-Reply-To: <003401c25d61$af410500$5104120a@huaweisarav>
References: <035701c258c0$8f1ad260$4004120a@huaweisarav>
 <20020911034628.GA21628@juniper.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 16 Sep 2002 10:26:25 +0100

How do you plan to ensure that the restarting router can correctly 
synchronize its LSP database with the non-cooperating router?

BTW, I don't think there is a way to make the hello be ignored without a 
protocol change in the non-cooperating router, other than sending it a 
"correct" hello in the first place :-)

         Mike

At 14:46 16/09/2002 +0530, Saravana Kumar wrote:
>Hannes, Everyone..
>
>First of all, sorry for the late reply, been away from my mail for a while.
>Going back to the business at hand, I dont think that the muti-topology
>draft is the place to find answers to the requirements for my "application".
>
>Guess i should explain the "application" first and ask questions later. One
>of the big challenges for a restarting router is to successfully re-acquire
>all its adjacencies without disturbing the area. If any one of the
>restarting routers neighbors does not support the restart signalling
>feature, then it will re-intializse its adjacency with the restarting router
>and flood new LSPs throught the area/domain.
>
>If the restarting router can somehow backup information about its
>adjacencies with one of its neighbors, it can later use that information to
>re-acquire all its adjacencies without disturbing the network.
>
>So, now when the restarting router comes up, the first step is to retrive
>the adjacency information from its neighbor. It doesnt know to which
>neighbor it has given the information to, so the restarting router should
>send a special hello PDU (with RR bit set) and the neighbor should reply
>with a hello PDU (RA bit set) containing the backup information (by
>including sub-TLL's in the restart TLV) . All the other neighbor routers
>which do not support the restart feature should ignore the hello PDU (so
>that they dont reset the adjacency and flood new LSPs through the domain).
>The restarting router can now use the adjacency information to generate
>hello PDU's on each circuit which are exactly similar to the Hello PDU's
>that it generated over the circuit before it restarted.
>
>so, now going back to the original question, how do i ensure that the old
>routers which do not support the restart feature would ignore the hello PDU
>and not re-initialize the adjacency. Squeezing TLV 129 is one way i can
>think of right now. Let me know what problems you foresee in that mechanism
>and if there are any alternatives.
>
>Thanks,
>Sarav
>
> > On Tue, Sep 10, 2002 at 05:22:37PM +0530, Saravana Kumar wrote:
> > | Hi Everyone,
> > |
> > | Is there a way for a router(A) to send out Hello PDU's such that they
>are
> > | processed by only a subset of its neighbors who support a particular new
> > | feature ( restart, for instance) and the rest of its neighbors just
>ignore
> > | the Hello PDU and do not refresh/re-initialize the adjacency with the
> > | router(A)
> > |
> > | One easy way i can think of is to change the value in the protocols
> > | supported TLV to some new value which is recognized only by the routers
> > | supporting the new feature and not by the older generation routers.
> > |
> > | Is this feasible (if so, what value of NLPID should be used ?) or is
>there
> > | any other way in which i can acheive the selective ignoring of hello
>PDU's.
> >
> > sarav,
> >
> > you may want look into the multi-topology draft to see if it fits
> > your purpose; - squeezing tlv 129 is clearly the wrong place for
> > your "application";
> >
> > /hannes
> > _______________________________________________
> > Isis-wg mailing list
> > Isis-wg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 16 10:34:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06664
	for <isis-archive@lists.ietf.org>; Mon, 16 Sep 2002 10:34:07 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GETVv02154;
	Mon, 16 Sep 2002 10:29:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GEPBv01973
	for <isis-wg@optimus.ietf.org>; Mon, 16 Sep 2002 10:25:11 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06209
	for <isis-wg@ietf.org>; Mon, 16 Sep 2002 10:23:23 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A742F2@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Saravana Kumar'" <saravanak@huawei.com>,
        Mike Truskowski
	 <truskows@cisco.com>,
        Jeff Parker <jparker@axiowave.com>
Cc: sarav_k@spymac.com, isis-wg@ietf.org
Subject: RE: [Isis-wg] MTU lowering in IS-IS
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 16 Sep 2002 10:24:13 -0400

> Hi Mike, Jeff,
> 
> Sorry for my late reply.. as i've been away form my mail for a while.
> 
> I see both your points here. But my concern is with the 
> definition of the ReceiveLSPBufferSize, .... the  
> "size of the largest LSP we can receive". Is'nt
> it given that a router which receives a LSP on one 
> of its interface should flood it out through all 
> its other interfaces.
 
> > Are we bit fiddling with  something that works or trying to fix
> > something that does not work?
> >
> > Mike
 
Saravana -
	Three different answers to your question. 

	1) This doesn't break anything, so we don't need to fix it.
	An integer can be used to store an Enum that never gets close
	to MAXINT.  

	2) Be liberal in what you recieve ....

	3) If you are trying to change the MTU in a running network, 
	you will find that you need something like this variable as
	part of your transition.  

But what is your concern about this value?  Are you worried about
wasting fixed-size buffers?  Or that everything doesn't line up
perfectly?

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 16 14:48:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14146
	for <isis-archive@lists.ietf.org>; Mon, 16 Sep 2002 14:48:54 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GIkvv17029;
	Mon, 16 Sep 2002 14:46:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8GIhnv16973
	for <isis-wg@optimus.ietf.org>; Mon, 16 Sep 2002 14:43:49 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13907
	for <isis-wg@ietf.org>; Mon, 16 Sep 2002 14:41:59 -0400 (EDT)
Received: from net4u.ch (adsl-63-200-52-122.dsl.snfc21.pacbell.net [63.200.52.122])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g8GIh9j14390;
	Mon, 16 Sep 2002 20:43:09 +0200
Message-ID: <3D861F24.1020203@net4u.ch>
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: mike shand <mshand@cisco.com>
CC: Saravana Kumar <saravanak@huawei.com>,
        Hannes Gredler
 <hannes@juniper.net>, isis <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Selectively Ignoring Hello PDU's
References: <035701c258c0$8f1ad260$4004120a@huaweisarav> <20020911034628.GA21628@juniper.net> <4.3.2.7.2.20020916102222.0478ce50@jaws.cisco.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 16 Sep 2002 11:12:52 -0700
Content-Transfer-Encoding: 7bit

mike shand wrote:

> How do you plan to ensure that the restarting router can correctly 
> synchronize its LSP database with the non-cooperating router?
>
> BTW, I don't think there is a way to make the hello be ignored without 
> a protocol change in the non-cooperating router, other than sending it 
> a "correct" hello in the first place :-) 

yes, and I would be very reluctant (beside the practical problem that it 
would be impossible practically anyway) to
change the deployed protocol in existing routers.

Meanwhile, all kind of trick can be played and will work in some or most 
circumstances for the restart by storing adjacency
data, it may be however safest to wait for Mike's RFC for an 
interoperable, clean solution.

    thanks

    -- tony

>
>
>         Mike
>
> At 14:46 16/09/2002 +0530, Saravana Kumar wrote:
>
>> Hannes, Everyone..
>>
>> First of all, sorry for the late reply, been away from my mail for a 
>> while.
>> Going back to the business at hand, I dont think that the muti-topology
>> draft is the place to find answers to the requirements for my 
>> "application".
>>
>> Guess i should explain the "application" first and ask questions 
>> later. One
>> of the big challenges for a restarting router is to successfully 
>> re-acquire
>> all its adjacencies without disturbing the area. If any one of the
>> restarting routers neighbors does not support the restart signalling
>> feature, then it will re-intializse its adjacency with the restarting 
>> router
>> and flood new LSPs throught the area/domain.
>>
>> If the restarting router can somehow backup information about its
>> adjacencies with one of its neighbors, it can later use that 
>> information to
>> re-acquire all its adjacencies without disturbing the network.
>>
>> So, now when the restarting router comes up, the first step is to 
>> retrive
>> the adjacency information from its neighbor. It doesnt know to which
>> neighbor it has given the information to, so the restarting router 
>> should
>> send a special hello PDU (with RR bit set) and the neighbor should reply
>> with a hello PDU (RA bit set) containing the backup information (by
>> including sub-TLL's in the restart TLV) . All the other neighbor routers
>> which do not support the restart feature should ignore the hello PDU (so
>> that they dont reset the adjacency and flood new LSPs through the 
>> domain).
>> The restarting router can now use the adjacency information to generate
>> hello PDU's on each circuit which are exactly similar to the Hello PDU's
>> that it generated over the circuit before it restarted.
>>
>> so, now going back to the original question, how do i ensure that the 
>> old
>> routers which do not support the restart feature would ignore the 
>> hello PDU
>> and not re-initialize the adjacency. Squeezing TLV 129 is one way i can
>> think of right now. Let me know what problems you foresee in that 
>> mechanism
>> and if there are any alternatives.
>>
>> Thanks,
>> Sarav
>>
>> > On Tue, Sep 10, 2002 at 05:22:37PM +0530, Saravana Kumar wrote:
>> > | Hi Everyone,
>> > |
>> > | Is there a way for a router(A) to send out Hello PDU's such that 
>> they
>> are
>> > | processed by only a subset of its neighbors who support a 
>> particular new
>> > | feature ( restart, for instance) and the rest of its neighbors just
>> ignore
>> > | the Hello PDU and do not refresh/re-initialize the adjacency with 
>> the
>> > | router(A)
>> > |
>> > | One easy way i can think of is to change the value in the protocols
>> > | supported TLV to some new value which is recognized only by the 
>> routers
>> > | supporting the new feature and not by the older generation routers.
>> > |
>> > | Is this feasible (if so, what value of NLPID should be used ?) or is
>> there
>> > | any other way in which i can acheive the selective ignoring of hello
>> PDU's.
>> >
>> > sarav,
>> >
>> > you may want look into the multi-topology draft to see if it fits
>> > your purpose; - squeezing tlv 129 is clearly the wrong place for
>> > your "application";
>> >
>> > /hannes
>> > _______________________________________________
>> > Isis-wg mailing list
>> > Isis-wg@ietf.org
>> > https://www1.ietf.org/mailman/listinfo/isis-wg
>
>
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
>
>



_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 17 05:21:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08341
	for <isis-archive@lists.ietf.org>; Tue, 17 Sep 2002 05:21:45 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8H8mXv32142;
	Tue, 17 Sep 2002 04:48:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8H8jDv32068
	for <isis-wg@optimus.ietf.org>; Tue, 17 Sep 2002 04:45:13 -0400
Received: from hal2.bizland-inc.net (mail2.bizland-inc.net [64.28.88.158])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07741
	for <isis-wg@ietf.org>; Tue, 17 Sep 2002 04:43:16 -0400 (EDT)
Received: from adsl-63-196-0-219.dsl.snfc21.pacbell.net ([63.196.0.219] helo=les.espsoft.com)
	by hal2.bizland-inc.net with asmtp (Exim 4.10)
	id 17rDy4-0005du-00; Tue, 17 Sep 2002 04:44:24 -0400
Message-Id: <5.1.0.14.0.20020917010658.00a1a9f0@pop.bizland.com>
X-Sender: espllc@pop.bizland.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: Saravana Kumar <saravanak@huawei.com>, Jeff Parker <jparker@axiowave.com>,
        sarav_k@spymac.com, isis-wg@ietf.org
From: Les Ginsberg <les@espsoft.com>
Subject: Re: [Isis-wg] MTU lowering in IS-IS
In-Reply-To: <03b501c258ce$94bda900$4004120a@huaweisarav>
References: <EB5FFC72F183D411B38200062957342902A74237@r2d2.axiowave.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Bizland-Abuse: This message was sent on behalf of a Bizland customer espllc -- Please report any abuse to abuse@bizland-inc.com
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 17 Sep 2002 01:46:20 -0700


(Coming to the party a little late...)

At 07:03 PM 9/10/02 +0530, Saravana Kumar wrote:
>Hi Jeff,
>
>After looking into the draft, i've got one basic question, should'nt
>ReceiveLSPBufferSize be less than ( or equal to ) the minimum of the Link
>MTUs of all the circuitsin the router ?  Otherwise how will the router
>receive LSPs through a circuit whose MTU is smaller than the LSP size.


The short answer to this question is "No".

When discussing this issue it is important to understand the functions of 
all the relevant parameters:

1)ReceiveLSPBufferSize - which defines the largest LSP which an 
implementation can expect to receive. This parameter also serves as an 
upper bound on the largest LSP which an implementation can be configured to 
generate. While it is desirable that ReceiveLSPBufferSize be set 
consistently on all routers, it is not required. It is also not a problem 
if ReceiveLSPBufferSize is larger than the MTU of some circuits on which 
LSPs are propagated. The obvious real world example of this is existing 
10589 conformant IS-IS implementations used in SONET networks. In this case 
ReceiveLSPBufferSize is 1492, but LAPD/DCC links have an MTU of 512. This 
is OK so long as originatingLxLSPBufferSize is set to 512 on all routers.

2)originatingLxLSPBufferSize - which defines the largest LSP which an 
implementation is allowed to generate. This parameter is subject to the 
following restrictions:

a)It MUST be >=512 AND <= ReceiveLSPBufferSize
b)It MUST be <= the minimum MTU of any circuit used to propagate LSPs in 
the area/domain
c)It SHOULD be consistent on all routers in the area/domain

While I would not recommend it, there would be no operational problem with 
the following configuration:

Router A:  ReceiveLSPBuffSize = 1492
                 originatingL1LSPBufferSize = 1492

Router B:  ReceiveLSPBuffSize = 4096
                originatingL1LSPBufferSize = 1492

I believe 
http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt does a 
good job of discussing this, but if people feel that some further 
clarification would be helpful, then perhaps some rewording can be done, 
though that discussion should take place within the isis-update sub-group.

As far as your original question

> > > I have a question regarding how IS-IS should handle MTU
> > > changes in the System. If i decrease the MTU size on a
> > > interface to a value which will lower the current LSP buffer
> > > size, then how should IS-IS handle this case ?


Strictly speaking, something which causes originatingLxLSPBufferSize to 
change in value requires a logical restart of the protocol. This is because 
it would likely require regeneration of all existing local LSPs. This is 
why draft-ietf-isis-wg-mib-09.txt associates 
the   "replaceOnlyWhileDisabled behavior" with this parameter. Existing 
implementations may, as a convenience to the user, allow changes to this 
parameter "on the fly", but that does not alter the fact that what must 
occur internally is equivalent to a protocol restart. This is especially 
true if one remembers that inconsistent settings of 
originatingLxLSPBufferSize in the area/domain can cause interoperability 
problems.

    Les


c)
>Thanks,
>Sarav
>
>----- Original Message -----
>From: "Jeff Parker" <jparker@axiowave.com>
>To: <sarav_k@spymac.com>; <isis-wg@ietf.org>
>Sent: Tuesday, September 10, 2002 2:24 AM
>Subject: RE: [Isis-wg] MTU lowering in IS-IS
>
>
> >
> > > Hello Everyone,
> > >
> > > I have a question regarding how IS-IS should handle MTU
> > > changes in the System. If i decrease the MTU size on a
> > > interface to a value which will lower the current LSP buffer
> > > size, then how should IS-IS handle this case ?
> > >
> > >  Also how do we inform the IS's neighbours that the Buffer
> > > Size in the Local IS has been lowered ? Does the padding of
> > > the IIH packets help in this case?
> > >
> > > Thanks,
> > > Sarav
> >
> > Sarav -
> > This is covered in the draft on interoperability.
> > There is a version of that draft at
> > http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt
> > Take a look and let me know if that doesn't answer your questions:
> > it isn't too late to change it.
> >
> > An updated version which splits this into 2 should appear
> > before long: this issue will be addressed in the pure ISO half.
> >
> > - jeff parker
> > _______________________________________________
> > Isis-wg mailing list
> > Isis-wg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/isis-wg
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 17 06:01:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA08965
	for <isis-archive@lists.ietf.org>; Tue, 17 Sep 2002 06:01:32 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8H9wlv03123;
	Tue, 17 Sep 2002 05:58:48 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8H9t5v03017
	for <isis-wg@optimus.ietf.org>; Tue, 17 Sep 2002 05:55:05 -0400
Received: from hal2.bizland-inc.net (mail2.bizland-inc.net [64.28.88.158])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08818
	for <isis-wg@ietf.org>; Tue, 17 Sep 2002 05:53:18 -0400 (EDT)
Received: from adsl-63-196-0-219.dsl.snfc21.pacbell.net ([63.196.0.219] helo=les.espsoft.com)
	by hal2.bizland-inc.net with asmtp (Exim 4.10)
	id 17rF3v-0003ZM-00; Tue, 17 Sep 2002 05:54:31 -0400
Message-Id: <5.1.0.14.0.20020917025054.00a21d10@pop.bizland.com>
X-Sender: espllc@pop.bizland.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: Saravana Kumar <saravanak@huawei.com>, Jeff Parker <jparker@axiowave.com>,
        sarav_k@spymac.com, isis-wg@ietf.org
From: Les Ginsberg <les@espsoft.com>
Subject: Re: [Isis-wg] MTU lowering in IS-IS
In-Reply-To: <003301c25e29$aab390c0$5104120a@huaweisarav>
References: <EB5FFC72F183D411B38200062957342902A74237@r2d2.axiowave.com>
 <5.1.0.14.0.20020917010658.00a1a9f0@pop.bizland.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Bizland-Abuse: This message was sent on behalf of a Bizland customer espllc -- Please report any abuse to abuse@bizland-inc.com
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 17 Sep 2002 02:56:27 -0700

At 02:37 PM 9/17/02 +0530, Saravana Kumar wrote:

> > 2)originatingLxLSPBufferSize - which defines the largest LSP which an
> > implementation is allowed to generate. This parameter is subject to the
> > following restrictions:
> >
> > a)It MUST be >=512 AND <= ReceiveLSPBufferSize
> > b)It MUST be <= the minimum MTU of any circuit used to propagate LSPs in
> > the area/domain
>
>
>We should add this restriction for the originatingLxLSPBufferSize in the
>interoperability draft, instead of stating that "for all Lx links in the
>area, originatingLxLSPBufferSize <= MTU"

I do not see any difference in (intended) meaning between the two 
statements. Perhaps it is a matter of clarity of wording. If so, we can 
certainly revise the wording of the draft - but this is not "adding" 
anything other than clarity. This is what we always meant to say.

Jeff P - consider this as a proposed revision to the draft.

     Les

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 08:12:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09601
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 08:12:12 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IC8fv29729;
	Wed, 18 Sep 2002 08:08:42 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IBwAv28808
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 07:58:10 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09135;
	Wed, 18 Sep 2002 07:56:20 -0400 (EDT)
Message-Id: <200209181156.HAA09135@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: isis-wg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-auto-encap-02.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 07:56:19 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title		: IS-IS Automatic Encapsulation
	Author(s)	: P. Christian
	Filename	: draft-ietf-isis-auto-encap-02.txt
	Pages		: 23
	Date		: 2002-9-17
	
RFC 1195 [1] documents a dual routing protocol that can be used to 
route both CLNP and IPv4, that is Integrated IS-IS.   Integrated IS-
IS can now also be used to route IPv6 [12]. 
RFC 1195 [1] places certain topological restrictions on networks 
that are routed using Integrated IS-IS, specifically that every 
Intermediate System in a level-1 area must be able to forward all 
network layer protocols that are present in that area, and that 
every level-2 Intermediate System must be able to forward all 
network layer protocols present in the routing domain. 
The mechanism described in this document enables an Intermediate 
System or a group of Intermediate Systems that do not support a 
particular network layer protocol to be used in a level-1 area or 
level-2 subdomain where that network layer protocol is present. 
Specifically the mechanism provides automatic encapsulation and 
unencapsulation so that a packet or PDU may pass through an 
Intermediate System that would not normally be able to forward that
type of packet.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-02.txt

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-isis-auto-encap-02.txt

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

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

--OtherAccess--

--NextPart--


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 08:14:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA09715
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 08:14:23 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ICBpv29790;
	Wed, 18 Sep 2002 08:11:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IBwFv28812
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 07:58:15 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA09151;
	Wed, 18 Sep 2002 07:56:25 -0400 (EDT)
Message-Id: <200209181156.HAA09151@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: isis-wg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-igp-p2p-over-lan-01.txt
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 07:56:24 -0400

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IS-IS for IP Internets Working Group of the IETF.

	Title		: Point-to-point operation over LAN in link-state 
                          routing protocols
	Author(s)	: N. Shen et al.
	Filename	: draft-ietf-isis-igp-p2p-over-lan-01.txt
	Pages		: 8
	Date		: 2002-9-17
	
The two predominant circuit types used by link state routing
protocols are point-to-point and broadcast. It is important to 
identify the correct circuit type when forming adjacencies, 
flooding link state database packets, and representing the circuit
topologically. This document describes a simple mechanism to treat
the broadcast network as a point-to-point connection from the 
standpoint of IP routing.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-isis-igp-p2p-over-lan-01.txt

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

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

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


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

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

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

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

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

ENCODING mime
FILE /internet-drafts/draft-ietf-isis-igp-p2p-over-lan-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-isis-igp-p2p-over-lan-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

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

--OtherAccess--

--NextPart--


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 08:47:59 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10836
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 08:47:59 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ICl3v31770;
	Wed, 18 Sep 2002 08:47:03 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IChjv31688
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 08:43:45 -0400
Received: from ws1-4.us4.outblaze.com (205-158-62-50.outblaze.com [205.158.62.50])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id IAA10547
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 08:41:57 -0400 (EDT)
Received: (qmail 44451 invoked by uid 1001); 18 Sep 2002 12:43:03 -0000
Message-ID: <20020918124303.44450.qmail@iname.com>
Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-4.us4.outblaze.com with http for
    philip.christian@iname.com; Wed, 18 Sep 2002 12:43:03 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: isis-wg@ietf.org
Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-auto-encap-02.txt
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-4.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 12:43:03 +0000
Content-Transfer-Encoding: 7bit

Just a quick note to explain the update.

Firstly it updates my contact details, as I now have a different employer.

Secondly I realised that documenting several different encapsulation methods would encourage folks to implement different ones, leading to inability of vendor As box to build a dynamic tunnel to vendor Bs box.
If box A cannot forward a packet to box B, when all of the other boxes are expecting them to do so (IS-IS would tell them that a path is there), then a classic blackhole is the result.
I guess that sometime choice is a bad thing.

The original ITU scheme didn't suffer from this problem as it doesn't give any choice of encapsulation.

I added a History section to document / explain this stuff.

Regards, Philip

----- Original Message -----
From: Internet-Drafts@ietf.org
Date: Wed, 18 Sep 2002 07:56:19 -0400 
To: IETF-Announce: ;
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-auto-encap-02.txt


snip
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-02.txt
> 



-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 10:48:25 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA16114
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 10:48:25 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IEk5v22142;
	Wed, 18 Sep 2002 10:46:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IEehv21881
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 10:40:43 -0400
Received: from zcars04f.ca.nortel.com (zcars04f.nortelnetworks.com [47.129.242.57])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA15651
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 10:38:53 -0400 (EDT)
Received: from zcard307.ca.nortel.com (americasm07.nt.com [47.129.242.67])
	by zcars04f.ca.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id g8IEe6811034
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 10:40:06 -0400 (EDT)
Received: from zcard04e.ca.nortel.com ([47.129.242.64]) by zcard307.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id SK2MXX3K; Wed, 18 Sep 2002 10:40:08 -0400
Received: from americasm01.nt.com (wcars0rx.ca.nortel.com [47.128.148.154]) by zcard04e.ca.nortel.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id RD1LSXKH; Wed, 18 Sep 2002 10:40:07 -0400
Message-ID: <3D888FFF.97F0D0A7@americasm01.nt.com>
From: "Ruth Civil" <rxc@nortelnetworks.com>
Organization: Nortel Networks
X-Mailer: Mozilla 4.72C-CCK-MCD CUE 6.2H or 8S [en] (X11; U; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: isis-wg@ietf.org
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] Protocols Supported TLV
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 10:38:55 -0400
Content-Transfer-Encoding: 7bit


I would like to know what people think should be done with the
information received in the Protocols Supported TLV of an IIH, in the
way of compatibility checking.

I can think of 3 possibilities:

1. Nothing. 
E.g. If a neighbour sends you a Protocol Supported TLV indicating that
it only supports CLNP, and the receiving router is configured to only
support IP, you ignore the information in the PSupp TLV and bring up the
adjacency anyway.  (In which case, what was the point of sending the
PSupp TLV in the IIH in the first place ?)

2. You bring up the adjacency if there is an overlap. E.g, if the
neighbour advertises CLNP and IP in its PSupp TLV, but you support only
IP, you bring up the adjacency. If there is no overlap between the
supported protocols you don't bring up the adjacency.

3. You bring up the adjacency only if there is an exact match between
the protocols the neighbour advertises in its Psupp TLV and the
protocols you are configured to support, and don't bring it up
otherwise.

Any ideas/comments/opinions out there ?

Cheers,
	Ruth
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 11:14:37 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17377
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 11:14:37 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IFD0v25038;
	Wed, 18 Sep 2002 11:13:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IF9Bv24916
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 11:09:11 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16872
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 11:07:21 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74343@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Ruth Civil'" <rxc@nortelnetworks.com>
Cc: "ISIS-WG (E-mail)" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] Protocols Supported TLV
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 11:08:25 -0400

> I would like to know what people think should be done with the
> information received in the Protocols Supported TLV of an IIH, in the
> way of compatibility checking.

Ruth -
	We hashed this out a few months ago when writing
http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt

The document is still under revision, but this portion 
has settled down, and hasn't changed much recently.
The section from my current version is reproduced
below.  

One of the sticky points is what happens
with DIS election on a LAN - you can get into 
situations where not everyone can talk to the DIS,
or where you have dueling DISs.  It seems that 
discussion of this issue was left on the 
cutting room floor.  

Work on this draft is ongoing in sub mailing list of
this group.  Let me know if you'd like to help.  

- jeff parker
- axiowave networks


12. Non-homogeneous Protocol Networks

   RFC 1195 [2] assumes that every deployment of IS-IS routers will sup-
   port a homogeneous set of protocols. It anticipates OSI only, IP
   only, or dual OSI and IP routers. While it allows mixed areas with,
   for example, both pure IP and Dual IP and OSI routers, it allows only
   IP traffic in such domains, and OSI traffic only when pure OSI and
   Dual IP and OSI routers are present. Thus it provides only lowest
   common denominator routing.

   RFC 1195 [2] also requires the inclusion of the Protocol Supported
   TLV with code 129 in IIH and ISH PDUs and in LSP number Zero. IP
   capable routers MUST generate a Protocol Supported TLV, and MUST
   include the IP protocol as a supported protocol. A router that does
   not include the Protocols Supported TLV may be assumed to be a pure
   OSI router and can be interpreted as implicitly "advertising" support
   for the OSI protocol.

   The requirements of RFC 1195 [2] are ample if networks adhere to this
   restriction. However, the behavior of mixed networks that do not fol-
   low these guidelines is not well defined.

   The ITU-T requires that SONET/SDH equipment running the IS-IS proto-
   col must not form an adjacency with a neighbour unless they share at
   least one network layer protocol in common. Unless this feature is
   present in every IS in the SONET or SDH DCN network the network may
   not function correctly. Implementors MAY include this feature if they
   wish to ensure interoperability with SONET and SDH DCN networks.

   Definition of an interoperable strategy for resolving the problems
   that arise in non-homogeneous protocol remains incomplete. Members of
   the ITU are actively working on a proposal: see "Architecture and
   Specification of Data Communication Network", [9].

   
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 11:57:36 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18736
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 11:57:36 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IFu1v27089;
	Wed, 18 Sep 2002 11:56:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IFlGv26803
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 11:47:16 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18229
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 11:45:26 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8IFkH1W010667;
	Wed, 18 Sep 2002 11:46:19 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-222-117.cisco.com [64.102.222.117])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAC10792;
	Wed, 18 Sep 2002 11:45:57 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020918114450.01981d40@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 TLV
Cc: "'Ruth Civil'" <rxc@nortelnetworks.com>,
        "ISIS-WG (E-mail)" <isis-wg@ietf.org>
In-Reply-To: <EB5FFC72F183D411B38200062957342902A74343@r2d2.axiowave.com
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 11:45:54 -0400

At 11:08 AM 9/18/2002, Jeff Parker wrote:
>> I would like to know what people think should be done with the
>> information received in the Protocols Supported TLV of an IIH, in the
>> way of compatibility checking.
>
>Ruth -
>        We hashed this out a few months ago when writing
>http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt
>
>The document is still under revision, but this portion 
>has settled down, and hasn't changed much recently.
>The section from my current version is reproduced
>below.  
>
>One of the sticky points is what happens
>with DIS election on a LAN - you can get into 
>situations where not everyone can talk to the DIS,
>or where you have dueling DISs.  It seems that 
>discussion of this issue was left on the 
>cutting room floor.  

I'm surprised I let that happen, since this was my mantra for a while.
I'll see if I can come up with a paragraph to fit in context.

Regards,
Jeff

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 13:00:22 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21290
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:00:22 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IGxFv30791;
	Wed, 18 Sep 2002 12:59:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IGtkv30669
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 12:55:46 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA21057
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 12:53:55 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 3B9702CDB5E; Wed, 18 Sep 2002 09:55:41 -0700 (PDT)
To: mike shand <mshand@cisco.com>
Cc: isis <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling 
In-reply-to: Mail from mike shand <mshand@cisco.com> 
 dated Fri, 06 Sep 2002 10:08:30 BST
 <4.3.2.7.2.20020906095803.04434a50@jaws.cisco.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020918165541.3B9702CDB5E@prattle.redback.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 09:55:41 -0700

 ] 
 ] There are those (Naiming?) who believe this is a bad idea, and I have some 
 ] sympathy with that viewpoint. This says that since we have committed to 
 ] doing restart, we ought to be able to extend the adjacency holding timer to 
 ] give ourselves a bit more time to get it all done. So the spec now permits 
 ] you to do this if you want to.
 ] 
 ] So to summarise, the text your referred to says don't refresh, but you MAY 
 ] refresh if you want to.

I don't see the version 01.txt says that. Could you change the draft
text to make this more clear? I basically see no reason we need to
"don't refresh". The closest thing I can related to this is to offer
a control by operators to limit the total number of graceful restart
a neighbor can have in a short period of time.

thanks.
- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 13:07:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21678
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:07:53 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IH6tv31124;
	Wed, 18 Sep 2002 13:06:55 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IH3gv31016
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 13:03:42 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21417;
	Wed, 18 Sep 2002 13:01:51 -0400 (EDT)
Message-Id: <200209181701.NAA21417@ietf.org>
To: IETF-Announce: ;
Cc: isis-wg@ietf.org
From: The IESG <iesg-secretary@ietf.org>
Reply-to: iesg@ietf.org
Subject: [Isis-wg] Last Call: Extending the Number of IS-IS LSP Fragments Beyond
 the 256 Limit to Informational
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 13:01:51 -0400


The IESG has received a request from the IS-IS for IP Internets Working 
Group to consider Extending the Number of IS-IS LSP Fragments Beyond 
the 256 Limit <draft-ietf-isis-ext-lsp-frags-02.txt> as a Informational.  

The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the 
iesg@ietf.org or ietf@ietf.org mailing lists by 2002-10-2.

Files can be obtained via 
http://www.ietf.org/internet-drafts/draft-ietf-isis-ext-lsp-frags-02.txt



_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 13:11:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21802
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:11:34 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IHAov31832;
	Wed, 18 Sep 2002 13:10:50 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IH7dv31703
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 13:07:39 -0400
Received: from hal2.bizland-inc.net (mail2.bizland-inc.net [64.28.88.158])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21543
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 13:05:47 -0400 (EDT)
Received: from adsl-64-169-93-204.dsl.snfc21.pacbell.net ([64.169.93.204] helo=les.espsoft.com)
	by hal2.bizland-inc.net with asmtp (Exim 4.10)
	id 17riHq-0008Kn-00; Wed, 18 Sep 2002 13:06:50 -0400
Message-Id: <5.1.0.14.0.20020918095722.00a1bc90@pop.bizland.com>
X-Sender: espllc@pop.bizland.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: Jeff Learman <jlearman@cisco.com>, Jeff Parker <jparker@axiowave.com>
From: Les Ginsberg <les@espsoft.com>
Subject: RE: [Isis-wg] Protocols Supported TLV
Cc: "'Ruth Civil'" <rxc@nortelnetworks.com>,
        "ISIS-WG (E-mail)" <isis-wg@ietf.org>
In-Reply-To: <4.3.2.7.2.20020918114450.01981d40@dingdong.cisco.com>
References: <EB5FFC72F183D411B38200062957342902A74343@r2d2.axiowave.com >
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_10815495==_.ALT"
X-Bizland-Abuse: This message was sent on behalf of a Bizland customer espllc -- Please report any abuse to abuse@bizland-inc.com
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 10:07:18 -0700

--=====================_10815495==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

At 11:45 AM 9/18/02 -0400, Jeff Learman wrote:
> >
> >One of the sticky points is what happens
> >with DIS election on a LAN - you can get into
> >situations where not everyone can talk to the DIS,
> >or where you have dueling DISs.  It seems that
> >discussion of this issue was left on the
> >cutting room floor.
>
>I'm surprised I let that happen, since this was my mantra for a while.
>I'll see if I can come up with a paragraph to fit in context.


Actually I believe we deliberately left out discussion of this issue 
because we knew that the ITU work and the associated auto-encapsulation 
draft work being done by Philip were addressing this issue and we didn't 
want to do a disservice by having either an incomplete discussion or a 
solution which differed from what was eventually settled on by the other 
work. Hence the statement in the section from 
http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt which 
Jeff P quoted:

     "However, the behavior of mixed networks that do not fol-
      low these guidelines is not well defined."


  Section 5.1 of Philip's latest draft  (draft-ietf-isis-auto-encap-02.txt) 
addresses this issue quite well.

    Les

--=====================_10815495==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
At 11:45 AM 9/18/02 -0400, Jeff Learman wrote:<br>
<blockquote type=cite class=cite cite>&gt;<br>
&gt;One of the sticky points is what happens<br>
&gt;with DIS election on a LAN - you can get into <br>
&gt;situations where not everyone can talk to the DIS,<br>
&gt;or where you have dueling DISs.&nbsp; It seems that <br>
&gt;discussion of this issue was left on the <br>
&gt;cutting room floor.&nbsp; <br><br>
I'm surprised I let that happen, since this was my mantra for a
while.<br>
I'll see if I can come up with a paragraph to fit in context.<br>
</blockquote><br><br>
Actually I believe we deliberately left out discussion of this issue
because we knew that the ITU work and the associated auto-encapsulation
draft work being done by Philip were addressing this issue and we didn't
want to do a disservice by having either an incomplete discussion or a
solution which differed from what was eventually settled on by the other
work. Hence the statement in the section from
<a href="http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt" eudora="autourl"><font color="#0000FF"><u>http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt</a></u></font>
which Jeff P quoted:<br><br>
&nbsp;&nbsp;&nbsp; &quot;However, the behavior of mixed networks that do not fol- <br>
&nbsp;&nbsp;&nbsp;&nbsp; low these guidelines is not well defined.&quot;<br><br>
<br>
&nbsp;Section 5.1 of Philip's latest draft&nbsp; (draft-ietf-isis-auto-encap-02.txt) addresses this issue quite well.<br><br>
&nbsp;&nbsp; Les<br>
</html>

--=====================_10815495==_.ALT--

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 13:20:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA22144
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 13:20:02 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IHJDv32185;
	Wed, 18 Sep 2002 13:19:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IHFkv32049
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 13:15:46 -0400
Received: from mail4.nec.com (dns4.nec.com [131.241.15.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA21889
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 13:13:54 -0400 (EDT)
Received: from netkeeper2.sj.nec.com (netkeeper2.sj.nec.com [131.241.31.10])
	by mail4.nec.com (/) with ESMTP id g8IHFAa14902
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 10:15:10 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1])
	by netkeeper2.sj.nec.com (8.9.1a/8.9.1) with ESMTP id KAA24243
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 10:15:01 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com 
	by necsun.tdd.sj.nec.com  with ESMTP id g8IH7cAd008622
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 10:07:39 -0700 (PDT)
Received: from ems11 (ems11 [131.241.5.62])
	by bunny.tdd.sj.nec.com  with SMTP id g8IH7bKq013457
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 10:07:37 -0700 (PDT)
Received: by localhost with Microsoft MAPI; Wed, 18 Sep 2002 10:21:03 -0700
Message-ID: <01C25EFD.176AB080.ramsrm@tdd.sj.nec.com>
From: ramanathan rams <ramsrm@tdd.sj.nec.com>
Reply-To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
To: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Organization: NEC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 43 TEXT
Subject: [Isis-wg] ISIS doubts.
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 10:21:02 -0700

hi all,

I have some doubts in ISIS-TE, could u please explain me, also please let
me know if I am wrong with my assumptions.?

Assumptions :

*  In traffic engineering we usually specify the Explicit route for 
LSP(tunnel)
   establishment to the signalling protocol.

*  Link's traffic engineering attributes are distributed within the area
   for L1 and within L2 backbone for L2.

Doubts :

*  Using the domain wide prefix distribution standard, L2 information is
leaked inside the area and  L1 information is leaked outside the area. So
the path computed will have a best exit point( L1L2 router ) from that
area. ( from the exit point, L2 SPF is run and resulting inofrmation is
flooded within the area using  L1 LSPs ), for TE links how do L1L2
routers(exit points) compute the C-SPF( on what basis ) and flood the
information within the area using L1 LSP?

*  how do we get the full path( list of router's IP addresses ) which is
used for setting up the LSP, by running the C-SPF ? ( my assumption is that 
we can get information only till the exit router after that we don't know
about any routers which is present along the path to the destination) or
even the partial path till the exit point is enough for setting up LSP
tunnels?

How do we guarantee the specified constraints along the complete path of
the LSP using the ISIS-TE extension( because the TE information about the
links which are present in the other areas are not distributed throughout
the AS ) ?

* could u please briefly explain me how the Explicit path is calculated
with given constraints using ISIS TE & C-SPF to any destination which is
outside the source area in an ISIS AS( path calculation and TE database 
synchronisation which is used for explicit path calculation)?

thanks
rams.

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 18 14:53:21 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25945
	for <isis-archive@lists.ietf.org>; Wed, 18 Sep 2002 14:53:21 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IIpTv04659;
	Wed, 18 Sep 2002 14:51:30 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8IImxv04590
	for <isis-wg@optimus.ietf.org>; Wed, 18 Sep 2002 14:48:59 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA25619
	for <isis-wg@ietf.org>; Wed, 18 Sep 2002 14:47:09 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8IIlwPR020989;
	Wed, 18 Sep 2002 14:47:58 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-222-117.cisco.com [64.102.222.117])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAC16473;
	Wed, 18 Sep 2002 14:47:41 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020918133036.037ebc28@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Les Ginsberg <les@espsoft.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported TLV
Cc: Jeff Parker <jparker@axiowave.com>,
        "'Ruth Civil'" <rxc@nortelnetworks.com>,
        "ISIS-WG (E-mail)" <isis-wg@ietf.org>
In-Reply-To: <5.1.0.14.0.20020918095722.00a1bc90@pop.bizland.com>
References: <4.3.2.7.2.20020918114450.01981d40@dingdong.cisco.com>
 <EB5FFC72F183D411B38200062957342902A74343@r2d2.axiowave.com >
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_1787362461==_.ALT"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 18 Sep 2002 13:31:52 -0400

--=====================_1787362461==_.ALT
Content-Type: text/plain; charset="us-ascii"


Good point, Les, but we should at least warn folks that this is
not a plug-and-play situation.  I agree we shouldn't attempt to
solve it, just point out the problem and mention that it can be
worked around by configuring DR priorities.

At 01:07 PM 9/18/2002, Les Ginsberg wrote:
>At 11:45 AM 9/18/02 -0400, Jeff Learman wrote:
>>>
>>>One of the sticky points is what happens
>>>with DIS election on a LAN - you can get into 
>>>situations where not everyone can talk to the DIS,
>>>or where you have dueling DISs.  It seems that 
>>>discussion of this issue was left on the 
>>>cutting room floor.  
>>
>>I'm surprised I let that happen, since this was my mantra for a while.
>>I'll see if I can come up with a paragraph to fit in context.
>
>
>Actually I believe we deliberately left out discussion of this issue because we knew that the ITU work and the associated auto-encapsulation draft work being done by Philip were addressing this issue and we didn't want to do a disservice by having either an incomplete discussion or a solution which differed from what was eventually settled on by the other work. Hence the statement in the section from http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt which Jeff P quoted:
>
>    "However, the behavior of mixed networks that do not fol- 
>     low these guidelines is not well defined."
>
>
> Section 5.1 of Philip's latest draft  (draft-ietf-isis-auto-encap-02.txt) addresses this issue quite well.
>
>   Les

--=====================_1787362461==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<br>
Good point, Les, but we should at least warn folks that this is<br>
not a plug-and-play situation.&nbsp; I agree we shouldn't attempt 
to<br>
solve it, just point out the problem and mention that it can be<br>
worked around by configuring DR priorities.<br>
<br>
At 01:07 PM 9/18/2002, Les Ginsberg wrote:<br>
<blockquote type=cite cite>At 11:45 AM 9/18/02 -0400, Jeff Learman
wrote:<br>
<blockquote type=cite cite>&gt;<br>
&gt;One of the sticky points is what happens<br>
&gt;with DIS election on a LAN - you can get into <br>
&gt;situations where not everyone can talk to the DIS,<br>
&gt;or where you have dueling DISs.&nbsp; It seems that <br>
&gt;discussion of this issue was left on the <br>
&gt;cutting room floor.&nbsp; <br>
<br>
I'm surprised I let that happen, since this was my mantra for a
while.<br>
I'll see if I can come up with a paragraph to fit in
context.</blockquote><br>
<br>
Actually I believe we deliberately left out discussion of this issue
because we knew that the ITU work and the associated auto-encapsulation
draft work being done by Philip were addressing this issue and we didn't
want to do a disservice by having either an incomplete discussion or a
solution which differed from what was eventually settled on by the other
work. Hence the statement in the section from
<a href="http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt" eudora="autourl"><font color="#0000FF"><u>http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt</a></u></font>
which Jeff P quoted:<br>
<br>
&nbsp;&nbsp;&nbsp; &quot;However, the behavior of mixed networks that do not fol- <br>
&nbsp;&nbsp;&nbsp;&nbsp; low these guidelines is not well defined.&quot;<br>
<br>
<br>
&nbsp;Section 5.1 of Philip's latest draft&nbsp; (draft-ietf-isis-auto-encap-02.txt) addresses this issue quite well.<br>
<br>
&nbsp;&nbsp; Les</blockquote></html>

--=====================_1787362461==_.ALT--

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 02:31:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21829
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 02:31:07 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J6TVv15639;
	Thu, 19 Sep 2002 02:29:31 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J6Q6v15558
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 02:26:06 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA21634
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 02:24:06 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2O00F5O9VDMR@mta2.huawei.com> for isis-wg@ietf.org;
 Thu, 19 Sep 2002 14:26:01 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2O00FII9VCUR@mta2.huawei.com> for isis-wg@ietf.org;
 Thu, 19 Sep 2002 14:26:01 +0800 (CST)
Received: from CL5002VJAMRIT ([10.18.4.151]) by          mailin.huawei.com
 (Netscape Messaging Server 4.15) with ESMTP id          H2O9WV00.60N for
 <isis-wg@ietf.org>; Thu, 19 Sep 2002 14:26:55 +0800
From: Vijay Amrit Agrawal <vijayamrit@huawei.com>
To: isis <isis-wg@ietf.org>
Message-id: <00b001c25fa7$1c4caf40$9704120a@in.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <20020918165541.3B9702CDB5E@prattle.redback.com>
Content-Transfer-Encoding: 7BIT
Subject: [Isis-wg] Questions on IS-IS Restart Signalling
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 12:08:05 +0530
Content-Transfer-Encoding: 7BIT

Hi All,
I had some simple questions regarding the restart option TLV in the IIH.

i) When the router starts for first time it can include the "restart" TLV in
the IIH, but it has no need to set the RR bit (as the remaining time in RA
will not have any meaning for it anyway and the only other purpose RR serves
is to speed up the sending of CSNP). Is this correct?
ii)The draft talks about what the neighbor should do when it receives a
"re-start" TLV with RR bit set and the adjacency is UP. What if the
adjacency is not UP? (Agreed the probability for this happening is low, but
possible).
The neighbor can do the following:
  a)Send an IIH with "re-start" TLV in which neither RA nor RR bit is set.
The restarting router can't use this as ack (at least for the first time) as
this hello might have been sent by the neighbor before recieving the IIH
with RR bit set. Restarting router will try for sometime and then give up.
  b)Send an IIH with "re-start" TLV with the RA bit set, and the remaining
time as zero. Restarting router can treat that as indication to follow the
normal process on this interface.

Regards,
Vijay


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 03:12:23 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22421
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 03:12:23 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J7BXv18006;
	Thu, 19 Sep 2002 03:11:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J79jv17959
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 03:09:45 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA22359
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 03:07:49 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 35179F2C46; Thu, 19 Sep 2002 00:09:34 -0700 (PDT)
To: Vijay Amrit Agrawal <vijayamrit@huawei.com>
Cc: isis <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling 
In-reply-to: Mail from Vijay Amrit Agrawal <vijayamrit@huawei.com> 
 dated Thu, 19 Sep 2002 12:08:05 +0530
 <00b001c25fa7$1c4caf40$9704120a@in.huawei.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020919070934.35179F2C46@prattle.redback.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 00:09:34 -0700

 ] Hi All,
 ] I had some simple questions regarding the restart option TLV in the IIH.
 ] 
 ] i) When the router starts for first time it can include the "restart" TLV in
 ] the IIH,

the "restart" TLV is ALWAYS included in IIH, regardless of a router
restart or not.

 ] but it has no need to set the RR bit (as the remaining time in RA
 ] will not have any meaning for it anyway

this statement may NOT be true, this is the difference between mike
and i were discussing.

 ] and the only other purpose RR serves
 ] is to speed up the sending of CSNP). Is this correct?

the most important thing the RR bit set, is to ask the neighbor not
to reset the adjacency if its already up, this is done by ignoring
the content of "Intermediate System Neighbors" option TLV in IIH
after receiving the IIH with this RR bit set. the side benefit is
also ask the neighbor to send csnp and lsps if it can.

 ] ii)The draft talks about what the neighbor should do when it receives a
 ] "re-start" TLV with RR bit set and the adjacency is UP. What if the
 ] adjacency is not UP? (Agreed the probability for this happening is low, but
 ] possible).

this probability is not low. there is also prossibility that when a
router restart, it never had any neighbor before. but those things
have little to do with graceful restart. the graceful restart is to
keep the adjacency states the same before and after restart. if it
was not "UP" before, then this draft does not apply at all, the
neighbor should just do what ever it does for normal ISIS adjacency
setup regardless of this "restart" TLV.

 ] The neighbor can do the following:
 ]   a)Send an IIH with "re-start" TLV in which neither RA nor RR bit is set.
 ] The restarting router can't use this as ack (at least for the first time) as
 ] this hello might have been sent by the neighbor before recieving the IIH
 ] with RR bit set. Restarting router will try for sometime and then give up.
 ]   b)Send an IIH with "re-start" TLV with the RA bit set, and the remaining
 ] time as zero. Restarting router can treat that as indication to follow the
 ] normal process on this interface.
 ] 
 ] Regards,
 ] Vijay
 ] 
 ] 
 ] _______________________________________________
 ] Isis-wg mailing list
 ] Isis-wg@ietf.org
 ] https://www1.ietf.org/mailman/listinfo/isis-wg

- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 04:42:57 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27016
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 04:42:57 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J8fOv22865;
	Thu, 19 Sep 2002 04:41:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J8cUv22738
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 04:38:30 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26881
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 04:36:30 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2O00FFUG04MR@mta2.huawei.com> for isis-wg@ietf.org;
 Thu, 19 Sep 2002 16:38:28 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2O00FCHG03UR@mta2.huawei.com> for isis-wg@ietf.org;
 Thu, 19 Sep 2002 16:38:28 +0800 (CST)
Received: from CL5002VJAMRIT ([10.18.4.151]) by          mailin.huawei.com
 (Netscape Messaging Server 4.15) with ESMTP id          H2OG1M00.10R; Thu,
 19 Sep 2002 16:39:22 +0800
From: Vijay Amrit Agrawal <vijayamrit@huawei.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
To: Naiming Shen <naiming@redback.com>
Cc: isis <isis-wg@ietf.org>
Message-id: <00c101c25fb9$9cee0bf0$9704120a@in.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <20020919070934.35179F2C46@prattle.redback.com>
Content-Transfer-Encoding: 7BIT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 14:20:32 +0530
Content-Transfer-Encoding: 7BIT

Please see my comments inline
----- Original Message -----
From: "Naiming Shen" <naiming@redback.com>
To: "Vijay Amrit Agrawal" <vijayamrit@huawei.com>
Cc: "isis" <isis-wg@ietf.org>
Sent: Thursday, September 19, 2002 12:39 PM
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling


> ] Hi All,
>  ] I had some simple questions regarding the restart option TLV in the
IIH.
>  ]
>  ] i) When the router starts for first time it can include the "restart"
TLV in
>  ] the IIH,
>
> the "restart" TLV is ALWAYS included in IIH, regardless of a router
> restart or not.
>
>  ] but it has no need to set the RR bit (as the remaining time in RA
>  ] will not have any meaning for it anyway
>
> this statement may NOT be true, this is the difference between mike
> and i were discussing.
>
>  ] and the only other purpose RR serves
>  ] is to speed up the sending of CSNP). Is this correct?
>
> the most important thing the RR bit set, is to ask the neighbor not
> to reset the adjacency if its already up, this is done by ignoring

If the router is starting for the FIRST time the adjacency won't be up. Am I
missing something?  (one can say, as you are indicating that the draft
doesn't apply for this case so RR bit will be ignored)

> the content of "Intermediate System Neighbors" option TLV in IIH
> after receiving the IIH with this RR bit set. the side benefit is
> also ask the neighbor to send csnp and lsps if it can.
>
>  ] ii)The draft talks about what the neighbor should do when it receives a
>  ] "re-start" TLV with RR bit set and the adjacency is UP. What if the
>  ] adjacency is not UP? (Agreed the probability for this happening is low,
but
>  ] possible).
>
> this probability is not low. there is also prossibility that when a
> router restart, it never had any neighbor before. but those things
> have little to do with graceful restart. the graceful restart is to
> keep the adjacency states the same before and after restart. if it
> was not "UP" before, then this draft does not apply at all, the
> neighbor should just do what ever it does for normal ISIS adjacency
> setup regardless of this "restart" TLV.

My point was, yes the normal ISIS adjacency setup will be done, but the
neighboring router can "help" the restarting router in knowing "quickly"
that there is no point waiting for RA and cancel your T1 timer.

>
>  ] The neighbor can do the following:
>  ]   a)Send an IIH with "re-start" TLV in which neither RA nor RR bit is
set.
>  ] The restarting router can't use this as ack (at least for the first
time) as
>  ] this hello might have been sent by the neighbor before recieving the
IIH
>  ] with RR bit set. Restarting router will try for sometime and then give
up.
>  ]   b)Send an IIH with "re-start" TLV with the RA bit set, and the
remaining
>  ] time as zero. Restarting router can treat that as indication to follow
the
>  ] normal process on this interface.
>  ]
>  ] Regards,
>  ] Vijay
>  ]
>  ]
>  ] _______________________________________________
>  ] Isis-wg mailing list
>  ] Isis-wg@ietf.org
>  ] https://www1.ietf.org/mailman/listinfo/isis-wg
>
> - Naiming
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 05:19:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27656
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 05:19:29 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J9I0v25079;
	Thu, 19 Sep 2002 05:18:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J9Fkv25015
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 05:15:46 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27590
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 05:13:59 -0400 (EDT)
Received: from mshand-w2k.cisco.com (lon-sto4-lan-vlan133-dhcp16.cisco.com [144.254.108.83])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA28709;
	Thu, 19 Sep 2002 10:15:08 +0100 (BST)
Message-Id: <4.3.2.7.2.20020919100939.046ddfd0@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Vijay Amrit Agrawal <vijayamrit@huawei.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
Cc: Naiming Shen <naiming@redback.com>, isis <isis-wg@ietf.org>
In-Reply-To: <00c101c25fb9$9cee0bf0$9704120a@in.huawei.com>
References: <20020919070934.35179F2C46@prattle.redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 10:14:02 +0100

At 14:20 19/09/2002 +0530, Vijay Amrit Agrawal wrote:


>If the router is starting for the FIRST time the adjacency won't be up. Am I
>missing something?

Yes. See clause 3,  para 4 at bottom of page starting
"Secondly, ...."

and clause 4.3.1.1



         Mike

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 05:23:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27737
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 05:23:51 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J9N5v25321;
	Thu, 19 Sep 2002 05:23:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J9KLv25175
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 05:20:21 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27631
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 05:18:32 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id C63D24BA214; Thu, 19 Sep 2002 02:20:13 -0700 (PDT)
To: Vijay Amrit Agrawal <vijayamrit@huawei.com>
Cc: Naiming Shen <naiming@redback.com>, isis <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling 
In-reply-to: Mail from Vijay Amrit Agrawal <vijayamrit@huawei.com> 
 dated Thu, 19 Sep 2002 14:20:32 +0530
 <00c101c25fb9$9cee0bf0$9704120a@in.huawei.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020919092013.C63D24BA214@prattle.redback.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 02:20:13 -0700

 ] Please see my comments inline
 ] ----- Original Message -----
 ] From: "Naiming Shen" <naiming@redback.com>
 ] To: "Vijay Amrit Agrawal" <vijayamrit@huawei.com>
 ] Cc: "isis" <isis-wg@ietf.org>
 ] Sent: Thursday, September 19, 2002 12:39 PM
 ] Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
 ] 
 ] 
 ] > ] Hi All,
 ] >  ] I had some simple questions regarding the restart option TLV in the
 ] IIH.
 ] >  ]
 ] >  ] i) When the router starts for first time it can include the "restart"
 ] TLV in
 ] >  ] the IIH,
 ] >
 ] > the "restart" TLV is ALWAYS included in IIH, regardless of a router
 ] > restart or not.
 ] >
 ] >  ] but it has no need to set the RR bit (as the remaining time in RA
 ] >  ] will not have any meaning for it anyway
 ] >
 ] > this statement may NOT be true, this is the difference between mike
 ] > and i were discussing.
 ] >
 ] >  ] and the only other purpose RR serves
 ] >  ] is to speed up the sending of CSNP). Is this correct?
 ] >
 ] > the most important thing the RR bit set, is to ask the neighbor not
 ] > to reset the adjacency if its already up, this is done by ignoring
 ] 
 ] If the router is starting for the FIRST time the adjacency won't be up. Am I
 ] missing something?  (one can say, as you are indicating that the draft
 ] doesn't apply for this case so RR bit will be ignored)
 ] 
 ] > the content of "Intermediate System Neighbors" option TLV in IIH
 ] > after receiving the IIH with this RR bit set. the side benefit is
 ] > also ask the neighbor to send csnp and lsps if it can.
 ] >
 ] >  ] ii)The draft talks about what the neighbor should do when it receives a
 ] >  ] "re-start" TLV with RR bit set and the adjacency is UP. What if the
 ] >  ] adjacency is not UP? (Agreed the probability for this happening is low,
 ] but
 ] >  ] possible).
 ] >
 ] > this probability is not low. there is also prossibility that when a
 ] > router restart, it never had any neighbor before. but those things
 ] > have little to do with graceful restart. the graceful restart is to
 ] > keep the adjacency states the same before and after restart. if it
 ] > was not "UP" before, then this draft does not apply at all, the
 ] > neighbor should just do what ever it does for normal ISIS adjacency
 ] > setup regardless of this "restart" TLV.
 ] 
 ] My point was, yes the normal ISIS adjacency setup will be done, but the
 ] neighboring router can "help" the restarting router in knowing "quickly"
 ] that there is no point waiting for RA and cancel your T1 timer.

if the neighbor didn't have an "Up" adjacency state with the restarting
router, it should not set the RA bit in it's "restart" TLV when it sends
back the IIH. this IS the information to timeout whatever the timer
the restarting router has on this interface. In p2p case the neighbor
will not set "Up" state in the 3way handshanking IIH back to the
restarting router.

besides, since the restarting router never had a working
adjacency with that neighbor, upon restarting, what's the hurry
to speed up this adjacency process? usually one needs to do things
quickly when an adjacency is changing from "Up" to "Down", but there is
no reason to do the same while changing from "Down" to "Up". keep
using a sub-optimal path is always OK.

 ] 
 ] >
 ] >  ] The neighbor can do the following:
 ] >  ]   a)Send an IIH with "re-start" TLV in which neither RA nor RR bit is
 ] set.
 ] >  ] The restarting router can't use this as ack (at least for the first
 ] time) as
 ] >  ] this hello might have been sent by the neighbor before recieving the
 ] IIH
 ] >  ] with RR bit set. Restarting router will try for sometime and then give
 ] up.
 ] >  ]   b)Send an IIH with "re-start" TLV with the RA bit set, and the
 ] remaining
 ] >  ] time as zero. Restarting router can treat that as indication to follow
 ] the
 ] >  ] normal process on this interface.
 ] >  ]
 ] >  ] Regards,
 ] >  ] Vijay
 ] >  ]
 ] >  ]
 ] >  ] _______________________________________________
 ] >  ] Isis-wg mailing list
 ] >  ] Isis-wg@ietf.org
 ] >  ] https://www1.ietf.org/mailman/listinfo/isis-wg
 ] >
 ] > - Naiming
 ] > _______________________________________________
 ] > Isis-wg mailing list
 ] > Isis-wg@ietf.org
 ] > https://www1.ietf.org/mailman/listinfo/isis-wg
 ] 

- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 05:33:24 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27949
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 05:33:24 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J9W2v25888;
	Thu, 19 Sep 2002 05:32:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8J9Tvv25735
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 05:29:57 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA27881
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 05:28:10 -0400 (EDT)
Received: from mshand-w2k.cisco.com (lon-sto4-lan-vlan133-dhcp16.cisco.com [144.254.108.83])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id KAA29247;
	Thu, 19 Sep 2002 10:29:24 +0100 (BST)
Message-Id: <4.3.2.7.2.20020919101525.046de308@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Naiming Shen <naiming@redback.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling 
Cc: isis <isis-wg@ietf.org>
In-Reply-To: <20020918165541.3B9702CDB5E@prattle.redback.com>
References: <Mail from mike shand <mshand@cisco.com>
 <4.3.2.7.2.20020906095803.04434a50@jaws.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 10:28:36 +0100

At 09:55 18/09/2002 -0700, Naiming Shen wrote:
>  ]
>  ] There are those (Naiming?) who believe this is a bad idea, and I have 
> some
>  ] sympathy with that viewpoint. This says that since we have committed to
>  ] doing restart, we ought to be able to extend the adjacency holding 
> timer to
>  ] give ourselves a bit more time to get it all done. So the spec now 
> permits
>  ] you to do this if you want to.
>  ]
>  ] So to summarise, the text your referred to says don't refresh, but you 
> MAY
>  ] refresh if you want to.
>
>I don't see the version 01.txt says that.

You are right. I thought I put that in, but in fact all I did was add the 
last para at the end of 4.2 (just before 4.2.1)
which says that you can send an RR clear IIH to refresh it if you want to.

How about replacing 4.2 a) "DO NOT refresh...." with

a) Do not change the state of the adjacency. It is an implementation choice 
whether or not the holding time of the adjacency is refreshed. Not 
refreshing the holding time preserves the intention of the original holding 
time. Refreshing it may allow a longer grace period for the completion of 
the restart process. Whichever option is chosen, the "remaining time" 
transmitted according to (b) below MUST reflect the actual time after which 
the adjacency will now expire.





>Could you change the draft
>text to make this more clear? I basically see no reason we need to
>"don't refresh". The closest thing I can related to this is to offer
>a control by operators to limit the total number of graceful restart
>a neighbor can have in a short period of time.
>
>thanks.
>- Naiming

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 06:28:33 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29032
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 06:28:33 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JARKv29403;
	Thu, 19 Sep 2002 06:27:21 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JAQIv29378
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 06:26:18 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA29002
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 06:24:27 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2O00FGSL01MR@mta2.huawei.com> for isis-wg@ietf.org;
 Thu, 19 Sep 2002 18:26:25 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2O00FYZL00UR@mta2.huawei.com> for isis-wg@ietf.org;
 Thu, 19 Sep 2002 18:26:25 +0800 (CST)
Received: from CL5002VJAMRIT ([10.18.4.151]) by          mailin.huawei.com
 (Netscape Messaging Server 4.15) with ESMTP id          H2OL1J00.L15; Thu,
 19 Sep 2002 18:27:19 +0800
From: Vijay Amrit Agrawal <vijayamrit@huawei.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
To: isis <isis-wg@ietf.org>
Cc: Naiming Shen <naiming@redback.com>, mike shand <mshand@cisco.com>
Message-id: <00de01c25fc8$b1c99030$9704120a@in.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <20020919092013.C63D24BA214@prattle.redback.com>
Content-Transfer-Encoding: 7BIT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 16:08:29 +0530
Content-Transfer-Encoding: 7BIT

Let me try to summarize to make sure I understand it:

i) On starting for FIRST time, the starting router sends IIH with RR bit
set. This will cause the neighbor to send CSNP (for broadcast one would have
got the CSNP anyway but for p2p CSNP is ensured because of timer T1.) This
CSNP will help the starting router to realize when it has synchronized with
the neighbor. The starting router should stop sending packet with RR bit set
on receiving CSNP and not wait for RA.

ii)Neighbor should send CSNP packet on receiving packet with RR bit set
(even if the adjacency is not up). Neighbor should not send IIH with RA bit
set if the adjacency is not up.




----- Original Message -----
From: "Naiming Shen" <naiming@redback.com>
To: "Vijay Amrit Agrawal" <vijayamrit@huawei.com>
Cc: "Naiming Shen" <naiming@redback.com>; "isis" <isis-wg@ietf.org>
Sent: Thursday, September 19, 2002 2:50 PM
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling


> ] Please see my comments inline
>  ] ----- Original Message -----
>  ] From: "Naiming Shen" <naiming@redback.com>
>  ] To: "Vijay Amrit Agrawal" <vijayamrit@huawei.com>
>  ] Cc: "isis" <isis-wg@ietf.org>
>  ] Sent: Thursday, September 19, 2002 12:39 PM
>  ] Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
>  ]
>  ]
>  ] > ] Hi All,
>  ] >  ] I had some simple questions regarding the restart option TLV in
the
>  ] IIH.
>  ] >  ]
>  ] >  ] i) When the router starts for first time it can include the
"restart"
>  ] TLV in
>  ] >  ] the IIH,
>  ] >
>  ] > the "restart" TLV is ALWAYS included in IIH, regardless of a router
>  ] > restart or not.
>  ] >
>  ] >  ] but it has no need to set the RR bit (as the remaining time in RA
>  ] >  ] will not have any meaning for it anyway
>  ] >
>  ] > this statement may NOT be true, this is the difference between mike
>  ] > and i were discussing.
>  ] >
>  ] >  ] and the only other purpose RR serves
>  ] >  ] is to speed up the sending of CSNP). Is this correct?
>  ] >
>  ] > the most important thing the RR bit set, is to ask the neighbor not
>  ] > to reset the adjacency if its already up, this is done by ignoring
>  ]
>  ] If the router is starting for the FIRST time the adjacency won't be up.
Am I
>  ] missing something?  (one can say, as you are indicating that the draft
>  ] doesn't apply for this case so RR bit will be ignored)
>  ]
>  ] > the content of "Intermediate System Neighbors" option TLV in IIH
>  ] > after receiving the IIH with this RR bit set. the side benefit is
>  ] > also ask the neighbor to send csnp and lsps if it can.
>  ] >
>  ] >  ] ii)The draft talks about what the neighbor should do when it
receives a
>  ] >  ] "re-start" TLV with RR bit set and the adjacency is UP. What if
the
>  ] >  ] adjacency is not UP? (Agreed the probability for this happening is
low,
>  ] but
>  ] >  ] possible).
>  ] >
>  ] > this probability is not low. there is also prossibility that when a
>  ] > router restart, it never had any neighbor before. but those things
>  ] > have little to do with graceful restart. the graceful restart is to
>  ] > keep the adjacency states the same before and after restart. if it
>  ] > was not "UP" before, then this draft does not apply at all, the
>  ] > neighbor should just do what ever it does for normal ISIS adjacency
>  ] > setup regardless of this "restart" TLV.
>  ]
>  ] My point was, yes the normal ISIS adjacency setup will be done, but the
>  ] neighboring router can "help" the restarting router in knowing
"quickly"
>  ] that there is no point waiting for RA and cancel your T1 timer.
>
> if the neighbor didn't have an "Up" adjacency state with the restarting
> router, it should not set the RA bit in it's "restart" TLV when it sends
> back the IIH. this IS the information to timeout whatever the timer
> the restarting router has on this interface. In p2p case the neighbor
> will not set "Up" state in the 3way handshanking IIH back to the
> restarting router.
>
> besides, since the restarting router never had a working
> adjacency with that neighbor, upon restarting, what's the hurry
> to speed up this adjacency process? usually one needs to do things
> quickly when an adjacency is changing from "Up" to "Down", but there is
> no reason to do the same while changing from "Down" to "Up". keep
> using a sub-optimal path is always OK.
>
>  ]
>  ] >
>  ] >  ] The neighbor can do the following:
>  ] >  ]   a)Send an IIH with "re-start" TLV in which neither RA nor RR bit
is
>  ] set.
>  ] >  ] The restarting router can't use this as ack (at least for the
first
>  ] time) as
>  ] >  ] this hello might have been sent by the neighbor before recieving
the
>  ] IIH
>  ] >  ] with RR bit set. Restarting router will try for sometime and then
give
>  ] up.
>  ] >  ]   b)Send an IIH with "re-start" TLV with the RA bit set, and the
>  ] remaining
>  ] >  ] time as zero. Restarting router can treat that as indication to
follow
>  ] the
>  ] >  ] normal process on this interface.
>  ] >  ]
>  ] >  ] Regards,
>  ] >  ] Vijay
>  ] >  ]
>  ] >  ]
>  ] >  ] _______________________________________________
>  ] >  ] Isis-wg mailing list
>  ] >  ] Isis-wg@ietf.org
>  ] >  ] https://www1.ietf.org/mailman/listinfo/isis-wg
>  ] >
>  ] > - Naiming
>  ] > _______________________________________________
>  ] > Isis-wg mailing list
>  ] > Isis-wg@ietf.org
>  ] > https://www1.ietf.org/mailman/listinfo/isis-wg
>  ]
>
> - Naiming

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 09:47:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05133
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 09:47:15 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JDjcv08246;
	Thu, 19 Sep 2002 09:45:38 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JDgUv08145
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 09:42:30 -0400
Received: from mta1-3.us4.outblaze.com (205-158-62-44.outblaze.com [205.158.62.44])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04662
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 09:40:39 -0400 (EDT)
Received: from ws1-2.us4.outblaze.com (205-158-62-54.outblaze.com [205.158.62.54])
	by mta1-3.us4.outblaze.com (8.12.3/8.12.3/us4-srs) with SMTP id g8JDfnQR011565
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 13:41:49 GMT
Received: (qmail 10124 invoked by uid 1001); 19 Sep 2002 09:06:21 -0000
Message-ID: <20020919090621.10123.qmail@iname.com>
Content-Type: text/html; charset="us-ascii"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-2.us4.outblaze.com with http for
    philip.christian@iname.com; Thu, 19 Sep 2002 09:06:21 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: rxc@nortelnetworks.com, isis-wg@ietf.org
Subject: RE: [Isis-wg] Protocols Supported TLV
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-2.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 09:06:21 +0000
Content-Transfer-Encoding: 7bit

<P>As Ruth says, there are three options open to us (wrt Protocols Supported field in Hellos):-</P>
<P>1. Ignore it.</P>
<P>2. Only form adjacency if there is an overlap of one or more.</P>
<P>3. Only form adjacency if there is exact match.</P>
<P>Sadly there is no perfect answer...</P>
<P>Option 1 always allows you to build a network, but a network designer has to be careful as it will allow him to build blackholes into the network.</P>
<P>Option 2 only rejects totally useless adjacencies, and so this is why the ITU-T went for this.&nbsp; Also a certain large(st) vendor had already put this in their implementation and it seems to make sense.</P>
<P>Option 3 is idiot proof in the sense that it stops you from getting blackholes, but it also prevents you from building a topology which is perfectly valid.&nbsp; If you read RFC 1195 then you see that it is allowable to put a dual router into an OSI-only area, because that dual router can forward OSI packets perfectly well.&nbsp; Therefore option 3 is probably too restrictive.</P>
<P>Thinking about an IPv6 migration for example.&nbsp; If you have an existing IP4 network then it is perfectly valid to start adding IPv4 / IPv6 dual routers to it (or upgrading the ones that you have), one at a time.&nbsp; It might take you months or years to upgrade them all.&nbsp; Once you have upgraded them all then you can declare it to now be an IPv4 / IPv6 dual area and start forwarding IPv6 traffic on it too.&nbsp; Option 1 and 2 allow this, but 3 doesn't.</P>
<P>Of course if you go for automatic encapsulation then you don't even need to finish upgrading them all before you can start sending IPv6 :-)&nbsp; See <A href="http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-02.txt">http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-02.txt</A>&nbsp;for more details.</P>
<P>Philip</P>
<P><BR><BR>----- Original Message -----<BR>From: Jeff Learman <JLEARMAN@CISCO.COM><BR>Date: Wed, 18 Sep 2002 13:31:52 -0400 <BR>To: Les Ginsberg <LES@ESPSOFT.COM><BR>Subject: RE: [Isis-wg] Protocols Supported TLV<BR><BR><BR>Good point, Les, but we should at least warn folks that this is<BR>not a plug-and-play situation.&nbsp; I agree we shouldn't attempt to<BR>solve it, just point out the problem and mention that it can be<BR>worked around by configuring DR priorities.<BR><BR>At 01:07 PM 9/18/2002, Les Ginsberg wrote:<BR></P>
<BLOCKQUOTE cite type="cite">At 11:45 AM 9/18/02 -0400, Jeff Learman wrote:<BR>
<BLOCKQUOTE cite type="cite">&gt;<BR>&gt;One of the sticky points is what happens<BR>&gt;with DIS election on a LAN - you can get into <BR>&gt;situations where not everyone can talk to the DIS,<BR>&gt;or where you have dueling DISs.&nbsp; It seems that <BR>&gt;discussion of this issue was left on the <BR>&gt;cutting room floor.&nbsp; <BR><BR>I'm surprised I let that happen, since this was my mantra for a while.<BR>I'll see if I can come up with a paragraph to fit in context.</BLOCKQUOTE><BR><BR>Actually I believe we deliberately left out discussion of this issue because we knew that the ITU work and the associated auto-encapsulation draft work being done by Philip were addressing this issue and we didn't want to do a disservice by having either an incomplete discussion or a solution which differed from what was eventually settled on by the other work. Hence the statement in the section from <A href="http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt" eudora!
="autourl"><FONT color=#0000ff><U>http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt</A></U></FONT> which Jeff P quoted:<BR><BR>&nbsp;&nbsp;&nbsp; "However, the behavior of mixed networks that do not fol- <BR>&nbsp;&nbsp;&nbsp;&nbsp; low these guidelines is not well defined."<BR><BR><BR>&nbsp;Section 5.1 of Philip's latest draft&nbsp; (draft-ietf-isis-auto-encap-02.txt) addresses this issue quite well.<BR><BR>&nbsp;&nbsp; Les</BLOCKQUOTE>
-- 
<p>_______________________________________________<br>
Sign-up for your own FREE Personalized E-mail at <font color="#0000FF"><a href="http://www.mail.com/?sr=signup" target="_new">Mail.com</a></font></p>

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 10:14:58 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06462
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 10:14:57 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JEDcv10291;
	Thu, 19 Sep 2002 10:13:38 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JEAuv10165
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 10:10:56 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06152
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 10:09:02 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8JEAU9L000378;
	Thu, 19 Sep 2002 10:10:31 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (rtp-vpn1-452.cisco.com [10.82.225.196])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAC35770;
	Thu, 19 Sep 2002 10:10:13 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020919095815.021d41b8@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Philip Christian" <philip.christian@iname.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported TLV
Cc: rxc@nortelnetworks.com, isis-wg@ietf.org
In-Reply-To: <20020919090621.10123.qmail@iname.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_1857112586==_.ALT"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 10:10:11 -0400

--=====================_1857112586==_.ALT
Content-Type: text/plain; charset="us-ascii"


Option 1 is what 1195 says to do.  It works fine in networks that
follow 1195's topology restrictions (if you want protocol X in a
subdomain, all routers in the subdomain must support protocol X).

Option 2 allows the auto-encapsulation option.

Either option 1 or option 2 work in a mixed network that has
sufficient connectivity for all supported protocols but does not
conform to 1195's restrictions.  However, for either option to work,
DR priorities must be configured so that on any LAN with multiple
protocols, the DR elected must support all protocols.  (That's an
oversimplification, but it's sufficient.)  By "suffiently connected"
I mean that there is a network path supporting protocol X between any
two entities that communicate using protocol X.  For this to work,
multiprotocol routers have to run separate SPFs for each protocol,
while assuming that all pseudonode LSPs support all protocols.

Option 3 has serious disadvantages and no significant advantages.

Regards,
Jeff

At 05:06 AM 9/19/2002, Philip Christian wrote:

>As Ruth says, there are three options open to us (wrt Protocols Supported field in Hellos):-
>
>1. Ignore it.
>
>2. Only form adjacency if there is an overlap of one or more.
>
>3. Only form adjacency if there is exact match.
>
>Sadly there is no perfect answer...
>
>Option 1 always allows you to build a network, but a network designer has to be careful as it will allow him to build blackholes into the network.
>
>Option 2 only rejects totally useless adjacencies, and so this is why the ITU-T went for this.  Also a certain large(st) vendor had already put this in their implementation and it seems to make sense.
>
>Option 3 is idiot proof in the sense that it stops you from getting blackholes, but it also prevents you from building a topology which is perfectly valid.  If you read RFC 1195 then you see that it is allowable to put a dual router into an OSI-only area, because that dual router can forward OSI packets perfectly well.  Therefore option 3 is probably too restrictive.
>
>Thinking about an IPv6 migration for example.  If you have an existing IP4 network then it is perfectly valid to start adding IPv4 / IPv6 dual routers to it (or upgrading the ones that you have), one at a time.  It might take you months or years to upgrade them all.  Once you have upgraded them all then you can declare it to now be an IPv4 / IPv6 dual area and start forwarding IPv6 traffic on it too.  Option 1 and 2 allow this, but 3 doesn't.
>
>Of course if you go for automatic encapsulation then you don't even need to finish upgrading them all before you can start sending IPv6 :-)  See <http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-02.txt>http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-02.txt for more details.
>
>Philip
>
>
>
>----- Original Message -----
>From: Jeff Learman 
>Date: Wed, 18 Sep 2002 13:31:52 -0400 
>To: Les Ginsberg 
>Subject: RE: [Isis-wg] Protocols Supported TLV
>
>
>Good point, Les, but we should at least warn folks that this is
>not a plug-and-play situation.  I agree we shouldn't attempt to
>solve it, just point out the problem and mention that it can be
>worked around by configuring DR priorities.
>
>At 01:07 PM 9/18/2002, Les Ginsberg wrote:
>>At 11:45 AM 9/18/02 -0400, Jeff Learman wrote:
>>>>
>>>>One of the sticky points is what happens
>>>>with DIS election on a LAN - you can get into 
>>>>situations where not everyone can talk to the DIS,
>>>>or where you have dueling DISs.  It seems that 
>>>>discussion of this issue was left on the 
>>>>cutting room floor.  
>>>
>>>I'm surprised I let that happen, since this was my mantra for a while.
>>>I'll see if I can come up with a paragraph to fit in context.
>>
>>
>>Actually I believe we deliberately left out discussion of this issue because we knew that the ITU work and the associated auto-encapsulation draft work being done by Philip were addressing this issue and we didn't want to do a disservice by having either an incomplete discussion or a solution which differed from what was eventually settled on by the other work. Hence the statement in the section from <http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt>http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt which Jeff P quoted:
>>
>>    "However, the behavior of mixed networks that do not fol- 
>>     low these guidelines is not well defined."
>>
>>
>> Section 5.1 of Philip's latest draft  (draft-ietf-isis-auto-encap-02.txt) addresses this issue quite well.
>>
>>   Les
>-- 
>
>_______________________________________________
>Sign-up for your own FREE Personalized E-mail at <http://www.mail.com/?sr=signup>Mail.com
>_______________________________________________ Isis-wg mailing list Isis-wg@ietf.org https://www1.ietf.org/mailman/listinfo/isis-wg 

--=====================_1857112586==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<br>
Option 1 is what 1195 says to do.&nbsp; It works fine in networks
that<br>
follow 1195's topology restrictions (if you want protocol X in a<br>
subdomain, all routers in the subdomain must support protocol X).<br>
<br>
Option 2 allows the auto-encapsulation option.<br>
<br>
Either option 1 or option 2 work in a mixed network that has<br>
sufficient connectivity for all supported protocols but does not<br>
conform to 1195's restrictions.&nbsp; However, for either option to
work,<br>
DR priorities must be configured so that on any LAN with multiple<br>
protocols, the DR elected must support all protocols.&nbsp; (That's
an<br>
oversimplification, but it's sufficient.)&nbsp; By &quot;suffiently
connected&quot;<br>
I mean that there is a network path supporting protocol X between
any<br>
two entities that communicate using protocol X.&nbsp; For this to
work,<br>
multiprotocol routers have to run separate SPFs for each protocol,<br>
while assuming that all pseudonode LSPs support all protocols.<br>
<br>
Option 3 has serious disadvantages and no significant advantages.<br>
<br>
Regards,<br>
Jeff<br>
<br>
At 05:06 AM 9/19/2002, Philip Christian wrote:<br>
<br>
<blockquote type=cite cite>As Ruth says, there are three options open to
us (wrt Protocols Supported field in Hellos):-<br>
<br>
1. Ignore it.<br>
<br>
2. Only form adjacency if there is an overlap of one or more.<br>
<br>
3. Only form adjacency if there is exact match.<br>
<br>
Sadly there is no perfect answer...<br>
<br>
Option 1 always allows you to build a network, but a network designer has
to be careful as it will allow him to build blackholes into the
network.<br>
<br>
Option 2 only rejects totally useless adjacencies, and so this is why the
ITU-T went for this.&nbsp; Also a certain large(st) vendor had already
put this in their implementation and it seems to make sense.<br>
<br>
Option 3 is idiot proof in the sense that it stops you from getting
blackholes, but it also prevents you from building a topology which is
perfectly valid.&nbsp; If you read RFC 1195 then you see that it is
allowable to put a dual router into an OSI-only area, because that dual
router can forward OSI packets perfectly well.&nbsp; Therefore option 3
is probably too restrictive.<br>
<br>
Thinking about an IPv6 migration for example.&nbsp; If you have an
existing IP4 network then it is perfectly valid to start adding IPv4 /
IPv6 dual routers to it (or upgrading the ones that you have), one at a
time.&nbsp; It might take you months or years to upgrade them all.&nbsp;
Once you have upgraded them all then you can declare it to now be an IPv4
/ IPv6 dual area and start forwarding IPv6 traffic on it too.&nbsp;
Option 1 and 2 allow this, but 3 doesn't.<br>
<br>
Of course if you go for automatic encapsulation then you don't even need
to finish upgrading them all before you can start sending IPv6 :-)&nbsp;
See
<a href="http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-02.txt">http://www.ietf.org/internet-drafts/draft-ietf-isis-auto-encap-02.txt</a>
for more details.<br>
<br>
Philip<br>
<br>
<br>
<br>
----- Original Message -----<br>
From: Jeff Learman <br>
Date: Wed, 18 Sep 2002 13:31:52 -0400 <br>
To: Les Ginsberg <br>
Subject: RE: [Isis-wg] Protocols Supported TLV<br>
<br>
<br>
Good point, Les, but we should at least warn folks that this is<br>
not a plug-and-play situation.&nbsp; I agree we shouldn't attempt to<br>
solve it, just point out the problem and mention that it can be<br>
worked around by configuring DR priorities.<br>
<br>
At 01:07 PM 9/18/2002, Les Ginsberg wrote:<br>
<blockquote type=cite cite>At 11:45 AM 9/18/02 -0400, Jeff Learman wrote:<br>
<blockquote type=cite cite>&gt;<br>
&gt;One of the sticky points is what happens<br>
&gt;with DIS election on a LAN - you can get into <br>
&gt;situations where not everyone can talk to the DIS,<br>
&gt;or where you have dueling DISs.&nbsp; It seems that <br>
&gt;discussion of this issue was left on the <br>
&gt;cutting room floor.&nbsp; <br>
<br>
I'm surprised I let that happen, since this was my mantra for a while.<br>
I'll see if I can come up with a paragraph to fit in context.</blockquote><br>
<br>
Actually I believe we deliberately left out discussion of this issue because we knew that the ITU work and the associated auto-encapsulation draft work being done by Philip were addressing this issue and we didn't want to do a disservice by having either an incomplete discussion or a solution which differed from what was eventually settled on by the other work. Hence the statement in the section from <a href="http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt"><font color="#0000FF"><u>http://ietf.org/internet-drafts/draft-ietf-isis-interoperable-01.txt</a></u></font> which Jeff P quoted:<br>
<br>
&nbsp;&nbsp;&nbsp; &quot;However, the behavior of mixed networks that do not fol- <br>
&nbsp;&nbsp;&nbsp;&nbsp; low these guidelines is not well defined.&quot;<br>
<br>
<br>
&nbsp;Section 5.1 of Philip's latest draft&nbsp; (draft-ietf-isis-auto-encap-02.txt) addresses this issue quite well.<br>
<br>
&nbsp;&nbsp; Les</blockquote>-- <br>
<br>
_______________________________________________<br>
Sign-up for your own FREE Personalized E-mail at <a href="http://www.mail.com/?sr=signup"><font color="#0000FF">Mail.com</a><br>
</font>_______________________________________________ Isis-wg mailing list Isis-wg@ietf.org <a href="https://www1.ietf.org/mailman/listinfo/isis-wg" eudora="autourl">https://www1.ietf.org/mailman/listinfo/isis-wg</a> </blockquote></html>

--=====================_1857112586==_.ALT--

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 11:15:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09314
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 11:15:50 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JFEVv14898;
	Thu, 19 Sep 2002 11:14:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JFBHv14789
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 11:11:17 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09070
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 11:09:26 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 42E5718D3E5; Thu, 19 Sep 2002 08:11:13 -0700 (PDT)
To: mike shand <mshand@cisco.com>
Cc: isis <isis-wg@ietf.org>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling 
In-reply-to: Mail from mike shand <mshand@cisco.com> 
 dated Thu, 19 Sep 2002 10:28:36 BST
 <4.3.2.7.2.20020919101525.046de308@jaws.cisco.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020919151113.42E5718D3E5@prattle.redback.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 08:11:13 -0700


Mike,
	sounds good to me. thanks.

 ] At 09:55 18/09/2002 -0700, Naiming Shen wrote:
 ] >  ]
 ] >  ] There are those (Naiming?) who believe this is a bad idea, and I have 
 ] > some
 ] >  ] sympathy with that viewpoint. This says that since we have committed to
 ] >  ] doing restart, we ought to be able to extend the adjacency holding 
 ] > timer to
 ] >  ] give ourselves a bit more time to get it all done. So the spec now 
 ] > permits
 ] >  ] you to do this if you want to.
 ] >  ]
 ] >  ] So to summarise, the text your referred to says don't refresh, but you 
 ] > MAY
 ] >  ] refresh if you want to.
 ] >
 ] >I don't see the version 01.txt says that.
 ] 
 ] You are right. I thought I put that in, but in fact all I did was add the 
 ] last para at the end of 4.2 (just before 4.2.1)
 ] which says that you can send an RR clear IIH to refresh it if you want to.
 ] 
 ] How about replacing 4.2 a) "DO NOT refresh...." with
 ] 
 ] a) Do not change the state of the adjacency. It is an implementation choice 
 ] whether or not the holding time of the adjacency is refreshed. Not 
 ] refreshing the holding time preserves the intention of the original holding 
 ] time. Refreshing it may allow a longer grace period for the completion of 
 ] the restart process. Whichever option is chosen, the "remaining time" 
 ] transmitted according to (b) below MUST reflect the actual time after which 
 ] the adjacency will now expire.
 ] 
 ] 
 ] 
 ] 
 ] 
 ] >Could you change the draft
 ] >text to make this more clear? I basically see no reason we need to
 ] >"don't refresh". The closest thing I can related to this is to offer
 ] >a control by operators to limit the total number of graceful restart
 ] >a neighbor can have in a short period of time.
 ] >
 ] >thanks.
 ] >- Naiming
 ] 

- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 12:08:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12136
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 12:08:41 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JG7Dv19157;
	Thu, 19 Sep 2002 12:07:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JG1Iv18210
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 12:01:18 -0400
Received: from ws1-7.us4.outblaze.com (205-158-62-57.outblaze.com [205.158.62.57])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA11594
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 11:59:27 -0400 (EDT)
Received: (qmail 96599 invoked by uid 1001); 19 Sep 2002 16:00:41 -0000
Message-ID: <20020919160041.96598.qmail@iname.com>
Content-Type: text/html; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-7.us4.outblaze.com with http for
    philip.christian@iname.com; Thu, 19 Sep 2002 16:00:41 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: jlearman@cisco.com
Cc: rxc@nortelnetworks.com, isis-wg@ietf.org
Subject: RE: [Isis-wg] Protocols Supported TLV
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-7.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 16:00:41 +0000
Content-Transfer-Encoding: 7bit

<P>This is a different subject, about which Jeff and I have a difference of opinion (I think).&nbsp; I'm going to rise to the bait though :-)</P>
<P>The problem with protocol aware multi-SPF is that it is not compatible with auto-encap.&nbsp; Auto-encap actually relies on routers NOT being protocol aware, and blindly sending stuff towards the auto-encap routers, which of cause then forward packets that would have been lost if it wasn't for their dynamic tunnelling capability.</P>
<P>Shame that Jeff and I have come up with valid but non-compatible solutions to the same problem...&nbsp; Jeff's way is (in effect) how it is done with OSPF, with an OSPFv2 instance for the IPv4 and an OSPFv3 instance for the IPv6. Demonstrably that does work.</P>
<P>That said, you cannot safely have a protocol aware&nbsp;multi-SPF router in the same domain as a traditional RFC 1195 dual router, and then break the RFC 1195 topological rules.&nbsp; If you cannot break the topological rules, then what is the point in having multi-SPFs ?</P>
<P>I will explain.</P>
<P>If all of the routers in a domain are dual, then a mult-SPF dual router will come up with the same answer for both Proto-A and Proto-B destinations.&nbsp; All routers are dual and so the calculated shortest path must be the same.&nbsp; This is safe, but there is no point in multi-SPF in this scenario, you just don't need it.</P>
<P>If all the routers in a domain are NOT dual, then a multi-SPF dual router might calculate a different path for Proto-A to the one it calculates for Proto-B.&nbsp; In that same domain there might be another dual router that is vanilla RFC 1195.&nbsp; That router now calculates a different path for one or the other protos to what the the multi-SPF router calculated.</P>
<P>The result will be routing loops and blackholes as the vanilla dual and the multi-SPF dual came up with differing shortest paths.</P>
<P>The only ways that I can think of making multi-SPF useful is to actually put the two instances in two seperate areas; eg run proto-A in area 0001 and proto-B in area 0002, or, to say that every router in the area must have protocol aware SPF&nbsp;(unluckily this isn't backwards compatible with existing implementations).</P>
<P>The important point with auto-encap is that it does not alter the shortest path to any destination compared with that calculated by vanilla RFC 1195.&nbsp; For any destination an auto-encap router will come up with the same next hop as a normal RFC 1195 router.&nbsp; Thus we get backwards compatibility, and no loops.&nbsp; What auto-encap does is to send packets down the same shortest path that RFC 1195 / ISO 10589 would, but it alters the protocol of the packets so that they can make the journey without being dumped.</P>
<P>Philip<BR><BR>Snip</P>
<P>For this to work,<BR>multiprotocol routers have to run separate SPFs for each protocol,<BR>while assuming that all pseudonode LSPs support all protocols.<BR><BR>Regards,<BR>Jeff<BR><BR><A href="https://www1.ietf.org/mailman/listinfo/isis-wg" eudora="autourl">https://www1.ietf.org/mailman/listinfo/isis-wg</A> </P>
-- 
<p>_______________________________________________<br>
Sign-up for your own FREE Personalized E-mail at <font color="#0000FF"><a href="http://www.mail.com/?sr=signup" target="_new">Mail.com</a></font></p>

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 19 15:11:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19330
	for <isis-archive@lists.ietf.org>; Thu, 19 Sep 2002 15:11:51 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JJARv31651;
	Thu, 19 Sep 2002 15:10:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8JJ7mv31534
	for <isis-wg@optimus.ietf.org>; Thu, 19 Sep 2002 15:07:48 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19178
	for <isis-wg@ietf.org>; Thu, 19 Sep 2002 15:05:54 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8JJ7H7v002028;
	Thu, 19 Sep 2002 15:07:18 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-146.cisco.com [64.102.83.146])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAC45677;
	Thu, 19 Sep 2002 15:05:25 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020919145328.0226ad70@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Philip Christian" <philip.christian@iname.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported TLV
Cc: rxc@nortelnetworks.com, isis-wg@ietf.org
In-Reply-To: <20020919160041.96598.qmail@iname.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_1874825296==_.ALT"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 19 Sep 2002 15:04:05 -0400

--=====================_1874825296==_.ALT
Content-Type: text/plain; charset="us-ascii"


I agree with everything except:

>The only ways that I can think of making multi-SPF useful is to actually put the two instances in two seperate areas; eg run proto-A in area 0001 and proto-B in area 0002, or, to say that every router in the area must have protocol aware SPF (unluckily this isn't backwards compatible with existing implementations).

Multi-SPF is necessary when you have mixed areas that don't follow 1195
restrictions, but have sufficient connectivity for all communicating
pairs to reach each other over routers that support their protocol.

I'm not advocating this, I'm just stating it because it's true.
I don't even remember why we're discussing this, but since the
"options" arose, I felt it necessary to explain some details of the
options that weren't mentioned.

Regards,
Jeff

At 12:00 PM 9/19/2002, Philip Christian wrote:

>This is a different subject, about which Jeff and I have a difference of opinion (I think).  I'm going to rise to the bait though :-)
>
>The problem with protocol aware multi-SPF is that it is not compatible with auto-encap.  Auto-encap actually relies on routers NOT being protocol aware, and blindly sending stuff towards the auto-encap routers, which of cause then forward packets that would have been lost if it wasn't for their dynamic tunnelling capability.
>
>Shame that Jeff and I have come up with valid but non-compatible solutions to the same problem...  Jeff's way is (in effect) how it is done with OSPF, with an OSPFv2 instance for the IPv4 and an OSPFv3 instance for the IPv6. Demonstrably that does work.
>
>That said, you cannot safely have a protocol aware multi-SPF router in the same domain as a traditional RFC 1195 dual router, and then break the RFC 1195 topological rules.  If you cannot break the topological rules, then what is the point in having multi-SPFs ?
>
>I will explain.
>
>If all of the routers in a domain are dual, then a mult-SPF dual router will come up with the same answer for both Proto-A and Proto-B destinations.  All routers are dual and so the calculated shortest path must be the same.  This is safe, but there is no point in multi-SPF in this scenario, you just don't need it.
>
>If all the routers in a domain are NOT dual, then a multi-SPF dual router might calculate a different path for Proto-A to the one it calculates for Proto-B.  In that same domain there might be another dual router that is vanilla RFC 1195.  That router now calculates a different path for one or the other protos to what the the multi-SPF router calculated.
>
>The result will be routing loops and blackholes as the vanilla dual and the multi-SPF dual came up with differing shortest paths.
>
>The only ways that I can think of making multi-SPF useful is to actually put the two instances in two seperate areas; eg run proto-A in area 0001 and proto-B in area 0002, or, to say that every router in the area must have protocol aware SPF (unluckily this isn't backwards compatible with existing implementations).
>
>The important point with auto-encap is that it does not alter the shortest path to any destination compared with that calculated by vanilla RFC 1195.  For any destination an auto-encap router will come up with the same next hop as a normal RFC 1195 router.  Thus we get backwards compatibility, and no loops.  What auto-encap does is to send packets down the same shortest path that RFC 1195 / ISO 10589 would, but it alters the protocol of the packets so that they can make the journey without being dumped.
>
>Philip
>
>Snip
>
>For this to work,
>multiprotocol routers have to run separate SPFs for each protocol,
>while assuming that all pseudonode LSPs support all protocols.
>
>Regards,
>Jeff
>
>https://www1.ietf.org/mailman/listinfo/isis-wg 
>-- 
>
>_______________________________________________
>Sign-up for your own FREE Personalized E-mail at <http://www.mail.com/?sr=signup>Mail.com

--=====================_1874825296==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
<br>
I agree with everything except:<br>
<br>
<blockquote type=cite cite>The only ways that I can think of making
multi-SPF useful is to actually put the two instances in two seperate
areas; eg run proto-A in area 0001 and proto-B in area 0002, or, to say
that every router in the area must have protocol aware SPF (unluckily
this isn't backwards compatible with existing
implementations).</blockquote><br>
Multi-SPF is necessary when you have mixed areas that don't follow
1195<br>
restrictions, but have sufficient connectivity for all 
communicating<br>
pairs to reach each other over routers that support their protocol.<br>
<br>
I'm not advocating this, I'm just stating it because it's true.<br>
I don't even remember why we're discussing this, but since the<br>
&quot;options&quot; arose, I felt it necessary to explain some details of
the<br>
options that weren't mentioned.<br>
<br>
Regards,<br>
Jeff<br>
<br>
At 12:00 PM 9/19/2002, Philip Christian wrote:<br>
<br>
<blockquote type=cite cite>This is a different subject, about which Jeff
and I have a difference of opinion (I think).&nbsp; I'm going to rise to
the bait though :-)<br>
<br>
The problem with protocol aware multi-SPF is that it is not compatible
with auto-encap.&nbsp; Auto-encap actually relies on routers NOT being
protocol aware, and blindly sending stuff towards the auto-encap routers,
which of cause then forward packets that would have been lost if it
wasn't for their dynamic tunnelling capability.<br>
<br>
Shame that Jeff and I have come up with valid but non-compatible
solutions to the same problem...&nbsp; Jeff's way is (in effect) how it
is done with OSPF, with an OSPFv2 instance for the IPv4 and an OSPFv3
instance for the IPv6. Demonstrably that does work.<br>
<br>
That said, you cannot safely have a protocol aware multi-SPF router in
the same domain as a traditional RFC 1195 dual router, and then break the
RFC 1195 topological rules.&nbsp; If you cannot break the topological
rules, then what is the point in having multi-SPFs ?<br>
<br>
I will explain.<br>
<br>
If all of the routers in a domain are dual, then a mult-SPF dual router
will come up with the same answer for both Proto-A and Proto-B
destinations.&nbsp; All routers are dual and so the calculated shortest
path must be the same.&nbsp; This is safe, but there is no point in
multi-SPF in this scenario, you just don't need it.<br>
<br>
If all the routers in a domain are NOT dual, then a multi-SPF dual router
might calculate a different path for Proto-A to the one it calculates for
Proto-B.&nbsp; In that same domain there might be another dual router
that is vanilla RFC 1195.&nbsp; That router now calculates a different
path for one or the other protos to what the the multi-SPF router
calculated.<br>
<br>
The result will be routing loops and blackholes as the vanilla dual and
the multi-SPF dual came up with differing shortest paths.<br>
<br>
The only ways that I can think of making multi-SPF useful is to actually
put the two instances in two seperate areas; eg run proto-A in area 0001
and proto-B in area 0002, or, to say that every router in the area must
have protocol aware SPF (unluckily this isn't backwards compatible with
existing implementations).<br>
<br>
The important point with auto-encap is that it does not alter the
shortest path to any destination compared with that calculated by vanilla
RFC 1195.&nbsp; For any destination an auto-encap router will come up
with the same next hop as a normal RFC 1195 router.&nbsp; Thus we get
backwards compatibility, and no loops.&nbsp; What auto-encap does is to
send packets down the same shortest path that RFC 1195 / ISO 10589 would,
but it alters the protocol of the packets so that they can make the
journey without being dumped.<br>
<br>
Philip<br>
<br>
Snip<br>
<br>
For this to work,<br>
multiprotocol routers have to run separate SPFs for each protocol,<br>
while assuming that all pseudonode LSPs support all protocols.<br>
<br>
Regards,<br>
Jeff<br>
<br>
<a href="https://www1.ietf.org/mailman/listinfo/isis-wg" eudora="autourl">https://www1.ietf.org/mailman/listinfo/isis-wg</a>
<br>
-- <br>
<br>
_______________________________________________<br>
Sign-up for your own FREE Personalized E-mail at <a href="http://www.mail.com/?sr=signup"><font color="#0000FF">Mail.com</a></font></blockquote></html>

--=====================_1874825296==_.ALT--

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep 20 05:14:55 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA16881
	for <isis-archive@lists.ietf.org>; Fri, 20 Sep 2002 05:14:54 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8K94Fv17120;
	Fri, 20 Sep 2002 05:04:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8K91dv17046
	for <isis-wg@optimus.ietf.org>; Fri, 20 Sep 2002 05:01:39 -0400
Received: from ws1-1.us4.outblaze.com (205-158-62-49.outblaze.com [205.158.62.49])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA16625
	for <isis-wg@ietf.org>; Fri, 20 Sep 2002 04:59:48 -0400 (EDT)
Received: (qmail 14535 invoked by uid 1001); 20 Sep 2002 09:01:00 -0000
Message-ID: <20020920090100.14534.qmail@iname.com>
Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-1.us4.outblaze.com with http for
    philip.christian@iname.com; Fri, 20 Sep 2002 09:01:00 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: jlearman@cisco.com
Cc: rxc@nortelnetworks.com, isis-wg@ietf.org
Subject: RE: [Isis-wg] Protocols Supported TLV
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-1.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 20 Sep 2002 09:01:00 +0000
Content-Transfer-Encoding: 7bit

Jeff,
Do you mean something like this (view in courier)? :-

  OSI_ES--OSIonly--Dual--Dual--OSIonly--OSI_ES
                     ¦     ¦
                     ¦     ¦
  IP_host--IPonly--Dual--Dual--IPonly--IP_host   

Such a network doesn't follow RFC 1195 restrictions, but it will work.  Protocol aware SPF isn't "necessary" to make it work.

I will accept that there are other topologies which wouldn't work, and where multi-SPF could make it work.  However in such a network you would have to be very careful about putting in a vanilla RFC 1195 dual router, because you might easily introduce loops and blackholes.

My point is that Integrated IS-IS was architected right from the start to have a single SPF for multiple network-layer protocols.  If we try to unravel this fundamental principle ten years on then we are going to get in an awful mess.

The type of network that I show was documented as working back in 1994 in a draft.  Read case "A" of
http://www.watersprings.org/pub/id/draft-ietf-isis-opexp-01.txt

Philip



----- Original Message -----
From: Jeff Learman 
Date: Thu, 19 Sep 2002 15:04:05 -0400
To: "Philip Christian" 
Subject: RE: [Isis-wg] Protocols Supported TLV


I agree with everything except:


The only ways that I can think of making multi-SPF useful is to actually put the two instances in two seperate areas; eg run proto-A in area 0001 and proto-B in area 0002, or, to say that every router in the area must have protocol aware SPF (unluckily this isn't backwards compatible with existing implementations).

Multi-SPF is necessary when you have mixed areas that don't follow 1195
restrictions, but have sufficient connectivity for all communicating
pairs to reach each other over routers that support their protocol.

I'm not advocating this, I'm just stating it because it's true.
I don't even remember why we're discussing this, but since the
"options" arose, I felt it necessary to explain some details of the
options that weren't mentioned.

Regards,
Jeff

At 12:00 PM 9/19/2002, Philip Christian wrote:


This is a different subject, about which Jeff and I have a difference of opinion (I think).  I'm going to rise to the bait though :-)

The problem with protocol aware multi-SPF is that it is not compatible with auto-encap.  Auto-encap actually relies on routers NOT being protocol aware, and blindly sending stuff towards the auto-encap routers, which of cause then forward packets that would have been lost if it wasn't for their dynamic tunnelling capability.

Shame that Jeff and I have come up with valid but non-compatible solutions to the same problem...  Jeff's way is (in effect) how it is done with OSPF, with an OSPFv2 instance for the IPv4 and an OSPFv3 instance for the IPv6. Demonstrably that does work.

That said, you cannot safely have a protocol aware multi-SPF router in the same domain as a traditional RFC 1195 dual router, and then break the RFC 1195 topological rules.  If you cannot break the topological rules, then what is the point in having multi-SPFs ?

I will explain.

If all of the routers in a domain are dual, then a mult-SPF dual router will come up with the same answer for both Proto-A and Proto-B destinations.  All routers are dual and so the calculated shortest path must be the same.  This is safe, but there is no point in multi-SPF in this scenario, you just don't need it.

If all the routers in a domain are NOT dual, then a multi-SPF dual router might calculate a different path for Proto-A to the one it calculates for Proto-B.  In that same domain there might be another dual router that is vanilla RFC 1195.  That router now calculates a different path for one or the other protos to what the the multi-SPF router calculated.

The result will be routing loops and blackholes as the vanilla dual and the multi-SPF dual came up with differing shortest paths.

The only ways that I can think of making multi-SPF useful is to actually put the two instances in two seperate areas; eg run proto-A in area 0001 and proto-B in area 0002, or, to say that every router in the area must have protocol aware SPF (unluckily this isn't backwards compatible with existing implementations).

The important point with auto-encap is that it does not alter the shortest path to any destination compared with that calculated by vanilla RFC 1195.  For any destination an auto-encap router will come up with the same next hop as a normal RFC 1195 router.  Thus we get backwards compatibility, and no loops.  What auto-encap does is to send packets down the same shortest path that RFC 1195 / ISO 10589 would, but it alters the protocol of the packets so that they can make the journey without being dumped.

Philip

Snip

For this to work,
multiprotocol routers have to run separate SPFs for each protocol,
while assuming that all pseudonode LSPs support all protocols.

Regards,
Jeff

https://www1.ietf.org/mailman/listinfo/isis-wg 
-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep 20 12:08:05 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27702
	for <isis-archive@lists.ietf.org>; Fri, 20 Sep 2002 12:08:05 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KFu5v06759;
	Fri, 20 Sep 2002 11:56:05 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KFqav06698
	for <isis-wg@optimus.ietf.org>; Fri, 20 Sep 2002 11:52:36 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA26656
	for <isis-wg@ietf.org>; Fri, 20 Sep 2002 11:50:45 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8KE4sB1011182;
	Fri, 20 Sep 2002 10:04:54 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (rtp-vpn2-642.cisco.com [10.82.242.130])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAC63161;
	Fri, 20 Sep 2002 10:04:13 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020920095008.021cc6f8@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Philip Christian" <philip.christian@iname.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Protocols Supported TLV
Cc: rxc@nortelnetworks.com, isis-wg@ietf.org
In-Reply-To: <20020920090100.14534.qmail@iname.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id g8KFqav06699
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 20 Sep 2002 10:04:07 -0400
Content-Transfer-Encoding: 8bit


If by "protocol-aware SPF" you mean the same thing as "multi-SPF", then
I really shouldn't have disagreed with that paragraph I quoted.

My understanding was that there were implementations that used
multi-SPF, but I don't remember which, or why I got that impression,
other than that it was through discussion on this forum.  I don't
know whether Cisco routers use multi-SPF, for example.

You're right of course that all implementations in a mixed subdomain
would ave to support multi-SPF.  In the same vein, you have to be
equally careful in auto-encap not to have "vanilla 1195 IP-only" and
"vanilla OSI-only" routers on a LAN, because they will form
adjacencies between each other.  I think that will mess things up.

I'm not recommending that we add this to the interop document, by the way.

Tangentially, I do have some issues with auto-encap -- not for IP/OSI,
but for IPV4/V6.  Is it possible, with auto-encap, to explicitly control
where tunnel endpoints are allowed to exist?  This would be extremely
important in a real rollout of IPV6, because only certain platforms
will be able to do the tunneling at line rate.  Also, I think it will
be important to make sure that automatic tunneling doesn't happen when
there is a pure-native path that might be slightly longer than a mixed
path.  (If you reply to this you can change the subject accordingly.)

Note that this concern doesn't necessarily represent a Cisco position;
I haven't discussed it with anyone here.

Regards,
Jeff



At 05:01 AM 9/20/2002, Philip Christian wrote:
>Jeff,
>Do you mean something like this (view in courier)? :-
>
>  OSI_ES--OSIonly--Dual--Dual--OSIonly--OSI_ES
>                     ¦     ¦
>                     ¦     ¦
>  IP_host--IPonly--Dual--Dual--IPonly--IP_host   
>
>Such a network doesn't follow RFC 1195 restrictions, but it will work.  Protocol aware SPF isn't "necessary" to make it work.
>
>I will accept that there are other topologies which wouldn't work, and where multi-SPF could make it work.  However in such a network you would have to be very careful about putting in a vanilla RFC 1195 dual router, because you might easily introduce loops and blackholes.
>
>My point is that Integrated IS-IS was architected right from the start to have a single SPF for multiple network-layer protocols.  If we try to unravel this fundamental principle ten years on then we are going to get in an awful mess.
>
>The type of network that I show was documented as working back in 1994 in a draft.  Read case "A" of
>http://www.watersprings.org/pub/id/draft-ietf-isis-opexp-01.txt
>
>Philip
>
>
>
>----- Original Message -----
>From: Jeff Learman 
>Date: Thu, 19 Sep 2002 15:04:05 -0400
>To: "Philip Christian" 
>Subject: RE: [Isis-wg] Protocols Supported TLV
>
>
>I agree with everything except:
>
>
>The only ways that I can think of making multi-SPF useful is to actually put the two instances in two seperate areas; eg run proto-A in area 0001 and proto-B in area 0002, or, to say that every router in the area must have protocol aware SPF (unluckily this isn't backwards compatible with existing implementations).
>
>Multi-SPF is necessary when you have mixed areas that don't follow 1195
>restrictions, but have sufficient connectivity for all communicating
>pairs to reach each other over routers that support their protocol.
>
>I'm not advocating this, I'm just stating it because it's true.
>I don't even remember why we're discussing this, but since the
>"options" arose, I felt it necessary to explain some details of the
>options that weren't mentioned.
>
>Regards,
>Jeff
>
>At 12:00 PM 9/19/2002, Philip Christian wrote:
>
>
>This is a different subject, about which Jeff and I have a difference of opinion (I think).  I'm going to rise to the bait though :-)
>
>The problem with protocol aware multi-SPF is that it is not compatible with auto-encap.  Auto-encap actually relies on routers NOT being protocol aware, and blindly sending stuff towards the auto-encap routers, which of cause then forward packets that would have been lost if it wasn't for their dynamic tunnelling capability.
>
>Shame that Jeff and I have come up with valid but non-compatible solutions to the same problem...  Jeff's way is (in effect) how it is done with OSPF, with an OSPFv2 instance for the IPv4 and an OSPFv3 instance for the IPv6. Demonstrably that does work.
>
>That said, you cannot safely have a protocol aware multi-SPF router in the same domain as a traditional RFC 1195 dual router, and then break the RFC 1195 topological rules.  If you cannot break the topological rules, then what is the point in having multi-SPFs ?
>
>I will explain.
>
>If all of the routers in a domain are dual, then a mult-SPF dual router will come up with the same answer for both Proto-A and Proto-B destinations.  All routers are dual and so the calculated shortest path must be the same.  This is safe, but there is no point in multi-SPF in this scenario, you just don't need it.
>
>If all the routers in a domain are NOT dual, then a multi-SPF dual router might calculate a different path for Proto-A to the one it calculates for Proto-B.  In that same domain there might be another dual router that is vanilla RFC 1195.  That router now calculates a different path for one or the other protos to what the the multi-SPF router calculated.
>
>The result will be routing loops and blackholes as the vanilla dual and the multi-SPF dual came up with differing shortest paths.
>
>The only ways that I can think of making multi-SPF useful is to actually put the two instances in two seperate areas; eg run proto-A in area 0001 and proto-B in area 0002, or, to say that every router in the area must have protocol aware SPF (unluckily this isn't backwards compatible with existing implementations).
>
>The important point with auto-encap is that it does not alter the shortest path to any destination compared with that calculated by vanilla RFC 1195.  For any destination an auto-encap router will come up with the same next hop as a normal RFC 1195 router.  Thus we get backwards compatibility, and no loops.  What auto-encap does is to send packets down the same shortest path that RFC 1195 / ISO 10589 would, but it alters the protocol of the packets so that they can make the journey without being dumped.
>
>Philip
>
>Snip
>
>For this to work,
>multiprotocol routers have to run separate SPFs for each protocol,
>while assuming that all pseudonode LSPs support all protocols.
>
>Regards,
>Jeff
>
>https://www1.ietf.org/mailman/listinfo/isis-wg 
>-- 
>__________________________________________________________
>Sign-up for your own FREE Personalized E-mail at Mail.com
>http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep 20 13:39:27 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA01484
	for <isis-archive@lists.ietf.org>; Fri, 20 Sep 2002 13:39:27 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KHSdv12402;
	Fri, 20 Sep 2002 13:28:39 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8KHPlv12289
	for <isis-wg@optimus.ietf.org>; Fri, 20 Sep 2002 13:25:47 -0400
Received: from ws1-7.us4.outblaze.com (205-158-62-57.outblaze.com [205.158.62.57])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA00662
	for <isis-wg@ietf.org>; Fri, 20 Sep 2002 13:23:54 -0400 (EDT)
Received: (qmail 66311 invoked by uid 1001); 20 Sep 2002 17:25:12 -0000
Message-ID: <20020920172512.66310.qmail@iname.com>
Content-Type: text/plain; charset="iso-8859-1"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-7.us4.outblaze.com with http for
    philip.christian@iname.com; Fri, 20 Sep 2002 17:25:12 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: jlearman@cisco.com
Cc: isis-wg@ietf.org
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-7.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] Auto-encap discussion
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 20 Sep 2002 17:25:12 +0000
Content-Transfer-Encoding: 7bit

Comments inline
----- Original Message -----
From: Jeff Learman <jlearman@cisco.com>
Date: Fri, 20 Sep 2002 10:04:07 -0400
To: "Philip Christian" <philip.christian@iname.com>
Subject: RE: [Isis-wg] Protocols Supported TLV


> 
> If by "protocol-aware SPF" you mean the same thing as "multi-SPF", then
> I really shouldn't have disagreed with that paragraph I quoted.

An IS could be protocol aware even though it is IPv4 only.  It could choose to ignore other ISs that don't support IPv4 so it is protocol aware, but it is only IPv4 so it isn't multi-SPF.

It therefore follows that if a router is a multi-protocol router, and has  protocol aware SPF, then actually it is going to be multi-SPF too...

This would all of course be contradictory to RFC 1195 (which explicitly forbids protocol aware SPF), and wouldn't interwork with auto-encap, and it can cause loops, so I'll fight such a suggestion when I see it :-)
> 
> My understanding was that there were implementations that used
> multi-SPF, but I don't remember which, or why I got that impression,
> other than that it was through discussion on this forum.  I don't
> know whether Cisco routers use multi-SPF, for example.

Not any that I lab tested.  The ones (Cisco IOS 11 and 12 I think) that I tested with auto-encap worked perfectly.  I was only doing IPv4 and OSI though.

> 
> You're right of course that all implementations in a mixed subdomain
> would ave to support multi-SPF.  In the same vein, you have to be
> equally careful in auto-encap not to have "vanilla 1195 IP-only" and
> "vanilla OSI-only" routers on a LAN, because they will form
> adjacencies between each other.  I think that will mess things up.

It will indeed mess things up.  For this reason the ITU-T document mandates that you only form an adjacency if there is at least an overlap.  This applies to all IP-only ISs.  Therefore you can't have an adjacency between an IP-only and an OSI-only, or between an IPv4-only and an IPv6-only.

Sadly this only applies to ITU-T multiplexers, it isn't retrospectively applied to internet type routers.  The draft does explain this.  Sadly it isn't idiot proof (hey, Integrated IS-IS never was). You can manually get around it by disabling adjacencies or just not connecting it that way.

The pseudonode election is also messy.  I'm confident that the draft gets it as good as it's ever going to get without sacrificing backwards compatibility (which is the whole point of auto-encap isn't it).
> 
> I'm not recommending that we add this to the interop document, by the way.
> 
> Tangentially, I do have some issues with auto-encap -- not for IP/OSI,
> but for IPV4/V6.  Is it possible, with auto-encap, to explicitly control
> where tunnel endpoints are allowed to exist?  This would be extremely
> important in a real rollout of IPV6, because only certain platforms
> will be able to do the tunneling at line rate.  Also, I think it will
> be important to make sure that automatic tunneling doesn't happen when
> there is a pure-native path that might be slightly longer than a mixed
> path.  (If you reply to this you can change the subject accordingly.)

Because it doesn't mess with SPF, and because IS-IS metrics are IS-IS metrics, not IP or OSI ones, this isn't easily possible, but I suppose that it could be done.

Routers that can terminate dynamic tunnels advertise the fact, and then a router that needs to encap can choose any that is on the shortest path.  Currently the draft says the first, but it could be any.  As the TLV was written in an extensible way we could now, at a later time put some sort or preference in there.  In this way a router could say that it is good at terminating dynamic tunnels, or that it can but only as a last resort.  That is actually quite a nice add on.
> 
> Note that this concern doesn't necessarily represent a Cisco position;
> I haven't discussed it with anyone here.

I have :-)

Philip
-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 21 09:21:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10902
	for <isis-archive@lists.ietf.org>; Sat, 21 Sep 2002 09:21:19 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LDIvv07545;
	Sat, 21 Sep 2002 09:18:58 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LDFHv07491
	for <isis-wg@optimus.ietf.org>; Sat, 21 Sep 2002 09:15:17 -0400
Received: from mta2 ([61.144.161.16])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA10778
	for <isis-wg@ietf.org>; Sat, 21 Sep 2002 09:13:24 -0400 (EDT)
Received: from mta2 (localhost [127.0.0.1])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2S00LPPI5OMS@mta2.huawei.com> for isis-wg@ietf.org;
 Sat, 21 Sep 2002 21:15:24 +0800 (CST)
Received: from mailin.huawei.com ([10.18.1.252])
 by mta2.huawei.com (iPlanet Messaging Server 5.2 HotFix 0.7 (built Jun 26
 2002)) with ESMTP id <0H2S00L2SI5NUP@mta2.huawei.com> for isis-wg@ietf.org;
 Sat, 21 Sep 2002 21:15:24 +0800 (CST)
Received: from CL5002VJAMRIT ([10.18.4.151]) by          mailin.huawei.com
 (Netscape Messaging Server 4.15) with ESMTP id          H2SI7800.20V; Sat,
 21 Sep 2002 21:16:20 +0800
From: Vijay Amrit Agrawal <vijayamrit@huawei.com>
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling
To: isis <isis-wg@ietf.org>
Cc: Naiming Shen <naiming@redback.com>, mike shand <mshand@cisco.com>
Message-id: <000c01c26172$ad1a4060$9704120a@in.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
Content-type: text/plain; charset=gb2312
Content-transfer-encoding: 7BIT
X-Priority: 3
X-MSMail-priority: Normal
References: <20020919092013.C63D24BA214@prattle.redback.com>
 <00de01c25fc8$b1c99030$9704120a@in.huawei.com>
Content-Transfer-Encoding: 7BIT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 21 Sep 2002 18:57:46 +0530
Content-Transfer-Encoding: 7BIT

Hi All,

Since I did not receive any more comments on this I am assuming the
summarization captures the intention of the draft.
Will it better if we include these two statements explicitly in the draft.
i)Neighbor SHOULD respond with complete CSNP on receiving a hello with RR
bit set, even when adjacency is not up.
ii)Router may send IIH with RR bit set even when starting for first time, to
request neighbor to send complete CSNP.

According to the draft RA bit should be set even when adjacency is not up
(see page 4, first paragraph after point "c".) If this is the case what
should the remaining time set to? My take is set the remaining time to zero,
so restarting router uses zero value to understand adjacency is not up.

Thanks everyone for their responses.
Regards,
Vijay Amrit Agrawal

----- Original Message -----
From: "Vijay Amrit Agrawal" <vijayamrit@huawei.com>
To: "isis" <isis-wg@ietf.org>
Cc: "Naiming Shen" <naiming@redback.com>; "mike shand" <mshand@cisco.com>
Sent: Thursday, September 19, 2002 4:08 PM
Subject: Re: [Isis-wg] Questions on IS-IS Restart Signalling


> Let me try to summarize to make sure I understand it:
>
> i) On starting for FIRST time, the starting router sends IIH with RR bit
> set. This will cause the neighbor to send CSNP (for broadcast one would
have
> got the CSNP anyway but for p2p CSNP is ensured because of timer T1.) This
> CSNP will help the starting router to realize when it has synchronized
with
> the neighbor. The starting router should stop sending packet with RR bit
set
> on receiving CSNP and not wait for RA.
>
> ii)Neighbor should send CSNP packet on receiving packet with RR bit set
> (even if the adjacency is not up). Neighbor should not send IIH with RA
bit
> set if the adjacency is not up.
>
>
>
>
>

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 21 15:18:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16148
	for <isis-archive@lists.ietf.org>; Sat, 21 Sep 2002 15:18:41 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LJG3v21127;
	Sat, 21 Sep 2002 15:16:04 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LJCHv21077
	for <isis-wg@optimus.ietf.org>; Sat, 21 Sep 2002 15:12:17 -0400
Received: from tahoe.sj.allegronetworks.com (tahoe.allegronetworks.com [63.115.58.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16039
	for <isis-wg@ietf.org>; Sat, 21 Sep 2002 15:10:22 -0400 (EDT)
Received: by tahoe.allegronetworks.com with Internet Mail Service (5.5.2653.19)
	id <THMN004Y>; Sat, 21 Sep 2002 12:11:41 -0700
Message-ID: <B4DFCB7CDE2DD4118F690008C786941604F233AB@tahoe.allegronetworks.com>
From: Chris Hopps <chopps@allegronetworks.com>
To: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Isis-wg] isisSysTEEnabled in ISIS MIB
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 21 Sep 2002 12:11:41 -0700

Shouldn't we have an isisSysL1TEEnabled and isisSysL2TEEnabled, instead of a
single isisSysTEEnabled entry? TE can be enabled on either or both levels.

Chris.
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 21 15:19:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16171
	for <isis-archive@lists.ietf.org>; Sat, 21 Sep 2002 15:19:49 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LJJ8v21212;
	Sat, 21 Sep 2002 15:19:08 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LJDmv21105
	for <isis-wg@optimus.ietf.org>; Sat, 21 Sep 2002 15:13:48 -0400
Received: from tahoe.sj.allegronetworks.com (tahoe.allegronetworks.com [63.115.58.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16055
	for <isis-wg@ietf.org>; Sat, 21 Sep 2002 15:11:54 -0400 (EDT)
Received: by tahoe.allegronetworks.com with Internet Mail Service (5.5.2653.19)
	id <THMN004Z>; Sat, 21 Sep 2002 12:13:15 -0700
Message-ID: <B4DFCB7CDE2DD4118F690008C786941604F233AC@tahoe.allegronetworks.com>
From: Chris Hopps <chopps@allegronetworks.com>
To: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Isis-wg] older archives
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 21 Sep 2002 12:13:15 -0700

Where are the older archives for this mailing list?

Archive: ftp://ftp.ietf.org/ietf-mail-archive/isis-wg

only has the last couple months.

Thanks,
Chris.
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 21 17:26:53 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17645
	for <isis-archive@lists.ietf.org>; Sat, 21 Sep 2002 17:26:52 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LLPWv26144;
	Sat, 21 Sep 2002 17:25:32 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8LLMZv26091
	for <isis-wg@optimus.ietf.org>; Sat, 21 Sep 2002 17:22:35 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17543
	for <isis-wg@ietf.org>; Sat, 21 Sep 2002 17:20:40 -0400 (EDT)
Received: from net4u.ch (adsl-63-200-52-122.dsl.snfc21.pacbell.net [63.200.52.122])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g8LLMOq27560;
	Sat, 21 Sep 2002 23:22:25 +0200
Message-ID: <3D8CDA0F.4010204@net4u.ch>
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Chris Hopps <chopps@allegronetworks.com>
CC: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] older archives
References: <B4DFCB7CDE2DD4118F690008C786941604F233AC@tahoe.allegronetworks.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 21 Sep 2002 13:43:59 -0700
Content-Transfer-Encoding: 7bit

Chris Hopps wrote:

>Where are the older archives for this mailing list?
>
>Archive: ftp://ftp.ietf.org/ietf-mail-archive/isis-wg
>
>only has the last couple months.
>
>Thanks,
>
I begged and pledged for them to be put onto the new server, so far
without success.

    thanks

    -- tony


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sun Sep 22 11:21:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09337
	for <isis-archive@lists.ietf.org>; Sun, 22 Sep 2002 11:21:11 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8MFFuv13329;
	Sun, 22 Sep 2002 11:15:57 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8MFCvv13281
	for <isis-wg@optimus.ietf.org>; Sun, 22 Sep 2002 11:12:57 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09238
	for <isis-wg@ietf.org>; Sun, 22 Sep 2002 11:11:04 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8MFCduC000033;
	Sun, 22 Sep 2002 11:12:40 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (rtp-vpn2-197.cisco.com [10.82.240.197])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAC90200;
	Sun, 22 Sep 2002 11:12:21 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020922111142.0218c888@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: prz@net4u.ch
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] older archives
Cc: Chris Hopps <chopps@allegronetworks.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
In-Reply-To: <3D8CDA0F.4010204@net4u.ch>
References: <B4DFCB7CDE2DD4118F690008C786941604F233AC@tahoe.allegronetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sun, 22 Sep 2002 11:12:19 -0400


To whom may we express our desire to see this done, to help support
your claim that it's important?

Thanks,
Jeff

At 04:43 PM 9/21/2002, Tony Przygienda wrote:
>Chris Hopps wrote:
>
>>Where are the older archives for this mailing list?
>>
>>Archive: ftp://ftp.ietf.org/ietf-mail-archive/isis-wg
>>
>>only has the last couple months.
>>
>>Thanks,
>I begged and pledged for them to be put onto the new server, so far
>without success.
>
>   thanks
>
>   -- tony
>
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 10:37:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10795
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 10:37:47 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NEOwv13843;
	Mon, 23 Sep 2002 10:24:59 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NEJfv13630
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 10:19:41 -0400
Received: from titanium ([217.167.198.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA10103
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 10:17:47 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17tU3k-0001WH-00
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 16:19:36 +0200
Message-ID: <87lm5srdpr.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: isis-wg@ietf.org
Subject: Re: [Isis-wg] isisSysTEEnabled in ISIS MIB
In-Reply-To: <B4DFCB7CDE2DD4118F690008C786941604F233AB@tahoe.allegronetworks.com>
References: <B4DFCB7CDE2DD4118F690008C786941604F233AB@tahoe.allegronetworks.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 16:18:56 +0200

> Shouldn't we have an isisSysL1TEEnabled and isisSysL2TEEnabled, instead of a
> single isisSysTEEnabled entry? TE can be enabled on either or both levels.

	I agree with it.

								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 11:14:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA12328
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 11:14:28 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NF3Mv16123;
	Mon, 23 Sep 2002 11:03:22 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NF0Ev16004
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 11:00:14 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11582
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 10:58:20 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A743C5@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: isis-wg@ietf.org
Subject: RE: [Isis-wg] isisSysTEEnabled in ISIS MIB
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 10:59:38 -0400

> > Shouldn't we have an isisSysL1TEEnabled and 
> isisSysL2TEEnabled, instead of a
> > single isisSysTEEnabled entry? TE can be enabled on either 
> or both levels.
> 
> 	I agree with it.
> 
> 								kay

Looking at this, we have a number of system parameters
that have levels.  They are currently not very well
organized.  I propose splitting out a new object
which is indexed by System ID and Level, and 
which holds things like TE Enabled and

            isisSysOrigL2LSPBuffSize
            isisSysMinL2LSPGenInt
            isisSysL2MetricStyle
            isisSysL2SPFConsiders

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 14:18:44 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19496
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 14:18:44 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NIGqv27749;
	Mon, 23 Sep 2002 14:16:53 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NID1v27646
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 14:13:01 -0400
Received: from titanium ([217.167.198.98])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19288
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 14:11:05 -0400 (EDT)
Received: from titanium ([127.0.0.1] helo=titanium.ipinfusion.com)
	by titanium with esmtp (Exim 3.35 #1 (Debian))
	id 17tXhX-0002Rh-00
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 20:12:55 +0200
Message-ID: <87fzw0r2x2.wl@ipinfusion.com>
From: Noguchi Kay <kay@ipinfusion.com>
To: isis-wg@ietf.org
Subject: Re: [Isis-wg] isisSysTEEnabled in ISIS MIB
In-Reply-To: <EB5FFC72F183D411B38200062957342902A743C5@r2d2.axiowave.com>
References: <EB5FFC72F183D411B38200062957342902A743C5@r2d2.axiowave.com>
User-Agent: Wanderlust/2.8.1 (Something) Emacs/21.2 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 20:12:09 +0200

> > > Shouldn't we have an isisSysL1TEEnabled and 
> > isisSysL2TEEnabled, instead of a
> > > single isisSysTEEnabled entry? TE can be enabled on either 
> > or both levels.
> > 
> > 	I agree with it.
> > 
> > 								kay
> 
> Looking at this, we have a number of system parameters
> that have levels.  They are currently not very well
> organized.  I propose splitting out a new object
> which is indexed by System ID and Level, and 
> which holds things like TE Enabled and
> 
>             isisSysOrigL2LSPBuffSize
>             isisSysMinL2LSPGenInt
>             isisSysL2MetricStyle
>             isisSysL2SPFConsiders

	I also agree with this.

								kay
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 15:29:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21657
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 15:29:47 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NJHCv31613;
	Mon, 23 Sep 2002 15:17:12 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NJDev31543
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 15:13:40 -0400
Received: from rchss001.chiaro.com (rchss001.chiaro.com [63.88.196.81])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA21155
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 15:11:45 -0400 (EDT)
Received: (qmail 9331 invoked from network); 23 Sep 2002 19:04:06 -0000
Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81)
  by rchss001.chiaro.com with SMTP; 23 Sep 2002 19:04:06 -0000
Received: by MAIL with Internet Mail Service (5.5.2653.19)
	id <SQ62BR86>; Mon, 23 Sep 2002 14:12:47 -0500
Message-ID: <F69EB380D594D611BBEA00065B3F14B44E987B@MAIL>
From: Laura Liu <lliu@chiaro.com>
To: Jeff Parker <jparker@axiowave.com>, isis-wg@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary"
Subject: [Isis-wg] isisRedistributeAddrTable in mib09
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 14:12:43 -0500

--=_IS_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"

Hi Jeff,

Mib09 introduces isisRredistributeAddrTable, from the definition, it
displays the routes redistributed from L2 into L1. If a router configures
redistribution L1 routes to another area's L1, how to display those route
states in mib?

thanks,

Laura




--=_IS_MIME_Boundary
Content-Type: text/plain;charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

----------------------------------------- (on rchss001)

This e-mail and any files transmitted with it are the property
of Chiaro Networks, Ltd., and may contain confidential and 
privileged material for the sole use of the intended recipient(s)
to whom this e-mail is addressed. If you are not one of the named
recipient(s), or otherwise have reason to believe that you have 
received this message in error, please notify the sender and 
delete all copies from your system.  Any other use, retention, 
dissemination, forwarding, printing or copying of this e-mail is 
strictly prohibited.


---------------------------------------------------------

--=_IS_MIME_Boundary--
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 15:38:29 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21946
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 15:38:29 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NJSOv32111;
	Mon, 23 Sep 2002 15:28:24 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NJPWv32032
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 15:25:32 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21497
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 15:23:37 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A743D2@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Laura Liu'" <lliu@chiaro.com>, Jeff Parker <jparker@axiowave.com>,
        isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: isisRedistributeAddrTable in mib09
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 15:24:47 -0400

> Hi Jeff,
> 
> Mib09 introduces isisRredistributeAddrTable, from the definition, it
> displays the routes redistributed from L2 into L1. If a 
> router configures
> redistribution L1 routes to another area's L1, how to display 
> those route
> states in mib?
> 
> thanks,
> 
> Laura

[For those that might grep for it, that is isisRedistributeAddrTable]

I'm not sure what the question is.  Is it to find out which
routes were redistributed this way, or to find out which
rules fired?

In the parallel L1 to L2 Summary Address Table, there is
no indication of which summaries are being used.  
And there is no table today of the IP Route Table.  
So neither function has been supported in the past.
(Though there is provision for "Manual" addresses)

We could discuss adding such funcationality, but this
shades from the management/monitoring side to the 
bits and bytes side.  

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 16:11:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA23109
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 16:11:02 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NK9Fv02473;
	Mon, 23 Sep 2002 16:09:15 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NK6Ev01852
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 16:06:14 -0400
Received: from rchss001.chiaro.com (rchss001.chiaro.com [63.88.196.81])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA22942
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 16:04:18 -0400 (EDT)
Received: (qmail 10740 invoked from network); 23 Sep 2002 19:55:37 -0000
Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81)
  by rchss001.chiaro.com with SMTP; 23 Sep 2002 19:55:37 -0000
Received: by MAIL with Internet Mail Service (5.5.2653.19)
	id <SQ62BSF6>; Mon, 23 Sep 2002 15:04:17 -0500
Message-ID: <F69EB380D594D611BBEA00065B3F14B44E98A4@MAIL>
From: Laura Liu <lliu@chiaro.com>
To: Jeff Parker <jparker@axiowave.com>, isis-wg@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary"
Subject: [Isis-wg] RE: isisRedistributeAddrTable in mib09
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 15:04:13 -0500

--=_IS_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"

To better state my question and for discussing purpose, should we add
another table to monitor the routes redistributed from L1 to another area's
L1? It is parallel to L2 to L1 leaking.

Laura

-----Original Message-----
From: Jeff Parker [mailto:jparker@axiowave.com]
Sent: Monday, September 23, 2002 2:25 PM
To: 'Laura Liu'; Jeff Parker; isis-wg@ietf.org
Subject: RE: isisRedistributeAddrTable in mib09


> Hi Jeff,
> 
> Mib09 introduces isisRredistributeAddrTable, from the definition, it
> displays the routes redistributed from L2 into L1. If a 
> router configures
> redistribution L1 routes to another area's L1, how to display 
> those route
> states in mib?
> 
> thanks,
> 
> Laura

[For those that might grep for it, that is isisRedistributeAddrTable]

I'm not sure what the question is.  Is it to find out which
routes were redistributed this way, or to find out which
rules fired?

In the parallel L1 to L2 Summary Address Table, there is
no indication of which summaries are being used.  
And there is no table today of the IP Route Table.  
So neither function has been supported in the past.
(Though there is provision for "Manual" addresses)

We could discuss adding such funcationality, but this
shades from the management/monitoring side to the 
bits and bytes side.  

- jeff parker
--=_IS_MIME_Boundary
Content-Type: text/plain;charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

----------------------------------------- (on rchss001)

This e-mail and any files transmitted with it are the property
of Chiaro Networks, Ltd., and may contain confidential and 
privileged material for the sole use of the intended recipient(s)
to whom this e-mail is addressed. If you are not one of the named
recipient(s), or otherwise have reason to believe that you have 
received this message in error, please notify the sender and 
delete all copies from your system.  Any other use, retention, 
dissemination, forwarding, printing or copying of this e-mail is 
strictly prohibited.


---------------------------------------------------------

--=_IS_MIME_Boundary--
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 17:09:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25081
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 17:09:39 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NL8Zv06406;
	Mon, 23 Sep 2002 17:08:35 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NL55v05760
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 17:05:05 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA24902
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 17:03:09 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A743DC@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "ISIS-WG (E-mail)" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] isisSysTEEnabled in ISIS MIB
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 17:04:27 -0400

I have rev'd the mib (torn out L1 or L2 specific info in the system table
and built a new SystemLevelTable to hold these things).  As a side effect,
we can now set TE at L1 and/or L2.  

I can send copies to interested parties, but would rather not subject
the list to a MIB Megabyte Moment.  

- jeff parker
- axiowave networks
- It's tough to make predictions, especially about the future.
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 17:28:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25778
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 17:28:15 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NLRKv07235;
	Mon, 23 Sep 2002 17:27:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NLOpv07128
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 17:24:51 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA25592
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 17:22:54 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A743DD@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Laura Liu'" <lliu@chiaro.com>, Jeff Parker <jparker@axiowave.com>,
        isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: isisRedistributeAddrTable in mib09
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 17:23:57 -0400

> To better state my question and for discussing purpose, should we add
> another table to monitor the routes redistributed from L1 to 
> another area's
> L1? It is parallel to L2 to L1 leaking.
> 
> Laura
 
Laura -
	I think this is really L1 to L2 to L1 leaking, and is 
thus covered by the Summary Address Table and the new
Redistribution Table.  
	If you find this is not ample, or the coverage we
give does not give you enough control, I'll be happy to
discuss it more on or off the list.

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 23 18:16:03 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27465
	for <isis-archive@lists.ietf.org>; Mon, 23 Sep 2002 18:16:03 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NMESv09928;
	Mon, 23 Sep 2002 18:14:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8NMANv09803
	for <isis-wg@optimus.ietf.org>; Mon, 23 Sep 2002 18:10:23 -0400
Received: from psg.com (smmsp@psg.com [147.28.0.62])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA27168
	for <isis-wg@ietf.org>; Mon, 23 Sep 2002 18:08:26 -0400 (EDT)
Received: from psg.com ([147.28.0.62] helo=127.0.0.1)
	by psg.com with esmtp (Exim 3.36 #1)
	id 17tbP8-000Hfh-00; Mon, 23 Sep 2002 15:10:10 -0700
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.51) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <11296373537.20020923150813@psg.com>
To: Jeff Learman <jlearman@cisco.com>
CC: prz@net4u.ch, Chris Hopps <chopps@allegronetworks.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] older archives
In-Reply-To: <4.3.2.7.2.20020922111142.0218c888@dingdong.cisco.com>
References: 
 <B4DFCB7CDE2DD4118F690008C786941604F233AC@tahoe.allegronetworks.com>
 <4.3.2.7.2.20020922111142.0218c888@dingdong.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 23 Sep 2002 15:08:13 -0700
Content-Transfer-Encoding: 7bit


To your friendly ADs, who, though kicked some folks,
apparently haven't kicked enough >-|
I'll escalate this as much as I can...

-- 
Alex

Sunday, September 22, 2002, 8:12:19 AM, Jeff Learman wrote:

> To whom may we express our desire to see this done, to help support
> your claim that it's important?

> Thanks,
> Jeff

> At 04:43 PM 9/21/2002, Tony Przygienda wrote:
>>Chris Hopps wrote:
>>
>>>Where are the older archives for this mailing list?
>>>
>>>Archive: ftp://ftp.ietf.org/ietf-mail-archive/isis-wg
>>>
>>>only has the last couple months.
>>>
>>>Thanks,
>>I begged and pledged for them to be put onto the new server, so far
>>without success.
>>
>>   thanks
>>
>>   -- tony


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 24 09:52:28 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA27462
	for <isis-archive@lists.ietf.org>; Tue, 24 Sep 2002 09:52:28 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ODmdv01028;
	Tue, 24 Sep 2002 09:48:40 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8ODjiv00960
	for <isis-wg@optimus.ietf.org>; Tue, 24 Sep 2002 09:45:44 -0400
Received: from rchss001.chiaro.com (rchss001.chiaro.com [63.88.196.81])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA27076
	for <isis-wg@ietf.org>; Tue, 24 Sep 2002 09:43:50 -0400 (EDT)
Received: (qmail 24445 invoked from network); 24 Sep 2002 13:36:06 -0000
Received: from rchss001.chiaro.com (HELO mail.chiaro.com) (63.88.196.81)
  by rchss001.chiaro.com with SMTP; 24 Sep 2002 13:36:06 -0000
Received: by MAIL with Internet Mail Service (5.5.2653.19)
	id <SQ62B4NL>; Tue, 24 Sep 2002 08:44:36 -0500
Message-ID: <F69EB380D594D611BBEA00065B3F14B44E9978@MAIL>
From: Laura Liu <lliu@chiaro.com>
To: Jeff Parker <jparker@axiowave.com>, isis-wg@ietf.org
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-type: multipart/mixed; boundary="=_IS_MIME_Boundary"
Subject: [Isis-wg] RE: isisRedistributeAddrTable in mib09
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 24 Sep 2002 08:44:36 -0500

--=_IS_MIME_Boundary
Content-Type: text/plain;
	charset="iso-8859-1"

Jeff,

My question was triggered by the discussion on the mailing list a while ago
about up/down bit referring to "IS-IS extensions for Traffic Engineering"
draft v.04 section 5.1:

"If a prefix is advertised from an area to another area at the same level,
then the up/down bit shall be set to 1. This situation can arise when a
router implements multiple virtual routers at the same level, but in
different areas.".

Can we use isisRedistributeAddrTable for all the up/down bit set to 1
routes? 

regards,
Laura 

-----Original Message-----
From: Jeff Parker [mailto:jparker@axiowave.com]
Sent: Monday, September 23, 2002 4:24 PM
To: 'Laura Liu'; Jeff Parker; isis-wg@ietf.org
Subject: RE: isisRedistributeAddrTable in mib09


> To better state my question and for discussing purpose, should we add
> another table to monitor the routes redistributed from L1 to 
> another area's
> L1? It is parallel to L2 to L1 leaking.
> 
> Laura
 
Laura -
	I think this is really L1 to L2 to L1 leaking, and is 
thus covered by the Summary Address Table and the new
Redistribution Table.  
	If you find this is not ample, or the coverage we
give does not give you enough control, I'll be happy to
discuss it more on or off the list.

- jeff parker
--=_IS_MIME_Boundary
Content-Type: text/plain;charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

----------------------------------------- (on rchss001)

This e-mail and any files transmitted with it are the property
of Chiaro Networks, Ltd., and may contain confidential and 
privileged material for the sole use of the intended recipient(s)
to whom this e-mail is addressed. If you are not one of the named
recipient(s), or otherwise have reason to believe that you have 
received this message in error, please notify the sender and 
delete all copies from your system.  Any other use, retention, 
dissemination, forwarding, printing or copying of this e-mail is 
strictly prohibited.


---------------------------------------------------------

--=_IS_MIME_Boundary--
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Tue Sep 24 11:09:47 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA01448
	for <isis-archive@lists.ietf.org>; Tue, 24 Sep 2002 11:09:47 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8OF7Jv06887;
	Tue, 24 Sep 2002 11:07:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8OF3Xv06223
	for <isis-wg@optimus.ietf.org>; Tue, 24 Sep 2002 11:03:33 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA00986
	for <isis-wg@ietf.org>; Tue, 24 Sep 2002 11:01:39 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A743EA@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "ISIS-WG (E-mail)" <isis-wg@ietf.org>
Subject: FW: [Isis-wg] isisSysTEEnabled in ISIS MIB
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Tue, 24 Sep 2002 11:02:58 -0400

All -
	Sorry for the spam

Don -
	I would be interested to see your suggestions.  
However, I am unable to reply to your mail: the address
dgoodspe@excite.com bounces for me.

- jeff parker

> Jeff,
> 
> I'm compiling a list of other changes based on our discussion in the
> past (on LSP database table) and on the MIB in general, based on my
> company's experience.
> 
> When I compile my list, do you want me to send as one BIG item, or
> as several small items topic-by-topic?
> 
> -don 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Wed Sep 25 13:30:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03792
	for <isis-archive@lists.ietf.org>; Wed, 25 Sep 2002 13:30:54 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PHS0v01946;
	Wed, 25 Sep 2002 13:28:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8PHOmv01842
	for <isis-wg@optimus.ietf.org>; Wed, 25 Sep 2002 13:24:48 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03456
	for <isis-wg@ietf.org>; Wed, 25 Sep 2002 13:22:50 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74407@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Laura Liu'" <lliu@chiaro.com>, isis-wg@ietf.org
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: isisRedistributeAddrTable in mib09
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Wed, 25 Sep 2002 13:18:47 -0400

 
> Jeff,
> 
> My question was triggered by the discussion on the mailing 
> list a while ago
> about up/down bit referring to "IS-IS extensions for Traffic 
> Engineering"
> draft v.04 section 5.1:
> 
> "If a prefix is advertised from an area to another area at 
> the same level,
> then the up/down bit shall be set to 1. This situation can 
> arise when a
> router implements multiple virtual routers at the same level, but in
> different areas.".
> 
> Can we use isisRedistributeAddrTable for all the up/down bit set to 1
> routes? 
> 
> regards,
> Laura 
 
Laura -
	The goal is to have a platform independent way to specify
which routes can be leaked down from L2 to L1.

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 15:21:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18907
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 15:21:08 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QJGXv25469;
	Thu, 26 Sep 2002 15:16:33 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QJCnv25347
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 15:12:49 -0400
Received: from mail4.nec.com (dns4.nec.com [131.241.15.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA18679
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 15:10:51 -0400 (EDT)
Received: from netkeeper.sj.nec.com (netkeeper.sj.nec.com [131.241.31.2])
	by mail4.nec.com (/) with ESMTP id g8QJCCc01513
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 12:12:12 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1])
	by netkeeper.sj.nec.com (8.9.1a/8.9.1) with ESMTP id MAA28553
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 12:12:06 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com 
	by necsun.tdd.sj.nec.com  with ESMTP id g8QJ4YAd013993
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 12:04:35 -0700 (PDT)
Received: from ems11 (ems11 [131.241.5.62])
	by bunny.tdd.sj.nec.com  with SMTP id g8QJ4XKq015591
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 12:04:33 -0700 (PDT)
Received: by localhost with Microsoft MAPI; Thu, 26 Sep 2002 12:18:14 -0700
Message-ID: <01C26556.C9F9CF60.ramsrm@tdd.sj.nec.com>
From: ramanathan rams <ramsrm@tdd.sj.nec.com>
Reply-To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
To: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Organization: NEC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 24 TEXT
Subject: [Isis-wg] doubts
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 12:18:13 -0700

hi all,

    I have few doubts in ISIS and three way handshake. could u please 
explain me?

*   In section 7.3.15.2 - Action on receipt of sequence number PDU, under 
b) ,4. - it says if C is non broadcast circuit clear SRMflag.  why don't we 
clear it for broadcast circuit.

*   In ISIS 3 way handshake while mentioning  the first problem which will 
occur if we don't support 3 way handshake if the datalink protocol used is 
unrelaible, they say it may take full complete LSP refresh period upto 
eighteen hours. how do they get this 18 hours?  within  a maximum time 
frame of Maximum LSP Generation interval all the LSPs will be regenrated 
even if there is no change and so flooding will assure that all the LSPs 
will be reached to the other side,  even though the first CSNP is lost in 
PP circuit right?.

*   Do u have any idea on DDRP based on ISIS and any reference to DDRP 
materials?


thanks
rams.

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 15:36:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19456
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 15:36:17 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QJZKv26143;
	Thu, 26 Sep 2002 15:35:20 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QJUGv25955
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 15:30:16 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19200
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 15:28:17 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74442@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 15:29:20 -0400

> *   In section 7.3.15.2 - Action on receipt of sequence 
> number PDU, under 
> it says if C is non broadcast circuit clear SRMflag. 
>  why don't we clear it for broadcast circuit[?]

The SRM flag is used to control an IS's acknowledgement
of a packet.  Acknowledgements on a LAN are handled
by the DIS sending CSNPs.  

> *   In ISIS 3 way handshake while mentioning  the first 
> problem which will occur if we don't support 3 way 
> handshake if the datalink protocol used is 
> unrelaible, they say it may take full complete LSP refresh 
> period upto eighteen hours. how do they get this 18 hours? 

In 16 bits, you can encode 18 hours worth of seconds.  
There are ISPs that demand (and craven implementors 
who provide) the ability to increase the LSP Lifetime.

> *   Do u have any idea on DDRP based on ISIS and any 
> reference to DDRP materials?

Sorry, I'm having a jargon cache miss.  Do you 
mean the National Guard Drug Demand Reduction
Policy?  I know of no mention of ISIS in their
material.  

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 16:06:07 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20125
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 16:06:07 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QK4Tv27436;
	Thu, 26 Sep 2002 16:04:29 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QK18v27385
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 16:01:08 -0400
Received: from mx4.tellabs.com (mx4.tellabs.com [204.68.180.54])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA19977
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 15:59:09 -0400 (EDT)
Received: from mailw02.hq.tellabs.com (mailw02.lisle.tellabs.com [172.23.207.12])
	by mx4.tellabs.com (Mirapoint)
	with ESMTP id AQU47646;
	Thu, 26 Sep 2002 15:00:02 -0500 (CDT)
Received: from tellabs.com (dhcp-172-23-111-21.lisle.tellabs.com [172.23.111.21]) by mailw02.hq.tellabs.com with ESMTP (8.8.6 (PHNE_17190)/8.7.1) id PAA25388; Thu, 26 Sep 2002 15:00:03 -0500 (CDT)
Message-ID: <3D936738.DEF85B28@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 Parker <jparker@axiowave.com>
CC: "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] doubts
References: <H0000c080562e8f5.1033069072.mailw02@MHS>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 14:59:52 -0500
Content-Transfer-Encoding: 7bit

Jeff -

Jeff Parker wrote:
> > *   Do u have any idea on DDRP based on ISIS and any
> > reference to DDRP materials?
> 
> Sorry, I'm having a jargon cache miss.  Do you
> mean the National Guard Drug Demand Reduction
> Policy?  I know of no mention of ISIS in their
> material.

DDRP is the "Domain to Domain Routing Protocol", which is being
discussed in the OIF to handle E-NNI Optical Routing.  While the title
includes the word "Protocol", it is really conceptual in nature --
no-one is looking to reinvent the wheel.  Let me explain:

Three documents exist.  The first (oif2002.378) defines requirements for
Hierarchical Optical Routing when using a Link State protocol.  These
are based on the ITU-T's G.7715 (ASON Routing) as well as requirements
provided by the OIF Carriers group.  The second (oif2002.023) and third
(oif2002.163) are competing proposals that fulfill the requirements
using extensions to OSPF and IS-IS, respectively.

There are a number of things the requirements add which aren't already
covered in the GMPLS extensions for IS-IS draft.  The biggest probably
is the need to support Multi-Level hierarchies with a depth greater than
2.

Jonathan Sadler
============================================================
The information contained in this message may be privileged 
and confidential and protected from disclosure.  If the 
reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to 
the intended recipient, you are hereby notified that any 
reproduction, dissemination or distribution of this 
communication is strictly prohibited. If you have received 
this communication in error, please notify us immediately by 
replying to the message and deleting it from your computer.

Thank you.
Tellabs
============================================================
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 16:15:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20351
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 16:15:17 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKEDv28262;
	Thu, 26 Sep 2002 16:14:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKBBv28165
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 16:11:11 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20227
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 16:09:12 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74444@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'jonathan.sadler@tellabs.com'" <jonathan.sadler@tellabs.com>,
        Jeff Parker <jparker@axiowave.com>
Cc: "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 16:10:16 -0400

 
> The biggest probably is the need to support 
> Multi-Level hierarchies with a depth greater 
> than 2.

Jonathan -
	Thanks for rectifying my appalling ignorance.

	While I don't want to start a food fight
here, can you help me understand why we need 
additional levels?  I have heard people mutter
things about this for years, but I haven't
really understood the point yet.  

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 16:24:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20681
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 16:24:00 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKMnv28663;
	Thu, 26 Sep 2002 16:22:50 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKJkv28538
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 16:19:46 -0400
Received: from mail4.nec.com (dns4.nec.com [131.241.15.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20483
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 16:17:49 -0400 (EDT)
Received: from netkeeper.sj.nec.com (netkeeper.sj.nec.com [131.241.31.2])
	by mail4.nec.com (/) with ESMTP id g8QKJAc05356;
	Thu, 26 Sep 2002 13:19:10 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1])
	by netkeeper.sj.nec.com (8.9.1a/8.9.1) with ESMTP id NAA00261;
	Thu, 26 Sep 2002 13:19:03 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com 
	by necsun.tdd.sj.nec.com  with ESMTP id g8QKBVAd014469;
	Thu, 26 Sep 2002 13:11:31 -0700 (PDT)
Received: from ems11 (ems11 [131.241.5.62])
	by bunny.tdd.sj.nec.com  with SMTP id g8QKBUKq017042;
	Thu, 26 Sep 2002 13:11:30 -0700 (PDT)
Received: by localhost with Microsoft MAPI; Thu, 26 Sep 2002 13:25:11 -0700
Message-ID: <01C26560.241B7440.ramsrm@tdd.sj.nec.com>
From: ramanathan rams <ramsrm@tdd.sj.nec.com>
Reply-To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
To: "'Jeff Parker'" <jparker@axiowave.com>,
        "'isis-wg@ietf.org'"
	 <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
Organization: NEC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 62 TEXT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 13:25:10 -0700

Hi,

     for point to point straight forward reason( for acking SRM flag will 
be set,  if we don't clear it, again LSP will be sent ) is there, so it's 
fine.

For Lan,  consider the following situation :

     Machine A, B are in LAN.  A is the DIS. B is connected to C via PP 
circuit.

    B is having an old copy of an LSP.  now B is getting the new copy of 
the same LSP from  C via PP. so SRM flag will be set for that LSP in B to 
transmitt that LSP in LAN. By then B is getting the CSNP from the DIS, 
which has a latest version of that LSP, so B will set SSN flag for 
requesting that LSP and according to the specification won't clear the SRM 
flag for that LSP in the Broadcast circuit. so  B will flood the old LSP in 
the broadcast circuit, even though it will converge soon, this seems to be 
unnecessary operation right? if i am wrong please correct me.

thanks
rams.






-----Original Message-----
From:	Jeff Parker [SMTP:jparker@axiowave.com]
Sent:	Thursday, September 26, 2002 12:29 PM
To:	'ramsrm@tdd.sj.nec.com'; 'isis-wg@ietf.org'
Subject:	RE: [Isis-wg] doubts

> *   In section 7.3.15.2 - Action on receipt of sequence
> number PDU, under
> it says if C is non broadcast circuit clear SRMflag.
>  why don't we clear it for broadcast circuit[?]

The SRM flag is used to control an IS's acknowledgement
of a packet.  Acknowledgements on a LAN are handled
by the DIS sending CSNPs.

> *   In ISIS 3 way handshake while mentioning  the first
> problem which will occur if we don't support 3 way
> handshake if the datalink protocol used is
> unrelaible, they say it may take full complete LSP refresh
> period upto eighteen hours. how do they get this 18 hours?

In 16 bits, you can encode 18 hours worth of seconds.
There are ISPs that demand (and craven implementors
who provide) the ability to increase the LSP Lifetime.

> *   Do u have any idea on DDRP based on ISIS and any
> reference to DDRP materials?

Sorry, I'm having a jargon cache miss.  Do you
mean the National Guard Drug Demand Reduction
Policy?  I know of no mention of ISIS in their
material.

- jeff parker

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 16:26:46 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20829
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 16:26:46 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKPEv28778;
	Thu, 26 Sep 2002 16:25:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKL3v28614
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 16:21:03 -0400
Received: from mx4.tellabs.com (mx4.tellabs.com [204.68.180.54])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA20508
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 16:19:06 -0400 (EDT)
Received: from mailw02.hq.tellabs.com (mailw02.lisle.tellabs.com [172.23.207.12])
	by mx4.tellabs.com (Mirapoint)
	with ESMTP id AQU48333;
	Thu, 26 Sep 2002 15:20:27 -0500 (CDT)
Received: from tellabs.com (dhcp-172-23-111-21.lisle.tellabs.com [172.23.111.21]) by mailw02.hq.tellabs.com with ESMTP (8.8.6 (PHNE_17190)/8.7.1) id PAA02126; Thu, 26 Sep 2002 15:20:28 -0500 (CDT)
Message-ID: <3D936C02.1A6EA439@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 Parker <jparker@axiowave.com>
CC: "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] doubts
References: <H0000c080562e8fb.1033071099.mailw02@MHS>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 15:20:18 -0500
Content-Transfer-Encoding: 7bit

Jeff -

Jeff Parker wrote:
> > The biggest probably is the need to support
> > Multi-Level hierarchies with a depth greater
> > than 2.
>
>         While I don't want to start a food fight
> here, can you help me understand why we need
> additional levels?  I have heard people mutter
> things about this for years, but I haven't
> really understood the point yet.

The main rationale has to do with the way that Telecom Service Providers
organize their operations staffs, as well as their networks, and the
size of those networks.  Many operate separate groups that individually
focus on Metro, Regional, National, and International networks. 
Consequently, there is natural summarization in the network designs. 
Couple this with aggregate SONET/SDH node counts of >30,000 (!) nodes
and you can see why they find hierarchy for ASON routing desireable.

Jonathan Sadler
============================================================
The information contained in this message may be privileged 
and confidential and protected from disclosure.  If the 
reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to 
the intended recipient, you are hereby notified that any 
reproduction, dissemination or distribution of this 
communication is strictly prohibited. If you have received 
this communication in error, please notify us immediately by 
replying to the message and deleting it from your computer.

Thank you.
Tellabs
============================================================
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 16:52:15 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21611
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 16:52:15 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKp6v30332;
	Thu, 26 Sep 2002 16:51:06 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKmjv30266
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 16:48:45 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21507
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 16:46:46 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 235551DCC7D; Thu, 26 Sep 2002 13:48:38 -0700 (PDT)
To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
Cc: "'Jeff Parker'" <jparker@axiowave.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: Re: [Isis-wg] doubts 
In-reply-to: Mail from ramanathan rams <ramsrm@tdd.sj.nec.com> 
 dated Thu, 26 Sep 2002 13:25:10 PDT
 <01C26560.241B7440.ramsrm@tdd.sj.nec.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020926204838.235551DCC7D@prattle.redback.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 13:48:38 -0700


you example being there are only A and B on a LAN. what if there are
C and D. B does not know C and D has it or not. why not just send
it instead of waiting for C and D both send PSNP asking for it.

 ] Hi,
 ] 
 ]      for point to point straight forward reason( for acking SRM flag will 
 ] be set,  if we don't clear it, again LSP will be sent ) is there, so it's 
 ] fine.
 ] 
 ] For Lan,  consider the following situation :
 ] 
 ]      Machine A, B are in LAN.  A is the DIS. B is connected to C via PP 
 ] circuit.
 ] 
 ]     B is having an old copy of an LSP.  now B is getting the new copy of 
 ] the same LSP from  C via PP. so SRM flag will be set for that LSP in B to 
 ] transmitt that LSP in LAN. By then B is getting the CSNP from the DIS, 
 ] which has a latest version of that LSP, so B will set SSN flag for 
 ] requesting that LSP and according to the specification won't clear the SRM 
 ] flag for that LSP in the Broadcast circuit. so  B will flood the old LSP in 
 ] the broadcast circuit, even though it will converge soon, this seems to be 
 ] unnecessary operation right? if i am wrong please correct me.
 ] 
 ] thanks
 ] rams.
 ] 
 ] 
 ] 
 ] 
 ] 
 ] 
 ] -----Original Message-----
 ] From:	Jeff Parker [SMTP:jparker@axiowave.com]
 ] Sent:	Thursday, September 26, 2002 12:29 PM
 ] To:	'ramsrm@tdd.sj.nec.com'; 'isis-wg@ietf.org'
 ] Subject:	RE: [Isis-wg] doubts
 ] 
 ] > *   In section 7.3.15.2 - Action on receipt of sequence
 ] > number PDU, under
 ] > it says if C is non broadcast circuit clear SRMflag.
 ] >  why don't we clear it for broadcast circuit[?]
 ] 
 ] The SRM flag is used to control an IS's acknowledgement
 ] of a packet.  Acknowledgements on a LAN are handled
 ] by the DIS sending CSNPs.
 ] 
 ] > *   In ISIS 3 way handshake while mentioning  the first
 ] > problem which will occur if we don't support 3 way
 ] > handshake if the datalink protocol used is
 ] > unrelaible, they say it may take full complete LSP refresh
 ] > period upto eighteen hours. how do they get this 18 hours?
 ] 
 ] In 16 bits, you can encode 18 hours worth of seconds.
 ] There are ISPs that demand (and craven implementors
 ] who provide) the ability to increase the LSP Lifetime.
 ] 
 ] > *   Do u have any idea on DDRP based on ISIS and any
 ] > reference to DDRP materials?
 ] 
 ] Sorry, I'm having a jargon cache miss.  Do you
 ] mean the National Guard Drug Demand Reduction
 ] Policy?  I know of no mention of ISIS in their
 ] material.
 ] 
 ] - jeff parker
 ] 
 ] _______________________________________________
 ] Isis-wg mailing list
 ] Isis-wg@ietf.org
 ] https://www1.ietf.org/mailman/listinfo/isis-wg

- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 16:57:08 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21760
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 16:57:08 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKuDv30469;
	Thu, 26 Sep 2002 16:56:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QKriv30397
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 16:53:44 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21608
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 16:51:46 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8QKr8Ns019126;
	Thu, 26 Sep 2002 16:53:09 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-222-156.cisco.com [64.102.222.156])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAD99571;
	Thu, 26 Sep 2002 16:53:06 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020926162623.01b4cc68@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] doubts
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
In-Reply-To: <01C26556.C9F9CF60.ramsrm@tdd.sj.nec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 16:28:17 -0400

At 03:18 PM 9/26/2002, ramanathan rams wrote:
>hi all,
>
>    I have few doubts in ISIS and three way handshake. could u please 
>explain me?
>
>*   In section 7.3.15.2 - Action on receipt of sequence number PDU, under 
>b) ,4. - it says if C is non broadcast circuit clear SRMflag.  why don't we 
>clear it for broadcast circuit.

My understanding is that three-way handshake is important for ptp links,
because ISIS PTP procedures assumed a reliable link.  Since ISIS does
not assume a reliable link on a broadcast link, 3-way handshake is
superfluous.

If 3-way provides any significant benefit on a broadcast network, please
let me know.

Thanks,
Jeff


>*   In ISIS 3 way handshake while mentioning  the first problem which will 
>occur if we don't support 3 way handshake if the datalink protocol used is 
>unrelaible, they say it may take full complete LSP refresh period upto 
>eighteen hours. how do they get this 18 hours?  within  a maximum time 
>frame of Maximum LSP Generation interval all the LSPs will be regenrated 
>even if there is no change and so flooding will assure that all the LSPs 
>will be reached to the other side,  even though the first CSNP is lost in 
>PP circuit right?.
>
>*   Do u have any idea on DDRP based on ISIS and any reference to DDRP 
>materials?
>
>
>thanks
>rams.
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 17:13:02 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22374
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 17:13:02 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QLBev31929;
	Thu, 26 Sep 2002 17:11:40 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QL87v31835
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 17:08:07 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA22175
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 17:06:09 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A74445@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 17:07:21 -0400

> For Lan,  consider the following situation :
> 
>      Machine A, B are in LAN.  A is the DIS. B is connected 
> to C via PP 
> circuit.
> 
>     B is having an old copy of an LSP.  now B is getting the 
> new copy of 
> the same LSP from  C via PP. so SRM flag will be set for that 
> LSP in B to 
> transmitt that LSP in LAN. By then B is getting the CSNP from 
> the DIS, 
> which has a latest version of that LSP, so B will set SSN flag for 
> requesting that LSP and according to the specification won't 
> clear the SRM 
> flag for that LSP in the Broadcast circuit. so  B will flood 
> the old LSP in 
> the broadcast circuit, even though it will converge soon, 
> this seems to be 
> unnecessary operation right? if i am wrong please correct me.
> 
> thanks
> rams.

Rams -
	I'm not sure I'm following all of this.  
Let me draw the network, and change a few names
to match 10589's language here...
B is connect to D via a p2p link, and to A, E and F
via a Bcast link

	          D
                |
	A*        B    E    F
      +         +    +    +
    ===========================  

A* == A is the DIS

I think this is your network.  
B has recieved LSP X from D, and has set the
SRM bit on circuit C (the circuit to the LAN).  
Section 7.3.15.2.b.1 talks about getting a 
CSPN on circuit C from DIS A

	1) If the reported value equals the database
	value and C is a non-broadcast circuit, clear
	the SRM flag for C in that LSP

Your observation is that we could safely clear the
SRM bit on a broadcast link as well as a p2p.  If there 
are other IS's E and F on the LAN, they will have just
seen the CSPN, so they will ask for the LSP if
they don't have it.  Nothing is gained by sending.
I don't know if this has been observed before or fixed
in some version of the draft - a brief look at the
recent revision shows no change.

As you note, there is no harm in the extra send, but
it does seem odd that this is singled out.  There
must be a reason 

Mike?  What are we missing?  

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 17:57:09 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23307
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 17:57:09 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QLtdv01242;
	Thu, 26 Sep 2002 17:55:40 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QLq4v01146
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 17:52:04 -0400
Received: from mail4.nec.com (dns4.nec.com [131.241.15.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA23160
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 17:50:05 -0400 (EDT)
Received: from netkeeper2.sj.nec.com (netkeeper2.sj.nec.com [131.241.31.10])
	by mail4.nec.com (/) with ESMTP id g8QLpMc12255;
	Thu, 26 Sep 2002 14:51:23 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1])
	by netkeeper2.sj.nec.com (8.9.1a/8.9.1) with ESMTP id OAA12390;
	Thu, 26 Sep 2002 14:51:11 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com 
	by necsun.tdd.sj.nec.com  with ESMTP id g8QLhfAd015129;
	Thu, 26 Sep 2002 14:43:41 -0700 (PDT)
Received: from ems11 (ems11 [131.241.5.62])
	by bunny.tdd.sj.nec.com  with SMTP id g8QLheKq020919;
	Thu, 26 Sep 2002 14:43:40 -0700 (PDT)
Received: by localhost with Microsoft MAPI; Thu, 26 Sep 2002 14:57:21 -0700
Message-ID: <01C2656D.04263A50.ramsrm@tdd.sj.nec.com>
From: ramanathan rams <ramsrm@tdd.sj.nec.com>
Reply-To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
To: "'Jeff Parker'" <jparker@axiowave.com>,
        "'isis-wg@ietf.org'"
	 <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
Organization: NEC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 85 TEXT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 14:57:20 -0700

hi,

       one extra send of equal lsp case b,2  and  one extra send of old lsp 
or new lsp ( based on the time gap between sending the ssn request, 
receiving the new lsp and checking of SRM flag for the LSP propogation ) 
will also occur because of b,4.

thanks
rams.

-----Original Message-----
From:	Jeff Parker [SMTP:jparker@axiowave.com]
Sent:	Thursday, September 26, 2002 2:07 PM
To:	'ramsrm@tdd.sj.nec.com'; 'isis-wg@ietf.org'
Subject:	RE: [Isis-wg] doubts

> For Lan,  consider the following situation :
>
>      Machine A, B are in LAN.  A is the DIS. B is connected
> to C via PP
> circuit.
>
>     B is having an old copy of an LSP.  now B is getting the
> new copy of
> the same LSP from  C via PP. so SRM flag will be set for that
> LSP in B to
> transmitt that LSP in LAN. By then B is getting the CSNP from
> the DIS,
> which has a latest version of that LSP, so B will set SSN flag for
> requesting that LSP and according to the specification won't
> clear the SRM
> flag for that LSP in the Broadcast circuit. so  B will flood
> the old LSP in
> the broadcast circuit, even though it will converge soon,
> this seems to be
> unnecessary operation right? if i am wrong please correct me.
>
> thanks
> rams.

Rams -
	I'm not sure I'm following all of this.
Let me draw the network, and change a few names
to match 10589's language here...
B is connect to D via a p2p link, and to A, E and F
via a Bcast link

	          D
                |
	A*        B    E    F
      +         +    +    +
    ===========================

A* == A is the DIS

I think this is your network.
B has recieved LSP X from D, and has set the
SRM bit on circuit C (the circuit to the LAN).
Section 7.3.15.2.b.1 talks about getting a
CSPN on circuit C from DIS A

	1) If the reported value equals the database
	value and C is a non-broadcast circuit, clear
	the SRM flag for C in that LSP

Your observation is that we could safely clear the
SRM bit on a broadcast link as well as a p2p.  If there
are other IS's E and F on the LAN, they will have just
seen the CSPN, so they will ask for the LSP if
they don't have it.  Nothing is gained by sending.
I don't know if this has been observed before or fixed
in some version of the draft - a brief look at the
recent revision shows no change.

As you note, there is no harm in the extra send, but
it does seem odd that this is singled out.  There
must be a reason

Mike?  What are we missing?

- jeff parker
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 18:21:35 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23788
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 18:21:35 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMKPv02642;
	Thu, 26 Sep 2002 18:20:25 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMHxv02526
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 18:17:59 -0400
Received: from mail4.nec.com (dns4.nec.com [131.241.15.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23618
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 18:16:00 -0400 (EDT)
Received: from netkeeper.sj.nec.com (netkeeper.sj.nec.com [131.241.31.2])
	by mail4.nec.com (/) with ESMTP id g8QMHLc14185;
	Thu, 26 Sep 2002 15:17:21 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1])
	by netkeeper.sj.nec.com (8.9.1a/8.9.1) with ESMTP id PAA03209;
	Thu, 26 Sep 2002 15:17:16 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com 
	by necsun.tdd.sj.nec.com  with ESMTP id g8QM9iAd015247;
	Thu, 26 Sep 2002 15:09:44 -0700 (PDT)
Received: from ems11 (ems11 [131.241.5.62])
	by bunny.tdd.sj.nec.com  with SMTP id g8QM9hKq021480;
	Thu, 26 Sep 2002 15:09:43 -0700 (PDT)
Received: by localhost with Microsoft MAPI; Thu, 26 Sep 2002 15:23:24 -0700
Message-ID: <01C26570.A7BA1D50.ramsrm@tdd.sj.nec.com>
From: ramanathan rams <ramsrm@tdd.sj.nec.com>
Reply-To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
To: "'Jeff Parker'" <jparker@axiowave.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
Organization: NEC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 49 TEXT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 15:23:23 -0700

hi,

    sorry b,2 is the convergence case, it will not result in extra send.


     for b,4 old lsp will  be sent in the following scenario

     old LSP will be sent when SRM flag is examined before getting the new 
LSP update from the DIS.     B receives the CSNP packet from A, finds it is 
having a old copy so it will set the SSN bit, to request the new version of 
that LSP. Meanwhile another   new version of the LSP comes from D which is 
not as latest as A is having. but to B, it is latest and it will update the 
database and set the SRM flag,  then SSN request is sent and then because 
of SRM flag set, B will send the LSP received from D on the LAN before 
receiving the new ( latest ) LSP from  DIS.  In this case old LSP is 
propogated.

      new lsp will be sent when SRM flag is examined after getting the new 
update from the DIS.

 is that right or wrong?

thanks
rams.




-----Original Message-----
From:	Jeff Parker [SMTP:jparker@axiowave.com]
Sent:	Thursday, September 26, 2002 2:57 PM
To:	'ramsrm@tdd.sj.nec.com'
Subject:	RE: [Isis-wg] doubts

> hi,
>
>        one extra send of equal lsp case b,2  and  one extra
> send of old lsp
> or new lsp ( based on the time gap between sending the ssn request,
> receiving the new lsp and checking of SRM flag for the LSP
> propogation )
> will also occur because of b,4.
>
> thanks
> rams.

I don't see that b.2 leads to an extra send.

I don't understand the scenario you describe for b.4

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 18:30:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23960
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 18:30:54 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMU9v03022;
	Thu, 26 Sep 2002 18:30:09 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMRKv02955
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 18:27:20 -0400
Received: from mail4.nec.com (dns4.nec.com [131.241.15.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23852
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 18:25:20 -0400 (EDT)
Received: from netkeeper2.sj.nec.com (netkeeper2.sj.nec.com [131.241.31.10])
	by mail4.nec.com (/) with ESMTP id g8QMQfc14672;
	Thu, 26 Sep 2002 15:26:41 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1])
	by netkeeper2.sj.nec.com (8.9.1a/8.9.1) with ESMTP id PAA16753;
	Thu, 26 Sep 2002 15:26:36 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com 
	by necsun.tdd.sj.nec.com  with ESMTP id g8QMJ4Ad015315;
	Thu, 26 Sep 2002 15:19:04 -0700 (PDT)
Received: from ems11 (ems11 [131.241.5.62])
	by bunny.tdd.sj.nec.com  with SMTP id g8QMJ2Kq023694;
	Thu, 26 Sep 2002 15:19:03 -0700 (PDT)
Received: by localhost with Microsoft MAPI; Thu, 26 Sep 2002 15:32:44 -0700
Message-ID: <01C26571.F55DF300.ramsrm@tdd.sj.nec.com>
From: ramanathan rams <ramsrm@tdd.sj.nec.com>
Reply-To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
To: "'Jeff Parker'" <jparker@axiowave.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
Organization: NEC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 28 TEXT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 15:32:42 -0700

hi,

     in b,2   also one extra send of equal LSP may result because of the reason i gave in my previous mail for b,4.

thanks
rams.

-----Original Message-----
From:	Jeff Parker [SMTP:jparker@axiowave.com]
Sent:	Thursday, September 26, 2002 2:57 PM
To:	'ramsrm@tdd.sj.nec.com'
Subject:	RE: [Isis-wg] doubts

> hi,
> 
>        one extra send of equal lsp case b,2  and  one extra 
> send of old lsp 
> or new lsp ( based on the time gap between sending the ssn request, 
> receiving the new lsp and checking of SRM flag for the LSP 
> propogation ) 
> will also occur because of b,4.
> 
> thanks
> rams.
 
I don't see that b.2 leads to an extra send.

I don't understand the scenario you describe for b.4

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 18:34:00 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24051
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 18:34:00 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMXDv03111;
	Thu, 26 Sep 2002 18:33:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMTxv03005
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 18:29:59 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA23885
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 18:28:00 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A7444B@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        Jeff Parker
	 <jparker@axiowave.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 18:29:05 -0400

 
>      old LSP will be sent when SRM flag is examined before 
> getting the new 
> LSP update from the DIS.     B receives the CSNP packet from 
> A, finds it is 
> having a old copy so it will set the SSN bit, to request the 
> new version of 
> that LSP. Meanwhile another   new version of the LSP comes 
> from D which is 
> not as latest as A is having. but to B, it is latest and it 
> will update the 
> database and set the SRM flag,  then SSN request is sent and 
> then because 
> of SRM flag set, B will send the LSP received from D on the 
> LAN before 
> receiving the new ( latest ) LSP from  DIS.  In this case old LSP is 
> propogated.
> 
>       new lsp will be sent when SRM flag is examined after 
> getting the new 
> update from the DIS.
> 
>  is that right or wrong?
> 
> thanks
> rams.

Rams -

Three routers, with three version of LSP X

	X3   X1    X2

	A*    B    D
	|     |    |
    =================

A is DIS, sends CSNP.  
B sees it, marks SSN bit to request it.
D then sends X2, which B replaces.
Is this your scenario?

Note that D's transmission is a race condition
with A's CSNP.  If D had processed the CSNP, he
would send a PSNP rather than an LSP.  Further,
if A is including the LSP in the CSNP, it probably
send LSP X3 out recently, so neither B nor D
should have the wrong stuff.  

This is a distributed database: there is going
to be extra packets.  However, it does converge,
and it converges pretty quickly.  The scenario
you describe is -possible-, but doesn't look
likely.

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 18:51:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24494
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 18:51:41 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMp0v04223;
	Thu, 26 Sep 2002 18:51:00 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMliv04108
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 18:47:44 -0400
Received: from mail4.nec.com (dns4.nec.com [131.241.15.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24291
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 18:45:44 -0400 (EDT)
Received: from netkeeper.sj.nec.com (netkeeper.sj.nec.com [131.241.31.2])
	by mail4.nec.com (/) with ESMTP id g8QMl5c15909;
	Thu, 26 Sep 2002 15:47:05 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1])
	by netkeeper.sj.nec.com (8.9.1a/8.9.1) with ESMTP id PAA03796;
	Thu, 26 Sep 2002 15:47:00 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com 
	by necsun.tdd.sj.nec.com  with ESMTP id g8QMdSAd015444;
	Thu, 26 Sep 2002 15:39:28 -0700 (PDT)
Received: from ems11 (ems11 [131.241.5.62])
	by bunny.tdd.sj.nec.com  with SMTP id g8QMdRKq024009;
	Thu, 26 Sep 2002 15:39:27 -0700 (PDT)
Received: by localhost with Microsoft MAPI; Thu, 26 Sep 2002 15:53:08 -0700
Message-ID: <01C26574.CF61A590.ramsrm@tdd.sj.nec.com>
From: ramanathan rams <ramsrm@tdd.sj.nec.com>
Reply-To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
To: "'Jeff Parker'" <jparker@axiowave.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
Organization: NEC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 79 TEXT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 15:53:07 -0700

hi,

       the diagram which I referred in my mail was ur first diagram not 
this. B and D are connected in PP circuit. A and B are in LAN.
further  PSNP interval is 2 secs. So after processing the CSNP, PSNP may 
not be immediately sent. so by that time if minimum LSP generation interval 
is expired then there is a chance that it can happen.

      but any way one extra send might result  and it could be either new 
or old. is this right or wrong?

thanks
rams.


-----Original Message-----
From:	Jeff Parker [SMTP:jparker@axiowave.com]
Sent:	Thursday, September 26, 2002 3:29 PM
To:	'ramsrm@tdd.sj.nec.com'; Jeff Parker
Cc:	'isis-wg@ietf.org'
Subject:	RE: [Isis-wg] doubts


>      old LSP will be sent when SRM flag is examined before
> getting the new
> LSP update from the DIS.     B receives the CSNP packet from
> A, finds it is
> having a old copy so it will set the SSN bit, to request the
> new version of
> that LSP. Meanwhile another   new version of the LSP comes
> from D which is
> not as latest as A is having. but to B, it is latest and it
> will update the
> database and set the SRM flag,  then SSN request is sent and
> then because
> of SRM flag set, B will send the LSP received from D on the
> LAN before
> receiving the new ( latest ) LSP from  DIS.  In this case old LSP is
> propogated.
>
>       new lsp will be sent when SRM flag is examined after
> getting the new
> update from the DIS.
>
>  is that right or wrong?
>
> thanks
> rams.

Rams -

Three routers, with three version of LSP X

	X3   X1    X2

	A*    B    D
	|     |    |
    =================

A is DIS, sends CSNP.
B sees it, marks SSN bit to request it.
D then sends X2, which B replaces.
Is this your scenario?

Note that D's transmission is a race condition
with A's CSNP.  If D had processed the CSNP, he
would send a PSNP rather than an LSP.  Further,
if A is including the LSP in the CSNP, it probably
send LSP X3 out recently, so neither B nor D
should have the wrong stuff.

This is a distributed database: there is going
to be extra packets.  However, it does converge,
and it converges pretty quickly.  The scenario
you describe is -possible-, but doesn't look
likely.

- jeff parker
- axiowave networks

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 18:58:17 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24811
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 18:58:17 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMuYv04402;
	Thu, 26 Sep 2002 18:56:34 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QMrAv04280
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 18:53:10 -0400
Received: from bridge.axiowave.com (ppp-64-115-125-242.broadviewnet.net [64.115.125.242] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24481
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 18:51:11 -0400 (EDT)
Message-ID: <EB5FFC72F183D411B38200062957342902A7444D@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>
Cc: "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 18:52:18 -0400

Rams -
	As noted before, if DIS A has an LSP, he
shouldn't keep it under his hat.  B should have
heard about the latest version of LSP X before
A sent out the CSNP.  

- jdp

> hi,
> 
>        the diagram which I referred in my mail was ur first 
> diagram not 
> this. B and D are connected in PP circuit. A and B are in LAN.
> further  PSNP interval is 2 secs. So after processing the 
> CSNP, PSNP may 
> not be immediately sent. so by that time if minimum LSP 
> generation interval 
> is expired then there is a chance that it can happen.
> 
>       but any way one extra send might result  and it could 
> be either new 
> or old. is this right or wrong?
> 
> thanks
> rams.
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 19:18:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25332
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 19:18:40 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QNHJv05570;
	Thu, 26 Sep 2002 19:17:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QNEKv05511
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 19:14:20 -0400
Received: from hal2.bizland-inc.net (mail2.bizland-inc.net [64.28.88.158])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25167
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 19:12:21 -0400 (EDT)
Received: from adsl-66-124-254-12.dsl.snfc21.pacbell.net ([66.124.254.12] helo=les.espsoft.com)
	by hal2.bizland-inc.net with asmtp (Exim 4.10)
	id 17uhpH-0001aL-00; Thu, 26 Sep 2002 19:13:43 -0400
Message-Id: <5.1.0.14.0.20020926160549.00a22540@pop.bizland.com>
X-Sender: espllc@pop.bizland.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: Jeff Parker <jparker@axiowave.com>,
        "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
From: Les Ginsberg <les@espsoft.com>
Subject: RE: [Isis-wg] doubts
In-Reply-To: <EB5FFC72F183D411B38200062957342902A74445@r2d2.axiowave.com
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Bizland-Abuse: This message was sent on behalf of a Bizland customer espllc -- Please report any abuse to abuse@bizland-inc.com
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 16:16:14 -0700

At 05:07 PM 9/26/02 -0400, Jeff Parker wrote:
>Rams -
>         I'm not sure I'm following all of this.
>Let me draw the network, and change a few names
>to match 10589's language here...
>B is connect to D via a p2p link, and to A, E and F
>via a Bcast link
>
>                   D
>                 |
>         A*        B    E    F
>       +         +    +    +
>     ===========================
>
>A* == A is the DIS
>
>I think this is your network.
>B has recieved LSP X from D, and has set the
>SRM bit on circuit C (the circuit to the LAN).
>Section 7.3.15.2.b.1 talks about getting a
>CSPN on circuit C from DIS A
>
>         1) If the reported value equals the database
>         value and C is a non-broadcast circuit, clear
>         the SRM flag for C in that LSP
>
>Your observation is that we could safely clear the
>SRM bit on a broadcast link as well as a p2p.  If there
>are other IS's E and F on the LAN, they will have just
>seen the CSPN, so they will ask for the LSP if
>they don't have it.  Nothing is gained by sending.


Actually something is gained by maintaining the SRMflag This is one of 
those cases where the handling of a received SNP entry is not and should 
not be equivalent to handling the receipt of the matching LSP. In the 
example Jeff has provided, when the non-DIS node  B receives an SNP entry 
from the DIS(A) it knows that A and B have the matching entry, but knows 
nothing about the state of this LSP in other non-DIS neighbors. In this 
example, all ISs who have recently received a new copy of the LSP in 
question will have set SRMflag on the broadcast circuit. Because LSPs are 
multicast, the first IS (DIS or non-DIS) who sends the new copy of the LSP 
will cause all other IS's on the LAN to clear the SRMflag when processing 
the received LSP (see 7.3.15.1e-iii). This will minimize the number of ISs 
who send the same copy of the LSP and will also minimize the number of 
PSNPs sent containing the corresponding SNP entry because the receipt of 
the LSP will also cause SSNflag to be  cleared (see 7.3.15.1e-v).

If every IS who had the SRMflag set cleared the SRMflag on receipt of a 
CSNP with an equal entry convergence time would be lengthened becaus

>I don't know if this has been observed before or fixed
>in some version of the draft - a brief look at the
>recent revision shows no change.
>
>As you note, there is no harm in the extra send, but
>it does seem odd that this is singled out.  There
>must be a reason
>
>Mike?  What are we missing?
>
>- jeff parker
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 19:23:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25487
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 19:23:54 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QNNDv05797;
	Thu, 26 Sep 2002 19:23:13 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QNKQv05715
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 19:20:26 -0400
Received: from hal2.bizland-inc.net (mail2.bizland-inc.net [64.28.88.158])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25329
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 19:18:27 -0400 (EDT)
Received: from adsl-66-124-254-12.dsl.snfc21.pacbell.net ([66.124.254.12] helo=les.espsoft.com)
	by hal2.bizland-inc.net with asmtp (Exim 4.10)
	id 17uhvF-00040Z-00; Thu, 26 Sep 2002 19:19:54 -0400
Message-Id: <5.1.0.14.0.20020926161904.00a2cec0@pop.bizland.com>
X-Sender: espllc@pop.bizland.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
To: Jeff Parker <jparker@axiowave.com>,
        "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
From: Les Ginsberg <les@espsoft.com>
Subject: RE: [Isis-wg] doubts
In-Reply-To: <EB5FFC72F183D411B38200062957342902A74445@r2d2.axiowave.com
 >
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_7531212==_.ALT"
X-Bizland-Abuse: This message was sent on behalf of a Bizland customer espllc -- Please report any abuse to abuse@bizland-inc.com
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 16:22:25 -0700

--=====================_7531212==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

(My apologies for the earlier inadvertent send of my reply before it was 
completed. Here is the complete reply).

    Les


At 05:07 PM 9/26/02 -0400, Jeff Parker wrote:
>Rams -
>         I'm not sure I'm following all of this.
>Let me draw the network, and change a few names
>to match 10589's language here...
>B is connect to D via a p2p link, and to A, E and F
>via a Bcast link
>
>                   D
>                 |
>         A*        B    E    F
>       +         +    +    +
>     ===========================
>
>A* == A is the DIS
>
>I think this is your network.
>B has recieved LSP X from D, and has set the
>SRM bit on circuit C (the circuit to the LAN).
>Section 7.3.15.2.b.1 talks about getting a
>CSPN on circuit C from DIS A
>
>         1) If the reported value equals the database
>         value and C is a non-broadcast circuit, clear
>         the SRM flag for C in that LSP
>
>Your observation is that we could safely clear the
>SRM bit on a broadcast link as well as a p2p.  If there
>are other IS's E and F on the LAN, they will have just
>seen the CSPN, so they will ask for the LSP if
>they don't have it.  Nothing is gained by sending.



Actually something is gained by maintaining the SRMflag This is one of 
those cases where the handling of a received SNP entry is not and should 
not be equivalent to handling the receipt of the matching LSP. In the 
example Jeff has provided, when the non-DIS node B receives an SNP entry 
from the DIS(A) it knows that A and B have the matching entry, but knows 
nothing about the state of this LSP in other non-DIS neighbors. In this 
example, all ISs who have recently received a new copy of the LSP in 
question will have set SRMflag on the broadcast circuit. Because LSPs are 
multicast, the first IS (DIS or non-DIS) who sends the new copy of the LSP 
will cause all other IS's on the LAN to clear the SRMflag when processing 
the received LSP (see 7.3.15.1e-iii). This will minimize the number of ISs 
who send the same copy of the LSP and will also minimize the number of 
PSNPs sent containing the corresponding SNP entry because the receipt of 
the LSP will also cause SSNflag to be cleared (see 7.3.15.1e-v).

If every IS who had the SRMflag set cleared the SRMflag on receipt of a 
CSNP with an equal entry convergence time would be lengthened because we 
would have to wait for the PSNPs to be sent by all systems which still have 
an older version even though some systems already were intending to 
propagate the new version of the LSP.


>I don't know if this has been observed before or fixed
>in some version of the draft - a brief look at the
>recent revision shows no change.
>
>As you note, there is no harm in the extra send, but
>it does seem odd that this is singled out.  There
>must be a reason
>
>Mike?  What are we missing?
>
>- jeff parker

--=====================_7531212==_.ALT
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
(My apologies for the earlier inadvertent send of my reply before it was
completed. Here is the complete reply).<br><br>
&nbsp;&nbsp; Les<br><br>
<br>
At 05:07 PM 9/26/02 -0400, Jeff Parker wrote:<br>
<blockquote type=3Dcite class=3Dcite cite>Rams -<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>I'm not
sure I'm following all of this.&nbsp; <br>
Let me draw the network, and change a few names<br>
to match 10589's language here...<br>
B is connect to D via a p2p link, and to A, E and F<br>
via a Bcast link<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
D<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp;&nbsp;
|<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>A*&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
B&nbsp;&nbsp;&nbsp; E&nbsp;&nbsp;&nbsp; F<br>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; +&nbsp;&nbsp;&nbsp;
+&nbsp;&nbsp;&nbsp; +<br>
&nbsp;&nbsp;&nbsp; =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D&nbsp; <br><br>
A* =3D=3D A is the DIS<br><br>
I think this is your network.&nbsp; <br>
B has recieved LSP X from D, and has set the<br>
SRM bit on circuit C (the circuit to the LAN).&nbsp; <br>
Section 7.3.15.2.b.1 talks about getting a <br>
CSPN on circuit C from DIS A<br><br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>1) If the
reported value equals the database<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>value and
C is a non-broadcast circuit, clear<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>the SRM
flag for C in that LSP<br><br>
Your observation is that we could safely clear the<br>
SRM bit on a broadcast link as well as a p2p.&nbsp; If there <br>
are other IS's E and F on the LAN, they will have just<br>
seen the CSPN, so they will ask for the LSP if<br>
they don't have it.&nbsp; Nothing is gained by sending.<br>
</blockquote><br><br>
<br>
Actually something is gained by maintaining the SRMflag This is one of
those cases where the handling of a received SNP entry is not and should
not be equivalent to handling the receipt of the matching LSP. In the
example Jeff has provided, when the non-DIS node B receives an SNP entry
from the DIS(A) it knows that A and B have the matching entry, but knows
nothing about the state of this LSP in other non-DIS neighbors. In this
example, all ISs who have recently received a new copy of the LSP in
question will have set SRMflag on the broadcast circuit. Because LSPs are
multicast, the first IS (DIS or non-DIS) who sends the new copy of the
LSP will cause all other IS's on the LAN to clear the SRMflag when
processing the received LSP (see 7.3.15.1e-iii). This will minimize the
number of ISs who send the same copy of the LSP and will also minimize
the number of PSNPs sent containing the corresponding SNP entry because
the receipt of the LSP will also cause SSNflag to be cleared (see
7.3.15.1e-v).<br><br>
If every IS who had the SRMflag set cleared the SRMflag on receipt of a
CSNP with an equal entry convergence time would be lengthened because we
would have to wait for the PSNPs to be sent by all systems which still
have an older version even though some systems already were intending to
propagate the new version of the LSP.<br><br>
<br>
<blockquote type=3Dcite class=3Dcite cite>I don't know if this has been
observed before or fixed<br>
in some version of the draft - a brief look at the<br>
recent revision shows no change.<br><br>
As you note, there is no harm in the extra send, but<br>
it does seem odd that this is singled out.&nbsp; There<br>
must be a reason <br><br>
Mike?&nbsp; What are we missing?&nbsp; <br><br>
- jeff parker</blockquote></html>

--=====================_7531212==_.ALT--

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Thu Sep 26 19:54:11 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25972
	for <isis-archive@lists.ietf.org>; Thu, 26 Sep 2002 19:54:11 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QNqRv07069;
	Thu, 26 Sep 2002 19:52:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8QNn1v06995
	for <isis-wg@optimus.ietf.org>; Thu, 26 Sep 2002 19:49:01 -0400
Received: from mail4.nec.com (dns4.nec.com [131.241.15.4])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25873
	for <isis-wg@ietf.org>; Thu, 26 Sep 2002 19:47:00 -0400 (EDT)
Received: from netkeeper.sj.nec.com (netkeeper.sj.nec.com [131.241.31.2])
	by mail4.nec.com (/) with ESMTP id g8QNmLc19486;
	Thu, 26 Sep 2002 16:48:21 -0700 (PDT)
Received: from necsun.tdd.sj.nec.com (localhost [127.0.0.1])
	by netkeeper.sj.nec.com (8.9.1a/8.9.1) with ESMTP id QAA05418;
	Thu, 26 Sep 2002 16:48:15 -0700 (PDT)
Received: from bunny.tdd.sj.nec.com 
	by necsun.tdd.sj.nec.com  with ESMTP id g8QNehAd015777;
	Thu, 26 Sep 2002 16:40:43 -0700 (PDT)
Received: from ems11 (ems11 [131.241.5.62])
	by bunny.tdd.sj.nec.com  with SMTP id g8QNegKq025801;
	Thu, 26 Sep 2002 16:40:42 -0700 (PDT)
Received: by localhost with Microsoft MAPI; Thu, 26 Sep 2002 16:54:23 -0700
Message-ID: <01C2657D.5DCD05B0.ramsrm@tdd.sj.nec.com>
From: ramanathan rams <ramsrm@tdd.sj.nec.com>
Reply-To: "ramsrm@tdd.sj.nec.com" <ramsrm@tdd.sj.nec.com>
To: "'Les Ginsberg'" <les@espsoft.com>, Jeff Parker <jparker@axiowave.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
Subject: RE: [Isis-wg] doubts
Organization: NEC
X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211
Encoding: 85 TEXT
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Thu, 26 Sep 2002 16:54:22 -0700

reason is really excellent. this clears my doubt.

thanks
rams.

-----Original Message-----
From:	Les Ginsberg [SMTP:les@espsoft.com]
Sent:	Thursday, September 26, 2002 4:22 PM
To:	Jeff Parker; 'ramsrm@tdd.sj.nec.com'; 'isis-wg@ietf.org'
Subject:	RE: [Isis-wg] doubts

(My apologies for the earlier inadvertent send of my reply before it was 
completed. Here is the complete reply).

    Les


At 05:07 PM 9/26/02 -0400, Jeff Parker wrote:
>Rams -
>         I'm not sure I'm following all of this.
>Let me draw the network, and change a few names
>to match 10589's language here...
>B is connect to D via a p2p link, and to A, E and F
>via a Bcast link
>
>                   D
>                 |
>         A*        B    E    F
>       +         +    +    +
>     ===========================
>
>A* == A is the DIS
>
>I think this is your network.
>B has recieved LSP X from D, and has set the
>SRM bit on circuit C (the circuit to the LAN).
>Section 7.3.15.2.b.1 talks about getting a
>CSPN on circuit C from DIS A
>
>         1) If the reported value equals the database
>         value and C is a non-broadcast circuit, clear
>         the SRM flag for C in that LSP
>
>Your observation is that we could safely clear the
>SRM bit on a broadcast link as well as a p2p.  If there
>are other IS's E and F on the LAN, they will have just
>seen the CSPN, so they will ask for the LSP if
>they don't have it.  Nothing is gained by sending.



Actually something is gained by maintaining the SRMflag This is one of 
those cases where the handling of a received SNP entry is not and should 
not be equivalent to handling the receipt of the matching LSP. In the 
example Jeff has provided, when the non-DIS node B receives an SNP entry 
from the DIS(A) it knows that A and B have the matching entry, but knows 
nothing about the state of this LSP in other non-DIS neighbors. In this 
example, all ISs who have recently received a new copy of the LSP in 
question will have set SRMflag on the broadcast circuit. Because LSPs are 
multicast, the first IS (DIS or non-DIS) who sends the new copy of the LSP 
will cause all other IS's on the LAN to clear the SRMflag when processing 
the received LSP (see 7.3.15.1e-iii). This will minimize the number of ISs 
who send the same copy of the LSP and will also minimize the number of 
PSNPs sent containing the corresponding SNP entry because the receipt of 
the LSP will also cause SSNflag to be cleared (see 7.3.15.1e-v).

If every IS who had the SRMflag set cleared the SRMflag on receipt of a 
CSNP with an equal entry convergence time would be lengthened because we 
would have to wait for the PSNPs to be sent by all systems which still have 
an older version even though some systems already were intending to 
propagate the new version of the LSP.


>I don't know if this has been observed before or fixed
>in some version of the draft - a brief look at the
>recent revision shows no change.
>
>As you note, there is no harm in the extra send, but
>it does seem odd that this is singled out.  There
>must be a reason
>
>Mike?  What are we missing?
>
>- jeff parker
 << File: ATT00696.html >> 

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep 27 04:54:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14617
	for <isis-archive@lists.ietf.org>; Fri, 27 Sep 2002 04:54:49 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8R8ohv08938;
	Fri, 27 Sep 2002 04:50:43 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8R8ndv08879
	for <isis-wg@optimus.ietf.org>; Fri, 27 Sep 2002 04:49:39 -0400
Received: from mta1-3.us4.outblaze.com (205-158-62-44.outblaze.com [205.158.62.44])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14520
	for <isis-wg@ietf.org>; Fri, 27 Sep 2002 04:47:30 -0400 (EDT)
Received: from ws1-4.us4.outblaze.com (205-158-62-50.outblaze.com [205.158.62.50])
	by mta1-3.us4.outblaze.com (8.12.3/8.12.3/us4-srs) with SMTP id g8R8mqQR028494
	for <isis-wg@ietf.org>; Fri, 27 Sep 2002 08:48:52 GMT
Received: (qmail 50475 invoked by uid 1001); 27 Sep 2002 08:48:44 -0000
Message-ID: <20020927084844.50474.qmail@iname.com>
Content-Type: text/plain; charset="iso-8859-15"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
MIME-Version: 1.0
X-Mailer: MIME-tools 5.41 (Entity 5.404)
Received: from [149.254.120.136] by ws1-4.us4.outblaze.com with http for
    philip.christian@iname.com; Fri, 27 Sep 2002 08:48:44 +0000
From: "Philip Christian" <philip.christian@iname.com>
To: jonathan.sadler@tellabs.com
Cc: isis-wg@ietf.org
X-Originating-Ip: 149.254.120.136
X-Originating-Server: ws1-4.us4.outblaze.com
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] DDRP (was doubts)
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 27 Sep 2002 08:48:44 +0000
Content-Transfer-Encoding: 7bit

Jonathan,

My understanding was that DDRP is nothing more than a simple way of flooding TE type information around a cloud.  More specifically it uses the OSPF flooding mechanism, without the requirement for building an IP forwarding table.

Basically the layers of hierarchy are provided having multiple clouds which do not interact with each other, other than that the TE information "somehow" gets passed from one cloud into another.  My understanding was that the "somehow", which is actually the unique point, is not yet defined.

If I am right then one could use IS-IS as a flooding mechanism instead (or any other).  The TE stuff could still be delivered to the edge of the cloud and passed onto the next (somehow), but the IS-IS LSPs wouldn't.  You wouldn't need 30,000 IP addresses either.

Have I got it about right ?

Philip




----- Original Message -----
From: Jonathan Sadler <jonathan.sadler@tellabs.com>
Date: Thu, 26 Sep 2002 15:20:18 -0500 
To: Jeff Parker <jparker@axiowave.com>
Subject: Re: [Isis-wg] doubts


> Jeff -
> 
> Jeff Parker wrote:
> > > The biggest probably is the need to support
> > > Multi-Level hierarchies with a depth greater
> > > than 2.
> >
> >         While I don't want to start a food fight
> > here, can you help me understand why we need
> > additional levels?  I have heard people mutter
> > things about this for years, but I haven't
> > really understood the point yet.
> 
> The main rationale has to do with the way that Telecom Service Providers
> organize their operations staffs, as well as their networks, and the
> size of those networks.  Many operate separate groups that individually
> focus on Metro, Regional, National, and International networks. 
> Consequently, there is natural summarization in the network designs. 
> Couple this with aggregate SONET/SDH node counts of >30,000 (!) nodes
> and you can see why they find hierarchy for ASON routing desireable.
> 
> Jonathan Sadler
> ============================================================
> The information contained in this message may be privileged 
> and confidential and protected from disclosure.  If the 
> reader of this message is not the intended recipient, or an 
> employee or agent responsible for delivering this message to 
> the intended recipient, you are hereby notified that any 
> reproduction, dissemination or distribution of this 
> communication is strictly prohibited. If you have received 
> this communication in error, please notify us immediately by 
> replying to the message and deleting it from your computer.
> 
> Thank you.
> Tellabs
> ============================================================
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> 

-- 
__________________________________________________________
Sign-up for your own FREE Personalized E-mail at Mail.com
http://www.mail.com/?sr=signup

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep 27 05:02:41 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14743
	for <isis-archive@lists.ietf.org>; Fri, 27 Sep 2002 05:02:41 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8R912v09274;
	Fri, 27 Sep 2002 05:01:02 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8R8xsv09210
	for <isis-wg@optimus.ietf.org>; Fri, 27 Sep 2002 04:59:54 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA14667
	for <isis-wg@ietf.org>; Fri, 27 Sep 2002 04:58:01 -0400 (EDT)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4344.cisco.com [10.50.16.247])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id JAA11476;
	Fri, 27 Sep 2002 09:54:55 +0100 (BST)
Message-Id: <4.3.2.7.2.20020927093234.0294d8e0@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Les Ginsberg <les@espsoft.com>
From: mike shand <mshand@cisco.com>
Subject: RE: [Isis-wg] doubts
Cc: Jeff Parker <jparker@axiowave.com>,
        "'ramsrm@tdd.sj.nec.com'" <ramsrm@tdd.sj.nec.com>,
        "'isis-wg@ietf.org'" <isis-wg@ietf.org>
In-Reply-To: <5.1.0.14.0.20020926161904.00a2cec0@pop.bizland.com>
References: <EB5FFC72F183D411B38200062957342902A74445@r2d2.axiowave.com >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 27 Sep 2002 09:53:25 +0100

Yes, Les has it.

To put it another way, when you receive a newer copy of an LSP you need to 
assert the presence of that LSP onto the LAN by setting SRMflags (and 
subsequently transmitting it). If you see a copy of that LSP on the LAN 
before you get around to transmitting it yourself, your desire to assert 
that LSP has been satisfied, and you are therefore justified in clearing 
your SRMflags (i.e. somebody else did what you were going to do ).

However, if you see that same LSP in a CSNP, all that tells you is that the 
DR has a copy. It tells you nothing about whether or not the LSP in 
question has been asserted onto the LAN, and hence whether or not anyone 
else MIGHT have a copy (note that sending an LSP on the LAN tells you 
NOTHING about whether anyone successfully received it). So this is NOT 
sufficient evidence for you to cancel your desire to assert the presence of 
the LSP on the LAN.

As Les correctly says, if you DID clear your flag, everything would still 
be sorted out, because those routers which didn't have a copy of the LSP 
would request one via a PSNP, and the DR would then send it.


But to be absolutely honest, I rather suspect this is all 
post-rationalization. I think the REAL reason for the "only clear SRM flags 
on a non-broadcast circuit" is simply that on a LAN SRMflags are self clearing!

Radia can correct me if I am wrong, but I don't THINK it was ever a 
conscious decision to optimize this case. Indeed I would be surprised if it 
were, because the whole design philosophy of the update process is that 
there are a very simple set of rules which will always guarantee correct 
operation under any circumstance whatever. They may not always be 
completely optimal, but they will NEVER do the wrong thing. In general the 
update process strenuously avoids rare case optimizations, on the grounds 
that special case code which is rarely exercised will almost certainly have 
undiscovered bugs in it, and optimizing rare cases is a waste of time 
anyway. The update process is not designed to be optimal. It IS designed to 
be correct.

KISS.



	Mike

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep 27 12:28:12 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29135
	for <isis-archive@lists.ietf.org>; Fri, 27 Sep 2002 12:28:12 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8RGPtv32005;
	Fri, 27 Sep 2002 12:25:56 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8RGMlv31929
	for <isis-wg@optimus.ietf.org>; Fri, 27 Sep 2002 12:22:47 -0400
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28271
	for <isis-wg@ietf.org>; Fri, 27 Sep 2002 12:20:50 -0400 (EDT)
Received: (truskows@localhost) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id JAA08313; Fri, 27 Sep 2002 09:21:46 -0700 (PDT)
From: Mike Truskowski <truskows@cisco.com>
Message-Id: <200209271621.JAA08313@wells.cisco.com>
Subject: Re: [Isis-wg] DDRP (was doubts)
To: philip.christian@iname.com
Cc: jonathan.sadler@tellabs.com, isis-wg@ietf.org
In-Reply-To: <20020927084844.50474.qmail@iname.com> from Philip Christian at Sep "27," 2002 "08:48:44" am
X-Mailer: ELM []
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 27 Sep 2002 09:21:46 -0700 (PDT)
Content-Transfer-Encoding: 7bit

And to complete... you wouldn't need a multi-layer heirarchy greater
then 2.

Mike

> Jonathan,
> 
> My understanding was that DDRP is nothing more than a simple way of flooding TE type information around a cloud.  More specifically it uses the OSPF flooding mechanism, without the requirement for building an IP forwarding table.
> 
> Basically the layers of hierarchy are provided having multiple clouds which do not interact with each other, other than that the TE information "somehow" gets passed from one cloud into another.  My understanding was that the "somehow", which is actually the unique point, is not yet defined.
> 
> If I am right then one could use IS-IS as a flooding mechanism instead (or any other).  The TE stuff could still be delivered to the edge of the cloud and passed onto the next (somehow), but the IS-IS LSPs wouldn't.  You wouldn't need 30,000 IP addresses either.
> 
> Have I got it about right ?
> 
> Philip
> 
> 
> 
> 
> ----- Original Message -----
> From: Jonathan Sadler <jonathan.sadler@tellabs.com>
> Date: Thu, 26 Sep 2002 15:20:18 -0500 
> To: Jeff Parker <jparker@axiowave.com>
> Subject: Re: [Isis-wg] doubts
> 
> 
> > Jeff -
> > 
> > Jeff Parker wrote:
> > > > The biggest probably is the need to support
> > > > Multi-Level hierarchies with a depth greater
> > > > than 2.
> > >
> > >         While I don't want to start a food fight
> > > here, can you help me understand why we need
> > > additional levels?  I have heard people mutter
> > > things about this for years, but I haven't
> > > really understood the point yet.
> > 
> > The main rationale has to do with the way that Telecom Service Providers
> > organize their operations staffs, as well as their networks, and the
> > size of those networks.  Many operate separate groups that individually
> > focus on Metro, Regional, National, and International networks. 
> > Consequently, there is natural summarization in the network designs. 
> > Couple this with aggregate SONET/SDH node counts of >30,000 (!) nodes
> > and you can see why they find hierarchy for ASON routing desireable.
> > 
> > Jonathan Sadler
> > ============================================================
> > The information contained in this message may be privileged 
> > and confidential and protected from disclosure.  If the 
> > reader of this message is not the intended recipient, or an 
> > employee or agent responsible for delivering this message to 
> > the intended recipient, you are hereby notified that any 
> > reproduction, dissemination or distribution of this 
> > communication is strictly prohibited. If you have received 
> > this communication in error, please notify us immediately by 
> > replying to the message and deleting it from your computer.
> > 
> > Thank you.
> > Tellabs
> > ============================================================
> > _______________________________________________
> > Isis-wg mailing list
> > Isis-wg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/isis-wg
> > 
> 
> -- 
> __________________________________________________________
> Sign-up for your own FREE Personalized E-mail at Mail.com
> http://www.mail.com/?sr=signup
> 
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org
> https://www1.ietf.org/mailman/listinfo/isis-wg
> 

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Fri Sep 27 20:58:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14940
	for <isis-archive@lists.ietf.org>; Fri, 27 Sep 2002 20:58:56 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8S0u9v23923;
	Fri, 27 Sep 2002 20:56:10 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8S0qTv23855
	for <isis-wg@optimus.ietf.org>; Fri, 27 Sep 2002 20:52:29 -0400
Received: from mx4.tellabs.com (mx4.tellabs.com [204.68.180.54])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA14799
	for <isis-wg@ietf.org>; Fri, 27 Sep 2002 20:50:28 -0400 (EDT)
Received: from mailw02.hq.tellabs.com (mailw02.lisle.tellabs.com [172.23.207.12])
	by mx4.tellabs.com (Mirapoint)
	with ESMTP id AQV07916;
	Fri, 27 Sep 2002 19:51:51 -0500 (CDT)
Received: from tellabs.com (dhcp-172-23-111-21.lisle.tellabs.com [172.23.111.21]) by mailw02.hq.tellabs.com with ESMTP (8.8.6 (PHNE_17190)/8.7.1) id TAA07590; Fri, 27 Sep 2002 19:51:53 -0500 (CDT)
Message-ID: <3D94FD26.1845041E@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: Mike Truskowski <truskows@cisco.com>
CC: philip.christian@iname.com, isis-wg@ietf.org
Subject: Re: [Isis-wg] DDRP (was doubts)
References: <H0000c08056502ec.1033144168.mailw02@MHS>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 27 Sep 2002 19:51:50 -0500
Content-Transfer-Encoding: 7bit

Mike -

The 30,000 node issue is not about the DCN, or about IP address
utilization -- instead it describes the complexity of the graph that
the ASON routing will be done over.  Since in ASON each node is a
switching point, it is basically an IS.  For the simplest topologies,
the number of links will be the number of nodes minus one.  And the
transport networks are certainly far from simple -- they're more like
a sparse mesh than a string or a hub/spoke topology.  Therefore
reducing graph complexity is important to keeping route calculation
times reasonable.  Use of hierarchical calculation is one way of
accomplishing this.

When hierarchical calculation is used, the next question is what
should the hierarchical "chunks" be.  While it may be possible to
run an area with 600 or so ISes in it, the network topology may be
such that creating a 600 node area is not practical, not to mention
the fact it doesn't provide any growth room.  Instead, it is better
to look at how the network is organized.  Since many Telco service
providers organize their networks and operations staffs along the
lines of metro, regional, national and international networks, the
best deliniation of an area may be similar.  For example, the Chicago
Metro may be one area, with Metro Indianapolis as another, and Metro
Detroit as a third.  These areas would then be contained in the
Upper-Midwest area.  In turn, the Upper-Midwest area as well as,
say, the BosWash area and others would be contained within the North
America network.  This would be contained along with the Europe
network (and others) in the "world" network.

Given this design, a 4-level hierarchical routing protocol is
necessary.  And we havn't even started adding levels to deal with
the interconnection points between service providers.

Jonathan Sadler

Mike Truskowski wrote:
> 
> And to complete... you wouldn't need a multi-layer heirarchy greater
> then 2.
> 
> Mike
> 
> > Jonathan,
> >
> > My understanding was that DDRP is nothing more than a simple way of flooding TE type information around a cloud.  More specifically it uses the OSPF flooding mechanism, without the requirement for building an IP forwarding table.
> >
> > Basically the layers of hierarchy are provided having multiple clouds which do not interact with each other, other than that the TE information "somehow" gets passed from one cloud into another.  My understanding was that the "somehow", which is actually the unique point, is not yet defined.
> >
> > If I am right then one could use IS-IS as a flooding mechanism instead (or any other).  The TE stuff could still be delivered to the edge of the cloud and passed onto the next (somehow), but the IS-IS LSPs wouldn't.  You wouldn't need 30,000 IP addresses either.
> >
> > Have I got it about right ?
> >
> > Philip
> >
> >
> >
> >
> > ----- Original Message -----
> > From: Jonathan Sadler <jonathan.sadler@tellabs.com>
> > Date: Thu, 26 Sep 2002 15:20:18 -0500
> > To: Jeff Parker <jparker@axiowave.com>
> > Subject: Re: [Isis-wg] doubts
> >
> >
> > > Jeff -
> > >
> > > Jeff Parker wrote:
> > > > > The biggest probably is the need to support
> > > > > Multi-Level hierarchies with a depth greater
> > > > > than 2.
> > > >
> > > >         While I don't want to start a food fight
> > > > here, can you help me understand why we need
> > > > additional levels?  I have heard people mutter
> > > > things about this for years, but I haven't
> > > > really understood the point yet.
> > >
> > > The main rationale has to do with the way that Telecom Service Providers
> > > organize their operations staffs, as well as their networks, and the
> > > size of those networks.  Many operate separate groups that individually
> > > focus on Metro, Regional, National, and International networks.
> > > Consequently, there is natural summarization in the network designs.
> > > Couple this with aggregate SONET/SDH node counts of >30,000 (!) nodes
> > > and you can see why they find hierarchy for ASON routing desireable.
> > >
> > > Jonathan Sadler
> > > ============================================================
> > > The information contained in this message may be privileged
> > > and confidential and protected from disclosure.  If the
> > > reader of this message is not the intended recipient, or an
> > > employee or agent responsible for delivering this message to
> > > the intended recipient, you are hereby notified that any
> > > reproduction, dissemination or distribution of this
> > > communication is strictly prohibited. If you have received
> > > this communication in error, please notify us immediately by
> > > replying to the message and deleting it from your computer.
> > >
> > > Thank you.
> > > Tellabs
> > > ============================================================
> > > _______________________________________________
> > > Isis-wg mailing list
> > > Isis-wg@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/isis-wg
> > >
> >
> > --
> > __________________________________________________________
> > Sign-up for your own FREE Personalized E-mail at Mail.com
> > http://www.mail.com/?sr=signup
> >
> > _______________________________________________
> > Isis-wg mailing list
> > Isis-wg@ietf.org
> > https://www1.ietf.org/mailman/listinfo/isis-wg
> >
============================================================
The information contained in this message may be privileged 
and confidential and protected from disclosure.  If the 
reader of this message is not the intended recipient, or an 
employee or agent responsible for delivering this message to 
the intended recipient, you are hereby notified that any 
reproduction, dissemination or distribution of this 
communication is strictly prohibited. If you have received 
this communication in error, please notify us immediately by 
replying to the message and deleting it from your computer.

Thank you.
Tellabs
============================================================
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 28 01:19:56 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19805
	for <isis-archive@lists.ietf.org>; Sat, 28 Sep 2002 01:19:56 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8S5Iev02050;
	Sat, 28 Sep 2002 01:18:41 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8S5FYv01997
	for <isis-wg@optimus.ietf.org>; Sat, 28 Sep 2002 01:15:34 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA19753
	for <isis-wg@ietf.org>; Sat, 28 Sep 2002 01:13:30 -0400 (EDT)
Received: from net4u.ch (adsl-63-200-49-94.dsl.snfc21.pacbell.net [63.200.49.94])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g8S5F2q24702;
	Sat, 28 Sep 2002 07:15:02 +0200
Message-ID: <3D952FEC.9010601@net4u.ch>
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Philip Christian <philip.christian@iname.com>
CC: jonathan.sadler@tellabs.com, isis-wg@ietf.org
Subject: Re: [Isis-wg] DDRP (was doubts)
References: <20020927084844.50474.qmail@iname.com>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 27 Sep 2002 21:28:28 -0700
Content-Transfer-Encoding: 7bit

Philip Christian wrote:

>Jonathan,
>
>My understanding was that DDRP is nothing more than a simple way of flooding TE type information around a cloud.  More specifically it uses the OSPF flooding mechanism, without the requirement for building an IP forwarding table.
>
well, if this effort is going on I would encourage to think very 
carefully about the 'link-state as a flooding mechanism we can 
piggy-back on' approach first.
 Throwing arbitrary 'stuff' into a link-state and letting it rip leads 
to tears and broken hearts. Some kind of scoping is needed. Whether it is a
hierarchy, a 'time-to-live', 'flooding-scope', 'summarization'  or other 
abstraction approach is a design decision but just thinking that TE can 
be flooded to all people in the whole ISIS cloud will bite ...

    maybe just saying the obvious

    -- tony

>
>Basically the layers of hierarchy are provided having multiple clouds which do not interact with each other, other than that the TE information "somehow" gets passed from one cloud into another.  My understanding was that the "somehow", which is actually the unique point, is not yet defined.
>
>If I am right then one could use IS-IS as a flooding mechanism instead (or any other).  The TE stuff could still be delivered to the edge of the cloud and passed onto the next (somehow), but the IS-IS LSPs wouldn't.  You wouldn't need 30,000 IP addresses either.
>
>Have I got it about right ?
>
>Philip
>
>
>
>
>----- Original Message -----
>From: Jonathan Sadler <jonathan.sadler@tellabs.com>
>Date: Thu, 26 Sep 2002 15:20:18 -0500 
>To: Jeff Parker <jparker@axiowave.com>
>Subject: Re: [Isis-wg] doubts
>
>
>>Jeff -
>>
>>Jeff Parker wrote:
>>
>>>>The biggest probably is the need to support
>>>>Multi-Level hierarchies with a depth greater
>>>>than 2.
>>>>
>>>        While I don't want to start a food fight
>>>here, can you help me understand why we need
>>>additional levels?  I have heard people mutter
>>>things about this for years, but I haven't
>>>really understood the point yet.
>>>
>>The main rationale has to do with the way that Telecom Service Providers
>>organize their operations staffs, as well as their networks, and the
>>size of those networks.  Many operate separate groups that individually
>>focus on Metro, Regional, National, and International networks. 
>>Consequently, there is natural summarization in the network designs. 
>>Couple this with aggregate SONET/SDH node counts of >30,000 (!) nodes
>>and you can see why they find hierarchy for ASON routing desireable.
>>
>>Jonathan Sadler
>>============================================================
>>The information contained in this message may be privileged 
>>and confidential and protected from disclosure.  If the 
>>reader of this message is not the intended recipient, or an 
>>employee or agent responsible for delivering this message to 
>>the intended recipient, you are hereby notified that any 
>>reproduction, dissemination or distribution of this 
>>communication is strictly prohibited. If you have received 
>>this communication in error, please notify us immediately by 
>>replying to the message and deleting it from your computer.
>>
>>Thank you.
>>Tellabs
>>============================================================
>>_______________________________________________
>>Isis-wg mailing list
>>Isis-wg@ietf.org
>>https://www1.ietf.org/mailman/listinfo/isis-wg
>>
>



_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 28 02:11:18 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29532
	for <isis-archive@lists.ietf.org>; Sat, 28 Sep 2002 02:11:18 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8S69Lv10577;
	Sat, 28 Sep 2002 02:09:21 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8S66Dv05273
	for <isis-wg@optimus.ietf.org>; Sat, 28 Sep 2002 02:06:13 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25657
	for <isis-wg@ietf.org>; Sat, 28 Sep 2002 02:04:09 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 547274BA21D; Fri, 27 Sep 2002 23:06:02 -0700 (PDT)
To: cmartin@gnilink.net, bneal@broadwing.com, sprevidi@cisco.com
Cc: isis-wg@ietf.org
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020928060602.547274BA21D@prattle.redback.com>
Subject: [Isis-wg] thoughts on isis-admin-tags draft
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Fri, 27 Sep 2002 23:06:02 -0700


one thing its not clear of the admin-tag operation is that,
when leaking happens in the level boundary, should the admin-tag
by default be removed or rewritten.

i think it would be useful to also define two categories of tags,
(regardless of 4/8 bytes tags). one is to be flooded only 
area wide, the other is for domain wide. the area-wide tagged
routes will not be leaked by default, but the domain-wide tagged
routes will be automatically leaked(either L1->L2 or L2->L1, they
should follow the rule of up/down of course), and the tag MUST
be copied over at the leaking boundary. for the same example
in the draft, if the property A route has a domain-wide tag,
property B has a area-wide tag. Then without any policy needed
at the "border" routers, the 1.1.1.0/24 will be automatically
leaked to every router in the domain and 1.1.2.0/24 will only
stay in the local area. this also get rid of the ambiguity of
if tag should be rewritten during leaking or not.

not only the admin-tag is useful to control the leak operation
between the levels, but many domain-wide applications can use those
tags. it will be very nice users do not need to worry about:
 1) if a route with this tag can be leaked at the level boundaries
 2) if the tag can be rewritten at the level boundaries

for any security concern, local policy should overwrite those
tag rules if needed. this is sort of like bgp's "transitive bit".

thanks.
- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 28 14:03:14 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08247
	for <isis-archive@lists.ietf.org>; Sat, 28 Sep 2002 14:03:14 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8SI0ov08989;
	Sat, 28 Sep 2002 14:00:51 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8SHtbv08882
	for <isis-wg@optimus.ietf.org>; Sat, 28 Sep 2002 13:55:37 -0400
Received: from net4u.net4u.ch (root@net4u.net4u.ch [194.191.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08122
	for <isis-wg@ietf.org>; Sat, 28 Sep 2002 13:53:38 -0400 (EDT)
Received: from net4u.ch (adsl-63-200-49-94.dsl.snfc21.pacbell.net [63.200.49.94])
	by net4u.net4u.ch (8.11.3/8.11.3) with ESMTP id g8SHtHq21066;
	Sat, 28 Sep 2002 19:55:17 +0200
Message-ID: <3D95ECFB.9090603@net4u.ch>
From: Tony Przygienda <prz@net4u.ch>
Reply-To: prz@net4u.ch
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Naiming Shen <naiming@redback.com>
CC: cmartin@gnilink.net, bneal@broadwing.com, sprevidi@cisco.com,
        isis-wg@ietf.org
Subject: Re: [Isis-wg] thoughts on isis-admin-tags draft
References: <20020928060602.547274BA21D@prattle.redback.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 28 Sep 2002 10:55:07 -0700
Content-Transfer-Encoding: 7bit

Naiming Shen wrote:

>one thing its not clear of the admin-tag operation is that,
>when leaking happens in the level boundary, should the admin-tag
>by default be removed or rewritten.
>
>i think it would be useful to also define two categories of tags,
>(regardless of 4/8 bytes tags). one is to be flooded only 
>area wide, the other is for domain wide. the area-wide tagged
>routes will not be leaked by default, but the domain-wide tagged
>routes will be automatically leaked(either L1->L2 or L2->L1, they
>should follow the rule of up/down of course), and the tag MUST
>be copied over at the leaking boundary. for the same example
>in the draft, if the property A route has a domain-wide tag,
>property B has a area-wide tag. Then without any policy needed
>at the "border" routers, the 1.1.1.0/24 will be automatically
>leaked to every router in the domain and 1.1.2.0/24 will only
>stay in the local area. this also get rid of the ambiguity of
>if tag should be rewritten during leaking or not.
>
>not only the admin-tag is useful to control the leak operation
>between the levels, but many domain-wide applications can use those
>tags. it will be very nice users do not need to worry about:
> 1) if a route with this tag can be leaked at the level boundaries
> 2) if the tag can be rewritten at the level boundaries
>
>for any security concern, local policy should overwrite those
>tag rules if needed. this is sort of like bgp's "transitive bit".
>
this is kind of a larger scope issue IMO, namely of a 'flooding scope' 
that connects to the DDRP thread.
We should think whether we want
a per fragment or a 'per-TLV, per-sub-TLV' flooding scope. per TLV would 
be cool _BUT_ it has a serious drawback,
one would need to 'repackage' other people fragments, a no-no, especally 
with authentication, _unless_
we only look at those tags when a TLV is 'reissued' for flooding 
purposes by a 'border-node' [which route
redistribution implies].    Maybe we even want both flooding scopes (I 
personally think that we will have
both hierarchy-defined flooding scopes and kind of 
'transitive'-attribute scopes as you indicate).
Just food for thought.



    -- tony



_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 28 15:42:39 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09815
	for <isis-archive@lists.ietf.org>; Sat, 28 Sep 2002 15:42:38 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8SJfRv12895;
	Sat, 28 Sep 2002 15:41:27 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8SJc7v12791
	for <isis-wg@optimus.ietf.org>; Sat, 28 Sep 2002 15:38:07 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA09744
	for <isis-wg@ietf.org>; Sat, 28 Sep 2002 15:36:08 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id C909A1DCC72; Sat, 28 Sep 2002 12:38:01 -0700 (PDT)
To: prz@net4u.ch
Cc: Naiming Shen <naiming@redback.com>, cmartin@gnilink.net,
        bneal@broadwing.com, sprevidi@cisco.com, isis-wg@ietf.org
Subject: Re: [Isis-wg] thoughts on isis-admin-tags draft 
In-reply-to: Mail from Tony Przygienda <prz@net4u.ch> 
 dated Sat, 28 Sep 2002 10:55:07 PDT
 <3D95ECFB.9090603@net4u.ch> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020928193801.C909A1DCC72@prattle.redback.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 28 Sep 2002 12:38:01 -0700


tony,

	yes, this is kind of "scoping". most of the protocols have some
kind of scoping. in ospf, the type 5 LSA; in bgp the "transitive bit" and
"no export" well known community; in multicast there is scoping boundary;
in IPv6(not really routing protocol) the site-locol. admin-tag is probably the
right place to put the scope for isis routing information.
	i would think this is not a fragment/TLV level scoping, but
it's an isis per-prefix scoping. usually for a router there is only
one prefix which need to be flooded over the domain. for isps
do not rewrite ebgp nexthops, they need more. gre source addresses
if not the same as the loopback for bgp, also need to be flooded over.
	since the draft already has a type field of this subtlv,
how about to have type 2 to be domain-wide scoping, and type 1 is
the area scoping subtlv for admin-tag. if its a type-2, it MUST be
flooding(leaked) over the entire domain(still observe the up/down bit),
and the admin-tag value(subtlv) MUST be copied over during the leaking
into another level. local policy can be used to allow all prefixes
leaking, to allow some prefixes leaking, or deny any prefix leaking.
if no policy is applied at the level boundary, then implementations
should follow the admin-tag scoping rule.
	the above is just the "hierarchical scoping" as you mentioned,
for ddrp kind of application, i would think its an isis route
redistribution between two isis instances(probably in level-2
backbone level). yes, the admin-tag can be carried over. but BGP
has the AS paths to detect looping, this does not. unless they want
to add diff admin-tag in each domain to detect the looping;-) then
why not just use bgp? bgp has multi-protocol mechanism already,
i'm sure they are willing to add clns into it...

thanks.

 ] Naiming Shen wrote:
 ] 
 ] >one thing its not clear of the admin-tag operation is that,
 ] >when leaking happens in the level boundary, should the admin-tag
 ] >by default be removed or rewritten.
 ] >
 ] >i think it would be useful to also define two categories of tags,
 ] >(regardless of 4/8 bytes tags). one is to be flooded only 
 ] >area wide, the other is for domain wide. the area-wide tagged
 ] >routes will not be leaked by default, but the domain-wide tagged
 ] >routes will be automatically leaked(either L1->L2 or L2->L1, they
 ] >should follow the rule of up/down of course), and the tag MUST
 ] >be copied over at the leaking boundary. for the same example
 ] >in the draft, if the property A route has a domain-wide tag,
 ] >property B has a area-wide tag. Then without any policy needed
 ] >at the "border" routers, the 1.1.1.0/24 will be automatically
 ] >leaked to every router in the domain and 1.1.2.0/24 will only
 ] >stay in the local area. this also get rid of the ambiguity of
 ] >if tag should be rewritten during leaking or not.
 ] >
 ] >not only the admin-tag is useful to control the leak operation
 ] >between the levels, but many domain-wide applications can use those
 ] >tags. it will be very nice users do not need to worry about:
 ] > 1) if a route with this tag can be leaked at the level boundaries
 ] > 2) if the tag can be rewritten at the level boundaries
 ] >
 ] >for any security concern, local policy should overwrite those
 ] >tag rules if needed. this is sort of like bgp's "transitive bit".
 ] >
 ] this is kind of a larger scope issue IMO, namely of a 'flooding scope' 
 ] that connects to the DDRP thread.
 ] We should think whether we want
 ] a per fragment or a 'per-TLV, per-sub-TLV' flooding scope. per TLV would 
 ] be cool _BUT_ it has a serious drawback,
 ] one would need to 'repackage' other people fragments, a no-no, especally 
 ] with authentication, _unless_
 ] we only look at those tags when a TLV is 'reissued' for flooding 
 ] purposes by a 'border-node' [which route
 ] redistribution implies].    Maybe we even want both flooding scopes (I 
 ] personally think that we will have
 ] both hierarchy-defined flooding scopes and kind of 
 ] 'transitive'-attribute scopes as you indicate).
 ] Just food for thought.
 ] 
 ] 
 ] 
 ]     -- tony
 ] 
 ] 
 ] 

- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 28 17:45:51 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11337
	for <isis-archive@lists.ietf.org>; Sat, 28 Sep 2002 17:45:51 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8SLiZv17839;
	Sat, 28 Sep 2002 17:44:36 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8SLfdv17775
	for <isis-wg@optimus.ietf.org>; Sat, 28 Sep 2002 17:41:39 -0400
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA11247
	for <isis-wg@ietf.org>; Sat, 28 Sep 2002 17:39:38 -0400 (EDT)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.12.2/8.12.2) with ESMTP id g8SLf4TG014416;
	Sat, 28 Sep 2002 17:41:04 -0400 (EDT)
Received: from JLEARMAN-W2K1.cisco.com (rtp-vpn1-546.cisco.com [10.82.226.34])
	by dingdong.cisco.com (Mirapoint Messaging Server MOS 3.1.0.66-GA)
	with ESMTP id AAE37687;
	Sat, 28 Sep 2002 17:40:58 -0400 (EDT)
Message-Id: <4.3.2.7.2.20020928172602.03989318@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: jonathan.sadler@tellabs.com
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] DDRP (was doubts)
Cc: Mike Truskowski <truskows@cisco.com>, philip.christian@iname.com,
        isis-wg@ietf.org
In-Reply-To: <3D94FD26.1845041E@tellabs.com>
References: <H0000c08056502ec.1033144168.mailw02@MHS>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 28 Sep 2002 17:40:53 -0400

At 08:51 PM 9/27/2002, Jonathan Sadler wrote:

>Given this design, a 4-level hierarchical routing protocol is
>necessary.  And we havn't even started adding levels to deal with
>the interconnection points between service providers.

Those should definitely be inter-domain routing protocols, not intra-domain.
And while I don't doubt that there's a potential benefit to multi-level
IS-IS, it also may make the most sense to use inter-domain routing
between high-level regions within a single service provider (based
on administrative autonomy).

If you're serious about multi-level IS-IS, I know that Radia Perlman
had an idea of how to add this a couple years back, but there wasn't
enough interest in it in the industry for her to dig into it very far.

My understanding, drawn almost entirely from responses on this mail
list, is that very few networks even run 2-level IS-IS.  I realize that
this is based on ISP networks, as opposed to embedded telecom
management networks.  In support of your arguments, though, I understand
that in embedded telecom management networks, it isn't possible to
simply "build a manageable network" like it is when the routing protocol
is supporting the payload traffic.  Instead, there are a number of                                                      
complicated driving principles in the network design, and the foremost
are those concerning the payload network topology -- the embedded
management network topology considerations are secondary.  Most router
jocks are simply not used to this kind of situation and it's
understandable that they have difficulty envisioning the need for
the complexity.  "Why in the heck would you design a routing network
using cascading rings?  Why are you using such underpowered routers?"  ;)

Regards,
Jeff


Regards,
Jeff

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 28 21:47:48 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15732
	for <isis-archive@lists.ietf.org>; Sat, 28 Sep 2002 21:47:48 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8T1e1v26497;
	Sat, 28 Sep 2002 21:40:01 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8T1aYv25868
	for <isis-wg@optimus.ietf.org>; Sat, 28 Sep 2002 21:36:34 -0400
Received: from entmail.gnilink.net (entmail.gnilink.net [199.45.47.10])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15308
	for <isis-wg@ietf.org>; Sat, 28 Sep 2002 21:34:32 -0400 (EDT)
Received: by entmail.gnilink.com with Internet Mail Service (5.5.2656.59)
	id <TRPKPV8S>; Sat, 28 Sep 2002 21:35:53 -0400
Message-ID: <94B9091E1149D411A45C00508BACEB35015F3304@entmail.gnilink.com>
From: "Martin, Christian" <cmartin@gnilink.net>
To: "'Naiming Shen'" <naiming@redback.com>, prz@net4u.ch
Cc: "Martin, Christian" <cmartin@gnilink.net>, bneal@broadwing.com,
        sprevidi@cisco.com, isis-wg@ietf.org
Subject: RE: [Isis-wg] thoughts on isis-admin-tags draft 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2656.59)
Content-Type: text/plain
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 28 Sep 2002 21:35:47 -0400

Tony, Naiming,

Perhaps we should have been more specific with our wording.  The intention
was to make the tag values domain-wide, unless the local policy at the L1/L2
boundary dictates otherwise:

From section 8:

   [...] When IS-IS advertises reachability for some IP
   prefix that has that property, it adds the Administrative Tag to the
   IP reachability information TLV for that prefix, and the tag "sticks"
   to the prefix as it is flooded throughout the routing domian.

Also, from section 6.

   [...] If an implementation needs to
   change tag values, for example, at an area boundary, then the TLV(s)
   SHOULD be copied to the newly generated Level-1 or Level-2 LSP at
   which point, the contents of the SubTLV(s) MAY change as dictated by
   the policy action.

I suppose it depends on where the implementations are at this point,
particularly with regards to the TE extensions implementations.  How are TLV
135 prefixes being treated at the L1/L2 boundary?  AFAIK, they are
regenerated in a new LSP, so the same should apply to the sub-TLVs.

Thoughts?

-chris



> -----Original Message-----
> From: Naiming Shen [mailto:naiming@redback.com] 
> Sent: Saturday, September 28, 2002 3:38 PM
> To: prz@net4u.ch
> Cc: Naiming Shen; cmartin@gnilink.net; bneal@broadwing.com; 
> sprevidi@cisco.com; isis-wg@ietf.org
> Subject: Re: [Isis-wg] thoughts on isis-admin-tags draft 
> 
> 
> 
> tony,
> 
> 	yes, this is kind of "scoping". most of the protocols have some
> kind of scoping. in ospf, the type 5 LSA; in bgp the 
> "transitive bit" and
> "no export" well known community; in multicast there is 
> scoping boundary;
> in IPv6(not really routing protocol) the site-locol. 
> admin-tag is probably the
> right place to put the scope for isis routing information.
> 	i would think this is not a fragment/TLV level scoping, but
> it's an isis per-prefix scoping. usually for a router there is only
> one prefix which need to be flooded over the domain. for isps
> do not rewrite ebgp nexthops, they need more. gre source addresses
> if not the same as the loopback for bgp, also need to be flooded over.
> 	since the draft already has a type field of this subtlv,
> how about to have type 2 to be domain-wide scoping, and type 1 is
> the area scoping subtlv for admin-tag. if its a type-2, it MUST be
> flooding(leaked) over the entire domain(still observe the 
> up/down bit),
> and the admin-tag value(subtlv) MUST be copied over during the leaking
> into another level. local policy can be used to allow all prefixes
> leaking, to allow some prefixes leaking, or deny any prefix leaking.
> if no policy is applied at the level boundary, then implementations
> should follow the admin-tag scoping rule.
> 	the above is just the "hierarchical scoping" as you mentioned,
> for ddrp kind of application, i would think its an isis route
> redistribution between two isis instances(probably in level-2
> backbone level). yes, the admin-tag can be carried over. but BGP
> has the AS paths to detect looping, this does not. unless they want
> to add diff admin-tag in each domain to detect the looping;-) then
> why not just use bgp? bgp has multi-protocol mechanism already,
> i'm sure they are willing to add clns into it...
> 
> thanks.
> 
>  ] Naiming Shen wrote:
>  ] 
>  ] >one thing its not clear of the admin-tag operation is that,
>  ] >when leaking happens in the level boundary, should the admin-tag
>  ] >by default be removed or rewritten.
>  ] >
>  ] >i think it would be useful to also define two categories of tags,
>  ] >(regardless of 4/8 bytes tags). one is to be flooded only 
>  ] >area wide, the other is for domain wide. the area-wide tagged
>  ] >routes will not be leaked by default, but the domain-wide tagged
>  ] >routes will be automatically leaked(either L1->L2 or L2->L1, they
>  ] >should follow the rule of up/down of course), and the tag MUST
>  ] >be copied over at the leaking boundary. for the same example
>  ] >in the draft, if the property A route has a domain-wide tag,
>  ] >property B has a area-wide tag. Then without any policy needed
>  ] >at the "border" routers, the 1.1.1.0/24 will be automatically
>  ] >leaked to every router in the domain and 1.1.2.0/24 will only
>  ] >stay in the local area. this also get rid of the ambiguity of
>  ] >if tag should be rewritten during leaking or not.
>  ] >
>  ] >not only the admin-tag is useful to control the leak operation
>  ] >between the levels, but many domain-wide applications can 
> use those
>  ] >tags. it will be very nice users do not need to worry about:
>  ] > 1) if a route with this tag can be leaked at the level boundaries
>  ] > 2) if the tag can be rewritten at the level boundaries
>  ] >
>  ] >for any security concern, local policy should overwrite those
>  ] >tag rules if needed. this is sort of like bgp's "transitive bit".
>  ] >
>  ] this is kind of a larger scope issue IMO, namely of a 
> 'flooding scope' 
>  ] that connects to the DDRP thread.
>  ] We should think whether we want
>  ] a per fragment or a 'per-TLV, per-sub-TLV' flooding scope. 
> per TLV would 
>  ] be cool _BUT_ it has a serious drawback,
>  ] one would need to 'repackage' other people fragments, a 
> no-no, especally 
>  ] with authentication, _unless_
>  ] we only look at those tags when a TLV is 'reissued' for flooding 
>  ] purposes by a 'border-node' [which route
>  ] redistribution implies].    Maybe we even want both 
> flooding scopes (I 
>  ] personally think that we will have
>  ] both hierarchy-defined flooding scopes and kind of 
>  ] 'transitive'-attribute scopes as you indicate).
>  ] Just food for thought.
>  ] 
>  ] 
>  ] 
>  ]     -- tony
>  ] 
>  ] 
>  ] 
> 
> - Naiming
> 
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Sat Sep 28 22:06:20 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15902
	for <isis-archive@lists.ietf.org>; Sat, 28 Sep 2002 22:06:20 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8T25Jv27056;
	Sat, 28 Sep 2002 22:05:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8T22Qv27013
	for <isis-wg@optimus.ietf.org>; Sat, 28 Sep 2002 22:02:26 -0400
Received: from prattle.redback.com (hiddenuser@prattle.redback.com [155.53.12.9])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA15837
	for <isis-wg@ietf.org>; Sat, 28 Sep 2002 22:00:24 -0400 (EDT)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 1F723F2C5C; Sat, 28 Sep 2002 19:02:18 -0700 (PDT)
To: "Martin, Christian" <cmartin@gnilink.net>
Cc: "'Naiming Shen'" <naiming@redback.com>, prz@net4u.ch, bneal@broadwing.com,
        sprevidi@cisco.com, isis-wg@ietf.org
Subject: Re: [Isis-wg] thoughts on isis-admin-tags draft 
In-reply-to: Mail from "Martin, Christian" <cmartin@gnilink.net> 
 dated Sat, 28 Sep 2002 21:35:47 EDT
 <94B9091E1149D411A45C00508BACEB35015F3304@entmail.gnilink.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20020929020218.1F723F2C5C@prattle.redback.com>
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Sat, 28 Sep 2002 19:02:18 -0700


Chris,

 ] Tony, Naiming,
 ] 
 ] Perhaps we should have been more specific with our wording.  The intention
 ] was to make the tag values domain-wide, unless the local policy at the L1/L2
 ] boundary dictates otherwise:
 ] 
 ] >From section 8:
 ] 
 ]    [...] When IS-IS advertises reachability for some IP
 ]    prefix that has that property, it adds the Administrative Tag to the
 ]    IP reachability information TLV for that prefix, and the tag "sticks"
 ]    to the prefix as it is flooded throughout the routing domian.

it needs to add MUST "sticks" here if this is the intention.

 ] 
 ] Also, from section 6.
 ] 
 ]    [...] If an implementation needs to
 ]    change tag values, for example, at an area boundary, then the TLV(s)
 ]    SHOULD be copied to the newly generated Level-1 or Level-2 LSP at
 ]    which point, the contents of the SubTLV(s) MAY change as dictated by
 ]    the policy action.

this is a local policy issue, which is fine.

 ] 
 ] I suppose it depends on where the implementations are at this point,
 ] particularly with regards to the TE extensions implementations.  How are TLV
 ] 135 prefixes being treated at the L1/L2 boundary?  AFAIK, they are
 ] regenerated in a new LSP, so the same should apply to the sub-TLVs.
 ] 
 ] Thoughts?

i think what i ask is not so much about the tag value is kept in
the level transition, but how the PREFIX itself will be flooded
differently due to such a admin-tag is attached.

for most of the implementations i know of, L2->L1 leaking is not
done by default, a configuration with policy needs to be defined
to enable this; but L1->L2 is done automatically. If we can have
the "scope" capability of the admin-tag, then by default without
any policy, the "domain-wide" admin-tagged routes will be flooded
to entire domain by DEFAULT, and "area-wide" admin-tagged routes
will be flooded only within the area by DEFAULT. Even in the
implementation by default, if routes without admin-tag, L1->L2
is leaked and L2->L1 is NOT leaked.

thanks.
 ] 
 ] -chris
 ] 
 ] 
 ] 
 ] > -----Original Message-----
 ] > From: Naiming Shen [mailto:naiming@redback.com] 
 ] > Sent: Saturday, September 28, 2002 3:38 PM
 ] > To: prz@net4u.ch
 ] > Cc: Naiming Shen; cmartin@gnilink.net; bneal@broadwing.com; 
 ] > sprevidi@cisco.com; isis-wg@ietf.org
 ] > Subject: Re: [Isis-wg] thoughts on isis-admin-tags draft 
 ] > 
 ] > 
 ] > 
 ] > tony,
 ] > 
 ] > 	yes, this is kind of "scoping". most of the protocols have some
 ] > kind of scoping. in ospf, the type 5 LSA; in bgp the 
 ] > "transitive bit" and
 ] > "no export" well known community; in multicast there is 
 ] > scoping boundary;
 ] > in IPv6(not really routing protocol) the site-locol. 
 ] > admin-tag is probably the
 ] > right place to put the scope for isis routing information.
 ] > 	i would think this is not a fragment/TLV level scoping, but
 ] > it's an isis per-prefix scoping. usually for a router there is only
 ] > one prefix which need to be flooded over the domain. for isps
 ] > do not rewrite ebgp nexthops, they need more. gre source addresses
 > if not the same as the loopback for bgp, also need to be flooded over.
 ] > 	since the draft already has a type field of this subtlv,
 ] > how about to have type 2 to be domain-wide scoping, and type 1 is
 ] > the area scoping subtlv for admin-tag. if its a type-2, it MUST be
 ] > flooding(leaked) over the entire domain(still observe the 
 ] > up/down bit),
 ] > and the admin-tag value(subtlv) MUST be copied over during the leaking
 ] > into another level. local policy can be used to allow all prefixes
 ] > leaking, to allow some prefixes leaking, or deny any prefix leaking.
 ] > if no policy is applied at the level boundary, then implementations
 ] > should follow the admin-tag scoping rule.
 ] > 	the above is just the "hierarchical scoping" as you mentioned,
 ] > for ddrp kind of application, i would think its an isis route
 ] > redistribution between two isis instances(probably in level-2
 ] > backbone level). yes, the admin-tag can be carried over. but BGP
 ] > has the AS paths to detect looping, this does not. unless they want
 ] > to add diff admin-tag in each domain to detect the looping;-) then
 ] > why not just use bgp? bgp has multi-protocol mechanism already,
 ] > i'm sure they are willing to add clns into it...
 ] > 
 ] > thanks.
 ] > 
 ] >  ] Naiming Shen wrote:
 ] >  ] 
 ] >  ] >one thing its not clear of the admin-tag operation is that,
 ] >  ] >when leaking happens in the level boundary, should the admin-tag
 ] >  ] >by default be removed or rewritten.
 ] >  ] >
 ] >  ] >i think it would be useful to also define two categories of tags,
 ] >  ] >(regardless of 4/8 bytes tags). one is to be flooded only 
 ] >  ] >area wide, the other is for domain wide. the area-wide tagged
 ] >  ] >routes will not be leaked by default, but the domain-wide tagged
 ] >  ] >routes will be automatically leaked(either L1->L2 or L2->L1, they
 ] >  ] >should follow the rule of up/down of course), and the tag MUST
 ] >  ] >be copied over at the leaking boundary. for the same example
 ] >  ] >in the draft, if the property A route has a domain-wide tag,
 ] >  ] >property B has a area-wide tag. Then without any policy needed
 ] >  ] >at the "border" routers, the 1.1.1.0/24 will be automatically
 ] >  ] >leaked to every router in the domain and 1.1.2.0/24 will only
 ] >  ] >stay in the local area. this also get rid of the ambiguity of
 ] >  ] >if tag should be rewritten during leaking or not.
 ] >  ] >
 ] >  ] >not only the admin-tag is useful to control the leak operation
 ] >  ] >between the levels, but many domain-wide applications can 
 ] > use those
 ] >  ] >tags. it will be very nice users do not need to worry about:
 ] >  ] > 1) if a route with this tag can be leaked at the level boundaries
 ] >  ] > 2) if the tag can be rewritten at the level boundaries
 ] >  ] >
 ] >  ] >for any security concern, local policy should overwrite those
 ] >  ] >tag rules if needed. this is sort of like bgp's "transitive bit".
 ] >  ] >
 ] >  ] this is kind of a larger scope issue IMO, namely of a 
 ] > 'flooding scope' 
 ] >  ] that connects to the DDRP thread.
 ] >  ] We should think whether we want
 ] >  ] a per fragment or a 'per-TLV, per-sub-TLV' flooding scope. 
 ] > per TLV would 
 ] >  ] be cool _BUT_ it has a serious drawback,
 ] >  ] one would need to 'repackage' other people fragments, a 
 ] > no-no, especally 
 ] >  ] with authentication, _unless_
 ] >  ] we only look at those tags when a TLV is 'reissued' for flooding 
 ] >  ] purposes by a 'border-node' [which route
 ] >  ] redistribution implies].    Maybe we even want both 
 ] > flooding scopes (I 
 ] >  ] personally think that we will have
 ] >  ] both hierarchy-defined flooding scopes and kind of 
 ] >  ] 'transitive'-attribute scopes as you indicate).
 ] >  ] Just food for thought.
 ] >  ] 
 ] >  ] 
 ] >  ] 
 ] >  ]     -- tony
 ] >  ] 
 ] >  ] 
 ] >  ] 
 ] > 
 ] > - Naiming
 ] > 
 ] _______________________________________________
 ] Isis-wg mailing list
 ] Isis-wg@ietf.org
 ] https://www1.ietf.org/mailman/listinfo/isis-wg

- Naiming
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 30 02:36:49 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA25158
	for <isis-archive@lists.ietf.org>; Mon, 30 Sep 2002 02:36:49 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U6Xxv16474;
	Mon, 30 Sep 2002 02:33:59 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U5lAv06202
	for <isis-wg@optimus.ietf.org>; Mon, 30 Sep 2002 01:47:10 -0400
Received: from blooper.utfors.se (mail.utfors.se [195.58.103.125])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA15259
	for <isis-wg@ietf.org>; Mon, 30 Sep 2002 01:45:03 -0400 (EDT)
Received: from utfors.se (nat-sto.utfors.se [212.73.0.237])
	by blooper.utfors.se (8.12.6/8.12.6) with ESMTP id g8U5kRtA012847;
	Mon, 30 Sep 2002 07:46:27 +0200 (MEST)
Message-ID: <3D97E533.2020107@utfors.se>
From: Loa Andersson <loa.andersson@utfors.se>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: ospf wg <OSPF@DISCUSS.MICROSOFT.COM>, isis-wg <isis-wg@ietf.org>
CC: Loa Andersson <loa.andersson@utfors.se>, MPLS wg <mpls@uu.net>
References: <3D6DBFBE.4050603@utfors.se> <3D7CC9FF.6010509@utfors.se>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Content-Transfer-Encoding: 8bit
Subject: [Isis-wg] Last Call: draft-ietf-mpls-bundle-04.txt - has ended
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 30 Sep 2002 07:46:27 +0200
Content-Transfer-Encoding: 8bit

All,

the last call on the

<draft-ietf-mpls-bundle-04.txt>

on the ospf and isis list has ended. Thanks for comments.

/Loa

Loa Andersson wrote:
> All,
> 
> it is my understanding that there has been some hick-ups on
> the is-is list, so I'm re-issueing this last call and extending
> the time to September 29th. At the same time I would like point out
> that there is an acompanying mib draft-ietf-mpls-bundle-mib-03.txt.
> 
> Also comments on the mib is welcome.
> 
> BTW, thanks to those of you who already sent us comments :)
> 
> The wg last call on
> 
>  <draft-ietf-mpls-bundle-04.txt>
>  <draft-ietf-mpls-bundle-mib-03.txt>
> 
> has been extended to September 29.
> 
> /Loa
> 
> Loa Andersson wrote:
> 
>> OSPF and IS-IS working groups, (mpls wg for info)
>>
>> the iesg has started the review of the mpls working group draft
>> draft-ietf-mpls-bundle-04.txt. The immediate response from the iesg
>> is that the draft contains OSPF and ISIS related details (see
>> the included mail). After discussing with the wg chairs for ospf
>> and is-is working groups, there is a feeling that the two weeks
>> the iesg allocated for this last call might not be enough, since the
>> draft has not been widely circulated in the routing working groups.
>>
>> Therefore:
>>
>> This is to initiate a last call for the
>>
>> <draft-ietf-mpls-bundle-04.txt>
>>
>> by the ospf and is-is working groups.
>> The last call ends September 22nd at 12PM CET
>>
>>
>> Please include the mpls mailing list (mpls@uu.net) in your responses.
>>
>> /Loa (co-chair of the mpls wg)
>>
>> -------- Original Message --------
>> Subject: draft-ietf-mpls-bundle-04.txt
>> Date: Tue, 27 Aug 2002 15:06:48 -0400 (EDT)
>> From: Scott Bradner
>> To: loa.andersson@utfors.se, swallow@cisco.com
>>
>>
>> The IESG discussed this ID last week during its teleconference
>> one issue was raised during the discussion
>>
>> "the draft contains OSPF & ISIS
>> related details and I don't remember it being LC'ed or reviewed
>> in the corresponding WGs."
>>
>> can you start a 2 week last call on the IS-IS and OSPF mailing
>> lists for this document?
>>
>> Scott
>>
> 
> 


-- 
     Loa Andersson
     Chief Architect,
     Utfors Research, Architecture and Future Lab (URAX)
     Utfors AB
     Råsundavägen 12
     Box 525, 169 29 Solna
     Office          +46 8 5270 2000
     Office direct   +46 8 5270 5038
     Mobile          +46 70 848 5038
     Email           loa.andersson@utfors.se
     WWW             www.utfors.se


_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


From isis-wg-admin@ietf.org  Mon Sep 30 03:41:54 2002
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25885
	for <isis-archive@lists.ietf.org>; Mon, 30 Sep 2002 03:41:54 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U7bjv20097;
	Mon, 30 Sep 2002 03:37:45 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id g8U7Ykv19480
	for <isis-wg@optimus.ietf.org>; Mon, 30 Sep 2002 03:34:46 -0400
Received: from cisco.com (mrwint.cisco.com [144.254.98.48])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA25812
	for <isis-wg@ietf.org>; Mon, 30 Sep 2002 03:32:37 -0400 (EDT)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4168.cisco.com [10.50.16.71])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id IAA15135;
	Mon, 30 Sep 2002 08:33:35 +0100 (BST)
Message-Id: <4.3.2.7.2.20020930082838.028f8088@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: prz@net4u.ch
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] DDRP (was doubts)
Cc: Philip Christian <philip.christian@iname.com>, jonathan.sadler@tellabs.com,
        isis-wg@ietf.org
In-Reply-To: <3D952FEC.9010601@net4u.ch>
References: <20020927084844.50474.qmail@iname.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@ietf.org
Errors-To: isis-wg-admin@ietf.org
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/isis-wg/>
Date: Mon, 30 Sep 2002 08:33:32 +0100

I strongly agree with Tony. And on the matter of multi-level hierarchies, 
don't forget that there is no need to invent new protocol mechanisms (or 
packet types) to do this. You can get most of what you would want simply by 
running the level 2 protocol multiple times, with suitable scoping rules.

         Mike

At 21:28 27/09/2002 -0700, Tony Przygienda wrote:
>Philip Christian wrote:
>
>>Jonathan,
>>
>>My understanding was that DDRP is nothing more than a simple way of 
>>flooding TE type information around a cloud.  More specifically it uses 
>>the OSPF flooding mechanism, without the requirement for building an IP 
>>forwarding table.
>well, if this effort is going on I would encourage to think very carefully 
>about the 'link-state as a flooding mechanism we can piggy-back on' 
>approach first.
>Throwing arbitrary 'stuff' into a link-state and letting it rip leads to 
>tears and broken hearts. Some kind of scoping is needed. Whether it is a
>hierarchy, a 'time-to-live', 'flooding-scope', 'summarization'  or other 
>abstraction approach is a design decision but just thinking that TE can be 
>flooded to all people in the whole ISIS cloud will bite ...
>
>    maybe just saying the obvious
>
>    -- tony
>
>>
>>Basically the layers of hierarchy are provided having multiple clouds 
>>which do not interact with each other, other than that the TE information 
>>"somehow" gets passed from one cloud into another.  My understanding was 
>>that the "somehow", which is actually the unique point, is not yet defined.
>>
>>If I am right then one could use IS-IS as a flooding mechanism instead 
>>(or any other).  The TE stuff could still be delivered to the edge of the 
>>cloud and passed onto the next (somehow), but the IS-IS LSPs 
>>wouldn't.  You wouldn't need 30,000 IP addresses either.
>>
>>Have I got it about right ?
>>
>>Philip
>>
>>
>>
>>
>>----- Original Message -----
>>From: Jonathan Sadler <jonathan.sadler@tellabs.com>
>>Date: Thu, 26 Sep 2002 15:20:18 -0500 To: Jeff Parker <jparker@axiowave.com>
>>Subject: Re: [Isis-wg] doubts
>>
>>
>>>Jeff -
>>>
>>>Jeff Parker wrote:
>>>
>>>>>The biggest probably is the need to support
>>>>>Multi-Level hierarchies with a depth greater
>>>>>than 2.
>>>>        While I don't want to start a food fight
>>>>here, can you help me understand why we need
>>>>additional levels?  I have heard people mutter
>>>>things about this for years, but I haven't
>>>>really understood the point yet.
>>>The main rationale has to do with the way that Telecom Service Providers
>>>organize their operations staffs, as well as their networks, and the
>>>size of those networks.  Many operate separate groups that individually
>>>focus on Metro, Regional, National, and International networks. 
>>>Consequently, there is natural summarization in the network designs. 
>>>Couple this with aggregate SONET/SDH node counts of >30,000 (!) nodes
>>>and you can see why they find hierarchy for ASON routing desireable.
>>>
>>>Jonathan Sadler
>>>============================================================
>>>The information contained in this message may be privileged and 
>>>confidential and protected from disclosure.  If the reader of this 
>>>message is not the intended recipient, or an employee or agent 
>>>responsible for delivering this message to the intended recipient, you 
>>>are hereby notified that any reproduction, dissemination or distribution 
>>>of this communication is strictly prohibited. If you have received this 
>>>communication in error, please notify us immediately by replying to the 
>>>message and deleting it from your computer.
>>>
>>>Thank you.
>>>Tellabs
>>>============================================================
>>>_______________________________________________
>>>Isis-wg mailing list
>>>Isis-wg@ietf.org
>>>https://www1.ietf.org/mailman/listinfo/isis-wg
>
>
>
>_______________________________________________
>Isis-wg mailing list
>Isis-wg@ietf.org
>https://www1.ietf.org/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org
https://www1.ietf.org/mailman/listinfo/isis-wg


