From isis-wg-admin@spider.juniper.net  Thu Mar  1 01:45:00 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA16477
	for <isis-archive@odin.ietf.org>; Thu, 1 Mar 2001 01:44: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 XAA44898;
	Wed, 28 Feb 2001 23:16:02 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id XAA44886
	for <isis-wg@spider.juniper.net>; Wed, 28 Feb 2001 23:15:45 -0800 (PST)
Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f216dta24555
	for <isis-wg@juniper.net>; Wed, 28 Feb 2001 22:39:55 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com ([63.200.51.249])
 by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with ESMTP id <0G9I0067TAIS56@mta6.snfc21.pbi.net> for isis-wg@juniper.net;
 Wed, 28 Feb 2001 22:40:06 -0800 (PST)
From: Tony Przygienda <prz@redback.com>
Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-multi-topology-00.txt
To: Serge Maskalik <serge@ivmg.net>
Cc: isis-wg@juniper.net
Message-id: <3A9DDE62.5F271B14@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: <200102281155.GAA02125@ietf.org> <20010228112859.C27593@ivmg.net>
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, 28 Feb 2001 21:30:10 -0800
Content-Transfer-Encoding: 7bit

Serge Maskalik wrote:

>      Tony et al.,
>
>    Outside of the protocol-based VPN (limited amount), the
>   benefits of having multiple parallel IGP topologies is
>   not obvious to me. Even the VPNs are questionable. Can
>   you explain why someone would want a different topology
>   for and in-band management network? Are there NSPs asking
>   for this functionality?
>
>         - Serge

yepp, some of the functionality has been requested by ISPs since
a while and the draft is somehow a generalization of the problem.
Look @ the section describing different topology numbers and their
uses.

And as we say "you can run only very limited amount of VPNs" that
way ...

        -- 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 Mar  1 03:05:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA27899
	for <isis-archive@odin.ietf.org>; Thu, 1 Mar 2001 03:05: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 AAA45273;
	Thu, 1 Mar 2001 00:37:03 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id AAA45261
	for <isis-wg@spider.juniper.net>; Thu, 1 Mar 2001 00:36:26 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2180Zq39029
	for <isis-wg@juniper.net>; Thu, 1 Mar 2001 00:00:35 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 2D910B76787; Thu,  1 Mar 2001 00:01:51 -0800 (PST)
To: Serge Maskalik <serge@ivmg.net>
Cc: isis-wg@juniper.net
Subject: Re: [Isis-wg] I-D ACTION:draft-ietf-isis-wg-multi-topology-00.txt 
In-reply-to: Mail from Serge Maskalik <serge@ivmg.net> 
 dated Wed, 28 Feb 2001 11:28:59 PST
 <20010228112859.C27593@ivmg.net> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20010301080151.2D910B76787@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: Thu, 01 Mar 2001 00:01:25 -0800


Serge,

 ]   Outside of the protocol-based VPN (limited amount), the 
 ]  benefits of having multiple parallel IGP topologies is 
 ]  not obvious to me. Even the VPNs are questionable. Can 
 ]  you explain why someone would want a different topology 
 ]  for and in-band management network?

In the case of applying M-ISIS in in-band management, "different topology"
probably means they share the same set of routers in the network, and
they may use different set of links each topology.

Using a simple example to illustrate this will be all the routers are 
connected using ATM links; between some pair of routers, there are 1 or 
2 VCs dedicated for in-band management use. The "normal" VCs are 
configured with high BW using UBR, the in-band management VCs are
configured with low BW using CBR. One ISIS topology only "sees" the UBR 
data links, the other only "sees" the CBR links. They use seperate routing 
tables.
The in-band management topology now has more protection from the general
routing problems, it can use it's own private address space, it can
use different QoS mechanisms and different ACLs on the links with less
concern of performance, it can also set different IGP costs on the links
independent of data traffic reqirements on other links.

In real life, you can replace the above CBR VCs example with dedicated T1s,
channelized bandwidths, etc.

 ]Are there NSPs asking for this functionality? 
 ]
 ] 	- Serge 

- 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 Mar  5 06:47:13 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA11440
	for <isis-archive@odin.ietf.org>; Mon, 5 Mar 2001 06:47:11 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA71129;
	Mon, 5 Mar 2001 04:18:03 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA71117
	for <isis-wg@spider.juniper.net>; Mon, 5 Mar 2001 04:17:44 -0800 (PST)
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f25BfAU49516
	for <isis-wg@juniper.net>; Mon, 5 Mar 2001 03:41:10 -0800 (PST)
X-JNPR-Received-From: outside
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA10675;
	Mon, 5 Mar 2001 06:42:40 -0500 (EST)
Message-Id: <200103051142.GAA10675@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: isis-wg@juniper.net
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Isis-wg] I-D ACTION:draft-ietf-isis-gmpls-extensions-02.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 05 Mar 2001 06:42:39 -0500

--NextPart

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

	Title		: IS-IS Extensions in Support of Generalized MPLS
	Author(s)	: K. Kompella, Y. Rekhter, A. Banerjee, 
                          J. Drake, G. Bernstein, D. Fedyk, E. Mannie,
                          B. Rajagopalan, V. Sharma
	Filename	: draft-ietf-isis-gmpls-extensions-02.txt
	Pages		: 12
	Date		: 02-Mar-01
	
This document specifies extensions to the IS-IS routing protocol in
support of Generalized Multi-Protocol Label Switching (previously
known as Multi-Protocol Lambda Switching).

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

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

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


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

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

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

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

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

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

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

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

--OtherAccess--

--NextPart--


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


From isis-wg-admin@spider.juniper.net  Wed Mar  7 09:03:41 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA04559
	for <isis-archive@odin.ietf.org>; Wed, 7 Mar 2001 09:03: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 GAA83291;
	Wed, 7 Mar 2001 06:35:04 -0800 (PST)
Received: from cisco.com (jaws.cisco.com [198.135.0.150])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA83276
	for <isis-wg@spider.juniper.net>; Wed, 7 Mar 2001 06:34:25 -0800 (PST)
Received: from mshand-w2k.cisco.com (uxb-dhcp-198-135-1-182.cisco.com [198.135.1.182])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id NAA27184
	for <isis-wg@external.juniper.net>; Wed, 7 Mar 2001 13:59:04 GMT
Message-Id: <4.3.2.7.2.20010307134635.02e78008@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: isis-wg@spider.juniper.net
From: mike shand <mshand@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [Isis-wg] IS-IS restart
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 07 Mar 2001 13:58:14 +0000

I've written up some thoughts about doing IS-IS restart (analogous to 
OSPF). Basically the idea is that we add an "I'm restarting" option to the 
IIH, which then causes the neighbor to revive its adjacency by setting 
SRMflags and sending a CSNP WITHOUT bouncing the adjacency. We make this 
reliable, so we are sure we will get database synchronization, and by 
looking at the CSNP we can check when we think it has been achieved, and 
hence run SPF for the first time.

Here it is rather more formally in draft format.

Comments?

	Mike

Network Working Group                                          M. Shand
Internet Draft                                            Cisco Systems
Expiration Date: August 2001
                                                           February 2001






                        Restart signaling for ISIS
                     draft-shand-ISIS-restart-00.txt


Status of this Memo


    This document is an Internet-Draft and is in full conformance with
    all provisions of Section 10 of RFC2026 [1].

    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.

1. Abstract

    The IS-IS routing protocol (RFC 1142 [2], ISO/IEC 10589 [3]) is a
    link state intra-domain routing protocol. Normally, when an IS-IS
    router is re-started, the neighboring routers detect the restart
    event and cycle their adjacencies with the restarting router through
    the down state. This is necessary in order to invoke the protocol
    mechanisms to ensure correct re-synchronization of the LSP database.
    However, the cycling of the adjacency state causes the neighbors to
    regenerate their LSPs describing the adjacency concerned. This in
    turn causes temporary disruption of routes passing through the
    restarting router.

    In certain scenarios such temporary disruption of the routes is
    highly undesirable.

    This draft describes a mechanism for a restarting router to signal
    that it is restarting to its neighbors, and allow them to re-

Shand                      Expires Aug 2001                   [Page 1]
  
INTERNET DRAFT              IS-IS restart                    Feb 2001


    establish their adjacencies without cycling through the down state,
    while still correctly initiating database synchronization.

    When such a router is restarted, it is highly desirable that it does
    not re-compute its own routes until it has achieved database
    synchronization with its neighbors. Re-computing its routes before
    synchronization is achieved will result in its own routes being
    temporarily incorrect.

    This draft additionally describes a mechanism for a restarting
    router to determine when it has achieved synchronization with its
    neighbors.

2. Conventions used in this document

    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
    "SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in
    this document are to be interpreted as described in RFC-2119 [4].

3. Overview

    There are two related problems with the existing specification of
    IS-IS with regard to re-synchronization of LSP databases when a
    router is re-started.

    Firstly, when a routing process restarts, and an adjacency to a
    neighboring router is re-initialized the neighboring routing process
    does three things

      1. It re-initializes the adjacency and causes its own LSP(s) to be
         regenerated, thus triggering SPF runs throughout the domain.

      2. It sets SRMflags on its own LSP database on the adjacency
         concerned.

      3. In the case of a Point-to-Point link it transmits a (set of)
         CSNP(s) over the adjacency.

    In the case of a restarting router process, the first of these is
    highly undesirable, but the second is essential in order to ensure
    re-synchronization of the LSP database.

    Secondly, whether or not the router is being re-started, it is
    desirable to be able to determine when the LSP databases of the
    neighboring routers have been synchronized (so that the overload bit
    can be cleared in the router's own LSP, for example). This document
    describes modifications to achieve this.

    It is assumed that the three-way handshake [5] is being used on
    Point-to-Point circuits.



Shand                      Expires Aug 2001                   [Page 2]
  
INTERNET DRAFT              IS-IS restart                    Feb 2001


4. Approach

4.1 Adjacency re-acquisition

    Adjacency re-acquisition is the first step in re-initialization. The
    restarting router explicitly notifies its neighbor that the
    adjacency is being re-acquired, and hence that it should not re-
    initialize the adjacency. This is achieved by the inclusion of a new
    "re-start" option (TLV) in the IIH PDU. The presence of this TLV
    indicates that the sender supports the new restart capability and it
    carries flags that are used to convey information during a restart.
    All IIHs transmitted by a router that supports this capability MUST
    include this TLV.

      Type [TBD]
      Length 1
      Value (1 octet)
          Bit 1 - Restart Request (RR)
          Bit 2 - Restart Acknowledgment (RA)
          Bits 3-8 - Reserved

    On receipt of an IIH with the "re-start" TLV having the RR bit set,
    if there exists on this interface an adjacency in state "Up" with
    the same System ID, and in the case of a LAN circuit, with the same
    source LAN address, then, irrespective of the other contents of the
    "Intermediate System Neighbors" option (LAN circuits), or the
    "Point-to-Point Adjacency State" option (Point-to-Point circuits):-

    a) Refresh the timer on the adjacency and leave the adjacency in
      state "Up",

    b) immediately (i.e. without waiting for any currently running timer
      interval to expire, but with a small random delay of a few 10s of
      milliseconds on LANs to avoid "storms"), transmit over the
      corresponding interface an IIH including the "re-start" TLV with
      the RR bit clear and the RA bit set, having updated the "Point-to-
      Point Adjacency State" option to reflect any new values received
      from the re-starting router. (This allows the restarting router to
      quickly acquire the correct information to place in its hellos.),

    c) if the corresponding interface is a Point-to-Point interface, or

       i)   if the receiving router is the LAN level n designated router
         (where n is the level of the IIH), or

       ii)  if the transmitting router is currently (according to the
         receiving router) the LAN level n designated router (where n is
         the level of the IIH) and the receiving router would be elected
         the LAN level n designated router if the transmitting router
         were ignored (note the actual DR is NOT changed by this
         process),


Shand                      Expires Aug 2001                   [Page 3]
  
INTERNET DRAFT              IS-IS restart                    Feb 2001


       initiate the transmission over the corresponding interface of a
       complete set of CSNPs, and set SRMflags on the corresponding
       interface for all LSPs in the local LSP database.

    Otherwise (i.e. if there was no adjacency to the system ID in
    question), process the IIH as normal by re-initializing the
    adjacency, and setting the RA bit in the returned IIH.

    A router that does not support the re-start capability will ignore
    the "re-start" TLV and re-initialize the adjacency as normal,
    returning an IIH without the "re-start" TLV.

    On starting, a router starts a timer T1 and transmits an IIH
    containing the "re-start" TLV with the RR bit set.

       1. On a LAN circuit the IIH contains an empty "Intermediate
          Systems Neighbors" TLV.

       2. On a Point-to-Point circuit the IIH contains a "Point-to-Point
          Adjacency State" option with state "Initializing", and with
          empty "Neighbor System ID" and "Neighbor Extended Local
          Circuit ID" options. The values of the "LocalCircuitID" and
          the "Extended Local CircuitID" may, but need not be, the same
          as those used previously for this circuit.

    Transmission of "normal" IIHs is inhibited until the conditions
    described below are met (in order to avoid causing an unnecessary
    adjacency re-initialization). On expiry of the timer T1, it is
    restarted and the IIH is retransmitted as above.

    On receipt of an IIH by the restarting router, a local adjacency is
    established as usual, and if the IIH contains a "re-start" TLV with
    the RA bit set, the receipt of the acknowledgement over that
    interface is noted.

    Receipt of an IIH not containing the "re-start" option is also
    treated as an acknowledgement, since it indicates that the neighbor
    is not re-start capable. In this case the neighbor will have re-
    initialized the adjacency as normal, which in the case of a Point-
    to-Point link will guarantee that SRMflags have been set on its
    database. In the case of LAN interface, the usual operation of the
    update process will ensure that synchronization is eventually
    achieved.

    In the case of a Point-to-Point circuit, the "LocalCircuitID" and
    "Extended Local Circuit ID" information contained in the IIH can be
    used immediately to generate an IIH containing the correct 3-way
    handshake information. The presence of "Neighbor System ID" or
    "Neighbor Extended Local Circuit ID" information which does not
    match the values currently in use by the local system is ignored
    (since the IIH may have been transmitted before the neighbor had
    received the new values from the re-starting router), but the

Shand                      Expires Aug 2001                   [Page 4]
  
INTERNET DRAFT              IS-IS restart                    Feb 2001


    adjacency remains in the initializing state until the correct
    information is received.

    In the case of a LAN circuit the information in the Intermediate
    Systems Neighbors option is recorded and used for the generation of
    subsequent IIHs as normal.

    When BOTH a complete set of CSNP(s) and an acknowledgement have been
    received over the interface, the timer T1 is cancelled.

    Once T1 has been cancelled, subsequent IIHs are transmitted
    according to the normal algorithms, but including the "re-start" TLV
    with both RR and RA clear.

    If a LAN contains a mixture of systems, only some of which support
    the new algorithm, database synchronization is still guaranteed, but
    the "old" systems will have re-initialized their adjacencies.

    If an interface is active, but does not have any neighboring router
    reachable over that interface the timer T1 would never be cancelled,
    and according to clause 4.2.1.2 the SPF would never be run.
    Therefore timer T1 is cancelled after some pre-determined
    expirations. (By this time any existing adjacency on a remote system
    would probably have expired anyway.)

4.1.1 State Table

    The above operations can be summarized by the following state table.

























Shand                      Expires Aug 2001                   [Page 5]
  
INTERNET DRAFT              IS-IS restart                    Feb 2001


       Event     | Running    | Restarting | Seen RA    | Seen CSNP
    ==================================================================
       RX RR     | Set SRM    | Set SRM    | Set SRM    | Set SRM
                 | Send RA    | Send RA    | Send RA    | Send RA
                 | Send CSNP  | Send CSNP  | Send CSNP  | Send CSNP
    -------------+------------+------------+------------+-------------
       RX RA     |            | Goto Seen  |            | Cancel T1
                 |            |  RA        |            | Goto Running
    -------------+------------+------------+------------+-------------
       RX CSNP   |            | Goto Seen  | Cancel T1  |
                 |            |  CSNP      | Goto       |
                 |            |            |  Running   |
    -------------+------------+------------+------------+-------------
       RX IIH    |            | Cancel T1  | Cancel T1  | Cancel T1
       with no   |            | Goto       | Goto       | Goto
       Reset TLV |            |  Running   |  Running   |  Running
    -------------+------------+------------+------------+-------------
       T1        |            | Send RR    | Send RR    | Send RR
       Expires   |            | Send CSNP  | Send CSNP  | Send CSNP
                 |            | Start T1   | Start T1   | Start T1
    -------------+------------+------------+------------+-------------
       T1        |            | Cancel T1  | Cancel T1  | Cancel T1
       Expires   |            | Goto       | Goto       | Goto
       n times   |            |  Running   |  Running   |  Running
    -------------+------------+------------+------------+-------------
       Router    | Set SRM    | Set SRM    | Set SRM    | Set SRM
       Restarted | Send RR    | Send RR    | Send RR    | Send RR
                 | Send CSNP  | Send CSNP  | Send CSNP  | Send CSNP
                 | Start T1   | Start T1   | Start T1   | Start T1
                 | Goto       | Goto       | Goto       | Goto
                 | Restarting | Restarting | Restarting | Restarting
    ==================================================================

4.2 Database synchronization

    When a router is started or re-started it can expect to receive a
    (set of) CSNP(s) over each interface. The arrival of the CSNP(s) is
    now guaranteed, since the "re-start" IIH with the RR bit set will be
    retransmitted until the CSNP(s) are correctly received.

    The CSNPs describe the set of LSPs that are currently held by each
    neighbor. Synchronization will be complete when all these LSPs have
    been received.

    On starting, a router starts a timer T2 for each active level. In
    addition to normal processing of the CSNPs, the set of LSPIDs
    contained in the first complete set of CSNP(s) received over each
    interface is recorded. If there are multiple interfaces on the
    restarting router, the recorded set of LSPIDs is the union of those
    received over each interface. LSPs with a remaining lifetime of zero
    are NOT so recorded.


Shand                      Expires Aug 2001                   [Page 6]
  
INTERNET DRAFT              IS-IS restart                    Feb 2001


    As LSPs are received (by the normal operation of the update process)
    over any interface, the corresponding LSPID entry is removed (it is
    also removed if the LSP had arrived before the CSNP containing the
    reference). When the list of LSPIDs becomes empty, the timer T2 is
    cancelled.

    At this point the local database is guaranteed to contain all the
    LSP(s) (either the same sequence number, or a more recent sequence
    number) which were present in the neighbors' databases at the time
    of re-starting. LSPs that arrived in a neighbor's database after the
    time of re-starting may, or may not, be present, but the normal
    operation of the update process will guarantee that they will
    eventually be received. At this point the local database is deemed
    to be "synchronized".

    Since LSPs mentioned in the CSNP(s) with a zero remaining lifetime
    are not recorded, it is unlikely that cancellation of the timer T2
    will be prevented by waiting for an LSP which will never arrive.
    However it is possible that an LSP with a small remaining lifetime
    was placed in the list. If the re-synchronization process takes
    longer than 'ZeroAgeLifetime' (default 60 seconds), the
    corresponding LSP will have been removed from the neighbors' LSP
    databases and will never arrive. Under these circumstances, the
    timer T2 may expire, and the databases are deemed to be
    synchronized.

