From isis-wg-admin@spider.juniper.net  Sat Dec  1 05:14:16 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10340
	for <isis-archive@lists.ietf.org>; Sat, 1 Dec 2001 05:14:16 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA95793;
	Sat, 1 Dec 2001 02:31:51 -0800 (PST)
Received: from hotmail.com (f63.law3.hotmail.com [209.185.241.63])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA95778
	for <isis-wg@external.juniper.net>; Sat, 1 Dec 2001 02:30:01 -0800 (PST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Sat, 1 Dec 2001 02:08:51 -0800
Received: from 203.196.145.150 by lw3fd.law3.hotmail.msn.com with HTTP;
	Sat, 01 Dec 2001 10:08:50 GMT
X-Originating-IP: [203.196.145.150]
From: "Sachidananda K" <sachidananda_k@hotmail.com>
To: isis-wg@spider.juniper.net
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F63AHbx4Rrnu2CCbJz900016d27@hotmail.com>
X-OriginalArrivalTime: 01 Dec 2001 10:08:51.0062 (UTC) FILETIME=[2CCBF160:01C17A50]
Subject: [Isis-wg] IIHs Optional TLV
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 01 Dec 2001 10:08:50 +0000

Hi,

I have a doubt regarding the nubmer of times the below mentioned TLVs can 
appear in the IIH PDUs.
1. Area Address TLVs.
2. IP interface TLVs.
3. Protocol Supported TLVs.

Does the standard impose any restriction on the number of times these TLVs 
can appear in a IIH (LAN or P2P).

Pls help me understand ISIS better.
Thanking you in advance.
Sachi

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

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec  3 14:18:09 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23032
	for <isis-archive@lists.ietf.org>; Mon, 3 Dec 2001 14:18:07 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA11154;
	Mon, 3 Dec 2001 11:36:52 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA99477
	for <isis-wg@spider.juniper.net>; Sat, 1 Dec 2001 10:06:25 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fB1HjC283394
	for <isis-wg@juniper.net>; Sat, 1 Dec 2001 09:45:12 -0800 (PST)
X-JNPR-Received-From: outside
Received: from ghostrider.gredler.at ([193.83.223.228]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Sat, 1 Dec 2001 09:42:23 -0800
Received: (from hannes@localhost)
	by ghostrider.gredler.at (8.9.3/8.9.3) id SAA11087;
	Sat, 1 Dec 2001 18:43:41 +0100
From: Hannes Gredler <hannes@juniper.net>
To: Sachidananda K <sachidananda_k@hotmail.com>
Cc: isis-wg@juniper.net
Subject: Re: [Isis-wg] IIHs Optional TLV
Message-ID: <20011201184340.A11078@juniper.net>
References: <F63AHbx4Rrnu2CCbJz900016d27@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <F63AHbx4Rrnu2CCbJz900016d27@hotmail.com>; from sachidananda_k@hotmail.com on Sat, Dec 01, 2001 at 10:08:50AM +0000
X-OriginalArrivalTime: 01 Dec 2001 17:42:23.0625 (UTC) FILETIME=[88BF8790:01C17A8F]
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 1 Dec 2001 18:43:40 +0100

On Sat, Dec 01, 2001 at 10:08:50AM +0000, Sachidananda K wrote:
| Hi,
| 
| I have a doubt regarding the nubmer of times the below mentioned TLVs can 
| appear in the IIH PDUs.
| 1. Area Address TLVs.
| 2. IP interface TLVs.
| 3. Protocol Supported TLVs.
| 
| Does the standard impose any restriction on the number of times these TLVs 
| can appear in a IIH (LAN or P2P).

sachi, 

as long the number of total areas does not contratict the number of
areas in the is-is commmon header TLV #1 can occur more than one
time;

the IP interface TLV and the protcols supported TLV can occur also
several times;

however, practically speaking the most-common implementations support
upto three areas. given the max. NSAP size of 20 bytes and
assuming that the sys-len = 6 bytes there
are upto 13 bytes to carry; an additional byte is needed
for the area-adress length field; so this results in 
14*3 = 42 bytes which fit quite easily into a single TLV;

most systems today support IPv4 routing, some of them support additionally
IPv6; so the typical prot.supported TLV is filled with 2 bytes - again no
need for several occurences of TLV #129;

given that you do not have more than 21 IP adresses configured
on your physical interface you mostly find also just one occurence of
TLV #132;

/hannes

| Pls help me understand ISIS better.
| Thanking you in advance.
| Sachi
| 
| _________________________________________________________________
| Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
| 
| _______________________________________________
| Isis-wg mailing list  -  Isis-wg@external.juniper.net
| http://external.juniper.net/mailman/listinfo/isis-wg
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec  3 14:23:46 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA23458
	for <isis-archive@lists.ietf.org>; Mon, 3 Dec 2001 14:23:45 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA11199;
	Mon, 3 Dec 2001 11:43:29 -0800 (PST)
Received: from hoemail2.firewall.lucent.com (hoemail2.lucent.com [192.11.226.163])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA03519
	for <isis-wg@spider.juniper.net>; Sun, 2 Dec 2001 02:41:41 -0800 (PST)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.1.3/Switch-2.1.0) with ESMTP id fB2AKMe21165
	for <isis-wg@spider.juniper.net>; Sun, 2 Dec 2001 05:20:22 -0500 (EST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <WNHC1W8Z>; Sun, 2 Dec 2001 11:20:16 +0100
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB0E05AF10@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Jeff Parker <jparker@axiowave.com>,
        "IS-IS-WG (E-mail)"
	 <isis-wg@spider.juniper.net>
Cc: "Bert Wijnen (Bert) (E-mail)" <bwijnen@lucent.com>,
        "'KChapman@unispherenetworks.com'" <KChapman@unispherenetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Aligning MIB values with Implementation values
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 2 Dec 2001 11:20:09 +0100

Inline

> -----Original Message-----
> From: Jeff Parker [mailto:jparker@axiowave.com]
> Sent: Thursday, November 29, 2001 11:30 PM
> To: IS-IS-WG (E-mail)
> Cc: Bert Wijnen (Bert) (E-mail); 'KChapman@unispherenetworks.com'
> Subject: Aligning MIB values with Implementation values
> 
> 
> I've received the following request to align MIB values with
> implementation values.  
> 
> As Neal notes, I had been following an admonition to avoid the
> use of 0 as the value of an enumeration.  However, I don't
> think this is a prohibition.  
> 
> There are two things we could do:
> 	Make the mapping be the identity (so that Up becomes 0, etc)
> 	Make the mapping be addition (subtraction) by 1
> 
> Any objections to doing the first?
> 
It is recommended that enumerations start at 1.
But not prohibeted as you state. And you seem to have a valid reason
to not follow the receommendation. Maybe you can add some text to the
DESCRIPTION clause to explain why you start at zero.

Bert
> - jeff parker
> - axiowave networks
> 
> ///////////////////////////////////////////////////
> 
> Jeff,
> 
> The isisISAdjState values are inconsistent with the those in the 3-way
> handshake draft.  Because of this, my code must translate 
> between the two.
> 
> The MIB has values:
> 
>            Initializing 1
>            Up           2
>            Down         4
> 
> Whereas the 3-way handshake draft has these different values 
> for adjacency
> state:
> 
>            Initializing 1
>            Up           0
>            Down         2
> 
> Any chance the MIB values could be made to be consistent?  I 
> note that in
> the MIB there appears to be a desire to avoid the use of the 
> number "0" as a
> value for an entry, and so in this case giving values such as Up 1,
> Initializing 2, Down 3, would be pretty good since there is 
> an easy function
> to map between the two values.
> 
> Secondly, the fields for Adjacency usage are inconsistent 
> with those values
> that one might use to index into the 10589 state tables for 
> received hellos
> (8.2.4.2).  Looking at table 6, which contains all the 
> indecis, the ideal
> index values for adjusage would be:
> 
> 
>              None:          0
>              L1:            1
>              L1andL2:       2
>              L2-only        3
> 
> The mib has values:
>              Undefined:     1
>              level1         2
>              level2         3
>              level1and2     4
> 
> As before, if 0 is being avoided values such as none: 1 l1: 
> 2, l1andl2 3
> l2-only 4, would be preferable.
> 
> I realize this isn't terribly important, but there is some 
> confusing code
> that maps between the table indices and the MIB values that 
> makes this part
> of the code a little more difficult to read.  No translation 
> would improve
> this bit of code's readability.
> 
> Thanks for your attention,
> 
>   --Neal
> 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 07:29:46 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24249
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 07:29:46 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA15415;
	Tue, 4 Dec 2001 04:48:51 -0800 (PST)
Received: from mailFA2.rediffmail.com ([202.54.124.147])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id EAA15403
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 04:47:08 -0800 (PST)
Received: (qmail 27006 invoked by uid 510); 4 Dec 2001 12:20:11 -0000
Message-ID: <20011204122011.27005.qmail@mailFA2.rediffmail.com>
Received: from unknown (203.197.138.201) by rediffmail.com via HTTP; 04 Dec 2001 12:20:11 -0000
MIME-Version: 1.0
From: "aridaman  kaushik" <kaushik_ari@rediffmail.com>
Reply-To: "aridaman  kaushik" <kaushik_ari@rediffmail.com>
To: isis-wg@spider.juniper.net
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by external.juniper.net id EAA15404
Subject: [Isis-wg] (no subject)
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: 4 Dec 2001 12:20:11 -0000
Content-Transfer-Encoding: 8bit


hi all,
    I hope, anyone would clarify my doubt regarding ipv6 route prefernece in isis.
in draft draft-isis-ipv6-02.txt, route preference is given like this(from best to worst).

1. level1  up
2. level2  up
3. level2  down
4. level1   down

What is meaning of up/down here.
we can assume that level2 down means l2 to l1 leaked route. but what is the meaning of l1 down
thanks in advance
ari
 

 

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 09:12:31 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26048
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 09:12:30 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA15898;
	Tue, 4 Dec 2001 06:31:50 -0800 (PST)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA15885
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 06:30:54 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734290122FEF4@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'aridaman  kaushik'" <kaushik_ari@rediffmail.com>,
        isis-wg@spider.juniper.net
Subject: RE: [Isis-wg] (no subject)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 09:09:15 -0500

> 1. level1  up
> 2. level2  up
> 3. level2  down
> 4. level1   down
> 
> What ... is the meaning of l1 down[?]

Take a look at RFC 2966, 
http://www.ietf.org/rfc/rfc2966.txt

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 12:39:39 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03313
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 12:39:38 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16771;
	Tue, 4 Dec 2001 09:58:51 -0800 (PST)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16759
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:57:27 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4HZAd05449;
	Tue, 4 Dec 2001 12:35:10 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4HZgl03548;
	Tue, 4 Dec 2001 17:35:43 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L44XC>; Tue, 4 Dec 2001 17:34:28 -0000
Message-ID: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'"
	 <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE9.E8F94900"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:34:22 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE9.E8F94900
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE9.E8F94900
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE9.E8F94900--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 13:44:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06171
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 13:44:42 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA17089;
	Tue, 4 Dec 2001 11:03:51 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA17077
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 11:02:12 -0800 (PST)
Received: from alpha-tli.procket.com (IDENT:root@alpha-tli.procket.com [10.2.3.1])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fB4IeUes018700;
	Tue, 4 Dec 2001 10:40:30 -0800 (PST)
Received: (from tli@localhost)
	by alpha-tli.procket.com (8.12.1/8.12.1) id fB4IeUK3005272;
	Tue, 4 Dec 2001 10:40:30 -0800
From: Tony Li <tli@Procket.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15373.6302.577326.223821@alpha-tli.procket.com>
To: "Philip Christian" <christi@nortelnetworks.com>
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'"
	 <rsaluja@nortelnetworks.com>
Subject: [Isis-wg] Concerns with 3-way-handshake
In-Reply-To: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com>
References: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com>
X-Mailer: VM 6.92 under Emacs 20.5.1
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 10:40:30 -0800
Content-Transfer-Encoding: 7bit


 | This draft specifically declares itself to be useful in SONET networks
 | (presumably in the embedded DCC channels, although this is not stated).


Actually, most of the IP routers running IS-IS do so over POS links, and
thus, IS-IS is running in-band.

I agree with your comments.  Other opinions?

Tony

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 14:40:46 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08548
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 14:40:45 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA17367;
	Tue, 4 Dec 2001 11:59:52 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA17355
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 11:58:22 -0800 (PST)
Received: from redback.com (dhcp-35-94.redback.com [155.53.35.94])
	by prattle.redback.com (Postfix) with ESMTP
	id 478A9CAB75; Tue,  4 Dec 2001 11:36:46 -0800 (PST)
Message-ID: <3C0D12CA.2B982FCB@redback.com>
From: Tony Przygienda <prz@redback.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; NetBSD 1.4.1 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Philip Christian <christi@nortelnetworks.com>
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
Subject: Re: [Isis-wg] Concerns with 3-way-handshake
References: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 04 Dec 2001 10:15:38 -0800
Content-Transfer-Encoding: 7bit

Philip Christian wrote:

>
>
> I have a number of concerns and comments about the 3-way-handshake
> draft, draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that
> this draft is about to become an RFC, although I can find no evidence
> of this on the RFC editor's web page.
>
> Here are my concerns.
>
> This draft specifically declares itself to be useful in SONET networks
> (presumably in the embedded DCC channels, although this is not
> stated). However I believe that there is an area of ambiguity in it
> which reduces its usefulness somewhat. The draft mentions only IIH
> packets, where as SONET and SDH networks (oh yes, SDH is not mentioned
> either) are currently based on CLNS and therefore the NEs transmit ISH
> packets too.
>
> I understand that an old CLNS SONET/SDH node will not support
> three-way handshaking anyway, and so a new neighbour would engage
> legacy mode anyway, BUT....
>
> With the advent of G.7712 vendors will be looking at implementing dual
> IP and CLNS routers that are able to still interface to the old CLNS
> nodes, and which also support three way handshaking. Such a new dual
> node may well need to declare itself a CLNS End System, and so will be
> transmitting ISHs. This will be necessary to terminate RFC 3147
> encapsulated packets, for example.
>
> The problem is that I believe that receipt of ISH packets "short
> circuits" the three way handshake, and results in the adjacency coming
> up whether the neighbour has received  IIHs, or not. This is my
> understanding of the problem:
>
> A is connected to B and issues an ISH.
> B receives the ISH, and according to ISO 10589 section 8.2.2 creates
> an adjacency of type "Initialising".
> B now reports to A in the new "Point to point adjacency state" option
> that the adjacency is "Initialising".
> A receives this and according to the table in the draft, brings the
> adjacency "up".
> However B may never have received an IIH from A and so the three way
> handshake has been short circuited, or have I misunderstood something?
>
> The draft really needs to state how a router with three way
> handshaking should handle receipt of an ISH from a neighbouring IS
> that also supports the option.
>
> I guess that this is not a problem for pure IP routers if they ignore
> ISHs, and this could be stated.
>
> Next concern; what happened to ISHs anyway? RFC 1195 states in section
> 4.4 "For point-to-point links, IS-IS requires exchange of ISO 9542
> ISHs, as the first step in establishing the link between routers. All
> IS-IS routers are therefore required to transmit and receive ISO 9542
> ISH packets on point-to-point links.". There is a similar statement in
> section 5.1.
>
> I am told that many implementors do not transmit ISH packets anymore,
> as they cannot terminate CLNP and thus are not an CLNS End System
> anymore.
>
> This seems perfectly logical to me, but, if this is the case then I
> think that this draft should state it. It is the after-all going to be
> (hopefully) the first RFC to actually alter the adjacency creation
> process from ISO 10589; RFC 1195 did not change it. If it is now okay
> not to transmit ISHs then let's say so.

funny enough, I know that multiple vendors shortcut ISHs since a while
and I stated in some conversations that I'm concerned. Since I could not
prove the specific problem that would cause (since IIHs will bring the
adjacency anyway), it was dismissed with a shrug.

From my vintage, yes, it should be fixed, maybe as simply as saying that
three-way-hello capable routers drop ISHs and do not send them ?  The
very details of 1195 slip my mind right now but that should not cause
any backwards capability problems?

    something is definitely worth an addition to the 3-way-hello draft

    -- tony

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 14:46:36 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA08956
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 14:46:34 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17415;
	Tue, 4 Dec 2001 12:05:53 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17391
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 12:03:12 -0800 (PST)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 405FFCAB6E; Tue,  4 Dec 2001 11:41:37 -0800 (PST)
To: Tony Li <tli@procket.com>
Cc: "Philip Christian" <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
Subject: Re: [Isis-wg] Concerns with 3-way-handshake 
In-reply-to: Mail from Tony Li <tli@procket.com> 
 dated Tue, 04 Dec 2001 10:40:30 PST
 <15373.6302.577326.223821@alpha-tli.procket.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011204194137.405FFCAB6E@prattle.redback.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 04 Dec 2001 11:41:37 -0800


this draft reflects many vendors current implementation for the ip
routers, we should let this to go through to become an rfc(informational).
any need for ish probably should submit a seperate one, maybe a big
one to handle all other clns cases where the ip portion has already
advanced.


 ]
 ] | This draft specifically declares itself to be useful in SONET networks
 ] | (presumably in the embedded DCC channels, although this is not stated).
 ]
 ]
 ]Actually, most of the IP routers running IS-IS do so over POS links, and
 ]thus, IS-IS is running in-band.
 ]
 ]I agree with your comments.  Other opinions?
 ]
 ]Tony
 ]
 ]_______________________________________________
 ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ]http://external.juniper.net/mailman/listinfo/isis-wg

- Naiming
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 14:57:49 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09441
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 14:57:48 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17485;
	Tue, 4 Dec 2001 12:17:51 -0800 (PST)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17468
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 12:16:51 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4JsXd02524;
	Tue, 4 Dec 2001 14:54:33 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4Jt6l13822;
	Tue, 4 Dec 2001 19:55:07 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L456S>; Tue, 4 Dec 2001 19:54:01 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071390@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: "'Naiming Shen'" <naiming@redback.com>, Tony Li <tli@procket.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>
Cc: "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "Rajesh Saluja" <rsaluja@nortelnetworks.com>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CFD.6A36A220"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 19:53:59 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CFD.6A36A220
Content-Type: text/plain;
	charset="iso-8859-1"

I absolutely do not agree.
I said that it is acceptable for a pure IP implementation to ignore ISH, and
so these "current vendors implementations" need not have a problem with it.
We can even say this in the RFC, so for the first time ever, it will say in
an RFC "you can ignore ISH". I would have thought that this would be good
news for the implementations that you mention.
However the draft is useless for routers that do need to terminate CLNS
packets, and is therefore useless for sorting out the SONET protection
switching events that it claims to help.
Do we want RFCs that do not acheive what they claim to?
We can sort out one without affecting the other, and therefore should do so.

By the way, the draft has expired, but people can still read it at
http://www.watersprings.org/pub/id/draft-ietf-isis-3way-03.txt

Philip Christian

-----Original Message-----
From: Naiming Shen [mailto:naiming@redback.com]
Sent: 04 December 2001 19:42
To: Tony Li
Cc: Christian, Philip [HAL02:GI50:EXCH]; 'isis-wg@spider.juniper.net';
'dkatz@juniper.net'; Saluja, Rajesh [BL60:432:EXCH]
Subject: Re: [Isis-wg] Concerns with 3-way-handshake



this draft reflects many vendors current implementation for the ip
routers, we should let this to go through to become an rfc(informational).
any need for ish probably should submit a seperate one, maybe a big
one to handle all other clns cases where the ip portion has already
advanced.


 ]
 ] | This draft specifically declares itself to be useful in SONET networks
 ] | (presumably in the embedded DCC channels, although this is not stated).
 ]
 ]
 ]Actually, most of the IP routers running IS-IS do so over POS links, and
 ]thus, IS-IS is running in-band.
 ]
 ]I agree with your comments.  Other opinions?
 ]
 ]Tony
 ]
 ]_______________________________________________
 ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ]http://external.juniper.net/mailman/listinfo/isis-wg

- Naiming

------_=_NextPart_001_01C17CFD.6A36A220
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Isis-wg] Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I absolutely do not agree.</FONT>
<BR><FONT SIZE=3D2>I said that it is acceptable for a pure IP =
implementation to ignore ISH, and so these &quot;current vendors =
implementations&quot; need not have a problem with it.</FONT></P>

<P><FONT SIZE=3D2>We can even say this in the RFC, so for the first =
time ever, it will say in an RFC &quot;you can ignore ISH&quot;. I =
would have thought that this would be good news for the implementations =
that you mention.</FONT></P>

<P><FONT SIZE=3D2>However the draft is useless for routers that do need =
to terminate CLNS packets, and is therefore useless for sorting out the =
SONET protection switching events that it claims to help.</FONT></P>

<P><FONT SIZE=3D2>Do we want RFCs that do not acheive what they claim =
to?</FONT>
<BR><FONT SIZE=3D2>We can sort out one without affecting the other, and =
therefore should do so.</FONT>
</P>

<P><FONT SIZE=3D2>By the way, the draft has expired, but people can =
still read it at</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://www.watersprings.org/pub/id/draft-ietf-isis-3way-03.txt" =
TARGET=3D"_blank">http://www.watersprings.org/pub/id/draft-ietf-isis-3wa=
y-03.txt</A></FONT>
</P>

<P><FONT SIZE=3D2>Philip Christian</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Naiming Shen [<A =
HREF=3D"mailto:naiming@redback.com">mailto:naiming@redback.com</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: 04 December 2001 19:42</FONT>
<BR><FONT SIZE=3D2>To: Tony Li</FONT>
<BR><FONT SIZE=3D2>Cc: Christian, Philip [HAL02:GI50:EXCH]; =
'isis-wg@spider.juniper.net';</FONT>
<BR><FONT SIZE=3D2>'dkatz@juniper.net'; Saluja, Rajesh =
[BL60:432:EXCH]</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [Isis-wg] Concerns with =
3-way-handshake</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>this draft reflects many vendors current =
implementation for the ip</FONT>
<BR><FONT SIZE=3D2>routers, we should let this to go through to become =
an rfc(informational).</FONT>
<BR><FONT SIZE=3D2>any need for ish probably should submit a seperate =
one, maybe a big</FONT>
<BR><FONT SIZE=3D2>one to handle all other clns cases where the ip =
portion has already</FONT>
<BR><FONT SIZE=3D2>advanced.</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;]</FONT>
<BR><FONT SIZE=3D2>&nbsp;] | This draft specifically declares itself to =
be useful in SONET networks</FONT>
<BR><FONT SIZE=3D2>&nbsp;] | (presumably in the embedded DCC channels, =
although this is not stated).</FONT>
<BR><FONT SIZE=3D2>&nbsp;]</FONT>
<BR><FONT SIZE=3D2>&nbsp;]</FONT>
<BR><FONT SIZE=3D2>&nbsp;]Actually, most of the IP routers running =
IS-IS do so over POS links, and</FONT>
<BR><FONT SIZE=3D2>&nbsp;]thus, IS-IS is running in-band.</FONT>
<BR><FONT SIZE=3D2>&nbsp;]</FONT>
<BR><FONT SIZE=3D2>&nbsp;]I agree with your comments.&nbsp; Other =
opinions?</FONT>
<BR><FONT SIZE=3D2>&nbsp;]</FONT>
<BR><FONT SIZE=3D2>&nbsp;]Tony</FONT>
<BR><FONT SIZE=3D2>&nbsp;]</FONT>
<BR><FONT =
SIZE=3D2>&nbsp;]_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&nbsp;]Isis-wg mailing list&nbsp; -&nbsp; =
Isis-wg@external.juniper.net</FONT>
<BR><FONT SIZE=3D2>&nbsp;]<A =
HREF=3D"http://external.juniper.net/mailman/listinfo/isis-wg" =
TARGET=3D"_blank">http://external.juniper.net/mailman/listinfo/isis-wg</=
A></FONT>
</P>

<P><FONT SIZE=3D2>- Naiming</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CFD.6A36A220--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 15:08:20 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10056
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 15:08:19 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17582;
	Tue, 4 Dec 2001 12:27:52 -0800 (PST)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17570
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 12:26:13 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4K3ud03954;
	Tue, 4 Dec 2001 15:03:56 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4K4Tl14185;
	Tue, 4 Dec 2001 20:04:30 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L46CG>; Tue, 4 Dec 2001 20:03:24 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071391@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: "'Tony Li'" <tli@Procket.com>,
        "'isis-wg@spider.juniper.net'"
	 <isis-wg@spider.juniper.net>
Cc: "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CFE.BAA29880"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 20:03:23 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CFE.BAA29880
Content-Type: text/plain;
	charset="iso-8859-1"

The draft is definitely talking about embedded DCC channels when it says

"In addition, SONET links bring a third issue, which is that when SONET
protection is used, a system may receive packets that are actually destined
for a different system (or a different link on the same system).  The
receiving system may end up thinking that it has an adjacency with the
remote system when in fact the remote system is adjacent with a third
system."

This has to be referring to when the embedded DCC channel in a SONET signal
switches with the K bytes from one fibre to another. The problem mentioned
above occurs when the active signal goes through a different regenerator to
the protection fibre. Interestingly SDH acts differently with two
adjacencies maintained and one of them just disappearing.

A protection switch should be invisible to the SONET payload, i.e. a POS
circuit between two routers, and so this is not what it is talking about.

Philip Christian

-----Original Message-----
From: Tony Li [mailto:tli@Procket.com]
Sent: 04 December 2001 18:41
To: Christian, Philip [HAL02:GI50:EXCH]
Cc: 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net';
'rsaluja@nortelnetworks.com'
Subject: [Isis-wg] Concerns with 3-way-handshake



 | This draft specifically declares itself to be useful in SONET networks
 | (presumably in the embedded DCC channels, although this is not stated).


Actually, most of the IP routers running IS-IS do so over POS links, and
thus, IS-IS is running in-band.

I agree with your comments.  Other opinions?

Tony


------_=_NextPart_001_01C17CFE.BAA29880
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Isis-wg] Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>The draft is definitely talking about embedded DCC =
channels when it says</FONT>
</P>

<P><FONT SIZE=3D2>&quot;In addition, SONET links bring a third issue, =
which is that when SONET protection is used, a system may receive =
packets that are actually destined for a different system (or a =
different link on the same system).&nbsp; The receiving system may end =
up thinking that it has an adjacency with the remote system when in =
fact the remote system is adjacent with a third =
system.&quot;</FONT></P>

<P><FONT SIZE=3D2>This has to be referring to when the embedded DCC =
channel in a SONET signal switches with the K bytes from one fibre to =
another. The problem mentioned above occurs when the active signal goes =
through a different regenerator to the protection fibre. Interestingly =
SDH acts differently with two adjacencies maintained and one of them =
just disappearing.</FONT></P>

<P><FONT SIZE=3D2>A protection switch should be invisible to the SONET =
payload, i.e. a POS circuit between two routers, and so this is not =
what it is talking about.</FONT></P>

<P><FONT SIZE=3D2>Philip Christian</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Tony Li [<A =
HREF=3D"mailto:tli@Procket.com">mailto:tli@Procket.com</A>]</FONT>
<BR><FONT SIZE=3D2>Sent: 04 December 2001 18:41</FONT>
<BR><FONT SIZE=3D2>To: Christian, Philip [HAL02:GI50:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: 'isis-wg@spider.juniper.net'; =
'dkatz@juniper.net';</FONT>
<BR><FONT SIZE=3D2>'rsaluja@nortelnetworks.com'</FONT>
<BR><FONT SIZE=3D2>Subject: [Isis-wg] Concerns with =
3-way-handshake</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=3D2>&nbsp;| This draft specifically declares itself to be =
useful in SONET networks</FONT>
<BR><FONT SIZE=3D2>&nbsp;| (presumably in the embedded DCC channels, =
although this is not stated).</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Actually, most of the IP routers running IS-IS do so =
over POS links, and</FONT>
<BR><FONT SIZE=3D2>thus, IS-IS is running in-band.</FONT>
</P>

<P><FONT SIZE=3D2>I agree with your comments.&nbsp; Other =
opinions?</FONT>
</P>

<P><FONT SIZE=3D2>Tony</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CFE.BAA29880--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 15:29:48 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10983
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 15:29:45 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17733;
	Tue, 4 Dec 2001 12:49:52 -0800 (PST)
Received: from ams-msg-core-1.cisco.com (ams-msg-core-1.cisco.com [144.254.74.60])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17717
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 12:47:20 -0800 (PST)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fB4KPeB10587;
	Tue, 4 Dec 2001 21:25:40 +0100 (MET)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGQ38589;
	Tue, 4 Dec 2001 15:24:23 -0500 (EST)
Message-Id: <4.3.2.7.2.20011204143729.00ba2418@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Tony Li <tli@procket.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] Concerns with 3-way-handshake
Cc: "Philip Christian" <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
In-Reply-To: <15373.6302.577326.223821@alpha-tli.procket.com>
References: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com>
 <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 04 Dec 2001 15:24:00 -0500

At 01:40 PM 12/4/2001, Tony Li wrote:

> | This draft specifically declares itself to be useful in SONET networks
> | (presumably in the embedded DCC channels, although this is not stated).
>
>
>Actually, most of the IP routers running IS-IS do so over POS links, and
>thus, IS-IS is running in-band.

In addition, the draft addresses running IS-IS over an unreliable
point-to-point link level protocol, whereas 10598 states that a
reliable link is required.  I believe the draft states this to
be the case (at least, the author promised me it would!)

I agree with the recommendation.  While the three-way handshake
is superfluous on a reliable link, it should be permitted.  If I
remember correctly, it could be used for a related purpose -- 
a larger circuit ID or something.

Regards,
Jeff


>I agree with your comments.  Other opinions?
>
>Tony
>
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 15:36:19 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11208
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 15:36:09 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17790;
	Tue, 4 Dec 2001 12:55:52 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17765
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 12:54:37 -0800 (PST)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 0AE58CAB70; Tue,  4 Dec 2001 12:33:01 -0800 (PST)
To: "Philip Christian" <christi@nortelnetworks.com>
Cc: Tony Li <tli@procket.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "Rajesh Saluja" <rsaluja@nortelnetworks.com>
Subject: Re: [Isis-wg] Concerns with 3-way-handshake 
In-reply-to: Mail from "Philip Christian" <christi@nortelnetworks.com> 
 dated Tue, 04 Dec 2001 19:53:59 GMT
 <4103264BC8D3D51180B7002048400C45071390@zhard0jd.europe.nortel.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011204203301.0AE58CAB70@prattle.redback.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 04 Dec 2001 12:33:00 -0800


I don't think the draft claims to work during the sonet switch level,
the sonet switching portion this draft talking about has nothing to
do with ISIS. this draft only claims to solve the problem after the
sonet switching happened(with some lower layer signalling), how to
make sure from layer 3 this link has changed circuit from ISIS point
of view.

 ]
 ]I absolutely do not agree.
 ]I said that it is acceptable for a pure IP implementation to ignore ISH, and
 ]so these "current vendors implementations" need not have a problem with it.
 ]We can even say this in the RFC, so for the first time ever, it will say in
 ]an RFC "you can ignore ISH". I would have thought that this would be good
 ]news for the implementations that you mention.
 ]However the draft is useless for routers that do need to terminate CLNS
 ]packets, and is therefore useless for sorting out the SONET protection
 ]switching events that it claims to help.
 ]Do we want RFCs that do not acheive what they claim to?
 ]We can sort out one without affecting the other, and therefore should do so.
 ]
 ]By the way, the draft has expired, but people can still read it at
 ]http://www.watersprings.org/pub/id/draft-ietf-isis-3way-03.txt
 ]
 ]Philip Christian
 ]
 ]-----Original Message-----
 ]From: Naiming Shen [mailto:naiming@redback.com]
 ]Sent: 04 December 2001 19:42
 ]To: Tony Li
 ]Cc: Christian, Philip [HAL02:GI50:EXCH]; 'isis-wg@spider.juniper.net';
 ]'dkatz@juniper.net'; Saluja, Rajesh [BL60:432:EXCH]
 ]Subject: Re: [Isis-wg] Concerns with 3-way-handshake
 ]
 ]
 ]
 ]this draft reflects many vendors current implementation for the ip
 ]routers, we should let this to go through to become an rfc(informational).
 ]any need for ish probably should submit a seperate one, maybe a big
 ]one to handle all other clns cases where the ip portion has already
 ]advanced.
 ]
 ]
 ] ]
 ] ] | This draft specifically declares itself to be useful in SONET networks
 ] ] | (presumably in the embedded DCC channels, although this is not stated).
 ] ]
 ] ]
 ] ]Actually, most of the IP routers running IS-IS do so over POS links, and
 ] ]thus, IS-IS is running in-band.
 ] ]
 ] ]I agree with your comments.  Other opinions?
 ] ]
 ] ]Tony
 ] ]
 ] ]_______________________________________________
 ] ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ] ]http://external.juniper.net/mailman/listinfo/isis-wg
 ]
 ]- Naiming
 ]

- Naiming
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 15:41:02 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11556
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 15:41:01 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA17835;
	Tue, 4 Dec 2001 13:01:02 -0800 (PST)
Received: from ams-msg-core-1.cisco.com (ams-msg-core-1.cisco.com [144.254.74.60])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17770
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 12:54:44 -0800 (PST)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fB4KX3I12865;
	Tue, 4 Dec 2001 21:33:03 +0100 (MET)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGQ38821;
	Tue, 4 Dec 2001 15:31:45 -0500 (EST)
Message-Id: <4.3.2.7.2.20011204152711.05186e50@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Philip Christian" <christi@nortelnetworks.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
Cc: "'Tony Li'" <tli@procket.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
In-Reply-To: <4103264BC8D3D51180B7002048400C45071391@zhard0jd.europe.nor
 tel.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_104596201==_.ALT"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 04 Dec 2001 15:31:42 -0500

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

At 03:03 PM 12/4/2001, Philip Christian wrote:

>The draft is definitely talking about embedded DCC channels when it says 
>
>"In addition, SONET links bring a third issue, which is that when SONET protection is used, a system may receive packets that are actually destined for a different system (or a different link on the same system).  The receiving system may end up thinking that it has an adjacency with the remote system when in fact the remote system is adjacent with a third system."
>
>This has to be referring to when the embedded DCC channel in a SONET signal switches with the K bytes from one fibre to another. The problem mentioned above occurs when the active signal goes through a different regenerator to the protection fibre. Interestingly SDH acts differently with two adjacencies maintained and one of them just disappearing.

This would cause the LAPD link to fail with high probability, so I
doubt it's what is being referred to in the draft.

>A protection switch should be invisible to the SONET payload, i.e. a POS circuit between two routers, and so this is not what it is talking about.

For channelized SONET, reprovisioning could cause the VT to be terminated
at a different remote system.  Since the link layer protocol is unreliable
and does not detect the fact that it is now connected to a different system,
the 3-way handshake is required.

Jeff


>Philip Christian 
>
>-----Original Message----- 
>From: Tony Li [<mailto:tli@Procket.com>mailto:tli@Procket.com] 
>Sent: 04 December 2001 18:41 
>To: Christian, Philip [HAL02:GI50:EXCH] 
>Cc: 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net'; 
>'rsaluja@nortelnetworks.com' 
>Subject: [Isis-wg] Concerns with 3-way-handshake 
>
>
> | This draft specifically declares itself to be useful in SONET networks 
> | (presumably in the embedded DCC channels, although this is not stated). 
>
>Actually, most of the IP routers running IS-IS do so over POS links, and 
>thus, IS-IS is running in-band. 
>
>I agree with your comments.  Other opinions? 
>
>Tony 

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

<html>
At 03:03 PM 12/4/2001, Philip Christian wrote:<br>
<br>
<blockquote type=cite cite><font size=2>The draft is definitely talking
about embedded DCC channels when it says</font> <br>
<br>
<font size=2>&quot;In addition, SONET links bring a third issue, which is
that when SONET protection is used, a system may receive packets that are
actually destined for a different system (or a different link on the same
system).&nbsp; The receiving system may end up thinking that it has an
adjacency with the remote system when in fact the remote system is
adjacent with a third system.&quot;<br>
</font><br>
<font size=2>This has to be referring to when the embedded DCC channel in
a SONET signal switches with the K bytes from one fibre to another. The
problem mentioned above occurs when the active signal goes through a
different regenerator to the protection fibre. Interestingly SDH acts
differently with two adjacencies maintained and one of them just
disappearing.</font></blockquote><br>
This would cause the LAPD link to fail with high probability, so I<br>
doubt it's what is being referred to in the draft.<br>
<br>
<blockquote type=cite cite><font size=2>A protection switch should be
invisible to the SONET payload, i.e. a POS circuit between two routers,
and so this is not what it is talking about.</font></blockquote><br>
For channelized SONET, reprovisioning could cause the VT to be
terminated<br>
at a different remote system.&nbsp; Since the link layer protocol is
unreliable<br>
and does not detect the fact that it is now connected to a different
system,<br>
the 3-way handshake is required.<br>
<br>
Jeff<br>
<br>
<br>
<blockquote type=cite cite><font size=2>Philip Christian</font> <br>
<br>
<font size=2>-----Original Message-----</font> <br>
<font size=2>From: Tony Li
[<a href="mailto:tli@Procket.com">mailto:tli@Procket.com</a>]</font>
<br>
<font size=2>Sent: 04 December 2001 18:41</font> <br>
<font size=2>To: Christian, Philip [HAL02:GI50:EXCH]</font> <br>
<font size=2>Cc: 'isis-wg@spider.juniper.net';
'dkatz@juniper.net';</font> <br>
<font size=2>'rsaluja@nortelnetworks.com'</font> <br>
<font size=2>Subject: [Isis-wg] Concerns with 3-way-handshake</font>
<br>
<br>
<br>
<font size=2>&nbsp;| This draft specifically declares itself to be useful in SONET networks</font> <br>
<font size=2>&nbsp;| (presumably in the embedded DCC channels, although this is not stated).</font> <br>
<br>
<font size=2>Actually, most of the IP routers running IS-IS do so over POS links, and</font> <br>
<font size=2>thus, IS-IS is running in-band.</font> <br>
<br>
<font size=2>I agree with your comments.&nbsp; Other opinions?</font> <br>
<br>
<font size=2>Tony</font> </blockquote></html>

--=====================_104596201==_.ALT--

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 15:47:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11815
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 15:47:41 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA17892;
	Tue, 4 Dec 2001 13:06:55 -0800 (PST)
Received: from ams-msg-core-1.cisco.com (ams-msg-core-1.cisco.com [144.254.74.60])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA17805
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 12:58:47 -0800 (PST)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by ams-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fB4Kb4H15374;
	Tue, 4 Dec 2001 21:37:04 +0100 (MET)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGQ39001;
	Tue, 4 Dec 2001 15:36:51 -0500 (EST)
Message-Id: <4.3.2.7.2.20011204153429.01cbbe40@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Philip Christian" <christi@nortelnetworks.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
Cc: "'Naiming Shen'" <naiming@redback.com>, Tony Li <tli@procket.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "Rajesh Saluja" <rsaluja@nortelnetworks.com>
In-Reply-To: <4103264BC8D3D51180B7002048400C45071390@zhard0jd.europe.nor
 tel.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_104902642==_.ALT"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 04 Dec 2001 15:36:47 -0500

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


Implementations are required to send ISHs by RFC 1195 and ISO 10589.
Therefore, wouldn't it be wise for the draft to accommodate this
requirement?  (Regardless of the fact that many (most?) implementations
don't do it.)

Jeff


At 02:53 PM 12/4/2001, Philip Christian wrote:

>I absolutely do not agree. 
>I said that it is acceptable for a pure IP implementation to ignore ISH, and so these "current vendors implementations" need not have a problem with it.
>
>We can even say this in the RFC, so for the first time ever, it will say in an RFC "you can ignore ISH". I would have thought that this would be good news for the implementations that you mention.
>
>However the draft is useless for routers that do need to terminate CLNS packets, and is therefore useless for sorting out the SONET protection switching events that it claims to help.
>
>Do we want RFCs that do not acheive what they claim to? 
>We can sort out one without affecting the other, and therefore should do so. 
>
>By the way, the draft has expired, but people can still read it at 
><http://www.watersprings.org/pub/id/draft-ietf-isis-3way-03.txt>http://www.watersprings.org/pub/id/draft-ietf-isis-3way-03.txt 
>
>Philip Christian 
>
>-----Original Message----- 
>From: Naiming Shen [<mailto:naiming@redback.com>mailto:naiming@redback.com] 
>Sent: 04 December 2001 19:42 
>To: Tony Li 
>Cc: Christian, Philip [HAL02:GI50:EXCH]; 'isis-wg@spider.juniper.net'; 
>'dkatz@juniper.net'; Saluja, Rajesh [BL60:432:EXCH] 
>Subject: Re: [Isis-wg] Concerns with 3-way-handshake 
>
>
>this draft reflects many vendors current implementation for the ip 
>routers, we should let this to go through to become an rfc(informational). 
>any need for ish probably should submit a seperate one, maybe a big 
>one to handle all other clns cases where the ip portion has already 
>advanced. 
>
> ] 
> ] | This draft specifically declares itself to be useful in SONET networks 
> ] | (presumably in the embedded DCC channels, although this is not stated). 
> ] 
> ] 
> ]Actually, most of the IP routers running IS-IS do so over POS links, and 
> ]thus, IS-IS is running in-band. 
> ] 
> ]I agree with your comments.  Other opinions? 
> ] 
> ]Tony 
> ] 
> ]_______________________________________________ 
> ]Isis-wg mailing list  -  Isis-wg@external.juniper.net 
> ]<http://external.juniper.net/mailman/listinfo/isis-wg>http://external.juniper.net/mailman/listinfo/isis-wg 
>
>- Naiming 

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

<html>
<br>
Implementations are required to send ISHs by RFC 1195 and ISO 
10589.<br>
Therefore, wouldn't it be wise for the draft to accommodate this<br>
requirement?&nbsp; (Regardless of the fact that many (most?)
implementations<br>
don't do it.)<br>
<br>
Jeff<br>
<br>
<br>
At 02:53 PM 12/4/2001, Philip Christian wrote:<br>
<br>
<blockquote type=cite cite><font size=2>I absolutely do not agree.</font>
<br>
<font size=2>I said that it is acceptable for a pure IP implementation to ignore ISH, and so these &quot;current vendors implementations&quot; need not have a problem with it.<br>
</font><br>
<font size=2>We can even say this in the RFC, so for the first time ever, it will say in an RFC &quot;you can ignore ISH&quot;. I would have thought that this would be good news for the implementations that you mention.<br>
</font><br>
<font size=2>However the draft is useless for routers that do need to terminate CLNS packets, and is therefore useless for sorting out the SONET protection switching events that it claims to help.<br>
</font><br>
<font size=2>Do we want RFCs that do not acheive what they claim to?</font> <br>
<font size=2>We can sort out one without affecting the other, and therefore should do so.</font> <br>
<br>
<font size=2>By the way, the draft has expired, but people can still read it at</font> <br>
<font size=2><a href="http://www.watersprings.org/pub/id/draft-ietf-isis-3way-03.txt">http://www.watersprings.org/pub/id/draft-ietf-isis-3way-03.txt</a></font> <br>
<br>
<font size=2>Philip Christian</font> <br>
<br>
<font size=2>-----Original Message-----</font> <br>
<font size=2>From: Naiming Shen [<a href="mailto:naiming@redback.com">mailto:naiming@redback.com</a>]</font> <br>
<font size=2>Sent: 04 December 2001 19:42</font> <br>
<font size=2>To: Tony Li</font> <br>
<font size=2>Cc: Christian, Philip [HAL02:GI50:EXCH]; 'isis-wg@spider.juniper.net';</font> <br>
<font size=2>'dkatz@juniper.net'; Saluja, Rajesh [BL60:432:EXCH]</font> <br>
<font size=2>Subject: Re: [Isis-wg] Concerns with 3-way-handshake</font> <br>
<br>
<br>
<font size=2>this draft reflects many vendors current implementation for the ip</font> <br>
<font size=2>routers, we should let this to go through to become an rfc(informational).</font> <br>
<font size=2>any need for ish probably should submit a seperate one, maybe a big</font> <br>
<font size=2>one to handle all other clns cases where the ip portion has already</font> <br>
<font size=2>advanced.</font> <br>
<br>
<font size=2>&nbsp;]</font> <br>
<font size=2>&nbsp;] | This draft specifically declares itself to be useful in SONET networks</font> <br>
<font size=2>&nbsp;] | (presumably in the embedded DCC channels, although this is not stated).</font> <br>
<font size=2>&nbsp;]</font> <br>
<font size=2>&nbsp;]</font> <br>
<font size=2>&nbsp;]Actually, most of the IP routers running IS-IS do so over POS links, and</font> <br>
<font size=2>&nbsp;]thus, IS-IS is running in-band.</font> <br>
<font size=2>&nbsp;]</font> <br>
<font size=2>&nbsp;]I agree with your comments.&nbsp; Other opinions?</font> <br>
<font size=2>&nbsp;]</font> <br>
<font size=2>&nbsp;]Tony</font> <br>
<font size=2>&nbsp;]</font> <br>
<font size=2>&nbsp;]_______________________________________________</font> <br>
<font size=2>&nbsp;]Isis-wg mailing list&nbsp; -&nbsp; Isis-wg@external.juniper.net</font> <br>
<font size=2>&nbsp;]<a href="http://external.juniper.net/mailman/listinfo/isis-wg">http://external.juniper.net/mailman/listinfo/isis-wg</a></font> <br>
<br>
<font size=2>- Naiming</font> </blockquote></html>

--=====================_104902642==_.ALT--

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 16:04:23 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12398
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 16:04:23 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA18065;
	Tue, 4 Dec 2001 13:23:54 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA18033
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 13:22:31 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id NAA10472;
	Tue, 4 Dec 2001 13:00:48 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <Y2HL84T4>; Tue, 4 Dec 2001 13:00:48 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F625@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Philip Christian'" <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'"
	 <rsaluja@nortelnetworks.com>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17D06.BF367EE0"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 13:00:47 -0800

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17D06.BF367EE0
Content-Type: text/plain;
	charset="iso-8859-1"

The problem has nothing to do with ISHs, but rather with the clarity of the
presentation of the draft and some legacy issues from older versions of the
3 way handshake.
 
Philip states:
>A is connected to B and issues an ISH. 
>B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising". 
>B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising". 
>A receives this and according to the table in the draft, brings the
adjacency "up". 
>However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have >I misunderstood something?
 
The draft states:
    "If the option is present, the Neighbor System ID and Neighbor
     Extended Local Circuit ID fields, if present, shall be examined.
     If they are present, and the system ID contained therein does not
     match the local system's ID, or the extended circuit ID does not
     match the local system's extended circuit ID, the PDU shall be
     discarded and no further action is taken.

     If the Neighbor System ID and Neighbor Extended Local Circuit ID
     fields match those of the local system, or are not present, the
     procedures described in section 8.2.4.2 are followed ..."

A router which supports the latest version of the draft could either omit
sending the neighbor's system ID/extended local circuit ID  in the 3 way TLV
when it doesn't know  what they are or send them as all 0's (hopefully no
one allows a system ID to be set to all 0's ???) . If the sending system
sends all 0's the above rule works. But if the sending system is allowed to
omit the neighbor system ID/circuit ID, then for proper operation the rules
above have to be modified to indicate that if either the neighbor system ID
or neighbor circuit id fields are not present then no adjacency state change
should take place.

This modification is not quite enough, however, because an older version of
the 3 way handshake specified a TLV which only included the local adjacency
state. Therefore, a robust implementation has to recognize that the presence
of the 3way TLV with only the local adjacency state in a received IIH
indicates a system which will never echo the neighbor system-id/circuit id
and so it cannot look for a match in these non-existent fields and must
resort to the revised state table solely based on the local/remote adjacency
state. This legacy usage of the option can encounter the problem outlined by
Philip, which results in behavior no different than that which occurs in the
absence of the 3 way TLV.

Reception of an ISH indicates that the neighbor is NOT an OSI End System and
therefore that it is useful to send IIHs on this link. In an IP world, this
requirement is less useful and some implementations, whether intentionally
or not, have omitted sending ISHs. In the strictest sense this is a
violation of ISO 10589, but is workable and in the spirit of "being generous
in what you receive" some implementations allow this, which requires that
the receiver start sending IIH PDUs on receipt of an IIH PDU ( as well as on
a receipt of an ISH).

It probably would be better if the draft was updated to discuss the proper
behavior when dealing with legacy 3 way implementations and what is the
expected behavior when neighbor system ID/extended circuit ID are omitted.

In any event, don't blame ISHs.

  Les

 

 

 -----Original Message-----
From: Philip Christian [mailto:christi@nortelnetworks.com]
Sent: Tuesday, December 04, 2001 9:34 AM
To: 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net';
'rsaluja@nortelnetworks.com'
Subject: [Isis-wg] Concerns with 3-way-handshake



I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns. 

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:

A is connected to B and issues an ISH. 
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising". 
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising". 
A receives this and according to the table in the draft, brings the
adjacency "up". 
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated. 

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian. 


------_=_NextPart_001_01C17D06.BF367EE0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Concerns with 3-way-handshake</TITLE>

<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=383521320-04122001>The 
problem has nothing to do with ISHs, but rather with the clarity of the 
presentation of the draft and some legacy issues from older versions of the 3 
way handshake.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=383521320-04122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=383521320-04122001>Philip 
states:</SPAN></FONT><SPAN class=383521320-04122001><FONT color=#0000ff 
face=Arial size=2></FONT></SPAN></DIV>
<DIV><SPAN class=383521320-04122001><FONT color=#0000ff face=Arial size=2>&gt;A 
is connected to B and issues an ISH.&nbsp;<BR><SPAN 
class=383521320-04122001></SPAN>&gt;B receives the ISH, and according to ISO 
10589 section 8.2.2 creates an adjacency of type "Initialising".&nbsp;<BR><SPAN 
class=383521320-04122001></SPAN>&gt;B now reports to A in the new "Point to 
point adjacency state" option that the adjacency is 
"Initialising".&nbsp;<BR><SPAN class=383521320-04122001></SPAN>&gt;A receives 
this and according to the table in the draft, brings the adjacency 
"up".&nbsp;<BR><SPAN class=383521320-04122001></SPAN>&gt;However B may never 
have received an IIH from A and so the three way handshake has been short 
circuited, or have <SPAN class=383521320-04122001>&gt;</SPAN><SPAN 
class=383521320-04122001>I </SPAN>misunderstood something?</FONT></SPAN></DIV>
<DIV><SPAN class=383521320-04122001></SPAN>&nbsp;</DIV>
<DIV><SPAN class=383521320-04122001><FONT color=#0000ff face=Arial size=2>The 
draft states:</FONT></DIV>
<DIV><FONT face=Arial><FONT color=#0000ff><FONT size=2>
<P><SPAN class=383521320-04122001>&nbsp;&nbsp;&nbsp; "If the option is present, 
the Neighbor System ID and Neighbor<BR>&nbsp;&nbsp;&nbsp;&nbsp; Extended Local 
Circuit ID fields, if present, shall be examined.<BR>&nbsp;&nbsp;&nbsp;&nbsp; If 
they are present, and the system ID contained therein does 
not<BR>&nbsp;&nbsp;&nbsp;&nbsp; match the local system's ID, or the extended 
circuit ID does not<BR>&nbsp;&nbsp;&nbsp;&nbsp; match the local system's 
extended circuit ID, the PDU shall be<BR>&nbsp;&nbsp;&nbsp;&nbsp; discarded and 
no further action is taken.</SPAN></P>
<P><SPAN class=383521320-04122001>&nbsp;&nbsp;&nbsp;&nbsp; If the Neighbor 
System ID and Neighbor Extended Local Circuit ID<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
fields match those of the local system, or are not present, 
the<BR>&nbsp;&nbsp;&nbsp;&nbsp; procedures described in section 8.2.4.2 are 
followed&nbsp;..."</SPAN></P>
<P><SPAN class=383521320-04122001>A router which supports the latest version of 
the draft could either omit sending the neighbor's system ID/extended local 
circuit ID&nbsp; in the 3 way TLV when it doesn't know&nbsp; what they are or 
send them as all 0's (hopefully no one allows a system ID to be set to all 0's 
???)&nbsp;. If the sending system sends all 0's the above rule works. But 
if&nbsp;the sending system is allowed to omit the neighbor system ID/circuit ID, 
then for proper operation the rules above have to be modified to indicate that 
if either the neighbor system ID or neighbor circuit&nbsp;id fields are not 
present then no adjacency state change should take place.</SPAN></P>
<P><SPAN class=383521320-04122001>This modification is not quite enough, 
however, because an older version of the 3 way handshake specified a TLV which 
only included the local adjacency state. Therefore,  a robust implementation has 
to recognize that the presence of the 3way TLV with only the local adjacency 
state in a received IIH indicates a system which will never echo the neighbor 
system-id/circuit id and so it cannot look for a match in these non-existent 
fields and must resort to the revised state table solely based on the 
local/remote adjacency state. This legacy usage of the option can encounter the 
problem outlined by Philip, which results in behavior no&nbsp;different than 
that which occurs in the absence of the 3 way TLV.</SPAN></P>
<P><SPAN class=383521320-04122001>Reception of an ISH indicates that the 
neighbor is NOT an OSI End System and therefore that it is useful to send IIHs 
on this link. In an IP world, this requirement is less useful and some 
implementations, whether intentionally or not, have omitted sending ISHs. In the 
strictest sense this is a violation of ISO 10589, but is workable and in the 
spirit of "being generous in what you receive" some implementations allow this, 
which requires that the receiver start sending IIH PDUs on receipt of an IIH PDU 
( as well as on a receipt of an ISH).</SPAN></P>
<P><SPAN class=383521320-04122001>It probably would be better if the draft was 
updated to discuss the proper behavior when dealing with legacy 3 way 
implementations and what is the expected behavior when neighbor system 
ID/extended circuit ID are omitted.</SPAN></P>
<P><SPAN class=383521320-04122001>In any event, don't blame ISHs.</SPAN></P>
<P><SPAN class=383521320-04122001>&nbsp; Les</SPAN></P>
<P><SPAN class=383521320-04122001></SPAN>&nbsp;</P>
<P><SPAN class=383521320-04122001></SPAN>&nbsp;</P>
<P><SPAN class=383521320-04122001></SPAN><SPAN 
class=383521320-04122001>&nbsp;</SPAN></SPAN></FONT></FONT></FONT><FONT 
face=Tahoma><FONT size=2>-----Original Message-----<BR><B>From:</B> Philip 
Christian [mailto:christi@nortelnetworks.com]<BR><B>Sent:</B> Tuesday, December 
04, 2001 9:34 AM<BR><B>To:</B> 'isis-wg@spider.juniper.net'; 
'dkatz@juniper.net'; 'rsaluja@nortelnetworks.com'<BR><B>Subject:</B> [Isis-wg] 
Concerns with 3-way-handshake<BR><BR></P></FONT></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"></FONT>
  <P><FONT size=2>I have a number of concerns and comments about the 
  3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember 
  hearing that this draft is about to become an RFC, although I can find no 
  evidence of this on the RFC editor's web page.</FONT></P>
  <P><FONT size=2>Here are my concerns.</FONT> </P>
  <P><FONT size=2>This draft specifically declares itself to be useful in SONET 
  networks (presumably in the embedded DCC channels, although this is not 
  stated). However I believe that there is an area of ambiguity in it which 
  reduces its usefulness somewhat. The draft mentions only IIH packets, where as 
  SONET and SDH networks (oh yes, SDH is not mentioned either) are currently 
  based on CLNS and therefore the NEs transmit ISH packets too.</FONT></P>
  <P><FONT size=2>I understand that an old CLNS SONET/SDH node will not support 
  three-way handshaking anyway, and so a new neighbour would engage legacy mode 
  anyway, BUT....</FONT></P>
  <P><FONT size=2>With the advent of G.7712 vendors will be looking at 
  implementing dual IP and CLNS routers that are able to still interface to the 
  old CLNS nodes, and which also support three way handshaking. Such a new dual 
  node may well need to declare itself a CLNS End System, and so will be 
  transmitting ISHs. This will be necessary to terminate RFC 3147 encapsulated 
  packets, for example.</FONT></P>
  <P><FONT size=2>The problem is that I believe that receipt of ISH packets 
  "short circuits" the three way handshake, and results in the adjacency coming 
  up whether the neighbour has received&nbsp; IIHs, or not. This is my 
  understanding of the problem:</FONT></P>
  <P><FONT size=2>A is connected to B and issues an ISH.</FONT> <BR><FONT 
  size=2>B receives the ISH, and according to ISO 10589 section 8.2.2 creates an 
  adjacency of type "Initialising".</FONT> <BR><FONT size=2>B now reports to A 
  in the new "Point to point adjacency state" option that the adjacency is 
  "Initialising".</FONT> <BR><FONT size=2>A receives this and according to the 
  table in the draft, brings the adjacency "up".</FONT> <BR><FONT size=2>However 
  B may never have received an IIH from A and so the three way handshake has 
  been short circuited, or have I misunderstood something?</FONT></P>
  <P><FONT size=2>The draft really needs to state how a router with three way 
  handshaking should handle receipt of an ISH from a neighbouring IS that also 
  supports the option.</FONT></P>
  <P><FONT size=2>I guess that this is not a problem for pure IP routers if they 
  ignore ISHs, and this could be stated.</FONT> </P>
  <P><FONT size=2>Next concern; what happened to ISHs anyway? RFC 1195 states in 
  section 4.4 "For point-to-point links, IS-IS requires exchange of ISO 9542 
  ISHs, as the first step in establishing the link between routers. All IS-IS 
  routers are therefore required to transmit and receive ISO 9542 ISH packets on 
  point-to-point links.". There is a similar statement in section 
5.1.</FONT></P>
  <P><FONT size=2>I am told that many implementors do not transmit ISH packets 
  anymore, as they cannot terminate CLNP and thus are not an CLNS End System 
  anymore.</FONT></P>
  <P><FONT size=2>This seems perfectly logical to me, but, if this is the case 
  then I think that this draft should state it. It is the after-all going to be 
  (hopefully) the first RFC to actually alter the adjacency creation process 
  from ISO 10589; RFC 1195 did not change it. If it is now okay not to transmit 
  ISHs then let's say so.</FONT></P>
  <P><FONT size=2>I think that this issues could be addressed just in a few 
  sentences, once we have agreed how to handle ISHs on nodes that need to. I am 
  ready to help with some drafting in order to help get this right.</FONT></P>
  <P><FONT size=2>Regards, Philip Christian.</FONT> 
</P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C17D06.BF367EE0--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 16:20:13 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12785
	for <isis-archive@odin.ietf.org>; Tue, 4 Dec 2001 16:20:12 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA18194;
	Tue, 4 Dec 2001 13:39:54 -0800 (PST)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA18176
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 13:38:42 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4LGOd15586;
	Tue, 4 Dec 2001 16:16:24 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4LGvl15874;
	Tue, 4 Dec 2001 21:16:57 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L47J1>; Tue, 4 Dec 2001 21:15:49 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071392@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: "'Jeff Learman'" <jlearman@cisco.com>
Cc: "'Tony Li'" <tli@procket.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "Rajesh Saluja" <rsaluja@nortelnetworks.com>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17D08.D7B183F0"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 21:15:47 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17D08.D7B183F0
Content-Type: text/plain;
	charset="iso-8859-1"

okay, I can see that. But why does it talk about "SONET protection" rather
than reprovisioning ?
 
Philip Christian

 
 For channelized SONET, reprovisioning could cause the VT to be terminated
at a different remote system.  Since the link layer protocol is unreliable
and does not detect the fact that it is now connected to a different system,
the 3-way handshake is required.

Jeff
 



------_=_NextPart_001_01C17D08.D7B183F0
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=340471321-04122001>okay, 
I can see that. But why does it talk about "SONET protection" rather than 
reprovisioning ?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=340471321-04122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=340471321-04122001>Philip 
Christian</SPAN></FONT></DIV>
<BLOCKQUOTE style="MARGIN-RIGHT: 0px">
  <DIV><SPAN class=340471321-04122001></SPAN>&nbsp;</DIV>
  <DIV><SPAN class=340471321-04122001>&nbsp;</SPAN>For channelized SONET, 
  reprovisioning could cause the VT to be terminated<BR>at a different remote 
  system.&nbsp; Since the link layer protocol is unreliable<BR>and does not 
  detect the fact that it is now connected to a different system,<BR>the 3-way 
  handshake is required.<BR><BR>Jeff<BR><FONT size=2><FONT color=#0000ff><FONT 
  face=Arial><SPAN 
  class=340471321-04122001>&nbsp;</SPAN><BR></DIV></FONT></FONT></FONT></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C17D08.D7B183F0--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 21:01:04 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21506
	for <isis-archive@lists.ietf.org>; Tue, 4 Dec 2001 21:01:03 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA19463;
	Tue, 4 Dec 2001 18:19:53 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA19450
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 18:18:06 -0800 (PST)
Received: from redback.com (dhcp-35-94.redback.com [155.53.35.94])
	by prattle.redback.com (Postfix) with ESMTP
	id F0B374BA213; Tue,  4 Dec 2001 17:56:28 -0800 (PST)
Message-ID: <3C0D6BC7.B54EBFDF@redback.com>
From: Tony Przygienda <prz@redback.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; NetBSD 1.4.1 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: Rajesh Saluja <rsaluja@nortelnetworks.com>
Cc: Philip Christian <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: Re: [Isis-wg] Concerns with 3-way-handshake
References: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com> <3C0D12CA.2B982FCB@redback.com> <3C0D6B51.7EBB951D@nortelnetworks.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 04 Dec 2001 16:35:19 -0800
Content-Transfer-Encoding: 7bit

Rajesh Saluja wrote:

> >
> >
> > >From my vintage, yes, it should be fixed, maybe as simply as saying that
> > three-way-hello capable routers drop ISHs and do not send them ?  The
> > very details of 1195 slip my mind right now but that should not cause
> > any backwards capability problems?
> >
> >     something is definitely worth an addition to the 3-way-hello draft
> >
> >     -- tony
>
> I agree with Philip's concerns. Will the following modifications be
> acceptable to the group:
> 1. As Tony suggested, say that  three-way-hello capable routers drop ISHs
> and do not send them.

you better be very carefull with the MUST and MAYs when writing this. As well,
someone thinks carefully whether it won't break more than it fixes (although
deployment with dropped ISHs seems to prove that it works and since we will
 be able to chhose whether we send/receive them, we can force pretty much
this situation with the draft).

    thanks

    -- tonyt

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec  4 23:42:30 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA26471
	for <isis-archive@lists.ietf.org>; Tue, 4 Dec 2001 23:42:28 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id VAA20113;
	Tue, 4 Dec 2001 21:01:53 -0800 (PST)
Received: from mailweb12.rediffmail.com ([203.199.83.24])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id VAA20101
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 21:00:50 -0800 (PST)
Received: (qmail 2678 invoked by uid 510); 5 Dec 2001 04:38:28 -0000
Message-ID: <20011205043828.2677.qmail@mailweb12.rediffmail.com>
Received: from unknown (203.197.138.201) by rediffmail.com via HTTP; 05 Dec 2001 04:38:28 -0000
MIME-Version: 1.0
From: "aridaman  kaushik" <kaushik_ari@rediffmail.com>
Reply-To: "aridaman  kaushik" <kaushik_ari@rediffmail.com>
To: isis-wg@spider.juniper.net
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by external.juniper.net id VAA20102
Subject: [Isis-wg] isis route preference
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: 5 Dec 2001 04:38:28 -0000
Content-Transfer-Encoding: 8bit


  I have gone through rfc 2966. This is related L2to L1 leaking(L2 down). It does not talk about L1 down.In draft draft-ietf-isis-ipv6-02.txt section #3

1. if a prefix is redistributed from an area to another area at the same level then the up/down bit shall be set to one.

What is meaning of it. as there is no redistribution of routes from one area to another area. Routes are learned through L2 routing only.

2. in the next sentance, 
if the prefix was distributed into isis form another routing protocol, the external bit shall be set to one. This information is useful while distributing routes from is-is other protocols.
I am not getting how it is useful. 

Please Confirm This. 
3. when ipv6 routes will be leaked from L2 to l1. How should these routes should be distributed, my mean to say, as external reachiablity information or internal reachiablity information.

if it is to be sent as external reachiability information, then external bit the ipv6 prefix TLV should be set to one. But in draft, while leaking routes from L2 to L1, set up/down bit to one. External bit is set only when route is being redisributed from other routing protocol. So leaked route from L2 to L1 should be sent as internal reachiablity information.
thanks in advance
 

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 01:06:04 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA28195
	for <isis-archive@lists.ietf.org>; Wed, 5 Dec 2001 01:06:03 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id WAA20501;
	Tue, 4 Dec 2001 22:25:53 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id WAA20486
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 22:24:49 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id WAA09344;
	Tue, 4 Dec 2001 22:03:06 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <Y2HL8W25>; Tue, 4 Dec 2001 22:03:06 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F627@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Tony Przygienda'" <prz@redback.com>,
        Rajesh Saluja
	 <rsaluja@nortelnetworks.com>
Cc: Philip Christian <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 22:03:05 -0800

Sorry folks - but IMHO you are focusing on the wrong issue. The problem is
not ISHs, but some ambiguity in the current definition of the 3way draft and
the fact that a number of vendors still utilize the old version of the 3 way
handshake which only sends local adjacency state. (Please see my earlier
mail on this subject)

Suggesting that ISHs be ignored just creates more potential backwards
compatibility problems and ignores the real cause of the problem. That
doesn't make sense to me.

(The fact that some implementations already do not send ISHs has created
compatibility problems in that implementations in strict conformance to ISO
10589 will not interoperate with these implementations i.e. an
implementation which expects to receive an ISH before sending an IIH (as per
ISO 10589) will never form an adjacency with an implementation that never
sends an ISH.)

   Les


> -----Original Message-----
> From: Tony Przygienda [mailto:prz@redback.com]
> Sent: Tuesday, December 04, 2001 4:35 PM
> To: Rajesh Saluja
> Cc: Philip Christian; 'isis-wg@spider.juniper.net'; 
> 'dkatz@juniper.net'
> Subject: Re: [Isis-wg] Concerns with 3-way-handshake
> 
> 
> Rajesh Saluja wrote:
> 
> > >
> > >
> > > >From my vintage, yes, it should be fixed, maybe as 
> simply as saying that
> > > three-way-hello capable routers drop ISHs and do not send 
> them ?  The
> > > very details of 1195 slip my mind right now but that 
> should not cause
> > > any backwards capability problems?
> > >
> > >     something is definitely worth an addition to the 
> 3-way-hello draft
> > >
> > >     -- tony
> >
> > I agree with Philip's concerns. Will the following modifications be
> > acceptable to the group:
> > 1. As Tony suggested, say that  three-way-hello capable 
> routers drop ISHs
> > and do not send them.
> 
> you better be very carefull with the MUST and MAYs when 
> writing this. As well,
> someone thinks carefully whether it won't break more than it 
> fixes (although
> deployment with dropped ISHs seems to prove that it works and 
> since we will
>  be able to chhose whether we send/receive them, we can force 
> pretty much
> this situation with the draft).
> 
>     thanks
> 
>     -- tonyt
> 
> _______________________________________________
> Isis-wg mailing list  -  Isis-wg@external.juniper.net
> http://external.juniper.net/mailman/listinfo/isis-wg
> 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 01:13:43 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA29205
	for <isis-archive@lists.ietf.org>; Wed, 5 Dec 2001 01:13:43 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id WAA20549;
	Tue, 4 Dec 2001 22:33:52 -0800 (PST)
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id WAA20537
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 22:32:27 -0800 (PST)
Received: from cirrus.juniper.net (cirrus.juniper.net [172.17.20.57])
	by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id fB56Ah021972;
	Tue, 4 Dec 2001 22:10:43 -0800 (PST)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost)
	by cirrus.juniper.net (8.11.6/8.11.6) id fB56Ab507507;
	Tue, 4 Dec 2001 22:10:37 -0800 (PST)
	(envelope-from dkatz@cirrus.juniper.net)
Message-Id: <200112050610.fB56Ab507507@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: rsaluja@nortelnetworks.com
CC: prz@redback.com, christi@nortelnetworks.com, isis-wg@spider.juniper.net,
        rsaluja@nortelnetworks.com
In-reply-to: <3C0D6B51.7EBB951D@nortelnetworks.com>
	(rsaluja@nortelnetworks.com)
Subject: Re: [Isis-wg] Concerns with 3-way-handshake
References: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com> <3C0D12CA.2B982FCB@redback.com> <3C0D6B51.7EBB951D@nortelnetworks.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 22:10:37 -0800 (PST)

   1. As Tony suggested, say that  three-way-hello capable routers drop ISHs
   and do not send them.

Sounds reasonable.

   2. Reword SONET protection to SONET reprovisioning.

This is *not* what was intended when the draft was written.

SONET purists will choke on their Cheerios when they read this, but several
router vendors have implemented a scheme where two routers act together
as a SONET ADM for the purposes of implementing Automatic Protection
Switching (APS.)  The idea is that the trunk circuit comes into a POP,
hits an ADM, and out the other side come the APS Working and Protect
circuits, which then go into different routers.  This is primarily viewed
as a way of protecting against router/interface failure or somebody
tripping over the last 100 feet of fiber, while keeping the expensive
trunk circuit operating.  The routers coordinate via a back channel
to instigate and react to APS signalling (via the K1/K2 overhead bytes.)

In 1+1 Bidirectional mode, the ADM will send the same bit stream to both
routers, but only listen to one of them.  Without the addition of the
ID stuff, it is theoretically possible that the router on the circuit
not selected by the ADM can think that it has an adjacency to the guy
at the far end of the trunk, which would cause traffic to be poured down
a black hole.

Frankly, I think this bastardization of APS is of dubious use, but the
customers were willing to pay real cash money for it, so I wrote the
APS code.  However, it became apparent that a sane (if that's a
reasonable word to use in this context) implementation will logically
shut down the interface based on APS signalling anyhow, so this
detection mechanism is probably redundant, unless folks have come up
with something else that it is good for.

In any case, this is *not* about DCC, and it is *not* about SONET
provisioning, it's about terminating APS protection on routers running
ISIS in-band over the SONET circuit.

   3. Allowing length of option from 1 (not 5) to 17 octets so that it can work
   with old three way implementations.

Sure.

--Dave



BTW, for what it's worth, the dominant CLNP router in the world did
not couple ISHs to ISIS at all when I last saw the source code (five
years ago) and probably still doesn't today.  It is just as happy to
bring up an ISIS adjacency based on receipt of only an IIH when
operating in CLNP mode as it is in IP mode.  Doesn't make it right,
but there it is.

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 03:40:05 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA16687
	for <isis-archive@lists.ietf.org>; Wed, 5 Dec 2001 03:40:04 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA21317;
	Wed, 5 Dec 2001 00:58:54 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA21305
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 00:57:42 -0800 (PST)
Received: from alpha-tli.procket.com (IDENT:root@alpha-tli.procket.com [10.2.3.1])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fB58a1es019998;
	Wed, 5 Dec 2001 00:36:01 -0800 (PST)
Received: (from tli@localhost)
	by alpha-tli.procket.com (8.12.1/8.12.1) id fB58a1rF005757;
	Wed, 5 Dec 2001 00:36:01 -0800
From: Tony Li <tli@Procket.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15373.56433.93331.6355@alpha-tli.procket.com>
To: "aridaman  kaushik" <kaushik_ari@rediffmail.com>
Cc: isis-wg@spider.juniper.net
Subject: [Isis-wg] isis route preference
In-Reply-To: <20011205043828.2677.qmail@mailweb12.rediffmail.com>
References: <20011205043828.2677.qmail@mailweb12.rediffmail.com>
X-Mailer: VM 6.92 under Emacs 20.5.1
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 5 Dec 2001 00:36:01 -0800
Content-Transfer-Encoding: 7bit



 |   I have gone through rfc 2966. This is related L2to L1 leaking(L2
 |   down). It does not talk about L1 down.In draft
 |   draft-ietf-isis-ipv6-02.txt section #3
 | 
 | 1. if a prefix is redistributed from an area to another area at the same
 | level then the up/down bit shall be set to one.
 | 
 | What is meaning of it. as there is no redistribution of routes from one
 | area to another area. Routes are learned through L2 routing only.


Certain implementations allow a router to participate in multiple different
L1 areas and interchange routes between the different L1 areas.  Clearly
this is way past the spirit of ISO 10589, but is also not impossible.  It
seems like a reasonable condition to add.


 | 2. in the next sentance,
 | if the prefix was distributed into isis form another routing protocol,
 | the external bit shall be set to one. This information is useful while
 | distributing routes from is-is other protocols.  I am not getting how it
 | is useful.


An obvious benefit is the ability to subsequently write policy about those
external routes when injecting routes from IS-IS into another routing
protocol.

Example: suppose that I have a domain that is routed with both IS-IS and
OSPF [possibly as the result of an acquistion].  As a migration aid, I wish
to interconnect the domain at multiple points yet not convert to one or the
other IGP in a flash manner.  If I leak OSPF non-externals into IS-IS and
mark them external and then I leak IS-IS non-externals into OSPF, I have
full connectivity without a feedback loop.


 | Please Confirm This.  3. when ipv6 routes will be leaked from L2 to
 | l1. How should these routes should be distributed, my mean to say, as
 | external reachiablity information or internal reachiablity information.


It's still internal.

Tony
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 04:52:59 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA17582
	for <isis-archive@lists.ietf.org>; Wed, 5 Dec 2001 04:52:57 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA21822;
	Wed, 5 Dec 2001 02:12:53 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA21810
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 02:11:51 -0800 (PST)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4186.cisco.com [10.50.16.89])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id JAA08400;
	Wed, 5 Dec 2001 09:50:06 GMT
Message-Id: <4.3.2.7.2.20011205094706.033305f8@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Philip Christian" <christi@nortelnetworks.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] Concerns with 3-way-handshake
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
In-Reply-To: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nor
 tel.com>
Mime-Version: 1.0
Content-Type: text/html; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 05 Dec 2001 09:50:27 +0000

<html>
At 17:34 04/12/2001 +0000, Philip Christian wrote:<br>
<blockquote type=cite cite><font size=2>Such a new dual node may well
need to declare itself a CLNS End System, and so will be transmitting
ISHs. This will be necessary to terminate RFC 3147 encapsulated packets,
for example.</blockquote><br>
I don't understand what you mean here. Sending ISHs has nothing to do
with being an ES, and it is CERTAINLY not necessary to declare itself an
ES in order to terminate CLNP packets. An IS can do that just as well.
The only reason an IS sends ISHs over a pt-pt link is in case the system
at thew other end happens to be an ES (only). Becuasre it has to do this,
the ISH sending is integrated into the IIH initialization sequence.<br>
<br>
<x-tab>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</x-tab>Mike<br>
</font></html>

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 05:05:07 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17692
	for <isis-archive@lists.ietf.org>; Wed, 5 Dec 2001 05:05:07 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA21891;
	Wed, 5 Dec 2001 02:24:53 -0800 (PST)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA21879
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 02:23:55 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB5A1Xd12168;
	Wed, 5 Dec 2001 05:01:34 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB5A25l22271;
	Wed, 5 Dec 2001 10:02:05 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6LV3GA>; Wed, 5 Dec 2001 10:01:00 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071395@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: "'mike shand'" <mshand@cisco.com>
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "Rajesh Saluja" <rsaluja@nortelnetworks.com>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17D73.A8EAB670"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 5 Dec 2001 10:00:25 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17D73.A8EAB670
Content-Type: text/plain;
	charset="iso-8859-1"

Yes, I got this wrong. I believe that the ISHs are there so that an IS can
say hello to an ES. Thus an CLNP capable router needs to send ISHs to talk
to an CLNS End System, but a pure IP router maybe does not.
 
However the ISHs still have to be there if one wants to build a dual router,
and I still believe that they short circuit the 3-way-handshake (as if it
isn't there) as it is in its current form.
 
thanks, Philip

-----Original Message-----
From: mike shand [mailto:mshand@cisco.com]
Sent: 05 December 2001 09:50
To: Christian, Philip [HAL02:GI50:EXCH]
Cc: 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net'; Saluja, Rajesh
[BL60:432:EXCH]
Subject: Re: [Isis-wg] Concerns with 3-way-handshake


At 17:34 04/12/2001 +0000, Philip Christian wrote:


Such a new dual node may well need to declare itself a CLNS End System, and
so will be transmitting ISHs. This will be necessary to terminate RFC 3147
encapsulated packets, for example.


I don't understand what you mean here. Sending ISHs has nothing to do with
being an ES, and it is CERTAINLY not necessary to declare itself an ES in
order to terminate CLNP packets. An IS can do that just as well. The only
reason an IS sends ISHs over a pt-pt link is in case the system at thew
other end happens to be an ES (only). Becuasre it has to do this, the ISH
sending is integrated into the IIH initialization sequence.

        Mike



------_=_NextPart_001_01C17D73.A8EAB670
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">


<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=070435609-05122001>Yes, I 
got this wrong. I believe that the ISHs are there so that an IS can say hello to 
an ES. Thus an CLNP capable router needs to send ISHs to talk to an CLNS End 
System, but a pure IP router maybe does not.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=070435609-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=070435609-05122001>However the ISHs still have to be there if one wants to 
build a dual router, and I still believe that they short circuit the 
3-way-handshake (as if it isn't there) as it is in its current 
form.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=070435609-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=070435609-05122001>thanks, Philip</SPAN></FONT></DIV>
<BLOCKQUOTE>
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>-----Original Message-----<BR><B>From:</B> mike shand 
  [mailto:mshand@cisco.com]<BR><B>Sent:</B> 05 December 2001 09:50<BR><B>To:</B> 
  Christian, Philip [HAL02:GI50:EXCH]<BR><B>Cc:</B> 
  'isis-wg@spider.juniper.net'; 'dkatz@juniper.net'; Saluja, Rajesh 
  [BL60:432:EXCH]<BR><B>Subject:</B> Re: [Isis-wg] Concerns with 
  3-way-handshake<BR><BR></DIV></FONT>At 17:34 04/12/2001 +0000, Philip 
  Christian wrote:<BR>
  <BLOCKQUOTE cite type="cite"><FONT size=2>Such a new dual node may well need 
    to declare itself a CLNS End System, and so will be transmitting ISHs. This 
    will be necessary to terminate RFC 3147 encapsulated packets, for 
  example.</BLOCKQUOTE><BR>I don't understand what you mean here. Sending ISHs 
  has nothing to do with being an ES, and it is CERTAINLY not necessary to 
  declare itself an ES in order to terminate CLNP packets. An IS can do that 
  just as well. The only reason an IS sends ISHs over a pt-pt link is in case 
  the system at thew other end happens to be an ES (only). Becuasre it has to do 
  this, the ISH sending is integrated into the IIH initialization 
  sequence.<BR><BR><X-TAB>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;</X-TAB>Mike<BR></BLOCKQUOTE></FONT></BODY></HTML>

------_=_NextPart_001_01C17D73.A8EAB670--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 06:02:28 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18191
	for <isis-archive@odin.ietf.org>; Wed, 5 Dec 2001 06:02:27 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA22232;
	Wed, 5 Dec 2001 03:21:54 -0800 (PST)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA22220
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 03:20:48 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB5AwPd24713;
	Wed, 5 Dec 2001 05:58:26 -0500 (EST)
Received: from znsgy0k8.europe.nortel.com (znsgy0k8.europe.nortel.com [47.165.24.67])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB5Awxl03651;
	Wed, 5 Dec 2001 10:58:59 GMT
Received: by znsgy0k8.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YHZ2FVN6>; Wed, 5 Dec 2001 10:57:39 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071396@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: "'Les Ginsberg'" <ginsberg@pluris.com>,
        "'Tony Przygienda'" <prz@redback.com>,
        "Rajesh Saluja" <rsaluja@nortelnetworks.com>
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17D7A.C7C1E620"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 5 Dec 2001 10:51:23 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17D7A.C7C1E620
Content-Type: text/plain;
	charset="ISO-8859-1"

I (and a colleague, credit where it's due) can think of a couple of ways to
solve this problem.
First we could add an explicit statement such as

"Sending and receiving ISHs is required by Intermediate Systems that can
route CLNP packets. Intermediate Systems that cannot route CLNP may or may
not send and receive ISHs."

Now here are the two ideas

1.
On Intermediate Systems where receipt of an ISH causes an adjacency to start
in the "initialise" state, and which support the "Point-to-Point Adjacency
State" option, such an adjacency will be reported in the option as being
Adjacency State "Down". Once an IIH has been received then the state of the
adjacency shall be reported in the option as normal.

or

2.
On Intermediate Systems where receipt of an ISH caused an adjacency to start
in the "initialise" state, and which support the "Point-to-Point Adjacency
State" option, such an adjacency will be reported in the option as being
Adjacency State 3 = "ISH_init" (for example). Intermediate Systems that do
not send and receive ISHs are not required to implement reporting of this
state, as they will neither send it, nor cause a neighbour to send it back
to them. We then have to mess with the table a little, basically saying that
if you support ISHs and receive an "ISH_init" then you go to "Initialise"
(rather than "up", which was the problem).

I think that both of these ideas allow routers that support CLNP forwarding
to also use the 3-way-handshake, without upsetting anyone who has already
stopped using ISHs on their pure IP implementations.

I prefer idea "2", as "1" feels like the IS is misreporting the state, and
just doesn't appeal to my sense of correctness so well.

The problem with "2" is that if you send an ISH to an IS, then you can
expect it to send back this new Adjacency State = 3 ="ISH_init" message
back. Now it seems to me that if someone just dumps incoming ISHs then they
shouldn't be trasmitting them either, but if someone HAS implemented that,
then they are going to get "3=ISH_init"s coming back at them and won't know
what to do with them (maybe that doesn't matter anyway, as long as they
don't bring the adjacency up).

Comments? other ideas?

Philip Christian

-----Original Message-----
From: Les Ginsberg [mailto:ginsberg@pluris.com]
Sent: 05 December 2001 06:03
To: 'Tony Przygienda'; Saluja, Rajesh [BL60:432:EXCH]
Cc: Christian, Philip [HAL02:GI50:EXCH]; 'isis-wg@spider.juniper.net';
'dkatz@juniper.net'
Subject: RE: [Isis-wg] Concerns with 3-way-handshake


Sorry folks - but IMHO you are focusing on the wrong issue. The problem is
not ISHs, but some ambiguity in the current definition of the 3way draft and
the fact that a number of vendors still utilize the old version of the 3 way
handshake which only sends local adjacency state. (Please see my earlier
mail on this subject)

Suggesting that ISHs be ignored just creates more potential backwards
compatibility problems and ignores the real cause of the problem. That
doesn't make sense to me.

(The fact that some implementations already do not send ISHs has created
compatibility problems in that implementations in strict conformance to ISO
10589 will not interoperate with these implementations i.e. an
implementation which expects to receive an ISH before sending an IIH (as per
ISO 10589) will never form an adjacency with an implementation that never
sends an ISH.)

   Les


> -----Original Message-----
> From: Tony Przygienda [mailto:prz@redback.com]
> Sent: Tuesday, December 04, 2001 4:35 PM
> To: Rajesh Saluja
> Cc: Philip Christian; 'isis-wg@spider.juniper.net'; 
> 'dkatz@juniper.net'
> Subject: Re: [Isis-wg] Concerns with 3-way-handshake
> 
> 
> Rajesh Saluja wrote:
> 
> > >
> > >
> > > >From my vintage, yes, it should be fixed, maybe as 
> simply as saying that
> > > three-way-hello capable routers drop ISHs and do not send 
> them ?  The
> > > very details of 1195 slip my mind right now but that 
> should not cause
> > > any backwards capability problems?
> > >
> > >     something is definitely worth an addition to the 
> 3-way-hello draft
> > >
> > >     -- tony
> >
> > I agree with Philip's concerns. Will the following modifications be
> > acceptable to the group:
> > 1. As Tony suggested, say that  three-way-hello capable 
> routers drop ISHs
> > and do not send them.
> 
> you better be very carefull with the MUST and MAYs when 
> writing this. As well,
> someone thinks carefully whether it won't break more than it 
> fixes (although
> deployment with dropped ISHs seems to prove that it works and 
> since we will
>  be able to chhose whether we send/receive them, we can force 
> pretty much
> this situation with the draft).
> 
>     thanks
> 
>     -- tonyt
> 
> _______________________________________________
> Isis-wg mailing list  -  Isis-wg@external.juniper.net
> http://external.juniper.net/mailman/listinfo/isis-wg
> 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg

------_=_NextPart_001_01C17D7A.C7C1E620
Content-Type: text/html;
	charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3DISO-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Isis-wg] Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I (and a colleague, credit where it's due) can think =
of a couple of ways to solve this problem.</FONT>
<BR><FONT SIZE=3D2>First we could add an explicit statement such =
as</FONT>
</P>

<P><FONT SIZE=3D2>&quot;Sending and receiving ISHs is required by =
Intermediate Systems that can route CLNP packets. Intermediate Systems =
that cannot route CLNP may or may not send and receive =
ISHs.&quot;</FONT></P>

<P><FONT SIZE=3D2>Now here are the two ideas</FONT>
</P>

<P><FONT SIZE=3D2>1.</FONT>
<BR><FONT SIZE=3D2>On Intermediate Systems where receipt of an ISH =
causes an adjacency to start in the &quot;initialise&quot; state, and =
which support the &quot;Point-to-Point Adjacency State&quot; option, =
such an adjacency will be reported in the option as being Adjacency =
State &quot;Down&quot;. Once an IIH has been received then the state of =
the adjacency shall be reported in the option as normal.</FONT></P>

<P><FONT SIZE=3D2>or</FONT>
</P>

<P><FONT SIZE=3D2>2.</FONT>
<BR><FONT SIZE=3D2>On Intermediate Systems where receipt of an ISH =
caused an adjacency to start in the &quot;initialise&quot; state, and =
which support the &quot;Point-to-Point Adjacency State&quot; option, =
such an adjacency will be reported in the option as being Adjacency =
State 3 =3D &quot;ISH_init&quot; (for example). Intermediate Systems =
that do not send and receive ISHs are not required to implement =
reporting of this state, as they will neither send it, nor cause a =
neighbour to send it back to them. We then have to mess with the table =
a little, basically saying that if you support ISHs and receive an =
&quot;ISH_init&quot; then you go to &quot;Initialise&quot; (rather than =
&quot;up&quot;, which was the problem).</FONT></P>

<P><FONT SIZE=3D2>I think that both of these ideas allow routers that =
support CLNP forwarding to also use the 3-way-handshake, without =
upsetting anyone who has already stopped using ISHs on their pure IP =
implementations.</FONT></P>

<P><FONT SIZE=3D2>I prefer idea &quot;2&quot;, as &quot;1&quot; feels =
like the IS is misreporting the state, and just doesn't appeal to my =
sense of correctness so well.</FONT></P>

<P><FONT SIZE=3D2>The problem with &quot;2&quot; is that if you send an =
ISH to an IS, then you can expect it to send back this new Adjacency =
State =3D 3 =3D&quot;ISH_init&quot; message back. Now it seems to me =
that if someone just dumps incoming ISHs then they shouldn't be =
trasmitting them either, but if someone HAS implemented that, then they =
are going to get &quot;3=3DISH_init&quot;s coming back at them and =
won't know what to do with them (maybe that doesn't matter anyway, as =
long as they don't bring the adjacency up).</FONT></P>

<P><FONT SIZE=3D2>Comments? other ideas?</FONT>
</P>

<P><FONT SIZE=3D2>Philip Christian</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Les Ginsberg [<A =
HREF=3D"mailto:ginsberg@pluris.com">mailto:ginsberg@pluris.com</A>]</FON=
T>
<BR><FONT SIZE=3D2>Sent: 05 December 2001 06:03</FONT>
<BR><FONT SIZE=3D2>To: 'Tony Przygienda'; Saluja, Rajesh =
[BL60:432:EXCH]</FONT>
<BR><FONT SIZE=3D2>Cc: Christian, Philip [HAL02:GI50:EXCH]; =
'isis-wg@spider.juniper.net';</FONT>
<BR><FONT SIZE=3D2>'dkatz@juniper.net'</FONT>
<BR><FONT SIZE=3D2>Subject: RE: [Isis-wg] Concerns with =
3-way-handshake</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>Sorry folks - but IMHO you are focusing on the wrong =
issue. The problem is</FONT>
<BR><FONT SIZE=3D2>not ISHs, but some ambiguity in the current =
definition of the 3way draft and</FONT>
<BR><FONT SIZE=3D2>the fact that a number of vendors still utilize the =
old version of the 3 way</FONT>
<BR><FONT SIZE=3D2>handshake which only sends local adjacency state. =
(Please see my earlier</FONT>
<BR><FONT SIZE=3D2>mail on this subject)</FONT>
</P>

<P><FONT SIZE=3D2>Suggesting that ISHs be ignored just creates more =
potential backwards</FONT>
<BR><FONT SIZE=3D2>compatibility problems and ignores the real cause of =
the problem. That</FONT>
<BR><FONT SIZE=3D2>doesn't make sense to me.</FONT>
</P>

<P><FONT SIZE=3D2>(The fact that some implementations already do not =
send ISHs has created</FONT>
<BR><FONT SIZE=3D2>compatibility problems in that implementations in =
strict conformance to ISO</FONT>
<BR><FONT SIZE=3D2>10589 will not interoperate with these =
implementations i.e. an</FONT>
<BR><FONT SIZE=3D2>implementation which expects to receive an ISH =
before sending an IIH (as per</FONT>
<BR><FONT SIZE=3D2>ISO 10589) will never form an adjacency with an =
implementation that never</FONT>
<BR><FONT SIZE=3D2>sends an ISH.)</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; Les</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt; -----Original Message-----</FONT>
<BR><FONT SIZE=3D2>&gt; From: Tony Przygienda [<A =
HREF=3D"mailto:prz@redback.com">mailto:prz@redback.com</A>]</FONT>
<BR><FONT SIZE=3D2>&gt; Sent: Tuesday, December 04, 2001 4:35 PM</FONT>
<BR><FONT SIZE=3D2>&gt; To: Rajesh Saluja</FONT>
<BR><FONT SIZE=3D2>&gt; Cc: Philip Christian; =
'isis-wg@spider.juniper.net'; </FONT>
<BR><FONT SIZE=3D2>&gt; 'dkatz@juniper.net'</FONT>
<BR><FONT SIZE=3D2>&gt; Subject: Re: [Isis-wg] Concerns with =
3-way-handshake</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; Rajesh Saluja wrote:</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; &gt;From my vintage, yes, it should =
be fixed, maybe as </FONT>
<BR><FONT SIZE=3D2>&gt; simply as saying that</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; three-way-hello capable routers drop =
ISHs and do not send </FONT>
<BR><FONT SIZE=3D2>&gt; them ?&nbsp; The</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; very details of 1195 slip my mind =
right now but that </FONT>
<BR><FONT SIZE=3D2>&gt; should not cause</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt; any backwards capability =
problems?</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; something is =
definitely worth an addition to the </FONT>
<BR><FONT SIZE=3D2>&gt; 3-way-hello draft</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; -- =
tony</FONT>
<BR><FONT SIZE=3D2>&gt; &gt;</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; I agree with Philip's concerns. Will the =
following modifications be</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; acceptable to the group:</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; 1. As Tony suggested, say that&nbsp; =
three-way-hello capable </FONT>
<BR><FONT SIZE=3D2>&gt; routers drop ISHs</FONT>
<BR><FONT SIZE=3D2>&gt; &gt; and do not send them.</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; you better be very carefull with the MUST and =
MAYs when </FONT>
<BR><FONT SIZE=3D2>&gt; writing this. As well,</FONT>
<BR><FONT SIZE=3D2>&gt; someone thinks carefully whether it won't break =
more than it </FONT>
<BR><FONT SIZE=3D2>&gt; fixes (although</FONT>
<BR><FONT SIZE=3D2>&gt; deployment with dropped ISHs seems to prove =
that it works and </FONT>
<BR><FONT SIZE=3D2>&gt; since we will</FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp; be able to chhose whether we send/receive =
them, we can force </FONT>
<BR><FONT SIZE=3D2>&gt; pretty much</FONT>
<BR><FONT SIZE=3D2>&gt; this situation with the draft).</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; thanks</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; -- tonyt</FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT SIZE=3D2>&gt; =
_______________________________________________</FONT>
<BR><FONT SIZE=3D2>&gt; Isis-wg mailing list&nbsp; -&nbsp; =
Isis-wg@external.juniper.net</FONT>
<BR><FONT SIZE=3D2>&gt; <A HREF=3D"http://external.juniper.net/mailman/l=
istinfo/isis-wg" =
TARGET=3D"_blank">http://external.juniper.net/mailman/listinfo/isis-wg</=
A></FONT>
<BR><FONT SIZE=3D2>&gt; </FONT>
<BR><FONT =
SIZE=3D2>_______________________________________________</FONT>
<BR><FONT SIZE=3D2>Isis-wg mailing list&nbsp; -&nbsp; =
Isis-wg@external.juniper.net</FONT>
<BR><FONT SIZE=3D2><A =
HREF=3D"http://external.juniper.net/mailman/listinfo/isis-wg" =
TARGET=3D"_blank">http://external.juniper.net/mailman/listinfo/isis-wg</=
A></FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17D7A.C7C1E620--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 09:12:14 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21262
	for <isis-archive@odin.ietf.org>; Wed, 5 Dec 2001 09:12:14 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA23175;
	Wed, 5 Dec 2001 06:31:53 -0800 (PST)
Received: from mailFA9.rediffmail.com ([202.54.124.178])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id GAA23163
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 06:30:52 -0800 (PST)
Received: (qmail 23092 invoked by uid 510); 5 Dec 2001 14:08:24 -0000
Message-ID: <20011205140824.23091.qmail@mailFA9.rediffmail.com>
Received: from unknown (203.197.138.194) by rediffmail.com via HTTP; 05 Dec 2001 14:08:24 -0000
MIME-Version: 1.0
From: "perumal  conf" <perconf@rediffmail.com>
Reply-To: "perumal  conf" <perconf@rediffmail.com>
To: isis-wg@spider.juniper.net
Content-type: text/plain;
	charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by external.juniper.net id GAA23164
Subject: [Isis-wg] IS-IS commands - Need info
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: 5 Dec 2001 14:08:24 -0000
Content-Transfer-Encoding: 8bit


Hi all
   I am unable to get the description and usage of "external overload signalling" IS-IS command.  Any information about this would be helpful to me.

Thanks in advance for your response
per

 

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 11:01:23 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25485
	for <isis-archive@odin.ietf.org>; Wed, 5 Dec 2001 11:01:22 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id IAA23681;
	Wed, 5 Dec 2001 08:20:54 -0800 (PST)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id IAA23666
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 08:19:44 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734290122FF1E@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'aridamank@future.futsoft.com'" <aridamank@future.futsoft.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] (no subject)
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 5 Dec 2001 10:57:56 -0500

> hi Jeff,
>       I have gone through rfc 2966. This is related L2to L1 leaking(L2
> down). It does not talk about L1 down.In draft 
> draft-ietf-isis-ipv6-02.txt section #3
> 
> 1. if a prefix is redistributed from an area to another area 
> at the same level then the up/down bit shall be set to one.

Isn't an L1 down a route that has been up to L2 and back?
 
> What is meaning of it. as there is no redistribution of 
> routes from one area
> to another area. Routes are learned through L2 routing only.

If they are leaked from L1 to L2 back down to L1, then it
is a different L1 area, as there would be no point in
returning it to the same area.  
 
> 2. in the next sentance,
> if the prefix was distributed into isis form another routing 
> protocol, the
> external bit shall be set to one. This information is useful while
> distributing routes from is-is other protocols.
> I am not getting how it is useful.

As routes slosh around from say BGP to IS-IS, information is lost,
esp. if you are sticking with 1195 metrics.  This bit could be
used, if you trusted it, to let you know that you are exporting
a genuine copy of a distorted metric, and to make adjustments 
accordingly: perhaps deciding not to use the route if there was
anything the looked more plausible.  

Mark Twain wrote a version of the "Jumping Frog of Calaveras 
County" that was a translation of a French translation of his
story.  I found it funnier than the original.  While much is
lost in translation, even more is lost in a second translation.  

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 11:47:43 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27372
	for <isis-archive@odin.ietf.org>; Wed, 5 Dec 2001 11:47:42 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA23933;
	Wed, 5 Dec 2001 09:07:55 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA23921
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 09:06:08 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fB5GiOc21188;
	Wed, 5 Dec 2001 11:44:24 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AGQ57695;
	Wed, 5 Dec 2001 11:44:17 -0500 (EST)
Message-Id: <4.3.2.7.2.20011205110907.01f0def8@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Philip Christian" <christi@nortelnetworks.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
Cc: "'Les Ginsberg'" <ginsberg@pluris.com>,
        "'Tony Przygienda'" <prz@redback.com>,
        "Rajesh Saluja" <rsaluja@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
In-Reply-To: <4103264BC8D3D51180B7002048400C45071396@zhard0jd.europe.nor
 tel.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_4939202==_.ALT"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 05 Dec 2001 11:17:10 -0500

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

At 05:51 AM 12/5/2001, Philip Christian wrote:

>I (and a colleague, credit where it's due) can think of a couple of ways to solve this problem. 
>First we could add an explicit statement such as 
>
>"Sending and receiving ISHs is required by Intermediate Systems that can route CLNP packets. Intermediate Systems that cannot route CLNP may or may not send and receive ISHs."

Is this intended as a statement of fact or as a proposed normative
statement?  If it's supposed to be normative, use SHOULD, MAY, and MUST.
If it's descriptive of standards, it's inaccurate, because 10589
and 1195 both require sending ISH PDUs.  If it's a statement of
practical fact, then it should be carefully written to state that --
e.g.,

  "Practically speaking, ISs that support CLNP need to send ISH
  packets on point-to-point links that might be connected to ESs in
  order for CLNP ESs to be able to communicate properly.  Many existing
  IP-only implementations fail to send ISH PDUs, even though it's required
  by 10589 and RFC-1195, and most (many?) IS-IS implementations interoperate
  with these implementations.

We need to be clear and accurate!  If I've made any inaccurate statements
here, please point them out.

Statements below are also not written using MUST, MAY, or SHOULD, and
need to be rewritten to say what the author means, because as written,
they can be misinterpreted as descriptive statements rather than
normative statements, which I assume they're intended to be.

Regards,
Jeff


>Now here are the two ideas 
>
>1. 
>On Intermediate Systems where receipt of an ISH causes an adjacency to start in the "initialise" state, and which support the "Point-to-Point Adjacency State" option, such an adjacency will be reported in the option as being Adjacency State "Down". Once an IIH has been received then the state of the adjacency shall be reported in the option as normal.
>
>or 
>
>2. 
>On Intermediate Systems where receipt of an ISH caused an adjacency to start in the "initialise" state, and which support the "Point-to-Point Adjacency State" option, such an adjacency will be reported in the option as being Adjacency State 3 = "ISH_init" (for example). Intermediate Systems that do not send and receive ISHs are not required to implement reporting of this state, as they will neither send it, nor cause a neighbour to send it back to them. We then have to mess with the table a little, basically saying that if you support ISHs and receive an "ISH_init" then you go to "Initialise" (rather than "up", which was the problem).
>
>I think that both of these ideas allow routers that support CLNP forwarding to also use the 3-way-handshake, without upsetting anyone who has already stopped using ISHs on their pure IP implementations.
>
>I prefer idea "2", as "1" feels like the IS is misreporting the state, and just doesn't appeal to my sense of correctness so well.
>
>The problem with "2" is that if you send an ISH to an IS, then you can expect it to send back this new Adjacency State = 3 ="ISH_init" message back. Now it seems to me that if someone just dumps incoming ISHs then they shouldn't be trasmitting them either, but if someone HAS implemented that, then they are going to get "3=ISH_init"s coming back at them and won't know what to do with them (maybe that doesn't matter anyway, as long as they don't bring the adjacency up).
>
>Comments? other ideas? 
>
>Philip Christian 
>
>-----Original Message----- 
>From: Les Ginsberg [<mailto:ginsberg@pluris.com>mailto:ginsberg@pluris.com] 
>Sent: 05 December 2001 06:03 
>To: 'Tony Przygienda'; Saluja, Rajesh [BL60:432:EXCH] 
>Cc: Christian, Philip [HAL02:GI50:EXCH]; 'isis-wg@spider.juniper.net'; 
>'dkatz@juniper.net' 
>Subject: RE: [Isis-wg] Concerns with 3-way-handshake 
>
>Sorry folks - but IMHO you are focusing on the wrong issue. The problem is 
>not ISHs, but some ambiguity in the current definition of the 3way draft and 
>the fact that a number of vendors still utilize the old version of the 3 way 
>handshake which only sends local adjacency state. (Please see my earlier 
>mail on this subject) 
>
>Suggesting that ISHs be ignored just creates more potential backwards 
>compatibility problems and ignores the real cause of the problem. That 
>doesn't make sense to me. 
>
>(The fact that some implementations already do not send ISHs has created 
>compatibility problems in that implementations in strict conformance to ISO 
>10589 will not interoperate with these implementations i.e. an 
>implementation which expects to receive an ISH before sending an IIH (as per 
>ISO 10589) will never form an adjacency with an implementation that never 
>sends an ISH.) 
>
>   Les 
>
>> -----Original Message----- 
>> From: Tony Przygienda [<mailto:prz@redback.com>mailto:prz@redback.com] 
>> Sent: Tuesday, December 04, 2001 4:35 PM 
>> To: Rajesh Saluja 
>> Cc: Philip Christian; 'isis-wg@spider.juniper.net'; 
>> 'dkatz@juniper.net' 
>> Subject: Re: [Isis-wg] Concerns with 3-way-handshake 
>> 
>> 
>> Rajesh Saluja wrote: 
>> 
>> > > 
>> > > 
>> > > >From my vintage, yes, it should be fixed, maybe as 
>> simply as saying that 
>> > > three-way-hello capable routers drop ISHs and do not send 
>> them ?  The 
>> > > very details of 1195 slip my mind right now but that 
>> should not cause 
>> > > any backwards capability problems? 
>> > > 
>> > >     something is definitely worth an addition to the 
>> 3-way-hello draft 
>> > > 
>> > >     -- tony 
>> > 
>> > I agree with Philip's concerns. Will the following modifications be 
>> > acceptable to the group: 
>> > 1. As Tony suggested, say that  three-way-hello capable 
>> routers drop ISHs 
>> > and do not send them. 
>> 
>> you better be very carefull with the MUST and MAYs when 
>> writing this. As well, 
>> someone thinks carefully whether it won't break more than it 
>> fixes (although 
>> deployment with dropped ISHs seems to prove that it works and 
>> since we will 
>>  be able to chhose whether we send/receive them, we can force 
>> pretty much 
>> this situation with the draft). 
>> 
>>     thanks 
>> 
>>     -- tonyt 
>> 
>> _______________________________________________ 
>> Isis-wg mailing list  -  Isis-wg@external.juniper.net 
>> <http://external.juniper.net/mailman/listinfo/isis-wg>http://external.juniper.net/mailman/listinfo/isis-wg 
>> 
>_______________________________________________ 
>Isis-wg mailing list  -  Isis-wg@external.juniper.net 
><http://external.juniper.net/mailman/listinfo/isis-wg>http://external.juniper.net/mailman/listinfo/isis-wg 

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

<html>
At 05:51 AM 12/5/2001, Philip Christian wrote:<br>
<br>
<blockquote type=cite cite><font size=2>I (and a colleague, credit where
it's due) can think of a couple of ways to solve this problem.</font>
<br>
<font size=2>First we could add an explicit statement such as</font>
<br>
<br>
<font size=2>&quot;Sending and receiving ISHs is required by Intermediate Systems that can route CLNP packets. Intermediate Systems that cannot route CLNP may or may not send and receive ISHs.&quot;</font></blockquote><br>
Is this intended as a statement of fact or as a proposed normative<br>
statement?&nbsp; If it's supposed to be normative, use SHOULD, MAY, and MUST.<br>
If it's descriptive of standards, it's inaccurate, because 10589<br>
and 1195 both require sending ISH PDUs.&nbsp; If it's a statement of<br>
practical fact, then it should be carefully written to state that --<br>
e.g.,<br>
<br>
&nbsp; &quot;Practically speaking, ISs that support CLNP need to send ISH<br>
&nbsp; packets on point-to-point links that might be connected to ESs in<br>
&nbsp; order for CLNP ESs to be able to communicate properly.&nbsp; Many existing<br>
&nbsp; IP-only implementations fail to send ISH PDUs, even though it's required<br>
&nbsp; by 10589 and RFC-1195, and most (many?) IS-IS implementations interoperate<br>
&nbsp; with these implementations.<br>
<br>
We need to be clear and accurate!&nbsp; If I've made any inaccurate statements<br>
here, please point them out.<br>
<br>
Statements below are also not written using MUST, MAY, or SHOULD, and<br>
need to be rewritten to say what the author means, because as written,<br>
they can be misinterpreted as descriptive statements rather than<br>
normative statements, which I assume they're intended to be.<br>
<br>
Regards,<br>
Jeff<br>
<br>
<br>
<blockquote type=cite cite><font size=2>Now here are the two ideas</font> <br>
<br>
<font size=2>1.</font> <br>
<font size=2>On Intermediate Systems where receipt of an ISH causes an adjacency to start in the &quot;initialise&quot; state, and which support the &quot;Point-to-Point Adjacency State&quot; option, such an adjacency will be reported in the option as being Adjacency State &quot;Down&quot;. Once an IIH has been received then the state of the adjacency shall be reported in the option as normal.<br>
</font><br>
<font size=2>or</font> <br>
<br>
<font size=2>2.</font> <br>
<font size=2>On Intermediate Systems where receipt of an ISH caused an adjacency to start in the &quot;initialise&quot; state, and which support the &quot;Point-to-Point Adjacency State&quot; option, such an adjacency will be reported in the option as being Adjacency State 3 = &quot;ISH_init&quot; (for example). Intermediate Systems that do not send and receive ISHs are not required to implement reporting of this state, as they will neither send it, nor cause a neighbour to send it back to them. We then have to mess with the table a little, basically saying that if you support ISHs and receive an &quot;ISH_init&quot; then you go to &quot;Initialise&quot; (rather than &quot;up&quot;, which was the problem).<br>
</font><br>
<font size=2>I think that both of these ideas allow routers that support CLNP forwarding to also use the 3-way-handshake, without upsetting anyone who has already stopped using ISHs on their pure IP implementations.<br>
</font><br>
<font size=2>I prefer idea &quot;2&quot;, as &quot;1&quot; feels like the IS is misreporting the state, and just doesn't appeal to my sense of correctness so well.<br>
</font><br>
<font size=2>The problem with &quot;2&quot; is that if you send an ISH to an IS, then you can expect it to send back this new Adjacency State = 3 =&quot;ISH_init&quot; message back. Now it seems to me that if someone just dumps incoming ISHs then they shouldn't be trasmitting them either, but if someone HAS implemented that, then they are going to get &quot;3=ISH_init&quot;s coming back at them and won't know what to do with them (maybe that doesn't matter anyway, as long as they don't bring the adjacency up).<br>
</font><br>
<font size=2>Comments? other ideas?</font> <br>
<br>
<font size=2>Philip Christian</font> <br>
<br>
<font size=2>-----Original Message-----</font> <br>
<font size=2>From: Les Ginsberg [<a href="mailto:ginsberg@pluris.com">mailto:ginsberg@pluris.com</a>]</font> <br>
<font size=2>Sent: 05 December 2001 06:03</font> <br>
<font size=2>To: 'Tony Przygienda'; Saluja, Rajesh [BL60:432:EXCH]</font> <br>
<font size=2>Cc: Christian, Philip [HAL02:GI50:EXCH]; 'isis-wg@spider.juniper.net';</font> <br>
<font size=2>'dkatz@juniper.net'</font> <br>
<font size=2>Subject: RE: [Isis-wg] Concerns with 3-way-handshake</font> <br>
<br>
<font size=2>Sorry folks - but IMHO you are focusing on the wrong issue. The problem is</font> <br>
<font size=2>not ISHs, but some ambiguity in the current definition of the 3way draft and</font> <br>
<font size=2>the fact that a number of vendors still utilize the old version of the 3 way</font> <br>
<font size=2>handshake which only sends local adjacency state. (Please see my earlier</font> <br>
<font size=2>mail on this subject)</font> <br>
<br>
<font size=2>Suggesting that ISHs be ignored just creates more potential backwards</font> <br>
<font size=2>compatibility problems and ignores the real cause of the problem. That</font> <br>
<font size=2>doesn't make sense to me.</font> <br>
<br>
<font size=2>(The fact that some implementations already do not send ISHs has created</font> <br>
<font size=2>compatibility problems in that implementations in strict conformance to ISO</font> <br>
<font size=2>10589 will not interoperate with these implementations i.e. an</font> <br>
<font size=2>implementation which expects to receive an ISH before sending an IIH (as per</font> <br>
<font size=2>ISO 10589) will never form an adjacency with an implementation that never</font> <br>
<font size=2>sends an ISH.)</font> <br>
<br>
<font size=2>&nbsp;&nbsp; Les</font> <br>
<br>
<font size=2>&gt; -----Original Message-----</font> <br>
<font size=2>&gt; From: Tony Przygienda [<a href="mailto:prz@redback.com">mailto:prz@redback.com</a>]</font> <br>
<font size=2>&gt; Sent: Tuesday, December 04, 2001 4:35 PM</font> <br>
<font size=2>&gt; To: Rajesh Saluja</font> <br>
<font size=2>&gt; Cc: Philip Christian; 'isis-wg@spider.juniper.net'; </font><br>
<font size=2>&gt; 'dkatz@juniper.net'</font> <br>
<font size=2>&gt; Subject: Re: [Isis-wg] Concerns with 3-way-handshake</font> <br>
<font size=2>&gt; </font><br>
<font size=2>&gt; </font><br>
<font size=2>&gt; Rajesh Saluja wrote:</font> <br>
<font size=2>&gt; </font><br>
<font size=2>&gt; &gt; &gt;</font> <br>
<font size=2>&gt; &gt; &gt;</font> <br>
<font size=2>&gt; &gt; &gt; &gt;From my vintage, yes, it should be fixed, maybe as </font><br>
<font size=2>&gt; simply as saying that</font> <br>
<font size=2>&gt; &gt; &gt; three-way-hello capable routers drop ISHs and do not send </font><br>
<font size=2>&gt; them ?&nbsp; The</font> <br>
<font size=2>&gt; &gt; &gt; very details of 1195 slip my mind right now but that </font><br>
<font size=2>&gt; should not cause</font> <br>
<font size=2>&gt; &gt; &gt; any backwards capability problems?</font> <br>
<font size=2>&gt; &gt; &gt;</font> <br>
<font size=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; something is definitely worth an addition to the </font><br>
<font size=2>&gt; 3-way-hello draft</font> <br>
<font size=2>&gt; &gt; &gt;</font> <br>
<font size=2>&gt; &gt; &gt;&nbsp;&nbsp;&nbsp;&nbsp; -- tony</font> <br>
<font size=2>&gt; &gt;</font> <br>
<font size=2>&gt; &gt; I agree with Philip's concerns. Will the following modifications be</font> <br>
<font size=2>&gt; &gt; acceptable to the group:</font> <br>
<font size=2>&gt; &gt; 1. As Tony suggested, say that&nbsp; three-way-hello capable </font><br>
<font size=2>&gt; routers drop ISHs</font> <br>
<font size=2>&gt; &gt; and do not send them.</font> <br>
<font size=2>&gt; </font><br>
<font size=2>&gt; you better be very carefull with the MUST and MAYs when </font><br>
<font size=2>&gt; writing this. As well,</font> <br>
<font size=2>&gt; someone thinks carefully whether it won't break more than it </font><br>
<font size=2>&gt; fixes (although</font> <br>
<font size=2>&gt; deployment with dropped ISHs seems to prove that it works and </font><br>
<font size=2>&gt; since we will</font> <br>
<font size=2>&gt;&nbsp; be able to chhose whether we send/receive them, we can force </font><br>
<font size=2>&gt; pretty much</font> <br>
<font size=2>&gt; this situation with the draft).</font> <br>
<font size=2>&gt; </font><br>
<font size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; thanks</font> <br>
<font size=2>&gt; </font><br>
<font size=2>&gt;&nbsp;&nbsp;&nbsp;&nbsp; -- tonyt</font> <br>
<font size=2>&gt; </font><br>
<font size=2>&gt; _______________________________________________</font> <br>
<font size=2>&gt; Isis-wg mailing list&nbsp; -&nbsp; Isis-wg@external.juniper.net</font> <br>
<font size=2>&gt; <a href="http://external.juniper.net/mailman/listinfo/isis-wg">http://external.juniper.net/mailman/listinfo/isis-wg</a></font> <br>
<font size=2>&gt; </font><br>
<font size=2>_______________________________________________</font> <br>
<font size=2>Isis-wg mailing list&nbsp; -&nbsp; Isis-wg@external.juniper.net</font> <br>
<font size=2><a href="http://external.juniper.net/mailman/listinfo/isis-wg">http://external.juniper.net/mailman/listinfo/isis-wg</a></font> </blockquote></html>

--=====================_4939202==_.ALT--

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 16:18:08 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA12644
	for <isis-archive@odin.ietf.org>; Wed, 5 Dec 2001 16:18:07 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA25215;
	Wed, 5 Dec 2001 13:36:56 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA25203
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 13:35:47 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id NAA25323;
	Wed, 5 Dec 2001 13:12:40 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <Y2HL8YY7>; Wed, 5 Dec 2001 13:12:40 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F62A@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Philip Christian'" <christi@nortelnetworks.com>,
        Les  Ginsberg
	 <ginsberg@pluris.com>,
        "'Tony Przygienda'" <prz@redback.com>,
        Rajesh Saluja <rsaluja@nortelnetworks.com>
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17DD1.91E14120"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 5 Dec 2001 13:12:39 -0800

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17DD1.91E14120
Content-Type: text/plain;
	charset="iso-8859-1"

All of this is very unnecessary. Let's go back to the beginning. The
original problem that Philip stated was:
 
>A is connected to B and issues an ISH. 
>B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising". 
>B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising". 
>A receives this and according to the table in the draft, brings the
adjacency "up". 
>However B may never have received an IIH from A and so the three way
handshake has been short circuited
 
Pretend the 3 way handshake was never invented - so we run according to the
original rules in ISO 10589. For clarity I will refer to the 2001 draft
because it includes wording that was corrected based on Technical
Corrigendum 1. No fundamental change in procedure from the 1992 version was
made - just a clearer presentation. What happens?
 
A is connected to B and issues an ISH. 
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising". 
B now sends an IIH to A
A receives the IIH and according to Table 5,6,7, or 8 (whichever applies)
brings the adjacency up
Note that at this time B has yet to receive an IIH from A (A presumably will
soon send one soon)
 
This demonstrates that this behavior involves no interaction between ISHs
and 3-way handshake.
 
Now enter the 3-way handshake era. The 3-way draft makes changes in the
adjacency state table logic so as to be able to detect neighbor state
changes even when run over unreliable link layers. It says nothing about the
use/non-use of ISHs because it is not concerned with that - quite correctly.
So, using the same scenario, what happens? 
 
There are a number of cases here depending on what form the 3-way TLV takes:
 
      Type = 0xF0 (decimal 240)
          Length = 5 to 17 octets
          Value:
            Adjacency State (one octet):
              0 = Up
              1 = Initializing
              2 = Down
            Extended Local Circuit ID (four octets)
            Neighbor System ID if known (zero to eight octets)
            Neighbor Extended Local Circuit ID (four octets, if Neighbor
              System ID is present)

As has been noted, there is a legacy version of the 3-way TLV - still in
widespread use - which sends only adjacency state (Length = 1). This is not
discussed in the current draft and should be. Anyway, we have three cases to
consider depending on what has been sent in the 3 way TLV when B sends its
first IIH:
 
Case 1)Adjacency state only (length = 1)
 
In this legacy 3-way case, B will never send neighbor system ID/circuit ID
so A cannot know whether B has received an IIH from A yet or not - and can
never know. So it must bring the adjacency up. Note that this behavior is no
different from that which happens in the total absence of the 3-way TLV.
Basically, this form of the 3-way handshake hasn't helped in this scenario.
(Part of the reason the later form was defined I assume.)
 
Case 2)Adjacency state + Extended Local Circuit ID (length = 5)
 
In this case A should assume that B has not yet received an IIH from A -
otherwise B would have inserted the neighbor system ID/circuit id. A should
only record B's advertised info (system ID/circuit ID) for use in its own
IIH but not make any adjacency state change. 
 
The draft is incorrect in this case because it says if the neighbor system
ID/circuit ID are "not present" the implementation should go ahead and
follow the state change table anyway. This wording needs to be corrected to
read something like:
 
    "If the option is present, the Neighbor System ID and Neighbor
     Extended Local Circuit ID fields, if present, shall be examined.
     If they are present, and the system ID contained therein does not
     match the local system's ID, or the extended circuit ID does not
     match the local system's extended circuit ID, the PDU shall be
     discarded and no further action is taken. 
 
     If they are NOT present, but the Extended Local Circuit ID is present
     then the PDU shall be discarded and no further action taken.
 
     If the Neighbor System ID and Neighbor Extended Local Circuit ID
     fields match those of the local system, or are not present and the 
     Extended Local Circuit ID is not present, the
     procedures described in section 8.2.4.2 are followed with following
     changes:"
 
 
Case 3)Adjacency state + Extended Local Circuit ID + neighbor system +
Neighbor extended local circuit ID (length = 17)
 
Presumably, if B chose to include neighbor system ID and neighbor circuit ID
before it had received an IIH from A, it would use values which are
guaranteed to not match A's local values. In my previous mail I suggested
using a system ID of all 0's, which is probably fairly safe, but a better
choice would be for B to place it's own system ID there. Since there can be
no duplicate system IDs this should never match A's local ID and therefore
the check would fail and therefore no adjacency state change would occur.
 
I believe changing the draft to include wording described in Case 2 above
solves the problem. There should also be some discussion of what the legacy
version (adjacency state only) does - that text has fallen into the black
hole of expired drafts.
 
Now, the issue of whether sending ISHs should be optional is something that
needs to be addressed - thus far this "violation" of the spec has been
supported by liberal implementations on the receiver side - but should be
agreed upon and defined in a draft. But that issue is distinct and unrelated
to the operation of the 3-way handshake. There is no reason to confuse the
two.
 
   Les
 
 

 Message-----
From: Philip Christian [mailto:christi@nortelnetworks.com]
Sent: Wednesday, December 05, 2001 2:51 AM
To: 'Les Ginsberg'; 'Tony Przygienda'; Rajesh Saluja
Cc: 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net'
Subject: RE: [Isis-wg] Concerns with 3-way-handshake



I (and a colleague, credit where it's due) can think of a couple of ways to
solve this problem. 
First we could add an explicit statement such as 

"Sending and receiving ISHs is required by Intermediate Systems that can
route CLNP packets. Intermediate Systems that cannot route CLNP may or may
not send and receive ISHs."

Now here are the two ideas 

1. 
On Intermediate Systems where receipt of an ISH causes an adjacency to start
in the "initialise" state, and which support the "Point-to-Point Adjacency
State" option, such an adjacency will be reported in the option as being
Adjacency State "Down". Once an IIH has been received then the state of the
adjacency shall be reported in the option as normal.

or 

2. 
On Intermediate Systems where receipt of an ISH caused an adjacency to start
in the "initialise" state, and which support the "Point-to-Point Adjacency
State" option, such an adjacency will be reported in the option as being
Adjacency State 3 = "ISH_init" (for example). Intermediate Systems that do
not send and receive ISHs are not required to implement reporting of this
state, as they will neither send it, nor cause a neighbour to send it back
to them. We then have to mess with the table a little, basically saying that
if you support ISHs and receive an "ISH_init" then you go to "Initialise"
(rather than "up", which was the problem).

I think that both of these ideas allow routers that support CLNP forwarding
to also use the 3-way-handshake, without upsetting anyone who has already
stopped using ISHs on their pure IP implementations.

I prefer idea "2", as "1" feels like the IS is misreporting the state, and
just doesn't appeal to my sense of correctness so well.

The problem with "2" is that if you send an ISH to an IS, then you can
expect it to send back this new Adjacency State = 3 ="ISH_init" message
back. Now it seems to me that if someone just dumps incoming ISHs then they
shouldn't be trasmitting them either, but if someone HAS implemented that,
then they are going to get "3=ISH_init"s coming back at them and won't know
what to do with them (maybe that doesn't matter anyway, as long as they
don't bring the adjacency up).

Comments? other ideas? 

Philip Christian 

 


------_=_NextPart_001_01C17DD1.91E14120
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Isis-wg] Concerns with 3-way-handshake</TITLE>

<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>All of 
this is very unnecessary. Let's go back to the beginning. The original problem 
that Philip stated was:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><SPAN class=726221820-05122001>
<DIV><SPAN class=383521320-04122001><FONT color=#0000ff face=Arial size=2>&gt;A 
is connected to B and issues an ISH.&nbsp;<BR><SPAN 
class=383521320-04122001></SPAN>&gt;B receives the ISH, and according to ISO 
10589 section 8.2.2 creates an adjacency of type "Initialising".&nbsp;<BR><SPAN 
class=383521320-04122001></SPAN>&gt;B now reports to A in the new "Point to 
point adjacency state" option that the adjacency is 
"Initialising".&nbsp;<BR><SPAN class=383521320-04122001></SPAN>&gt;A receives 
this and according to the table in the draft, brings the adjacency 
"up".&nbsp;<BR><SPAN class=383521320-04122001></SPAN>&gt;However B may never 
have received an IIH from A and so the three way handshake has been short 
circuited</FONT></SPAN></DIV>
<DIV><SPAN class=383521320-04122001></SPAN>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>Pretend the 3 way handshake was never invented - so we 
run according to the original rules in ISO 10589. For clarity I will&nbsp;refer 
to the 2001 draft because it includes wording that was corrected based on 
Technical Corrigendum 1. No fundamental change in procedure from the 1992 
version was made - just a clearer presentation.</SPAN></FONT><FONT color=#0000ff 
face=Arial size=2><SPAN class=726221820-05122001>&nbsp;What 
happens?</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001><SPAN 
class=383521320-04122001><FONT color=#0000ff face=Arial size=2>A is connected to 
B and issues an ISH.&nbsp;<BR>B receives the ISH, and according to ISO 10589 
section 8.2.2 creates an adjacency of type "Initialising".&nbsp;<BR>B now sends 
an IIH to A</FONT></SPAN></SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001><SPAN 
class=383521320-04122001><FONT color=#0000ff face=Arial size=2>A receives the 
IIH and according to Table 5,6,7, or 8 (whichever applies) brings the adjacency 
up</FONT></SPAN></SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001><SPAN 
class=383521320-04122001><FONT color=#0000ff face=Arial size=2>Note that at this 
time B has yet to receive an IIH from A (A presumably will soon send one 
soon)</FONT></SPAN></SPAN></FONT></DIV>
<DIV><SPAN class=383521320-04122001></SPAN><FONT color=#0000ff face=Arial 
size=2></FONT>&nbsp;</DIV>
<DIV><SPAN class=726221820-05122001></SPAN><FONT size=2><FONT 
color=#0000ff><FONT face=Arial>T<SPAN class=726221820-05122001>his 
demonst</SPAN></FONT></FONT><SPAN class=726221820-05122001><FONT color=#0000ff 
face=Arial>rates that this behavior</FONT></SPAN></FONT>&nbsp;<FONT 
color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>involves no 
interaction between ISHs and 3-way handshake.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>Now 
enter the 3-way handshake era. The 3-way draft makes changes in the adjacency 
state table logic so as to be able to detect neighbor state changes even when 
run over unreliable link layers. It says nothing about the use/non-use of ISHs 
because it is not concerned with that - quite correctly. So, using the same 
scenario, what happens? </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>There 
are a number of cases here depending on what form the 3-way TLV 
takes:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Type = 0xF0 (decimal 
240)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Length = 5 to 17 
octets<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Value:<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Adjacency State (one 
octet):<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
0 = 
Up<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
1 = 
Initializing<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
2 = Down<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Extended Local Circuit ID (four 
octets)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Neighbor System ID if known (zero to eight 
octets)<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
Neighbor Extended Local Circuit ID (four octets, if 
Neighbor<BR>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 
System ID is present)<BR></SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>As has 
been noted, there is a legacy version of the 3-way TLV - still in widespread use 
- which sends only adjacency state (Length = 1). This is not discussed in the 
current draft and should be. Anyway, we have three cases to consider depending 
on what has been sent in the 3 way TLV when B sends its first 
IIH:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>Case 
1)Adjacency state only (length = 1)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>In 
this legacy 3-way case, B will never send neighbor system ID/circuit ID so A 
cannot know whether B has received an IIH from A yet or not - and can never 
know. So it must bring the adjacency up. Note that this behavior is no different 
from that which happens in the total absence of the 3-way TLV. Basically, this 
form of the  3-way handshake hasn't helped in this scenario. (Part of the reason 
the later form was defined I assume.)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>Case 
2)Adjacency state + Extended Local Circuit ID (length = 5)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>In 
this case A should assume that B has not yet received an IIH from A - otherwise 
B would have inserted the neighbor system ID/circuit id. A should only record 
B's advertised info (system ID/circuit ID) for use in its own IIH but not make 
any adjacency state change. </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>The 
draft is incorrect in this case because it says if the neighbor system 
ID/circuit ID are "not present" the implementation should go ahead and follow 
the state change table anyway. This wording needs to be corrected to read 
something like:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>&nbsp;&nbsp;&nbsp; "If the option is present, the 
Neighbor System ID and Neighbor<BR>&nbsp;&nbsp;&nbsp;&nbsp; Extended Local 
Circuit ID fields, if present, shall be examined.<BR>&nbsp;&nbsp;&nbsp;&nbsp; If 
they are present, and the system ID contained therein does 
not<BR>&nbsp;&nbsp;&nbsp;&nbsp; match the local system's ID, or the extended 
circuit ID does not<BR>&nbsp;&nbsp;&nbsp;&nbsp; match the local system's 
extended circuit ID, the PDU shall be<BR>&nbsp;&nbsp;&nbsp;&nbsp; discarded and 
no further action is taken. </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>&nbsp;&nbsp;&nbsp;&nbsp; If they are NOT present, but 
the Extended Local Circuit ID is present</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>&nbsp;&nbsp;&nbsp;&nbsp; then the PDU shall be 
discarded and no further action taken.</SPAN></FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>&nbsp;&nbsp;&nbsp;&nbsp; If the Neighbor System ID and 
Neighbor Extended Local Circuit ID<BR>&nbsp;&nbsp;&nbsp;&nbsp; fields match 
those of the local system, or are not present and the </SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>&nbsp;&nbsp;&nbsp;&nbsp; Extended Local Circuit ID is 
not present, the<BR>&nbsp;&nbsp;&nbsp;&nbsp; procedures described in section 
8.2.4.2 are followed with following<BR>&nbsp;&nbsp;&nbsp;&nbsp; 
changes:"</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>Case 
3)Adjacency state + Extended Local Circuit ID + neighbor system + Neighbor 
extended local circuit ID (length = 17)</SPAN></FONT></DIV>
<DIV><SPAN class=726221820-05122001>&nbsp;</DIV></SPAN>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>Presumably, if B chose to include neighbor system ID 
and neighbor circuit ID before it had received an IIH from A, it would use 
values which are guaranteed to not match A's local values. In my previous mail I 
suggested using a system ID of all 0's, which is probably fairly safe, but a 
better choice would be for B to place it's own system ID there. Since there can 
be no duplicate system IDs this should never match A's local ID and therefore 
the check would fail and therefore no adjacency state change would 
occur.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>I 
believe changing the draft to include wording described in Case 2 above solves 
the problem. There should also be some discussion of what the legacy version 
(adjacency state only) does - that text has fallen into the black hole of 
expired drafts.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=726221820-05122001>Now, 
the issue of whether sending ISHs should be optional is something that needs to 
be addressed - thus far this "violation" of the spec has been supported by 
liberal implementations on the receiver side - but should be agreed upon and 
defined in a draft. But that issue is distinct and unrelated to the operation of 
the 3-way handshake. There is no reason to confuse the two.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001>&nbsp;&nbsp; Les</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=726221820-05122001></SPAN></FONT></SPAN>&nbsp;</DIV></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px">
  <DIV align=left class=OutlookMessageHeader dir=ltr><FONT face=Tahoma 
  size=2>&nbsp;Message-----<BR><B>From:</B> Philip Christian 
  [mailto:christi@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, December 05, 
  2001 2:51 AM<BR><B>To:</B> 'Les Ginsberg'; 'Tony Przygienda'; Rajesh 
  Saluja<BR><B>Cc:</B> 'isis-wg@spider.juniper.net'; 
  'dkatz@juniper.net'<BR><B>Subject:</B> RE: [Isis-wg] Concerns with 
  3-way-handshake<BR><BR></DIV></FONT>
  <P><FONT size=2>I (and a colleague, credit where it's due) can think of a 
  couple of ways to solve this problem.</FONT> <BR><FONT size=2>First we could 
  add an explicit statement such as</FONT> </P>
  <P><FONT size=2>"Sending and receiving ISHs is required by Intermediate 
  Systems that can route CLNP packets. Intermediate Systems that cannot route 
  CLNP may or may not send and receive ISHs."</FONT></P>
  <P><FONT size=2>Now here are the two ideas</FONT> </P>
  <P><FONT size=2>1.</FONT> <BR><FONT size=2>On Intermediate Systems where 
  receipt of an ISH causes an adjacency to start in the "initialise" state, and 
  which support the "Point-to-Point Adjacency State" option, such an adjacency 
  will be reported in the option as being Adjacency State "Down". Once an IIH 
  has been received then the state of the adjacency shall be reported in the 
  option as normal.</FONT></P>
  <P><FONT size=2>or</FONT> </P>
  <P><FONT size=2>2.</FONT> <BR><FONT size=2>On Intermediate Systems where 
  receipt of an ISH caused an adjacency to start in the "initialise" state, and 
  which support the "Point-to-Point Adjacency State" option, such an adjacency 
  will be reported in the option as being Adjacency State 3 = "ISH_init" (for 
  example). Intermediate Systems that do not send and receive ISHs are not 
  required to implement reporting of this state, as they will neither send it, 
  nor cause a neighbour to send it back to them. We then have to mess with the 
  table a little, basically saying that if you support ISHs and receive an 
  "ISH_init" then you go to "Initialise" (rather than "up", which was the 
  problem).</FONT></P>
  <P><FONT size=2>I think that both of these ideas allow routers that support 
  CLNP forwarding to also use the 3-way-handshake, without upsetting anyone who 
  has already stopped using ISHs on their pure IP implementations.</FONT></P>
  <P><FONT size=2>I prefer idea "2", as "1" feels like the IS is misreporting 
  the state, and just doesn't appeal to my sense of correctness so 
  well.</FONT></P>
  <P><FONT size=2>The problem with "2" is that if you send an ISH to an IS, then 
  you can expect it to send back this new Adjacency State = 3 ="ISH_init" 
  message back. Now it seems to me that if someone just dumps incoming ISHs then 
  they shouldn't be trasmitting them either, but if someone HAS implemented 
  that, then they are going to get "3=ISH_init"s coming back at them and won't 
  know what to do with them (maybe that doesn't matter anyway, as long as they 
  don't bring the adjacency up).</FONT></P>
  <P><FONT size=2>Comments? other ideas?</FONT> </P>
  <P><FONT size=2>Philip Christian</FONT> </P>
  <P>&nbsp;</P></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C17DD1.91E14120--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 16:57:50 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA14819
	for <isis-archive@odin.ietf.org>; Wed, 5 Dec 2001 16:57:49 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA25433;
	Wed, 5 Dec 2001 14:17:55 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [209.140.237.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA25421
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 14:16:25 -0800 (PST)
Received: from alpha-tli.procket.com (IDENT:root@alpha-tli.procket.com [10.2.3.1])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id fB5LsRes004936;
	Wed, 5 Dec 2001 13:54:27 -0800 (PST)
Received: (from tli@localhost)
	by alpha-tli.procket.com (8.12.1/8.12.1) id fB5LsR63007068;
	Wed, 5 Dec 2001 13:54:27 -0800
From: Tony Li <tli@Procket.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15374.38803.435266.953078@alpha-tli.procket.com>
To: "perumal  conf" <perconf@rediffmail.com>
Cc: isis-wg@spider.juniper.net
Subject: [Isis-wg] IS-IS commands - Need info
In-Reply-To: <20011205140824.23091.qmail@mailFA9.rediffmail.com>
References: <20011205140824.23091.qmail@mailFA9.rediffmail.com>
X-Mailer: VM 6.92 under Emacs 20.5.1
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 5 Dec 2001 13:54:27 -0800
Content-Transfer-Encoding: 7bit


 |    I am unable to get the description and usage of "external overload
 |    signalling" IS-IS command.  Any information about this would be
 |    helpful to me.
 | 
 | Thanks in advance for your response


Please consult your vendor for questions about their products.  

This mailing list is for the IETF IS-IS Working Group and is not a
technical support resource.

Thank you,
Tony Li
IS-IS WG co-chair
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 17:11:13 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA15640
	for <isis-archive@odin.ietf.org>; Wed, 5 Dec 2001 17:11:12 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA25528;
	Wed, 5 Dec 2001 14:31:01 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA25503
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 14:29:33 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fB5M7o242287
	for <isis-wg@juniper.net>; Wed, 5 Dec 2001 14:07:50 -0800 (PST)
X-JNPR-Received-From: outside
Received: from prattle.redback.com ([155.53.12.9]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Wed, 5 Dec 2001 14:03:07 -0800
Received: from redback.com (dhcp-35-94.redback.com [155.53.35.94])
	by prattle.redback.com (Postfix) with ESMTP
	id 3240AF2C55; Wed,  5 Dec 2001 14:04:40 -0800 (PST)
Message-ID: <3C0E86F1.66854ABC@redback.com>
From: Tony Przygienda <prz@redback.com>
X-Mailer: Mozilla 4.61 [en] (X11; I; NetBSD 1.4.1 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: drafts@ietf.org
Cc: isis-wg@juniper.net
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 05 Dec 2001 22:03:08.0140 (UTC) FILETIME=[9F4212C0:01C17DD8]
Subject: [Isis-wg] pls update this draft ...
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 05 Dec 2001 12:43:29 -0800
Content-Transfer-Encoding: 7bit

Internet Engineering Task Force                               T.
Przygienda
INTERNET DRAFT                                                     Nov
2001

                       Reserved TLV Codepoints in ISIS
                 <draft-ietf-isis-wg-tlv-codepoints-02.txt>



Status of This Memo

    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026.  Internet-Drafts are
working
    documents of the Internet Engineering Task Force (IETF), its areas,
    and its working groups.  Note that other groups may also distribute
    working documents as Internet-Drafts.

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

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

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

    Copyright Notice Copyright (C) The Internet Society (2000).  All
    Rights Reserved.



Abstract

    This draft describes implementation codepoints within
    IS-IS [ISO90 , Cal90a , Cal90b ] used today by several ISPs for
    routing within their clouds.  IS-IS is an interior gateway routing
    protocol developed originally by OSI and used with IP extensions as
    IGP. This draft summarizes all TLV codepoints that are being used by

    the protocol and its pending extensions.


Przygienda                     Expires May 2002
[Page 1]

Internet Draft                    TLV Codepoints
Nov 2001

1.  TLV Codepoints reserved

________________________________________________________________________

     Name                 Value   IIH   LSP  SNP   Status


________________________________________________________________________

     Area Addresses            1  y     y    n  ISO 10589
     IIS Neighbors             2  n     y    n  ISO 10589
     ES Neighbors              3  n     y    n  ISO 10589
     Part. DIS                 4  n     y    n  ISO 10589
     Prefix Neighbors          5  n     y    n  ISO 10589
     IIS Neighbors             6  y     n    n  ISO 10589
     Padding                   8  y     n    n  ISO 10589
     LSP Entries               9  n     n    y  ISO 10589
     Authentication           10  y     y    y  ISO 10589
     Opt. Checksum            12  y     n    y  IETF-draft
     LSPBufferSize            14  n     y    n  ISO 10589 Rev 2 Draft
     TE IIS Neigh.            22  n     y    n  IETF-draft
     DECnet Phase IV          42  y     n    n  DEC (ancient)
     IP Int. Reach           128  n     y    n  RFC 1195
     Prot. Supported         129  y     y    n  RFC 1195
     IP Ext. Address         130  n     y    n  RFC 1195
     IDRPI                   131  n     y    y  RFC 1195
     IP Intf. Address        132  y     y    n  RFC 1195
     Illegal                 133  n     n    n  RFC 1195 (not used)
     Router ID               134  n     y    n  IETF-draft
     TE IP. Reach            135  n     y    n  IETF-draft
     Dynamic Name            137  n     y    n  RFC 2763
     Nortel Proprietary      176  n     y    n
     Nortel Proprietary      177  n     y    n
     Restart TLV             211  y     n    n  IETF-draft
     MT-ISN                  222  n     y    n  IETF-draft
     M-Topologies            229  y     y    n  IETF-draft
     IPv6 Intf. Addr.        232  y     y    n  IETF-draft
     MT IP. Reach            235  n     y    n  IETF-draft
     IPv6 IP. Reach          236  n     y    n  IETF-draft
     MT IPv6 IP. Reach       237  n     y    n  IETF-draft
     P2P Adjacency State     240  y     n    n  IETF-draft

Przygienda                     Expires May 2002
[Page 2]

Internet Draft                    TLV Codepoints
Nov 2001

2.  Assignment Procedures

    This document is provided to avoid possible future conflicts in
    assignment of TLV numbers.  It does not constitute or represent any
    standard or authority assigning TLV numbers.  TLV assignment happens

    on a shared, informational basis between the ISO, SIF and the IETF
    working groups.  The core ISIS protocol is being specified in the
    ISO standards body, IP extensions to it however are products of the
    ISIS working group in IETF. Since ISO does not provide a numbering
    authority and IANA is only responsible for IP related coding points,

    no plausible central authority to assign TLV numbers exists as of
    today.

    This document will be periodically updated by never versions in the
    fashion of [RP94 ] and successors.

    This document will not indicate specific drafts using the
codepoints,
    nor will it resolve the sub-TLV codepoints.

3.  Acknowledgments

    Thanks to Les Ginsberg and others for pointing out details and
    improving this work.

4.  Security Consideration

    ISIS security applies to the work presented.  No specific security
    issues are being introduced.

References

    [Cal90a]  R. Callon.  OSI ISIS Intradomain Routing Protocol.
              INTERNET-RFC, Internet Engineering Task Force, February
              1990.


    [Cal90b]  R. Callon.  Use of OSI ISIS for Routing in TCP/IP and Dual

              Environments.  INTERNET-RFC, Internet Engineering Task
              Force, December 1990.


    [ISO90]   ISO.  Information Technology - Telecommunications and
              Information Exchange between Systems - Intermediate System

              to Intermediate System Routing Exchange Protocol for
              Use in Conjunction with the Protocol for Providing the
              Connectionless-Mode Network Service.  ISO, 1990.


    [RP94]    J. Reynolds and J. Postel.  Rfc 1700, Assigned Numbers.
              Internet Engineering Task Force, October 1994.



Przygienda                     Expires May 2002
[Page 3]

Internet Draft                    TLV Codepoints
Nov 2001

5.  Authors' Addresses

     Tony Przygienda
     Redback Networks
     350 Holger Way
     San Jose, CA, 95134-1362
     prz@redback.com



6.   Full Copyright Statement

    Copyright (C) The Internet Society (1997).  All Rights Reserved.

    This document and translations of it may be copied and furnished to
    others, and derivative works that comment on or otherwise explain it

    or assist in its implementation may be prepared, copied, published
    and distributed, in whole or in part, without restriction of any
    kind, provided that the above copyright notice and this paragraph
    are included on all such copies and derivative works.  However,
    this document itself may not be modified in any way, such as by
    removing the copyright notice or references to the Internet Society
    or other Internet organizations, except as needed for the purpose
    of developing Internet standards in which case the procedures
    for copyrights defined in the Internet Standards process must be
    followed, or as required to translate it into languages other than
    English.

    The limited permissions granted above are perpetual and will not be
    revoked by the Internet Society or its successors or assigns.

    This document and the information contained herein is provided on an

    "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
    TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
    BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
    HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
    MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE."



Przygienda                     Expires May 2002
[Page 4]




_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec  5 18:51:02 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21562
	for <isis-archive@lists.ietf.org>; Wed, 5 Dec 2001 18:51:02 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA26015;
	Wed, 5 Dec 2001 16:10:56 -0800 (PST)
Received: from tahoe.allegronetworks.com (tahoe.allegronetworks.com [63.115.58.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA26000
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 16:09:05 -0800 (PST)
Received: by tahoe.allegronetworks.com with Internet Mail Service (5.5.2653.19)
	id <YCX6A47G>; Wed, 5 Dec 2001 15:47:02 -0800
Message-ID: <B4DFCB7CDE2DD4118F690008C78694160115D9A3@tahoe.allegronetworks.com>
From: Neal Castagnoli <cast@allegronetworks.com>
To: "'Les  Ginsberg'" <ginsberg@pluris.com>,
        "'Philip Christian'"
	 <christi@nortelnetworks.com>,
        "'Tony Przygienda'" <prz@redback.com>,
        Rajesh Saluja <rsaluja@nortelnetworks.com>
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 5 Dec 2001 15:46:55 -0800


Should an ISH effect adjacency state?

The purpose of sending an ISH to an end system is to indicate the
availability of the router, and to a router to cause it to start the
router-to-router hello protocol (WANs only).  ISHs convey neighbor type,
address, and availability.

Routers send IIHs to convey router to router adjacency information.

Having ISH's set adjacency state mixes functions and gets in the way of the
IIH protocol managing the adjacency state.

To prevent ISHs from setting adjacency state, add a sentence to section 3.2
of the 3-way draft that reads something like:

	In section 8.2.2 replace each instance of "Initialising" with
"Down".

  --Neal



-----Original Message-----
From: Les Ginsberg [mailto:ginsberg@pluris.com]
Sent: Wednesday, December 05, 2001 1:13 PM
To: 'Philip Christian'; Les Ginsberg; 'Tony Przygienda'; Rajesh Saluja
Cc: 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net'
Subject: RE: [Isis-wg] Concerns with 3-way-handshake


All of this is very unnecessary. Let's go back to the beginning. The
original problem that Philip stated was:

>A is connected to B and issues an ISH. 
>B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising". 
>B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising". 
>A receives this and according to the table in the draft, brings the
adjacency "up". 
>However B may never have received an IIH from A and so the three way
handshake has been short circuited

Pretend the 3 way handshake was never invented - so we run according to the
original rules in ISO 10589. For clarity I will refer to the 2001 draft
because it includes wording that was corrected based on Technical
Corrigendum 1. No fundamental change in procedure from the 1992 version was
made - just a clearer presentation. What happens?

A is connected to B and issues an ISH. 
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising". 
B now sends an IIH to A
A receives the IIH and according to Table 5,6,7, or 8 (whichever applies)
brings the adjacency up
Note that at this time B has yet to receive an IIH from A (A presumably will
soon send one soon)

This demonstrates that this behavior involves no interaction between ISHs
and 3-way handshake.

Now enter the 3-way handshake era. The 3-way draft makes changes in the
adjacency state table logic so as to be able to detect neighbor state
changes even when run over unreliable link layers. It says nothing about the
use/non-use of ISHs because it is not concerned with that - quite correctly.
So, using the same scenario, what happens? 

There are a number of cases here depending on what form the 3-way TLV takes:

      Type = 0xF0 (decimal 240)
          Length = 5 to 17 octets
          Value:
            Adjacency State (one octet):
              0 = Up
              1 = Initializing
              2 = Down
            Extended Local Circuit ID (four octets)
            Neighbor System ID if known (zero to eight octets)
            Neighbor Extended Local Circuit ID (four octets, if Neighbor
              System ID is present)

As has been noted, there is a legacy version of the 3-way TLV - still in
widespread use - which sends only adjacency state (Length = 1). This is not
discussed in the current draft and should be. Anyway, we have three cases to
consider depending on what has been sent in the 3 way TLV when B sends its
first IIH:

Case 1)Adjacency state only (length = 1)

In this legacy 3-way case, B will never send neighbor system ID/circuit ID
so A cannot know whether B has received an IIH from A yet or not - and can
never know. So it must bring the adjacency up. Note that this behavior is no
different from that which happens in the total absence of the 3-way TLV.
Basically, this form of the 3-way handshake hasn't helped in this scenario.
(Part of the reason the later form was defined I assume.)

Case 2)Adjacency state + Extended Local Circuit ID (length = 5)

In this case A should assume that B has not yet received an IIH from A -
otherwise B would have inserted the neighbor system ID/circuit id. A should
only record B's advertised info (system ID/circuit ID) for use in its own
IIH but not make any adjacency state change. 

The draft is incorrect in this case because it says if the neighbor system
ID/circuit ID are "not present" the implementation should go ahead and
follow the state change table anyway. This wording needs to be corrected to
read something like:

    "If the option is present, the Neighbor System ID and Neighbor
     Extended Local Circuit ID fields, if present, shall be examined.
     If they are present, and the system ID contained therein does not
     match the local system's ID, or the extended circuit ID does not
     match the local system's extended circuit ID, the PDU shall be
     discarded and no further action is taken. 

     If they are NOT present, but the Extended Local Circuit ID is present
     then the PDU shall be discarded and no further action taken.

     If the Neighbor System ID and Neighbor Extended Local Circuit ID
     fields match those of the local system, or are not present and the 
     Extended Local Circuit ID is not present, the
     procedures described in section 8.2.4.2 are followed with following
     changes:"


Case 3)Adjacency state + Extended Local Circuit ID + neighbor system +
Neighbor extended local circuit ID (length = 17)

Presumably, if B chose to include neighbor system ID and neighbor circuit ID
before it had received an IIH from A, it would use values which are
guaranteed to not match A's local values. In my previous mail I suggested
using a system ID of all 0's, which is probably fairly safe, but a better
choice would be for B to place it's own system ID there. Since there can be
no duplicate system IDs this should never match A's local ID and therefore
the check would fail and therefore no adjacency state change would occur.

I believe changing the draft to include wording described in Case 2 above
solves the problem. There should also be some discussion of what the legacy
version (adjacency state only) does - that text has fallen into the black
hole of expired drafts.

Now, the issue of whether sending ISHs should be optional is something that
needs to be addressed - thus far this "violation" of the spec has been
supported by liberal implementations on the receiver side - but should be
agreed upon and defined in a draft. But that issue is distinct and unrelated
to the operation of the 3-way handshake. There is no reason to confuse the
two.

   Les


 Message-----
From: Philip Christian [mailto:christi@nortelnetworks.com]
Sent: Wednesday, December 05, 2001 2:51 AM
To: 'Les Ginsberg'; 'Tony Przygienda'; Rajesh Saluja
Cc: 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net'
Subject: RE: [Isis-wg] Concerns with 3-way-handshake


I (and a colleague, credit where it's due) can think of a couple of ways to
solve this problem. 
First we could add an explicit statement such as 
"Sending and receiving ISHs is required by Intermediate Systems that can
route CLNP packets. Intermediate Systems that cannot route CLNP may or may
not send and receive ISHs."
Now here are the two ideas 
1. 
On Intermediate Systems where receipt of an ISH causes an adjacency to start
in the "initialise" state, and which support the "Point-to-Point Adjacency
State" option, such an adjacency will be reported in the option as being
Adjacency State "Down". Once an IIH has been received then the state of the
adjacency shall be reported in the option as normal.
or 
2. 
On Intermediate Systems where receipt of an ISH caused an adjacency to start
in the "initialise" state, and which support the "Point-to-Point Adjacency
State" option, such an adjacency will be reported in the option as being
Adjacency State 3 = "ISH_init" (for example). Intermediate Systems that do
not send and receive ISHs are not required to implement reporting of this
state, as they will neither send it, nor cause a neighbour to send it back
to them. We then have to mess with the table a little, basically saying that
if you support ISHs and receive an "ISH_init" then you go to "Initialise"
(rather than "up", which was the problem).
I think that both of these ideas allow routers that support CLNP forwarding
to also use the 3-way-handshake, without upsetting anyone who has already
stopped using ISHs on their pure IP implementations.
I prefer idea "2", as "1" feels like the IS is misreporting the state, and
just doesn't appeal to my sense of correctness so well.
The problem with "2" is that if you send an ISH to an IS, then you can
expect it to send back this new Adjacency State = 3 ="ISH_init" message
back. Now it seems to me that if someone just dumps incoming ISHs then they
shouldn't be trasmitting them either, but if someone HAS implemented that,
then they are going to get "3=ISH_init"s coming back at them and won't know
what to do with them (maybe that doesn't matter anyway, as long as they
don't bring the adjacency up).
Comments? other ideas? 
Philip Christian 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec  6 00:41:37 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA01920
	for <isis-archive@lists.ietf.org>; Thu, 6 Dec 2001 00:41:36 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id WAA27443;
	Wed, 5 Dec 2001 22:00:57 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id VAA27425
	for <isis-wg@spider.juniper.net>; Wed, 5 Dec 2001 21:59:40 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id VAA22967;
	Wed, 5 Dec 2001 21:37:44 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <Y2HL85K9>; Wed, 5 Dec 2001 21:37:43 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F62D@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Rajesh Saluja'" <rsaluja@nortelnetworks.com>,
        Les  Ginsberg
	 <ginsberg@pluris.com>,
        Philip Christian <christi@nortelnetworks.com>,
        "'Tony Przygienda'" <prz@redback.com>
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17E18.1D890B40"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 5 Dec 2001 21:37:38 -0800

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17E18.1D890B40
Content-Type: text/plain;
	charset="iso-8859-1"

Rajesh -
 
You have reminded me that the adjacency states defined by the 3way draft and
sent in the 3 way TLV are not equivalent to the adjacency states defined in
10589. 10589 defines the following states:
 
   INITIALISING: Created on receipt of ISH (or IIH if you allow that)
   UP
   FAILED (Only used on DA circuits - let's ignore that)
   DOWN: A transient state because the adjacency is deleted immediately
after
 
3way defines:
 
   DOWN: Can mean no adjacency exists or the state associated with the
adjacency when an IIH is received and the action in Tables 5,6,7, or 8 from
10589 is UP
  INITIALISING: Reached after receiving an IIH when you are in down state
(as per table in 3way draft)
  UP
 
Conceptually it is necessary to maintain these two sets of adjacency states
because until you receive an IIH you do not know whether your neighbor
supports 3way or not. If your neighbor does not include the 3way TLV then
you follow the original 10589 rules, which means that you transition from
Initialising to UP when receiving an IIH.
 
If your neighbor does include the 3 way TLV, then after determining via
Tables 5,6,7,8 that the action is UP you must set local 3way state to DOWN
and then apply the 3way state table.
 
If you are initiating an IIH before you have received one, then you should
set the adjacency state field in the 3way TLV to down (NOT initialising),
whether you have received an ISH or not. The 3way state can only transition
to Initialising after receiving an IIH.
 
All of this makes me think that Philip's original premise is wrong (and
unfortunately much of the discussion, including much of my comments) is off
the mark. Philip said:
 
 >A is connected to B and issues an ISH. 
>B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising". 
>B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising". 

 
No - this is incorrect. B should report the 3way state as "Down" because it
has yet to receive an IIH.
 
>A receives this and according to the table in the draft, brings the
adjacency "up". 
 
Now A will, following the table in 3 way draft, change the adjacency to
Initialising.

>However B may never have received an IIH from A and so the three way
handshake has been short circuited
 
This no longer applies.
 
---------------------------
 
The textual correction that is needed in the 3 way draft is as follows:
 
   Add a clause e) to the end of Section 8.2.3:
 
   "Set the state to be reported in the Adjacency State field of the
Point-to-Point
   Adjacency State option to down."
 
(NOTE: This would be clause f) in the 10589:2001 draft)
 
The previous textual correction I suggested then is not needed. No further
change to ISH sending/processing is needed either. Whether we want to
standardize not sending ISHs is a separate issue which should be discussed
on a separate thread.
 
Sorry for heading down the wrong road previously.
 
   Les
 
 -----Original Message-----
From: Rajesh Saluja [mailto:rsaluja@nortelnetworks.com]
Sent: Wednesday, December 05, 2001 3:49 PM
To: 'Les Ginsberg'; Philip Christian; 'Tony Przygienda'
Cc: 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net'
Subject: RE: [Isis-wg] Concerns with 3-way-handshake



 


 
Case 2)Adjacency state + Extended Local Circuit ID (length = 5)
 
In this case A should assume that B has not yet received an IIH from A -
otherwise B would have inserted the neighbor system ID/circuit id. A should
only record B's advertised info (system ID/circuit ID) for use in its own
IIH but not make any adjacency state change. 
[Rajesh Saluja] 
Les,
If a router has not heard from its neighbor, the first IIH will always
contain just the extended local circuit id and then the adjacency goes from
down to initialising. If we do not make any adjacency change, we will
actually need one extra IIH to come to UP state. Also how does this help in
solving the original problem to interoperate with ISH?
 
Thanks,
Rajesh
 
 


------_=_NextPart_001_01C17E18.1D890B40
Content-Type: text/html;
	charset="iso-8859-1"

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>RE: [Isis-wg] Concerns with 3-way-handshake</TITLE>

<META content="MSHTML 5.00.2314.1000" name=GENERATOR></HEAD>
<BODY>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>Rajesh 
-</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>You 
have reminded me that the adjacency states defined by the 3way draft and sent in 
the 3 way TLV are not equivalent to the adjacency states defined in 10589. 10589 
defines the following states:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>&nbsp;&nbsp; INITIALISING: Created on receipt of ISH 
(or IIH if you allow that)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>&nbsp;&nbsp; UP</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>&nbsp;&nbsp; FAILED (Only used on DA circuits - let's 
ignore that)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>&nbsp;&nbsp; DOWN: A transient state because the 
adjacency is deleted immediately after</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>3way 
defines:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>&nbsp;&nbsp; DOWN: Can mean no adjacency exists or the 
state associated with the adjacency when an IIH is received and the action in 
Tables 5,6,7, or 8 from 10589 is UP</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>&nbsp; 
INITIALISING: Reached after receiving an IIH when you are in down state (as per 
table in 3way draft)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>&nbsp; 
UP</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>Conceptually it is necessary to maintain these two sets 
of adjacency states because until you receive an IIH you do not know whether 
your neighbor supports 3way or not. If your neighbor does not include the 3way 
TLV then you follow the original 10589 rules, which means that you transition 
from Initialising to UP when receiving an IIH.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>If 
your neighbor does include the 3 way TLV, then after determining via Tables 
5,6,7,8 that the action is UP you must set local 3way state to DOWN and then 
apply the 3way state table.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>If you 
are initiating an IIH before you have received one, then you should set the 
adjacency state field in the 3way TLV to down (NOT initialising), whether you 
have received an ISH or not. The 3way state can only transition to Initialising 
after receiving an IIH.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>All of 
this makes me think that Philip's original premise is wrong (and unfortunately 
much of the discussion, including much of my comments) is off the mark. Philip 
said:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><SPAN class=392080600-06122001><SPAN class=726221820-05122001><FONT 
face=Arial><FONT color=#0000ff><FONT size=2>&nbsp;<SPAN 
class=383521320-04122001></FONT></FONT></FONT><FONT color=#0000ff face=Arial 
size=2>&gt;A is connected to B and issues an ISH.&nbsp;<BR><SPAN 
class=383521320-04122001></SPAN>&gt;B receives the ISH, and according to ISO 
10589 section 8.2.2 creates an adjacency of type "Initialising".&nbsp;<BR><SPAN 
class=383521320-04122001></SPAN>&gt;B now reports to A in the new "Point to 
point adjacency state" option that the adjacency is 
"Initialising".&nbsp;<BR></FONT></DIV>
<DIV><SPAN class=383521320-04122001></SPAN>&nbsp;</DIV><FONT size=2><FONT 
color=#0000ff><FONT face=Arial>
<DIV><SPAN class=383521320-04122001><SPAN class=392080600-06122001>No - this is 
incorrect. B should report the 3way state as "Down" because it has yet to 
receive an IIH.</SPAN></SPAN></FONT></FONT></SPAN></FONT></SPAN></SPAN></DIV>
<DIV><SPAN class=392080600-06122001><SPAN class=726221820-05122001><SPAN 
class=383521320-04122001><FONT color=#0000ff face=Arial 
size=2></FONT></SPAN></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN class=392080600-06122001><SPAN class=726221820-05122001><SPAN 
class=383521320-04122001><FONT color=#0000ff face=Arial size=2>&gt;A receives 
this and according to the table in the draft, brings the adjacency 
"up".&nbsp;</FONT></SPAN></SPAN></SPAN></DIV>
<DIV><SPAN class=392080600-06122001><SPAN class=726221820-05122001><SPAN 
class=383521320-04122001><FONT color=#0000ff face=Arial 
size=2></FONT></SPAN></SPAN></SPAN>&nbsp;</DIV>
<DIV><SPAN class=392080600-06122001><SPAN class=726221820-05122001><SPAN 
class=383521320-04122001><FONT color=#0000ff face=Arial size=2>Now A will, 
following the table in 3 way draft, change the adjacency to 
Initialising.</FONT></SPAN></SPAN></SPAN></DIV>
<DIV><SPAN class=392080600-06122001><SPAN class=726221820-05122001><SPAN 
class=383521320-04122001><FONT color=#0000ff face=Arial size=2><BR><SPAN 
class=383521320-04122001></SPAN>&gt;However B may never have received an IIH 
from A and so the three way handshake has been short 
circuited</FONT></SPAN></DIV>
<DIV><SPAN class=383521320-04122001></SPAN><FONT color=#0000ff face=Arial 
size=2><SPAN class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>This 
no longer applies.</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>---------------------------</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><SPAN class=392080600-06122001></SPAN><FONT color=#0000ff face=Arial 
size=2><SPAN class=392080600-06122001>The textual correction that is needed in 
the 3 way draft is as follows:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>&nbsp;&nbsp; Add a clause e) to the end of Section 
8.2.3:</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>&nbsp;&nbsp; "Set the state to be reported in the 
Adjacency State field of the Point-to-Point</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001>&nbsp;&nbsp; Adjacency State option to 
down."</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN class=392080600-06122001>(NOTE: 
This would be clause f) in the 10589:2001 draft)</SPAN></FONT></DIV>
<DIV><FONT color=#0000ff face=Arial size=2><SPAN 
class=392080600-06122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
class=392080600-06122001>The previous textual correction I suggested then is not 
needed. No further change to ISH sending/processing is needed either. Whether we 
want to standardize not sending ISHs is a separate issue which should be 
discussed on a separate thread.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
class=392080600-06122001></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
class=392080600-06122001>Sorry for heading down the wrong road 
previously.</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
class=392080600-06122001></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
class=392080600-06122001>&nbsp;&nbsp; Les</SPAN></FONT></FONT></FONT></DIV>
<DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
class=392080600-06122001></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
<DIV><SPAN class=392080600-06122001>
<DIV><SPAN class=726221820-05122001></SPAN><FONT color=#0000ff face=Arial 
size=2>&nbsp;</FONT></SPAN></SPAN></SPAN><FONT face=Tahoma size=2>-----Original 
Message-----<BR><B>From:</B> Rajesh Saluja 
[mailto:rsaluja@nortelnetworks.com]<BR><B>Sent:</B> Wednesday, December 05, 2001 
3:49 PM<BR><B>To:</B> 'Les Ginsberg'; Philip Christian; 'Tony 
Przygienda'<BR><B>Cc:</B> 'isis-wg@spider.juniper.net'; 
'dkatz@juniper.net'<BR><B>Subject:</B> RE: [Isis-wg] Concerns with 
3-way-handshake<BR><BR></DIV></DIV>
<BLOCKQUOTE 
style="BORDER-LEFT: #0000ff 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px; PADDING-LEFT: 5px"></FONT>
  <DIV>&nbsp;</DIV>
  <BLOCKQUOTE style="MARGIN-RIGHT: 0px">
    <DIV><SPAN class=726221820-05122001>
    <DIV>&nbsp;</DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=726221820-05122001>Case 2)Adjacency state + Extended Local Circuit ID 
    (length = 5)</SPAN></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=726221820-05122001></SPAN></FONT>&nbsp;</DIV>
    <DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=726221820-05122001>In this case A should assume that B has not yet 
    received an IIH from A - otherwise B would have inserted the neighbor system 
    ID/circuit id. A should only record B's advertised info (system ID/circuit 
    ID) for use in its own IIH but not make any adjacency state change. 
    <BR><SPAN class=820150421-05122001>[Rajesh 
    Saluja]&nbsp;</SPAN></SPAN></FONT></FONT></FONT></DIV>
    <DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=726221820-05122001><SPAN 
    class=820150421-05122001>Les,</SPAN></SPAN></FONT></FONT></FONT></DIV>
    <DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=726221820-05122001><SPAN class=820150421-05122001>If&nbsp;a router has 
    not heard from its neighbor, the&nbsp;first IIH will always contain just the 
    extended local circuit&nbsp;id and then the adjacency goes from down to 
    initialising. If we do&nbsp;not make any adjacency change, we will actually 
    need one&nbsp;extra IIH to&nbsp;come to UP state.&nbsp;Also how does 
    this&nbsp;help in solving the&nbsp;original problem to interoperate with 
    ISH?</SPAN></SPAN></FONT></FONT></FONT></DIV>
    <DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=726221820-05122001><SPAN 
    class=820150421-05122001></SPAN></SPAN></FONT></FONT></FONT>&nbsp;</DIV>
    <DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=726221820-05122001><SPAN 
    class=820150421-05122001>Thanks,</SPAN></SPAN></FONT></FONT></FONT></DIV>
    <DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=726221820-05122001><SPAN 
    class=820150421-05122001>Rajesh</SPAN></SPAN></FONT></FONT></FONT></DIV>
    <DIV><FONT size=2><FONT color=#0000ff><FONT face=Arial><SPAN 
    class=726221820-05122001><SPAN 
    class=820150421-05122001>&nbsp;</SPAN></SPAN></FONT></FONT></FONT></DIV>
    <DIV><FONT color=#0000ff face=Arial size=2><SPAN 
    class=726221820-05122001></SPAN></FONT>&nbsp;</DIV></SPAN></DIV></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C17E18.1D890B40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec  6 18:19:51 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA15954
	for <isis-archive@lists.ietf.org>; Thu, 6 Dec 2001 18:19:50 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA31731;
	Thu, 6 Dec 2001 15:38:57 -0800 (PST)
Received: from Thor.Adtech-Inc.COM (Thor.Adtech-Inc.COM [63.165.80.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA31719
	for <isis-wg@spider.juniper.net>; Thu, 6 Dec 2001 15:37:17 -0800 (PST)
Received: from apollo.adtech-inc.com (apollo.adtech-inc.com [10.12.0.17])
	by Thor.Adtech-Inc.COM (8.11.6/8.11.6) with ESMTP id fB6NFP529072
	for <isis-wg@spider.juniper.net>; Thu, 6 Dec 2001 13:15:26 -1000 (HST)
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19)
	id <YBFTAXN2>; Thu, 6 Dec 2001 13:21:08 -1000
Message-ID: <8AC36D3167EED41184C800508BD9540501EE3C5A@apollo.adtech-inc.com>
From: "Chan, Chung Ming" <Ming.Chan@SpirentCom.COM>
To: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Cc: "Chan, Chung Ming" <Ming.Chan@SpirentCom.COM>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Isis-wg] Replacing IS-IS Neighbors TLV , etc in TE??
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 6 Dec 2001 13:21:08 -1000

Hi,
I just come across draft-ietf-sis-trafic-0.4.txt and read that the intend of
introducing some of new TLVs are to replace the ones defined in ISO10589.
e.g., Extended IS Reachability TVL will replace ISIS-Neighbors (code 2)

1) Does it mean that if an Implementation supports this new draft, then it
SHALL not use ISIS Neighbor TLV at all?

	2) If that is the case, dose any one know where can find any info
talks about the migration or this type of related stuffs?


	Thanks!


Ming Chan
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec  6 19:20:16 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA18302
	for <isis-archive@lists.ietf.org>; Thu, 6 Dec 2001 19:20:14 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA32014;
	Thu, 6 Dec 2001 16:39:56 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA32002
	for <isis-wg@spider.juniper.net>; Thu, 6 Dec 2001 16:38:40 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fB70Gn276728
	for <isis-wg@juniper.net>; Thu, 6 Dec 2001 16:16:49 -0800 (PST)
X-JNPR-Received-From: outside
Received: from mail-green.research.att.com ([135.207.30.103]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 6 Dec 2001 16:12:50 -0800
Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26])
	by mail-green.research.att.com (Postfix) with ESMTP
	id 00A801E070; Thu,  6 Dec 2001 19:14:23 -0500 (EST)
Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46])
	by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id TAA01204;
	Thu, 6 Dec 2001 19:14:22 -0500 (EST)
From: Bill Fenner <fenner@research.att.com>
Received: (from fenner@localhost)
	by windsor.research.att.com (8.8.8+Sun/8.8.5) id QAA05041;
	Thu, 6 Dec 2001 16:14:22 -0800 (PST)
Message-Id: <200112070014.QAA05041@windsor.research.att.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
To: prz@redback.com
Subject: Re: [Isis-wg] Reserved TLV Codepoints in ISIS
Cc: isis-wg@juniper.net
Versions: dmail (solaris) 2.2j/makemail 2.9b
X-OriginalArrivalTime: 07 Dec 2001 00:12:50.0734 (UTC) FILETIME=[E8756CE0:01C17EB3]
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 6 Dec 2001 16:14:22 -0800


Tony,

>    This document will be periodically updated by never versions in the
>    fashion of [RP94 ] and successors.

i.e. not since 1994? =)

  Forgive me if you've covered this already, but have you contacted the
IANA about their willingness to run a registry for this, even though
they can't be 100% authoritative?  It seems like just like the IANA no
longer publishes RFC 1700 that it'd be much easier to have a registry
than an RFC that has to be periodically updated.  Instead, we could have
an "IANA Considerations for ISIS Type Codepoints" spec, which directs
the IANA to register code points that the ISO and SIF create as well.

  How does the ISIS WG decide upon a code point for a new work item?

Thanks,
  Bill
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec  6 20:00:59 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19954
	for <isis-archive@lists.ietf.org>; Thu, 6 Dec 2001 20:00:58 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id RAA32233;
	Thu, 6 Dec 2001 17:20:57 -0800 (PST)
Received: from mta7.pltn13.pbi.net (mta7.pltn13.pbi.net [64.164.98.8])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id RAA32217
	for <isis-wg@spider.juniper.net>; Thu, 6 Dec 2001 17:19:32 -0800 (PST)
Received: from redback.com ([63.200.48.233])
 by mta7.pltn13.pbi.net (iPlanet Messaging Server 5.1 (built May  7 2001))
 with ESMTP id <0GNY00I26804YF@mta7.pltn13.pbi.net> for
 isis-wg@spider.juniper.net; Thu, 06 Dec 2001 16:57:40 -0800 (PST)
From: Tony Przygienda <prz@redback.com>
Subject: Re: [Isis-wg] Concerns with 3-way-handshake
To: Les Ginsberg <ginsberg@pluris.com>
Cc: "'Rajesh Saluja'" <rsaluja@nortelnetworks.com>,
        Philip Christian <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Message-id: <3C1000FB.1D82412F@redback.com>
MIME-version: 1.0
X-Mailer: Mozilla 4.61 [en] (X11; I; NetBSD 1.4.1 i386)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
X-Accept-Language: en
References: <17C81AD1F1FED411991E006008F6D1CA01B3F62D@avalon.pluris.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 06 Dec 2001 15:36:28 -0800
Content-Transfer-Encoding: 7BIT

Les,

> ajesh -
>
> You have reminded me that the adjacency states defined by the 3way draft and sent in the 3 way TLV are not equivalent to the adjacency states defined in 10589.
> 10589 defines the following states:
>
>    INITIALISING: Created on receipt of ISH (or IIH if you allow that)
>    UP
>    FAILED (Only used on DA circuits - let's ignore that)
>    DOWN: A transient state because the adjacency is deleted immediately after
>
> 3way defines:
>
>    DOWN: Can mean no adjacency exists or the state associated with the adjacency when an IIH is received and the action in Tables 5,6,7, or 8 from 10589 is UP
>   INITIALISING: Reached after receiving an IIH when you are in down state (as per table in 3way draft)
>   UP
>
> Conceptually it is necessary to maintain these two sets of adjacency states because until you receive an IIH you do not know whether your neighbor supports
> 3way or not. If your neighbor does not include the 3way TLV then you follow the original 10589 rules, which means that you transition from Initialising to UP
> when receiving an IIH.
>
> If your neighbor does include the 3 way TLV, then after determining via Tables 5,6,7,8 that the action is UP you must set local 3way state to DOWN and then
> apply the 3way state table.
>
> If you are initiating an IIH before you have received one, then you should set the adjacency state field in the 3way TLV to down (NOT initialising), whether
> you have received an ISH or not. The 3way state can only transition to Initialising after receiving an IIH.
>
> All of this makes me think that Philip's original premise is wrong (and unfortunately much of the discussion, including much of my comments) is off the mark.
> Philip said:
>
>  >A is connected to B and issues an ISH.
> >B receives the ISH, and according to ISO 10589 section 8.2.2 creates an adjacency of type "Initialising".
> >B now reports to A in the new "Point to point adjacency state" option that the adjacency is "Initialising".
>
> No - this is incorrect. B should report the 3way state as "Down" because it has yet to receive an IIH.
>
> >A receives this and according to the table in the draft, brings the adjacency "up".
>
> Now A will, following the table in 3 way draft, change the adjacency to Initialising.
>
> >However B may never have received an IIH from A and so the three way handshake has been short circuited
>
> This no longer applies.
>

fine, so if understood correctly you originate first hello always with 'Down'
for 3-way which makes for ISHs impossible to short-cut the 3-way state machine.
Any first hello you receive for ISH you sent should therefore be 'Down' for
3-way as well. That solves the problem or rather it seems really non-existent.

The textual correction that is needed in the 3 way draft is as follows:

   Add a clause e) to the end of Section 8.2.3:

   "Set the state to be reported in the Adjacency State field of the
Point-to-Point
   Adjacency State option to down."

(NOTE: This would be clause f) in the 10589:2001 draft)

yes, seems to me indeed necessary AND sufficient. I suggest to halt the
RFC publication and do another last call after this fix is propagated.  Protocol
specifications
with buggy or unclear state machines shine a poor light on the group involved
;-)

> The previous textual correction I suggested then is not needed. No further change to ISH sending/processing is needed either. Whether we want to standardize
> not sending ISHs is a separate issue which should be discussed on a separate thread.
>

yes, it is a fully orthogonal issue and if somebody feels like documenting it,
fine, does not seem to me very important or even necessary (seems you can
violate the 10589 here in many inventive
ways and it is still stable enough to survive it).

>
> Sorry for heading down the wrong road previously.
>

good scare, everybody fell for it initially ;-)


    --- tony



_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec  6 21:11:22 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21307
	for <isis-archive@odin.ietf.org>; Thu, 6 Dec 2001 21:11:21 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA32555;
	Thu, 6 Dec 2001 18:30:57 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA32540
	for <isis-wg@spider.juniper.net>; Thu, 6 Dec 2001 18:29:02 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id SAA02215;
	Thu, 6 Dec 2001 18:07:05 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <Y2HL88WK>; Thu, 6 Dec 2001 18:07:05 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F634@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Tony Przygienda'" <prz@redback.com>,
        Les  Ginsberg
	 <ginsberg@pluris.com>
Cc: "'Rajesh Saluja'" <rsaluja@nortelnetworks.com>,
        Philip Christian
	 <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'"
	 <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 6 Dec 2001 18:07:04 -0800

Tony -

Thanks for your comments. I agree with your view that the text should be
revised before publication.

In addition to the correction mentioned below, there was also discussion of
revising it to indicate there is a legacy version of the 3 way TLV which
only sends adjacency state. This should require no changes to the state
table, which handles it (as indicated in the draft), but it should be noted
that the length can be 1-17 (rather than 5-17 as it indicates now) and
perhaps some brief description of what form this legacy version takes.

   Les
 

> -----Original Message-----
> From: Tony Przygienda [mailto:prz@redback.com]
> Sent: Thursday, December 06, 2001 3:36 PM
> To: Les Ginsberg
> Cc: 'Rajesh Saluja'; Philip Christian; 'isis-wg@spider.juniper.net';
> 'dkatz@juniper.net'
> Subject: Re: [Isis-wg] Concerns with 3-way-handshake
> 
> 
> Les,
> 
> > ajesh -
> >
> > You have reminded me that the adjacency states defined by 
> the 3way draft and sent in the 3 way TLV are not equivalent 
> to the adjacency states defined in 10589.
> > 10589 defines the following states:
> >
> >    INITIALISING: Created on receipt of ISH (or IIH if you 
> allow that)
> >    UP
> >    FAILED (Only used on DA circuits - let's ignore that)
> >    DOWN: A transient state because the adjacency is deleted 
> immediately after
> >
> > 3way defines:
> >
> >    DOWN: Can mean no adjacency exists or the state 
> associated with the adjacency when an IIH is received and the 
> action in Tables 5,6,7, or 8 from 10589 is UP
> >   INITIALISING: Reached after receiving an IIH when you are 
> in down state (as per table in 3way draft)
> >   UP
> >
> > Conceptually it is necessary to maintain these two sets of 
> adjacency states because until you receive an IIH you do not 
> know whether your neighbor supports
> > 3way or not. If your neighbor does not include the 3way TLV 
> then you follow the original 10589 rules, which means that 
> you transition from Initialising to UP
> > when receiving an IIH.
> >
> > If your neighbor does include the 3 way TLV, then after 
> determining via Tables 5,6,7,8 that the action is UP you must 
> set local 3way state to DOWN and then
> > apply the 3way state table.
> >
> > If you are initiating an IIH before you have received one, 
> then you should set the adjacency state field in the 3way TLV 
> to down (NOT initialising), whether
> > you have received an ISH or not. The 3way state can only 
> transition to Initialising after receiving an IIH.
> >
> > All of this makes me think that Philip's original premise 
> is wrong (and unfortunately much of the discussion, including 
> much of my comments) is off the mark.
> > Philip said:
> >
> >  >A is connected to B and issues an ISH.
> > >B receives the ISH, and according to ISO 10589 section 
> 8.2.2 creates an adjacency of type "Initialising".
> > >B now reports to A in the new "Point to point adjacency 
> state" option that the adjacency is "Initialising".
> >
> > No - this is incorrect. B should report the 3way state as 
> "Down" because it has yet to receive an IIH.
> >
> > >A receives this and according to the table in the draft, 
> brings the adjacency "up".
> >
> > Now A will, following the table in 3 way draft, change the 
> adjacency to Initialising.
> >
> > >However B may never have received an IIH from A and so the 
> three way handshake has been short circuited
> >
> > This no longer applies.
> >
> 
> fine, so if understood correctly you originate first hello 
> always with 'Down'
> for 3-way which makes for ISHs impossible to short-cut the 
> 3-way state machine.
> Any first hello you receive for ISH you sent should therefore 
> be 'Down' for
> 3-way as well. That solves the problem or rather it seems 
> really non-existent.
> 
> The textual correction that is needed in the 3 way draft is 
> as follows:
> 
>    Add a clause e) to the end of Section 8.2.3:
> 
>    "Set the state to be reported in the Adjacency State field of the
> Point-to-Point
>    Adjacency State option to down."
> 
> (NOTE: This would be clause f) in the 10589:2001 draft)
> 
> yes, seems to me indeed necessary AND sufficient. I suggest 
> to halt the
> RFC publication and do another last call after this fix is 
> propagated.  Protocol
> specifications
> with buggy or unclear state machines shine a poor light on 
> the group involved
> ;-)
> 
> > The previous textual correction I suggested then is not 
> needed. No further change to ISH sending/processing is needed 
> either. Whether we want to standardize
> > not sending ISHs is a separate issue which should be 
> discussed on a separate thread.
> >
> 
> yes, it is a fully orthogonal issue and if somebody feels 
> like documenting it,
> fine, does not seem to me very important or even necessary 
> (seems you can
> violate the 10589 here in many inventive
> ways and it is still stable enough to survive it).
> 
> >
> > Sorry for heading down the wrong road previously.
> >
> 
> good scare, everybody fell for it initially ;-)
> 
> 
>     --- tony
> 
> 
> 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec  6 21:26:32 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA21533
	for <isis-archive@odin.ietf.org>; Thu, 6 Dec 2001 21:26:30 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA32635;
	Thu, 6 Dec 2001 18:46:57 -0800 (PST)
Received: from tahoe.allegronetworks.com (tahoe.allegronetworks.com [63.115.58.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id SAA32623
	for <isis-wg@spider.juniper.net>; Thu, 6 Dec 2001 18:45:10 -0800 (PST)
Received: by tahoe.allegronetworks.com with Internet Mail Service (5.5.2653.19)
	id <YCX6AZ3N>; Thu, 6 Dec 2001 18:23:02 -0800
Message-ID: <B4DFCB7CDE2DD4118F690008C78694160115D9A6@tahoe.allegronetworks.com>
From: Neal Castagnoli <cast@allegronetworks.com>
To: "'Tony Przygienda'" <prz@redback.com>,
        Les Ginsberg
	 <ginsberg@pluris.com>
Cc: "'Rajesh Saluja'" <rsaluja@nortelnetworks.com>,
        Philip Christian
	 <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'"
	 <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 6 Dec 2001 18:23:01 -0800


> fine, so if understood correctly you originate first hello 
> always with 'Down'
> for 3-way which makes for ISHs impossible to short-cut the 
> 3-way state machine.

Does this follow?  The first transmitted hello could be dropped, the ISH
would then come in and update the adjacency state to "Initialising" though
you've never received a hello from the other side.


> Any first hello you receive for ISH you sent should therefore 
> be 'Down' for
> 3-way as well. That solves the problem or rather it seems 
> really non-existent.
> 
> The textual correction that is needed in the 3 way draft is 
> as follows:
> 
>    Add a clause e) to the end of Section 8.2.3:
> 
>    "Set the state to be reported in the Adjacency State field of the
> Point-to-Point
>    Adjacency State option to down."

Section 8.2.3 in the original 10589 describes constructing hellos in
general.  This text would result in *all* hellos being transmitted with
"Down."

If this is meant to be added to section 8.2.2, the ISH section, then it
seems you would need to change some of the three-way text to create a new
3-way adjacency state in addition to the regular adjacency state, but is
this really necessary?

Also, if there were an implementation that forgot to turn off transmission
of ISHs, then the adjacency would potentially not come up or perhaps cycle
up and down.  Perhaps it would be better to take advantage of the built in
conditionals in section 8.2.2.

  --Neal
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec  6 21:57:00 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA22841
	for <isis-archive@odin.ietf.org>; Thu, 6 Dec 2001 21:56:59 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id TAA32872;
	Thu, 6 Dec 2001 19:16:58 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id TAA32847
	for <isis-wg@spider.juniper.net>; Thu, 6 Dec 2001 19:15:07 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id SAA04410;
	Thu, 6 Dec 2001 18:50:56 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <Y2HL8851>; Thu, 6 Dec 2001 18:50:56 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F635@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Neal Castagnoli'" <cast@allegronetworks.com>,
        "'Tony Przygienda'"
	 <prz@redback.com>,
        Les  Ginsberg <ginsberg@pluris.com>
Cc: "'Rajesh Saluja'" <rsaluja@nortelnetworks.com>,
        Philip Christian
	 <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'"
	 <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 6 Dec 2001 18:50:55 -0800


Neal -

Sorry. My error. I indeed was referring to Section 8.2.2 "Receiving ISHs by
an Intermediate System". Good catch. So we have:

The textual correction that is needed in the 3 way draft is 
as follows:
 
   Add a clause e) to the end of Section 8.2.2:

   "Set the state to be reported in the Adjacency State field of the
    Point-to-Point Adjacency State option to down."

(NOTE: This would be clause f) in the 10589:2001 draft)
 

I believe after making this correction your concern about the state moving
from down to initialised as a result of receiving an ISH goes away.

ISHs received after the adjacency has been created are not a problem as
8.2.2b tells you to discard them. ISHs received after an adjacency is UP
should be ignored. This was never made explicit in the 1992 version. Much
clearer text can be found in 10589:2001 8.2.3

The issue you raise regarding adjacency state vs. 3way adjacency state can
be viewed as an implementation issue. There is nothing in the 3way draft
that requires that the state advertised in the TLV be identical to the value
of "adjacencyState" as defined in 10589. The latter is never directly
visible to the neighbor.

It can be argued that it would clearer/more intuitive if these states were
perfectly aligned. This would require some revisions to the 10589 text to
substitute "Down" for "Initialised" in some places. This should not break
anything because the 10589 state tables really depend on the notion of the
adjacency being "up or not up". But if not done carefully, there would
confusion introduced regarding the new use of state "Down" and
AdjacencyStateChange(Down) events. I do not object to this clarification in
principle - but I am not inclined to go to this trouble.

   Les


> -----Original Message-----
> From: Neal Castagnoli [mailto:cast@allegronetworks.com]
> Sent: Thursday, December 06, 2001 6:23 PM
> To: 'Tony Przygienda'; Les Ginsberg
> Cc: 'Rajesh Saluja'; Philip Christian; 'isis-wg@spider.juniper.net';
> 'dkatz@juniper.net'
> Subject: RE: [Isis-wg] Concerns with 3-way-handshake
> 
> 
> 
> > fine, so if understood correctly you originate first hello 
> > always with 'Down'
> > for 3-way which makes for ISHs impossible to short-cut the 
> > 3-way state machine.
> 
> Does this follow?  The first transmitted hello could be 
> dropped, the ISH
> would then come in and update the adjacency state to 
> "Initialising" though
> you've never received a hello from the other side.
> 
> 
> > Any first hello you receive for ISH you sent should therefore 
> > be 'Down' for
> > 3-way as well. That solves the problem or rather it seems 
> > really non-existent.
> > 
> > The textual correction that is needed in the 3 way draft is 
> > as follows:
> > 
> >    Add a clause e) to the end of Section 8.2.3:
> > 
> >    "Set the state to be reported in the Adjacency State field of the
> > Point-to-Point
> >    Adjacency State option to down."
> 
> Section 8.2.3 in the original 10589 describes constructing hellos in
> general.  This text would result in *all* hellos being 
> transmitted with
> "Down."
> 
> If this is meant to be added to section 8.2.2, the ISH 
> section, then it
> seems you would need to change some of the three-way text to 
> create a new
> 3-way adjacency state in addition to the regular adjacency 
> state, but is
> this really necessary?
> 
> Also, if there were an implementation that forgot to turn off 
> transmission
> of ISHs, then the adjacency would potentially not come up or 
> perhaps cycle
> up and down.  Perhaps it would be better to take advantage of 
> the built in
> conditionals in section 8.2.2.
> 
>   --Neal
> 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec  7 05:18:06 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA17763
	for <isis-archive@odin.ietf.org>; Fri, 7 Dec 2001 05:18:05 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA34772;
	Fri, 7 Dec 2001 02:37:58 -0800 (PST)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA34760
	for <isis-wg@spider.juniper.net>; Fri, 7 Dec 2001 02:36:58 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB7AEMd04286;
	Fri, 7 Dec 2001 05:14:22 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB7AEql13197;
	Fri, 7 Dec 2001 10:14:52 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6LZB9T>; Fri, 7 Dec 2001 10:13:57 -0000
Message-ID: <4103264BC8D3D51180B7002048400C4507139F@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: "'Tony Przygienda'" <prz@redback.com>,
        Les Ginsberg
	 <ginsberg@pluris.com>
Cc: "Rajesh Saluja" <rsaluja@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17F07.DDD95130"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 7 Dec 2001 10:13:50 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17F07.DDD95130
Content-Type: text/plain;
	charset="iso-8859-1"

To be fair to Les, it was me that started the scare. I did misunderstand
what was going on, however it will hopefully result in a better RFC.

This text of Les'

 Add a clause e) to the end of Section 8.2.3:

   "Set the state to be reported in the Adjacency State field of the
Point-to-Point
   Adjacency State option to down."

Presumably this is to be added to what is already there in the draft, making
the complete text:-

"Add a clause e) to the end of section 8.2.3:

     The IS shall include the Point-to-Point Adjacency State option in
     the transmitted Point-to-Point IIH PDU.  The current state of the
     adjacency with its neighbor on the link (as defined in section
     8.2.4.1.1) shall be reported in the Adjacency State field.  If no
     adjacency exists, the state shall be reported as Down.

     The Extended Local Circuit ID field shall contain a value assigned
     by this IS when the circuit is created.  This value shall be unique
     among all the circuits of this Intermediate System.  The value is
     not necessarily related to that carried in the Local Circuit ID
     field of the IIH PDU.

     If the system ID and Extended Local Circuit ID of the neighboring
     system are known (in state Initializing or Up), the neighbor's
     system ID shall be reported in the Neighbor System ID field, and
     the neighbor's Extended Local Circuit ID shall be reported in the
     Neighbor Extended Local Circuit ID field.

     Set the state to be reported in the Adjacency State field of the
     Point-to-Point Adjacency State option to Down."

Is that right?

Philip Christian.

>
> Sorry for heading down the wrong road previously.
>

good scare, everybody fell for it initially ;-)


    --- tony




------_=_NextPart_001_01C17F07.DDD95130
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>RE: [Isis-wg] Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>To be fair to Les, it was me that started the scare. =
I did misunderstand what was going on, however it will hopefully result =
in a better RFC.</FONT></P>

<P><FONT SIZE=3D2>This text of Les'</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;Add a clause e) to the end of Section =
8.2.3:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp; &quot;Set the state to be reported in =
the Adjacency State field of the</FONT>
<BR><FONT SIZE=3D2>Point-to-Point</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp; Adjacency State option to =
down.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>Presumably this is to be added to what is already =
there in the draft, making the complete text:-</FONT>
</P>

<P><FONT SIZE=3D2>&quot;Add a clause e) to the end of section =
8.2.3:</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; The IS shall include the =
Point-to-Point Adjacency State option in</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; the transmitted =
Point-to-Point IIH PDU.&nbsp; The current state of the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; adjacency with its neighbor =
on the link (as defined in section</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; 8.2.4.1.1) shall be =
reported in the Adjacency State field.&nbsp; If no</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; adjacency exists, the state =
shall be reported as Down.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; The Extended Local Circuit =
ID field shall contain a value assigned</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; by this IS when the circuit =
is created.&nbsp; This value shall be unique</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; among all the circuits of =
this Intermediate System.&nbsp; The value is</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; not necessarily related to =
that carried in the Local Circuit ID</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; field of the IIH =
PDU.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; If the system ID and =
Extended Local Circuit ID of the neighboring</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; system are known (in state =
Initializing or Up), the neighbor's</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; system ID shall be reported =
in the Neighbor System ID field, and</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; the neighbor's Extended =
Local Circuit ID shall be reported in the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Neighbor Extended Local =
Circuit ID field.</FONT>
</P>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Set the state to be reported =
in the Adjacency State field of the</FONT>
<BR><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp;&nbsp; Point-to-Point Adjacency =
State option to Down.&quot;</FONT>
</P>

<P><FONT SIZE=3D2>Is that right?</FONT>
</P>

<P><FONT SIZE=3D2>Philip Christian.</FONT>
</P>

<P><FONT SIZE=3D2>&gt;</FONT>
<BR><FONT SIZE=3D2>&gt; Sorry for heading down the wrong road =
previously.</FONT>
<BR><FONT SIZE=3D2>&gt;</FONT>
</P>

<P><FONT SIZE=3D2>good scare, everybody fell for it initially =
;-)</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&nbsp;&nbsp;&nbsp; --- tony</FONT>
</P>
<BR>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C17F07.DDD95130--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec  7 06:11:36 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA18804
	for <isis-archive@odin.ietf.org>; Fri, 7 Dec 2001 06:11:36 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA35039;
	Fri, 7 Dec 2001 03:31:58 -0800 (PST)
Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA35024
	for <isis-wg@spider.juniper.net>; Fri, 7 Dec 2001 03:30:16 -0800 (PST)
Received: from ssntw1 by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago)
	id DAA07561; Fri, 7 Dec 2001 03:08:13 -0800 (PST)
From: "Matthew Noble" <matthew.noble@riverstonenet.com>
To: <mshand@cisco.com>
Cc: "'Isis-Wg (E-mail)" <isis-wg@spider.juniper.net>
Message-ID: <000001c17f11$e107a230$e9dc14ac@ctron.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Subject: [Isis-wg] IS-IS Restart draft clarification
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 7 Dec 2001 11:25:03 -0000
Content-Transfer-Encoding: 7bit

Mike

In section 4.3.1.2 second paragraph says that SPF is not run while T3 is
running, but in the 5th paragraph of the same section it says that when T2
expires/cancelled, the SPF for that level _is_ run. Now T2 will expire under
normal sucessful conditions before T3 expires - so there is a contradiction
here. I am assuming that the info in the 5th paragraph is correct, and that
that in the second paragraph is wrong.

Could you confirm that for me.

Thanks
Matt

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec  7 09:26:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20836
	for <isis-archive@lists.ietf.org>; Fri, 7 Dec 2001 09:26:57 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA35827;
	Fri, 7 Dec 2001 06:46:57 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA35815
	for <isis-wg@spider.juniper.net>; Fri, 7 Dec 2001 06:45:43 -0800 (PST)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4.cisco.com [10.50.0.3])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id OAA21915;
	Fri, 7 Dec 2001 14:23:44 GMT
Message-Id: <4.3.2.7.2.20011207142041.033b1740@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Matthew Noble" <matthew.noble@riverstonenet.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] IS-IS Restart draft clarification
Cc: "'Isis-Wg (E-mail)" <isis-wg@spider.juniper.net>
In-Reply-To: <000001c17f11$e107a230$e9dc14ac@ctron.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 07 Dec 2001 14:24:10 +0000

At 11:25 07/12/2001 +0000, Matthew Noble wrote:
>Mike
>
>In section 4.3.1.2 second paragraph says that SPF is not run while T3 is
>running, but in the 5th paragraph of the same section it says that when T2
>expires/cancelled, the SPF for that level _is_ run. Now T2 will expire under
>normal sucessful conditions before T3 expires - so there is a contradiction
>here. I am assuming that the info in the 5th paragraph is correct, and that
>that in the second paragraph is wrong.
>
>Could you confirm that for me.

Without actually looking at the draft, I think the issue is that once we 
have got synchronization we can safely run SPF at that level. Once we have 
got synchronization at both levels we can clear T3. But while one level is 
synchronized and the other is not we still need to keep T3 running.

So yes, I think the second para is strictly wrong.

But I'll look at it in more detail later.

         Mike



>Thanks
>Matt
>
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec  7 09:49:56 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA21208
	for <isis-archive@lists.ietf.org>; Fri, 7 Dec 2001 09:49:55 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA36001;
	Fri, 7 Dec 2001 07:09:57 -0800 (PST)
Received: from mailhost.avici.com ([208.246.215.9])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA35989
	for <isis-wg@spider.juniper.net>; Fri, 7 Dec 2001 07:08:29 -0800 (PST)
Received: from Kontoff.com (mkontoff-pc.avici.com [10.2.20.117])
	by mailhost.avici.com (8.11.0/8.11.0) with ESMTP id fB7EkXj14748
	for <isis-wg@spider.juniper.net>; Fri, 7 Dec 2001 09:46:33 -0500 (EST)
Message-ID: <3C10D61B.16370A8@Kontoff.com>
From: Matthew Kontoff <mkontoff@Kontoff.com>
X-Mailer: Mozilla 4.76 [en] (WinNT; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
CC: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Subject: Re: [Isis-wg] Replacing IS-IS Neighbors TLV , etc in TE??
References: <8AC36D3167EED41184C800508BD9540501EE3C5A@apollo.adtech-inc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 07 Dec 2001 09:45:47 -0500
Content-Transfer-Encoding: 7bit

Hi,

"Chan, Chung Ming" wrote:
> 
> Hi,
> I just came across draft-ietf-isis-traffic-04.txt and read that the intent of
> introducing some of new TLVs are to replace the ones defined in ISO 10589.
> e.g., Extended IS Reachability TLV will replace ISIS-Neighbors (code 2)
> 
> 1) Does it mean that if an Implementation supports this new draft, then it
> SHALL not use ISIS Neighbor TLV at all?

No. Whether or not the ISIS Neighbor TLV is used is up to the implementation
but it is a real good idea to be backward compatible with IS-IS routers that
don't support the draft.

> 2) If that is the case, does any one know where I can find any info
> that talks about the migration or this type of related stuff?

For a migration to occur smoothly - without losing routes - you need to be 
able to handle both the old style IS neighbor TLV and the new style (extended 
IS Reachability TLV). You will need to decide which TLV you will use when
running your SPF. 

Matt
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec  7 17:18:38 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01362
	for <isis-archive@odin.ietf.org>; Fri, 7 Dec 2001 17:18:38 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA37775;
	Fri, 7 Dec 2001 14:37:58 -0800 (PST)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA37762
	for <isis-wg@spider.juniper.net>; Fri, 7 Dec 2001 14:36:17 -0800 (PST)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id NAA10857;
	Fri, 7 Dec 2001 13:24:23 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <YNMDDAN8>; Fri, 7 Dec 2001 13:24:23 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F637@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Philip Christian '" <christi@nortelnetworks.com>,
        "''Tony Przygienda' '"
	 <prz@redback.com>,
        Les  Ginsberg <ginsberg@pluris.com>
Cc: "'Rajesh Saluja '" <rsaluja@nortelnetworks.com>,
        "''isis-wg@spider.juniper.net' '" <isis-wg@spider.juniper.net>,
        "''dkatz@juniper.net' '" <dkatz@juniper.net>
Subject: RE: [Isis-wg] Concerns with 3-way-handshake
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 7 Dec 2001 13:24:22 -0800

 
As pointed out by Neal Castagnoli yesterday, the text I presented below
belongs in Section 8.2.2 Receiving ISH PDUs by an Intermediate System. This
was a section reference error on my part which I corrected based on Neal's
input.

The existing text in the 3 way draft which adds a new item (coincidentally
also "e)") still belongs in 8.2.3 Sending point-to-point IIH PDUs as is
currently indicated in the draft. 


   Les



-----Original Message-----
From: Philip Christian
To: 'Tony Przygienda'; Les Ginsberg
Cc: Rajesh Saluja; 'isis-wg@spider.juniper.net'; 'dkatz@juniper.net'
Sent: 12/7/01 2:13 AM
Subject: RE: [Isis-wg] Concerns with 3-way-handshake

To be fair to Les, it was me that started the scare. I did misunderstand
what was going on, however it will hopefully result in a better RFC.

This text of Les' 

 Add a clause e) to the end of Section 8.2.3: 

   "Set the state to be reported in the Adjacency State field of the 
Point-to-Point 
   Adjacency State option to down." 

Presumably this is to be added to what is already there in the draft,
making the complete text:- 

"Add a clause e) to the end of section 8.2.3: 

     The IS shall include the Point-to-Point Adjacency State option in 
     the transmitted Point-to-Point IIH PDU.  The current state of the 
     adjacency with its neighbor on the link (as defined in section 
     8.2.4.1.1) shall be reported in the Adjacency State field.  If no 
     adjacency exists, the state shall be reported as Down. 

     The Extended Local Circuit ID field shall contain a value assigned 
     by this IS when the circuit is created.  This value shall be unique

     among all the circuits of this Intermediate System.  The value is 
     not necessarily related to that carried in the Local Circuit ID 
     field of the IIH PDU. 

     If the system ID and Extended Local Circuit ID of the neighboring 
     system are known (in state Initializing or Up), the neighbor's 
     system ID shall be reported in the Neighbor System ID field, and 
     the neighbor's Extended Local Circuit ID shall be reported in the 
     Neighbor Extended Local Circuit ID field. 

     Set the state to be reported in the Adjacency State field of the 
     Point-to-Point Adjacency State option to Down." 

Is that right? 

Philip Christian. 

> 
> Sorry for heading down the wrong road previously. 
> 

good scare, everybody fell for it initially ;-) 


    --- tony 



_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 10 17:21:52 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13227
	for <isis-archive@lists.ietf.org>; Mon, 10 Dec 2001 17:21:51 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA56570;
	Mon, 10 Dec 2001 14:39:58 -0800 (PST)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA56558
	for <isis-wg@spider.juniper.net>; Mon, 10 Dec 2001 14:38:20 -0800 (PST)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fBAMFu259614
	for <isis-wg@juniper.net>; Mon, 10 Dec 2001 14:15:57 -0800 (PST)
X-JNPR-Received-From: outside
Received: from exc-sc1.yagosys.com ([63.113.148.3]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 10 Dec 2001 14:12:41 -0800
Received: from ray (134.141.180.42 [134.141.180.42]) by exc-sc1.yagosys.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2653.13)
	id X7WV3BLP; Mon, 10 Dec 2001 14:14:03 -0800
Reply-To: <rayq@riverstonenet.com>
From: "Ray Qiu" <rayq@riverstonenet.com>
To: <isis-wg@juniper.net>
Message-ID: <001301c181c8$41bf1a50$0101a8c0@ray>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
X-OriginalArrivalTime: 10 Dec 2001 22:12:41.0250 (UTC) FILETIME=[C8EC7820:01C181C7]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by external.juniper.net id OAA56559
Subject: [Isis-wg] overload bit in TE mode
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 10 Dec 2001 14:15:49 -0800
Content-Transfer-Encoding: 8bit

Hi,

I got a question about the overload bit in TE mode.

In TE mode, the TLV 135 replaces the TLVs 128 and 130,
so we can not tell if the prefix is internal or external.  

If we get prefixes from an overloaded router, how
can we make sure that we only install the direct
routes?  By checking the interface address TLV?

Thanks for your clarification.

Regards,
Ray
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 10 19:28:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA15670
	for <isis-archive@lists.ietf.org>; Mon, 10 Dec 2001 19:28:57 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA57285;
	Mon, 10 Dec 2001 16:48:58 -0800 (PST)
Received: from ams2eusosrv15.ams.ops.eu.uu.net (ams2eusosrv15.ams.ops.eu.uu.net [146.188.99.70])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA57272
	for <isis-wg@spider.juniper.net>; Mon, 10 Dec 2001 16:47:43 -0800 (PST)
Received: from ams2eusosrv20.ams.ops.eu.uu.net by ams2eusosrv15.ams.ops.eu.uu.net with ESMTP 
	(peer crosschecked as: ams2eusosrv20.ams.ops.eu.uu.net [146.188.99.75])
	id QQlswf06237
	for <isis-wg@spider.juniper.net>; Tue, 11 Dec 2001 00:25:22 GMT
Received: from ams2eusosrv20.ams.ops.eu.uu.net by ams2eusosrv20.ams.ops.eu.uu.net with ESMTP 
	(peer crosschecked as: localhost [127.0.0.1])
	id QQlswf21882
	for <isis-wg@spider.juniper.net>; Tue, 11 Dec 2001 00:24:49 GMT
Received: from amr1.eu.uu.net by ams2eusosrv20.ams.ops.eu.uu.net with ESMTP 
	(peer crosschecked as: cgen1.cbg.ops.eu.uu.net [62.191.16.229])
	id QQlswf21873
	for <isis-wg@spider.juniper.net>; Tue, 11 Dec 2001 00:24:49 GMT
Received: from EMEATP600E03220 (eunoc218.ams.ops.eu.uu.net [146.188.96.143])
	SMTPAUTH: client authenticated: jgreenha/LOGIN
	by amr1.eu.uu.net (8.11.3/8.11.3) with ESMTP id fBB0OkR07010
	STARTTLS using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO
	for <isis-wg@external.juniper.net>; 
	Tue, 11 Dec 2001 00:24:48 GMT
Reply-To: <john@igtec.net>
From: "John Greenhalgh" <john@igtec.net>
To: <isis-wg@spider.juniper.net>
Message-ID: <000001c181da$6de23740$8f60bc92@emeaops.eu.frd.uu.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
Subject: [Isis-wg] IS-IS Resource Page
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 11 Dec 2001 01:26:07 +0100
Content-Transfer-Encoding: 7bit

Hi,

I've recently been teaching IS-IS, and put together some of the info I used
at http://www.igtec.net/isis

It's pretty basic and small, and not aimed directly at the audience of this
list, but I would appreciate any comments, ideas, links, etc.

Many Thanks,
John

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec 11 06:09:17 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16226
	for <isis-archive@lists.ietf.org>; Tue, 11 Dec 2001 06:09:16 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA60013;
	Tue, 11 Dec 2001 03:27:58 -0800 (PST)
Received: from hotmail.com (f100.law3.hotmail.com [209.185.241.100])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA59993
	for <isis-wg@external.juniper.net>; Tue, 11 Dec 2001 03:26:27 -0800 (PST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 11 Dec 2001 03:04:04 -0800
Received: from 203.196.145.150 by lw3fd.law3.hotmail.msn.com with HTTP;
	Tue, 11 Dec 2001 11:04:03 GMT
X-Originating-IP: [203.196.145.150]
From: "Sachidananda K" <sachidananda_k@hotmail.com>
To: isis-wg@spider.juniper.net
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F100ilmMpgRasC2SiwV0001c6ba@hotmail.com>
X-OriginalArrivalTime: 11 Dec 2001 11:04:04.0027 (UTC) FILETIME=[8B9BC8B0:01C18233]
Subject: [Isis-wg] (no subject)
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 11 Dec 2001 11:04:03 +0000

Hi,

I have some questions related to the waiting state.

The section 7.3.19 of ISO 10589 states that IS shall enter the waiting state 
upon being overloaded. The waiting state timer shall be restarted every time 
the PDU cannot be processed due to lack of resources (I understand this 
would generally be memory).

However, if the IS has ran out of memory, condition would persist for ever, 
till it is cold-rebooted (Unless some other auto-recovery mechanism is 
provided by OS). In either case the protocol would have to be re-started 
from fresh.

I would like to know if the IS enters the wait state for such reasons is 
there any specific sequence of activities to be performed (that standard 
describes).

Please help in this regards.
Thanking you in advance.
Sachi

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

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec 11 06:13:36 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16266
	for <isis-archive@lists.ietf.org>; Tue, 11 Dec 2001 06:13:34 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA60050;
	Tue, 11 Dec 2001 03:32:52 -0800 (PST)
Received: from hotmail.com (f72.law3.hotmail.com [209.185.241.72])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA59998
	for <isis-wg@external.juniper.net>; Tue, 11 Dec 2001 03:26:44 -0800 (PST)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Tue, 11 Dec 2001 03:04:21 -0800
Received: from 203.196.145.150 by lw3fd.law3.hotmail.msn.com with HTTP;
	Tue, 11 Dec 2001 11:04:21 GMT
X-Originating-IP: [203.196.145.150]
From: "Sachidananda K" <sachidananda_k@hotmail.com>
To: isis-wg@spider.juniper.net
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F72jzdgJI7fG7rIgwbO0000090a@hotmail.com>
X-OriginalArrivalTime: 11 Dec 2001 11:04:21.0656 (UTC) FILETIME=[961DC180:01C18233]
Subject: [Isis-wg] Waiting state
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 11 Dec 2001 11:04:21 +0000

Hi,

I have some questions related to the waiting state.

The section 7.3.19 of ISO 10589 states that IS shall enter the waiting state 
upon being overloaded. The waiting state timer shall be restarted every time 
the PDU cannot be processed due to lack of resources (I understand this 
would generally be memory).

However, if the IS has ran out of memory, condition would persist for ever, 
till it is cold-rebooted (Unless some other auto-recovery mechanism is 
provided by OS). In either case the protocol would have to be re-started 
from fresh.

I would like to know if the IS enters the wait state for such reasons is 
there any specific sequence of activities to be performed (that standard 
describes).

Please help in this regards.
Thanking you in advance.
Sachi

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

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec 11 06:34:26 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16425
	for <isis-archive@lists.ietf.org>; Tue, 11 Dec 2001 06:34:24 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA60196;
	Tue, 11 Dec 2001 03:54:58 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA60184
	for <isis-wg@spider.juniper.net>; Tue, 11 Dec 2001 03:53:48 -0800 (PST)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4158.cisco.com [10.50.16.61])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id LAA11935;
	Tue, 11 Dec 2001 11:31:22 GMT
Message-Id: <4.3.2.7.2.20011211112849.00baa6b0@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Sachidananda K" <sachidananda_k@hotmail.com>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] Waiting state
Cc: isis-wg@spider.juniper.net
In-Reply-To: <F72jzdgJI7fG7rIgwbO0000090a@hotmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 11 Dec 2001 11:31:47 +0000

At 11:04 11/12/2001 +0000, Sachidananda K wrote:
>Hi,
>
>I have some questions related to the waiting state.
>
>The section 7.3.19 of ISO 10589 states that IS shall enter the waiting 
>state upon being overloaded. The waiting state timer shall be restarted 
>every time the PDU cannot be processed due to lack of resources (I 
>understand this would generally be memory).
>
>However, if the IS has ran out of memory, condition would persist for 
>ever, till it is cold-rebooted (Unless some other auto-recovery mechanism 
>is provided by OS). In either case the protocol would have to be 
>re-started from fresh.
>
>I would like to know if the IS enters the wait state for such reasons is 
>there any specific sequence of activities to be performed (that standard 
>describes).

Dynamic overload is all too possible. For example an accidental merging of 
areas, which are then de-merged. Or even a DR change on a large LAN. The 
point is that (one hopes) the memory is adequate for the steady state 
designed topology. If anything happens to exceed that, the waiting state 
will allow recovery when the perturbation is removed without requiring 
further intervention.

         Mike



>Please help in this regards.
>Thanking you in advance.
>Sachi
>
>_________________________________________________________________
>Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp
>
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec 11 06:57:52 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA16562
	for <isis-archive@lists.ietf.org>; Tue, 11 Dec 2001 06:57:51 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA60335;
	Tue, 11 Dec 2001 04:17:58 -0800 (PST)
Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA60323
	for <isis-wg@spider.juniper.net>; Tue, 11 Dec 2001 04:16:20 -0800 (PST)
Received: from ssntw1 by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago)
	id DAA09921; Tue, 11 Dec 2001 03:53:48 -0800 (PST)
From: "Matthew Noble" <matthew.noble@riverstonenet.com>
To: "'mike shand'" <mshand@cisco.com>
Cc: "''Isis-Wg (E-mail)'" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] IS-IS Restart draft clarification
Message-ID: <000001c1823c$f1115c60$e9dc14ac@ctron.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
In-Reply-To: <4.3.2.7.2.20011207142041.033b1740@jaws.cisco.com>
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 11 Dec 2001 12:10:58 -0000
Content-Transfer-Encoding: 7bit

Mike

Could I get a further clarification on this draft.

The draft does not explicitly state what the meaning is for the expiration
of timer T2 (as opposed to it being cancelled when we have determined that
the LSP database for that level is sync'd). Can I take it that it is
considered a sucess (or about as close to a success we can get at the time)
and assume that at that point the LSP database for that level is sync'd?
This assumes that timer T3 has not yet expired when the timer T2 expires for
the given level.

Thanks
Matt

> -----Original Message-----
> From: mike shand [mailto:mshand@cisco.com]
> Sent: Friday, December 07, 2001 2:24 PM
> To: Matthew Noble
> Cc: 'Isis-Wg (E-mail)
> Subject: Re: [Isis-wg] IS-IS Restart draft clarification
>
>
> At 11:25 07/12/2001 +0000, Matthew Noble wrote:
> >Mike
> >
> >In section 4.3.1.2 second paragraph says that SPF is not run
> while T3 is
> >running, but in the 5th paragraph of the same section it
> says that when T2
> >expires/cancelled, the SPF for that level _is_ run. Now T2
> will expire under
> >normal sucessful conditions before T3 expires - so there is
> a contradiction
> >here. I am assuming that the info in the 5th paragraph is
> correct, and that
> >that in the second paragraph is wrong.
> >
> >Could you confirm that for me.
>
> Without actually looking at the draft, I think the issue is
> that once we
> have got synchronization we can safely run SPF at that level.
> Once we have
> got synchronization at both levels we can clear T3. But while
> one level is
> synchronized and the other is not we still need to keep T3 running.
>
> So yes, I think the second para is strictly wrong.
>
> But I'll look at it in more detail later.
>
>          Mike
>
>
>
> >Thanks
> >Matt
> >
> >_______________________________________________
> >Isis-wg mailing list  -  Isis-wg@external.juniper.net
> >http://external.juniper.net/mailman/listinfo/isis-wg
>
> _______________________________________________
> Isis-wg mailing list  -  Isis-wg@external.juniper.net
> http://external.juniper.net/mailman/listinfo/isis-wg
>

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec 11 07:07:39 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA16679
	for <isis-archive@lists.ietf.org>; Tue, 11 Dec 2001 07:07:39 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA60398;
	Tue, 11 Dec 2001 04:27:58 -0800 (PST)
Received: from cisco.com (mrwint.cisco.com [198.135.0.176])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA60386
	for <isis-wg@spider.juniper.net>; Tue, 11 Dec 2001 04:26:16 -0800 (PST)
Received: from mshand-w2k.cisco.com (ams-clip-vpn-dhcp4158.cisco.com [10.50.16.61])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id MAA13288;
	Tue, 11 Dec 2001 12:03:47 GMT
Message-Id: <4.3.2.7.2.20011211120123.0336b4b0@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Matthew Noble" <matthew.noble@riverstonenet.com>
From: mike shand <mshand@cisco.com>
Subject: RE: [Isis-wg] IS-IS Restart draft clarification
Cc: "''Isis-Wg (E-mail)'" <isis-wg@spider.juniper.net>
In-Reply-To: <000001c1823c$f1115c60$e9dc14ac@ctron.com>
References: <4.3.2.7.2.20011207142041.033b1740@jaws.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 11 Dec 2001 12:04:08 +0000

At 12:10 11/12/2001 +0000, Matthew Noble wrote:
>Mike
>
>Could I get a further clarification on this draft.
>
>The draft does not explicitly state what the meaning is for the expiration
>of timer T2 (as opposed to it being cancelled when we have determined that
>the LSP database for that level is sync'd). Can I take it that it is
>considered a sucess (or about as close to a success we can get at the time)
>and assume that at that point the LSP database for that level is sync'd?

Yes. T2 expiration indicates that we have given up on waiting for 
synchronization. This "shouldn't happen", but of course there may be 
pathological conditions where it does, and hence we have to have some way 
of avoiding waiting for ever.

>This assumes that timer T3 has not yet expired when the timer T2 expires for
>the given level.

Yes, in many cases T3 will expire before T2 does.

         Mike



>Thanks
>Matt
>
> > -----Original Message-----
> > From: mike shand [mailto:mshand@cisco.com]
> > Sent: Friday, December 07, 2001 2:24 PM
> > To: Matthew Noble
> > Cc: 'Isis-Wg (E-mail)
> > Subject: Re: [Isis-wg] IS-IS Restart draft clarification
> >
> >
> > At 11:25 07/12/2001 +0000, Matthew Noble wrote:
> > >Mike
> > >
> > >In section 4.3.1.2 second paragraph says that SPF is not run
> > while T3 is
> > >running, but in the 5th paragraph of the same section it
> > says that when T2
> > >expires/cancelled, the SPF for that level _is_ run. Now T2
> > will expire under
> > >normal sucessful conditions before T3 expires - so there is
> > a contradiction
> > >here. I am assuming that the info in the 5th paragraph is
> > correct, and that
> > >that in the second paragraph is wrong.
> > >
> > >Could you confirm that for me.
> >
> > Without actually looking at the draft, I think the issue is
> > that once we
> > have got synchronization we can safely run SPF at that level.
> > Once we have
> > got synchronization at both levels we can clear T3. But while
> > one level is
> > synchronized and the other is not we still need to keep T3 running.
> >
> > So yes, I think the second para is strictly wrong.
> >
> > But I'll look at it in more detail later.
> >
> >          Mike
> >
> >
> >
> > >Thanks
> > >Matt
> > >
> > >_______________________________________________
> > >Isis-wg mailing list  -  Isis-wg@external.juniper.net
> > >http://external.juniper.net/mailman/listinfo/isis-wg
> >
> > _______________________________________________
> > Isis-wg mailing list  -  Isis-wg@external.juniper.net
> > http://external.juniper.net/mailman/listinfo/isis-wg
> >

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec 11 09:34:02 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA17890
	for <isis-archive@lists.ietf.org>; Tue, 11 Dec 2001 09:33:59 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA61006;
	Tue, 11 Dec 2001 06:53:58 -0800 (PST)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA60994
	for <isis-wg@spider.juniper.net>; Tue, 11 Dec 2001 06:52:52 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734290122FF63@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'nabendu das'" <dasnabendu@yahoo.com>,
        Jeff Parker
	 <jparker@axiowave.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Mib Query
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 11 Dec 2001 09:30:16 -0500

> Hello,
> one Query regarding IISIS-mib-6
> 
> isisCircLevelHelloTimer OBJECT-TYPE
>          SYNTAX Integer32 (10..600000)
>          MAX-ACCESS read-create
>          STATUS current
>          DESCRIPTION
>              "Maximum period, in milliseconds, between
> IIH PDUs on multiaccess networks at this level for
> LANs. The value at level 1 is used as the period
> between Hellos on point to point circuits.  Setting
> this value at level 2 on a point to point circuit will
> result in an error of InconsistentValue. 
> This object follows the resettingTimer behaviour."
>          REFERENCE "{ISIS.aoi iSISHelloTimer (45)}"
>  
> Now my question is
> "The value at level 1 is used as the period between
> Hellos on point to point circuits" & why setting the
> value at level 2 on a point-to-point circuits will
> result in an error of Inconsistentvalue, & in that
> case what will be the Hello timer value for
> point-to-point circuits at level 2. Because nowhere in
> the mib i have found any timer for that purpose, i
> mean HEllo timer for point-to-point citcuits at
> level2.
> 
> definitaly we can have a point-to-point circuits at
> level 2, then what value should we put for the Hello
> timer for that purpose, and if we put the same value
> as isisHelloTimer, why that value will be an
> Inconsistent value. plz help;
> 
> thanking u in advance.

Nabendu -
	On a LAN, an IS will send both L1 and L2 hellos.
On a p2p circuit, it will send only one.  We need to
have a way to define that period.  I see the choices
as
	L1 timer
	L2 timer
	New p2p timer

I chose the first and attempted to document that 
choice.  If you can suggest text that will make 
the choice clearer, I will be happy to add it.

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Tue Dec 11 15:46:37 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24602
	for <isis-archive@lists.ietf.org>; Tue, 11 Dec 2001 15:46:34 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA62503;
	Tue, 11 Dec 2001 13:06:58 -0800 (PST)
Received: from ws1-7.us4.outblaze.com (205-158-62-57.outblaze.com [205.158.62.57])
	by external.juniper.net (8.9.3/8.9.3) with SMTP id NAA62491
	for <isis-wg@spider.juniper.net>; Tue, 11 Dec 2001 13:05:39 -0800 (PST)
Received: (qmail 25035 invoked by uid 1001); 11 Dec 2001 20:43:14 -0000
Message-ID: <20011211204314.25034.qmail@mail.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 ws1-7.us4.outblaze.com for [169.144.118.138] via web-mailer
    on Wed, 12 Dec 2001 04:43:13 +0800
From: "mie lau" <sam_isis@usa.com>
To: isis-wg@spider.juniper.net
Subject: [Isis-wg] test : please ignore
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 12 Dec 2001 04:43:13 +0800
Content-Transfer-Encoding: 7bit


-- 

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


1 cent a minute calls anywhere in the U.S.!

http://www.getpennytalk.com/cgi-bin/adforward.cgi?p_key=RG9853KJ&url=http://www.getpennytalk.com


_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec 12 16:57:41 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA19396
	for <isis-archive@lists.ietf.org>; Wed, 12 Dec 2001 16:57:40 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA68682;
	Wed, 12 Dec 2001 14:15:59 -0800 (PST)
Received: from Thor.Adtech-Inc.COM (Thor.Adtech-Inc.COM [63.165.80.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA68667
	for <isis-wg@spider.juniper.net>; Wed, 12 Dec 2001 14:14:20 -0800 (PST)
Received: from apollo.adtech-inc.com (apollo.adtech-inc.com [10.12.0.17])
	by Thor.Adtech-Inc.COM (8.12.1/8.12.1) with ESMTP id fBCLpj3x008363
	for <isis-wg@spider.juniper.net>; Wed, 12 Dec 2001 11:51:46 -1000 (HST)
Received: by apollo.adtech-inc.com with Internet Mail Service (5.5.2653.19)
	id <YP1X03NP>; Wed, 12 Dec 2001 11:57:30 -1000
Message-ID: <8AC36D3167EED41184C800508BD9540501EE3CA3@apollo.adtech-inc.com>
From: "Chan, Chung Ming" <Ming.Chan@SpirentCom.COM>
To: "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
Cc: "Chan, Chung Ming" <Ming.Chan@SpirentCom.COM>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="ISO-8859-1"
Subject: [Isis-wg] State transition diagram??
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 12 Dec 2001 11:57:29 -1000

Hi,
	Does anyone know where I can find a state transition diagram or
table for describing ISO-10589?
	Like in a lot of ITU's spec, there is SDL diagram to describe the
state transition.
	Or is there anything like that exists?

	Thanks,


Ming


_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 03:36:16 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA28260
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 03:36:15 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA95839;
	Mon, 17 Dec 2001 00:54:59 -0800 (PST)
Received: from bart.cwnt.com ([192.116.246.129])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA95827
	for <isis-wg@spider.juniper.net>; Mon, 17 Dec 2001 00:53:14 -0800 (PST)
X-MimeOLE: Produced By Microsoft Exchange V6.0.4712.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="windows-1255"
Message-ID: <95734BD21894AC4B9AEF464C5A2985EA5C9D49@bart.cwnt.com>
Thread-Topic: isisCircAdjChanges and isisSysOwnLSPPurges
Thread-Index: AcGG1QgUvCDxlPHlRQSefDt8DnPJVw==
From: "Shmuel Froimovich" <shmulik@cwnt.com>
To: "isis-wg (E-mail)" <isis-wg@spider.juniper.net>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by external.juniper.net id AAA95828
Subject: [Isis-wg] isisCircAdjChanges and isisSysOwnLSPPurges
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 17 Dec 2001 10:30:06 +0200
Content-Transfer-Encoding: 8bit

Hi,

The isisCircAdjChanges field is described in the MIB as "the number of
times an adjacency state change has occurred on this circuit."

However, the user might be more interested in the number of times an
adjacency went in and out of the "up" state.
It may not be useful to include adjacency state changes into "init" or
"down" in this sum.
Add to this the 3-way-handshake and you may add some more state changes.

For example, when an adjacency goes up, it will traverse through the
states "down", "init" and "up".  When it goes down, it will go through
"init" and "down". This will result in 5 state changes instead of two
(which actually interest the user).

While we're at it, consider the field isisSysOwnLSPPurges which
describes the "number of times a zero-age copy of the system's own LSP
is received from some other node".
The counter's purpose is to indicate abnormal behaviors and warn against
problems such as miss-configurations.
Do we include also the DR purges? (a new DR purges the old DR's LSPs).
This might render the counter useless for warning against network
problems.

Your thoughts?

Thanks,
Shmulik.

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 17:40:07 2001
Received: from new-spider.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20797
	for <isis-archive@lists.ietf.org>; Mon, 17 Dec 2001 17:40:06 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by new-spider.juniper.net (8.11.6/8.11.6) with ESMTP id fBHMPIX01449;
	Mon, 17 Dec 2001 14:25:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@new-spider.juniper.net
Errors-To: isis-wg-admin@new-spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 17:41:12 2001
Received: from new-spider.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20841
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 17:41:10 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by new-spider.juniper.net (8.11.6/8.11.6) with ESMTP id fBHMawX01521;
	Mon, 17 Dec 2001 14:36:58 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA19123
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 16:55:28 -0800 (PST)
Received: from zcars04f.ca.nortel.com (zcars04f.ca.nortel.com [47.129.242.57])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB50XBd29780
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 19:33:11 -0500 (EST)
Received: from zmers013 (actually zmers013.ca.nortel.com) 
          by zcars04f.ca.nortel.com; Tue, 4 Dec 2001 19:33:36 -0500
Received: from mailhost.BayNetworks.COM (actually ns2.baynetworks.com) 
          by zmers013; Tue, 4 Dec 2001 19:33:33 -0500
Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) 
          by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id QAA09959;
          Tue, 4 Dec 2001 16:22:28 -0800 (PST)
Received: from lead.engeast (lead [192.32.226.44]) 
          by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) 
          with ESMTP id TAA08784; Tue, 4 Dec 2001 19:33:22 -0500 for
Received: from nortelnetworks.com (localhost [127.0.0.1]) 
          by lead.engeast (8.9.3+Sun/8.9.1) with ESMTP id TAA27359;
          Tue, 4 Dec 2001 19:33:21 -0500 (EST)
Message-ID: <3C0D6B51.7EBB951D@nortelnetworks.com>
From: "Rajesh Saluja" <rsaluja@nortelnetworks.com>
X-Mailer: Mozilla 4.61 [en] (X11; U; SunOS 5.7 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Tony Przygienda <prz@redback.com>
CC: "Philip Christian" <christi@nortelnetworks.com>,
        "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
        "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "Rajesh Saluja" <rsaluja@nortelnetworks.com>
Subject: Re: [Isis-wg] Concerns with 3-way-handshake
References: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com> <3C0D12CA.2B982FCB@redback.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Orig: <rsaluja@americasm06.nt.com>
Sender: isis-wg-admin@new-spider.juniper.net
Errors-To: isis-wg-admin@new-spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 04 Dec 2001 19:33:21 -0500
Content-Transfer-Encoding: 7bit

>
>
> >From my vintage, yes, it should be fixed, maybe as simply as saying that
> three-way-hello capable routers drop ISHs and do not send them ?  The
> very details of 1195 slip my mind right now but that should not cause
> any backwards capability problems?
>
>     something is definitely worth an addition to the 3-way-hello draft
>
>     -- tony

I agree with Philip's concerns. Will the following modifications be
acceptable to the group:
1. As Tony suggested, say that  three-way-hello capable routers drop ISHs
and do not send them.
2. Reword SONET protection to SONET reprovisioning.
3. Allowing length of option from 1 (not 5) to 17 octets so that it can work
with old three way implementations.

If that's the case, I can add these and submit version 0.4.

Best regards,
Rajesh


_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 17:51:26 2001
Received: from new-spider.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA20968
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 17:51:25 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by new-spider.juniper.net (8.11.6/8.11.6) with ESMTP id fBHMlIX01592;
	Mon, 17 Dec 2001 14:47:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@new-spider.juniper.net
Errors-To: isis-wg-admin@new-spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 18:01:43 2001
Received: from new-spider.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21163
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 18:01:42 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by new-spider.juniper.net (8.11.6/8.11.6) with ESMTP id fBHMvAX01674;
	Mon, 17 Dec 2001 14:57:10 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by new-spider.juniper.net (8.11.6/8.11.6) with ESMTP id fBHMhxX01558
	for <isis-wg@spider.juniper.net>; Mon, 17 Dec 2001 14:43:59 -0800 (PST)
	(envelope-from dkatz@juniper.net)
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 fBHMeK635054;
	Mon, 17 Dec 2001 14:40:20 -0800 (PST)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost)
	by cirrus.juniper.net (8.11.6/8.11.6) id fBHMeCq11122;
	Mon, 17 Dec 2001 14:40:12 -0800 (PST)
	(envelope-from dkatz@cirrus.juniper.net)
Message-Id: <200112172240.fBHMeCq11122@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: rsaluja@nortelnetworks.com
CC: prz@redback.com, christi@nortelnetworks.com, isis-wg@spider.juniper.net,
        rsaluja@nortelnetworks.com
In-reply-to: <3C0D6B51.7EBB951D@nortelnetworks.com>
	(rsaluja@nortelnetworks.com)
Subject: Re: [Isis-wg] Concerns with 3-way-handshake
References: <4103264BC8D3D51180B7002048400C4507138D@zhard0jd.europe.nortel.com> <3C0D12CA.2B982FCB@redback.com> <3C0D6B51.7EBB951D@nortelnetworks.com>
Sender: isis-wg-admin@new-spider.juniper.net
Errors-To: isis-wg-admin@new-spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 17 Dec 2001 14:40:12 -0800 (PST)

Hm, another old message.  Something got unstuck somewhere.

   From: "Rajesh Saluja" <rsaluja@nortelnetworks.com>
   X-Accept-Language: en
   CC: "Philip Christian" <christi@nortelnetworks.com>,
      "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>,
      "'dkatz@juniper.net'" <dkatz@juniper.net>,
      "Rajesh Saluja" <rsaluja@nortelnetworks.com>
   Content-Type: text/plain; charset=us-ascii
   X-Orig: <rsaluja@americasm06.nt.com>
   Sender: isis-wg-admin@new-spider.juniper.net
   X-BeenThere: isis-wg@external.juniper.net
   X-Mailman-Version: 2.0rc1
   Precedence: bulk
   List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
   List-Post: <mailto:isis-wg@external.juniper.net>
   List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	   <mailto:isis-wg-request@external.juniper.net?subject=subscribe>
   List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
   List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	   <mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
   List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
   Date: Tue, 04 Dec 2001 19:33:21 -0500

   >
   >
   > >From my vintage, yes, it should be fixed, maybe as simply as saying that
   > three-way-hello capable routers drop ISHs and do not send them ?  The
   > very details of 1195 slip my mind right now but that should not cause
   > any backwards capability problems?
   >
   >     something is definitely worth an addition to the 3-way-hello draft
   >
   >     -- tony

   I agree with Philip's concerns. Will the following modifications be
   acceptable to the group:
   1. As Tony suggested, say that  three-way-hello capable routers drop ISHs
   and do not send them.
   2. Reword SONET protection to SONET reprovisioning.
   3. Allowing length of option from 1 (not 5) to 17 octets so that it can work
   with old three way implementations.

   If that's the case, I can add these and submit version 0.4.

   Best regards,
   Rajesh


   _______________________________________________
   Isis-wg mailing list  -  Isis-wg@external.juniper.net
   http://external.juniper.net/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 18:11:29 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21303
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 18:11:29 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBHN7IM01879;
	Mon, 17 Dec 2001 15:07:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@new-spider.juniper.net
Errors-To: isis-wg-admin@new-spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 18:32:15 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21530
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 18:32:14 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBHNRHU02059;
	Mon, 17 Dec 2001 15:27:17 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 18:52:26 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA21739
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 18:52:25 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBHNmIU02173;
	Mon, 17 Dec 2001 15:48:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 19:13:31 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22048
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 19:13:31 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI09IU02291;
	Mon, 17 Dec 2001 16:09:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 19:35:38 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22219
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 19:35:37 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI0UIU02420;
	Mon, 17 Dec 2001 16:30:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 19:55:43 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA22366
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 19:55:42 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI0pHU02542;
	Mon, 17 Dec 2001 16:51:17 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 20:20:35 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22585
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 20:20:35 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI1BIU02712;
	Mon, 17 Dec 2001 17:11:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 20:32:05 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA22735
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 20:32:04 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI1RHH02862;
	Mon, 17 Dec 2001 17:27:17 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 20:57:01 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA23088
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 20:57:00 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI1lIH03038;
	Mon, 17 Dec 2001 17:47:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 21:12:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23355
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 21:12:57 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI28HH03209;
	Mon, 17 Dec 2001 18:08:17 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 21:23:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23504
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 21:23:41 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI2J2H03266;
	Mon, 17 Dec 2001 18:19:02 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI1poH03075
	for <isis-wg@spider.juniper.net>; Mon, 17 Dec 2001 17:51:50 -0800 (PST)
	(envelope-from dkatz@juniper.net)
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 fBI1pp646322
	for <isis-wg@spider.juniper.net>; Mon, 17 Dec 2001 17:51:51 -0800 (PST)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost)
	by cirrus.juniper.net (8.11.6/8.11.6) id fBI1piH12274;
	Mon, 17 Dec 2001 17:51:44 -0800 (PST)
	(envelope-from dkatz@cirrus.juniper.net)
Message-Id: <200112180151.fBI1piH12274@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: isis-wg@spider.juniper.net
Subject: [Isis-wg] Looping email
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 17 Dec 2001 17:51:44 -0800 (PST)

Our sysadmins tell me that they've halted the looping email.  Hopefully
things will calm down soon.  Sorry about that...

--Dave
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 21:34:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA23888
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 21:34:57 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI2UIH03344;
	Mon, 17 Dec 2001 18:30:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 21:57:02 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA24748
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 21:57:01 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI2pIH03465;
	Mon, 17 Dec 2001 18:51:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 22:17:04 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA24884
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 22:17:03 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI3CHH03588;
	Mon, 17 Dec 2001 19:12:17 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 22:36:36 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA25954
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 22:36:35 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI3WIH03683;
	Mon, 17 Dec 2001 19:32:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 17 22:56:55 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26190
	for <isis-archive@odin.ietf.org>; Mon, 17 Dec 2001 22:56:54 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBI3qHH03801;
	Mon, 17 Dec 2001 19:52:17 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from zcars0m9.nortelnetworks.com (zcars0m9.nortelnetworks.com [47.129.242.157])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA16594
	for <isis-wg@spider.juniper.net>; Tue, 4 Dec 2001 09:27:25 -0800 (PST)
Received: from znsgs01r.europe.nortel.com (znsgs01r.europe.nortel.com [47.137.129.92])
	by zcars0m9.nortelnetworks.com (8.11.0/8.11.0) with ESMTP id fB4H50d26014;
	Tue, 4 Dec 2001 12:05:01 -0500 (EST)
Received: from zwcwc012.europe.nortel.com (zwcwc012.europe.nortel.com [47.73.112.187])
	by znsgs01r.europe.nortel.com (Switch-2.2.0/Switch-2.2.0) with ESMTP id fB4H5XW27646;
	Tue, 4 Dec 2001 17:05:33 GMT
Received: by zwcwc012.europe.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YH6L4SQB>; Tue, 4 Dec 2001 17:04:09 -0000
Message-ID: <4103264BC8D3D51180B7002048400C45071389@zhard0jd.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@spider.juniper.net, "'dkatz@juniper.net'" <dkatz@juniper.net>,
        "'rsaluja@nortelnetworks.com'" <rsaluja@nortelnetworks.com>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C17CE5.AE75DF40"
Subject: [Isis-wg] Concerns with 3-way-handshake
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 4 Dec 2001 17:04:05 -0000

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/plain;
	charset="iso-8859-1"

I have a number of concerns and comments about the 3-way-handshake draft,
draft-ietf-isis-3way-03.txt. I'm sure I remember hearing that this draft is
about to become an RFC, although I can find no evidence of this on the RFC
editor's web page.

Here are my concerns.

This draft specifically declares itself to be useful in SONET networks
(presumably in the embedded DCC channels, although this is not stated).
However I believe that there is an area of ambiguity in it which reduces its
usefulness somewhat. The draft mentions only IIH packets, where as SONET and
SDH networks (oh yes, SDH is not mentioned either) are currently based on
CLNS and therefore the NEs transmit ISH packets too.

I understand that an old CLNS SONET/SDH node will not support three-way
handshaking anyway, and so a new neighbour would engage legacy mode anyway,
BUT....

With the advent of G.7712 vendors will be looking at implementing dual IP
and CLNS routers that are able to still interface to the old CLNS nodes, and
which also support three way handshaking. Such a new dual node may well need
to declare itself a CLNS End System, and so will be transmitting ISHs. This
will be necessary to terminate RFC 3147 encapsulated packets, for example.

The problem is that I believe that receipt of ISH packets "short circuits"
the three way handshake, and results in the adjacency coming up whether the
neighbour has received  IIHs, or not. This is my understanding of the
problem:
A is connected to B and issues an ISH.
B receives the ISH, and according to ISO 10589 section 8.2.2 creates an
adjacency of type "Initialising".
B now reports to A in the new "Point to point adjacency state" option that
the adjacency is "Initialising".
A receives this and according to the table in the draft, brings the
adjacency "up".
However B may never have received an IIH from A and so the three way
handshake has been short circuited, or have I misunderstood something?

The draft really needs to state how a router with three way handshaking
should handle receipt of an ISH from a neighbouring IS that also supports
the option.

I guess that this is not a problem for pure IP routers if they ignore ISHs,
and this could be stated.

Next concern; what happened to ISHs anyway? RFC 1195 states in section 4.4
"For point-to-point links, IS-IS requires exchange of ISO 9542 ISHs, as the
first step in establishing the link between routers. All IS-IS routers are
therefore required to transmit and receive ISO 9542 ISH packets on
point-to-point links.". There is a similar statement in section 5.1.

I am told that many implementors do not transmit ISH packets anymore, as
they cannot terminate CLNP and thus are not an CLNS End System anymore.

This seems perfectly logical to me, but, if this is the case then I think
that this draft should state it. It is the after-all going to be (hopefully)
the first RFC to actually alter the adjacency creation process from ISO
10589; RFC 1195 did not change it. If it is now okay not to transmit ISHs
then let's say so.

I think that this issues could be addressed just in a few sentences, once we
have agreed how to handle ISHs on nodes that need to. I am ready to help
with some drafting in order to help get this right.

Regards, Philip Christian.

------_=_NextPart_001_01C17CE5.AE75DF40
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.89">
<TITLE>Concerns with 3-way-handshake</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>I have a number of concerns and comments about the =
3-way-handshake draft, draft-ietf-isis-3way-03.txt. I'm sure I remember =
hearing that this draft is about to become an RFC, although I can find =
no evidence of this on the RFC editor's web page.</FONT></P>

<P><FONT SIZE=3D2>Here are my concerns.</FONT>
</P>

<P><FONT SIZE=3D2>This draft specifically declares itself to be useful =
in SONET networks (presumably in the embedded DCC channels, although =
this is not stated). However I believe that there is an area of =
ambiguity in it which reduces its usefulness somewhat. The draft =
mentions only IIH packets, where as SONET and SDH networks (oh yes, SDH =
is not mentioned either) are currently based on CLNS and therefore the =
NEs transmit ISH packets too.</FONT></P>

<P><FONT SIZE=3D2>I understand that an old CLNS SONET/SDH node will not =
support three-way handshaking anyway, and so a new neighbour would =
engage legacy mode anyway, BUT....</FONT></P>

<P><FONT SIZE=3D2>With the advent of G.7712 vendors will be looking at =
implementing dual IP and CLNS routers that are able to still interface =
to the old CLNS nodes, and which also support three way handshaking. =
Such a new dual node may well need to declare itself a CLNS End System, =
and so will be transmitting ISHs. This will be necessary to terminate =
RFC 3147 encapsulated packets, for example.</FONT></P>

<P><FONT SIZE=3D2>The problem is that I believe that receipt of ISH =
packets &quot;short circuits&quot; the three way handshake, and results =
in the adjacency coming up whether the neighbour has received&nbsp; =
IIHs, or not. This is my understanding of the problem:</FONT></P>

<P><FONT SIZE=3D2>A is connected to B and issues an ISH.</FONT>
<BR><FONT SIZE=3D2>B receives the ISH, and according to ISO 10589 =
section 8.2.2 creates an adjacency of type =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>B now reports to A in the new &quot;Point to point =
adjacency state&quot; option that the adjacency is =
&quot;Initialising&quot;.</FONT>
<BR><FONT SIZE=3D2>A receives this and according to the table in the =
draft, brings the adjacency &quot;up&quot;.</FONT>
<BR><FONT SIZE=3D2>However B may never have received an IIH from A and =
so the three way handshake has been short circuited, or have I =
misunderstood something?</FONT></P>

<P><FONT SIZE=3D2>The draft really needs to state how a router with =
three way handshaking should handle receipt of an ISH from a =
neighbouring IS that also supports the option.</FONT></P>

<P><FONT SIZE=3D2>I guess that this is not a problem for pure IP =
routers if they ignore ISHs, and this could be stated.</FONT>
</P>

<P><FONT SIZE=3D2>Next concern; what happened to ISHs anyway? RFC 1195 =
states in section 4.4 &quot;For point-to-point links, IS-IS requires =
exchange of ISO 9542 ISHs, as the first step in establishing the link =
between routers. All IS-IS routers are therefore required to transmit =
and receive ISO 9542 ISH packets on point-to-point links.&quot;. There =
is a similar statement in section 5.1.</FONT></P>

<P><FONT SIZE=3D2>I am told that many implementors do not transmit ISH =
packets anymore, as they cannot terminate CLNP and thus are not an CLNS =
End System anymore.</FONT></P>

<P><FONT SIZE=3D2>This seems perfectly logical to me, but, if this is =
the case then I think that this draft should state it. It is the =
after-all going to be (hopefully) the first RFC to actually alter the =
adjacency creation process from ISO 10589; RFC 1195 did not change it. =
If it is now okay not to transmit ISHs then let's say so.</FONT></P>

<P><FONT SIZE=3D2>I think that this issues could be addressed just in a =
few sentences, once we have agreed how to handle ISHs on nodes that =
need to. I am ready to help with some drafting in order to help get =
this right.</FONT></P>

<P><FONT SIZE=3D2>Regards, Philip Christian.</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C17CE5.AE75DF40--
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec 19 15:38:22 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA06644
	for <isis-archive@odin.ietf.org>; Wed, 19 Dec 2001 15:38:21 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBJKS2110503;
	Wed, 19 Dec 2001 12:28:02 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from hotmail.com (f175.law7.hotmail.com [216.33.237.175])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBJKRp110491
	for <isis-wg@spider.juniper.net>; Wed, 19 Dec 2001 12:27:51 -0800 (PST)
	(envelope-from sboddapa@hotmail.com)
Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC;
	 Wed, 19 Dec 2001 12:28:00 -0800
Received: from 63.104.212.252 by lw7fd.law7.hotmail.msn.com with HTTP;
	Wed, 19 Dec 2001 20:28:00 GMT
X-Originating-IP: [63.104.212.252]
From: "Suresh Boddapati" <sboddapa@hotmail.com>
To: isis-wg@spider.juniper.net
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <F175wMw8lODAStRc0JF00001b4c@hotmail.com>
X-OriginalArrivalTime: 19 Dec 2001 20:28:00.0588 (UTC) FILETIME=[A71340C0:01C188CB]
Subject: [Isis-wg] Questions on Attached Bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 19 Dec 2001 20:28:00

Hi,
I have a few questions on the usage of the Attached bit. As I understand it, 
the attached bit enables an L1 router to figure out who its closest L2 
router is.

1)Is it right to assume that the attached bit is meaningfuly only when set 
in L1 LSPs and not in L2 LSPs? If not, when would it be set in L2 LSPs?

2)Is the attached bit meaningful only in LSP Zero and not in any other LSPs? 
Section 7.2.9.2 of ISO 10589 says "regenerate its Level 1 LSP with LSP 
number zero" upon detecting a change in the attached bit status. But Section 
7.3.4.3 does not list the attached bit as one of the fields that are 
meaningful ONLY if present in LSP zero.

3) Technical Corrigendum 1 modifies subclause 7.2.9.2 and states
"...The IS considers itself attached if either
a) it can reach at least one other area using the corresponding routing 
metric or
b) it has at least one enabled reachable address prefix with the 
corresponding metric defined."

Can someone elaborate on b). Is it referring to at least one external prefix 
being advertised by the IS itself, due to say redistribution from other 
protocols?

Also, the requirement of being able to reach at least one other area is not 
clear. Consider the following example.

IS A(L1) ------IS B(L1L2)------IS C(L2)--------IS D(L1L2)-----IS E(L1)
Area X          Area X         Area X          Area X,Y       Area Y


IS A is an L1 router with manually configured area X and so on....

Even though IS B is connected to the L2 backbone, it will not advertise 
itself as attached (since it can reach only Area X) and therefore IS A 
cannot reach any system in Area Y as it will not install a default route 
pointing towards IS B. Is this a bad configuration? Am I missing something?

Thanks a bunch in advance.

Regards,

Suresh

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 20 09:43:47 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA07943
	for <isis-archive@lists.ietf.org>; Thu, 20 Dec 2001 09:43:46 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBKEf1115376;
	Thu, 20 Dec 2001 06:41:01 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBKEeG115364
	for <isis-wg@spider.juniper.net>; Thu, 20 Dec 2001 06:40:16 -0800 (PST)
	(envelope-from bertcameron@rogers.com)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fBKEeV241983
	for <isis-wg@juniper.net>; Thu, 20 Dec 2001 06:40:31 -0800 (PST)
X-JNPR-Received-From: outside
Received: from fep02-mail.bloor.is.net.cable.rogers.com ([66.185.86.72]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Thu, 20 Dec 2001 06:38:20 -0800
Received: from bert ([24.156.170.195])
          by fep02-mail.bloor.is.net.cable.rogers.com
          (InterMail vM.5.01.04.02 201-253-122-122-102-20011128) with SMTP
          id <20011220144009.TXND345551.fep02-mail.bloor.is.net.cable.rogers.com@bert>
          for <isis-wg@juniper.net>; Thu, 20 Dec 2001 09:40:09 -0500
Message-ID: <006501c18964$461990a0$0200a8c0@bert>
From: "Bert Cameron" <bertcameron@rogers.com>
To: <isis-wg@juniper.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0062_01C1893A.5D21F6E0"
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
X-OriginalArrivalTime: 20 Dec 2001 14:38:20.0765 (UTC) FILETIME=[F88A10D0:01C18963]
Subject: [Isis-wg] (no subject)
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 20 Dec 2001 09:40:30 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_0062_01C1893A.5D21F6E0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

who isis

------=_NextPart_000_0062_01C1893A.5D21F6E0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2600.0" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>who isis</FONT></DIV></BODY></HTML>

------=_NextPart_000_0062_01C1893A.5D21F6E0--

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 21 12:29:57 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27290
	for <isis-archive@lists.ietf.org>; Fri, 21 Dec 2001 12:29:55 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBLHQh123074;
	Fri, 21 Dec 2001 09:26:43 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBLHLA123045
	for <isis-wg@spider.juniper.net>; Fri, 21 Dec 2001 09:21:10 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B3820006295734290123000C@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Manral, Vishwas'" <VishwasM@netplane.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 21 Dec 2001 12:20:51 -0500

 
> Jeff,
> 
> I had a few doubts/suggestion to make regarding the draft. 
 
Thanks.  I am forwarding to the list to keep the WG posted
on the changes you have suggested.  The letter ends with
a current list of 07 changes and my todo list.  

> 1. The isisAreaAddr description given in the overview section 
> is not clear.
> I think it should be mentioned area addresses in Level 1 
> LSP's, else first
> reading it gets confused with isisISAdjAreaAddr.

I'm not sure what you are suggesting here.  The MIB 
currently includes the following introduction

	-- The Level 1 Area Address Table

	-- The Level 1 Area Address Table contains the
	-- union of the sets of area addresses reported in all Level 1
	-- LSPs received by this Intermediate System.

Are you suggesting this is too much or too little?
If too little, could you provide suggested text?

> 2. What is the default behaviour of isisSysType?
> May be L1/L2 would be the desired default behaviour.

Good idea.  Done

> 3. Shouldn't isisSysMaxLSPGenInt be less than MaxAge(1200). 
> May be we could
> define a texual convention for this and declare for both 
> isisSysMaxLSPGenInt
> and isisMinLSPGenInt.

While MaxAge is specified in the protocol, there are vendors
who do not restrict the lifetime of the LSPs to this value.

> 4. isisSysMaxAreaAddress shouldnt a value of 0 be accepted too. It is
> regarded to be equiv to 3 right?

In a PDU on the wire MaxArea 0 means 3.  
I see no reason to preserve this behavior in the MIB.  

> 5. What abt packets dropped due to differences in authType.

I have added a new notification and a new counter

> 6. What does isisSummAddrAdminState signify(does it signify 
> from or to) ie
> when it is L1, is the table used to summarize to or from the L1?

I have added text.  See if it is clearer now.

> 7. In the isisCirc table, we have no isisCircentry9 - 13. 
> Guess its a typo?

Fixed.

> 8. What does functional multicast address mean?

You are asking about the definition of the object below.

I have no idea what this is about, and have done a quick
pass through 10589 without enlightenment.  Is there someone
out there who can shed light on this?  

     isisCircMCAddr OBJECT-TYPE
         SYNTAX INTEGER{
             group (1),
             functional (2)
             }
         MAX-ACCESS read-create
         STATUS current
         DESCRIPTION
             "Specifies which type of multicast address will
             be used for sending HELLO PDUs on this
             circuit."
         DEFVAL { group }
     ::= { isisCircEntry 16 }

> 
> 9. Wouldnt it be nice to keep a count of External routes, L1 
> routes , L2
> routes. Or may be how many of TLV 128 and how many 130? I am 
> just trying to
> draw a parallel with OSPF.

I have added to my todo list.  I won't try to add them this morning.  
 
> 10. What is the summary area-default metric. I feel thats not 
> required. If
> it matches more than one dest we can have the min cost of al 
> the dest it
> encompasses. Shldnt there be another field to tell when summ 
> area default
> metric is to be used, if thats required?

The term Default has an unusaul meaning in the protocol.  
I have removed "default" and "Def" from the names of metrics
where they appear, and added text to better describe the meaning
of "DefaultMetric" in ISIS.  The DefaultMetric TC is left as is.

> 11. What does isisSysL1state and SysL2 state OFF mean? What 
> is the relation to isisSysSetOverload?(If any)
> 
> Thanks,
> Vishwas

There is a notion of an overload bit which is used to signal
that a router is low on memory, and thus not to be trusted.

In OSPF, we don't use a router as a transit node until it has
finished the DataBase exchange.  In ISIS, some implementations
allow the administrator to bring up the router with the overload
bit set for a given time period.  This gives the router a 
chance to become synchronized.  

I have added text to the isisSysL1State and L2State definitions:
see if that makes things clearer.  

Vishwas -

I will send you a new copy of version 07, with the changes noted
below for your review.  I'm always happy to send out a current 
version of the mib for review.  

I will try to sort out the traps on Protocol Supported before
sending version 07 to the IETF.  

- jeff parker
- axiowave networks.  

-- Changes in version 07.
--      Added TE variables suggested by Satish Dattatri
--      Added traps culled from
--              Alarms in 10589
--              MTU Mismatch (Len G.)
--              Auth vailuer  (Vishwas)
--      Importing Inet definitions from INET-ADDRESS-MIB
--      Clarify the handling of isisManAreaAddrExistState
--      Removed isisCircLevelCircID: duplicates isisCircPtToPtCircID
--      Added UNITS clauses for timers and frame counters
--      Added default value for isisSysType
--      Added system counter isisSysAuthTypeFails
--      Revised numbering in isisCircTable
--      Removed the use of "Default" in definitions of metrics
--              To easy to confuse with the metric to be used by default
--      Added text to describe behavior of isisSysL1State and L2State

ToDo List
        Add timer between SPF computations
        The Hello Timer is measured in Milliseconds, but
                the HoldTimer for the Adjacency is measured in seconds.
                Change to milleseconds? 1
        Add trap for PLSP with no Protocol Supported TLV
        Add trap for LSP with no matching ProtSupported Flag
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 21 13:48:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29165
	for <isis-archive@odin.ietf.org>; Fri, 21 Dec 2001 13:48:57 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBLIjB123455;
	Fri, 21 Dec 2001 10:45:11 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBLINZ123353
	for <isis-wg@spider.juniper.net>; Fri, 21 Dec 2001 10:23:35 -0800 (PST)
	(envelope-from jlearman@cisco.com)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fBLINx922821;
	Fri, 21 Dec 2001 13:23:59 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AAI30578;
	Fri, 21 Dec 2001 13:23:50 -0500 (EST)
Message-Id: <4.3.2.7.2.20011221131041.053f6f08@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] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Cc: "'Manral, Vishwas'" <VishwasM@netplane.com>,
        "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
In-Reply-To: <EB5FFC72F183D411B3820006295734290123000C@r2d2.axiowave.com
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 21 Dec 2001 13:21:19 -0500


I'm surprised that the default for level would be L1+L2.  If
most ISIS routers are deployed as L1+L2 routers, then either
they're only used in small domains or else they're not being
deployed properly.  I would expect the typical router to be
L1, with L1+L2 routers in much smaller quantities.  It's
supposed to be hierarchical and scalable, after all.

Even if today, ISIS routers tend to be L1+L2, does that mean
we should make it the default?  Shouldn't we be encouraging
the proper, hierarchical deployment?  Or am I missing something?

More minor comments below.

At 12:20 PM 12/21/2001, Jeff Parker wrote in response to Vishwas Manral:
[snip]
>> 3. Shouldn't isisSysMaxLSPGenInt be less than MaxAge(1200). 
>> May be we could
>> define a texual convention for this and declare for both 
>> isisSysMaxLSPGenInt
>> and isisMinLSPGenInt.
>
>While MaxAge is specified in the protocol, there are vendors
>who do not restrict the lifetime of the LSPs to this value.

Furthermore, MaxAge is a very reasonable default setting for this
parameter.  Increasing it increases the load, but with the advantage
only that certain relatively rare problems are corrected sooner.

>> 4. isisSysMaxAreaAddress shouldnt a value of 0 be accepted too. It is
>> regarded to be equiv to 3 right?
>
>In a PDU on the wire MaxArea 0 means 3.  
>I see no reason to preserve this behavior in the MIB.  

It would be reasonable if we wanted a way to force 0 or 3 to be used
in the PDUs.  This would only be valuable because of a problem in
some router, I suppose.  I don't feel strongly on this, just my $0.02.

Regards,
Jeff

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 21 16:22:40 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA02365
	for <isis-archive@odin.ietf.org>; Fri, 21 Dec 2001 16:22:39 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBLLKD124140;
	Fri, 21 Dec 2001 13:20:13 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBLL0m124030
	for <isis-wg@spider.juniper.net>; Fri, 21 Dec 2001 13:00:48 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B3820006295734290123000E@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Jeff Learman'" <jlearman@cisco.com>,
        Jeff Parker
	 <jparker@axiowave.com>
Cc: "'Manral, Vishwas'" <VishwasM@netplane.com>,
        "IS-IS-WG (E-mail)"
	 <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 21 Dec 2001 16:00:27 -0500

> Even if today, ISIS routers tend to be L1+L2, does that mean
> we should make it the default?  Shouldn't we be encouraging
> the proper, hierarchical deployment?  Or am I missing something?

Jeff -
	Good point.  I'll accept your proposal.  

> >> 3. Shouldn't isisSysMaxLSPGenInt be less than MaxAge(1200). 
> >> May be we could
> >> define a texual convention for this and declare for both 
> >> isisSysMaxLSPGenInt
> >> and isisMinLSPGenInt.
> >
> >While MaxAge is specified in the protocol, there are vendors
> >who do not restrict the lifetime of the LSPs to this value.
> 
> Furthermore, MaxAge is a very reasonable default setting for this
> parameter.  Increasing it increases the load, but with the advantage
> only that certain relatively rare problems are corrected sooner.

Right.  Vishwas' suggestion was not to change the default,
but to change the permissible range.  I will leave that 
unchanged, as 

     isisSysMaxLSPGenInt OBJECT-TYPE
         SYNTAX Integer32 (1..65535)

The DEFVAL of isisSysMaxLSPGenInt has been 900 seconds all along.  
 
> >> 4. isisSysMaxAreaAddress shouldnt a value of 0 be accepted 
> too. It is
> >> regarded to be equiv to 3 right?
> >
> >In a PDU on the wire MaxArea 0 means 3.  
> >I see no reason to preserve this behavior in the MIB.  
> 
> It would be reasonable if we wanted a way to force 0 or 3 to be used
> in the PDUs.  This would only be valuable because of a problem in
> some router, I suppose.  I don't feel strongly on this, just my $0.02.
> 
> Regards,
> Jeff

Interesting point, but if we need this functionality, I would
rather create a new knob for this, rather than encoding it
in some behavoir that you will have to explain to folks for
the next 20 years.

Anyone who needs to control the generation of 0 vs 3 for MaxArea?

- jeff parker
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 21 17:01:33 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA02923
	for <isis-archive@odin.ietf.org>; Fri, 21 Dec 2001 17:01:32 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBLLx7124357;
	Fri, 21 Dec 2001 13:59:07 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBLLnr124306
	for <isis-wg@spider.juniper.net>; Fri, 21 Dec 2001 13:49:53 -0800 (PST)
	(envelope-from jlearman@cisco.com)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fBLLoM102506;
	Fri, 21 Dec 2001 16:50:22 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (dhcp-64-102-83-135.cisco.com [64.102.83.135])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AAI34766;
	Fri, 21 Dec 2001 16:50:13 -0500 (EST)
Message-Id: <4.3.2.7.2.20011221164956.01d04ef8@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] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Cc: Jeff Parker <jparker@axiowave.com>,
        "'Manral, Vishwas'" <VishwasM@netplane.com>,
        "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
In-Reply-To: <EB5FFC72F183D411B3820006295734290123000E@r2d2.axiowave.com
 >
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 21 Dec 2001 16:50:06 -0500


OK.  Agreed.

At 04:00 PM 12/21/2001, Jeff Parker wrote:
>> Even if today, ISIS routers tend to be L1+L2, does that mean
>> we should make it the default?  Shouldn't we be encouraging
>> the proper, hierarchical deployment?  Or am I missing something?
>
>Jeff -
>        Good point.  I'll accept your proposal.  
>
>> >> 3. Shouldn't isisSysMaxLSPGenInt be less than MaxAge(1200). 
>> >> May be we could
>> >> define a texual convention for this and declare for both 
>> >> isisSysMaxLSPGenInt
>> >> and isisMinLSPGenInt.
>> >
>> >While MaxAge is specified in the protocol, there are vendors
>> >who do not restrict the lifetime of the LSPs to this value.
>> 
>> Furthermore, MaxAge is a very reasonable default setting for this
>> parameter.  Increasing it increases the load, but with the advantage
>> only that certain relatively rare problems are corrected sooner.
>
>Right.  Vishwas' suggestion was not to change the default,
>but to change the permissible range.  I will leave that 
>unchanged, as 
>
>     isisSysMaxLSPGenInt OBJECT-TYPE
>         SYNTAX Integer32 (1..65535)
>
>The DEFVAL of isisSysMaxLSPGenInt has been 900 seconds all along.  
> 
>> >> 4. isisSysMaxAreaAddress shouldnt a value of 0 be accepted 
>> too. It is
>> >> regarded to be equiv to 3 right?
>> >
>> >In a PDU on the wire MaxArea 0 means 3.  
>> >I see no reason to preserve this behavior in the MIB.  
>> 
>> It would be reasonable if we wanted a way to force 0 or 3 to be used
>> in the PDUs.  This would only be valuable because of a problem in
>> some router, I suppose.  I don't feel strongly on this, just my $0.02.
>> 
>> Regards,
>> Jeff
>
>Interesting point, but if we need this functionality, I would
>rather create a new knob for this, rather than encoding it
>in some behavoir that you will have to explain to folks for
>the next 20 years.
>
>Anyone who needs to control the generation of 0 vs 3 for MaxArea?
>
>- jeff parker

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 21 19:27:02 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05374
	for <isis-archive@odin.ietf.org>; Fri, 21 Dec 2001 19:27:01 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBM0Nr125056;
	Fri, 21 Dec 2001 16:23:54 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBM0CX125000
	for <isis-wg@spider.juniper.net>; Fri, 21 Dec 2001 16:12:34 -0800 (PST)
	(envelope-from naiming@redback.com)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id E518A4BA213; Fri, 21 Dec 2001 16:12:56 -0800 (PST)
To: Jeff Learman <jlearman@cisco.com>
Cc: Jeff Parker <jparker@axiowave.com>,
        "'Manral, Vishwas'" <VishwasM@netplane.com>,
        "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
Subject: Re: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt 
In-reply-to: Mail from Jeff Learman <jlearman@cisco.com> 
 dated Fri, 21 Dec 2001 13:21:19 EST
 <4.3.2.7.2.20011221131041.053f6f08@dingdong.cisco.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011222001256.E518A4BA213@prattle.redback.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 21 Dec 2001 16:12:56 -0800

 ]
 ]I'm surprised that the default for level would be L1+L2.  If
 ]most ISIS routers are deployed as L1+L2 routers, then either
 ]they're only used in small domains or else they're not being
 ]deployed properly.  I would expect the typical router to be
 ]L1, with L1+L2 routers in much smaller quantities.  It's
 ]supposed to be hierarchical and scalable, after all.
 ]
 ]Even if today, ISIS routers tend to be L1+L2, does that mean
 ]we should make it the default?  Shouldn't we be encouraging
 ]the proper, hierarchical deployment?  Or am I missing something?
 ]

I don't think the issue is the number of routers in which level
determines the default setting, or the default setting means people
actually runs isis in both level-1/level-2. The reason some vendors
(correctly) use level-1/level-2 as default is because a user can
drop the router in any topology which will work.

If the L1/L2 router is in pure L1 area, then it behaves like a L1
router since no neighbor will talk with it with L2 packets. If the
L1/L2 router is in the "border" position, then its perfect. If the
L1/L2 router is in a pure L2 domain, then it only works like a L2
router.

There is a rare pathological case if the default is L1 for IS-IS
and no one bothers to change it: all the routers in the network are
in one area and running L1/L2 mode, if the user forgets to change the
level setting and drop this new L1 router in the middle, it will think
all the neighbors as gateways and it may blackhole the traffic. The
default of L1/L2 comes handy in this case.

thanks.
- Naiming
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Sun Dec 23 08:25:25 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA25918
	for <isis-archive@odin.ietf.org>; Sun, 23 Dec 2001 08:25:25 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBNDM8138024;
	Sun, 23 Dec 2001 05:22:08 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBMHaw132305
	for <isis-wg@spider.juniper.net>; Sat, 22 Dec 2001 09:36:59 -0800 (PST)
	(envelope-from jlearman@cisco.com)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fBMHbW302446;
	Sat, 22 Dec 2001 12:37:33 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (rtp-vpn1-2.cisco.com [10.82.224.2])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AAI41451;
	Sat, 22 Dec 2001 12:37:24 -0500 (EST)
Message-Id: <4.3.2.7.2.20011222122747.01d61790@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Naiming Shen <naiming@redback.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt 
Cc: Jeff Parker <jparker@axiowave.com>,
        "'Manral, Vishwas'" <VishwasM@netplane.com>,
        "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
In-Reply-To: <20011222001256.E518A4BA213@prattle.redback.com>
References: <Mail from Jeff Learman <jlearman@cisco.com>
 <4.3.2.7.2.20011221131041.053f6f08@dingdong.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 22 Dec 2001 12:37:15 -0500


I believe that defaults should be optimized for when one is deploying
a large number of systems, rather than just one.  But minimizing the
settings that must be made when deploying a single router in an
existing network is also reasonable.

I think it's more important to make it easy to put together networks
that are configured correctly than to make it easy for networks to work
even when misconfigured, though, so I still recommend L1 as the default.

In any case, though, will this draft really affect how any vendor's
implementation will default?  Perhaps the default should be unspecified,
since there are good arguments to go either way.  (On the other hand,
this IS a standards group!)

Jeff

As usual, please note that I don't represent Cisco.

At 07:12 PM 12/21/2001, Naiming Shen wrote:
> ]
> ]I'm surprised that the default for level would be L1+L2.  If
> ]most ISIS routers are deployed as L1+L2 routers, then either
> ]they're only used in small domains or else they're not being
> ]deployed properly.  I would expect the typical router to be
> ]L1, with L1+L2 routers in much smaller quantities.  It's
> ]supposed to be hierarchical and scalable, after all.
> ]
> ]Even if today, ISIS routers tend to be L1+L2, does that mean
> ]we should make it the default?  Shouldn't we be encouraging
> ]the proper, hierarchical deployment?  Or am I missing something?
> ]
>
>I don't think the issue is the number of routers in which level
>determines the default setting, or the default setting means people
>actually runs isis in both level-1/level-2. The reason some vendors
>(correctly) use level-1/level-2 as default is because a user can
>drop the router in any topology which will work.
>
>If the L1/L2 router is in pure L1 area, then it behaves like a L1
>router since no neighbor will talk with it with L2 packets. If the
>L1/L2 router is in the "border" position, then its perfect. If the
>L1/L2 router is in a pure L2 domain, then it only works like a L2
>router.
>
>There is a rare pathological case if the default is L1 for IS-IS
>and no one bothers to change it: all the routers in the network are
>in one area and running L1/L2 mode, if the user forgets to change the
>level setting and drop this new L1 router in the middle, it will think
>all the neighbors as gateways and it may blackhole the traffic. The
>default of L1/L2 comes handy in this case.
>
>thanks.
>- Naiming

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 24 01:47:03 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06388
	for <isis-archive@lists.ietf.org>; Mon, 24 Dec 2001 01:47:03 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBO6i1142470;
	Sun, 23 Dec 2001 22:44:01 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBO6eL142448
	for <isis-wg@spider.juniper.net>; Sun, 23 Dec 2001 22:40:22 -0800 (PST)
	(envelope-from sivaa@indiatimes.com)
Received: from pong.juniper.net (pong.juniper.net [207.17.137.102])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fBO6ew210818
	for <isis-wg@juniper.net>; Sun, 23 Dec 2001 22:40:59 -0800 (PST)
X-JNPR-Received-From: outside
Received: from WS0005.indiatimes.com ([203.199.93.15]) by pong.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Sun, 23 Dec 2001 22:40:29 -0800
Received: from 192.168.57.15 (a3 [192.168.57.23])
	by WS0005.indiatimes.com (8.9.3/8.9.3) with SMTP id LAA27184;
	Mon, 24 Dec 2001 11:47:05 +0530
From: "" <sivaa@indiatimes.com>
Message-Id: <200112240617.LAA27184@WS0005.indiatimes.com>
To: "workgroup"<isis-wg@juniper.net>
CC: "Jeff Parker"<jparker@axiowave.com>,
        "Radia Perlman - Boston Center for Networking"<Radia.Perlman@Sun.COM>
X-URL: http://indiatimes.com
Content-Type: multipart/alternative;
	   boundary="=_MAILER_ATTACH_BOUNDARY1_200112241115522950390868"
MIME-Version: 1.0
X-OriginalArrivalTime: 24 Dec 2001 06:40:29.0968 (UTC) FILETIME=[E110A100:01C18C45]
Subject: [Isis-wg] External IPRA
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 24 Dec 2001 11:55:22 +0530

--=_MAILER_ATTACH_BOUNDARY1_200112241115522950390868
Content-Type: text/plain; charset=us-ascii

Hi,


Kindly clarify the following


Whether External IPRA needs to be summarized? If yes, then consider the following.


External IPRA with Internal Metric matches  Summary Address Table Entry S1. We announce S1 with what ever metric that is configured in the Summary Address Table 


Note: SA table does not have a field indicating the type of metric whether internal or external.


External IPRA with External Metric matches Summary Address Table Entry S2. What should be done now, since the metric configured in the summary Address Table does not specify whether it is internal or external can S2 now be announced for the External IPRA. Will this not violate the specification which says, that external metrics are not camparable to internal metrics?


Any help on this is greatly appreciated 


Thanks &amp; Regards


Sivakumar A
Get Your Private, Free E-mail from Indiatimes at  http://email.indiatimes.com
Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from http://www.planetm.co.in

--=_MAILER_ATTACH_BOUNDARY1_200112241115522950390868
Content-Type: text/html; charset=us-ascii

<P>Hi,</P>
<P>Kindly clarify&nbsp;the following</P>
<P>Whether External IPRA needs to be summarized? If&nbsp;yes,&nbsp;then consider the following.</P>
<P>External IPRA with Internal Metric matches &nbsp;Summary Address Table Entry S1. We announce S1 with what ever metric that is configured in the Summary Address Table </P>
<P>Note:&nbsp;SA table does not have a field indicating the type of metric whether internal or external.</P>
<P>External IPRA with External Metric matches Summary Address Table Entry S2. What should be done now, since the metric configured in the summary Address Table does not specify whether it is internal or external can S2 now be announced for the External IPRA. Will this not violate the specification which says, that external metrics are not camparable to internal metrics?</P>
<P>Any help on this is greatly appreciated&nbsp;</P>
<P>Thanks &amp; Regards</P>
<P>Sivakumar A</P>
<hr><font face="Arial" size="2"><b>Get Your Private, Free E-mail from Indiatimes at  </font><a href="http://email.indiatimes.com"><font face="Arial" size="2">http://email.indiatimes.com</font></a></b><br>Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from <A href="http://www.planetm.co.in">http://www.planetm.co.in</A>

--=_MAILER_ATTACH_BOUNDARY1_200112241115522950390868--

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 24 03:33:51 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA20918
	for <isis-archive@odin.ietf.org>; Mon, 24 Dec 2001 03:33:50 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBO8Uh142977;
	Mon, 24 Dec 2001 00:30:43 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from blush.juniper.net (colo-blush-ext.juniper.net [207.17.137.35] (may be forged))
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBO8QO142951
	for <isis-wg@spider.juniper.net>; Mon, 24 Dec 2001 00:26:24 -0800 (PST)
	(envelope-from selvarajr@future.futsoft.com)
Received: from pong.juniper.net (pong.juniper.net [207.17.137.102])
	by blush.juniper.net (8.11.2/8.11.2) with ESMTP id fBO8R1211290
	for <isis-wg@juniper.net>; Mon, 24 Dec 2001 00:27:02 -0800 (PST)
X-JNPR-Received-From: outside
Received: from fsnt.future.futsoft.com ([203.197.140.35]) by pong.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Mon, 24 Dec 2001 00:18:45 -0800
Received: from kailash.future.futsoft.com (unverified) by fsnt.future.futsoft.com
 (Content Technologies SMTPRS 2.0.15) with ESMTP id <B0001578558@fsnt.future.futsoft.com>;
 Mon, 24 Dec 2001 14:02:49 +0530
Received: from selvarajr (selvarajr.future.futsoft.com [10.4.6.32])
	by kailash.future.futsoft.com (8.11.0/8.11.0) with SMTP id fBO8IHo01611;
	Mon, 24 Dec 2001 13:48:17 +0530
Reply-To: <selvarajr@future.futsoft.com>
From: "SelvarajR" <selvarajr@future.futsoft.com>
To: "'workgroup'" <isis-wg@juniper.net>
Cc: <sivaa@indiatimes.com>
Subject: RE: [Isis-wg] External IPRA
Message-Id: <000401c18c54$fc55afa0$2006040a@future.futsoft.com>
MIME-Version: 1.0
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200
In-Reply-To: <200112240617.LAA27184@WS0005.indiatimes.com>
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0005_01C18C83.160DEBA0"
X-OriginalArrivalTime: 24 Dec 2001 08:18:45.0937 (UTC) FILETIME=[9B561A10:01C18C53]
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 24 Dec 2001 13:58:37 +0530

This is a multi-part message in MIME format.

------=_NextPart_000_0005_01C18C83.160DEBA0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

Hi Siva,
In most of the implementation Summary address metric is NOT configurable.
Its determined dynamically whenever an IPRA falls under that. The LEAST
value among all the IPRA falling under the SA is advertised as the SA's
metric in the corresponding LSP.
If the SA is configured for L12, then the least value should be determined
for each level and should be advertised in the corresponding LSP. While Ext
and Int RA falls under the same SA, then the Int RA's are preferred over Ext
RA's.Thats it.

if ,RA1 => MetricType -  External,  Configured metric - 10
   RA2 => MetricType -  Internal,  Configured metric - 50

if RA1 and RA2 falls under the same summary address(say SA1) for the same
level, then metric with which SA1 should be advertised in the corresponding
level LSP should be 50 and metric type should be Internal.

Other hand, if SA1 is configured for L12, and if RA1 is configured for
L1-only and RA2 is configured for L2-only, then
SA1 should be advertised in L1 LSP with Metric = 10, Metric Type External.
SA1 should be advertised in L2 LSP with Metric = 50, Metric Type Internal.


Selva.

 -----Original Message-----
From: isis-wg-admin@spider.juniper.net
[mailto:isis-wg-admin@spider.juniper.net]On Behalf Of sivaa@indiatimes.com
Sent: Monday, 24 December 2001 11:55 AM
To: workgroup
Cc: Jeff Parker; Radia Perlman - Boston Center for Networking
Subject: [Isis-wg] External IPRA


  Hi,

  Kindly clarify the following

  Whether External IPRA needs to be summarized? If yes, then consider the
following.

  External IPRA with Internal Metric matches  Summary Address Table Entry
S1. We announce S1 with what ever metric that is configured in the Summary
Address Table

  Note: SA table does not have a field indicating the type of metric whether
internal or external.

  External IPRA with External Metric matches Summary Address Table Entry S2.
What should be done now, since the metric configured in the summary Address
Table does not specify whether it is internal or external can S2 now be
announced for the External IPRA. Will this not violate the specification
which says, that external metrics are not camparable to internal metrics?
  [Selvaraj R] In this case , External routes should be ignored. Should
prefer only the Internal routes.

  Any help on this is greatly appreciated

  Thanks & Regards

  Sivakumar A


----------------------------------------------------------------------------
--
  Get Your Private, Free E-mail from Indiatimes at
http://email.indiatimes.com
  Buy Music, Video, CD-ROM, Audio-Books and Music Accessories from
http://www.planetm.co.in

------=_NextPart_000_0005_01C18C83.160DEBA0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">


<META content=3D"MSHTML 5.00.2614.3500" name=3DGENERATOR></HEAD>
<BODY>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>Hi=20
Siva,</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>In=20
most of the implementation Summary address metric is =
NOT&nbsp;configurable.=20
Its&nbsp;determined dynamically whenever an IPRA falls under that.=20
</SPAN></FONT><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D190195107-24122001>The&nbsp;LEAST value&nbsp;among all the IPRA =
falling=20
under the&nbsp;SA is advertised as the SA's metric in the corresponding=20
LSP.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>If the=20
SA is configured for L12, then the least value should be determined for =
each=20
level and should be advertised in the corresponding LSP. <FONT =
color=3D#0000ff=20
face=3DArial size=3D2><SPAN class=3D190195107-24122001>While Ext and Int =
RA falls=20
under the same SA, then the Int RA's are preferred over Ext=20
RA's.</SPAN></FONT>Thats it.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D190195107-24122001></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>if=20
,</SPAN></FONT><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D190195107-24122001>RA1&nbsp;=3D&gt; MetricType -&nbsp; =
External,&nbsp;=20
Configured metric - 10</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001><FONT=20
color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>&nbsp;&nbsp;=20
RA2&nbsp;=3D&gt; MetricType -&nbsp; Internal,&nbsp; Configured metric -=20
50</SPAN></FONT></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001><FONT=20
color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D190195107-24122001></SPAN></FONT></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001><FONT=20
color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>if RA1 and RA2=20
falls under the same&nbsp;summary address(say SA1) for the same level, =
then=20
metric with which SA1 should be advertised in the corresponding level=20
LSP&nbsp;should be 50 and metric type should be=20
Internal.</SPAN></FONT></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001><FONT=20
color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D190195107-24122001></SPAN></FONT></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>Other=20
hand, if SA1 is configured for L12, and if RA1 is configured =
for&nbsp;L1-only=20
and RA2 is configured for&nbsp;L2-only, then</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>SA1=20
should be advertised in L1 LSP with </SPAN></FONT><FONT color=3D#0000ff =
face=3DArial=20
size=3D2><SPAN class=3D190195107-24122001>Metric =3D 10, Metric Type=20
External.</SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001><FONT=20
color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001>SA1 should be=20
advertised in L2 LSP with </SPAN></FONT><FONT color=3D#0000ff =
face=3DArial=20
size=3D2><SPAN class=3D190195107-24122001>Metric =3D 50, Metric Type=20
Internal.</SPAN></FONT></SPAN></FONT></DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001><FONT=20
color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D190195107-24122001></SPAN></FONT></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN =
class=3D190195107-24122001><FONT=20
color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D190195107-24122001></SPAN></FONT></SPAN></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#0000ff face=3DArial size=3D2><SPAN=20
class=3D190195107-24122001>Selva.</SPAN></FONT></DIV>
<DIV><SPAN class=3D190195107-24122001><SPAN=20
class=3D190195107-24122001></SPAN></SPAN><FONT face=3DTahoma><BR><FONT =
size=3D2><SPAN=20
class=3D190195107-24122001><FONT color=3D#0000ff=20
face=3DArial>&nbsp;</FONT></SPAN>-----Original =
Message-----<BR><B>From:</B>=20
isis-wg-admin@spider.juniper.net =
[mailto:isis-wg-admin@spider.juniper.net]<B>On=20
Behalf Of </B>sivaa@indiatimes.com<BR><B>Sent:</B> Monday, 24 December =
2001=20
11:55 AM<BR><B>To:</B> workgroup<BR><B>Cc:</B> Jeff Parker; Radia =
Perlman -=20
Boston Center for Networking<BR><B>Subject:</B> [Isis-wg] External=20
IPRA<BR><BR></FONT></DIV>
<BLOCKQUOTE></FONT>
  <P>Hi,</P>
  <P>Kindly clarify&nbsp;the following</P>
  <P>Whether External IPRA needs to be summarized? =
If&nbsp;yes,&nbsp;then=20
  consider the following.</P>
  <P>External IPRA with Internal Metric matches &nbsp;Summary Address =
Table=20
  Entry S1. We announce S1 with what ever metric that is configured in =
the=20
  Summary Address Table </P>
  <P>Note:&nbsp;SA table does not have a field indicating the type of =
metric=20
  whether internal or external.</P>
  <P>External IPRA with External Metric matches Summary Address Table =
Entry S2.=20
  What should be done now, since the metric configured in the summary =
Address=20
  Table does not specify whether it is internal or external can S2 now =
be=20
  announced for the External IPRA. Will this not violate the =
specification which=20
  says, that external metrics are not camparable to internal =
metrics?<BR><FONT=20
  size=3D2><FONT color=3D#0000ff><FONT face=3DArial><SPAN=20
  class=3D190195107-24122001>[Selvaraj R]&nbsp;In this case , External =
routes=20
  should be ignored. Should prefer only the Internal =
routes.&nbsp;</SPAN><SPAN=20
  class=3D190195107-24122001>&nbsp;</SPAN></FONT></FONT></FONT></P>
  <P>Any help on this is greatly appreciated&nbsp;</P>
  <P>Thanks &amp; Regards</P>
  <P>Sivakumar A</P>
  <HR>
  <FONT face=3DArial size=3D2><B>Get Your Private, Free E-mail from =
Indiatimes at=20
  </FONT><A href=3D"http://email.indiatimes.com"><FONT face=3DArial=20
  size=3D2>http://email.indiatimes.com</FONT></A></B><BR>Buy Music, =
Video, CD-ROM,=20
  Audio-Books and Music Accessories from <A=20
  href=3D"http://www.planetm.co.in">http://www.planetm.co.in</A>=20
</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_0005_01C18C83.160DEBA0--

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec 26 04:57:16 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16524
	for <isis-archive@odin.ietf.org>; Wed, 26 Dec 2001 04:57:16 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBQ9q1155636;
	Wed, 26 Dec 2001 01:52:01 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from xover.mindspeed.com ([198.62.10.2])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBQ9ph155624
	for <isis-wg@spider.juniper.net>; Wed, 26 Dec 2001 01:51:43 -0800 (PST)
	(envelope-from VishwasM@netplane.com)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <ZN3QPGBW>; Wed, 26 Dec 2001 04:52:33 -0500
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328291714@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'Jeff Parker'" <jparker@axiowave.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 26 Dec 2001 04:52:39 -0500

Jeff,

Thanks for forwarding to the list(got useful comments there) and sorry for
the delayed response, have not checked my mails for some time. Comments
inline prefixed by a VM>.

Thanks,
Vishwas
 
> 1. The isisAreaAddr description given in the overview section 
> is not clear.
> I think it should be mentioned area addresses in Level 1 
> LSP's, else first
> reading it gets confused with isisISAdjAreaAddr.

I'm not sure what you are suggesting here.  The MIB 
currently includes the following introduction

	-- The Level 1 Area Address Table

	-- The Level 1 Area Address Table contains the
	-- union of the sets of area addresses reported in all Level 1
	-- LSPs received by this Intermediate System.

Are you suggesting this is too much or too little?
If too little, could you provide suggested text?

VM> I was talking about the overview section, Section 4. At present it says

    - isisAreaAddr

       This table includes area addresses reported by peers.

    I thought it would be better if you clarifed this. It could say "area
addresses reported in Level 1 LSP's."

Regarding DEFVAL for SysType, does any vendor use any other default but
L1/L2? 

Also regarding the range for SysMaxLSPGenInt, MaxAge is given as an
architectural constant in document ISO-10589, section 7.3.21. So I guess
anyone who does not follow the MaxAge limit would not follow the new range
either(so no big deal). However setting the Max value of the range correctly
would not allow a wrong setting of SysMaxLSPGenInt in an implementation that
follows the architectural constants. Don't you think so? (A similar thing is
done in OSPF)
   
> 6. What does isisSummAddrAdminState signify(does it signify 
> from or to) ie
> when it is L1, is the table used to summarize to or from the L1?

I have added text.  See if it is clearer now.

VM> Yes.

> 8. What does functional multicast address mean?

You are asking about the definition of the object below.

I have no idea what this is about, and have done a quick
pass through 10589 without enlightenment.  Is there someone
out there who can shed light on this?  

     isisCircMCAddr OBJECT-TYPE
         SYNTAX INTEGER{
             group (1),
             functional (2)
             }
         MAX-ACCESS read-create
         STATUS current
         DESCRIPTION
             "Specifies which type of multicast address will
             be used for sending HELLO PDUs on this
             circuit."
         DEFVAL { group }
     ::= { isisCircEntry 16 }

VM> Does it mean the value of 2, is not used at present?

> 9. Wouldnt it be nice to keep a count of External routes, L1 
> routes , L2
> routes. Or may be how many of TLV 128 and how many 130? I am 
> just trying to
> draw a parallel with OSPF.

I have added to my todo list.  I won't try to add them this morning.

VM>  Great !!! ;-)
 
> 10. What is the summary area-default metric. I feel thats not 
> required. If
> it matches more than one dest we can have the min cost of al 
> the dest it
> encompasses. Shldnt there be another field to tell when summ 
> area default
> metric is to be used, if thats required?

The term Default has an unusaul meaning in the protocol.  
I have removed "default" and "Def" from the names of metrics
where they appear, and added text to better describe the meaning
of "DefaultMetric" in ISIS.  The DefaultMetric TC is left as is.

VM> Good enough. 

> 11. What does isisSysL1state and SysL2state OFF mean? What 
> is the relation to isisSysSetOverload?(If any)
> 
> Thanks,
> Vishwas

There is a notion of an overload bit which is used to signal
that a router is low on memory, and thus not to be trusted.

In OSPF, we don't use a router as a transit node until it has
finished the DataBase exchange.  In ISIS, some implementations
allow the administrator to bring up the router with the overload
bit set for a given time period.  This gives the router a 
chance to become synchronized.  

I have added text to the isisSysL1State and L2State definitions:
see if that makes things clearer.  

VM> mmmmm.....I am still not very clear.(I understand overload bit and where
it could be used) So isisSysL1State should not be read-only then, if it is
settable. Also what do states "on"/"off"/"waiting" mean in this context?

Also I still did not understand the relation with the isisSysSetOverload
object. Aren't they related? If we set the SysL1State to say "on", wouldn't
a get on SysSetOverload state return a setL1Overload(I know the answer is
no, but i am trying to understand)? Why two diff objects?
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Wed Dec 26 08:34:31 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17451
	for <isis-archive@odin.ietf.org>; Wed, 26 Dec 2001 08:34:29 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBQDVh157063;
	Wed, 26 Dec 2001 05:31:43 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from web13207.mail.yahoo.com (web13207.mail.yahoo.com [216.136.174.192])
	by external.juniper.net (8.11.6/8.11.6) with SMTP id fBQDQL157031
	for <isis-wg@spider.juniper.net>; Wed, 26 Dec 2001 05:26:21 -0800 (PST)
	(envelope-from dasnabendu@yahoo.com)
Message-ID: <20011226132712.63062.qmail@web13207.mail.yahoo.com>
Received: from [203.200.20.224] by web13207.mail.yahoo.com via HTTP; Wed, 26 Dec 2001 05:27:12 PST
From: nabendu das <dasnabendu@yahoo.com>
To: isis-wg@spider.juniper.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Isis-wg] minLSPTransmissionInterval
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 26 Dec 2001 05:27:12 -0800 (PST)

hi list,
confusion about minLSPTransmissionInterval.
in ISO-10589 7.3.14.3 ,
"The Update Process scans the Link State Database for
Link Stat PDUs with SRMflags set. when one is found,
provided the timestamp lastSent indicates that it was
propagated no more recently than
minimumLSPTransmissionInterval, the IS shall 
a) transmit it on all circuits with SRMflags set, and
b) update lastSent."
now here it is not being told whether above mentioned
check is for P2P link or Broadcast link, Do we need to
check this for p2p as well as for LAN case???? or
minimumBroadcastLSPTransmissionInterval takes care of
that, and if so " how does
minimumBroadcastLSPTransmissionInterval controls how
fast we send back-to-back LSPs as per the new
MIB(isisCircLevelLSPThrottle)???? is it like the way
as stated in ISO 10589 in 7.3.15.6, as "as IS is
permitted to transmit a small no of LSPs with a
shorter seperation interval, provided that no more
than 1000/minimumLSPTransmissionInterval LSPs are
transmitted in any one second period."????????

and again in 7.3.15.5,
" an IS shall perform the folln every
minimumLSPTransmissionInterval -
for all p2p circuits c transmit all LSPs that have
SRMflags set on circuit C."
 and below that
" the interval between two consecutive transmission of
the same LSP shall be at least
minimumLSPTransmissionInterval" 
the question is if the IS shall perform the action as
stated in 7.3.15.5 for every
minimumLSPTransmissionInterval, then the interval
between two consecutive transmission of the same LSP
will be at least minimumLSPTransmissionInterval
anyway. so why that has again been stated.???

Plz help.
thanking in advance.




__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 10:55:39 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17867
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 10:55:38 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRFq0164078;
	Thu, 27 Dec 2001 07:52:01 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRFpJ164066
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 07:51:20 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B38200062957342901230010@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Naiming Shen'" <naiming@redback.com>,
        Jeff Learman
	 <jlearman@cisco.com>
Cc: Jeff Parker <jparker@axiowave.com>,
        "'Manral, Vishwas'"
	 <VishwasM@netplane.com>,
        "IS-IS-WG (E-mail)"
	 <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt 
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 10:51:21 -0500

> The reason some vendors (correctly) use level-1/level-2 as 
> default is because a user can drop the router in any topology 
> which [and it will] work.
>
> - Naiming

Excellent point.

> In any case, though, will this draft really affect how any vendor's
> implementation will default?  Perhaps the default should be unspecified,
> since there are good arguments to go either way.  (On the other hand,
> this IS a standards group!)
> 
> [Jeff L]

I've seen a number of implementations that take an SNMP MIB
as -the- description of the default for CLI, DB, Web, or
whatever means you use to administer the box.  And others
will refer to the default values we define, if only as a
starting point.  So I do think it is worth getting this right.  

Here is one argument against the suggestion of a
default value of L1.  Since there is no way to have 
a default area, if L1 is the default, the administrator
must touch this 'region' of the configuration.  

I'm happy to return to L1L2.  Other opinions?

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 11:48:47 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA18340
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 11:48:47 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRGjk164332;
	Thu, 27 Dec 2001 08:45:46 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRGaM164277
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 08:36:22 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B38200062957342901230013@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Manral, Vishwas'" <VishwasM@netplane.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 11:36:46 -0500

Thanks for your review comments.  I'm responding to the list.  

> VM> I was talking about the overview section, Section 4. At 
> present it says
> 
>     - isisAreaAddr
> 
>        This table includes area addresses reported by peers.
>
>     I thought it would be better if you clarifed this. It 
> could say "area addresses reported in Level 1 LSP's."

I cannot find a match for the strings above in the 07 mib.  
Perhaps you could give me a line number from the mib which
I will send you offline.  


> Regarding DEFVAL for SysType, does any vendor use any other 
> default but L1/L2? 

There has been a recent discussion of this on the list.  
One contributor is suggesting a value of L1.  


> Also regarding the range for SysMaxLSPGenInt, MaxAge is given as an
> architectural constant in document ISO-10589, section 7.3.21. 

ISO 10589 is an excellent document that reflected the experience
of it's authors when it was written.  Time moves on, and things
change.  

> So I guess anyone who does not follow the MaxAge limit 
> would not follow the new range either(so no big deal). 
> However setting the Max value of the range correctly
> would not allow a wrong setting of SysMaxLSPGenInt in an 
> implementation that follows the architectural constants. 
> Don't you think so? (A similar thing is done in OSPF)

I think it is important to have a default setting that respects
MaxAge, and we meet that today.  

The value of MaxAge is not currently a variable in the
MIB, and it is not part of the negotiation phase in adjacency
bring up: it does not appear on the wire.  Since this is an 
area or domain wide context, it isn't really clear how 
negotiation of this could take place.  We could add MaxAge
to the MIB, but I think what needs to be discussed is what
the right action should be upon the receipt of an LSP that
has a larger MaxAge than you support.  
    
 
> > 8. What does functional multicast address mean?
> 
> You are asking about the definition of the object below.
> 
> I have no idea what this is about, and have done a quick
> pass through 10589 without enlightenment.  Is there someone
> out there who can shed light on this?  
> 
>      isisCircMCAddr OBJECT-TYPE
>          SYNTAX INTEGER{
>              group (1),
>              functional (2)
>              }
>          MAX-ACCESS read-create
>          STATUS current
>          DESCRIPTION
>              "Specifies which type of multicast address will
>              be used for sending HELLO PDUs on this
>              circuit."
>          DEFVAL { group }
>      ::= { isisCircEntry 16 }
> 
> VM> Does it mean the value of 2, is not used at present?

I confess that I still have no idea what this controls.  
If no one else does either, I will phase it out.  

> > 11. What does isisSysL1state and SysL2state OFF mean? What 
> > is the relation to isisSysSetOverload?(If any)
> 
> There is a notion of an overload bit which is used to signal
> that a router is low on memory, and thus not to be trusted.
> 
> In OSPF, we don't use a router as a transit node until it has
> finished the DataBase exchange.  In ISIS, some implementations
> allow the administrator to bring up the router with the overload
> bit set for a given time period.  This gives the router a 
> chance to become synchronized.  
> 
> I have added text to the isisSysL1State and L2State definitions:
> see if that makes things clearer.  
> 
> VM> mmmmm.....I am still not very clear.(I understand 
> overload bit and where
> it could be used) So isisSysL1State should not be read-only 
> then, if it is
> settable. Also what do states "on"/"off"/"waiting" mean in 
> this context?
> 
> Also I still did not understand the relation with the 
> isisSysSetOverload object. Aren't they related? If 
> we set the SysL1State to say "on", wouldn't
> a get on SysSetOverload state return a setL1Overload
> (I know the answer is no, but i am trying to understand)? 
> Why two diff objects?

I think I mispoke on this topic in my earlier private 
mail this morning.   

One is a gauge, one is a knob.  You don't use the 
speedometer in your car to accelerate: you use the 
gas pedal.  And if you are rolling down hill, the
position of the gas pedal may not reflect your speed.

The isisSysL1State tells you what state the system
is in, and is thus read-only.  isisSysSetOverload
is the knob you use to try to change things.  You
may try to bring the system out of Overload by 
setting isisSysSetOverload to overloadClear when 
the system is out of memory.  In that case, you 
expect the guage to move from wait to overloaded,
and you expect to continue to originate LSPs with
the O bit set.  

     isisSysL1State OBJECT-TYPE
         SYNTAX LevelState
         MAX-ACCESS read-only
         STATUS current
         DESCRIPTION
             "The state of the Level 1 database.
              The value 'overloaded' indicates a database that is
              low on an essential resource, such as memory.
              The administrator may set the state to 'wait' when
              the router is initializing by setting the object
              isisSysSetOverload.
              If the state is waiting or overloaded, we
              originate LSPs with the Overload bit set."
         REFERENCE "{ISIS.aoi l1State (17)}"
     ::= { isisSysEntry 14 }

Let me know if this is any clearer.

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 12:29:01 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18785
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 12:29:01 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRHPu164547;
	Thu, 27 Dec 2001 09:25:56 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from xover.mindspeed.com (cnxt10002.conexant.com [198.62.10.2])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRHEk164487
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 09:14:46 -0800 (PST)
	(envelope-from VishwasM@netplane.com)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <ZN3QPHQ8>; Thu, 27 Dec 2001 12:15:44 -0500
Message-ID: <E7E13AAF2F3ED41197C100508BD6A32829171E@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'Jeff Parker'" <jparker@axiowave.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 12:15:56 -0500

Jeff,

Comments inline preceded by a VM>.

Thanks,
Vishwas

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

Thanks for your review comments.  I'm responding to the list.  

I cannot find a match for the strings above in the 07 mib.  
Perhaps you could give me a line number from the mib which
I will send you offline.  

VM> Its in the overview section(section 4), just before the definition of
the MIB section(Section 5). I will send you a private mail about the line
number.

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

There has been a recent discussion of this on the list.  
One contributor is suggesting a value of L1.  

VM>Well as far as I know Jeff L. does not work on ISIS in his company(and
his views in his own words dont necessarily represent Cisco, which uses as
default L1/L2(or so their documents say)) ;-)

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

I think it is important to have a default setting that respects
MaxAge, and we meet that today.  

The value of MaxAge is not currently a variable in the
MIB, and it is not part of the negotiation phase in adjacency
bring up: it does not appear on the wire.  Since this is an 
area or domain wide context, it isn't really clear how 
negotiation of this could take place.  We could add MaxAge
to the MIB, but I think what needs to be discussed is what
the right action should be upon the receipt of an LSP that
has a larger MaxAge than you support.  
    
VM> This is exactly the reason why MaxAge needs to be same in all routers in
the domain. It also is an anomaly, where at one place we say MaxAge is arch.
constant and so not configurable, and other place we say it is not a
constant. 

Treating any LSP with age above Maxage could be done as if age was MaxAge.
May be we need to recommend that all routers in a domain have the same
Maxage(and the value of MaxLSPGenInt should be less than the value of the
smallest value of MaxAge in any router in the domain)value for things to
work ok(and then we can treat all LSP's with age greater than MaxAge as
MaxAge), we could raise a trap on getting an LSP with age greater than
MaxAge.
 
--------------------------------------

I confess that I still have no idea what this controls.  
If no one else does either, I will phase it out.  

VM> Ok, though I am sure someone will have an idea.

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

I think I mispoke on this topic in my earlier private 
mail this morning.   

One is a gauge, one is a knob.  You don't use the 
speedometer in your car to accelerate: you use the 
gas pedal.  And if you are rolling down hill, the
position of the gas pedal may not reflect your speed.

The isisSysL1State tells you what state the system
is in, and is thus read-only.  isisSysSetOverload
is the knob you use to try to change things.  You
may try to bring the system out of Overload by 
setting isisSysSetOverload to overloadClear when 
the system is out of memory.  In that case, you 
expect the guage to move from wait to overloaded,
and you expect to continue to originate LSPs with
the O bit set.  

     isisSysL1State OBJECT-TYPE
         SYNTAX LevelState
         MAX-ACCESS read-only
         STATUS current
         DESCRIPTION
             "The state of the Level 1 database.
              The value 'overloaded' indicates a database that is
              low on an essential resource, such as memory.
              The administrator may set the state to 'wait' when
              the router is initializing by setting the object
              isisSysSetOverload.
              If the state is waiting or overloaded, we
              originate LSPs with the Overload bit set."
         REFERENCE "{ISIS.aoi l1State (17)}"
     ::= { isisSysEntry 14 }

Let me know if this is any clearer.

VM> Yes, now it is clearer and I thought some thing like this though. ;-)
However I am not sure how the administrator could set the state to "wait".
Its a read only object(as pointed out in the private mail).

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 12:34:29 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA18850
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 12:34:27 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRHVv164589;
	Thu, 27 Dec 2001 09:31:57 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRHFr164498
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 09:15:53 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B38200062957342901230018@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Manral, Vishwas'" <VishwasM@netplane.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 12:16:17 -0500

I'm replying to the list.  I'd like to expose the requests
for change, so that others can react.  Witness the recent
discussion on the appropriate default system type.

> Also one more doubt. If you do go in for adding a table or 
> object for the
> number of TLV's of type 128 and 130. I guess we could also 
> have a couter for
> the number of TLV's with up/down bit set to 0 and same thing for 1.

I will add to the todo list.


> Also how about keeping a counter/trap when we get a mismatch in the
> configured MeshGroupEnabled i.e. getting an LSP even when the 
> circuit state is blocked.
> 
> Vishwas

Vishwas -
	One of the limitations of the mesh group idea is that
there is no way to check that the configuration makes sense,
and no way to know what configuration the far end has.  
So anything that would help catch errors would be welcome.  
But mesh state is not symetric.  You may be told not to speak,
but that doesn't mean you shouldn't listen.  As noted above, you
really don't know what state the other side is in.  

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 12:45:57 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA19025
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 12:45:56 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRHhP164667;
	Thu, 27 Dec 2001 09:43:25 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRHTY164565
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 09:29:34 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B38200062957342901230019@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Manral, Vishwas'" <VishwasM@netplane.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 12:29:58 -0500

> > There has been a recent discussion of this on the list.  
> > One contributor is suggesting a value of L1.  
> 
> VM>Well as far as I know Jeff L. does not work on ISIS in his 
> company(and his views in his own words dont necessarily 
> represent Cisco, which uses as default L1/L2(or so their 
> documents say)) ;-)

Jeff L. has presented arguments in favor of his position.
I think we need to read and respond to them, independent
of where he works and what his company does.   


> > The value of MaxAge is not currently ... in the MIB
 
> VM> This is exactly the reason why MaxAge needs to be same in 
> all routers in the domain. It also is an anomaly, where at 
> one place we say MaxAge is arch. constant and so not 
> configurable, and other place we say it is not a constant. 

The idea of a variable constant always makes me laugh.
I could add a value parallel to isisSysOrigL1LSPBuffSize.
However, I don't think we have really sorted out how such a
variable should be used.  I think dropping LSPs that are
larger than this has an adverse impact.  It could be used
as the largest value used on originated packets.  

> May be we need to recommend that all routers in a domain have the same
> Maxage(and the value of MaxLSPGenInt should be less than the 
> value of the
> smallest value of MaxAge in any router in the domain)value 
> for things to
> work ok(and then we can treat all LSP's with age greater than 
> MaxAge as
> MaxAge), we could raise a trap on getting an LSP with age greater than
> MaxAge.

 
> > One is a gauge, one is a knob.   
> 
> VM> Yes, now it is clearer and I thought some thing like this 
> though. ;-)  However I am not sure how the administrator 
> could set the state to "wait".  Its a read only object(as 
>pointed out in the private mail).

The administrator does not touch the gauge.  The administrator
touches the knob, setting isisSysSetOverload.  Please suggest
text changes that would make the following passages clearer on
this point.  

Your speedometer is read-only: the gas pedal is not.  

     isisSysL2State OBJECT-TYPE
         SYNTAX LevelState
         MAX-ACCESS read-only
         STATUS current
         DESCRIPTION
             "The state of the Level 2 database.
              The value 'overloaded' indicates a database that is
              low on an essential resource, such as memory.
              The administrator may set the state to 'wait' when
              the router is initializing by setting the object
              isisSysSetOverload.
              If the state is waiting or overloaded, we
              originate LSPs with the Overload bit set."
         REFERENCE "{ISIS.aoi l2State (28)}"
     ::= { isisSysEntry 24 }

and

     isisSysSetOverload OBJECT-TYPE
         SYNTAX INTEGER
                 {
                   setL1Overload(1),
                   setL2Overload(2),
                   setL1L2Overload(3),
                   overloadClear(4)
                 }
         MAX-ACCESS read-create
         STATUS current
         DESCRIPTION
             "Administratively set the overload bit for each level.
              The overload bit will continue to be set if the
              implementation runs out of memory, independent of
              this variable"
         DEFVAL {overloadClear }
     ::= { isisSysEntry 35 }

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 13:11:40 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19361
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 13:11:40 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRI8W164817;
	Thu, 27 Dec 2001 10:08:32 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from xover.mindspeed.com (cnxt10002.conexant.com [198.62.10.2])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRHf8164651
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 09:41:08 -0800 (PST)
	(envelope-from VishwasM@netplane.com)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <ZN3QPHSF>; Thu, 27 Dec 2001 12:42:06 -0500
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328291721@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'Jeff Parker'" <jparker@axiowave.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 12:42:19 -0500

Jeff,

Jeff L. has presented arguments in favor of his position.
I think we need to read and respond to them, independent
of where he works and what his company does.   

VM> I did not question the validity of the argument. The following was what
my initial question was. Does any vendor support a value other than L1/L2 as
DEFVAL?(May be I did not make myself too clear)


The administrator does not touch the gauge.  The administrator
touches the knob, setting isisSysSetOverload.  Please suggest
text changes that would make the following passages clearer on
this point.  

VM> Oops, sorry my fault now(I did not read carefully), the latest version
you sent is clear enough.

Thanks,
Vishwas
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 13:29:22 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19494
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 13:29:22 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRIQZ164927;
	Thu, 27 Dec 2001 10:26:35 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from xover.mindspeed.com (cnxt10002.conexant.com [198.62.10.2])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRHip164676
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 09:44:51 -0800 (PST)
	(envelope-from VishwasM@netplane.com)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <ZN3QPHSV>; Thu, 27 Dec 2001 12:45:49 -0500
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328291722@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'Jeff Parker'" <jparker@axiowave.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 12:45:56 -0500

Jeff,

Agreed, there is no way to negotiate the two ends configuration(we could
always add a TLV???). But doesn't Section 3a) RFC2973 mean that we prefer
mesh states are same at both ends. If we get an LSP via a blocked circuit,
doesn't it mean there is some config mismatch? Would it ever be required to
have a mismatch in the mesh states?

Also what should be done in case we get an LSP on a circuit C, where the
meshGroupEnabled attribute is blocked. Should we treat it similar to
meshGroupEnabled inactive state? 

Thanks,
Vishwas 

> Also how about keeping a counter/trap when we get a mismatch in the
> configured MeshGroupEnabled i.e. getting an LSP even when the 
> circuit state is blocked.
> 
> Vishwas
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 13:45:03 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA19624
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 13:45:02 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRIg1165035;
	Thu, 27 Dec 2001 10:42:01 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from celox-ma1-ems1.celoxnetworks.com (celox-ma1-imap1.celoxnetworks.com [12.40.60.233])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRIft165022
	for <isis-wg@external.juniper.net>; Thu, 27 Dec 2001 10:41:55 -0800 (PST)
	(envelope-from sganguly@celoxnetworks.com)
Received: by celox-ma1-ems1.celoxnetworks.com with Internet Mail Service (5.5.2653.19)
	id <Y2S03GHL>; Thu, 27 Dec 2001 13:42:53 -0500
Message-ID: <1117F7D44159934FB116E36F4ABF221B0102E83E@celox-ma1-ems1.celoxnetworks.com>
From: "Ganguly, Shamik" <sganguly@celoxnetworks.com>
To: "'IS-IS-WG (E-mail)'" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] Query for IS-IS in general
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 13:42:47 -0500

Hi,

I am a newcomer to IS-IS. Can somebody refer a good book on IS-IS? Most of
the book I have looked into just have a small section on the subject.

I will really appreciate your help.

-Shamik Ganguly
Celox Networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 14:00:07 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19742
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 14:00:05 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRIv4165132;
	Thu, 27 Dec 2001 10:57:04 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRIne165084
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 10:49:40 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B3820006295734290123001D@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Manral, Vishwas'" <VishwasM@netplane.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: Mesh Groups
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 13:50:03 -0500

Subject changed to match topic

> Agreed, there is no way to negotiate the two ends 
> configuration(we could always add a TLV???). But 
> doesn't Section 3a) RFC2973 mean that we prefer
> mesh states are same at both ends. If we get an 
> LSP via a blocked circuit, doesn't it mean there 
> is some config mismatch? Would it ever be 
> required to have a mismatch in the mesh states?

My reading of the RFC suggests that you shouldn't
use Mesh Groups at all.  But given that they exist,
I don't see why we should restrict them to be 
'blocked' symetricaly.  
 
> Also what should be done in case we get an LSP on a 
> circuit C, where the meshGroupEnabled attribute is 
> blocked. Should we treat it similar to 
> meshGroupEnabled inactive state? 
> 
> Vishwas 

I can imagine an implementation that sets the
value of meshGroup for a meshBlocked circuit,
and uses that value to restrict flooding. 
However, the RFC explicitly states that the 
meshGroup value is not meaningful when the 
circuit is meshBlocked.  

The intent of mesh groups is to reduce 
flooding, not to prevent it.  I would
do as you suggest: flood it out non-
blocked circuits.

- jeff parker
- axiowave networks
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 14:18:48 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA19903
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 14:18:47 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRJG7165248;
	Thu, 27 Dec 2001 11:16:07 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRIv3165123
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 10:57:03 -0800 (PST)
	(envelope-from jlearman@cisco.com)
Received: from dingdong.cisco.com (localhost [127.0.0.1])
	by rtp-msg-core-1.cisco.com (8.11.3/8.9.1) with ESMTP id fBRIwAm07773;
	Thu, 27 Dec 2001 13:58:10 -0500 (EST)
Received: from JLEARMAN-W2K1.cisco.com (rtp-vpn1-414.cisco.com [10.82.225.158])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id AAI70033;
	Thu, 27 Dec 2001 13:58:00 -0500 (EST)
Message-Id: <4.3.2.7.2.20011227135550.01f44ed8@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Ganguly, Shamik" <sganguly@celoxnetworks.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] Query for IS-IS in general
Cc: "'IS-IS-WG (E-mail)'" <isis-wg@spider.juniper.net>
In-Reply-To: <1117F7D44159934FB116E36F4ABF221B0102E83E@celox-ma1-ems1.ce
 loxnetworks.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 13:57:53 -0500


The best book I know of is Interconnections, by Radia Perlman.
However, this covers "Bridges and Routers", and has a section on
link-state routing protocols, but not a specific section on IS-IS
alone.

Jeff

At 01:42 PM 12/27/2001, Ganguly, Shamik wrote:
>Hi,
>
>I am a newcomer to IS-IS. Can somebody refer a good book on IS-IS? Most of
>the book I have looked into just have a small section on the subject.
>
>I will really appreciate your help.
>
>-Shamik Ganguly
>Celox Networks
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 15:21:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA20541
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 15:21:57 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRKJ1165565;
	Thu, 27 Dec 2001 12:19:01 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRK5Q165503
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 12:05:26 -0800 (PST)
	(envelope-from dkatz@juniper.net)
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 fBRK6P689190;
	Thu, 27 Dec 2001 12:06:25 -0800 (PST)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost)
	by cirrus.juniper.net (8.11.6/8.11.6) id fBRK5uF40246;
	Thu, 27 Dec 2001 12:05:56 -0800 (PST)
	(envelope-from dkatz@cirrus.juniper.net)
Message-Id: <200112272005.fBRK5uF40246@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: jlearman@cisco.com
CC: sganguly@celoxnetworks.com, isis-wg@spider.juniper.net
In-reply-to: <4.3.2.7.2.20011227135550.01f44ed8@dingdong.cisco.com> (message
	from Jeff Learman on Thu, 27 Dec 2001 13:57:53 -0500)
Subject: Re: [Isis-wg] Query for IS-IS in general
References:  <4.3.2.7.2.20011227135550.01f44ed8@dingdong.cisco.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 12:05:56 -0800 (PST)

Another resource is Piscitello and Chapin's book, which I believe is
entitled "Internetworking with TCP/IP and OSI."

   X-Sender: jlearman@dingdong.cisco.com
   From: Jeff Learman <jlearman@cisco.com>
   Cc: "'IS-IS-WG (E-mail)'" <isis-wg@spider.juniper.net>
   Content-Type: text/plain; charset="us-ascii"
   Sender: isis-wg-admin@spider.juniper.net
   X-BeenThere: isis-wg@external.juniper.net
   X-Mailman-Version: 2.0rc1
   Precedence: bulk
   List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
   List-Post: <mailto:isis-wg@external.juniper.net>
   List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	   <mailto:isis-wg-request@external.juniper.net?subject=subscribe>
   List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
   List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	   <mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
   List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
   Date: Thu, 27 Dec 2001 13:57:53 -0500


   The best book I know of is Interconnections, by Radia Perlman.
   However, this covers "Bridges and Routers", and has a section on
   link-state routing protocols, but not a specific section on IS-IS
   alone.

   Jeff

   At 01:42 PM 12/27/2001, Ganguly, Shamik wrote:
   >Hi,
   >
   >I am a newcomer to IS-IS. Can somebody refer a good book on IS-IS? Most of
   >the book I have looked into just have a small section on the subject.
   >
   >I will really appreciate your help.
   >
   >-Shamik Ganguly
   >Celox Networks
   >_______________________________________________
   >Isis-wg mailing list  -  Isis-wg@external.juniper.net
   >http://external.juniper.net/mailman/listinfo/isis-wg

   _______________________________________________
   Isis-wg mailing list  -  Isis-wg@external.juniper.net
   http://external.juniper.net/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Thu Dec 27 16:56:26 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21518
	for <isis-archive@odin.ietf.org>; Thu, 27 Dec 2001 16:56:24 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRLqt165982;
	Thu, 27 Dec 2001 13:52:55 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from web21110.mail.yahoo.com (web21110.mail.yahoo.com [216.136.227.112])
	by external.juniper.net (8.11.6/8.11.6) with SMTP id fBRLec165926
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 13:40:38 -0800 (PST)
	(envelope-from nagastabagamba@yahoo.com)
Message-ID: <20011227214138.86295.qmail@web21110.mail.yahoo.com>
Received: from [212.179.34.114] by web21110.mail.yahoo.com via HTTP; Thu, 27 Dec 2001 13:41:38 PST
From: Nagasta Bagamba <nagastabagamba@yahoo.com>
To: isis-wg@spider.juniper.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Isis-wg] IGP shortcuts
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 13:41:38 -0800 (PST)

Hi,

I have some wonders about several issues in the draft
"draft-hsmit-mpls-igp-spf-00.txt".

1. In secrion 6.1: "The relative metric is bounded by
minimum and maximum allowed metric values" 
Is there any use for maximum value higher than 1?
As I see it, any positive relative metric causes the
TE-tunnel not to be used by the IGP, so there is no
need for more than one positive value.

2. In section 4: "Traffic to nodes that are downstream
of the tail-end nodes will also flow over those
TE-tunnels"
I find the word "downstream" a little bit problematic.
It can be downstream to the node on the SPF tree OR
downstream to the node on the IGP topology graph.
I think it refers to the SPF tree, but is there any
prevention from using TE-tunnels, as shortcuts, on the

IGP topology graph instead of on the SPF tree? It
looks like it will give more functionality and meaning
to the word "shortcuts". Of course we have to be
careful form routing loops, but with some basic rules
it is possible... :)

Regards,
Nagi



__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 28 13:34:27 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10500
	for <isis-archive@lists.ietf.org>; Fri, 28 Dec 2001 13:34:27 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSITI171616;
	Fri, 28 Dec 2001 10:29:18 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRKmr165705
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 12:48:53 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B38200062957342901230026@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Dave Katz'" <dkatz@juniper.net>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] Query for IS-IS in general
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 15:49:48 -0500

> From: Dave Katz [mailto:dkatz@juniper.net]
> Subject: Re: [Isis-wg] Query for IS-IS in general
> 
> 
> Another resource is Piscitello and Chapin's book, which I believe is
> entitled "Internetworking with TCP/IP and OSI."
> 

Dave -
	Thanks for the reference.  

	Title is "Open Systems Networking : Tcp/Ip and Osi".  Amazon says
that it is now out of print, but you might be able to find in a library.  

http://www.amazon.com/exec/obidos/ASIN/0201563347/qid=1009485562/sr=1-2/ref=
sr_1_8_2/102-7400645-5347329

- jeff parker
- axiowave networks
- All those who believe in psychokinesis, raise my hand.


_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 28 13:55:11 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA10695
	for <isis-archive@odin.ietf.org>; Fri, 28 Dec 2001 13:55:10 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSIqL171725;
	Fri, 28 Dec 2001 10:52:21 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBRL0c165762
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 13:00:38 -0800 (PST)
	(envelope-from ginsberg@pluris.com)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id NAA27797;
	Thu, 27 Dec 2001 13:00:34 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <YNMD13NH>; Thu, 27 Dec 2001 13:00:34 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F69D@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Manral, Vishwas'" <VishwasM@netplane.com>,
        "'Jeff Parker'"
	 <jparker@axiowave.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 13:00:33 -0800

> 
> Treating any LSP with age above Maxage could be done as if 
> age was MaxAge.
> May be we need to recommend that all routers in a domain have the same
> Maxage(and the value of MaxLSPGenInt should be less than the 
> value of the
> smallest value of MaxAge in any router in the domain)value 
> for things to
> work ok(and then we can treat all LSP's with age greater than 
> MaxAge as
> MaxAge), we could raise a trap on getting an LSP with age greater than
> MaxAge.
>  

The change from an architectural constant to a configurable value was
presumably made based on customer demand. To require, or even suggest, that
an implementation treat an LSP received with a lifetime > the architectural
constant MAXAGE as if it were set to MAXAGE is a VERY BAD thing to do.
Routers which did this could end up purging an LSP from their database
before the originating router's MaxLSPGenInt timer fired, which would cause
unnecessary flapping. If you want to argue that the current "de facto
standard" of making LSP lifetime configurable should be made invalid you
will at least be addressing the issue directly - though I suspect you will
get little support. Circumventing the issue by pretending the value is not
configurable is unwise.

It is also worth noting that, as you suggest, there is a necessary
relationship between LSP lifetime and MaxLSPGenInt, namely:

1)MaxLSPGenInt must be less than LSPlifetime
2)(LSPlifetime - MaxLSPGenInt) should be large enough to allow propagation
of the LSP throughout the area/domain before the old LSP ages out

If LSP lifetime is modified from the "default" value of 1200 seconds, it
makes sense to change MaxLSPGenInt in a like manner.

   Les
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 28 14:03:10 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10770
	for <isis-archive@odin.ietf.org>; Fri, 28 Dec 2001 14:03:09 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSJ0h171811;
	Fri, 28 Dec 2001 11:00:43 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from fep01-mail.bloor.is.net.cable.rogers.com (fep01-mail.bloor.is.net.cable.rogers.com [66.185.86.71])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSIvA171763
	for <isis-wg@spider.juniper.net>; Fri, 28 Dec 2001 10:57:11 -0800 (PST)
	(envelope-from bertcameron@rogers.com)
Received: from bert ([24.156.170.195])
          by fep01-mail.bloor.is.net.cable.rogers.com
          (InterMail vM.5.01.04.02 201-253-122-122-102-20011128) with SMTP
          id <20011228185815.FBIL442720.fep01-mail.bloor.is.net.cable.rogers.com@bert>
          for <isis-wg@spider.juniper.net>; Fri, 28 Dec 2001 13:58:15 -0500
Message-ID: <002501c18fd1$b161d480$0200a8c0@bert>
From: "Bert Cameron" <bertcameron@rogers.com>
To: <isis-wg@spider.juniper.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0022_01C18FA7.C86A3AC0"
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
Subject: [Isis-wg] (no subject)
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 28 Dec 2001 13:58:52 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_0022_01C18FA7.C86A3AC0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

who isis

------=_NextPart_000_0022_01C18FA7.C86A3AC0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2712.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial>who isis</FONT></DIV></BODY></HTML>

------=_NextPart_000_0022_01C18FA7.C86A3AC0--

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 28 14:26:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA10985
	for <isis-archive@odin.ietf.org>; Fri, 28 Dec 2001 14:26:57 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSJOT172004;
	Fri, 28 Dec 2001 11:24:29 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSJ5c171864
	for <isis-wg@spider.juniper.net>; Fri, 28 Dec 2001 11:05:38 -0800 (PST)
	(envelope-from bertcameron@rogers.com)
Received: from ping.juniper.net (scanners.jnpr.net [207.17.137.101])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id fBSJ6iG62527
	for <isis-wg@juniper.net>; Fri, 28 Dec 2001 11:06:44 -0800 (PST)
X-JNPR-Received-From: outside
Received: from fep01-mail.bloor.is.net.cable.rogers.com ([66.185.86.71]) by ping.juniper.net with Microsoft SMTPSVC(5.0.2195.2966);
	 Fri, 28 Dec 2001 11:06:43 -0800
Received: from bert ([24.156.170.195])
          by fep01-mail.bloor.is.net.cable.rogers.com
          (InterMail vM.5.01.04.02 201-253-122-122-102-20011128) with SMTP
          id <20011228190642.FGXF442720.fep01-mail.bloor.is.net.cable.rogers.com@bert>
          for <isis-wg@juniper.net>; Fri, 28 Dec 2001 14:06:42 -0500
Message-ID: <004f01c18fd2$df8f5020$0200a8c0@bert>
From: "Bert Cameron" <bertcameron@rogers.com>
To: <isis-wg@juniper.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_004C_01C18FA8.F697B660"
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
X-OriginalArrivalTime: 28 Dec 2001 19:06:43.0546 (UTC) FILETIME=[C9D973A0:01C18FD2]
Subject: [Isis-wg] (no subject)
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 28 Dec 2001 14:07:19 -0500

This is a multi-part message in MIME format.

------=_NextPart_000_004C_01C18FA8.F697B660
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

who isis

------=_NextPart_000_004C_01C18FA8.F697B660
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2712.300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>who isis</FONT></DIV></BODY></HTML>

------=_NextPart_000_004C_01C18FA8.F697B660--

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 28 14:54:09 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11249
	for <isis-archive@odin.ietf.org>; Fri, 28 Dec 2001 14:54:07 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSJp1172157;
	Fri, 28 Dec 2001 11:51:01 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSJfd172092
	for <isis-wg@spider.juniper.net>; Fri, 28 Dec 2001 11:41:39 -0800 (PST)
	(envelope-from naiming@redback.com)
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 755121DCC74; Fri, 28 Dec 2001 11:42:41 -0800 (PST)
To: Nagasta Bagamba <nagastabagamba@yahoo.com>
Cc: isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] IGP shortcuts 
In-reply-to: Mail from Nagasta Bagamba <nagastabagamba@yahoo.com> 
 dated Thu, 27 Dec 2001 13:41:38 PST
 <20011227214138.86295.qmail@web21110.mail.yahoo.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20011228194241.755121DCC74@prattle.redback.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 28 Dec 2001 11:42:41 -0800

 ]Hi,
 ]
 ]I have some wonders about several issues in the draft
 ]"draft-hsmit-mpls-igp-spf-00.txt".
 ]
 ]1. In secrion 6.1: "The relative metric is bounded by
 ]minimum and maximum allowed metric values" 
 ]Is there any use for maximum value higher than 1?
 ]As I see it, any positive relative metric causes the
 ]TE-tunnel not to be used by the IGP, so there is no
 ]need for more than one positive value.

yes, it is not useful for relative metric > +1 if the igp
load sharing scheme is equal-cost.

but there is no need to restrict it as long as you know it will not
be used. if a paricular native path has metric of 10, and you set
absolute metric to 15, assume the native path does not change,
it's equivalent to setting the relative metric to +5 here.

 ]
 ]2. In section 4: "Traffic to nodes that are downstream
 ]of the tail-end nodes will also flow over those
 ]TE-tunnels"
 ]I find the word "downstream" a little bit problematic.
 ]It can be downstream to the node on the SPF tree OR
 ]downstream to the node on the IGP topology graph.
 ]I think it refers to the SPF tree, but is there any
 ]prevention from using TE-tunnels, as shortcuts, on the
 ]
 ]IGP topology graph instead of on the SPF tree? It
 ]looks like it will give more functionality and meaning
 ]to the word "shortcuts". Of course we have to be
 ]careful form routing loops, but with some basic rules
 ]it is possible... :)

i can't parse your sentence here, what is "downstream to SPF"
vs "downstream to IGP topology graph"?
how can you "form routing loops"? can you give an example
which actually causes routing loops?


- Naiming
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Dec 28 15:22:49 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11472
	for <isis-archive@odin.ietf.org>; Fri, 28 Dec 2001 15:22:48 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSKKB172311;
	Fri, 28 Dec 2001 12:20:11 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from bridge.axiowave.com ([216.49.69.50])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBSJp0172151
	for <isis-wg@spider.juniper.net>; Fri, 28 Dec 2001 11:51:01 -0800 (PST)
	(envelope-from jparker@axiowave.com)
Message-ID: <EB5FFC72F183D411B38200062957342901230038@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Les  Ginsberg'" <ginsberg@pluris.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] RE: New ISIS MIB Issue
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 28 Dec 2001 14:51:44 -0500

Thanks: will do.



- jeff parker
- axiowave networks
- All those who believe in psychokinesis, raise my hand.



> -----Original Message-----
> From: Les Ginsberg [mailto:ginsberg@pluris.com]
> Sent: Friday, December 28, 2001 2:50 PM
> To: 'Jeff Parker'
> Subject: New ISIS MIB Issue
> 
> 
> 
> 
> Jeff -
> 
> Here's another cleanup issue. In regards to:
> 
>      isisSysLSPIgnoreErrors OBJECT-TYPE
>          SYNTAX TruthValue
>          MAX-ACCESS read-create
>          STATUS current
>          DESCRIPTION
>              "If true, allow the router to ignore IS-IS link 
> state packets
>              (LSPs) that are received with internal checksum 
> errors rather
>              than purging the LSPs."
>          DEFVAL { false }
>      ::= { isisSysEntry 27 }
> 
> The truth of the matter is that the strategy of purging 
> received LSPs w
> checksum errors was a defect in the 1992 spec which was corrected by
> Technical Corrigendum I years ago. This change has been 
> incorporated into
> 10589:2001. The revised spec (7.3.14.2a) now reads:
> 
> a)	An Intermediate system receiving a Link State PDU with 
> an incorrect
> LSP Checksum or with an invalid PDU syntax shall
> 
> 1)	generate a corruptedLSPReceived circuit event,
> 
> 2)	discard the PDU.
> 
> Popular implementations that have knobs to control ignoring 
> vs. purging
> notwithstanding, the fact is that a conformant implementation 
> should always
> ignore LSPs with checksum errors. Therefore, I think the 
> above should be
> removed from the MIB.
> 
> If you need further references let me know - I can dig up the 
> old defect
> reports if needed.
> 
>    Les
> 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Sat Dec 29 04:38:44 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26462
	for <isis-archive@lists.ietf.org>; Sat, 29 Dec 2001 04:38:43 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBT9Yl175662;
	Sat, 29 Dec 2001 01:34:47 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from web13207.mail.yahoo.com (web13207.mail.yahoo.com [216.136.174.192])
	by external.juniper.net (8.11.6/8.11.6) with SMTP id fBT9O4175612
	for <isis-wg@spider.juniper.net>; Sat, 29 Dec 2001 01:24:04 -0800 (PST)
	(envelope-from dasnabendu@yahoo.com)
Message-ID: <20011229092513.39392.qmail@web13207.mail.yahoo.com>
Received: from [203.200.20.224] by web13207.mail.yahoo.com via HTTP; Sat, 29 Dec 2001 01:25:13 PST
From: nabendu das <dasnabendu@yahoo.com>
To: isis-wg@spider.juniper.net
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [Isis-wg] minimumLSPTransmissionInterval
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 29 Dec 2001 01:25:13 -0800 (PST)

hi list,
confusion about minLSPTransmissionInterval.
in ISO-10589 7.3.14.3 ,
"The Update Process scans the Link State Database for
Link Stat PDUs with SRMflags set. when one is found,
provided the timestamp lastSent indicates that it was
propagated no more recently than
minimumLSPTransmissionInterval, the IS shall 
a) transmit it on all circuits with SRMflags set, and
b) update lastSent."
now here it is not being told whether above mentioned
check is for P2P link or Broadcast link, Do we need to
check this for p2p as well as for LAN case???? or
minimumBroadcastLSPTransmissionInterval takes care of
that, and if so " how does
minimumBroadcastLSPTransmissionInterval controls how
fast we send back-to-back LSPs as per the new
MIB(isisCircLevelLSPThrottle)???? is it like the way
as stated in ISO 10589 in 7.3.15.6, as "an IS is
permitted to transmit a small no of LSPs with a
shorter seperation interval, provided that no more
than 1000/minimumBroadcastLSPTransmissionInterval LSPs
are
transmitted in any one second period."????????

and again in 7.3.15.5,
" an IS shall perform the folln every
minimumLSPTransmissionInterval -
for all p2p circuits c transmit all LSPs that have
SRMflags set on circuit C."
 and below that
" the interval between two consecutive transmission of
the same LSP shall be at least
minimumLSPTransmissionInterval" 
the question is if the IS shall perform the action as
stated in 7.3.15.5 for every
minimumLSPTransmissionInterval, then the interval
between two consecutive transmission of the same LSP
will be at least minimumLSPTransmissionInterval
anyway. so why that has again been stated.???

Plz help.
thanking in advance.


__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Sat Dec 29 16:52:19 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00847
	for <isis-archive@lists.ietf.org>; Sat, 29 Dec 2001 16:52:19 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBTLm8181537;
	Sat, 29 Dec 2001 13:48:08 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from web21109.mail.yahoo.com (web21109.mail.yahoo.com [216.136.227.111])
	by external.juniper.net (8.11.6/8.11.6) with SMTP id fBTLNf181421
	for <isis-wg@spider.juniper.net>; Sat, 29 Dec 2001 13:23:41 -0800 (PST)
	(envelope-from nagastabagamba@yahoo.com)
Message-ID: <20011229212454.55644.qmail@web21109.mail.yahoo.com>
Received: from [212.179.34.114] by web21109.mail.yahoo.com via HTTP; Sat, 29 Dec 2001 13:24:54 PST
From: Nagasta Bagamba <nagastabagamba@yahoo.com>
Subject: Re: [Isis-wg] IGP shortcuts 
To: Naiming Shen <naiming@redback.com>
Cc: isis-wg@spider.juniper.net
In-Reply-To: <20011228194241.755121DCC74@prattle.redback.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sat, 29 Dec 2001 13:24:54 -0800 (PST)

Hi,

I'm sorry, my second question wasn't clear enough.
I'll try to explain my question through examples.
There are 3 ways to use TE-tunnels as shortcuts. I'll
explain each one of them through examples. 
Topology A will be used for introducing case 1. This
case refers just to the nodes (ISs) in the topology,
not to the leafs (IPs).
Topology B will be used for introducing cases 2 and 3.
Those cases refers especially to the leafs (IPs) of
the tree.

Topology A:
      
      10
    A----B
  9 |    | 10
    C----D
      10

  TE-tunnel from A to B, relative -5.
  Source node - A.
  SPT (without TE-tunnels):
        A
    10 / \ 9
      B  C
         | 10
         D


Case 1: Using TE-tunnels as IGP links
If we use TE-tunnels after building the SPF tree, we
will get:
        A
     5 / \ 9
      B  C
         | 10
         D

But, if we look at the TE-tunnel as a link with cost 5
(10-5), and use it through the build of the SPT, we'll
get:

        A
     5 / \ 9
      B  C
   10 |
      D


Topology B:
      
      A
  10 / \ 9
    /   \
   B----C
     10

  TE-tunnel from A to B, relative -5.
  Source node - A.
  There is network X between B and C.
  SPT (without TE-tunnels):
        A
    10 / \ 9
      B  C
         | 10
         X
  
Case 2: Use TE-tunnels after building the nodes (ISs)
of the SPF tree, but before adding the leafs (IP
reachability).
The result:

        A
     5 / \ 9
      B  C
   10 |
      X

Case 3: Use TE-tunnels after building the whole SPF
tree (nodes and leafs).
The result:

        A
     5 / \ 9
      B  C
         | 10
         X


Case 3 is routing-loop-free.
Cases 1 and 2 can create routing-loops. To avoid it,
we must not allow negative links in the graph (it
seems impossible with the absolute metric type).

My question is - which of the above cases is the one
the draft refers to?

Nagi

--- Naiming Shen <naiming@redback.com> wrote:
>  ]Hi,
>  ]
>  ]I have some wonders about several issues in the
> draft
>  ]"draft-hsmit-mpls-igp-spf-00.txt".
>  ]
>  ]1. In secrion 6.1: "The relative metric is bounded
> by
>  ]minimum and maximum allowed metric values" 
>  ]Is there any use for maximum value higher than 1?
>  ]As I see it, any positive relative metric causes
> the
>  ]TE-tunnel not to be used by the IGP, so there is
> no
>  ]need for more than one positive value.
> 
> yes, it is not useful for relative metric > +1 if
> the igp
> load sharing scheme is equal-cost.
> 
> but there is no need to restrict it as long as you
> know it will not
> be used. if a paricular native path has metric of
> 10, and you set
> absolute metric to 15, assume the native path does
> not change,
> it's equivalent to setting the relative metric to +5
> here.
> 
>  ]
>  ]2. In section 4: "Traffic to nodes that are
> downstream
>  ]of the tail-end nodes will also flow over those
>  ]TE-tunnels"
>  ]I find the word "downstream" a little bit
> problematic.
>  ]It can be downstream to the node on the SPF tree
> OR
>  ]downstream to the node on the IGP topology graph.
>  ]I think it refers to the SPF tree, but is there
> any
>  ]prevention from using TE-tunnels, as shortcuts, on
> the
>  ]
>  ]IGP topology graph instead of on the SPF tree? It
>  ]looks like it will give more functionality and
> meaning
>  ]to the word "shortcuts". Of course we have to be
>  ]careful form routing loops, but with some basic
> rules
>  ]it is possible... :)
> 
> i can't parse your sentence here, what is
> "downstream to SPF"
> vs "downstream to IGP topology graph"?
> how can you "form routing loops"? can you give an
> example
> which actually causes routing loops?
> 
> 
> - Naiming
> _______________________________________________
> Isis-wg mailing list  - 
> Isis-wg@external.juniper.net
> http://external.juniper.net/mailman/listinfo/isis-wg






__________________________________________________
Do You Yahoo!?
Send your FREE holiday greetings online!
http://greetings.yahoo.com
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Sat Dec 29 23:30:17 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA04686
	for <isis-archive@odin.ietf.org>; Sat, 29 Dec 2001 23:30:16 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBU4Qd183227;
	Sat, 29 Dec 2001 20:26:39 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from xover.mindspeed.com (cnxt10002.conexant.com [198.62.10.2])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBS4EI167552
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 20:14:18 -0800 (PST)
	(envelope-from VishwasM@netplane.com)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <ZN3QP2DS>; Thu, 27 Dec 2001 23:15:18 -0500
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328291723@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'Les  Ginsberg'" <ginsberg@pluris.com>,
        "'Jeff Parker'"
	 <jparker@axiowave.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 23:15:28 -0500

Les,

I meant "remaining lifetime" field in the LSP and not age(wrong use of
terminology on my part).

So this is what I meant:-

1. If the remaining Lifetime is > MaxAge value in the router, treat the
remaining lifetime as if it was MaxAge.
2. MaxLSPGenInt should be less than min value of MaxAge for all routers in
the domain.
3. The difference(as pointed out) should be at least enough so that the LSP
is propagated thruout the domain(so that no one purges the LSP before the
new version reaches it).

Thanks,
Vishwas

-----Original Message-----
From: Les Ginsberg [mailto:ginsberg@pluris.com]
Sent: Friday, December 28, 2001 2:31 AM
To: 'Manral, Vishwas'; 'Jeff Parker'
Cc: IS-IS-WG (E-mail)
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt


> 
> Treating any LSP with age above Maxage could be done as if 
> age was MaxAge.
> May be we need to recommend that all routers in a domain have the same
> Maxage(and the value of MaxLSPGenInt should be less than the 
> value of the
> smallest value of MaxAge in any router in the domain)value 
> for things to
> work ok(and then we can treat all LSP's with age greater than 
> MaxAge as
> MaxAge), we could raise a trap on getting an LSP with age greater than
> MaxAge.
>  

The change from an architectural constant to a configurable value was
presumably made based on customer demand. To require, or even suggest, that
an implementation treat an LSP received with a lifetime > the architectural
constant MAXAGE as if it were set to MAXAGE is a VERY BAD thing to do.
Routers which did this could end up purging an LSP from their database
before the originating router's MaxLSPGenInt timer fired, which would cause
unnecessary flapping. If you want to argue that the current "de facto
standard" of making LSP lifetime configurable should be made invalid you
will at least be addressing the issue directly - though I suspect you will
get little support. Circumventing the issue by pretending the value is not
configurable is unwise.

It is also worth noting that, as you suggest, there is a necessary
relationship between LSP lifetime and MaxLSPGenInt, namely:

1)MaxLSPGenInt must be less than LSPlifetime
2)(LSPlifetime - MaxLSPGenInt) should be large enough to allow propagation
of the LSP throughout the area/domain before the old LSP ages out

If LSP lifetime is modified from the "default" value of 1200 seconds, it
makes sense to change MaxLSPGenInt in a like manner.

   Les
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Sun Dec 30 05:37:27 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15016
	for <isis-archive@odin.ietf.org>; Sun, 30 Dec 2001 05:37:26 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBUAXX184802;
	Sun, 30 Dec 2001 02:33:33 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from yarilo.pluris.com (yarilo.pluris.com [208.227.9.200])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBS4xE167736
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 20:59:14 -0800 (PST)
	(envelope-from ginsberg@pluris.com)
Received: from avalon.pluris.com (avalon.pluris.com [172.16.50.49])
	by yarilo.pluris.com (8.9.2/8.9.1) with ESMTP id UAA23615;
	Thu, 27 Dec 2001 20:59:13 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <YNMD1PD1>; Thu, 27 Dec 2001 20:59:13 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA01B3F6A0@avalon.pluris.com>
From: Les  Ginsberg <ginsberg@pluris.com>
To: "'Manral, Vishwas'" <VishwasM@netplane.com>,
        Les  Ginsberg
	 <ginsberg@pluris.com>,
        "'Jeff Parker'" <jparker@axiowave.com>
Cc: "IS-IS-WG (E-mail)" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 27 Dec 2001 20:59:12 -0800

Vishwas -

Makes no difference. From the point of view of the receiver of an LSP, it
has no way of knowing what the value of LSP lifetime may be on the
originating IS since the remaining lifetime field gets modified, based on
elapsed time, prior to flooding. All the receiver can say is that the
originating IS has a value for LSP lifetime which is >= the original
received remaining lifetime.

If an IS arbitrarily decreases the remaining lifetime of an LSP it has
received, then it is quite possible that the LSP will age out of the local
database before the originating router regenerates that LSP. The protocol
will eventually recover, but in order to do so the LSP will first be purged,
causing an SPF to be run on all routers (or many of them anyway) with this
LSP absent, and then the originating router will, on seeing the purged
version, regenerate that LSP, flood it, and a second SPF will be run on
every router. Reachability advertised in this LSP will temporarily disappear
from the forwarding databases throughout the area/domain and then be
restored. This is highly undesirable.

  Les


> 
> 
> Les,
> 
> I meant "remaining lifetime" field in the LSP and not age(wrong use of
> terminology on my part).
> 
> So this is what I meant:-
> 
> 1. If the remaining Lifetime is > MaxAge value in the router, 
> treat the
> remaining lifetime as if it was MaxAge.
> 2. MaxLSPGenInt should be less than min value of MaxAge for 
> all routers in
> the domain.
> 3. The difference(as pointed out) should be at least enough 
> so that the LSP
> is propagated thruout the domain(so that no one purges the 
> LSP before the
> new version reaches it).
> 
> Thanks,
> Vishwas
> 
> -----Original Message-----
> From: Les Ginsberg [mailto:ginsberg@pluris.com]
> Sent: Friday, December 28, 2001 2:31 AM
> To: 'Manral, Vishwas'; 'Jeff Parker'
> Cc: IS-IS-WG (E-mail)
> Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
> 
> 
> > 
> > Treating any LSP with age above Maxage could be done as if 
> > age was MaxAge.
> > May be we need to recommend that all routers in a domain 
> have the same
> > Maxage(and the value of MaxLSPGenInt should be less than the 
> > value of the
> > smallest value of MaxAge in any router in the domain)value 
> > for things to
> > work ok(and then we can treat all LSP's with age greater than 
> > MaxAge as
> > MaxAge), we could raise a trap on getting an LSP with age 
> greater than
> > MaxAge.
> >  
> 
> The change from an architectural constant to a configurable value was
> presumably made based on customer demand. To require, or even 
> suggest, that
> an implementation treat an LSP received with a lifetime > the 
> architectural
> constant MAXAGE as if it were set to MAXAGE is a VERY BAD thing to do.
> Routers which did this could end up purging an LSP from their database
> before the originating router's MaxLSPGenInt timer fired, 
> which would cause
> unnecessary flapping. If you want to argue that the current "de facto
> standard" of making LSP lifetime configurable should be made 
> invalid you
> will at least be addressing the issue directly - though I 
> suspect you will
> get little support. Circumventing the issue by pretending the 
> value is not
> configurable is unwise.
> 
> It is also worth noting that, as you suggest, there is a necessary
> relationship between LSP lifetime and MaxLSPGenInt, namely:
> 
> 1)MaxLSPGenInt must be less than LSPlifetime
> 2)(LSPlifetime - MaxLSPGenInt) should be large enough to 
> allow propagation
> of the LSP throughout the area/domain before the old LSP ages out
> 
> If LSP lifetime is modified from the "default" value of 1200 
> seconds, it
> makes sense to change MaxLSPGenInt in a like manner.
> 
>    Les
> 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Sun Dec 30 06:58:44 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA15400
	for <isis-archive@odin.ietf.org>; Sun, 30 Dec 2001 06:58:43 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBUBtA185646;
	Sun, 30 Dec 2001 03:55:10 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from xover.mindspeed.com (cnxt10002.conexant.com [198.62.10.2])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBS5ai167892
	for <isis-wg@spider.juniper.net>; Thu, 27 Dec 2001 21:36:44 -0800 (PST)
	(envelope-from VishwasM@netplane.com)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <ZN3QP2F5>; Fri, 28 Dec 2001 00:37:44 -0500
Message-ID: <E7E13AAF2F3ED41197C100508BD6A328291725@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'Les  Ginsberg'" <ginsberg@pluris.com>
Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 28 Dec 2001 00:37:40 -0500

Les,

I get the point you are trying to make. The problem you say would happen
whenever there is a diff in MaxAge in IS's in the domain(and the LSP's for
some reason is not refreshed).

This is what I am trying to say. The MaxAge would be the value which would
be put in a self LSP, as remaining lifetime when we are originating a new
LSP. If the remaining life time is greater than MaxAge for some other IS, it
should treat the stuff as if MaxAge(in the sense it should not drop the LSP,
MIB ops on remaining lifetime shld give age as MaxAge(if any), SPF(age
value) etc), however it should start the purge(MaxAge) timer for that LSP
with the value of "remaining lifetime" field(So remaining lifetime would be
zero after remaining life time period). However this would cause the MaxAge
field to be used as in the remaining lifetime and not as configured in the
IS itself.(some problems/loopholes/against existing approach with this
approach??)

This way all people would purge the LSP at nearly the same time(so the
problem described would not arise). 

Thanks,
Vishwas

-----Original Message-----
From: Les Ginsberg [mailto:ginsberg@pluris.com]
Sent: Friday, December 28, 2001 10:29 AM
To: 'Manral, Vishwas'; Les Ginsberg; 'Jeff Parker'
Cc: IS-IS-WG (E-mail)
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt


Vishwas -

Makes no difference. From the point of view of the receiver of an LSP, it
has no way of knowing what the value of LSP lifetime may be on the
originating IS since the remaining lifetime field gets modified, based on
elapsed time, prior to flooding. All the receiver can say is that the
originating IS has a value for LSP lifetime which is >= the original
received remaining lifetime.

If an IS arbitrarily decreases the remaining lifetime of an LSP it has
received, then it is quite possible that the LSP will age out of the local
database before the originating router regenerates that LSP. The protocol
will eventually recover, but in order to do so the LSP will first be purged,
causing an SPF to be run on all routers (or many of them anyway) with this
LSP absent, and then the originating router will, on seeing the purged
version, regenerate that LSP, flood it, and a second SPF will be run on
every router. Reachability advertised in this LSP will temporarily disappear
from the forwarding databases throughout the area/domain and then be
restored. This is highly undesirable.

  Les


> 
> 
> Les,
> 
> I meant "remaining lifetime" field in the LSP and not age(wrong use of
> terminology on my part).
> 
> So this is what I meant:-
> 
> 1. If the remaining Lifetime is > MaxAge value in the router, 
> treat the
> remaining lifetime as if it was MaxAge.
> 2. MaxLSPGenInt should be less than min value of MaxAge for 
> all routers in
> the domain.
> 3. The difference(as pointed out) should be at least enough 
> so that the LSP
> is propagated thruout the domain(so that no one purges the 
> LSP before the
> new version reaches it).
> 
> Thanks,
> Vishwas
> 
> -----Original Message-----
> From: Les Ginsberg [mailto:ginsberg@pluris.com]
> Sent: Friday, December 28, 2001 2:31 AM
> To: 'Manral, Vishwas'; 'Jeff Parker'
> Cc: IS-IS-WG (E-mail)
> Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
> 
> 
> > 
> > Treating any LSP with age above Maxage could be done as if 
> > age was MaxAge.
> > May be we need to recommend that all routers in a domain 
> have the same
> > Maxage(and the value of MaxLSPGenInt should be less than the 
> > value of the
> > smallest value of MaxAge in any router in the domain)value 
> > for things to
> > work ok(and then we can treat all LSP's with age greater than 
> > MaxAge as
> > MaxAge), we could raise a trap on getting an LSP with age 
> greater than
> > MaxAge.
> >  
> 
> The change from an architectural constant to a configurable value was
> presumably made based on customer demand. To require, or even 
> suggest, that
> an implementation treat an LSP received with a lifetime > the 
> architectural
> constant MAXAGE as if it were set to MAXAGE is a VERY BAD thing to do.
> Routers which did this could end up purging an LSP from their database
> before the originating router's MaxLSPGenInt timer fired, 
> which would cause
> unnecessary flapping. If you want to argue that the current "de facto
> standard" of making LSP lifetime configurable should be made 
> invalid you
> will at least be addressing the issue directly - though I 
> suspect you will
> get little support. Circumventing the issue by pretending the 
> value is not
> configurable is unwise.
> 
> It is also worth noting that, as you suggest, there is a necessary
> relationship between LSP lifetime and MaxLSPGenInt, namely:
> 
> 1)MaxLSPGenInt must be less than LSPlifetime
> 2)(LSPlifetime - MaxLSPGenInt) should be large enough to 
> allow propagation
> of the LSP throughout the area/domain before the old LSP ages out
> 
> If LSP lifetime is modified from the "default" value of 1200 
> seconds, it
> makes sense to change MaxLSPGenInt in a like manner.
> 
>    Les
> 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Sun Dec 30 13:48:53 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17437
	for <isis-archive@odin.ietf.org>; Sun, 30 Dec 2001 13:48:52 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBUIj0187352;
	Sun, 30 Dec 2001 10:45:00 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBUIiE187337
	for <isis-wg@spider.juniper.net>; Sun, 30 Dec 2001 10:44:14 -0800 (PST)
	(envelope-from dkatz@juniper.net)
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 fBUIjR680553;
	Sun, 30 Dec 2001 10:45:27 -0800 (PST)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost)
	by cirrus.juniper.net (8.11.6/8.11.6) id fBUIipb50547;
	Sun, 30 Dec 2001 10:44:51 -0800 (PST)
	(envelope-from dkatz@cirrus.juniper.net)
Message-Id: <200112301844.fBUIipb50547@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: VishwasM@netplane.com
CC: ginsberg@pluris.com, isis-wg@spider.juniper.net
In-reply-to: 
	<E7E13AAF2F3ED41197C100508BD6A328291725@india_exch.hyderabad.mindspeed.com>
	(VishwasM@netplane.com)
Subject: Re: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
References:  <E7E13AAF2F3ED41197C100508BD6A328291725@india_exch.hyderabad.mindspeed.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 30 Dec 2001 10:44:51 -0800 (PST)

I haven't been paying a lot of attention to this conversation, but that
never stopped me from commenting before.

One of the nice things about ISIS (as compared to OSPF) is that there
are very few things that are truly architectural constants (as in, if
you don't use this value, the protocol won't work.)  Further, there
are less settable parameters that must be coordinated between systems
in order for the network to function.

The LSP lifetime (along with the adjacency holding time) has the very
nice property that everybody can pick different values and the network
Just Works.  This has operationally saved people more times than I can
count.

Any system that makes judgement on the choice of values of these parameters
set by another system is just plain broken.

--Dave

   From: "Manral, Vishwas" <VishwasM@netplane.com>
   Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>
   Content-Type: text/plain;
	   charset="iso-8859-1"
   Sender: isis-wg-admin@spider.juniper.net
   X-BeenThere: isis-wg@external.juniper.net
   X-Mailman-Version: 2.0rc1
   Precedence: bulk
   List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
   List-Post: <mailto:isis-wg@external.juniper.net>
   List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	   <mailto:isis-wg-request@external.juniper.net?subject=subscribe>
   List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
   List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	   <mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
   List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
   Date: Fri, 28 Dec 2001 00:37:40 -0500

   Les,

   I get the point you are trying to make. The problem you say would happen
   whenever there is a diff in MaxAge in IS's in the domain(and the LSP's for
   some reason is not refreshed).

   This is what I am trying to say. The MaxAge would be the value which would
   be put in a self LSP, as remaining lifetime when we are originating a new
   LSP. If the remaining life time is greater than MaxAge for some other IS, it
   should treat the stuff as if MaxAge(in the sense it should not drop the LSP,
   MIB ops on remaining lifetime shld give age as MaxAge(if any), SPF(age
   value) etc), however it should start the purge(MaxAge) timer for that LSP
   with the value of "remaining lifetime" field(So remaining lifetime would be
   zero after remaining life time period). However this would cause the MaxAge
   field to be used as in the remaining lifetime and not as configured in the
   IS itself.(some problems/loopholes/against existing approach with this
   approach??)

   This way all people would purge the LSP at nearly the same time(so the
   problem described would not arise). 

   Thanks,
   Vishwas

   -----Original Message-----
   From: Les Ginsberg [mailto:ginsberg@pluris.com]
   Sent: Friday, December 28, 2001 10:29 AM
   To: 'Manral, Vishwas'; Les Ginsberg; 'Jeff Parker'
   Cc: IS-IS-WG (E-mail)
   Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt


   Vishwas -

   Makes no difference. From the point of view of the receiver of an LSP, it
   has no way of knowing what the value of LSP lifetime may be on the
   originating IS since the remaining lifetime field gets modified, based on
   elapsed time, prior to flooding. All the receiver can say is that the
   originating IS has a value for LSP lifetime which is >= the original
   received remaining lifetime.

   If an IS arbitrarily decreases the remaining lifetime of an LSP it has
   received, then it is quite possible that the LSP will age out of the local
   database before the originating router regenerates that LSP. The protocol
   will eventually recover, but in order to do so the LSP will first be purged,
   causing an SPF to be run on all routers (or many of them anyway) with this
   LSP absent, and then the originating router will, on seeing the purged
   version, regenerate that LSP, flood it, and a second SPF will be run on
   every router. Reachability advertised in this LSP will temporarily disappear
   from the forwarding databases throughout the area/domain and then be
   restored. This is highly undesirable.

     Les


   > 
   > 
   > Les,
   > 
   > I meant "remaining lifetime" field in the LSP and not age(wrong use of
   > terminology on my part).
   > 
   > So this is what I meant:-
   > 
   > 1. If the remaining Lifetime is > MaxAge value in the router, 
   > treat the
   > remaining lifetime as if it was MaxAge.
   > 2. MaxLSPGenInt should be less than min value of MaxAge for 
   > all routers in
   > the domain.
   > 3. The difference(as pointed out) should be at least enough 
   > so that the LSP
   > is propagated thruout the domain(so that no one purges the 
   > LSP before the
   > new version reaches it).
   > 
   > Thanks,
   > Vishwas
   > 
   > -----Original Message-----
   > From: Les Ginsberg [mailto:ginsberg@pluris.com]
   > Sent: Friday, December 28, 2001 2:31 AM
   > To: 'Manral, Vishwas'; 'Jeff Parker'
   > Cc: IS-IS-WG (E-mail)
   > Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
   > 
   > 
   > > 
   > > Treating any LSP with age above Maxage could be done as if 
   > > age was MaxAge.
   > > May be we need to recommend that all routers in a domain 
   > have the same
   > > Maxage(and the value of MaxLSPGenInt should be less than the 
   > > value of the
   > > smallest value of MaxAge in any router in the domain)value 
   > > for things to
   > > work ok(and then we can treat all LSP's with age greater than 
   > > MaxAge as
   > > MaxAge), we could raise a trap on getting an LSP with age 
   > greater than
   > > MaxAge.
   > >  
   > 
   > The change from an architectural constant to a configurable value was
   > presumably made based on customer demand. To require, or even 
   > suggest, that
   > an implementation treat an LSP received with a lifetime > the 
   > architectural
   > constant MAXAGE as if it were set to MAXAGE is a VERY BAD thing to do.
   > Routers which did this could end up purging an LSP from their database
   > before the originating router's MaxLSPGenInt timer fired, 
   > which would cause
   > unnecessary flapping. If you want to argue that the current "de facto
   > standard" of making LSP lifetime configurable should be made 
   > invalid you
   > will at least be addressing the issue directly - though I 
   > suspect you will
   > get little support. Circumventing the issue by pretending the 
   > value is not
   > configurable is unwise.
   > 
   > It is also worth noting that, as you suggest, there is a necessary
   > relationship between LSP lifetime and MaxLSPGenInt, namely:
   > 
   > 1)MaxLSPGenInt must be less than LSPlifetime
   > 2)(LSPlifetime - MaxLSPGenInt) should be large enough to 
   > allow propagation
   > of the LSP throughout the area/domain before the old LSP ages out
   > 
   > If LSP lifetime is modified from the "default" value of 1200 
   > seconds, it
   > makes sense to change MaxLSPGenInt in a like manner.
   > 
   >    Les
   > 
   _______________________________________________
   Isis-wg mailing list  -  Isis-wg@external.juniper.net
   http://external.juniper.net/mailman/listinfo/isis-wg

_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 31 00:29:22 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA23061
	for <isis-archive@odin.ietf.org>; Mon, 31 Dec 2001 00:29:21 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBV5PB189995;
	Sun, 30 Dec 2001 21:25:11 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from xover.mindspeed.com (cnxt10002.conexant.com [198.62.10.2])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBV50h189889
	for <isis-wg@spider.juniper.net>; Sun, 30 Dec 2001 21:00:43 -0800 (PST)
	(envelope-from VishwasM@netplane.com)
Received: by XOVER.dedham.mindspeed.com with Internet Mail Service (5.5.2653.19)
	id <ZN3QPKR7>; Mon, 31 Dec 2001 00:02:01 -0500
Message-ID: <E7E13AAF2F3ED41197C100508BD6A32829174E@india_exch.hyderabad.mindspeed.com>
From: "Manral, Vishwas" <VishwasM@netplane.com>
To: "'Dave Katz'" <dkatz@juniper.net>
Cc: ginsberg@pluris.com, isis-wg@spider.juniper.net
Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 31 Dec 2001 00:02:12 -0500

Dave,

We have sort of agreed, that not all architectural constants described in
ISIS are "truly architectural constants" and may be configureable also the
fact that making assumptions based on a constant MaxAge/some other
parameters is wrong.

However this brings me to another issue. I have been reading thru the mail
archives and I find a lot of things that are not done in the RFC way in the
current implementations. Wouldn't it be helpful if we had a document that
described the "Best Current Practices"? (I had written to Tony regarding the
same and he felt "yes, we could if we find a volunteer but then again, new
verison of ISIS document is supposed to fix that stuff").

Thanks,
Vishwas

-----Original Message-----
From: Dave Katz [mailto:dkatz@juniper.net]
Sent: Monday, December 31, 2001 12:15 AM
To: VishwasM@netplane.com
Cc: ginsberg@pluris.com; isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt


I haven't been paying a lot of attention to this conversation, but that
never stopped me from commenting before.

One of the nice things about ISIS (as compared to OSPF) is that there
are very few things that are truly architectural constants (as in, if
you don't use this value, the protocol won't work.)  Further, there
are less settable parameters that must be coordinated between systems
in order for the network to function.

The LSP lifetime (along with the adjacency holding time) has the very
nice property that everybody can pick different values and the network
Just Works.  This has operationally saved people more times than I can
count.

Any system that makes judgement on the choice of values of these parameters
set by another system is just plain broken.

--Dave

   From: "Manral, Vishwas" <VishwasM@netplane.com>
   Cc: "'isis-wg@spider.juniper.net'" <isis-wg@spider.juniper.net>
   Content-Type: text/plain;
	   charset="iso-8859-1"
   Sender: isis-wg-admin@spider.juniper.net
   X-BeenThere: isis-wg@external.juniper.net
   X-Mailman-Version: 2.0rc1
   Precedence: bulk
   List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
   List-Post: <mailto:isis-wg@external.juniper.net>
   List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	   <mailto:isis-wg-request@external.juniper.net?subject=subscribe>
   List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
   List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	   <mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
   List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
   Date: Fri, 28 Dec 2001 00:37:40 -0500

   Les,

   I get the point you are trying to make. The problem you say would happen
   whenever there is a diff in MaxAge in IS's in the domain(and the LSP's
for
   some reason is not refreshed).

   This is what I am trying to say. The MaxAge would be the value which
would
   be put in a self LSP, as remaining lifetime when we are originating a new
   LSP. If the remaining life time is greater than MaxAge for some other IS,
it
   should treat the stuff as if MaxAge(in the sense it should not drop the
LSP,
   MIB ops on remaining lifetime shld give age as MaxAge(if any), SPF(age
   value) etc), however it should start the purge(MaxAge) timer for that LSP
   with the value of "remaining lifetime" field(So remaining lifetime would
be
   zero after remaining life time period). However this would cause the
MaxAge
   field to be used as in the remaining lifetime and not as configured in
the
   IS itself.(some problems/loopholes/against existing approach with this
   approach??)

   This way all people would purge the LSP at nearly the same time(so the
   problem described would not arise). 

   Thanks,
   Vishwas

   -----Original Message-----
   From: Les Ginsberg [mailto:ginsberg@pluris.com]
   Sent: Friday, December 28, 2001 10:29 AM
   To: 'Manral, Vishwas'; Les Ginsberg; 'Jeff Parker'
   Cc: IS-IS-WG (E-mail)
   Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt


   Vishwas -

   Makes no difference. From the point of view of the receiver of an LSP, it
   has no way of knowing what the value of LSP lifetime may be on the
   originating IS since the remaining lifetime field gets modified, based on
   elapsed time, prior to flooding. All the receiver can say is that the
   originating IS has a value for LSP lifetime which is >= the original
   received remaining lifetime.

   If an IS arbitrarily decreases the remaining lifetime of an LSP it has
   received, then it is quite possible that the LSP will age out of the
local
   database before the originating router regenerates that LSP. The protocol
   will eventually recover, but in order to do so the LSP will first be
purged,
   causing an SPF to be run on all routers (or many of them anyway) with
this
   LSP absent, and then the originating router will, on seeing the purged
   version, regenerate that LSP, flood it, and a second SPF will be run on
   every router. Reachability advertised in this LSP will temporarily
disappear
   from the forwarding databases throughout the area/domain and then be
   restored. This is highly undesirable.

     Les


   > 
   > 
   > Les,
   > 
   > I meant "remaining lifetime" field in the LSP and not age(wrong use of
   > terminology on my part).
   > 
   > So this is what I meant:-
   > 
   > 1. If the remaining Lifetime is > MaxAge value in the router, 
   > treat the
   > remaining lifetime as if it was MaxAge.
   > 2. MaxLSPGenInt should be less than min value of MaxAge for 
   > all routers in
   > the domain.
   > 3. The difference(as pointed out) should be at least enough 
   > so that the LSP
   > is propagated thruout the domain(so that no one purges the 
   > LSP before the
   > new version reaches it).
   > 
   > Thanks,
   > Vishwas
   > 
   > -----Original Message-----
   > From: Les Ginsberg [mailto:ginsberg@pluris.com]
   > Sent: Friday, December 28, 2001 2:31 AM
   > To: 'Manral, Vishwas'; 'Jeff Parker'
   > Cc: IS-IS-WG (E-mail)
   > Subject: RE: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
   > 
   > 
   > > 
   > > Treating any LSP with age above Maxage could be done as if 
   > > age was MaxAge.
   > > May be we need to recommend that all routers in a domain 
   > have the same
   > > Maxage(and the value of MaxLSPGenInt should be less than the 
   > > value of the
   > > smallest value of MaxAge in any router in the domain)value 
   > > for things to
   > > work ok(and then we can treat all LSP's with age greater than 
   > > MaxAge as
   > > MaxAge), we could raise a trap on getting an LSP with age 
   > greater than
   > > MaxAge.
   > >  
   > 
   > The change from an architectural constant to a configurable value was
   > presumably made based on customer demand. To require, or even 
   > suggest, that
   > an implementation treat an LSP received with a lifetime > the 
   > architectural
   > constant MAXAGE as if it were set to MAXAGE is a VERY BAD thing to do.
   > Routers which did this could end up purging an LSP from their database
   > before the originating router's MaxLSPGenInt timer fired, 
   > which would cause
   > unnecessary flapping. If you want to argue that the current "de facto
   > standard" of making LSP lifetime configurable should be made 
   > invalid you
   > will at least be addressing the issue directly - though I 
   > suspect you will
   > get little support. Circumventing the issue by pretending the 
   > value is not
   > configurable is unwise.
   > 
   > It is also worth noting that, as you suggest, there is a necessary
   > relationship between LSP lifetime and MaxLSPGenInt, namely:
   > 
   > 1)MaxLSPGenInt must be less than LSPlifetime
   > 2)(LSPlifetime - MaxLSPGenInt) should be large enough to 
   > allow propagation
   > of the LSP throughout the area/domain before the old LSP ages out
   > 
   > If LSP lifetime is modified from the "default" value of 1200 
   > seconds, it
   > makes sense to change MaxLSPGenInt in a like manner.
   > 
   >    Les
 
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Mon Dec 31 21:01:25 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09104
	for <isis-archive@odin.ietf.org>; Mon, 31 Dec 2001 21:01:24 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id g011vW195464;
	Mon, 31 Dec 2001 17:57:32 -0800 (PST)
	(envelope-from isis-wg-admin@spider.juniper.net)
Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10])
	by external.juniper.net (8.11.6/8.11.6) with ESMTP id fBV5xg190147
	for <isis-wg@spider.juniper.net>; Sun, 30 Dec 2001 21:59:42 -0800 (PST)
	(envelope-from dkatz@juniper.net)
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 fBV60w687628;
	Sun, 30 Dec 2001 22:00:58 -0800 (PST)
	(envelope-from dkatz@juniper.net)
Received: (from dkatz@localhost)
	by cirrus.juniper.net (8.11.6/8.11.6) id fBV60LH51764;
	Sun, 30 Dec 2001 22:00:21 -0800 (PST)
	(envelope-from dkatz@cirrus.juniper.net)
Message-Id: <200112310600.fBV60LH51764@cirrus.juniper.net>
From: Dave Katz <dkatz@juniper.net>
To: VishwasM@netplane.com
CC: ginsberg@pluris.com, isis-wg@spider.juniper.net
In-reply-to: 
	<E7E13AAF2F3ED41197C100508BD6A32829174E@india_exch.hyderabad.mindspeed.com>
	(VishwasM@netplane.com)
Subject: Re: [Isis-wg] RE: Regarding draft-ietf-isis-wg-mib-06.txt
References:  <E7E13AAF2F3ED41197C100508BD6A32829174E@india_exch.hyderabad.mindspeed.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Sun, 30 Dec 2001 22:00:21 -0800 (PST)

   X-JNPR-Received-From: outside
   From: "Manral, Vishwas" <VishwasM@netplane.com>
   Cc: ginsberg@pluris.com, isis-wg@spider.juniper.net
   Date: Mon, 31 Dec 2001 00:02:12 -0500
   Content-Type: text/plain
   X-OriginalArrivalTime: 31 Dec 2001 05:02:01.0453 (UTC) FILETIME=[483509D0:01C191B8]

   Dave,

   We have sort of agreed, that not all architectural constants described in
   ISIS are "truly architectural constants" and may be configureable also the
   fact that making assumptions based on a constant MaxAge/some other
   parameters is wrong.

   However this brings me to another issue. I have been reading thru the mail
   archives and I find a lot of things that are not done in the RFC way in the
   current implementations. Wouldn't it be helpful if we had a document that
   described the "Best Current Practices"? (I had written to Tony regarding the
   same and he felt "yes, we could if we find a volunteer but then again, new
   verison of ISIS document is supposed to fix that stuff").

I think the number of things that are done in practical conflict with
the spec is vanishingly small, where "practical conflict" is
interpreted as "a reasonable implementation would notice."
Excessively pedantic boxes have a way of fixing themselves one way or
another.

Most of these things are pretty obvious to anyone reasonably versed in
the art, though the potentially sticky ones (like not bothering with
ISHs) should probably be documented.

--Dave
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