4.2.1 LSP generation and flooding and SPF computation

    The operation of a router starting, as opposed to re-starting is
    somewhat different. These two cases are dealt with separately below.

4.2.1.1. Starting for the first time

    In the case of a starting router, the router's own zeroth LSP is
    first transmitted with the overload bit set. This prevents other
    routers from computing routes through the router until it has
    reliably acquired the complete set of LSPs. The overload bit remains
    set in subsequent transmissions of the zeroth LSP (such as will
    occur if a previous copy of the routers LSP is still present in the
    network) while the timer T2 is running.

    When the timer T2 expires, or is cancelled, the own LSP is
    regenerated with the overload bit clear (assuming the router isn't
    in fact overloaded), and flooded as normal.

    Other 'own' LSPs (including pseudonodes) are generated and flooded
    as normal, irrespective of the timer T2. The SPF is also run as
    normal and the RIB and FIB updated as routes become available.





Shand                      Expires Aug 2001                   [Page 7]
  
INTERNET DRAFT              IS-IS restart                    Feb 2001


4.2.1.2. Re-starting

    In order to avoid causing unnecessary routing churn in other
    routers, it is highly desirable that the own LSPs generated by the
    restarting system are the same as those previously present in the
    network (assuming no other changes have taken place). It is
    important therefore not to regenerate and flood the LSPs until all
    the adjacencies have been re-established and any information
    required for propagation into the local LSPs is fully available.
    Ideally, the information should be loaded into the LSPs in a
    deterministic way, such that the same information occurs in the same
    place in the same LSP (and hence the LSPs are identical to their
    previous versions). If this can be achieved, the new versions will
    not even cause SPF to be run in other systems. However, provided the
    same information is included in the set of LSPs (albeit in a
    different order, and possibly different LSPs), the result of running
    the SPF will be the same and will not cause churn to the forwarding
    tables.

    In the case of a re-starting router, none of the router's own non-
    pseudonode LSPs are transmitted, nor is the SPF run to update the
    forwarding tables while the timer T2 is running, or while the timer
    T1 is still running on any of the interfaces.

    Redistribution of inter-level information must be regenerated before
    this router's LSP is flooded to other nodes. Therefore the level-n
    non-pseudonode LSP(s) should not be flooded until the other level's
    T2 timer has expired and its SPF has been run. This ensures that any
    inter-level information that should be propagated can be included in
    the level-n LSP(s).

    During this period, if one of the router's own (including
    pseudonodes) LSPs is received, which the local router does not
    currently have in its own database, it is NOT purged. Under normal
    operation, such an LSP would be purged, since the LSP clearly should
    not be present in the global LSP database. However, in the present
    circumstances, this would be highly undesirable, because it could
    cause premature removal of an own LSP -- and hence churn in remote
    routers. Even if the local system has one or more own LSPs (which is
    has generated, but not yet transmitted) it is still not valid to
    compare the received LSP against this set, since it may be that as a
    result of propagation between level 1 and level 2 (or vice versa) a
    further own LSP will need to be generated when the LSP databases
    have synchronized.

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

    Once the other level's SPF has run and any inter-level propagation
    has been resolved, the 'own' LSPs can be generated and flooded. Any
    'own' LSPs which were previously ignored, but which are not part of
    the current set of 'own' LSPs (including pseudonodes) should then be

Shand                      Expires Aug 2001                   [Page 8]
  
INTERNET DRAFT              IS-IS restart                    Feb 2001


    purged. Note that it is possible that a Designated Router change may
    have taken place, and consequently the router should purge those
    pseudonode LSPs which it previously owned, but which are now no
    longer part of its set of pseudonode LSPs.

5. Security Considerations

    This memo does not create any new security issues for the IS-IS
    protocol. Security considerations for the base IS-IS protocol are
    covered in [2] and [3].

6. References


    1  Bradner, S., "The Internet Standards Process -- Revision 3", BCP
       9, RFC 2026, October 1996.

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

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

    4  Bradner, S., "Key words for use in RFCs to Indicate Requirement
       Levels", BCP 14, RFC 2119, March 1997

    5  Katz, D., "Three-Way Handshake for IS-IS Point-to-Point
       Adjacencies", draft-ietf-isis-3way-03.txt, July 2000

7. Acknowledgments

    The author would like to acknowledge contributions made by Radia
    Perlman, Mark Schaefer, Russ White and Rena Yang.

8. Author's Addresses

    Mike Shand
    Cisco Systems
    4, The Square,
    Stockley Park,
    UXBRIDGE,
    Middlesex
    UB11 1BN, UK

    Phone: +44 20 8756 8690
    Email: mshand@cisco.com





Shand                      Expires Aug 2001                   [Page 9]
  

_______________________________________________
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 Mar  7 14:38:13 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA19417
	for <isis-archive@odin.ietf.org>; Wed, 7 Mar 2001 14:38: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 MAA84658;
	Wed, 7 Mar 2001 12:10:03 -0800 (PST)
Received: from mx4.tellabs.com (mx4.tellabs.com [204.68.180.54])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA84643
	for <isis-wg@spider.juniper.net>; Wed, 7 Mar 2001 12:09:52 -0800 (PST)
Received: from mail.hq.tellabs.com (mail.bb.tellabs.com [138.111.51.100])
	by mx4.tellabs.com (Mirapoint)
	with ESMTP id AAF61330;
	Wed, 7 Mar 2001 13:24:03 -0600 (CST)
Received: from tellabs.com (dhcp-163-199.bb.tellabs.com [138.111.163.199])
	by mail.hq.tellabs.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id NAA10634
	for <isis-wg@spider.juniper.net>; Wed, 7 Mar 2001 13:22:58 -0600 (CST)
Message-ID: <3AA68A89.8A456A1C@tellabs.com>
From: Jonathan Sadler <Jonathan.Sadler@tellabs.com>
Reply-To: Jonathan.Sadler@tellabs.com
Organization: Tellabs ONG SE Platform
X-Mailer: Mozilla 4.75 [en] (WinNT; U)
X-Accept-Language: en,pdf
MIME-Version: 1.0
To: isis-wg@spider.juniper.net
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] WG time slot in Minneapolis?
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 07 Mar 2001 13:22:49 -0600
Content-Transfer-Encoding: 7bit

Has a request for a timeslot been made for IS-IS?  I don't see it on the
current draft agenda...

Jonathan Sadler
_______________________________________________
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 Mar  7 15:52:55 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA22274
	for <isis-archive@odin.ietf.org>; Wed, 7 Mar 2001 15:52:54 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA85047;
	Wed, 7 Mar 2001 13:25:03 -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 NAA85032
	for <isis-wg@spider.juniper.net>; Wed, 7 Mar 2001 13:24:53 -0800 (PST)
Received: from redback.com (prz-laptop.redback.com [155.53.36.102])
	by prattle.redback.com (Postfix) with ESMTP
	id CC90EB76788; Wed,  7 Mar 2001 12:49:32 -0800 (PST)
Message-ID: <3AA68E64.5D548E57@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: Jonathan.Sadler@tellabs.com
Cc: isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] WG time slot in Minneapolis?
References: <3AA68A89.8A456A1C@tellabs.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 07 Mar 2001 11:39:16 -0800
Content-Transfer-Encoding: 7bit

Jonathan Sadler wrote:

> Has a request for a timeslot been made for IS-IS?  I don't see it on the
> current draft agenda...

and accordingly, there is no workgroup meeting there ...

    -- 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  Fri Mar  9 06:03:19 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA10797
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 06:03: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 DAA93973;
	Fri, 9 Mar 2001 03:35:04 -0800 (PST)
Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA93958
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 03:34:47 -0800 (PST)
Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80])
        by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id LAA07136;
        Fri, 9 Mar 2001 11:54:20 +0100
Received: from medine.ms.alcatel.fr (medine.ms.alcatel.fr [193.105.117.1])
        by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id LAA13077;
        Fri, 9 Mar 2001 11:53:40 +0100 (MET)
Received: from ms.ms.alcatel.fr (ms.ms.alcatel.fr [188.9.12.93])
	by medine.ms.alcatel.fr (8.8.8/8.8.8/aar-1.2) with ESMTP id LAA27580;
	Fri, 9 Mar 2001 11:58:47 +0100 (MET)
Received: from reaumur.dinsunnet (reaumur [188.9.33.51])
	by ms.ms.alcatel.fr (8.8.7/8.8.7/aar-1.0) with SMTP id LAA21015;
	Fri, 9 Mar 2001 11:58:52 +0100 (MET)
Received: from ms.alcatel.fr by reaumur.dinsunnet (SMI-8.6/SMI-SVR4)
	id LAA29418; Fri, 9 Mar 2001 11:54:40 +0100
Message-ID: <3AA8B670.801636DD@ms.alcatel.fr>
From: Bruno Mongazon <mongazon@ms.alcatel.fr>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mike shand <mshand@cisco.com>
CC: isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] IS-IS restart
References: <4.3.2.7.2.20010307134635.02e78008@jaws.cisco.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, 09 Mar 2001 11:54:40 +0100
Content-Transfer-Encoding: 7bit

mike shand wrote:
> 
> I've written up some thoughts about doing IS-IS restart (analogous to
> OSPF). Basically the idea is that we add an "I'm restarting" option to the
> IIH, which then causes the neighbor to revive its adjacency by setting
> SRMflags and sending a CSNP WITHOUT bouncing the adjacency. We make this
> reliable, so we are sure we will get database synchronization, and by
> looking at the CSNP we can check when we think it has been achieved, and
> hence run SPF for the first time.
> 
> Here it is rather more formally in draft format.
> 
> Comments?
> 
>         Mike
> 

Hi Mike,

Just to make my mind clear about your proposal, could you check my
preliminary wonders/questions below.

Point 1
-------

-Does restart signaling is to occur before restart or at restart?

-More clearly does a restarting router first announces it is going to
restart (while it is
 up and running) and then restarts?

-or does it restarts and then announces it has restarted? 


Point 2
-------

-Reading the draft, my answer for point 1 would be that restart
signaling occurs at
 restart. In such case, depending on the holding timer, neigbhors might
have already moved
 the restarting adjacency in down state before the restart signal has
been received, isn't
 it?

 If so, how do you handle such a case in your proposal?

 If so, how is your proposal compatible/incompatible with the draft(*)
which suggests to
 reduce hold times for faster convergence in isis when routers come up
and down?

 (*) see <draft-parker-short-isis-hold-times-00>


Thanks in advance.
Bruno.
_______________________________________________
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 Mar  9 06:26:36 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA10927
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 06:26: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 DAA94101;
	Fri, 9 Mar 2001 03:59:03 -0800 (PST)
Received: from cisco.com (jaws.cisco.com [198.135.0.150])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id DAA94089
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 03:58:03 -0800 (PST)
Received: from mshand-w2k.cisco.com (uxb-dhcp-198-135-1-182.cisco.com [198.135.1.182])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id LAA16558;
	Fri, 9 Mar 2001 11:22:29 GMT
Message-Id: <4.3.2.7.2.20010309110934.00b39b38@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Bruno Mongazon <mongazon@ms.alcatel.fr>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] IS-IS restart
Cc: isis-wg@spider.juniper.net
In-Reply-To: <3AA8B670.801636DD@ms.alcatel.fr>
References: <4.3.2.7.2.20010307134635.02e78008@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: Fri, 09 Mar 2001 11:22:33 +0000

At 11:54 09/03/2001 +0100, Bruno Mongazon wrote:
>mike shand wrote:
> >
> > I've written up some thoughts about doing IS-IS restart (analogous to
> > OSPF). Basically the idea is that we add an "I'm restarting" option to the
> > IIH, which then causes the neighbor to revive its adjacency by setting
> > SRMflags and sending a CSNP WITHOUT bouncing the adjacency. We make this
> > reliable, so we are sure we will get database synchronization, and by
> > looking at the CSNP we can check when we think it has been achieved, and
> > hence run SPF for the first time.
> >
> > Here it is rather more formally in draft format.
> >
> > Comments?
> >
> >         Mike
> >
>
>Hi Mike,
>
>Just to make my mind clear about your proposal, could you check my
>preliminary wonders/questions below.
>
>Point 1
>-------
>
>-Does restart signaling is to occur before restart or at restart?

after


>-More clearly does a restarting router first announces it is going to
>restart (while it is
>  up and running) and then restarts?

No its not like BGP "I'll be back"


>-or does it restarts and then announces it has restarted?

The latter

>
>
>
>Point 2
>-------
>
>-Reading the draft, my answer for point 1 would be that restart
>signaling occurs at
>  restart. In such case, depending on the holding timer, neigbhors might
>have already moved
>  the restarting adjacency in down state before the restart signal has
>been received, isn't
>  it?

Yes.


>  If so, how do you handle such a case in your proposal?

They come up as usual. i.e the adjacency is reinitialized completely, and 
of course a new LSP entry generated etc.


>  If so, how is your proposal compatible/incompatible with the draft(*)
>which suggests to
>  reduce hold times for faster convergence in isis when routers come up
>and down?

Clearly the re-starting router would have to come back before the neighbor 
declared the adjacency down (in the sense that it had re-generated its LSP 
describing it).

If the neighbor is detecting physical link failure, the physical link would 
not fail in the case of a re-starting router which was able to continue 
forwarding. So that would not be an issue.

If the LINK did fail, then the physical failure would cause the desired 
rapid detection.

We assume that failure of the "router" does NOT need to be detected 
quickly, since it does not disrupt forwarding.

         Mike




>  (*) see <draft-parker-short-isis-hold-times-00>
>
>
>Thanks in advance.
>Bruno.

_______________________________________________
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 Mar  9 06:54:02 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id GAA11120
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 06:54: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 EAA94321;
	Fri, 9 Mar 2001 04:26:04 -0800 (PST)
Received: from cisco.com (jaws.cisco.com [198.135.0.150])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id EAA94309
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 04:25:12 -0800 (PST)
Received: from mshand-w2k.cisco.com (uxb-dhcp-198-135-1-182.cisco.com [198.135.1.182])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id LAA19164;
	Fri, 9 Mar 2001 11:49:38 GMT
Message-Id: <4.3.2.7.2.20010309112952.03299948@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Bruno Mongazon <mongazon@ms.alcatel.fr>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] IS-IS restart
Cc: isis-wg@spider.juniper.net
In-Reply-To: <4.3.2.7.2.20010309110934.00b39b38@jaws.cisco.com>
References: <3AA8B670.801636DD@ms.alcatel.fr>
 <4.3.2.7.2.20010307134635.02e78008@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: Fri, 09 Mar 2001 11:49:43 +0000

Oh I've realized why you might be confused.

The restart TLV is always present in the IIH (for a router which supports 
re-starting).

But the "restart-request" bit is ONLY set when you actually re-start.


And of course, since you know whether or not you are yourself re-start 
capable, you can use suitable holding times for your own hellos.

         Mike

At 11:22 09/03/2001 +0000, mike shand wrote:
>At 11:54 09/03/2001 +0100, Bruno Mongazon wrote:
>>mike shand wrote:
>> >
>> > I've written up some thoughts about doing IS-IS restart (analogous to
>> > OSPF). Basically the idea is that we add an "I'm restarting" option to the
>> > IIH, which then causes the neighbor to revive its adjacency by setting
>> > SRMflags and sending a CSNP WITHOUT bouncing the adjacency. We make this
>> > reliable, so we are sure we will get database synchronization, and by
>> > looking at the CSNP we can check when we think it has been achieved, and
>> > hence run SPF for the first time.
>> >
>> > Here it is rather more formally in draft format.
>> >
>> > Comments?
>> >
>> >         Mike
>> >
>>
>>Hi Mike,
>>
>>Just to make my mind clear about your proposal, could you check my
>>preliminary wonders/questions below.
>>
>>Point 1
>>-------
>>
>>-Does restart signaling is to occur before restart or at restart?
>
>after
>
>
>>-More clearly does a restarting router first announces it is going to
>>restart (while it is
>>  up and running) and then restarts?
>
>No its not like BGP "I'll be back"
>
>
>>-or does it restarts and then announces it has restarted?
>
>The latter
>
>>
>>
>>
>>Point 2
>>-------
>>
>>-Reading the draft, my answer for point 1 would be that restart
>>signaling occurs at
>>  restart. In such case, depending on the holding timer, neigbhors might
>>have already moved
>>  the restarting adjacency in down state before the restart signal has
>>been received, isn't
>>  it?
>
>Yes.
>
>
>>  If so, how do you handle such a case in your proposal?
>
>They come up as usual. i.e the adjacency is reinitialized completely, and 
>of course a new LSP entry generated etc.
>
>
>>  If so, how is your proposal compatible/incompatible with the draft(*)
>>which suggests to
>>  reduce hold times for faster convergence in isis when routers come up
>>and down?
>
>Clearly the re-starting router would have to come back before the neighbor 
>declared the adjacency down (in the sense that it had re-generated its LSP 
>describing it).
>
>If the neighbor is detecting physical link failure, the physical link 
>would not fail in the case of a re-starting router which was able to 
>continue forwarding. So that would not be an issue.
>
>If the LINK did fail, then the physical failure would cause the desired 
>rapid detection.
>
>We assume that failure of the "router" does NOT need to be detected 
>quickly, since it does not disrupt forwarding.
>
>         Mike
>
>
>
>
>>  (*) see <draft-parker-short-isis-hold-times-00>
>>
>>
>>Thanks in advance.
>>Bruno.
>
>_______________________________________________
>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 Mar  9 09:31:01 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA14885
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 09:31: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 HAA94991;
	Fri, 9 Mar 2001 07:03:03 -0800 (PST)
Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA94979
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 07:02:42 -0800 (PST)
Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80])
        by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id PAA26818;
        Fri, 9 Mar 2001 15:22:15 +0100
Received: from medine.ms.alcatel.fr (medine.ms.alcatel.fr [193.105.117.1])
        by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id PAA17332;
        Fri, 9 Mar 2001 15:21:10 +0100 (MET)
Received: from ms.ms.alcatel.fr (ms.ms.alcatel.fr [188.9.12.93])
	by medine.ms.alcatel.fr (8.8.8/8.8.8/aar-1.2) with ESMTP id PAA07475;
	Fri, 9 Mar 2001 15:26:22 +0100 (MET)
Received: from reaumur.dinsunnet (reaumur [188.9.33.51])
	by ms.ms.alcatel.fr (8.8.7/8.8.7/aar-1.0) with SMTP id PAA10759;
	Fri, 9 Mar 2001 15:26:27 +0100 (MET)
Received: from ms.alcatel.fr by reaumur.dinsunnet (SMI-8.6/SMI-SVR4)
	id PAA00025; Fri, 9 Mar 2001 15:22:15 +0100
Message-ID: <3AA8E716.D0082056@ms.alcatel.fr>
From: Bruno Mongazon <mongazon@ms.alcatel.fr>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: mike shand <mshand@cisco.com>
CC: isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] IS-IS restart
References: <3AA8B670.801636DD@ms.alcatel.fr>
	 <4.3.2.7.2.20010307134635.02e78008@jaws.cisco.com> <4.3.2.7.2.20010309112952.03299948@jaws.cisco.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, 09 Mar 2001 15:22:14 +0100
Content-Transfer-Encoding: 7bit

mike shand wrote:
> 
> Oh I've realized why you might be confused.
> 
> The restart TLV is always present in the IIH (for a router which supports
> re-starting).
> 
> But the "restart-request" bit is ONLY set when you actually re-start.
> 
> And of course, since you know whether or not you are yourself re-start
> capable, you can use suitable holding times for your own hellos.
> 
>          Mike
>

Fine Mike,

Then i would like to suggest the following amendments to your proposal:

-Modify the proposed restart TLV to include a restart time. Might be
encoded on 1 byte in
 seconds or milliseconds.

-Interpret the restart time as follows (only if the restart capability
is supported):

 When a IIH PDU is received with a restart TLV having RR and RA bits
reset (means not
 restarting), then memorize, eventually override (*), the restart time
for the adjacency
 (in addition to the restart capability which i assumed to be memorized
in your current
 proposal). A zero restart time means no restart time.

 When the holding timer adjacency expires and the adjacency is
restartable and the
 restart timer is non-zero, then wait for restart time
seconds/milliseconds before
 the adjacency is declared down and recycled.

 Stop the restart timer when an IIH PDU is received with a restart TLV
having RR bit set
 and RA bit not set (means restarting).

 When restart timer expires, re-initialize the adjacency (as implied by
the current
 proposal).

(*) The restart time might be changed while exchanging regular IIH PDU
(RR and RA not
    set.

With this suggestion, it is possible to express the restart time
independently of the holding time. Otherwise, as you said, you have to
choose a 'suitable' value for both holding time and restart time. The
choice might be difficult. If you need more time to restart, this will
also take more time to detect and propagate failure in routing. If you
want early detection aand fast convergence, then you will have less time
to restart and less chance for restart to operate. Separating the hold
and restart time could solve this issue.

Let me know your opinion about this proposal.

Bruno.
 
 
> At 11:22 09/03/2001 +0000, mike shand wrote:
> >At 11:54 09/03/2001 +0100, Bruno Mongazon wrote:
> >>mike shand wrote:
> >> >
> >> > I've written up some thoughts about doing IS-IS restart (analogous to
> >> > OSPF). Basically the idea is that we add an "I'm restarting" option to the
> >> > IIH, which then causes the neighbor to revive its adjacency by setting
> >> > SRMflags and sending a CSNP WITHOUT bouncing the adjacency. We make this
> >> > reliable, so we are sure we will get database synchronization, and by
> >> > looking at the CSNP we can check when we think it has been achieved, and
> >> > hence run SPF for the first time.
> >> >
> >> > Here it is rather more formally in draft format.
> >> >
> >> > Comments?
> >> >
> >> >         Mike
> >> >
> >>
> >>Hi Mike,
> >>
> >>Just to make my mind clear about your proposal, could you check my
> >>preliminary wonders/questions below.
> >>
> >>Point 1
> >>-------
> >>
> >>-Does restart signaling is to occur before restart or at restart?
> >
> >after
> >
> >
> >>-More clearly does a restarting router first announces it is going to
> >>restart (while it is
> >>  up and running) and then restarts?
> >
> >No its not like BGP "I'll be back"
> >
> >
> >>-or does it restarts and then announces it has restarted?
> >
> >The latter
> >
> >>
> >>
> >>
> >>Point 2
> >>-------
> >>
> >>-Reading the draft, my answer for point 1 would be that restart
> >>signaling occurs at
> >>  restart. In such case, depending on the holding timer, neigbhors might
> >>have already moved
> >>  the restarting adjacency in down state before the restart signal has
> >>been received, isn't
> >>  it?
> >
> >Yes.
> >
> >
> >>  If so, how do you handle such a case in your proposal?
> >
> >They come up as usual. i.e the adjacency is reinitialized completely, and
> >of course a new LSP entry generated etc.
> >
> >
> >>  If so, how is your proposal compatible/incompatible with the draft(*)
> >>which suggests to
> >>  reduce hold times for faster convergence in isis when routers come up
> >>and down?
> >
> >Clearly the re-starting router would have to come back before the neighbor
> >declared the adjacency down (in the sense that it had re-generated its LSP
> >describing it).
> >
> >If the neighbor is detecting physical link failure, the physical link
> >would not fail in the case of a re-starting router which was able to
> >continue forwarding. So that would not be an issue.
> >
> >If the LINK did fail, then the physical failure would cause the desired
> >rapid detection.
> >
> >We assume that failure of the "router" does NOT need to be detected
> >quickly, since it does not disrupt forwarding.
> >
> >         Mike
> >
> >
> >
> >
> >>  (*) see <draft-parker-short-isis-hold-times-00>
> >>
> >>
> >>Thanks in advance.
> >>Bruno.
> >
> >_______________________________________________
> >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 Mar  9 09:56:47 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id JAA15719
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 09:56:47 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA95153;
	Fri, 9 Mar 2001 07:29:04 -0800 (PST)
Received: from cisco.com (jaws.cisco.com [198.135.0.150])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA95141
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 07:28:44 -0800 (PST)
Received: from mshand-w2k.cisco.com (uxb-dhcp-198-135-1-182.cisco.com [198.135.1.182])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id OAA05467;
	Fri, 9 Mar 2001 14:53:09 GMT
Message-Id: <4.3.2.7.2.20010309144809.032f6718@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Bruno Mongazon <mongazon@ms.alcatel.fr>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] IS-IS restart
Cc: isis-wg@spider.juniper.net
In-Reply-To: <3AA8E716.D0082056@ms.alcatel.fr>
References: <3AA8B670.801636DD@ms.alcatel.fr>
 <4.3.2.7.2.20010307134635.02e78008@jaws.cisco.com>
 <4.3.2.7.2.20010309112952.03299948@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: Fri, 09 Mar 2001 14:53:01 +0000

I'm afraid I don't see the point of your suggestion.

If you are restartable you simply set your holding time to include the time 
it takes you to re-start.

This means that the neighbor will keep its adjacency up for this time (and 
more importantly keep sending you data).

Since you are re-startable you will continue to forward that data more or 
less correctly (but no less correctly than normal propagation delays would 
cause).

Even if your neighbor DOESN't support restart this is OK, since it will 
simply re-initialize its adjacency when you come back up. You will cause a 
netowrk disturbance, but again this is no worse than you would have had 
without re-startability.

Provided you use physical detection of link failure (and why would you 
not?), then you have lost nothing.


         Mike

At 15:22 09/03/2001 +0100, Bruno Mongazon wrote:
>mike shand wrote:
> >
> > Oh I've realized why you might be confused.
> >
> > The restart TLV is always present in the IIH (for a router which supports
> > re-starting).
> >
> > But the "restart-request" bit is ONLY set when you actually re-start.
> >
> > And of course, since you know whether or not you are yourself re-start
> > capable, you can use suitable holding times for your own hellos.
> >
> >          Mike
> >
>
>Fine Mike,
>
>Then i would like to suggest the following amendments to your proposal:
>
>-Modify the proposed restart TLV to include a restart time. Might be
>encoded on 1 byte in
>  seconds or milliseconds.
>
>-Interpret the restart time as follows (only if the restart capability
>is supported):
>
>  When a IIH PDU is received with a restart TLV having RR and RA bits
>reset (means not
>  restarting), then memorize, eventually override (*), the restart time
>for the adjacency
>  (in addition to the restart capability which i assumed to be memorized
>in your current
>  proposal). A zero restart time means no restart time.
>
>  When the holding timer adjacency expires and the adjacency is
>restartable and the
>  restart timer is non-zero, then wait for restart time
>seconds/milliseconds before
>  the adjacency is declared down and recycled.
>
>  Stop the restart timer when an IIH PDU is received with a restart TLV
>having RR bit set
>  and RA bit not set (means restarting).
>
>  When restart timer expires, re-initialize the adjacency (as implied by
>the current
>  proposal).
>
>(*) The restart time might be changed while exchanging regular IIH PDU
>(RR and RA not
>     set.
>
>With this suggestion, it is possible to express the restart time
>independently of the holding time. Otherwise, as you said, you have to
>choose a 'suitable' value for both holding time and restart time. The
>choice might be difficult. If you need more time to restart, this will
>also take more time to detect and propagate failure in routing. If you
>want early detection aand fast convergence, then you will have less time
>to restart and less chance for restart to operate. Separating the hold
>and restart time could solve this issue.
>
>Let me know your opinion about this proposal.
>
>Bruno.
>
>
> > At 11:22 09/03/2001 +0000, mike shand wrote:
> > >At 11:54 09/03/2001 +0100, Bruno Mongazon wrote:
> > >>mike shand wrote:
> > >> >
> > >> > I've written up some thoughts about doing IS-IS restart (analogous to
> > >> > OSPF). Basically the idea is that we add an "I'm restarting" 
> option to the
> > >> > IIH, which then causes the neighbor to revive its adjacency by setting
> > >> > SRMflags and sending a CSNP WITHOUT bouncing the adjacency. We 
> make this
> > >> > reliable, so we are sure we will get database synchronization, and by
> > >> > looking at the CSNP we can check when we think it has been 
> achieved, and
> > >> > hence run SPF for the first time.
> > >> >
> > >> > Here it is rather more formally in draft format.
> > >> >
> > >> > Comments?
> > >> >
> > >> >         Mike
> > >> >
> > >>
> > >>Hi Mike,
> > >>
> > >>Just to make my mind clear about your proposal, could you check my
> > >>preliminary wonders/questions below.
> > >>
> > >>Point 1
> > >>-------
> > >>
> > >>-Does restart signaling is to occur before restart or at restart?
> > >
> > >after
> > >
> > >
> > >>-More clearly does a restarting router first announces it is going to
> > >>restart (while it is
> > >>  up and running) and then restarts?
> > >
> > >No its not like BGP "I'll be back"
> > >
> > >
> > >>-or does it restarts and then announces it has restarted?
> > >
> > >The latter
> > >
> > >>
> > >>
> > >>
> > >>Point 2
> > >>-------
> > >>
> > >>-Reading the draft, my answer for point 1 would be that restart
> > >>signaling occurs at
> > >>  restart. In such case, depending on the holding timer, neigbhors might
> > >>have already moved
> > >>  the restarting adjacency in down state before the restart signal has
> > >>been received, isn't
> > >>  it?
> > >
> > >Yes.
> > >
> > >
> > >>  If so, how do you handle such a case in your proposal?
> > >
> > >They come up as usual. i.e the adjacency is reinitialized completely, and
> > >of course a new LSP entry generated etc.
> > >
> > >
> > >>  If so, how is your proposal compatible/incompatible with the draft(*)
> > >>which suggests to
> > >>  reduce hold times for faster convergence in isis when routers come up
> > >>and down?
> > >
> > >Clearly the re-starting router would have to come back before the neighbor
> > >declared the adjacency down (in the sense that it had re-generated its LSP
> > >describing it).
> > >
> > >If the neighbor is detecting physical link failure, the physical link
> > >would not fail in the case of a re-starting router which was able to
> > >continue forwarding. So that would not be an issue.
> > >
> > >If the LINK did fail, then the physical failure would cause the desired
> > >rapid detection.
> > >
> > >We assume that failure of the "router" does NOT need to be detected
> > >quickly, since it does not disrupt forwarding.
> > >
> > >         Mike
> > >
> > >
> > >
> > >
> > >>  (*) see <draft-parker-short-isis-hold-times-00>
> > >>
> > >>
> > >>Thanks in advance.
> > >>Bruno.
> > >
> > >_______________________________________________
> > >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  Fri Mar  9 10:36:22 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA17844
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 10:36: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 IAA95378;
	Fri, 9 Mar 2001 08:07:03 -0800 (PST)
Received: from bridge.axiowave.com (mail.axiowave.com [209.6.34.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id IAA95366
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 08:06:02 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734296AE703@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Bruno Mongazon'" <mongazon@ms.alcatel.fr>,
        mike shand
	 <mshand@cisco.com>
Cc: isis-wg@spider.juniper.net
Subject: RE: [Isis-wg] IS-IS restart
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 10:30:21 -0500

 
> -Modify the proposed restart TLV to include a restart time. ...
>  
>  When the holding timer adjacency expires and the adjacency is
>  restartable and the restart timer is non-zero, then wait for 
>  restart time seconds/milliseconds before the adjacency is 
>  declared down and recycled.

Doesn't this make it take longer to detect a bad link via
hellos?   I think Mike's proposal allows the padding you
need by making the Hello Hold Time longer than the time
required to reboot and restart sending hellos on configured
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  Fri Mar  9 12:05:13 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA22876
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 12:05:11 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA95793;
	Fri, 9 Mar 2001 09:37:07 -0800 (PST)
Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA95781
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 09:36:43 -0800 (PST)
Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80])
        by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id RAA18062;
        Fri, 9 Mar 2001 17:56:11 +0100
Received: from medine.ms.alcatel.fr (medine.ms.alcatel.fr [193.105.117.1])
        by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id RAA18614;
        Fri, 9 Mar 2001 17:55:34 +0100 (MET)
Received: from ms.ms.alcatel.fr (ms.ms.alcatel.fr [188.9.12.93])
	by medine.ms.alcatel.fr (8.8.8/8.8.8/aar-1.2) with ESMTP id SAA15654;
	Fri, 9 Mar 2001 18:00:49 +0100 (MET)
Received: from reaumur.dinsunnet (reaumur [188.9.33.51])
	by ms.ms.alcatel.fr (8.8.7/8.8.7/aar-1.0) with SMTP id SAA02898;
	Fri, 9 Mar 2001 18:00:53 +0100 (MET)
Received: from ms.alcatel.fr by reaumur.dinsunnet (SMI-8.6/SMI-SVR4)
	id RAA01003; Fri, 9 Mar 2001 17:56:41 +0100
Message-ID: <3AA90B49.FD8B6883@ms.alcatel.fr>
From: Bruno Mongazon <mongazon@ms.alcatel.fr>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Jeff Parker <jparker@axiowave.com>
CC: mike shand <mshand@cisco.com>, isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] IS-IS restart
References: <EB5FFC72F183D411B3820006295734296AE703@r2d2.axiowave.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, 09 Mar 2001 17:56:41 +0100
Content-Transfer-Encoding: 7bit

Jeff Parker wrote:
> 
> 
> > -Modify the proposed restart TLV to include a restart time. ...
> >
> >  When the holding timer adjacency expires and the adjacency is
> >  restartable and the restart timer is non-zero, then wait for
> >  restart time seconds/milliseconds before the adjacency is
> >  declared down and recycled.
> 
> Doesn't this make it take longer to detect a bad link via
> hellos?   I think Mike's proposal allows the padding you
> need by making the Hello Hold Time longer than the time
> required to reboot and restart sending hellos on configured
> circuits.
>

Yes, i've got it:
The faster (lower) you detect bad links, the faster (lower) you restart!

Anyway the restart time will be hidden. It is a part of the holding
time.
If you want to make this part visible to the peer, my suggestion should
be ok?

Bruno.
  
> - jeff parker
> - axiowave 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  Fri Mar  9 12:18:59 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA23858
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 12:18: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 JAA95886;
	Fri, 9 Mar 2001 09:51:03 -0800 (PST)
Received: from ce-nfs-1.cisco.com (ce-nfs-1.cisco.com [171.68.202.251])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA95874
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 09:50:35 -0800 (PST)
Received: from AZININ-W2K.cisco.com (vjorge-dsl2.cisco.com [10.21.134.163])
	by ce-nfs-1.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id JAA20425;
	Fri, 9 Mar 2001 09:14:22 -0800 (PST)
From: Alex Zinin <azinin@cisco.com>
X-Mailer: The Bat! (v1.41) REG'D / CD5BF9353B3B7091
Reply-To: Alex Zinin <azinin@cisco.com>
Organization: Cisco Systems
X-Priority: 3 (Normal)
Message-ID: <14382.010309@cisco.com>
To: Bruno Mongazon <mongazon@ms.alcatel.fr>
CC: Jeff Parker <jparker@axiowave.com>, mike shand <mshand@cisco.com>,
        isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] IS-IS restart
In-reply-To: <3AA90B49.FD8B6883@ms.alcatel.fr>
References: <3AA90B49.FD8B6883@ms.alcatel.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 09:10:11 -0800
Content-Transfer-Encoding: 7bit


Bruno,

> Yes, i've got it:
> The faster (lower) you detect bad links, the faster (lower) you restart!

> Anyway the restart time will be hidden. It is a part of the holding
> time.
> If you want to make this part visible to the peer, my suggestion should
> be ok?

What value would it add to the mechanism?

Alex.


_______________________________________________
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 Mar  9 12:33:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA24784
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 12:33: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 KAA96006;
	Fri, 9 Mar 2001 10:06:04 -0800 (PST)
Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA95994
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 10:05:28 -0800 (PST)
Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80])
        by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id SAA27780;
        Fri, 9 Mar 2001 18:24:56 +0100
Received: from medine.ms.alcatel.fr (medine.ms.alcatel.fr [193.105.117.1])
        by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id SAA00265;
        Fri, 9 Mar 2001 18:24:19 +0100 (MET)
Received: from ms.ms.alcatel.fr (ms.ms.alcatel.fr [188.9.12.93])
	by medine.ms.alcatel.fr (8.8.8/8.8.8/aar-1.2) with ESMTP id SAA17000;
	Fri, 9 Mar 2001 18:29:34 +0100 (MET)
Received: from reaumur.dinsunnet (reaumur [188.9.33.51])
	by ms.ms.alcatel.fr (8.8.7/8.8.7/aar-1.0) with SMTP id SAA05285;
	Fri, 9 Mar 2001 18:29:38 +0100 (MET)
Received: from ms.alcatel.fr by reaumur.dinsunnet (SMI-8.6/SMI-SVR4)
	id SAA01019; Fri, 9 Mar 2001 18:25:25 +0100
Message-ID: <3AA91205.65DC418A@ms.alcatel.fr>
From: Bruno Mongazon <mongazon@ms.alcatel.fr>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Alex Zinin <azinin@cisco.com>
CC: Jeff Parker <jparker@axiowave.com>, mike shand <mshand@cisco.com>,
        isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] IS-IS restart
References: <3AA90B49.FD8B6883@ms.alcatel.fr> <14382.010309@cisco.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, 09 Mar 2001 18:25:25 +0100
Content-Transfer-Encoding: 7bit

Alex Zinin wrote:
> 
> Bruno,
> 
> > Yes, i've got it:
> > The faster (lower) you detect bad links, the faster (lower) you restart!
> 
> > Anyway the restart time will be hidden. It is a part of the holding
> > time.
> > If you want to make this part visible to the peer, my suggestion should
> > be ok?
> 
> What value would it add to the mechanism?
> 
> Alex.

Not a big value to the mechanism itself but a choice criterion from the
peer perspective:

The peer can choose to support or not restart for the adjacency
depending on the two values (holding time, restart time). If a router
says it can detect bad links fast but restarts slowly, then the peer
might choose high-speed detection without restart.

If everything is hidden in the hold timer, then the peer just ack/nack
according to its restart capability.

Bruno.
_______________________________________________
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 Mar  9 12:54:40 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA26278
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 12:54: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 KAA96138;
	Fri, 9 Mar 2001 10:27:03 -0800 (PST)
Received: from ce-nfs-1.cisco.com (ce-nfs-1.cisco.com [171.68.202.251])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA96121
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 10:26:03 -0800 (PST)
Received: from AZININ-W2K.cisco.com (vjorge-dsl2.cisco.com [10.21.134.163])
	by ce-nfs-1.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id JAA27542;
	Fri, 9 Mar 2001 09:49:50 -0800 (PST)
From: Alex Zinin <azinin@cisco.com>
X-Mailer: The Bat! (v1.41) REG'D / CD5BF9353B3B7091
Reply-To: Alex Zinin <azinin@cisco.com>
Organization: Cisco Systems
X-Priority: 3 (Normal)
Message-ID: <8406.010309@cisco.com>
To: Bruno Mongazon <mongazon@ms.alcatel.fr>
CC: Jeff Parker <jparker@axiowave.com>, mike shand <mshand@cisco.com>,
        isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] IS-IS restart
In-reply-To: <3AA91205.65DC418A@ms.alcatel.fr>
References: <3AA91205.65DC418A@ms.alcatel.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 09:45:38 -0800
Content-Transfer-Encoding: 7bit


Bruno,

 I see your point.

 However, I think such a choice would make it harder
 to predict that a graceful restart will actually happen
 when different implementations make difference choices.
 I would suggest we make it simple and go with the hold timer.

-- 
Alex Zinin

> Alex Zinin wrote:
>> 
>> Bruno,
>> 
>> > Yes, i've got it:
>> > The faster (lower) you detect bad links, the faster (lower) you restart!
>> 
>> > Anyway the restart time will be hidden. It is a part of the holding
>> > time.
>> > If you want to make this part visible to the peer, my suggestion should
>> > be ok?
>> 
>> What value would it add to the mechanism?
>> 
>> Alex.

> Not a big value to the mechanism itself but a choice criterion from the
> peer perspective:

> The peer can choose to support or not restart for the adjacency
> depending on the two values (holding time, restart time). If a router
> says it can detect bad links fast but restarts slowly, then the peer
> might choose high-speed detection without restart.

> If everything is hidden in the hold timer, then the peer just ack/nack
> according to its restart capability.

> Bruno.


_______________________________________________
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 Mar  9 13:39:05 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA28837
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 13:39: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 LAA96427;
	Fri, 9 Mar 2001 11:11:03 -0800 (PST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA96415
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 11:10:10 -0800 (PST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA09889;
	Fri, 9 Mar 2001 13:34:33 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id NAA18419;
	Fri, 9 Mar 2001 13:34:33 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <F301RZNS>; Fri, 9 Mar 2001 13:34:25 -0500
Message-ID: <39469E08BD83D411A3D900204840EC5519EB42@VIE-MSGUSR-01>
From: "Odak, John" <John.Odak@Marconi.com>
To: "'henk@procket.com'" <henk@procket.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: [Isis-wg] TE TLVs/Sub-TLVs
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 13:33:43 -0500

TE Authors,

Please forgive the lateness of these comments on the TE draft
(draft-ietf-isis-traffic-02.txt), but I only recently started looking at it
- and ISIS itself for that matter - and I have a few somewhat obvious
comments about the TLVs/sub-TLVs that you've specified. Again, please
forgive this post if these issues have already been discussed and resolved.

Specific comments:

- The Extended IP Reachability TLV (type 135) has a one-octet control
information field that uses 1 bit to indicate the existence of sub-TLVs.
This is not necessary because the enclosing TLV already has a length field
that will indicate whether sub-TLVs are present.

- The Extended IP Reachability TLV (type 135) has a one-octet control
information field that sets aside 6 bits for the IPv4 prefix length when
only 5 are required. One of the bits should be freed for possible future or
experimental use.

- The Extended IP Reachability TLV (type 135) potentially has a one-octet
field to indicate the total length of any sub TLVs. This is not necessary
because the enclosing TLV already has a length field that will indicate the
total length of any sub-TLVs.

- The Extended IS Reachability TLV (type 22) has a one-octet field to
indicate the total length of any sub TLVs. This is not necessary because the
enclosing TLV already has a length field that will indicate the total length
of any sub-TLVs.

General comments and issues:

- The Extended IS Reachability and  Extended IP Reachability TLVs are
inconsistent in the manner in which they specify the presence of sub-TLVs.
Since both definitions are from the same document, and in fact are only one
page apart, shouldn't they look a little more like each other?

- All of the sub-TLVs have been defined in terms of the Type-Length-Value
encoding format, but none has a variable length. This seems to be a real
waste of the relatively small 254 bytes of potential value space.

- Why are the sub-TLVs referred to as sub? Aren't they just TLVs? It looks
like there's still plenty of open space in the main Type range to
accommodate them, and many others for that matter. In a future enhancement,
will we have sub-sub-TLVs? It would seem that a more general and consistent
method for specifying, grouping, and encoding information might be called
for - ASN.1/BER comes to mind.

I realize that many vendors have already implemented this draft - my company
being one of them (I think they'll flog me for this posting), and that some
of the comments, while they will not add much functional value, will require
rework, and in the case of the general comments, possibly quite a lot of
rework. But since the document is still a draft and is introducing sub-TLVs,
it might be nice if it also established a framework that could be copied and
built upon instead of just something that can be made to work.

John Odak
john.odak@marconi.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 Mar  9 14:17:03 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA00627
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 14:17: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 LAA96626;
	Fri, 9 Mar 2001 11:49:04 -0800 (PST)
Received: from bridge.axiowave.com (mail.axiowave.com [209.6.34.2])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA96614
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 11:48:45 -0800 (PST)
Message-ID: <EB5FFC72F183D411B3820006295734296AE71D@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Odak, John'" <John.Odak@marconi.com>,
        "'henk@procket.com'"
	 <henk@procket.com>,
        "'isis-wg@external.juniper.net'"
	 <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] TE TLVs/Sub-TLVs
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 14:12:56 -0500

> - The Extended IS Reachability TLV (type 22) has a one-octet field to
> indicate the total length of any sub TLVs. This is not 
> necessary because the enclosing TLV already has a length 
> field that will indicate the total length of any sub-TLVs.

You might have multiple instances of this: you need the inner
length to split multiple items apart.  

> - All of the sub-TLVs have been defined in terms of the 
> Type-Length-Value encoding format, but none has a 
> variable length. This seems to be a real
> waste of the relatively small 254 bytes of potential value space.

The strength of the TLV  encoding is that you don't need to 
know anything about the T to decode it.  If you mix TLVs and 
TVs, then an older implementation has now way to deal with a 
newly defined TV.  Since it doesn't know the new Type, it 
doesn't know the fixed Length to skip.  

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


From isis-wg-admin@spider.juniper.net  Fri Mar  9 14:27:38 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA01054
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 14:27:37 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA96735;
	Fri, 9 Mar 2001 12:00:04 -0800 (PST)
Received: from yarilo.pluris.com (pluris.com [208.227.9.12])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA96717
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 11:59:16 -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 LAA05583;
	Fri, 9 Mar 2001 11:23:36 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <GD96LBLZ>; Fri, 9 Mar 2001 11:23:36 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA05A7C5@avalon.pluris.com>
From: Satish Dattatri <satish@pluris.com>
To: "'Odak, John'" <John.Odak@marconi.com>,
        "'henk@procket.com'"
	 <henk@procket.com>,
        "'isis-wg@external.juniper.net'"
	 <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] TE TLVs/Sub-TLVs
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 11:23:33 -0800

Hi,

By removing the 'L' in the sub-TLV it would cause headache for
implementations (other than cisco for now) not knowing a particular 
*reserved* sub-TLV's length. An implementation will now have to 
skip the rest of the data in TLV after hitting a unknown type.
This may not be desirable.

But by making the length of all sub-TLV types well-known and 
constant (no more *reserved* types), then the 'L' in the sub-TLVs 
can be removed and it becomes sub-TV ;-).
Multiple values now will be in multiple sub-TV's (for ex. IP V4 interface
addresses).

Satish

-----Original Message-----
From: Odak, John [mailto:John.Odak@marconi.com]
Sent: Friday, March 09, 2001 10:34 AM
To: 'henk@procket.com'; 'isis-wg@external.juniper.net'
Subject: [Isis-wg] TE TLVs/Sub-TLVs


TE Authors,

Please forgive the lateness of these comments on the TE draft
(draft-ietf-isis-traffic-02.txt), but I only recently started looking at it
- and ISIS itself for that matter - and I have a few somewhat obvious
comments about the TLVs/sub-TLVs that you've specified. Again, please
forgive this post if these issues have already been discussed and resolved.

Specific comments:

- The Extended IP Reachability TLV (type 135) has a one-octet control
information field that uses 1 bit to indicate the existence of sub-TLVs.
This is not necessary because the enclosing TLV already has a length field
that will indicate whether sub-TLVs are present.

- The Extended IP Reachability TLV (type 135) has a one-octet control
information field that sets aside 6 bits for the IPv4 prefix length when
only 5 are required. One of the bits should be freed for possible future or
experimental use.

- The Extended IP Reachability TLV (type 135) potentially has a one-octet
field to indicate the total length of any sub TLVs. This is not necessary
because the enclosing TLV already has a length field that will indicate the
total length of any sub-TLVs.

- The Extended IS Reachability TLV (type 22) has a one-octet field to
indicate the total length of any sub TLVs. This is not necessary because the
enclosing TLV already has a length field that will indicate the total length
of any sub-TLVs.

General comments and issues:

- The Extended IS Reachability and  Extended IP Reachability TLVs are
inconsistent in the manner in which they specify the presence of sub-TLVs.
Since both definitions are from the same document, and in fact are only one
page apart, shouldn't they look a little more like each other?

- All of the sub-TLVs have been defined in terms of the Type-Length-Value
encoding format, but none has a variable length. This seems to be a real
waste of the relatively small 254 bytes of potential value space.

- Why are the sub-TLVs referred to as sub? Aren't they just TLVs? It looks
like there's still plenty of open space in the main Type range to
accommodate them, and many others for that matter. In a future enhancement,
will we have sub-sub-TLVs? It would seem that a more general and consistent
method for specifying, grouping, and encoding information might be called
for - ASN.1/BER comes to mind.

I realize that many vendors have already implemented this draft - my company
being one of them (I think they'll flog me for this posting), and that some
of the comments, while they will not add much functional value, will require
rework, and in the case of the general comments, possibly quite a lot of
rework. But since the document is still a draft and is introducing sub-TLVs,
it might be nice if it also established a framework that could be copied and
built upon instead of just something that can be made to work.

John Odak
john.odak@marconi.com

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


From isis-wg-admin@spider.juniper.net  Fri Mar  9 14:48:16 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA01810
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 14:48: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 MAA96900;
	Fri, 9 Mar 2001 12:20:03 -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 MAA96885
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 12:19:42 -0800 (PST)
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id OAA07650;
	Fri, 9 Mar 2001 14:43:29 -0500 (EST)
Received: from JLEARMAN-W2K.cisco.com (dhcp-64-102-83-127.cisco.com [64.102.83.127])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id ABP84413;
	Fri, 9 Mar 2001 14:44:08 -0500 (EST)
Message-Id: <4.3.2.7.2.20010309144201.01a40bb8@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Satish Dattatri <satish@pluris.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: RE: [Isis-wg] TE TLVs/Sub-TLVs
Cc: "'Odak, John'" <John.Odak@marconi.com>,
        "'henk@procket.com'" <henk@procket.com>,
        "'isis-wg@external.juniper.net'" <isis-wg@spider.juniper.net>
In-Reply-To: <17C81AD1F1FED411991E006008F6D1CA05A7C5@avalon.pluris.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 09 Mar 2001 14:44:02 -0500


I realize this has already been answered, but I think it needs to
be stated more emphatically.  Implementations are REQUIRED to ignore
TLVs they don't recognize.  For this reason, the length field is
NECESSARY.

I assume this is also true for sub-TLVs (is it stated in the draft
that unrecognized sub-TLVs are to be ignored?)

Jeff

At 02:23 PM 3/9/2001, Satish Dattatri wrote:
>Hi,
>
>By removing the 'L' in the sub-TLV it would cause headache for
>implementations (other than cisco for now) not knowing a particular 
>*reserved* sub-TLV's length. An implementation will now have to 
>skip the rest of the data in TLV after hitting a unknown type.
>This may not be desirable.
>
>But by making the length of all sub-TLV types well-known and 
>constant (no more *reserved* types), then the 'L' in the sub-TLVs 
>can be removed and it becomes sub-TV ;-).
>Multiple values now will be in multiple sub-TV's (for ex. IP V4 interface
>addresses).
>
>Satish
>
>-----Original Message-----
>From: Odak, John [mailto:John.Odak@marconi.com]
>Sent: Friday, March 09, 2001 10:34 AM
>To: 'henk@procket.com'; 'isis-wg@external.juniper.net'
>Subject: [Isis-wg] TE TLVs/Sub-TLVs
>
>
>TE Authors,
>
>Please forgive the lateness of these comments on the TE draft
>(draft-ietf-isis-traffic-02.txt), but I only recently started looking at it
>- and ISIS itself for that matter - and I have a few somewhat obvious
>comments about the TLVs/sub-TLVs that you've specified. Again, please
>forgive this post if these issues have already been discussed and resolved.
>
>Specific comments:
>
>- The Extended IP Reachability TLV (type 135) has a one-octet control
>information field that uses 1 bit to indicate the existence of sub-TLVs.
>This is not necessary because the enclosing TLV already has a length field
>that will indicate whether sub-TLVs are present.
>
>- The Extended IP Reachability TLV (type 135) has a one-octet control
>information field that sets aside 6 bits for the IPv4 prefix length when
>only 5 are required. One of the bits should be freed for possible future or
>experimental use.
>
>- The Extended IP Reachability TLV (type 135) potentially has a one-octet
>field to indicate the total length of any sub TLVs. This is not necessary
>because the enclosing TLV already has a length field that will indicate the
>total length of any sub-TLVs.
>
>- The Extended IS Reachability TLV (type 22) has a one-octet field to
>indicate the total length of any sub TLVs. This is not necessary because the
>enclosing TLV already has a length field that will indicate the total length
>of any sub-TLVs.
>
>General comments and issues:
>
>- The Extended IS Reachability and  Extended IP Reachability TLVs are
>inconsistent in the manner in which they specify the presence of sub-TLVs.
>Since both definitions are from the same document, and in fact are only one
>page apart, shouldn't they look a little more like each other?
>
>- All of the sub-TLVs have been defined in terms of the Type-Length-Value
>encoding format, but none has a variable length. This seems to be a real
>waste of the relatively small 254 bytes of potential value space.
>
>- Why are the sub-TLVs referred to as sub? Aren't they just TLVs? It looks
>like there's still plenty of open space in the main Type range to
>accommodate them, and many others for that matter. In a future enhancement,
>will we have sub-sub-TLVs? It would seem that a more general and consistent
>method for specifying, grouping, and encoding information might be called
>for - ASN.1/BER comes to mind.
>
>I realize that many vendors have already implemented this draft - my company
>being one of them (I think they'll flog me for this posting), and that some
>of the comments, while they will not add much functional value, will require
>rework, and in the case of the general comments, possibly quite a lot of
>rework. But since the document is still a draft and is introducing sub-TLVs,
>it might be nice if it also established a framework that could be copied and
>built upon instead of just something that can be made to work.
>
>John Odak
>john.odak@marconi.com
>
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg

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


From isis-wg-admin@spider.juniper.net  Fri Mar  9 15:11:58 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id PAA02931
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 15:11: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 MAA97047;
	Fri, 9 Mar 2001 12:44:04 -0800 (PST)
Received: from yarilo.pluris.com (pluris.com [208.227.9.12])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id MAA97035
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 12:43:53 -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 MAA09716;
	Fri, 9 Mar 2001 12:08:17 -0800 (PST)
Received: by avalon.pluris.com with Internet Mail Service (5.5.2653.19)
	id <GD96LBSC>; Fri, 9 Mar 2001 12:08:17 -0800
Message-ID: <17C81AD1F1FED411991E006008F6D1CA05A7C7@avalon.pluris.com>
From: Satish Dattatri <satish@pluris.com>
To: "'Jeff Learman'" <jlearman@cisco.com>,
        Satish Dattatri
	 <satish@pluris.com>
Cc: "'Odak, John'" <John.Odak@marconi.com>,
        "'henk@procket.com'"
	 <henk@procket.com>,
        "'isis-wg@external.juniper.net'"
	 <isis-wg@spider.juniper.net>
Subject: RE: [Isis-wg] TE TLVs/Sub-TLVs
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 12:08:08 -0800

Hi Jeff,
Yes I know that LENGTH field is required in TLVs/sub-TLVs to skip
the unknown ones.

I was just saying that removing the length in the sub-TLV would not work
unless *ALL* sub-TLV types (complete range 0-255) and corresponding length
are defined.
Since it is not possible to define complete range of TYPE values now, we
need the length.

satish

-----Original Message-----
From: Jeff Learman [mailto:jlearman@cisco.com]
Sent: Friday, March 09, 2001 11:44 AM
To: Satish Dattatri
Cc: 'Odak, John'; 'henk@procket.com'; 'isis-wg@external.juniper.net'
Subject: RE: [Isis-wg] TE TLVs/Sub-TLVs



I realize this has already been answered, but I think it needs to
be stated more emphatically.  Implementations are REQUIRED to ignore
TLVs they don't recognize.  For this reason, the length field is
NECESSARY.

I assume this is also true for sub-TLVs (is it stated in the draft
that unrecognized sub-TLVs are to be ignored?)

Jeff

At 02:23 PM 3/9/2001, Satish Dattatri wrote:
>Hi,
>
>By removing the 'L' in the sub-TLV it would cause headache for
>implementations (other than cisco for now) not knowing a particular 
>*reserved* sub-TLV's length. An implementation will now have to 
>skip the rest of the data in TLV after hitting a unknown type.
>This may not be desirable.
>
>But by making the length of all sub-TLV types well-known and 
>constant (no more *reserved* types), then the 'L' in the sub-TLVs 
>can be removed and it becomes sub-TV ;-).
>Multiple values now will be in multiple sub-TV's (for ex. IP V4 interface
>addresses).
>
>Satish
>
>-----Original Message-----
>From: Odak, John [mailto:John.Odak@marconi.com]
>Sent: Friday, March 09, 2001 10:34 AM
>To: 'henk@procket.com'; 'isis-wg@external.juniper.net'
>Subject: [Isis-wg] TE TLVs/Sub-TLVs
>
>
>TE Authors,
>
>Please forgive the lateness of these comments on the TE draft
>(draft-ietf-isis-traffic-02.txt), but I only recently started looking at it
>- and ISIS itself for that matter - and I have a few somewhat obvious
>comments about the TLVs/sub-TLVs that you've specified. Again, please
>forgive this post if these issues have already been discussed and resolved.
>
>Specific comments:
>
>- The Extended IP Reachability TLV (type 135) has a one-octet control
>information field that uses 1 bit to indicate the existence of sub-TLVs.
>This is not necessary because the enclosing TLV already has a length field
>that will indicate whether sub-TLVs are present.
>
>- The Extended IP Reachability TLV (type 135) has a one-octet control
>information field that sets aside 6 bits for the IPv4 prefix length when
>only 5 are required. One of the bits should be freed for possible future or
>experimental use.
>
>- The Extended IP Reachability TLV (type 135) potentially has a one-octet
>field to indicate the total length of any sub TLVs. This is not necessary
>because the enclosing TLV already has a length field that will indicate the
>total length of any sub-TLVs.
>
>- The Extended IS Reachability TLV (type 22) has a one-octet field to
>indicate the total length of any sub TLVs. This is not necessary because
the
>enclosing TLV already has a length field that will indicate the total
length
>of any sub-TLVs.
>
>General comments and issues:
>
>- The Extended IS Reachability and  Extended IP Reachability TLVs are
>inconsistent in the manner in which they specify the presence of sub-TLVs.
>Since both definitions are from the same document, and in fact are only one
>page apart, shouldn't they look a little more like each other?
>
>- All of the sub-TLVs have been defined in terms of the Type-Length-Value
>encoding format, but none has a variable length. This seems to be a real
>waste of the relatively small 254 bytes of potential value space.
>
>- Why are the sub-TLVs referred to as sub? Aren't they just TLVs? It looks
>like there's still plenty of open space in the main Type range to
>accommodate them, and many others for that matter. In a future enhancement,
>will we have sub-sub-TLVs? It would seem that a more general and consistent
>method for specifying, grouping, and encoding information might be called
>for - ASN.1/BER comes to mind.
>
>I realize that many vendors have already implemented this draft - my
company
>being one of them (I think they'll flog me for this posting), and that some
>of the comments, while they will not add much functional value, will
require
>rework, and in the case of the general comments, possibly quite a lot of
>rework. But since the document is still a draft and is introducing
sub-TLVs,
>it might be nice if it also established a framework that could be copied
and
>built upon instead of just something that can be made to work.
>
>John Odak
>john.odak@marconi.com
>
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg
_______________________________________________
Isis-wg mailing list  -  Isis-wg@external.juniper.net
http://external.juniper.net/mailman/listinfo/isis-wg


From isis-wg-admin@spider.juniper.net  Fri Mar  9 16:26:24 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id QAA05519
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 16:26:18 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA97444;
	Fri, 9 Mar 2001 13:58:03 -0800 (PST)
Received: from miata.procket.com (miata.procket.com [205.253.146.45])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id NAA97432
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 13:57:53 -0800 (PST)
Received: from kraak.procket.com (miata.procket.com [10.1.1.1])
	by miata.procket.com (8.11.1/8.11.1) with ESMTP id f29LMHh13632;
	Fri, 9 Mar 2001 13:22:18 -0800 (PST)
From: Henk Smit <henk@Procket.com>
Received: (from henk@localhost)
	by kraak.procket.com (8.9.3/8.9.3) id WAA00900;
	Fri, 9 Mar 2001 22:25:26 +0100
Message-Id: <200103092125.WAA00900@kraak.procket.com>
To: John.Odak@Marconi.com (Odak, John)
Cc: henk@Procket.com ('henk@procket.com'),
        isis-wg@spider.juniper.net ('isis-wg@external.juniper.net')
In-Reply-To: <39469E08BD83D411A3D900204840EC5519EB42@VIE-MSGUSR-01> from "Odak, John" at Mar 09, 2001 01:33:43 PM
X-Mailer: ELM [version 2.5 PL1]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] Re: TE TLVs/Sub-TLVs
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 22:25:26 +0100 (MET)
Content-Transfer-Encoding: 7bit


    Hello John,

> Please forgive the lateness of these comments on the TE draft
> (draft-ietf-isis-traffic-02.txt), but I only recently started looking at it
> - and ISIS itself for that matter - and I have a few somewhat obvious
> comments about the TLVs/sub-TLVs that you've specified. Again, please
> forgive this post if these issues have already been discussed and resolved.
> 
> Specific comments:
> 
> - The Extended IP Reachability TLV (type 135) has a one-octet control
> information field that uses 1 bit to indicate the existence of sub-TLVs.
> This is not necessary because the enclosing TLV already has a length field
> that will indicate whether sub-TLVs are present.

  As others have pointed out, what happens if you put multiple IP prefixes
 in one TLV135 ? What comes after you have decyphered the first IP prefix ?
 Some sub-TLVs or the next IP prefix ?

> - The Extended IP Reachability TLV (type 135) has a one-octet control
> information field that sets aside 6 bits for the IPv4 prefix length when
> only 5 are required. One of the bits should be freed for possible future or
> experimental use.

  IP prefixes have a length between (and including) 0 bits (aka the default
 route) and 32 bits (aka host routes). That are 33 different values.
 Please enlighten us how to fit 33 values in 5 bits .... ;-)
 I think you are just of by one.

> - The Extended IP Reachability TLV (type 135) potentially has a one-octet
> field to indicate the total length of any sub TLVs. This is not necessary
> because the enclosing TLV already has a length field that will indicate the
> total length of any sub-TLVs.

  Same thing as above. Don't forget you can put multiple IP prefixes in
 TLV135, all which might have sub-TLVs.

> - The Extended IS Reachability TLV (type 22) has a one-octet field to
> indicate the total length of any sub TLVs. This is not necessary because the
> enclosing TLV already has a length field that will indicate the total length
> of any sub-TLVs.

  Same thing.

> General comments and issues:
> 
> - The Extended IS Reachability and  Extended IP Reachability TLVs are
> inconsistent in the manner in which they specify the presence of sub-TLVs.
> Since both definitions are from the same document, and in fact are only one
> page apart, shouldn't they look a little more like each other?

  This is intentional, and you'll have to blame Tony Li for this.
 The assumption was that a router can have tens to hunderds of adjacencies.
 In the worst case maye thousands. But a router might advertise thousands,
 maybe even hundreds of thousands of IP prefixes. Therefor we think that
 conserving space in TLV135 is more important than conserving space in TLV22.
 Another reason is that sub-TLVs in TLV22 are common, while sub-TLVs in
 TLV135 are hardly seen today. (There are plans for IP prefix coloring, and
 for multicast tags).

> - All of the sub-TLVs have been defined in terms of the Type-Length-Value
> encoding format, but none has a variable length. This seems to be a real
> waste of the relatively small 254 bytes of potential value space.

  You don't know what sub-TLVs will exist in the future. So once your code
 encounters a sub-TLV it doesn't understand, the Length will allow you to
 skip it. This is a great help in the real world when ISP and enterprises
 want to migrate to newer version of the protocol without first upgrading
 all the software on all their routers.

> - Why are the sub-TLVs referred to as sub? Aren't they just TLVs?

  Because sub-TLVs are TLVs inside TLVs.
 Giving them a different name makes it easier to discuss them in discussions.

> It looks
> like there's still plenty of open space in the main Type range to
> accommodate them, and many others for that matter. In a future enhancement,
> will we have sub-sub-TLVs?

  Maybe. That is up to the authors of new extensions that define new
 sub-TLVs. If they wanna use TLV encoding inside their sub-TLVs, that
 is fine with me. I guess those thingies will be called sub-sub-TLVs.

> It would seem that a more general and consistent
> method for specifying, grouping, and encoding information might be called
> for - ASN.1/BER comes to mind.

  The current encoding is all in the same spirit of the original ISO 10589.
 Using ASN.1 might be an improvement in itself, but it would also imply
 a big change in "style" of the protocol. I am not sure everybody likes
 this. And we wanna keep it simple. Maybe if people come up with a brand
 new routing protocol.

> I realize that many vendors have already implemented this draft - my company
> being one of them (I think they'll flog me for this posting), and that some
> of the comments, while they will not add much functional value, will require
> rework, and in the case of the general comments, possibly quite a lot of
> rework. But since the document is still a draft

  The document is a draft document. That implies we can change the text.
 That does not necessarily imply that we wanna change the content itself
 (the protocol). After all, the TE extensions are not just experimental
 anymore. They are used in the real world.
 
> and is introducing sub-TLVs,
> it might be nice if it also established a framework that could be copied and
> built upon instead of just something that can be made to work.

  IMHO the current draft is just that: a framework. It defines how
 sub-TLVs are used in TLV22 and TLV135. People that wanna experiment
 with new stuff can add any information they want to link or prefixes.
 Expanding this framework to other protocols is overkill IMHO, as many
 protocols have different needs.

  You might notice that all newer protocols nowadays make use of TLVs.
 See attributes in BGP for example.
 Hope this helps,

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


From isis-wg-admin@spider.juniper.net  Fri Mar  9 17:21:03 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA07469
	for <isis-archive@odin.ietf.org>; Fri, 9 Mar 2001 17:21: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 OAA97756;
	Fri, 9 Mar 2001 14:53:04 -0800 (PST)
Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA97744
	for <isis-wg@spider.juniper.net>; Fri, 9 Mar 2001 14:52:55 -0800 (PST)
Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12])
	by mailgate.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA28501;
	Fri, 9 Mar 2001 17:17:18 -0500 (EST)
Received: from whq-msgrtr-01.pit.comms.marconi.com (whq-msgrtr-01.pit.comms.marconi.com [169.144.2.221])
	by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id RAA18989;
	Fri, 9 Mar 2001 17:17:22 -0500 (EST)
Received: by whq-msgrtr-01.pit.comms.marconi.com with Internet Mail Service (5.5.2650.21)
	id <F301SJCS>; Fri, 9 Mar 2001 17:17:20 -0500
Message-ID: <39469E08BD83D411A3D900204840EC5519EB43@VIE-MSGUSR-01>
From: "Odak, John" <John.Odak@Marconi.com>
To: "'Henk Smit'" <henk@procket.com>
Cc: isis-wg@spider.juniper.net
Subject: RE: [Isis-wg] Re: TE TLVs/Sub-TLVs
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 9 Mar 2001 17:16:40 -0500

Hello Henk,

Thanks for the explanations.

John

-----Original Message-----
From: Henk Smit [mailto:henk@procket.com]
Sent: Friday, March 09, 2001 4:25 PM
To: John.Odak@marconi.com
Cc: henk@procket.com; isis-wg@spider.juniper.net
Subject: [Isis-wg] Re: TE TLVs/Sub-TLVs



    Hello John,

> Please forgive the lateness of these comments on the TE draft
> (draft-ietf-isis-traffic-02.txt), but I only recently started looking at
it
> - and ISIS itself for that matter - and I have a few somewhat obvious
> comments about the TLVs/sub-TLVs that you've specified. Again, please
> forgive this post if these issues have already been discussed and
resolved.
> 
> Specific comments:
> 
> - The Extended IP Reachability TLV (type 135) has a one-octet control
> information field that uses 1 bit to indicate the existence of sub-TLVs.
> This is not necessary because the enclosing TLV already has a length field
> that will indicate whether sub-TLVs are present.

  As others have pointed out, what happens if you put multiple IP prefixes
 in one TLV135 ? What comes after you have decyphered the first IP prefix ?
 Some sub-TLVs or the next IP prefix ?

> - The Extended IP Reachability TLV (type 135) has a one-octet control
> information field that sets aside 6 bits for the IPv4 prefix length when
> only 5 are required. One of the bits should be freed for possible future
or
> experimental use.

  IP prefixes have a length between (and including) 0 bits (aka the default
 route) and 32 bits (aka host routes). That are 33 different values.
 Please enlighten us how to fit 33 values in 5 bits .... ;-)
 I think you are just of by one.

> - The Extended IP Reachability TLV (type 135) potentially has a one-octet
> field to indicate the total length of any sub TLVs. This is not necessary
> because the enclosing TLV already has a length field that will indicate
the
> total length of any sub-TLVs.

  Same thing as above. Don't forget you can put multiple IP prefixes in
 TLV135, all which might have sub-TLVs.

> - The Extended IS Reachability TLV (type 22) has a one-octet field to
> indicate the total length of any sub TLVs. This is not necessary because
the
> enclosing TLV already has a length field that will indicate the total
length
> of any sub-TLVs.

  Same thing.

> General comments and issues:
> 
> - The Extended IS Reachability and  Extended IP Reachability TLVs are
> inconsistent in the manner in which they specify the presence of sub-TLVs.
> Since both definitions are from the same document, and in fact are only
one
> page apart, shouldn't they look a little more like each other?

  This is intentional, and you'll have to blame Tony Li for this.
 The assumption was that a router can have tens to hunderds of adjacencies.
 In the worst case maye thousands. But a router might advertise thousands,
 maybe even hundreds of thousands of IP prefixes. Therefor we think that
 conserving space in TLV135 is more important than conserving space in
TLV22.
 Another reason is that sub-TLVs in TLV22 are common, while sub-TLVs in
 TLV135 are hardly seen today. (There are plans for IP prefix coloring, and
 for multicast tags).

> - All of the sub-TLVs have been defined in terms of the Type-Length-Value
> encoding format, but none has a variable length. This seems to be a real
> waste of the relatively small 254 bytes of potential value space.

  You don't know what sub-TLVs will exist in the future. So once your code
 encounters a sub-TLV it doesn't understand, the Length will allow you to
 skip it. This is a great help in the real world when ISP and enterprises
 want to migrate to newer version of the protocol without first upgrading
 all the software on all their routers.

> - Why are the sub-TLVs referred to as sub? Aren't they just TLVs?

  Because sub-TLVs are TLVs inside TLVs.
 Giving them a different name makes it easier to discuss them in
discussions.

> It looks
> like there's still plenty of open space in the main Type range to
> accommodate them, and many others for that matter. In a future
enhancement,
> will we have sub-sub-TLVs?

  Maybe. That is up to the authors of new extensions that define new
 sub-TLVs. If they wanna use TLV encoding inside their sub-TLVs, that
 is fine with me. I guess those thingies will be called sub-sub-TLVs.

> It would seem that a more general and consistent
> method for specifying, grouping, and encoding information might be called
> for - ASN.1/BER comes to mind.

  The current encoding is all in the same spirit of the original ISO 10589.
 Using ASN.1 might be an improvement in itself, but it would also imply
 a big change in "style" of the protocol. I am not sure everybody likes
 this. And we wanna keep it simple. Maybe if people come up with a brand
 new routing protocol.

> I realize that many vendors have already implemented this draft - my
company
> being one of them (I think they'll flog me for this posting), and that
some
> of the comments, while they will not add much functional value, will
require
> rework, and in the case of the general comments, possibly quite a lot of
> rework. But since the document is still a draft

  The document is a draft document. That implies we can change the text.
 That does not necessarily imply that we wanna change the content itself
 (the protocol). After all, the TE extensions are not just experimental
 anymore. They are used in the real world.
 
> and is introducing sub-TLVs,
> it might be nice if it also established a framework that could be copied
and
> built upon instead of just something that can be made to work.

  IMHO the current draft is just that: a framework. It defines how
 sub-TLVs are used in TLV22 and TLV135. People that wanna experiment
 with new stuff can add any information they want to link or prefixes.
 Expanding this framework to other protocols is overkill IMHO, as many
 protocols have different needs.

  You might notice that all newer protocols nowadays make use of TLVs.
 See attributes in BGP for example.
 Hope this helps,

      henk.
_______________________________________________
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 Mar 15 04:34:33 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27658
	for <isis-archive@odin.ietf.org>; Thu, 15 Mar 2001 04:34:32 -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 CAA30552;
	Thu, 15 Mar 2001 02:07:05 -0800 (PST)
Received: from mel.alcatel.fr (mel.alcatel.fr [212.208.74.132])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA30536
	for <isis-wg@spider.juniper.net>; Thu, 15 Mar 2001 02:06:44 -0800 (PST)
Received: from aifhs2.alcatel.fr (mailhub.alcatel.fr [155.132.180.80])
        by mel.alcatel.fr (ALCANET/SMTP) with ESMTP id KAA29517;
        Thu, 15 Mar 2001 10:24:37 +0100
Received: from medine.ms.alcatel.fr (medine.ms.alcatel.fr [193.105.117.1])
        by aifhs2.alcatel.fr (ALCANET/SMTP2) with ESMTP id KAA18963;
        Thu, 15 Mar 2001 10:24:34 +0100 (MET)
Received: from ms.ms.alcatel.fr (ms.ms.alcatel.fr [188.9.12.93])
	by medine.ms.alcatel.fr (8.8.8/8.8.8/aar-1.2) with ESMTP id KAA05970;
	Thu, 15 Mar 2001 10:29:53 +0100 (MET)
Received: from reaumur.dinsunnet (reaumur [188.9.33.51])
	by ms.ms.alcatel.fr (8.8.7/8.8.7/aar-1.0) with SMTP id KAA21321;
	Thu, 15 Mar 2001 10:29:58 +0100 (MET)
Received: from ms.alcatel.fr by reaumur.dinsunnet (SMI-8.6/SMI-SVR4)
	id KAA10163; Thu, 15 Mar 2001 10:25:42 +0100
Message-ID: <3AB08A96.D67F9D1E@ms.alcatel.fr>
From: Bruno Mongazon <mongazon@ms.alcatel.fr>
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4u)
X-Accept-Language: en
MIME-Version: 1.0
To: Alex Zinin <azinin@cisco.com>
CC: Jeff Parker <jparker@axiowave.com>, mike shand <mshand@cisco.com>,
        isis-wg@spider.juniper.net
Subject: Re: [Isis-wg] IS-IS restart
References: <3AA91205.65DC418A@ms.alcatel.fr> <8406.010309@cisco.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: Thu, 15 Mar 2001 10:25:42 +0100
Content-Transfer-Encoding: 7bit

Alex Zinin wrote:
> 
> Bruno,
> 
>  I see your point.
> 
>  However, I think such a choice would make it harder
>  to predict that a graceful restart will actually happen
>  when different implementations make difference choices.
>  I would suggest we make it simple and go with the hold timer.
> 
> --
> Alex Zinin
>

Alex, Mike,

Agree, let's make it simple and go with the hold timer.

I would just suggest to add a note in the draft indicating that, in
order for graceful restart to actually happen, the hold timer of a
restarting-capable IS shall be set to the max time the IS is expected to
be out (including restart time).

Best regards.
Bruno.

 
> > Alex Zinin wrote:
> >>
> >> Bruno,
> >>
> >> > Yes, i've got it:
> >> > The faster (lower) you detect bad links, the faster (lower) you restart!
> >>
> >> > Anyway the restart time will be hidden. It is a part of the holding
> >> > time.
> >> > If you want to make this part visible to the peer, my suggestion should
> >> > be ok?
> >>
> >> What value would it add to the mechanism?
> >>
> >> Alex.
> 
> > Not a big value to the mechanism itself but a choice criterion from the
> > peer perspective:
> 
> > The peer can choose to support or not restart for the adjacency
> > depending on the two values (holding time, restart time). If a router
> > says it can detect bad links fast but restarts slowly, then the peer
> > might choose high-speed detection without restart.
> 
> > If everything is hidden in the hold timer, then the peer just ack/nack
> > according to its restart capability.
> 
> > Bruno.
_______________________________________________
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 Mar 15 04:56:42 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id EAA27813
	for <isis-archive@odin.ietf.org>; Thu, 15 Mar 2001 04:56:40 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA30673;
	Thu, 15 Mar 2001 02:28:04 -0800 (PST)
Received: from cisco.com (jaws.cisco.com [198.135.0.150])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id CAA30657
	for <isis-wg@spider.juniper.net>; Thu, 15 Mar 2001 02:27:56 -0800 (PST)
Received: from mshand-w2k.cisco.com (uxb-dhcp-198-135-1-182.cisco.com [198.135.1.182])
	by cisco.com (8.8.8/2.6/Cisco List Logging/8.8.8) with ESMTP id JAA06796;
	Thu, 15 Mar 2001 09:51:03 GMT
Message-Id: <4.3.2.7.2.20010315095011.034ee498@jaws.cisco.com>
X-Sender: mshand@jaws.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: Bruno Mongazon <mongazon@ms.alcatel.fr>
From: mike shand <mshand@cisco.com>
Subject: Re: [Isis-wg] IS-IS restart
Cc: Alex Zinin <azinin@cisco.com>, Jeff Parker <jparker@axiowave.com>,
        isis-wg@spider.juniper.net
In-Reply-To: <3AB08A96.D67F9D1E@ms.alcatel.fr>
References: <3AA91205.65DC418A@ms.alcatel.fr>
 <8406.010309@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Thu, 15 Mar 2001 09:51:06 +0000

OK. I'll add something to that effect.

         Mike

At 10:25 15/03/2001 +0100, Bruno Mongazon wrote:
>Alex Zinin wrote:
> >
> > Bruno,
> >
> >  I see your point.
> >
> >  However, I think such a choice would make it harder
> >  to predict that a graceful restart will actually happen
> >  when different implementations make difference choices.
> >  I would suggest we make it simple and go with the hold timer.
> >
> > --
> > Alex Zinin
> >
>
>Alex, Mike,
>
>Agree, let's make it simple and go with the hold timer.
>
>I would just suggest to add a note in the draft indicating that, in
>order for graceful restart to actually happen, the hold timer of a
>restarting-capable IS shall be set to the max time the IS is expected to
>be out (including restart time).
>
>Best regards.
>Bruno.
>
>
> > > Alex Zinin wrote:
> > >>
> > >> Bruno,
> > >>
> > >> > Yes, i've got it:
> > >> > The faster (lower) you detect bad links, the faster (lower) you 
> restart!
> > >>
> > >> > Anyway the restart time will be hidden. It is a part of the holding
> > >> > time.
> > >> > If you want to make this part visible to the peer, my suggestion 
> should
> > >> > be ok?
> > >>
> > >> What value would it add to the mechanism?
> > >>
> > >> Alex.
> >
> > > Not a big value to the mechanism itself but a choice criterion from the
> > > peer perspective:
> >
> > > The peer can choose to support or not restart for the adjacency
> > > depending on the two values (holding time, restart time). If a router
> > > says it can detect bad links fast but restarts slowly, then the peer
> > > might choose high-speed detection without restart.
> >
> > > If everything is hidden in the hold timer, then the peer just ack/nack
> > > according to its restart capability.
> >
> > > Bruno.

_______________________________________________
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 Mar 16 20:13:30 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA16895
	for <isis-archive@odin.ietf.org>; Fri, 16 Mar 2001 20:13:29 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id RAA39900;
	Fri, 16 Mar 2001 17:46:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA38107
	for <isis-wg@spider.juniper.net>; Fri, 16 Mar 2001 10:14:38 -0800 (PST)
Received: from qnsgs000.nortel.com (qnsgs000.nortelnetworks.com [47.211.0.31])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2GHaBb63019
	for <isis-wg@juniper.net>; Fri, 16 Mar 2001 09:36:12 -0800 (PST)
X-JNPR-Received-From: outside
Received: from znsgd00t.europe.nortel.com by qnsgs000.nortel.com;
          Fri, 16 Mar 2001 17:35:52 +0000
Received: by znsgd00t.europe.nortel.com 
          with Internet Mail Service (5.5.2653.19) id <G8XK1ZTZ>;
          Fri, 16 Mar 2001 17:34:25 -0000
Message-ID: <AD35145AF4A8D411BD6702204804F28302FC4053@zhard00m.europe.nortel.com>
From: "Philip Christian" <christi@nortelnetworks.com>
To: isis-wg@juniper.net, chopps@djinesys.com
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01C0AE3F.567A9260"
Subject: [Isis-wg] Comments on IS-IS for IPv6
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 16 Mar 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_01C0AE3F.567A9260
Content-Type: text/plain

First, I noticed that the draft-ietf-isis-ipv6-01.txt appears to have timed
out.
I think that it is important to have something that says how IPv6 should be
routed with IS-IS and so this should be re-submitted.
If Christian wants any help with this then I would be pleased to help.

I also have some comments on the draft.

It says in section 7 "Based on further study, future versions of this draft
may specify an optional method for encapsulating IS-IS PDUs in IPv6
packets.". My understanding is that this option has been more or less ruled
out for IPv4, and so I guess for IPv6 too. If so then this line could be
replaced with something similar to "IS-IS PDUs will continue to be
encapsulated using ISO 9542 as per RFC 1195."

Also I have a more radical idea.

In RFC 1195 it basically says (in my own words) that if any of network layer
protocol "X" appears in an IS-IS area, then all routers in that area must
support "X", where "X" would be something such as CLNP, IPv4 or IPv6.

The risk is that if an IPv6-only router or routers are accidentally
connected to an existing IPv4 network, that IS-IS in the IPv4 will see the
IPv6 routers as a valid path. If any IPv4 packets are then sent to the IPv6
routers or vice versa then packet loss will occur.

This problem could be solved by adding a clause into the IS-IS for IPv6
draft saying something like this:-
"An IPv6-only router that uses IS-IS for IPv6 shall check that a
neighbouring node supports IPv6 before completing an IS-IS adjacency with
that node. It may do this by inspection of the "protocols supported" field
of IS-IS Hello PDUs that it receives from the neighbouring node. If IPv6 is
not listed in the "protocols supported" field of Hello packets sent by the
neighbour then the IPv6-only router will refuse the adjacency."

It wouldn't really change the rule in RFC 1195, but it would help to protect
against an accidental connection dragging down part of an existing network.

Regards, Philip Christian

Tel (+44) (0)1279 403184 Fax (+44) (0)1279 402500
e-mail christi@nortelnetworks.com
> Registered Company name & Address:  
> Nortel Networks UK Limited, Maidenhead Office Park, 
> Westacott Way, Maidenhead, Berkshire SL6 3QH 
> Company number: 3937799

------_=_NextPart_001_01C0AE3F.567A9260
Content-Type: text/html
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=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2654.19">
<TITLE>Comments on IS-IS for IPv6</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2 FACE=3D"Arial">First, I noticed that the =
draft-ietf-isis-ipv6-01.txt appears to have timed out.</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">I think that it is important to have =
something that says how IPv6 should be routed with IS-IS and so this =
should be re-submitted.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">If Christian wants any help with this =
then I would be pleased to help.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">I also have some comments on the =
draft.</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">It says in section 7 =
&quot;</FONT><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Based on =
further study, future versions of this draft may specify an optional =
method for encapsulating IS-IS PDUs in IPv6 packets.&quot;. My =
understanding is that this option has been more or less ruled out for =
IPv4, and so I guess for IPv6 too. If so then this line could be =
replaced with something similar to &quot;IS-IS PDUs will continue to be =
encapsulated using ISO 9542 as per RFC 1195.&quot;</FONT></P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">Also I have a more =
radical idea.</FONT>
</P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">In RFC 1195 it =
basically says (in my own words) that if any of network layer protocol =
&quot;X&quot; appears in an IS-IS area, then all routers in that area =
must support &quot;X&quot;, where &quot;X&quot; would be something such =
as CLNP, IPv4 or IPv6.</FONT></P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">The risk is that if =
an IPv6-only router or routers are accidentally connected to an =
existing IPv4 network, that IS-IS in the IPv4 will see the IPv6 routers =
as a valid path. If any IPv4 packets are then sent to the IPv6 routers =
or vice versa then packet loss will occur.</FONT></P>

<P><FONT COLOR=3D"#000000" SIZE=3D2 FACE=3D"Arial">This problem could =
be solved by adding a clause into the IS-IS for IPv6 draft saying =
something like this:-</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">&quot;An IPv6-only router that uses =
IS-IS for IPv6 shall check that a neighbouring node supports IPv6 =
before completing an IS-IS adjacency with that node. It may do this by =
inspection of the &quot;protocols supported&quot; field of IS-IS Hello =
PDUs that it receives from the neighbouring node. If IPv6 is not listed =
in the &quot;protocols supported&quot; field of Hello packets sent by =
the neighbour then the IPv6-only router will refuse the =
adjacency.&quot;</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">It wouldn't really change the rule in =
RFC 1195, but it would help to protect against an accidental connection =
dragging down part of an existing network.</FONT></P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Regards, Philip Christian</FONT>
</P>

<P><FONT SIZE=3D2 FACE=3D"Arial">Tel (+44) (0)1279 403184 Fax (+44) =
(0)1279 402500</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">e-mail =
christi@nortelnetworks.com</FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Registered Company name &amp; =
Address:&nbsp; </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Nortel Networks UK Limited, =
Maidenhead Office Park, </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Westacott Way, Maidenhead, Berkshire =
SL6 3QH </FONT>
<BR><FONT SIZE=3D2 FACE=3D"Arial">Company number: 3937799</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C0AE3F.567A9260--
_______________________________________________
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 Mar 16 20:17:53 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA16949
	for <isis-archive@odin.ietf.org>; Fri, 16 Mar 2001 20:17:52 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id RAA39925;
	Fri, 16 Mar 2001 17:49:38 -0800 (PST)
Received: from red.juniper.net (red.juniper.net [172.17.28.10])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id RAA39822
	for <isis-wg@spider.juniper.net>; Fri, 16 Mar 2001 17:34:43 -0800 (PST)
Received: from postal.jnpr.net (postal.jnpr.net [172.24.244.20])
	by red.juniper.net (8.9.3/8.9.3) with ESMTP id QAA22785
	for <isis-wg@juniper.net>; Fri, 16 Mar 2001 16:58:16 -0800 (PST)
Received: by postal.jnpr.net with Internet Mail Service (5.5.2653.19)
	id <HB5A5K8P>; Fri, 16 Mar 2001 16:58:16 -0800
Message-ID: <C0D6C1C24CDBE1449BFEF1B72AFBF3A7026357E5@postal.jnpr.net>
From: Brian Edwards <bedwards@juniper.net>
To: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Isis-wg] M-ISIS
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 16 Mar 2001 16:58:15 -0800


Instead of specifying reserved MT ID #'s in the M-ISIS draft; why not use
the Address Families defined in RFC1700 like MBGP? I mentioned this to
Nischal and he thinks it is a good idea, so I am sending it to the working
group for comments.

-Brian
_______________________________________________
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 Mar 17 21:52:08 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id VAA12231
	for <isis-archive@odin.ietf.org>; Sat, 17 Mar 2001 21:52:08 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id TAA47952;
	Sat, 17 Mar 2001 19:24:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id TAA47936
	for <isis-wg@spider.juniper.net>; Sat, 17 Mar 2001 19:23:31 -0800 (PST)
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2I2ipb95410
	for <isis-wg@juniper.net>; Sat, 17 Mar 2001 18:44:51 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com ([63.200.50.170])
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with ESMTP id <0GAD00LI8H2792@mta5.snfc21.pbi.net> for isis-wg@juniper.net;
 Sat, 17 Mar 2001 18:46:55 -0800 (PST)
From: Tony Przygienda <prz@redback.com>
To: isis-wg@juniper.net
Message-id: <3AB410FF.233CEBFC@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
Subject: [Isis-wg] last call for draft-ietf-isis-transient-00.txt
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <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, 17 Mar 2001 17:35:59 -0800
Content-Transfer-Encoding: 7bit

draft-ietf-isis-transient-00.txt  goes last call. Last call finishes in
2 weeks

        thanks

        --- tony

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


From isis-wg-admin@spider.juniper.net  Sat Mar 17 22:06:05 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA12299
	for <isis-archive@odin.ietf.org>; Sat, 17 Mar 2001 22:06: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 TAA48049;
	Sat, 17 Mar 2001 19:39:03 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id TAA48037
	for <isis-wg@spider.juniper.net>; Sat, 17 Mar 2001 19:38:25 -0800 (PST)
Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2I2xjb95515
	for <isis-wg@juniper.net>; Sat, 17 Mar 2001 18:59:45 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com ([63.200.50.170])
 by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with ESMTP id <0GAD00KBXHQLKH@mta6.snfc21.pbi.net> for isis-wg@juniper.net;
 Sat, 17 Mar 2001 19:01:34 -0800 (PST)
From: Tony Przygienda <prz@redback.com>
Subject: Re: [Isis-wg] Comments on IS-IS for IPv6
To: Philip Christian <christi@nortelnetworks.com>
Cc: isis-wg@juniper.net, chopps@djinesys.com
Message-id: <3AB4146D.A0DEA9C6@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: 
 <AD35145AF4A8D411BD6702204804F28302FC4053@zhard00m.europe.nortel.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: Sat, 17 Mar 2001 17:50:37 -0800
Content-Transfer-Encoding: 7bit

Philip Christian wrote:

>
>
> First, I noticed that the draft-ietf-isis-ipv6-01.txt appears to have
> timed out.

Christian's reissuing. It's in ADs hands right now and should go
publication anytime soon.

> I think that it is important to have something that says how IPv6
> should be routed with IS-IS and so this should be re-submitted.
>
> If Christian wants any help with this then I would be pleased to help.
>
> I also have some comments on the draft.
>
> It says in section 7 "Based on further study, future versions of this
> draft may specify an optional method for encapsulating IS-IS PDUs in
> IPv6 packets.". My understanding is that this option has been more or
> less ruled out for IPv4, and so I guess for IPv6 too. If so then this
> line could be replaced with something similar to "IS-IS PDUs will
> continue to be encapsulated using ISO 9542 as per RFC 1195."

Nothing has been ruled out. The requirement may or may not arise again.
The 'may specify' here is fine.  But your point is valid in the sense
that since notyhing happened we should nuke the sentence completely
before it goes RFC.

> Also I have a more radical idea.
>
> In RFC 1195 it basically says (in my own words) that if any of network
> layer protocol "X" appears in an IS-IS area, then all routers in that
> area must support "X", where "X" would be something such as CLNP, IPv4
> or IPv6.
>
> The risk is that if an IPv6-only router or routers are accidentally
> connected to an existing IPv4 network, that IS-IS in the IPv4 will see
> the IPv6 routers as a valid path. If any IPv4 packets are then sent to
> the IPv6 routers or vice versa then packet loss will occur.
>
> This problem could be solved by adding a clause into the IS-IS for
> IPv6 draft saying something like this:-
> "An IPv6-only router that uses IS-IS for IPv6 shall check that a
> neighbouring node supports IPv6 before completing an IS-IS adjacency
> with that node. It may do this by inspection of the "protocols
> supported" field of IS-IS Hello PDUs that it receives from the
> neighbouring node. If IPv6 is not listed in the "protocols supported"
> field of Hello packets sent by the neighbour then the IPv6-only router
> will refuse the adjacency."

hmm, isn't that somewhere in 1195 anywherem too lazy to check now ?  You
can't build adjacencies unless protocols supported overlap.

> It wouldn't really change the rule in RFC 1195, but it would help to
> protect against an accidental connection dragging down part of an
> existing network.

Christian, you want to deal with those comments ?  Minor enough to
probably not being a MUST but somehow valid.

    thansk


    -- 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 Mar 19 09: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 SMTP id JAA11221
	for <isis-archive@odin.ietf.org>; Mon, 19 Mar 2001 09:17: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 GAA56510;
	Mon, 19 Mar 2001 06:50:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id GAA56495
	for <isis-wg@spider.juniper.net>; Mon, 19 Mar 2001 06:49:27 -0800 (PST)
Received: from presque.djinesys.com (presque.djinesys.com [198.108.88.2])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2JEAWb15459
	for <isis-wg@juniper.net>; Mon, 19 Mar 2001 06:10:32 -0800 (PST)
X-JNPR-Received-From: outside
Received: from q.nexthop.com ([141.211.130.163])
	by presque.djinesys.com (8.9.3/8.9.3) with ESMTP id JAA77274;
	Mon, 19 Mar 2001 09:11:47 -0500 (EST)
	(envelope-from chopps@q.nexthop.com)
Received: (from chopps@localhost)
	by q.nexthop.com (8.11.0/8.11.0) id f2JECgr26710;
	Mon, 19 Mar 2001 09:12:42 -0500 (EST)
From: "Christian E . Hopps" <chopps@nexthop.com>
To: Tony Przygienda <prz@redback.com>
Cc: Philip Christian <christi@nortelnetworks.com>, isis-wg@juniper.net
Subject: Re: [Isis-wg] Comments on IS-IS for IPv6
Message-ID: <20010319091242.A26591@nexthop.com>
References: <AD35145AF4A8D411BD6702204804F28302FC4053@zhard00m.europe.nortel.com> <3AB4146D.A0DEA9C6@redback.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <3AB4146D.A0DEA9C6@redback.com>; from prz@redback.com on Sat, Mar 17, 2001 at 05:50:37PM -0800
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Mar 2001 09:12:42 -0500

On Sat, Mar 17, 2001 at 05:50:37PM -0800, Tony Przygienda wrote:
> Philip Christian wrote:
> > It says in section 7 "Based on further study, future versions of this
> > draft may specify an optional method for encapsulating IS-IS PDUs in
> > IPv6 packets.". My understanding is that this option has been more or
> > less ruled out for IPv4, and so I guess for IPv6 too. If so then this
> > line could be replaced with something similar to "IS-IS PDUs will
> > continue to be encapsulated using ISO 9542 as per RFC 1195."
> 
> Nothing has been ruled out. The requirement may or may not arise again.
> The 'may specify' here is fine.  But your point is valid in the sense
> that since notyhing happened we should nuke the sentence completely
> before it goes RFC.

I can remove this before I re-submit.

> > Also I have a more radical idea.

[... don't form adj when nlpid of nbr indicates no ipv6 and router is
ipv6 only]

> > This problem could be solved by adding a clause into the IS-IS for
> > IPv6 draft saying something like this:-
> > "An IPv6-only router that uses IS-IS for IPv6 shall check that a
> > neighbouring node supports IPv6 before completing an IS-IS adjacency
> > with that node. It may do this by inspection of the "protocols
> > supported" field of IS-IS Hello PDUs that it receives from the
> > neighbouring node. If IPv6 is not listed in the "protocols supported"
> > field of Hello packets sent by the neighbour then the IPv6-only router
> > will refuse the adjacency."
> 
> hmm, isn't that somewhere in 1195 anywherem too lazy to check now ?  You
> can't build adjacencies unless protocols supported overlap.
> 
> > It wouldn't really change the rule in RFC 1195, but it would help to
> > protect against an accidental connection dragging down part of an
> > existing network.
> 
> Christian, you want to deal with those comments ?  Minor enough to
> probably not being a MUST but somehow valid.

I actually coded my implementation this way.  The problem is that this
doesn't solve all the misconfiguration situations.  I think the much
more likely "mis"-configuration will be for a router to be v6 only and
its neighbors dual v4v6. In this case the adjacency will form but v4
traffic will get dropped by the v6 only router.

Further the draft leaves open the above "misconfiguration" state and
implementors are free to actually run multiple SPFs paying attention
to the NLPID in the LSPs so as to restrict the graph to only supported
protocols.  This removes the "all routers must support the same protocols
in an area" restriction.

So, if people feel it is important I think we could add some text indicating
that adjacencies should only form when the intersection of the NLPID
is non-empty.  This will cover the v6 only to v4 only router case, but
not restrict the dual v6v4 to v6 only case.

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


From isis-wg-admin@spider.juniper.net  Mon Mar 19 11:47:37 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA15042
	for <isis-archive@odin.ietf.org>; Mon, 19 Mar 2001 11:47:35 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA57164;
	Mon, 19 Mar 2001 09:21:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id JAA57151
	for <isis-wg@spider.juniper.net>; Mon, 19 Mar 2001 09:20:25 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2JGfTb20341
	for <isis-wg@juniper.net>; Mon, 19 Mar 2001 08:41:29 -0800 (PST)
X-JNPR-Received-From: outside
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id LAA06604;
	Mon, 19 Mar 2001 11:42:56 -0500 (EST)
Received: from JLEARMAN-W2K.cisco.com (dhcp-64-102-83-127.cisco.com [64.102.83.127])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id ACH08249;
	Mon, 19 Mar 2001 11:43:38 -0500 (EST)
Message-Id: <4.3.2.7.2.20010319112244.019a51c8@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Christian E . Hopps" <chopps@nexthop.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] Comments on IS-IS for IPv6
Cc: isis-wg@juniper.net
In-Reply-To: <20010319091242.A26591@nexthop.com>
References: <3AB4146D.A0DEA9C6@redback.com>
 <AD35145AF4A8D411BD6702204804F28302FC4053@zhard00m.europe.nortel.com>
 <3AB4146D.A0DEA9C6@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: Mon, 19 Mar 2001 11:34:48 -0500



>Further the draft leaves open the above "misconfiguration" state and
>implementors are free to actually run multiple SPFs paying attention
>to the NLPID in the LSPs so as to restrict the graph to only supported
>protocols.  This removes the "all routers must support the same protocols
>in an area" restriction.

This is a great goal -- to permit mixing within a subdomain, unlike the
way it currently is for IP+OSI.  But  is this sufficient?  I think it
only works if you require all IPV6-capable routers to support IPV4.
Otherwise, you'd have an IPV4-only IS assuming that it can relay packets
through IPV6-only routers.

To make it possible to mix IPV6-only, IPV6+IPV4, and IPV4 only
implementations, we'd need to put the IPV6 IS adjacencies in a
new TLV.  Or are IPV6-only implementations too far in the future
for us to carefully consider them?  (Or did I get this wrong to
start with?)

Another problem with "leaving an implementation free" to discriminate
or not between protocols seems to me like it could cause routes to be
calculated differently by different routers, causing loops or black
holes.  If we do discriminate, shouldn't we require it of all routers
that implement the new RFC?  (Perhaps the answer here is that "some
new implementations can be mixed in areas, some can't". Is this what
we want?)  Forgive me if this was already discussed and I missed it,
but I would recommend requiring the discrimination when running SPF
and see if anyone objects. 

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  Mon Mar 19 13:35:02 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA17787
	for <isis-archive@odin.ietf.org>; Mon, 19 Mar 2001 13:35:00 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA57660;
	Mon, 19 Mar 2001 11:09:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA57648
	for <isis-wg@spider.juniper.net>; Mon, 19 Mar 2001 11:08:05 -0800 (PST)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.43.88])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2JIT8b25383;
	Mon, 19 Mar 2001 10:29:08 -0800 (PST)
X-JNPR-Received-From: outside
Received: from sj-msg-av-1.cisco.com (sj-msg-av-1.cisco.com [171.69.11.130])
	by sj-msg-core-2.cisco.com (8.9.3/8.9.1) with ESMTP id KAA10748;
	Mon, 19 Mar 2001 10:31:41 -0800 (PST)
Received: from mailman.cisco.com (localhost [127.0.0.1])
	by sj-msg-av-1.cisco.com (8.10.1/8.10.1) with ESMTP id f2JIVL621552;
	Mon, 19 Mar 2001 10:31:21 -0800 (PST)
Received: from emailid-pc (ssh-sj1.cisco.com [171.68.225.134]) by mailman.cisco.com (8.9.3/CISCO.SERVER.1.2) with ESMTP id KAA26725; Mon, 19 Mar 2001 10:31:18 -0800 (PST)
Message-Id: <4.2.0.58.20010319112742.009f81c0@127.0.0.1>
X-Sender: mbartell@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
To: Brian Edwards <bedwards@juniper.net>,
        "'isis-wg@juniper.net'" <isis-wg@juniper.net>
From: Micah Bartell <mbartell@cisco.com>
Subject: Re: [Isis-wg] M-ISIS
In-Reply-To: <C0D6C1C24CDBE1449BFEF1B72AFBF3A7026357E5@postal.jnpr.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Mar 2001 12:30:34 -0600

Isn't the idea of this draft to be a generic model for providing multiple topologies in the same AFI?

I am also concerned about the AFI grouping that is done within this proposal.  We take multiple AFI's and include them in a single TLV....I think it may worthwhile to consider the grouping a bit closer.

For example:

AFI = IPv4
    Sub-AFI = Unicast
    Sub-AFI = Multicast
    Sub-AFI = VPN

AFI = IPv6
    Sub-AFI = Unicast
    Sub-AFI = Multicast
    Sub-AFI = VPN

AFI = CLNS

(Inband Management Network is a member of VPN Sub-AFI)

This draft is taking all of the IPvX AFI's and Sub-AFI's and just mixing them all together in a single TLV.  IS-IS is an integrated protocol, we do not need to integrate it all at the TLV level again.  I would say we have plenty of TLV numbers available to cover about the next 50-75 protocols developed.  If we can resolve the number of fragments limitation, we should be fine to carry all of this TE information.  (How long before our LSPs are 90% TE info, and 10% routing info?)

It makes sense to have the IPv4 TLV (135) and the IPv6 (236) be the primary TLV for their respective AFI, and have Sub-AFI information contained within.

This draft does not remove the need for TLV22, but adds another TLV222, which would contain redundant information.  The same holds true for TLV135 and TLV235.  In fact, how many copies of the same link or prefix would we carry potentiallly?  This would cause a fair amount of LSP Bloat, IMHO.

If your goal is to create multiple topologies for IPv4 and IPv6, then create them on AFI boundaries.  Using the Sub-AFI as the boundary removes the ability to leverage common information across that AFI.  But a generic catch-all for all AFI's is not the right method.  

It can be argued that TLV 135 is going to become too bloated.  Maybe TLV 135 should be used primarily to carry TE information, allowing for a separate TLV that is routing specific.

Take your TLV 235 for instance.  Make this IPv4 specific.  Then we have the following sub-tlvs:

       sub-TLV 1: Unicast       Length: 4    Value: Metric
       sub-TLV 2: Multicast     Length: 4    Value: Metric
       sub-TLV 3: VPN Route     Length: 8    Value: VPN ID<4> Metric<4>

Now we take TLV 236 and relegate that to TE Information and the standard topology.  We create TLV 237 for our IPv6 MT TLV, with the following sub-TLV's.

       sub-TLV 1: Unicast       Length: 4    Value: Metric
       sub-TLV 2: Multicast     Length: 4    Value: Metric
       sub-TLV 3: VPN Route     Length: 8    Value: VPN ID<4> Metric<4>

Now we take a look at TLV22.  This is going to have to carry our TE information and the default metric.  Now let's assume that we wish to carry multiple topologies.  So we create TLV 222 and TLV 223.  We now have our MT Extended IS Reachability TLV's.  One for IPv4 and one for IPv6.  Our sub-TLVs would be as follows:

       sub-TLV 1: Unicast       Length: 4    Value: Metric
       sub-TLV 2: Multicast     Length: 4    Value: Metric
       sub-TLV 3: VPN Route     Length: 8    Value: VPN ID<4> Metric<4>

If all of the topologies are congruent, you don't need to include a sub-TLV and you just default to the metric in TLV 22.  In fact in all of the *new* TLV's mentioned here, the Unicast sub-TLV is optional, because that information is still carried in the main TLV.

Obviously the formatting of these TLV's is a bit different, because in the standard TLV's you would not need a sub-TLV for unicast due to the default metric.  But since these MT TLVs are in addition to the main TLV, the unicast metric is optional in the MT TLV.

More or less this is just off the top of my head, so if this is based off an incorrect understanding about how the MT draft works....

/mpb

At 04:58 PM 3/16/2001 -0800, Brian Edwards wrote:

>Instead of specifying reserved MT ID #'s in the M-ISIS draft; why not use
>the Address Families defined in RFC1700 like MBGP? I mentioned this to
>Nischal and he thinks it is a good idea, so I am sending it to the working
>group for comments.
>
>-Brian
>_______________________________________________
>Isis-wg mailing list  -  Isis-wg@external.juniper.net
>http://external.juniper.net/mailman/listinfo/isis-wg 


--
Micah Bartell, CCIE #5069			mbartell@cisco.com
Network Consulting Engineer   			Phone: 469.255.1806
SP-Advanced Network Services			Cisco Systems, Inc		
--
The Network Works, No Excuses
_______________________________________________
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 Mar 19 17:18:21 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23713
	for <isis-archive@odin.ietf.org>; Mon, 19 Mar 2001 17:18: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 OAA58603;
	Mon, 19 Mar 2001 14:53:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA58586
	for <isis-wg@spider.juniper.net>; Mon, 19 Mar 2001 14:52:06 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2JMD8b36571
	for <isis-wg@juniper.net>; Mon, 19 Mar 2001 14:13:08 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com (prz-laptop.redback.com [155.53.36.102])
	by prattle.redback.com (Postfix) with ESMTP
	id C1A6D39BC2C; Mon, 19 Mar 2001 14:15:19 -0800 (PST)
Message-ID: <3AB6744B.A6E037CF@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: "Christian E . Hopps" <chopps@nexthop.com>
Cc: Philip Christian <christi@nortelnetworks.com>, isis-wg@juniper.net
Subject: Re: [Isis-wg] Comments on IS-IS for IPv6
References: <AD35145AF4A8D411BD6702204804F28302FC4053@zhard00m.europe.nortel.com> <3AB4146D.A0DEA9C6@redback.com> <20010319091242.A26591@nexthop.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Mar 2001 13:04:11 -0800
Content-Transfer-Encoding: 7bit

>
> I actually coded my implementation this way.  The problem is that this
> doesn't solve all the misconfiguration situations.  I think the much
> more likely "mis"-configuration will be for a router to be v6 only and
> its neighbors dual v4v6. In this case the adjacency will form but v4
> traffic will get dropped by the v6 only router.
>
> Further the draft leaves open the above "misconfiguration" state and
> implementors are free to actually run multiple SPFs paying attention
> to the NLPID in the LSPs so as to restrict the graph to only supported
> protocols.  This removes the "all routers must support the same protocols
> in an area" restriction.
>
> So, if people feel it is important I think we could add some text indicating
> that adjacencies should only form when the intersection of the NLPID
> is non-empty.  This will cover the v6 only to v4 only router case, but
> not restrict the dual v6v4 to v6 only case.

now, wouldn't you just not advertise any ipv4 prefixes from the ipv6 onliy
router. So no ipv4 traffic would even head towards a ipv6-only router ?
So if an ipv6+ipv4 router forms adjacency, only traffic crossing it would
be ipv6 anyway ?

    -- 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 Mar 19 17:19:40 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id RAA23762
	for <isis-archive@odin.ietf.org>; Mon, 19 Mar 2001 17:19: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 OAA58639;
	Mon, 19 Mar 2001 14:54:06 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id OAA58594
	for <isis-wg@spider.juniper.net>; Mon, 19 Mar 2001 14:53:01 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2JME3b36671
	for <isis-wg@juniper.net>; Mon, 19 Mar 2001 14:14:03 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com (prz-laptop.redback.com [155.53.36.102])
	by prattle.redback.com (Postfix) with ESMTP
	id 21180B76799; Mon, 19 Mar 2001 14:16:13 -0800 (PST)
Message-ID: <3AB67481.FCD645AD@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: "Christian E . Hopps" <chopps@nexthop.com>
Cc: Philip Christian <christi@nortelnetworks.com>, isis-wg@juniper.net
Subject: Re: [Isis-wg] Comments on IS-IS for IPv6
References: <AD35145AF4A8D411BD6702204804F28302FC4053@zhard00m.europe.nortel.com> <3AB4146D.A0DEA9C6@redback.com> <20010319091242.A26591@nexthop.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Mar 2001 13:05:05 -0800
Content-Transfer-Encoding: 7bit

>
> So, if people feel it is important I think we could add some text indicating
> that adjacencies should only form when the intersection of the NLPID
> is non-empty.  This will cover the v6 only to v4 only router case, but
> not restrict the dual v6v4 to v6 only case.

I just wrote a stupid e-mail. Ignore it, I forgot the transit case ...

    silly me

    -- 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 Mar 19 18:16:01 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id SAA25274
	for <isis-archive@odin.ietf.org>; Mon, 19 Mar 2001 18:16:00 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA59043;
	Mon, 19 Mar 2001 15:51:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id PAA59030
	for <isis-wg@spider.juniper.net>; Mon, 19 Mar 2001 15:50:32 -0800 (PST)
Received: from presque.djinesys.com (presque.djinesys.com [198.108.88.2])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2JNBXb39179
	for <isis-wg@juniper.net>; Mon, 19 Mar 2001 15:11:33 -0800 (PST)
X-JNPR-Received-From: outside
Received: from q.nexthop.com ([141.211.130.163])
	by presque.djinesys.com (8.9.3/8.9.3) with ESMTP id SAA94788;
	Mon, 19 Mar 2001 18:12:49 -0500 (EST)
	(envelope-from chopps@q.nexthop.com)
Received: (from chopps@localhost)
	by q.nexthop.com (8.11.0/8.11.0) id f2JNDjD27772;
	Mon, 19 Mar 2001 18:13:45 -0500 (EST)
From: "Christian E . Hopps" <chopps@nexthop.com>
To: Jeff Learman <jlearman@cisco.com>
Cc: isis-wg@juniper.net
Subject: Re: [Isis-wg] Comments on IS-IS for IPv6
Message-ID: <20010319181335.A27758@nexthop.com>
References: <3AB4146D.A0DEA9C6@redback.com> <AD35145AF4A8D411BD6702204804F28302FC4053@zhard00m.europe.nortel.com> <3AB4146D.A0DEA9C6@redback.com> <20010319091242.A26591@nexthop.com> <4.3.2.7.2.20010319112244.019a51c8@dingdong.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <4.3.2.7.2.20010319112244.019a51c8@dingdong.cisco.com>; from jlearman@cisco.com on Mon, Mar 19, 2001 at 11:34:48AM -0500
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Mar 2001 18:13:35 -0500

On Mon, Mar 19, 2001 at 11:34:48AM -0500, Jeff Learman wrote:
> 
> 
> >Further the draft leaves open the above "misconfiguration" state and
> >implementors are free to actually run multiple SPFs paying attention
> >to the NLPID in the LSPs so as to restrict the graph to only supported
> >protocols.  This removes the "all routers must support the same protocols
> >in an area" restriction.
> 
> This is a great goal -- to permit mixing within a subdomain, unlike the
> way it currently is for IP+OSI.  But  is this sufficient?  I think it
> only works if you require all IPV6-capable routers to support IPV4.
> Otherwise, you'd have an IPV4-only IS assuming that it can relay packets
> through IPV6-only routers.

You are correct.  I suppose I was only thinking about the "IPv6 is a
subset of the IPv4 router set" case.  I really don't think we need to
overly complicate the extension to support any other configurations.

Its worth noting that multiple vendors at this point have implemented
this draft, in part I think because it was so easy. :)

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


From isis-wg-admin@spider.juniper.net  Mon Mar 19 18: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 SMTP id SAA26501
	for <isis-archive@odin.ietf.org>; Mon, 19 Mar 2001 18:54:08 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA59271;
	Mon, 19 Mar 2001 16:28:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id QAA59259
	for <isis-wg@spider.juniper.net>; Mon, 19 Mar 2001 16:27:04 -0800 (PST)
Received: from rtp-msg-core-1.cisco.com (rtp-msg-core-1.cisco.com [161.44.11.97])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2JNm5b41308
	for <isis-wg@juniper.net>; Mon, 19 Mar 2001 15:48:05 -0800 (PST)
X-JNPR-Received-From: outside
Received: from dingdong.cisco.com (dingdong.cisco.com [64.102.17.16])
	by rtp-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id SAA08783;
	Mon, 19 Mar 2001 18:49:33 -0500 (EST)
Received: from JLEARMAN-W2K.cisco.com (dhcp-64-102-83-127.cisco.com [64.102.83.127])
	by dingdong.cisco.com (Mirapoint)
	with ESMTP id ACH19945;
	Mon, 19 Mar 2001 18:50:16 -0500 (EST)
Message-Id: <4.3.2.7.2.20010319181948.01add4b8@dingdong.cisco.com>
X-Sender: jlearman@dingdong.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
To: "Christian E . Hopps" <chopps@nexthop.com>
From: Jeff Learman <jlearman@cisco.com>
Subject: Re: [Isis-wg] Comments on IS-IS for IPv6
Cc: isis-wg@juniper.net
In-Reply-To: <20010319181335.A27758@nexthop.com>
References: <4.3.2.7.2.20010319112244.019a51c8@dingdong.cisco.com>
 <3AB4146D.A0DEA9C6@redback.com>
 <AD35145AF4A8D411BD6702204804F28302FC4053@zhard00m.europe.nortel.com>
 <3AB4146D.A0DEA9C6@redback.com>
 <20010319091242.A26591@nexthop.com>
 <4.3.2.7.2.20010319112244.019a51c8@dingdong.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Mon, 19 Mar 2001 18:49:24 -0500


Chris,

>> This is a great goal -- to permit mixing within a subdomain, unlike the
>> way it currently is for IP+OSI.  But  is this sufficient?  I think it
>> only works if you require all IPV6-capable routers to support IPV4.
>> Otherwise, you'd have an IPV4-only IS assuming that it can relay packets
>> through IPV6-only routers.
>
>You are correct.  I suppose I was only thinking about the "IPv6 is a
>subset of the IPv4 router set" case.  I really don't think we need to
>overly complicate the extension to support any other configurations.
>
>Its worth noting that multiple vendors at this point have implemented
>this draft, in part I think because it was so easy. :)

It may be better than I first thought.  True, we won't be able to
intermix IPV6-only, dual, and IPV4-only.  But we might be able to
mix IPV6 with Dual, just as we can now mix Dual with IPV4.

If there was a configuration option to enable checking protocols-supported
when building both IPV4 FDBs, then we could do this.  Initially,
the IPV4 option would be disabled, so IPV4 FDBs would match between
old and new implementations.  As soon as all IPV4-only routers were
upgraded (I assume we'll have a few years yet to do that), the options
could be enabled, and we could mix Dual and IPV6.  Note that I'm
assuming that checking the option for IPV6 FDBs is required.
Otherwise, I think we get mayhem.

A little careful thought now might really reduce headaches later!

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  Wed Mar 21 03:50:17 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA08587
	for <isis-archive@odin.ietf.org>; Wed, 21 Mar 2001 03:50: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 BAA66882;
	Wed, 21 Mar 2001 01:18:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id BAA66870
	for <isis-wg@spider.juniper.net>; Wed, 21 Mar 2001 01:17:24 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2L8c6b98417;
	Wed, 21 Mar 2001 00:38:06 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 2A9C1B7679A; Wed, 21 Mar 2001 00:40:12 -0800 (PST)
To: Brian Edwards <bedwards@juniper.net>, Micah Bartell <mbartell@cisco.com>
Cc: "'isis-wg@juniper.net'" <isis-wg@juniper.net>
Subject: Re: [Isis-wg] M-ISIS 
In-reply-to: Mail from Brian Edwards <bedwards@juniper.net> 
 dated Fri, 16 Mar 2001 16:58:15 PST
 <C0D6C1C24CDBE1449BFEF1B72AFBF3A7026357E5@postal.jnpr.net> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20010321084012.2A9C1B7679A@prattle.redback.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 21 Mar 2001 00:39:49 -0800


I think M-ISIS is very different from MBGP. This is not meant to
"transport" AFI and sub-AFI routes as the case in MBGP. When we proposed
the reserved number and labelled them as "IPv6" or "multicast", it does
not mean inside those TLVs, we will have IPv6 routes, or 224.x.x.x routes.
They are still IPv4 unicast routes. Those routes are just "belong" to the
IGP topologies we designate them for the use of IPv6 or of multicast.
An example comes to mind will be UUcast, which is a seperate topology
from regular IP unicast backbones and of course runs it's own IGP. Even
though the purpose of that network is for multicast business, but the IGP
is no different from the IGPs running in unicast IP backbones.

Besides it uses up two more bytes than the MT ID# scheme, it will also
casue confusing since the AFI or sub-AFI don't really have their true
meaning. While the other useful things as In-Band management, special
QoS networks may not be defined in the rfc1700. I would say just keep
the current draft number scheme.

thanks.

 ]
 ]Instead of specifying reserved MT ID #'s in the M-ISIS draft; why not use
 ]the Address Families defined in RFC1700 like MBGP? I mentioned this to
 ]Nischal and he thinks it is a good idea, so I am sending it to the working
 ]group for comments.
 ]
 ]-Brian
 ]_______________________________________________
 ]Isis-wg mailing list  -  Isis-wg@external.juniper.net
 ]http://external.juniper.net/mailman/listinfo/isis-wg

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


From isis-wg-admin@spider.juniper.net  Wed Mar 21 12:30:26 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id MAA01928
	for <isis-archive@odin.ietf.org>; Wed, 21 Mar 2001 12:30:25 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA69129;
	Wed, 21 Mar 2001 10:03:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA69117
	for <isis-wg@spider.juniper.net>; Wed, 21 Mar 2001 10:02:45 -0800 (PST)
Received: from dino-pc.procket.com (flowpoint.procket.com [205.253.146.41])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2LHNFb12457;
	Wed, 21 Mar 2001 09:23:15 -0800 (PST)
X-JNPR-Received-From: outside
Received: (from dino@localhost)
	by dino-pc.procket.com (8.9.3/8.9.3) id JAA04063;
	Wed, 21 Mar 2001 09:24:50 -0800
Message-Id: <200103211724.JAA04063@dino-pc.procket.com>
X-Authentication-Warning: dino-pc.procket.com: dino set sender to dino@dino-pc.procket.com using -f
From: Dino Farinacci <dino@procket.com>
To: naiming@redback.com
CC: bedwards@juniper.net, mbartell@cisco.com, isis-wg@juniper.net
In-reply-to: <20010321084012.2A9C1B7679A@prattle.redback.com> (message from
	Naiming Shen on Wed, 21 Mar 2001 00:39:49 -0800)
Subject: Re: [Isis-wg] M-ISIS
References:  <20010321084012.2A9C1B7679A@prattle.redback.com>
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Wed, 21 Mar 2001 09:24:50 -0800

>> I think M-ISIS is very different from MBGP. This is not meant to
>> "transport" AFI and sub-AFI routes as the case in MBGP. When we proposed
>> the reserved number and labelled them as "IPv6" or "multicast", it does
>> not mean inside those TLVs, we will have IPv6 routes, or 224.x.x.x routes.

    Naiming, you seem to be implying MBGP carries 224.x.x.x routes. This is
    certainly not true. If that wasn't what you intended, ignore this message.

Dino

     
_______________________________________________
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 Mar 22 10:24:17 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA12929
	for <isis-archive@odin.ietf.org>; Thu, 22 Mar 2001 10:24: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 HAA74290;
	Thu, 22 Mar 2001 07:57:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id HAA74278
	for <isis-wg@spider.juniper.net>; Thu, 22 Mar 2001 07:56:57 -0800 (PST)
Received: from prattle.redback.com (prattle.redback.com [155.53.12.9])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2MFHVb51791;
	Thu, 22 Mar 2001 07:17:31 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com (yoo-hoo.redback.com [155.53.12.43])
	by prattle.redback.com (Postfix) with ESMTP
	id 9F3E6B76783; Thu, 22 Mar 2001 07:19:50 -0800 (PST)
To: Dino Farinacci <dino@procket.com>
Cc: bedwards@juniper.net, mbartell@cisco.com, isis-wg@juniper.net
Subject: Re: [Isis-wg] M-ISIS 
In-reply-to: Mail from Dino Farinacci <dino@procket.com> 
 dated Wed, 21 Mar 2001 09:24:50 PST
 <200103211724.JAA04063@dino-pc.procket.com> 
From: Naiming Shen <naiming@redback.com>
Message-Id: <20010322151950.9F3E6B76783@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: Thu, 22 Mar 2001 07:19:27 -0800

 ]>> I think M-ISIS is very different from MBGP. This is not meant to
 ]>> "transport" AFI and sub-AFI routes as the case in MBGP. When we proposed
 ]>> the reserved number and labelled them as "IPv6" or "multicast", it does
 ]>> not mean inside those TLVs, we will have IPv6 routes, or 224.x.x.x routes.
 ]
 ]    Naiming, you seem to be implying MBGP carries 224.x.x.x routes. This is
 ]    certainly not true. If that wasn't what you intended, ignore this message
.

      Dino. Thanks pointing this out. My mistake. I had a wrong impression
      that MBGP were able to carry both types of routes. MBGP made it's
      mistake on this(using the AFIs), that's why so confusing:-)

      And I still mentain the rest part of my argument. But if we are
      going to use the AFIs, we probably need a bit to indicate the value
      is or not from the AFIs of rfc1700, since some of the applications
      has little to do with address family; or make the AFI when it's 0,
      the sub-AFI portion is our M-ISIS definition of topologies.

      Thanks.

 ]
 ]Dino
 ]
 ]     

- 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 Mar 27 22:16:14 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA12264
	for <isis-archive@odin.ietf.org>; Tue, 27 Mar 2001 22:16:13 -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 TAA07189;
	Tue, 27 Mar 2001 19:51:05 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id TAA07176
	for <isis-wg@spider.juniper.net>; Tue, 27 Mar 2001 19:50:20 -0800 (PST)
Received: from ce-nfs-1.cisco.com (ce-nfs-1.cisco.com [171.68.202.251])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2S39wb28912
	for <isis-wg@juniper.net>; Tue, 27 Mar 2001 19:09:58 -0800 (PST)
X-JNPR-Received-From: outside
Received: from AZININ-W2K.cisco.com (vjorge-dsl1.cisco.com [10.21.134.162])
	by ce-nfs-1.cisco.com (8.8.8+Sun/8.8.8) with ESMTP id TAA27888;
	Tue, 27 Mar 2001 19:12:32 -0800 (PST)
From: Alex Zinin <azinin@cisco.com>
X-Mailer: The Bat! (v1.41) REG'D / CD5BF9353B3B7091
Reply-To: Alex Zinin <azinin@cisco.com>
Organization: Cisco Systems
X-Priority: 3 (Normal)
Message-ID: <9797.010327@cisco.com>
To: Danny McPherson <danny@AMBERNETWORKS.COM>
CC: OSPF@DISCUSS.MICROSOFT.COM, isis-wg@juniper.net
In-reply-To: <200103272235.PAA13925@tcb.net>
References: <200103272235.PAA13925@tcb.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] OSPF WG: Retstart: moving further                    was: [Re: draft-ietf-ospf-hitless-restart-00.txt, draft-ietf-idr-restart-00.txt]
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Tue, 27 Mar 2001 19:08:10 -0800
Content-Transfer-Encoding: 7bit


Danny:

Thanks for your thoughts, the message was a good break
in the middle of a battle... see my comments inline, please.

> IS-IS:

>   o "Restart signaling for ISIS" (draft-shand-ISIS-restart-00.txt),
>     which discusses restart and resync for IS-IS.

It must be noted that the discussion there was much more productive.

>     The IS-IS WG charter is quite dated as well...

> OSPF:

>   o "OSPF Restart Signaling" (draft-ietf-ospf-restart-01.txt),
>     which was the first of the OSPF proposals and triggered
>     [unfortunately] competing proposals to provide this
>     functionality.  This work falls into the "We'll accept
>     anything as a WG item" category".

Add draft-ietf-ospf-oob-resync-01.txt here.
This is a useful mechanism that is also used in our graceful
restart implementation to resync LSDB on restart.

>   o "Hitless OSPF Restart" (draft-ietf-ospf-hitless-restart-00.txt),
>     which is John's proposal and falls into the "we'll accept
>     anything as a WG item" category.  I guess this as well is
>     one of the benefits of having a charter with goals and
>     milestones as recent as Jun 98.

>   o I think an overhaul of the OSPF charter is necessary (have I
>     missed something in this area?).

As a message that I sent to the WG today tells, I also think the WG
charter should be updated.

> I'll not argue the merits of the two proposals (type 9's versus new
> bits in existing packets, resync, nsync, fairy dust, etc..), as I
> think they've pretty much been beat to death.  However, regardless of
> what some of the author(s) have said, I feel they could be merged into
> a single document and consensus reach in the WG based on the technical
> merits of each.

We are ready to work towards this.
This does require, however, that both sides are
willing to negotiate.

> Certainly, requirements documents would help to scope this discussion,
> as would up to date charters and milestones.  After all, I'd hope an
> associated requirements document would specify whether the additional
> functionality of Alex's proposal is interesting to the community.

> IMO, if we're planning to implement any of this, we might as well go
> ahead and provide a full set of capabilities (not that any one of them
> MUST be enabled in a network, mind you), as well as a common framework
> and architecture for NSF/headless routing.

I think it's doable and will have merit.
In fact, we have started working on something like this with
a number of folks... I think we can resume the effort and
come up with the requirement and framework documents.
Interested parties, please drop me a line.

Thanks again!

Alex.


_______________________________________________
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 Mar 30 13:23:11 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id NAA02011
	for <isis-archive@odin.ietf.org>; Fri, 30 Mar 2001 13:23:10 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA21948;
	Fri, 30 Mar 2001 10:58:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id KAA21900
	for <isis-wg@spider.juniper.net>; Fri, 30 Mar 2001 10:53:31 -0800 (PST)
Received: from riverstonenet.com (mail.riverstonenetworks.net [63.113.148.10])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2UIChb34488
	for <isis-wg@juniper.net>; Fri, 30 Mar 2001 10:12:43 -0800 (PST)
X-JNPR-Received-From: outside
Received: from riverstonenet.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago)
	id KAA28844; Fri, 30 Mar 2001 10:15:27 -0800 (PST)
Message-ID: <3AC4BD07.B9AC0522@riverstonenet.com>
From: Thippanna Hongal <hongal@riverstonenet.com>
Organization: Riverstone Networks Inc
X-Mailer: Mozilla 4.7 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: isis-wg@juniper.net
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [Isis-wg] SNMP MIB
Sender: isis-wg-admin@spider.juniper.net
Errors-To: isis-wg-admin@spider.juniper.net
X-BeenThere: isis-wg@external.juniper.net
X-Mailman-Version: 2.0rc1
Precedence: bulk
List-Help: <mailto:isis-wg-request@external.juniper.net?subject=help>
List-Post: <mailto:isis-wg@external.juniper.net>
List-Subscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=subscribe>
List-Id: IETF IS-IS working group <isis-wg.external.juniper.net>
List-Unsubscribe: <http://external.juniper.net/mailman/listinfo/isis-wg>,
	<mailto:isis-wg-request@external.juniper.net?subject=unsubscribe>
List-Archive: <http://external.juniper.net/pipermail/isis-wg/>
Date: Fri, 30 Mar 2001 10:06:15 -0700
Content-Transfer-Encoding: 7bit

hi ISIS-WG

I am looking for SNMP Management Information Base for the IS-IS.
Is anybody can point me to that document.

thanks
hongal

Thippanna Hongal
Riverstone Networks Inc. Santa Clara CA 95054

_______________________________________________
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 Mar 30 14:00:17 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA05234
	for <isis-archive@odin.ietf.org>; Fri, 30 Mar 2001 14:00:17 -0500 (EST)
Received: from spider.juniper.net (localhost [127.0.0.1])
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA22185;
	Fri, 30 Mar 2001 11:36:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA22173
	for <isis-wg@spider.juniper.net>; Fri, 30 Mar 2001 11:35:00 -0800 (PST)
Received: from bridge.axiowave.com (mail.axiowave.com [209.6.34.2])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2UIsCb36296
	for <isis-wg@juniper.net>; Fri, 30 Mar 2001 10:54:12 -0800 (PST)
X-JNPR-Received-From: outside
Message-ID: <EB5FFC72F183D411B3820006295734296AE867@r2d2.axiowave.com>
From: Jeff Parker <jparker@axiowave.com>
To: "'Thippanna Hongal'" <hongal@riverstonenet.com>, isis-wg@juniper.net
Subject: RE: [Isis-wg] SNMP MIB
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, 30 Mar 2001 13:56:44 -0500

> hi ISIS-WG
> 
> I am looking for SNMP Management Information Base for the IS-IS.
> Is anybody can point me to that document.
> 
> thanks
> hongal
> 
> Thippanna Hongal
> Riverstone Networks Inc. Santa Clara CA 95054

Thippanna -
	It has aged off the list.  I can send you a
copy of the older version, if that would help.

- 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 Mar 30 14:09:28 2001
Received: from external.juniper.net (spider.juniper.net [207.17.137.40])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id OAA06079
	for <isis-archive@odin.ietf.org>; Fri, 30 Mar 2001 14:09: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 LAA22275;
	Fri, 30 Mar 2001 11:45:04 -0800 (PST)
Received: from colo-rojo.jnpr.net (ns1.juniper.net [207.17.137.28] (may be forged))
	by external.juniper.net (8.9.3/8.9.3) with ESMTP id LAA22260
	for <isis-wg@spider.juniper.net>; Fri, 30 Mar 2001 11:44:09 -0800 (PST)
Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241])
	by colo-rojo.jnpr.net (8.11.2/8.11.2) with ESMTP id f2UJ3Lb36748
	for <isis-wg@juniper.net>; Fri, 30 Mar 2001 11:03:21 -0800 (PST)
X-JNPR-Received-From: outside
Received: from redback.com ([63.200.51.45])
 by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9)
 with ESMTP id <0GB000NNPYA93R@mta5.snfc21.pbi.net> for isis-wg@juniper.net;
 Fri, 30 Mar 2001 11:03:45 -0800 (PST)
From: Tony Przygienda <prz@redback.com>
Subject: Re: [Isis-wg] SNMP MIB
To: Jeff Parker <jparker@axiowave.com>
Cc: "'Thippanna Hongal'" <hongal@riverstonenet.com>, isis-wg@juniper.net
Message-id: <3AC4C7C8.830DE861@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: <EB5FFC72F183D411B3820006295734296AE867@r2d2.axiowave.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, 30 Mar 2001 09:52:08 -0800
Content-Transfer-Encoding: 7bit

Jeff Parker wrote:

> > hi ISIS-WG
> >
> > I am looking for SNMP Management Information Base for the IS-IS.
> > Is anybody can point me to that document.
> >
> > thanks
> > hongal
> >
> > Thippanna Hongal
> > Riverstone Networks Inc. Santa Clara CA 95054
>
> Thippanna -
>         It has aged off the list.  I can send you a
> copy of the older version, if that would help.
>
> - jeff parker

jeff, could you resubmit ? Or did the work die ?

    thanks

    -- tony


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


